| Name |
Last commit
|
Last update |
|---|---|---|
| .. | ||
| cloud | ||
| commands | ||
| database | ||
| files | ||
| internal | ||
| inventory | ||
| messaging | ||
| monitoring | ||
| net_infrastructure | ||
| network | ||
| notification | ||
| packaging | ||
| source_control | ||
| system | ||
| utilities | ||
| web_infrastructure |
A package may be removed but not purged with APT. The only way to identify this state is by looking at the list of installed files of a package. Even if the package has no files installed, this list will be non-empty until the package is removed: # python -c "import apt; c=apt.Cache(); c.update(); c.open(); p=c['ruby1.8']; print p, p.installed, p.installed_files" <Package: name:'ruby1.8' id:1425> None [u''] # dpkg --purge ruby1.8 (Reading database ... 27904 files and directories currently installed.) Removing ruby1.8 ... Purging configuration files for ruby1.8 ... # python -c "import apt; c=apt.Cache(); c.update(); c.open(); p=c['ruby1.8']; print p, p.installed, p.installed_files" <Package: name:'ruby1.8' id:1425> None [] See http://bugs.debian.org/712749 too. If a package is not marked installed but it still 'has_files', then it should be processed if the request is to purge it. Signed-off-by: martin f. krafft <madduck@madduck.net>
| Name |
Last commit
|
Last update |
|---|---|---|
| .. | ||
| cloud | Loading commit data... | |
| commands | Loading commit data... | |
| database | Loading commit data... | |
| files | Loading commit data... | |
| internal | Loading commit data... | |
| inventory | Loading commit data... | |
| messaging | Loading commit data... | |
| monitoring | Loading commit data... | |
| net_infrastructure | Loading commit data... | |
| network | Loading commit data... | |
| notification | Loading commit data... | |
| packaging | Loading commit data... | |
| source_control | Loading commit data... | |
| system | Loading commit data... | |
| utilities | Loading commit data... | |
| web_infrastructure | Loading commit data... |