Bug#736585: dpkg: trigger problem

[Andreas Beckmann]

Package: dpkg
Version: 1.17.6
Severity: important

Hi,

during a piuparts test I noticed the following problem:


apt-get remove <lots of packages including shared-mime-info>
[...]
dpkg: libglib2.0-0:i386: dependency problems, but removing anyway as you requested:
libxklavier16 depends on libglib2.0-0 (>= 2.24.0).
libzeitgeist-1.0-1 depends on libglib2.0-0 (>= 2.26.0).
libharfbuzz0b:i386 depends on libglib2.0-0 (>= 2.30.0); however:
Package libglib2.0-0:i386 is to be removed.
python-gobject-2 depends on libglib2.0-0 (>= 2.26.0); however:
Package libglib2.0-0:i386 is to be removed.
nbd-server depends on libglib2.0-0 (>= 2.26.0).
modemmanager depends on libglib2.0-0 (>= 2.31.8); however:
Package libglib2.0-0:i386 is to be removed.
libgudev-1.0-0:i386 depends on libglib2.0-0 (>= 2.22.0).
python-dbus depends on libglib2.0-0 (>= 2.12.0); however:
Package libglib2.0-0:i386 is to be removed.
python3-dbus depends on libglib2.0-0 (>= 2.12.0); however:
Package libglib2.0-0:i386 is to be removed.
shared-mime-info depends on libglib2.0-0 (>= 2.24.0).

Removing libglib2.0-0:i386 (2.36.4-1) ...
[...]
Processing triggers for mime-support (3.54) ...
Processing triggers for tex-common (4.04) ...
Processing triggers for shared-mime-info (1.0-1+b1) ...
update-mime-database.real: error while loading shared libraries: libglib-2.0.so.0: cannot open shared object file: No such file or directory
dpkg: error processing package shared-mime-info (--remove):
subprocess installed post-installation script returned error exit status 127
Processing triggers for libc-bin (2.17-97) ...
Errors were encountered while processing:
shared-mime-info
E: Sub-process /usr/bin/dpkg returned an error code (1)
[...]

There is probably a better ordering of the removals to not produce that
many "dependency problems". Anyway, shared-mime-info should be in a
"broken" state and triggers should not be run in this state.

Another thing that does not seem correct:
dpkg: error processing package shared-mime-info (--remove):
^^^^^^^^
The problem happened during trigger processing of s-m-i, not its
removal. (Btw, I like the improved verbosity in 1.17.x).

Full piuparts log is attached (it's huge), there are a lot of other
(unreleated) errors as well, you should just ignore them.

Andreas

[Guillem Jover]

Hi!

Post by Andreas Beckmann
Package: dpkg
Version: 1.17.6
Severity: important

[…]

Post by Andreas Beckmann
There is probably a better ordering of the removals to not produce that
many "dependency problems".

(Yeah, see the bug reports on apt and cupt about selections usage,
I've to follow up on the cupt one though this weekend.)

Post by Andreas Beckmann
Anyway, shared-mime-info should be in a
"broken" state and triggers should not be run in this state.

Without having checked any detail over this, my first guess would be
that this is probably #671711. But I'd have to take an actual look to
say for sure.

Post by Andreas Beckmann
^^^^^^^^
The problem happened during trigger processing of s-m-i, not its
removal.

Well, again w/o having looked at any detail, my guess would be that
this is just a consequence of the triggers failing while the dpkg
action invoked by apt was --remove.

Post by Andreas Beckmann
(Btw, I like the improved verbosity in 1.17.x).

(Thanks, precisely the intention was to help with cases like this! :)

Thanks,
Guillem