Your message dated Tue, 29 Jan 2019 12:19:06 +0100
with message-id <[email protected]>
and subject line Closing assert() related bugs
has caused the Debian Bug report #76687,
regarding [ASSERT] lib/dump.c:180: w_dependency: Assertion `yp->up == pigp'
failed.
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.)
--
76687: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=76687
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dpkg
Version: 1.7.2-1
I'm using the dpkg from woody, and I've just done an apt-get update; apt-get
dist-upgrade, and dpkg is doing some _VERY_ weird shit. I first got a bug
installing glibc that I unfortunately can't report as I had it in my gpm
buffer, but I forgot about it and rebooted, and when I just re-ran apt-get
dist-upgrade, it worked, it was something about an internal error, was
really weird. IIRC it was from dump.c, line 160.
Here's one I _CAN_ log:
Preparing to replace calife 2.8.4-2 (using .../calife_2.8.4b-1_i386.deb) ...
Unpacking replacement calife ...
dpkg: /home/wichert/sources/cvs/debian/x/dpkg-1.7.2/lib/dump.c:180:
w_dependency: Assertion `yp->up == pigp' failed.
E: Sub-process /usr/bin/dpkg exited unexpectedly
This happens every time.
--- End Message ---
--- Begin Message ---
Hi!
So, I'm not a big fan of closing bugs where it's unknown whether they
have been fixed or not. The problem with this set of reports, is that
they are pretty much unactionable. :/
What I've done in dpkg 1.19.1, has been to change all assert()s from the
dpkg codebase into internerr() calls, which means we should be getting
slightly better diagnostics from now on, if any of this ever happen
again.
So by closing these, I'm hoping to close things that have arleady been
fixed, even if accidentally, *and* to prompt any new occurrence to be
filed again as a new report with the additional information.
Thanks,
Guillem
--- End Message ---
