Weblog entry #3 for jeremiah
See all weblog entries made by jeremiah.
#3
List of installed packages
Posted by jeremiah on Wed 12 Nov 2008 at 12:06
15 11 * * * /usr/bin/dpkg --get-selections > /home/jeremiah/installed_packages.txt
I use the above crontab to get a fresh list of installed packages.
I use the above crontab to get a fresh list of installed packages.
Comments on this Entry
And I use it as part of my backup script. For later restoration with dpkg --set-selections.
[ Parent | Reply to this comment ]
Posted by Anonymous (83.248.xx.xx) on Thu 13 Nov 2008 at 17:00
Hmm, cool. I will have to check out --set-selections, I've never seen it before.
[ Parent | Reply to this comment ]
Is there a verify option like the rpm -V ?
Cheers,
Cheers,
[ Parent | Reply to this comment ]
Short answer: No.
Long answer: My understanding is that rpm -V "verifies" the rpm database. dpkg uses a flat file for a database; /var/lib/dpkg/available, so there is not the same need to verify a database for corruption in the same way as with rpm.
Long answer: My understanding is that rpm -V "verifies" the rpm database. dpkg uses a flat file for a database; /var/lib/dpkg/available, so there is not the same need to verify a database for corruption in the same way as with rpm.
[ Parent | Reply to this comment ]
Actually rpm -V verifies the files of the package in question, and report whether they change or not. I was wondering if such a functionality would be available in debian dpkg.
[ Parent | Reply to this comment ]
What type of changes are you referring to? If they have been updated?
Or if the md5sums changed? Because that type of information is available in the .dsc file that gets uploaded with the package. All debs have a special version number as well - the version number of the upstream software, plus a number followed by a "-". So a deb usually has a version like this: libfoo-perl_1.01-1 with the last two characters (-1) being the version number of the deb package.
It is generally left to the higher level packaging tools like atp-get and aptitude to do the version number and signature checking, dpkg keeps track of the packages on the local system.
The entire package handling system is a toolset, the sum of its parts being more powerful than just rpm or yum for example.
Or if the md5sums changed? Because that type of information is available in the .dsc file that gets uploaded with the package. All debs have a special version number as well - the version number of the upstream software, plus a number followed by a "-". So a deb usually has a version like this: libfoo-perl_1.01-1 with the last two characters (-1) being the version number of the deb package.
It is generally left to the higher level packaging tools like atp-get and aptitude to do the version number and signature checking, dpkg keeps track of the packages on the local system.
The entire package handling system is a toolset, the sum of its parts being more powerful than just rpm or yum for example.
[ Parent | Reply to this comment ]