On Mon, May 14, 2018 at 02:14:56PM +0200, Philipp Marek wrote: > Due to a bad $TERM I got my "apt-get upgrade" break down, "too many errors" > in man-db. > > When trying to fix that, I got (error messages manually translated - > fixed the problem first): > > # apt-get -f install > dpkg: Cycle in triggers found: > Chain of packages, which triggers might be the culprit: > man-db -> man-db > required triggers of packages that can't be resolved: > man-db: /usr/share/man > libc-bin: ldconfig > dpkg: Error while configureing package man-db (--configure): > Triggers build a loop, aborted > > > A manual "dpkg -i --force-all /var/cache/apt/archives/man-db-*" did fix the > basic problem, of course, so that the "apt-get -f install" was able to > recover.
I've never seen this myself. I guess it's due to man-db having "interest-noawait /usr/share/man" in its triggers and itself shipping files in /usr/share/man; but shouldn't dpkg notice that this is trivially resolved by configuring man-db and not consider it as a cycle? In any case I don't see any way to exclude man-db itself from the file trigger if that's not the case. CCing the dpkg maintainers. -- Colin Watson [cjwat...@debian.org]