Your message dated Wed, 20 Mar 2019 10:31:26 +0100
with message-id <a9dd0da8-b7b5-ad3c-a17c-2875616fb...@debian.org>
and subject line Re: Bug#923674: systemd: test-stat-util fails with SIGABRT
when /dev/random is bind-mounted from /dev/urandom
has caused the Debian Bug report #923674,
regarding systemd: test-stat-util fails with SIGABRT when /dev/random is
bind-mounted from /dev/urandom
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 ow...@bugs.debian.org
immediately.)
--
923674: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923674
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:systemd
Version: 240-2
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in sid but it failed:
--------------------------------------------------------------------------------
[...]
debian/rules binary-arch
dh binary-arch --without autoreconf,systemd --buildsystem=meson
dh_update_autotools_config -a -O--buildsystem=meson
debian/rules override_dh_auto_configure
make[1]: Entering directory '/<<PKGBUILDDIR>>'
dh_auto_configure --builddirectory=build-deb \
-- -Db_lto=true -Db_pie=true -Drootlibdir=/lib/x86_64-linux-gnu
-Dsplit-usr=true -Dquotaon-path=/sbin/quotaon
-Dquotacheck-path=/sbin/quotacheck -Dkmod-path=/bin/kmod
-Dkexec-path=/sbin/kexec -Dsulogin-path=/sbin/sulogin -Dmount-path=/bin/mount
-Dumount-path=/bin/umount -Dloadkeys-path=/bin/loadkeys
-Dsetfont-path=/bin/setfont -Dtelinit-path=/lib/sysvinit/telinit
-Dsysvinit-path=/etc/init.d -Dsysvrcnd-path=/etc -Ddebug-shell=/bin/bash
-Dzshcompletiondir=/usr/share/zsh/vendor-completions
-Ddbuspolicydir=/usr/share/dbus-1/system.d/
-Dsupport-url=https://www.debian.org/support
-Ddefault-kill-user-processes=false -Dpamconfdir=no -Drpmmacrosdir=no
-Dqrencode=false -Dvconsole=false -Dfirstboot=false -Dxkbcommon=false
-Dportabled=false -Dwheel-group=false -Dntp-servers="0.debian.pool.ntp.org
1.debian.pool.ntp.org 2.debian.pool.ntp.org 3.debian.pool.ntp.org"
-Dlink-udev-shared=false -Dsystem-uid-max=999 -Dsystem-gid-max=999
-Dnobody-user=nobody -Dnobody-group=nogroup -Dbump-proc-sys-fs-nr-o
pen=false -Ddev-kvm-mode=0660 -Dselinux=true -Dhwdb=true -Dsysusers=true
-Dinstall-tests=true -Defi=true -Dnss-myhostname=true -Dnss-mymachines=true
-Dnss-resolve=true -Dnss-systemd=true -Dresolve=true
-Dlink-systemctl-shared=false -Daudit=true -Dlibcryptsetup=true -Dcoredump=true
-Delfutils=true -Dapparmor=true -Dlibidn=true -Dlibiptc=true -Dlibcurl=true
-Dimportd=true -Dmicrohttpd=true -Dgnutls=true
cd build-deb && LC_ALL=C.UTF-8 meson .. --wrap-mode=nodownload
--buildtype=plain --prefix=/usr --sysconfdir=/etc --localstatedir=/var
--libdir=lib/x86_64-linux-gnu --libexecdir=lib/x86_64-linux-gnu -Db_lto=true
-Db_pie=true -Drootlibdir=/lib/x86_64-linux-gnu -Dsplit-usr=true
-Dquotaon-path=/sbin/quotaon -Dquotacheck-path=/sbin/quotacheck
-Dkmod-path=/bin/kmod -Dkexec-path=/sbin/kexec -Dsulogin-path=/sbin/sulogin
-Dmount-path=/bin/mount -Dumount-path=/bin/umount -Dloadkeys-path=/bin/loadkeys
-Dsetfont-path=/bin/setfont -Dtelinit-path=/lib/sysvinit/telinit
-Dsysvinit-path=/etc/init.d -Dsysvrcnd-path=/etc -Ddebug-shell=/bin/bash
-Dzshcompletiondir=/usr/share/zsh/vendor-completions
-Ddbuspolicydir=/usr/share/dbus-1/system.d/
-Dsupport-url=https://www.debian.org/support
-Ddefault-kill-user-processes=false -Dpamconfdir=no -Drpmmacrosdir=no
-Dqrencode=false -Dvconsole=false -Dfirstboot=false -Dxkbcommon=false
-Dportabled=false -Dwheel-group=false "-Dntp-servers=0.debian.pool.ntp.org
1.debi
an.pool.ntp.org 2.debian.pool.ntp.org 3.debian.pool.ntp.org"
-Dlink-udev-shared=false -Dsystem-uid-max=999 -Dsystem-gid-max=999
-Dnobody-user=nobody -Dnobody-group=nogroup -Dbump-proc-sys-fs-nr-open=false
-Ddev-kvm-mode=0660 -Dselinux=true -Dhwdb=true -Dsysusers=true
-Dinstall-tests=true -Defi=true -Dnss-myhostname=true -Dnss-mymachines=true
-Dnss-resolve=true -Dnss-systemd=true -Dresolve=true
-Dlink-systemctl-shared=false -Daudit=true -Dlibcryptsetup=true -Dcoredump=true
-Delfutils=true -Dapparmor=true -Dlibidn=true -Dlibiptc=true -Dlibcurl=true
-Dimportd=true -Dmicrohttpd=true -Dgnutls=true
The Meson build system
Version: 0.49.2
Source dir: /<<PKGBUILDDIR>>
Build dir: /<<PKGBUILDDIR>>/build-deb
Build type: native build
Project name: systemd
[... snipped ...]
--- command ---
/<<PKGBUILDDIR>>/tools/meson-check-help.sh
/<<PKGBUILDDIR>>/build-deb/systemd-hwdb
-------
510/514 check-help-systemd-socket-proxyd OK 0.04 s
--- command ---
/<<PKGBUILDDIR>>/tools/meson-check-help.sh
/<<PKGBUILDDIR>>/build-deb/systemd-socket-proxyd
-------
511/514 check-help-systemd-udevd OK 0.02 s
--- command ---
/<<PKGBUILDDIR>>/tools/meson-check-help.sh
/<<PKGBUILDDIR>>/build-deb/systemd-udevd
-------
512/514 check-help-udevadm OK 0.02 s
--- command ---
/<<PKGBUILDDIR>>/tools/meson-check-help.sh /<<PKGBUILDDIR>>/build-deb/udevadm
-------
513/514 check-help-systemd-nspawn OK 0.04 s
--- command ---
/<<PKGBUILDDIR>>/tools/meson-check-help.sh
/<<PKGBUILDDIR>>/build-deb/systemd-nspawn
-------
514/514 check-help-networkctl OK 0.04 s
--- command ---
/<<PKGBUILDDIR>>/tools/meson-check-help.sh /<<PKGBUILDDIR>>/build-deb/networkctl
-------
Ok: 484
Expected Fail: 0
Fail: 1
Unexpected Pass: 0
Skipped: 29
Timeout: 0
make[1]: *** [debian/rules:296: override_dh_auto_test] Error 1
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:302: binary-arch] Error 2
dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit
status 2
--------------------------------------------------------------------------------
The above is just how the build ends and not necessarily the most relevant part.
I was able to build this package on buster just fine until version 239-15.
Starting with version 240-2 it always fail for me.
I'm using sbuild + schroot. I've tried so far:
Self-hosted KVM machines with one CPU and 6 GB of RAM.
1-XS instances from Scaleway with one CPU and 1GB of RAM.
1-S instances from Scaleway with *two* CPUs and 2GB of RAM:
n1-standard-1 instances from GCE with one CPU and 3.75 GB of RAM.
You will see there is not a pattern here at all. Neither the amount of
RAM or the number of CPUs seem to have any relation with the failure.
(While monitoring RAM usage, I've never seen systemd build to require
more than 500 MB to build anyway).
It is possible that the package now requires an extraordinary amount
of bogomips to build?
Anyway, I've put all my failed build logs here:
https://people.debian.org/~sanvila/build-logs/systemd/
If you need a test machine to reproduce this failure, please contact
me privately and I will gladly offer ssh access to any of those
machines where this seems to happen all the time.
Thanks.
--- End Message ---
--- Begin Message ---
I talked to upstream about this in
https://github.com/systemd/systemd/issues/12023
He basically shares the same concerns that were already raised here and
is not really happy to cater for such special setups.
His suggestion is, that if you insist on bind-mounting /dev/random, you
should make sure to fix-up /dev/char/* accordingly, to not have an
inconsistent /dev.
Regards,
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
--- End Message ---
