Your message dated Wed, 27 Apr 2011 06:00:40 +0200
with message-id <[email protected]>
and subject line Re: Bug#147513: bug #147513 should be closed
has caused the Debian Bug report #147513,
regarding [DPKG-DEB] debconf upgrade fails with Broken Pipe
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.)
--
147513: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=147513
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: debconf
Version: 1.1.3
On apt-get dist-upgrade:
Preconfiguring packages ...
(Reading database ... 91736 files and directories currently installed.)
Preparing to replace debconf 1.0.32 (using
.../archives/debconf_1.1.3_all.deb) ...
Unpacking replacement debconf ...
dpkg: error processing /var/cache/apt/archives/debconf_1.1.3_all.deb
(--unpack): error reading from dpkg-deb pipe: Bad address
dpkg-deb: subprocess paste killed by signal (Broken pipe)
Running "dpkg --configure -a" configures everything correctly.
-Ralf.
--
--- End Message ---
--- Begin Message ---
Hi!
Initially you wrote:
> Preconfiguring packages ...
> (Reading database ... 91736 files and directories currently installed.)
> Preparing to replace debconf 1.0.32 (using
> .../archives/debconf_1.1.3_all.deb) ...
> Unpacking replacement debconf ...
> dpkg: error processing /var/cache/apt/archives/debconf_1.1.3_all.deb
> (--unpack): error reading from dpkg-deb pipe: Bad address
> dpkg-deb: subprocess paste killed by signal (Broken pipe)
Bad address is EFAULT, but most functions/syscalls should trigger a
segfault instead and not return that. So I don't think that was a problem
with dpkg.
On Thu, 2004-09-23 at 08:52:44 +0200, Ralf Treinen wrote:
> the problem that I reported in bug #147513 hasn't reproduced since
> so I suggest that you close this bug report. -Ralf.
Right, even if I'm not usually fan of closing bug reports that cannot be
tracked down, but in this case given it might seem like memory corruption
or a kernel bug, etc, it's not really reproducible, and I don't see
anything that could trigger this in dpkg itself, let's just close it.
thanks,
guillem
--- End Message ---
