Your message dated Thu, 8 Sep 2016 10:39:01 +0000
with message-id <[email protected]>
and subject line Re: Bug#837048: QEMU chroot broken
has caused the Debian Bug report #837048,
regarding QEMU chroot broken
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.)
--
837048: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837048
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: qemu
Version: 1:2.6+dfsg-3
Severity: Important
I'm fairly certain nearly all of Debian's chroots are broken. I think
the X32 chroot is the only one that actually works.
The broken QEMU chroots coupled with lack of documentation really
hinders our ability to do our job. Here, our job is to ensure our
project works under Debian so Debian users do not experience troubles.
Its mostly become a waste of our time to try to use them or submit
bugs for them since nothing seems to get fixed.
Perhaps Debian should try to automate some testing against its QEMU
chroots so it discovers its breaks.
$ cat debian-armel-chroot.txt
# qemu-debootstrap --arch=armel --keyring
/usr/share/keyrings/debian-archive-keyring.gpg \
> --variant=buildd --exclude=debfoster unstable debian-armel
> http://ftp.debian.org/debian
I: Running command: debootstrap --arch armel --foreign --keyring
/usr/share/keyrings/debian-archive-keyring.gpg --variant=buildd
--exclude=debfoster unstable debian-armel http://ftp.debian.org/debian
I: Retrieving Release
I: Retrieving Release.gpg
I: Checking Release signature
I: Valid Release signature (key id 126C0D24BD8A2942CC7DF8AC7638D0442B90D010)
I: Retrieving Packages
...
I: Extracting mount...
I: Extracting util-linux...
I: Extracting liblzma5...
I: Extracting zlib1g...
I: Running command: chroot debian-armel /debootstrap/debootstrap --second-stage
I: Keyring file not available at
/usr/share/keyrings/debian-archive-keyring.gpg; switching to https
mirror https://mirrors.kernel.org/debian
I: Installing core packages...
I: Unpacking required packages...
I: Unpacking libacl1:armel...
I: Unpacking libattr1:armel...
I: Unpacking libaudit-common...
I: Unpacking libaudit1:armel...
...
I: Configuring g++...
I: Configuring build-essential...
I: Configuring libc-bin...
I: Base system installed successfully.
debian-8-x64-vm:~# chmod debian-armel
chmod: missing operand after ‘debian-armel’
Try 'chmod --help' for more information.
debian-8-x64-vm:~# SHELL=sh chmod debian-armel
chmod: missing operand after ‘debian-armel’
Try 'chmod --help' for more information.
**********
$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux unstable (sid)
Release: unstable
Codename: sid
$ uname -a
Linux debian-8-x64-vm 4.7.0-1-amd64 #1 SMP Debian 4.7.2-1 (2016-08-28)
x86_64 GNU/Linux
--- End Message ---
--- Begin Message ---
On Thu, Sep 08, 2016 at 05:19:44AM -0400, Jeffrey Walton wrote:
> I'm fairly certain nearly all of Debian's chroots are broken. I think
> the X32 chroot is the only one that actually works.
...
> debian-8-x64-vm:~# chmod debian-armel
> chmod: missing operand after ‘debian-armel’
> Try 'chmod --help' for more information.
>
> debian-8-x64-vm:~# SHELL=sh chmod debian-armel
> chmod: missing operand after ‘debian-armel’
> Try 'chmod --help' for more information.
Try using "chroot" instead of chmod if you intend
to chroot.
--- End Message ---
