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 #64669,
regarding dpkg: main/filesdb.c:684: findnamenode_high: Assertion 
(*pointerp)->name[0] == '/'' 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.)


-- 
64669: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=64669
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dpkg
Version: 1.7.2
Severity: normal

Here's the error text and a listing of /var/cache/apt/archives:

(Reading database ... dpkg: 
/home/wichert/sources/cvs/debian/x/dpkg-1.7.2/main/filesdb.c:821: 
findnamenode_high: Assertion `(*pointerp)->name[0] == '/'' failed.
E: Sub-process /usr/bin/dpkg exited unexpectedly
Some errors occurred while unpacking. I'm going to configure the
packages that were installed. This may result in duplicate errors
or errors caused by missing dependencies. This is OK, only the errors
above this message are important. Please fix them and run [I]nstall again
Press enter to continue.

525 : /root\ > ls /var/cache/apt/archives
apel_10.2+20001228cvs-1_all.deb    libtext-querysql-perl_0.07-2_all.deb
gcd_2.95-3_i386.deb                lock
grafix-dev_1.6-2_i386.deb          partial/
grafix1_1.6-2_i386.deb             perl-5.6-base_5.6.0-6.1_i386.deb
grip_2.95-3_i386.deb               perl-5.6-debug_5.6.0-6.1_i386.deb
guile1.4-slib_1%3a1.4-6_i386.deb   perl-5.6-doc_5.6.0-6.1_all.deb
guile1.4_1%3a1.4-6_i386.deb        perl-5.6-suid_5.6.0-6.1_i386.deb
ifupdown_0.6.4-2_i386.deb          perl-5.6-thread_5.6.0-6.1_i386.deb
libcdb-file-perl_0.83-1_i386.deb   perl-5.6_5.6.0-6.1_i386.deb
libfreetype6_2.0.1-1_i386.deb      quanta_2.0-beta4-1_i386.deb
libgd-perl_1.30-5_i386.deb         save/
libguile9-dev_1%3a1.4-6_i386.deb   vim-gtk_5.7.019-2_i386.deb
libguile9_1%3a1.4-6_i386.deb       vim-rt_5.7.019-2_all.deb
libperl5.6_5.6.0-6.1_i386.deb      wordplay_7.22-14_i386.deb
libtext-query-perl_0.07-2_all.deb

And sadly it didn't reoccur the next time.  Maybe a local problem.  I'll
report it anyway.

Jim


-- System Information
Debian Release: woody
Architecture: i386
Kernel: Linux eeyore 2.4.0-test12pre4-reiserfs-cuecat-ipsec #1 Wed Nov 29 
12:53:25 EST 2000 i686

Versions of packages dpkg depends on:
ii  libc6                        2.2-6       GNU C Library: Shared libraries an
ii  libncurses5                  5.0-8       Shared libraries for terminal hand
ii  libstdc++2.10-glibc2.2       1: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 ---

Reply via email to