[Bug 1086548] Re: libc-bin/libc6 inverted deps causes nss to fail and can make dpkg-statoverride explode, killing the upgrade

[James Troup]

FWIW, I worked around this by manually deleting the NSS based group
from /var/lib/dpkg/statoverride.

Adam tells me the inverted libc6/libc-bin dependency has been fixed in
raring.  He's understandably queasy about doing that kind of a change
as an SRU.  Other ways this could be fixed/worked around is by having
the release upgrader check for statoverrides that use non-local users
or groups and deleting them (temporarily?).  Or perhaps
dpkg-statoverride itself should be fixed to not consider this
particular case terminal.

This is the first time I've run into such a case and I realise it's
not necessarily going to be a comon one, so if the consensus is that
this is not worth fixing, that's also OK by me.  (I've already updated
our LTS upgrade instructions with a workaround.)

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to update-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1086548

Title:
  libc-bin/libc6 inverted deps causes nss to fail and can make dpkg-
  statoverride explode, killing the upgrade

Status in “update-manager” package in Ubuntu:
  New

Bug description:
  I've just had a lucid -> precise upgrade explode in my face.  libc-bin
  was installed before libc6 and as a result, there was a period where
  nss was broken, after libc-bin had been upgraded, but before libc6
  had.  nss being broken caused dpkg-statoverride to explode on almost
  any use (because there was a override that used a group provided by
  NSS, not in /etc/group).  dpkg-statoverride failing caused the libc6
  install to fail and subsequently do-release-upgrade also.  I've
  attached the dist-upgrade logs from the failed run.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1086548/+subscriptions