Bug#923674: systemd: FTBFS (failing tests)

Santiago Vila sanvila at unex.es
Sat Mar 9 21:27:01 GMT 2019


On Sat, Mar 09, 2019 at 09:59:16PM +0100, Michael Biebl wrote:
> Am 09.03.19 um 21:50 schrieb Michael Biebl:
> > Am 09.03.19 um 21:00 schrieb Santiago Vila:
> >> to which I also add these two lines:
> > ..> /dev/urandom    /dev/random     none    rw,bind         0       0
> > 
> > This might very well be the culprit, given that test-stat-util does the
> > following check:
> > 
> >         test_device_path_make_canonical_one("/dev/random");
> >         test_device_path_make_canonical_one("/dev/urandom");
> > 
> > https://github.com/systemd/systemd/blob/master/src/test/test-stat-util.c#L148

Good catch!

> Why are you bind mounting /dev/urandom to /dev/random (note the missing
> 'u')?

It is a workaround for the fact that some packages FTBFS because of
lack of entropy (mostly unit tests for cryptography-related packages).

Why are you testing /dev/random and /dev/urandom at all?

They are supposed to be sane in an autobuilder, no need to check them
while building any package.

I'm going to check without the bind mount and probably retitle and
downgrade the bug.

Thanks.



More information about the Pkg-systemd-maintainers mailing list