Bug#598080: debootstrap: Empty devices.tar.gz

2010-09-26 Thread intrigeri 
Package: debootstrap
Version: 1.0.24
Severity: important

Hi,

now that makedev has priority extra instead of required,
the existence of basic devices nodes in a debootstrapped chroot (such
as /dev/random) purely relies on what is in the devices.tar.gz
provided by the debootstrap binary package.

1.0.23 had a bunch of devices in there.
However, 1.0.24's devices.tar.gz only contains an empty dev/ directory.
This breaks e.g. builds of Live images using Debian Live.

I haven't investigated this issue enough to tell the cause of the
problem. A somewhat unclean build environment might be involved, since
rebuilding from the source package in my sid chroot (using pbuilder
and cowbuilder) produces a binary package that has a devices tarball
full of usefull. Same when building from SVN.

(Temporary workarounds: downgrade to 1.0.23 or use cdebootstrap.)

Bye,

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (900, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages debootstrap depends on:
ii  wget  1.12-2.1   retrieves files from the web

Versions of packages debootstrap recommends:
ii  gnupg 1.4.10-4   GNU privacy guard - a free PGP rep

debootstrap suggests no packages.

-- no debconf information

--
  intrigeri intrig...@boum.org
  | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc
  | OTR fingerprint @ 
https://gaffer.ptitcanardnoir.org/intrigeri/otr-fingerprint.asc
  | Then we'll come from the shadows.



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#598080: debootstrap: Empty devices.tar.gz

2010-09-26 Thread Joey Hess 
intrig...@boum.org wrote:
 I haven't investigated this issue enough to tell the cause of the
 problem. A somewhat unclean build environment might be involved

I can't see how, nor can I reproduce it in that same build environment.

All I can think is that MAKEDEV somehow didn't create devices, or
fakeroot ate them, but I can't see how.

-- 
see shy jo


signature.asc
Description: Digital signature

Bug#598080: debootstrap: Empty devices.tar.gz

2010-09-26 Thread Sven Joachim 
On 2010-09-26 18:33 +0200, Joey Hess wrote:

 intrig...@boum.org wrote:
 I haven't investigated this issue enough to tell the cause of the
 problem. A somewhat unclean build environment might be involved

 I can't see how, nor can I reproduce it in that same build environment.

 All I can think is that MAKEDEV somehow didn't create devices, or
 fakeroot ate them, but I can't see how.

The top-level Makefile sets MAKEDEV to /dev/MAKEDEV if that exists, and
if udev is installed /dev/MAKEDEV is a symlink to /bin/true.

Sven



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#598080: debootstrap: Empty devices.tar.gz

2010-09-26 Thread Joey Hess 
Sven Joachim wrote:
 On 2010-09-26 18:33 +0200, Joey Hess wrote:
 
  intrig...@boum.org wrote:
  I haven't investigated this issue enough to tell the cause of the
  problem. A somewhat unclean build environment might be involved
 
  I can't see how, nor can I reproduce it in that same build environment.
 
  All I can think is that MAKEDEV somehow didn't create devices, or
  fakeroot ate them, but I can't see how.
 
 The top-level Makefile sets MAKEDEV to /dev/MAKEDEV if that exists, and
 if udev is installed /dev/MAKEDEV is a symlink to /bin/true.

Ok, so if a system is *booted* without makedev installed, udev makes
MAKEDEV be /bin/true. Then, installing makedev doesn't fix the symlink,
until next boot; then it will point to /sbin/MAKEDEV. 

What a nasty gotcha. Clearly debootstrap needs to use /sbin/MAKEDEV.

-- 
see shy jo


signature.asc
Description: Digital signature