@beardyunixer Doh. That actually exists? Thanks - totally wasn't aware of that.
# apt-show-versions | egrep -vc jessie
Ok, this looks much more manageable than the 65 outdated packages before... Yeah, really should update that Splunk... Perhaps get rid of the cnews installation too - it's not as if I still had a working UUCP uplink into Usenet anymore...
# apt-show-versions | egrep -v jessie | cut -d' ' -f-2
@galaxis a long shot, but you might get data from strings and similar tool to understand what compiler version has been used.Infer the debian release from that.
you can md5sum files on both you debian and the package upstream (needle / haystack).
Depending on the list of files contained in a package you might be able to get an idea of how old the package is.
the syntax of the config/default file maybe ?
(I'm sure someone already reply to this toot with the right reply ™)
@kyzh Well, I was hoping for something more obvious, like some information in the apt or dpkg databases... 😑
Kind of does the trick - on a system that's on jessie, all older or external packages are shown with a "No available version in archive" comment. For current packages, I get whether they come from jessie or jessie-security, for example.
Didn't know about that tool up to now.
@galaxis apt-cache showpkg YOURPACKAGEHERE and look for the line below Versions: it will have the path on the repo which will have the release codename in it.
@press5 The problem with that is that I need to know in advance which packages to look for - but I wanted to find out which of the roughly 1500 packages on the system were obsolete (and not being found by deborphan or apt-get autoremove).
The output seems consistent with apt-show-versions, as the packages where that sais "No available version in archive" have no package path besides (/var/lib/dpkg/status) in the apt-cache showpkg output.
@galaxis this may be bit too late, but before performing release upgrade it is recommended to do so with 'script' command. Then you can grep the output for dl locations.