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] dpkg: Assertion `dyp->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
Severity: normal
I have got this error message, I thought this would be interesting:
root@ondrej ~# apt-get install efax
Reading Package Lists... Done
Building Dependency Tree... Done
The following NEW packages will be installed:
efax
0 packages upgraded, 1 newly installed, 0 to remove and 49 not upgraded.
Need to get 99.6kB of archives. After unpacking 232kB will be used.
Get:1 http://http.us.debian.org unstable/main efax 1:0.9a-3 [99.6kB]
Fetched 99.6kB in 9s (10.6kB/s)
(Reading database ... 61594 files and directories currently installed.)
Unpacking efax (from .../efax_1%3a0.9a-3_i386.deb) ...
dpkg: /home/wichert/sources/cvs/debian/x/dpkg-1.7.2/lib/dump.c:180:
w_dependency: Assertion `dyp->up == pigp' failed.
E: Sub-process /usr/bin/dpkg exited unexpectedly
-- System Information
Debian Release: woody
Kernel Version: Linux ondrej 2.2.18pre24ext3 #1 SMP Mon Dec 4 18:04:55 CET 2000
i586 unknown
Versions of the packages dpkg depends on:
ii libc6 2.2-5 GNU C Library: Shared libraries and Timezone
ii libncurses5 5.0-8 Shared libraries for terminal handling
ii libstdc++2.10- 2.95.2-20 The GNU stdc++ library
--- 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 ---
