Your message dated Mon, 22 Aug 2011 11:23:10 -0500
with message-id <20110822162310.gd2...@elie.gateway.2wire.net>
and subject line Re: Bug#545701: dash.postinst abort in infinite loop
has caused the Debian Bug report #545701,
regarding dash.postinst abort in infinite loop
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 ow...@bugs.debian.org
immediately.)
--
545701: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=545701
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dash
Version: 0.5.5.1-2
Severity: important
I started an aptitude safe-upgrade and left the computer for half an
hour. Upon return I find that there's a suspicious process eating 100%
of a CPU for a long time. /proc/pid/cmdline says:
# cat cmdline
/usr/bin/perl-w/usr/share/debconf/frontend/var/lib/dpkg/info/dash.postinstabort-upgrade0.5.5.1-2.3
strace'ing the process yields this:
ioctl(0, SNDCTL_TMR_TIMEBASE or TCGETS, {B0 -opost -isig icanon -echo ...}) = 0
ioctl(0, SNDCTL_TMR_TIMEBASE or TCGETS, {B0 -opost -isig icanon -echo ...}) = 0
ioctl(0, SNDCTL_TMR_TIMEBASE or TCGETS, {B0 -opost -isig icanon -echo ...}) = 0
<repeats ad nauseam>
Killing that process and doing an "aptitude install dash" reports this:
# LC_ALL=C sudo aptitude install dash
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
Reading task descriptions... Done
The following packages will be upgraded:
dash
1 packages upgraded, 0 newly installed, 0 to remove and 473 not upgraded.
Need to get 0B/99.5kB of archives. After unpacking 0B will be used.
Do you want to continue? [Y/n/?]
Writing extended state information... Done
Reading changelogs...
Preconfiguring packages ...
(Reading database ... 213689 files and directories currently installed.)
Preparing to replace dash 0.5.5.1-2 (using .../dash_0.5.5.1-2.3_amd64.deb) ...
Adding `diversion of /usr/share/man/man1/sh.1.gz to
/usr/share/man/man1/sh.distrib.1.gz by dash'
Unpacking replacement dash ...
dpkg: error processing /var/cache/apt/archives/dash_0.5.5.1-2.3_amd64.deb
(--unpack):
trying to overwrite `/bin/sh', which is also in package bash
Removing `diversion of /usr/share/man/man1/sh.1.gz to
/usr/share/man/man1/sh.distrib.1.gz by dash'
Processing triggers for man-db ...
Processing triggers for menu ...
Errors were encountered while processing:
/var/cache/apt/archives/dash_0.5.5.1-2.3_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
Reading task descriptions... Done
And this is the status of bash and dash in my system:
LC_ALL=C apt-cache policy bash dash
bash:
Installed: 4.0-4
Candidate: 4.0-4
Version table:
*** 4.0-4 0
990 http://ftp.debian.org testing/main Packages
100 /var/lib/dpkg/status
dash:
Installed: 0.5.5.1-2
Candidate: 0.5.5.1-2.3
Version table:
0.5.5.1-2.3 0
990 http://ftp.debian.org testing/main Packages
*** 0.5.5.1-2 0
100 /var/lib/dpkg/status
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (990, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.30-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=es_CL.UTF-8, LC_CTYPE=es_CL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages dash depends on:
ii libc6 2.9-25 GNU C Library: Shared libraries
dash recommends no packages.
dash suggests no packages.
-- debconf information:
dash/sh: false
--- End Message ---
--- Begin Message ---
Jonathan Nieder wrote:
> Alvaro Herrera wrote:
>> Yeah ... I guess this can safely be closed.
>
> Thanks for the clarifications. Closing since it's hard to see how to
> move this forward, but I will remember it next time something similar
> happens.
Actually closing this time.
--- End Message ---
