[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#821953: debootstrap: does random crap when unpackign devices



Package: debootstrap
Version: 1.0.80
Severity: important

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

debootstrap on sid seems to do weird things when unpacking devices.tgz
on sid.

You can find the used call and everything around it at [0].

When running this script on jessie, dev/ inside the chroot contains
everything from debootstrap's devices.tgz afterwards.

When running on jessie, it contains only parts of it - the most
interesting thing is that, on sid, dev/ptmx becomes a symlink to
pts/ptmx, although it is not a symlink in devices.tgz. Everything apart
from that seems to be compeltely random - e.g., sometimes dev/null and
dev/console are missing, and sometimes not.

This looks a bit related to #601011, but in this case, debootstrap
doesn't even exit with failure, it just goes on and what's in dev/
afterwards is completely random.

[0]: https://www.teckids.org/gitweb/?p=verein.git;a=blob;f=sysadmin/scripts/mk-live-rdp;h=099986cc887c9c8dbbc056de71d31c4770d59afc;hb=HEAD

- -- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.5.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages debootstrap depends on:
ii  wget  1.17.1-1+b1

Versions of packages debootstrap recommends:
ii  debian-archive-keyring  2014.3
ii  gnupg                   1.4.20-6

debootstrap suggests no packages.

- -- no debconf information

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQJOBAEBCAA4BQJXF9qHMRpodHRwczovL3d3dy5kb21pbmlrLWdlb3JnZS5kZS9n
cGctcG9saWN5LnR4dC5hc2MACgkQt5o8FqDE8pZobQ//Xhly63g96nEyiGmoDJic
RbxWhT9/Gtbm7x1PA+ZplxPYQsOP9a1MppJfpgnnomrhEE3eEB0Pq//eyJkeiVQl
LO8vqAs/VRewJdNlJTzY4po9k8XXokBdRUfEHN/kCBvkisMKMOIeV7nBu4vBghgV
cD82Q1bOngftyJFvXVGgtsX2X/gYn34yQZo0jj8bFrwqF2aKMnXGeeeXljzRP8Yz
0/iiukI0d5E4sayJcZdp4pkxUiYT+zMmN4pdOMDhOcQkkWW3L7MFmiGl8JbdgWwj
7Dq/H1Bc0zT+IiMKh5YId82IsNdC+nMcgdBH8xLaH2hxY4UzJ4E5nNFcvE4WYwhO
q2xvMzEPZBwBE8TrwA3AzD1QfIf49igcvzUEZa3vnbPw99EZzkYd0ugAWKpxiPEQ
yd8soglGSrlvBym8eQkvVjLqI1Z4rHN+3+bx8b3zqBG4cEGKbaciTmn26C5+x+ly
StmMhMF+XnZWDp4UUAo5ZFZKB3Orsg58yZ+K5RafuXoq4mIm7gIxFqP7DwxJMY4V
HhIv+MZdL/orNbiZOE338skbbnqq6SgZINo+WovqW8/ODMgnfc2Kb5dzAxTqsIws
9weUdwgA1tqnrwnRUpLk67UbJrs8jsU36eNkOv6GtyLpkoI6+uU+6qojfUHtxJvI
Ixrq8gzGMfwEcU1YYZJcHfk=
=exaS
-----END PGP SIGNATURE-----


Reply to: