Package: dpkg
Version: 1.16.10

Hi,

I came accross the issue in a chroot, but it probably also maps to
non-chroot setups, though perhaps less likely.

| (sid_amd64-dchroot)root@barriere:~# grep postqueue /var/lib/dpkg/statoverride
| root postdrop 2555 /usr/sbin/postqueue
| (sid_amd64-dchroot)root@barriere:~# dpkg-statoverride --remove 
/usr/sbin/postqueue
| dpkg-statoverride: unrecoverable fatal error, aborting:
|  syntax error: unknown group 'postdrop' in statoverride file
| (sid_amd64-dchroot)root@barriere:~# grep postqueue /var/lib/dpkg/statoverride
| root postdrop 2555 /usr/sbin/postqueue

The problem is that when a group no longer exists, dpkg-statoverride in
incapable of removing the entry.

Furthermore, dpkg is incapable of doing anything at all from now on:
| # apt-get install vim
| Reading package lists... Done
| Building dependency tree
| Reading state information... Done
| Suggested packages:
|   ctags vim-doc vim-scripts
| The following NEW packages will be installed:
|   vim
| 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
| Need to get 841 kB of archives.
| After this operation, 1922 kB of additional disk space will be used.
| Get:1 http://ftp.us.debian.org/debian/ sid/main vim amd64 2:7.3.547-7 [841 kB]
| Fetched 841 kB in 1s (630 kB/s)
| dpkg: unrecoverable fatal error, aborting:
|  syntax error: unknown group 'postdrop' in statoverride file
| E: Sub-process /usr/bin/dpkg returned an error code (2)


This problem showed up for me, because postfix was installed and then - for
external reasons - the group database was restored to a pre-install version.

Worse, it's not really possible to cleanly recover from this without manually
editing dpkg's private files in /var/lib:
 - purging postfix would do the dpkg-statoverride --remove, but that doesn't 
help.
 - manually doing dpkg-statoverride --remove is likewise not successful (see 
above).

Maybe the statoverride parser should be more forgiving?

weasel


-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to