Hello everybody,

just in case it is more that just a private chroot broken, I would like to report the following:

I just updated my sid schroot, and got this:

Unpacking replacement libc-bin ...
Setting up libc-bin (2.13-3) ...
(Reading database ... 10764 files and directories currently installed.)
Preparing to replace libc6 2.13-2 (using .../libc6_2.13-3_amd64.deb) ...
Unpacking replacement libc6 ...
dpkg (subprocess): unable to execute rm command for cleanup (rm): No such file or directory
dpkg: error while cleaning up:
subprocess rm cleanup returned error exit status 2
Could not exec dpkg!
E: Sub-process /usr/bin/dpkg returned an error code (100)
E: Failed to execute "/bin/rm": No such file or directory
E: apt-get dist-upgrade failed

The schroot is now broken. I have not tested to upgrade on my system to see if
it would do the same

Cheers,

--
Charles Plessy
Tsurumi, Kanagawa, Japan


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110512062148.GF9678@merveille.plessy.net">http://lists.debian.org/20110512062148.GF9678@merveille.plessy.net

On Thu, May 12, 2011 at 11:51 AM, Charles Plessy <plessy@debian.org> wrote:
> just in case it is more that just a private chroot broken, I would like to report the following:
> I just updated my sid schroot, and got this:
...
> E: Sub-process /usr/bin/dpkg returned an error code (100)
> E: Failed to execute "/bin/rm": No such file or directory
> E: apt-get dist-upgrade failed
>
> The schroot is now broken. I have not tested to upgrade on my system to see if
> it would do the same

Confirmed. It breaks for me too (in my case, nicely working laptop )
This bug was mention and workaround was there, but I couldn't apply
solution as everything started breaking including shell..

--
Kartik Mistry
Debian GNU/Linux Developer
IRC: kart_ | Identica: @kartikm


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: BANLkTim-S4KTwKi+O+2c7DKZOBFgPkUd0w@mail.gmail.com">http://lists.debian.org/BANLkTim-S4KTwKi+O+2c7DKZOBFgPkUd0w@mail.gmail.com

2011/5/12 Charles Plessy <plessy@debian.org>:
> dpkg (subprocess): unable to execute rm command for cleanup (rm): No such file or directory
> dpkg: error while cleaning up:
> *subprocess rm cleanup returned error exit status 2
> Could not exec dpkg!
> E: Sub-process /usr/bin/dpkg returned an error code (100)
> E: Failed to execute "/bin/rm": No such file or directory
> E: apt-get dist-upgrade failed

This would explain why my desktop system (with unstable up-to-date via
unattended-upgrades) was broken this morning and I couldn't execute
any application. The error message was the same ("APPNAME: No such
file or directory).

After reboot I get a kernel panic, the last lines are:
Begin: Running /scripts/init-bottom ..done.
run-init: /sbin/init: No such file or directory
[ 3.85xxxx] Kernel panic - not syncing: Attempted to kill init!
[ 3.85xxxx] Pid: 1, comm: run-init Not tained 2.6.38-2-amd64 #1
[ 3.85xxxx] Call trace:
[ 3.85xxxx] [ff...] ? panic+0x92/0x1a1
[ 3.85xxxx] [ff...] ? sched_move_task+0xa7/0xb2
[ 3.85xxxx] [ff...] ? do_exit+0x73/0x736
[ 3.85xxxx] [ff...] ? vfs_write+0xc9/0xff
[ 3.85xxxx] [ff...] ? complete_and_exit+0x0/0x16
[ 3.85xxxx] [ff...] ? system_call_fastpath+0x16/0x1b

Thanks


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: BANLkTinYcX=rXog80fpb+qndWG6KdqtN6Q@mail.gmail.com ">http://lists.debian.org/BANLkTinYcX=rXog80fpb+qndWG6KdqtN6Q@mail.gmail.com

Teodor MICU <mteodor@gmail.com> writes:

> This would explain why my desktop system (with unstable up-to-date via
> unattended-upgrades) was broken this morning and I couldn't execute any
> application. The error message was the same ("APPNAME: No such file or
> directory).

Looks like this was fixed already in a 2.13-4 upload. (The symptoms
indicate that the dynamic linker went missing, which appears to have been
because of a missing /lib64 symlink.)

--
Russ Allbery (rra@debian.org) <http://www.eyrie.org/~eagle/>


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 87ei44pf10.fsf@windlord.stanford.edu">http://lists.debian.org/87ei44pf10.fsf@windlord.stanford.edu

On Thu, 12 May 2011 15:21:48 +0900
Charles Plessy wrote:


> Could not exec dpkg!
> E: Sub-process /usr/bin/dpkg returned an error code (100)
> E: Failed to execute "/bin/rm": No such file or directory
> E: apt-get dist-upgrade failed
>
> The schroot is now broken. I have not tested to upgrade on my system
> to see if it would do the same

On my system:

#ls /lib64
ls: can not access / lib6: No such file or directory

#cd /
# ln -s /lib lib64
# reboot

# apt-get -f install

sy,
peter


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110512111816.195a20de@blackp.vopmes">http://lists.debian.org/20110512111816.195a20de@blackp.vopmes

On 05/12/2011 08:21 AM, Charles Plessy wrote:
> Hello everybody,
>
> just in case it is more that just a private chroot broken, I would like to report the following:
>
> I just updated my sid schroot, and got this:
[...]
> The schroot is now broken. I have not tested to upgrade on my system to see if
> it would do the same

Hello.

You've just encountered:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=626450

I've fixed it this way:
# /lib/ld-linux-x86-64.so.2 /bin/ln -s /lib /lib64
# /lib/ld-linux-x86-64.so.2 /usr/bin/dpkg --configure -a

And yes - it do the same on unchrooted system too.

Kind regards,

--
Lech Karol Pawłaszek <ike>
"You will never see me fall from grace" [KoRn]


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 4DCBA9D4.7040309@szluug.org">http://lists.debian.org/4DCBA9D4.7040309@szluug.org

On Thu, May 12, 2011 at 11:35:16AM +0200, Lech Karol Pawłaszek wrote:
> You've just encountered:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=626450
>
> I've fixed it this way:
> # /lib/ld-linux-x86-64.so.2 /bin/ln -s /lib /lib64
> # /lib/ld-linux-x86-64.so.2 /usr/bin/dpkg --configure -a
Note that you need an existing root shell to do that.

--
WBR, wRAR