rpmdev-setuptree
~/rpmbuild/SRPMS/
~/rpmbuild/SPECS/
~/rpmbuild/SOURCES/
~/rpmbuild/RPMS/
~/rpmbuild/BUILD/
~/.rpmmacros
sudo dnf download --source package
Showing posts with label dnf. Show all posts
Showing posts with label dnf. Show all posts
Saturday, May 20, 2017
rpmbuild random notes
sudo dnf install rpmdevtools
rpmdev-setuptree
~/rpmbuild/SRPMS/
~/rpmbuild/SPECS/
rpmdev-setuptree
~/rpmbuild/SRPMS/
~/rpmbuild/SPECS/
Thursday, March 9, 2017
Fedora dnf history
Sometimes it can happen that you remove a package and inadvertently you remove a bunch of dependencies. Like removing the entire desktop manager: what a mess, waht a pain in the ass!
Sometimes dependecies are strange.
Rarely, but it can happen too, after an update something doesn't work anymore. Maybe the updated package is buggy? Better waiting for a fix.
By the way. If you install or uninstall packages by mistake, there is a way to rollback the changes: history.
sudo dnf history list
And you can see the dnf activities.
sudo dnf history info 132
You can see the details of the dnf command labeled as 132
Let's say 132 is the number of the last action
ID | Command line | Date and time | Action(s) | Altered
-------------------------------------------------------------------------------
132 | update | 2017-03-09 16:06 | Update | 8
Issue the following command in order to uninstall these updates:
sudo dnf history undo 132
And you will get something like:
Undoing transaction 132, from Thu Mar 9 21:06:10 2017
Sometimes dependecies are strange.
Rarely, but it can happen too, after an update something doesn't work anymore. Maybe the updated package is buggy? Better waiting for a fix.
By the way. If you install or uninstall packages by mistake, there is a way to rollback the changes: history.
sudo dnf history list
And you can see the dnf activities.
sudo dnf history info 132
You can see the details of the dnf command labeled as 132
Let's say 132 is the number of the last action
ID | Command line | Date and time | Action(s) | Altered
-------------------------------------------------------------------------------
132 | update | 2017-03-09 16:06 | Update | 8
Issue the following command in order to uninstall these updates:
sudo dnf history undo 132
And you will get something like:
Undoing transaction 132, from Thu Mar 9 21:06:10 2017
No package libgdata-0:0.17.6-3.fc25.x86_64 available.
Error: An operation cannot be undone
Well. WTF!
It seems that, if you would like to have the option to rollback updates, you must enable packages cache beforehand with keepcache=1 in the /etc/dnf/dnf.conf configuration file. This could lead to some disk space used to store previous versions of rpms? I must investigate a bit deeper.
References:
Subscribe to:
Posts (Atom)