How do I find out what packages have been installed since the OS was installed? I do not want to know all packages installed, only those that were not part of the initial OS install, and have been explicitly installed afterwards.
For the sake of this question, lets assume a fresh install, as I imagine distro upgrades would complicate matters. I would prefer to use command line, but a GUI solution would be OK if a command or script is not available.
I've had a quick look at the man pages of dpkg
and aptitude
, but didn't see anything obvious. Also, the output of apt-cache show package-name
or dpkg -s pkg-name
doesn't seem to give any dates that can be compared against the date of OS installation (which I would have to work out how to get too).
I have logwatch
on a server that sends daily notifications of what has been installed. My guess is that it parses dpkg.log. I'm not sure this method would be a solution, as many of the install entries may have been logrotated out, especially on older systems. And ideally this should work for any system, desktop or server.
It would also be great if the output could include the version of the package currently installed, but that may be asking too much, and I can always script it later once I have the package names.
All Ubuntu ISO ([UKLX]buntu/Ubuntu-gnome) comes with
.manifest
file that contains the list of all pre-installed packages in the ISO. You can find those manifest files in the same download dir as those ISO on any Ubuntu ISO mirrors. Take the list of available Ubuntu releases as an example; if you haveTrusty
64-bit for example, the manifest link would be http://releases.ubuntu.com/trusty/ubuntu-14.04.2-desktop-amd64.manifest.So once you have this file, just compare the package listing in it against the listing of all installed packages in your Ubuntu using
comm
commandTo explain what the
comm
does, it takes input from 2 files - first one supplies the list of all currently installed packages and the second one the manifest file. The-3
opt suppresses lines that both files have and-2
suppresses lines that only the second file (manifest file, that is) has. So in the end your output contains only lines that only file one has and that gives you packages that you installed manually since the OS was installed.So there you have it.
Edit
If you'd also like to see the package version next to package name in the output, as Slyvain Pineau pointed out, pipe the
comm
command above toxargs dpkg-query -W -f='${binary:Package} ${Version}\n'
so it becomesOr alternatively, with
awk
entirely, This too give the same result as command aboveSee this link for explanation on how the awk cmd work
The initial-status.gz and dpkg-query method from https://unix.stackexchange.com/a/80520/9132 gives the most accurate and concise list for my needs.
Why I like it, and not the others:
The manifest comparison method from Flint's answer and from https://unix.stackexchange.com/a/3624/9132 includes many dependencies and other packages possibly marked as 'required' and installed automatically. For example, it lists libvlc5 and vlc-data, whereas the method above only lists vlc.
The history.log method from https://askubuntu.com/a/250530/16741 will not list all packages if the logs do not go back as far as the release install. It also contains a lot of upgrade commands that would need to be filtered out.
The dpkg --get-selections method, which is an accepted answer from a similar question, lists all packages and dependencies, including those installed with the release. It does not list only those installed explicitly.
Big thanks and congratulations to those who came up with that gem of a script !!!
I wanted to add my 2¢ and I tacked the installation date I deduce from $info.
I did not master the details why $info files are updated or not and when, but it works in practice.
My script lists the latest updates of non dependency packages added after installation.
Giving it a periodic check, I was seeing what I would have manually logged without a single miss.
That is, batches of packets installed for the same reason. Unfortunately, updates break that order.
After a system upgrade, I had a list of my added packages that the upgrade did not update followed by those that it did.
Neat! Enjoy.