Re: Safe-upgrade of "dash" fails
On 2009-08-06 17:29 +0200, Eric Gerlach wrote:
> On Thu, Aug 06, 2009 at 09:05:56AM +0200, Jack Knowlton wrote:
>> On Thu, August 6, 2009 8:02 am, Sven Joachim wrote:
>> > On 2009-08-06 00:11 +0200, Jack Knowlton wrote:
>> >
>> >> Coming back from a month-long trip, I decided to safe-upgrade my debian
>> >> unstable desktop. Among the hundreds of new packages, apt seemed eager
>> >> to
>> >> install (or upgrade, I'm not sure) dash.
>> >
>> > This is intended.
>> >
>> >> Unfortunately, something seems to have gone terribly wrong and I would
>> >> like to complete successfully the upgrade before rebooting the box.
>> >> Here's
>> >> what aptitude is complaining about:
>> >>
>> >> Unpacking dash (from .../dash_0.5.5.1-2.3_amd64.deb) ...
>> >> Adding `diversion of /bin/sh to /bin/sh.distrib by dash'
>> >> Adding `diversion of /usr/share/man/man1/sh.1.gz to
>> >> /usr/share/man/man1/sh.distrib.1.gz by dash'
>> >> dpkg (subprocess): unable to exec dpkg-deb to get filesystem archive: No
>> >> such file or directory
>> >
>> > That sounds as if you had lost dpkg-deb, which would be very worrisome.
Looking closer into it, this will also happen if you lose /bin/sh
because dpkg invokes dpkg-deb using execlp(3), and by studying the
eglibc code I found out that this function relies on /bin/sh to find the
program to execute in $PATH.
>> Fortunately, after a little digging, I found out aptitude symlinked
>> /bin/sh -> dash before actually installing it. Now everything's cool again
>> :D
>>
>> -JK
>
> That *could* be a bug. It may be worth looking to see if anyone else has seen
> it, and filing it if no-one has.
There is already a bug report for this: http://bugs.debian.org/538822.
Sven
Reply to: