Your message dated Tue, 3 Feb 2015 13:00:56 +0100
with message-id <[email protected]>
and subject line Re: Bug#776912: debootstrap circular depends/pre-depends
between sytemd-sysv and systemd
has caused the Debian Bug report #776912,
regarding systemd: missing /dev/urandom makes postinst fail
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 [email protected]
immediately.)
--
776912: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776912
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 215-10
Severity: important
When trying to debootstrap jessie on an RHEL7 / CENTOS7 (system is
running systemd 208 Release 11.el7_0.6) system for usage with lxc or
docker debootstrap fails due to systemd and systemd-sys:
dpkh: systemd-sysv: dependency problems, but configuring anyway as you
requested:
systemd-sysv depends on systemd (= 215-10); however:
Package systemd is not cnfigured yet.
systemd-sysv depends on systemd; however:
Package systemd is not configured yet.
(...)
Errors were encountered while processing:
systemd
yours Martin
--- End Message ---
--- Begin Message ---
All,
sorry, I used reply instead of group-reply.
* Michael Biebl <[email protected]> [2015-02-03 12:46]:
> Am 03.02.2015 um 11:59 schrieb Ansgar Burchardt:
> >
> > please remember to also send replies to the bug report (I've not
> > forwarded your message).
> >
> > The debootstrap log looks a bit more scary than I think it should, but
> > I'll take a look at only the systemd error:
I did a verbose debootstrap to find out what is going on.
> > On 02/03/2015 11:22 AM, Martin Wuertele wrote:
> >> Setting up systemd (215-10) ...
> >> Failed to open /dev/urandom: Function not implemented
> >> dpkg: error processing package systemd (--configure):
> >> subprocess installed post-installation script returned error exit status 1
> >
> > I think this comes from systemd-machine-id-setup which is called in
> > systemd's postinst:
> >
> > core/machine-id-setup.c:140 (in generate):
> > r = sd_id128_randomize(&buf);
> >
> > libsystemd/sd-id128/sd-id128.c:216:
> > r = dev_urandom(&t, sizeof(t));
> >
> > shared/util.c:2371-2373:
> > fd = open("/dev/urandom", O_RDONLY|O_CLOEXEC|O_NOCTTY);
> > if (fd < 0)
> > return errno == ENOENT ? -ENOSYS : -errno;
> >
> > To make sure, could you try running systemd-machine-id-setup in the
> > chroot? And check if /dev/urandom is present in the chroot?
Yes, /dev/urandom is missing in the container as extracting
devices.tar.gz failed and I removed it from functions to do it manually.
> I might be missing something obvious, but where is the supposed
> dependency cycle between systemd-sysv and systemd?
You are right, there is no circualr dependency problem. I will close the
bug now.
Thank you all for the great help!
Martin
--- End Message ---
