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 #52087, regarding dpkg: main/processarc.c:814: process_archive: Assertion `otherpkg->clientdata->istobe == itb_normal || otherpkg->clientdata->istobe == itb_deconfigure' 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.) -- 52087: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=52087 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: dpkg Version: 1.6.7 I just got a potato CD and while installing from within dselect, dpkg crashes: dpkg: considering removing mysql-base in favour of libmysqlclient6 ... mysql-base is not properly installed - ignoring any dependencies on it. dpkg: yes, will remove mysql-base in favour of libmysqlclient6. Preparing to replace libmysqlclient6 3.22.27a-3 (using .../libmysqlclient6_3.22.27a-3.deb) ... Unpacking replacement libmysqlclient6 ... dpkg: /home/wichert/sources/dpkg-1.6.7/main/processarc.c:814: process_archive: Assertion herpkg->clientdata->istobe == itb_normal || otherpkg->clientdata->istobe == itb_deconfigure' failed. /usr/lib/dpkg/methods/disk/install: line 116: 547 Aborted dpkg -iGROEB "$p_mountpoint$this_binary" I am using kernel 2.2.13, libc-2.1.2, although I guess that this is not the problem. Hope that this can be overcome somehow... Greetings, Alex -- ... Alexander Klink ... Help Wanted: Telepath. You know where to apply. ... [email protected] ...
--- 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 ---
