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
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
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
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
4 matches
Mail list logo
