Re: Bug#768599: man-db: cycle found while processing triggers:

[Guillem Jover <guillem@debian.org>]

Hi!

On Sat, 2014-11-08 at 16:56:33 +0000, Colin Watson wrote:
> Control: reassign -1 dpkg 1.17.21
> 
> On Sat, Nov 08, 2014 at 04:05:17PM +0000, Holger Levsen wrote:
> > package: man-db
> > severity: serious
> > x-debbugs-cc: debian-dpkg@lists.debian.org

> > I'm not 100% sure the following issue is caused by man-db, please reassign 
> > appropriatly if it is not.
> > 
> > https://jenkins.debian.net/job/chroot-installation_wheezy_install_education-
> > networked_upgrade_to_jessie/2/console
> > 
> > Setting up startpar (0.59-3) ...
> > Installing new version of config file /etc/init/startpar-bridge.conf ...
> > dpkg: cycle found while processing triggers:
> >  chain of packages whose triggers are or may be responsible:
> >   man-db -> man-db
> >  packages' pending triggers which are or may be unresolvable:
> >   man-db: /usr/share/man
> > dpkg: error processing package man-db (--configure):
> >  triggers looping, abandoned
> > Setting up sysvinit-utils (2.88dsf-57) ...
> > Errors were encountered while processing:
> >  man-db
> > E: Sub-process /usr/bin/dpkg returned an error code (1)
> 
> This has got to be a dpkg bug.  There's no good reason for a package not
> to be able to trigger itself, and this has worked for ages.

That's because (according to the log), the man-db package being
triggered (version 2.6.2-1) is the one still using the awaiting
interest directive, which got switched to interest-noawait in 2.6.3-6.

I'll have to add Breaks for any such packages. :/ But I'm not sure how
much that might make the upgrade more difficult, as dpkg contains
already many Breaks/Conflicts.

Thanks,
Guillem