Hi On Tue, Feb 25, 2014 at 11:17:12AM +0100, ha wrote: > > > >Please note the difference between *are/is* installed, and *were* installed. > > > >I would expect dpkg -S to fail if those packages had been wrongly > >removed (corrupting dpkg database) but the pam and man files are > >extremely unlikely to be the result of malware. The OP never responded > >to my query about the other files that would have been installed - or > >checked the installation history with dpkg --get-selections (it won't > >show if purge was run, but then, those files would likely not be left). > > > > Sorry I didn't follow up on this one... > What info did you requested? > How can I check if the package was installed (but is there no more)? > I believe that dpkg --get-selections shows only available packages.
If the package was *purged* I don't think it should be different that never-installed-in-the-first-place. (If I'm wrong, somebody shout!) However, if it was installed and then removed, then the configuration files should remain, and "dpkg --status $packagename" would report: Status: deinstall ok config-files For the uninitiated: Removing a debian package will not remove the configuration files. Which is a brilliant if you subsequently re-install the package. To also remove configuration files, you need to *purge* the package. Since configuration files are usually very small, most people are not too bothered about the difference. However.... Neither seems to match the situation of the original poster - (s?)he seems to have both a binary *and* a configuration file... -- Karl E. Jorgensen -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140225102726.GB13544@hawking