Your message dated Thu, 10 Feb 2022 22:52:32 +0100
with message-id <[email protected]>
and subject line Re: Bug#898627: man-db: dependency loop
has caused the Debian Bug report #898627,
regarding man-db: dependency loop
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
898627: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898627
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: man-db
Version: 2.8.3-2
Severity: normal
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.
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'testing-debug'), (500, 'unstable'),
(500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.15.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8),
LANGUAGE=de_AT:de (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages man-db depends on:
ii bsdmainutils 11.1.2+b1
ii debconf [debconf-2.0] 1.5.66
ii dpkg 1.19.0.5+b1
ii groff-base 1.22.3-10
ii libc6 2.27-3
ii libgdbm5 1.14.1-6
ii libpipeline1 1.5.0-1
ii libseccomp2 2.3.3-1
ii zlib1g 1:1.2.11.dfsg-1
man-db recommends no packages.
Versions of packages man-db suggests:
ii apparmor 2.12-4
ii chromium [www-browser] 66.0.3359.139-1+b1
ii firefox [www-browser] 60.0-1
ii firefox-esr [www-browser] 52.7.3esr-1
pn groff <none>
ii less 487-0.1+b1
ii lynx [www-browser] 2.8.9dev18-1
ii w3m [www-browser] 0.5.3-36+b1
-- debconf information excluded
--
--- End Message ---
--- Begin Message ---
Version: 1.19.7
Hi!
On Wed, 2022-02-09 at 22:09:49 +0100, Sven Joachim wrote:
> On 2022-02-09 00:43 +0000, Colin Watson wrote:
> > Control: reassign -1 dpkg
> >
> > [For background, the dpkg output from earlier messages in this bug was:
> >
> >> # 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
> > ]
> >
> > On Mon, May 14, 2018 at 04:35:34PM +0100, Ian Jackson wrote:
> >> Colin Watson writes ("Re: Bug#898627: man-db: dependency loop"):
> >> > On Mon, May 14, 2018 at 04:03:51PM +0100, Ian Jackson wrote:
> >> > > Does the man-db or libc-bin postinst explicitly trigger
> >> > > /usr/share/man ?
> >> >
> >> > Not as far as I can see. That would have to be a dpkg-trigger(1) call,
> >> > right?
> >>
> >> Yes. (Directly or indirectly, of course.)
> >
> > I think this can only have been a dpkg bug, since to my knowledge
> > there's no such explicit triggering going on here, so I'm reassigning
> > it. Sorry to have to reassign an old bug that may be hard to reproduce
> > at this point ...
>
> Reproducing it will likely be difficult, although I suspect this could
> be the same problem as #928429, fixed in dpkg 1.19.7.
That was exactly my thought. I think I'm just closing this now, as we
have seen (AFAIK) no new gratuitous trigger cycles since then. If
there's any remaining I expect bugs will be forthcoming.
Thanks,
Guillem
--- End Message ---
