Your message dated Sun, 27 May 2018 09:24:45 +0900
with message-id <20180527092445.5528fc6a93205bd222ca8...@iijmio-mail.jp>
and subject line Re: Bug#900168: systemd: Ignore systemd-machine-id-setup
has caused the Debian Bug report #900168,
regarding systemd: Ignore systemd-machine-id-setup
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.)
--
900168: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900168
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd
Severity: wishlist
Hi,
During debootstrap autopkgtest, it runs debootstap itself under systemd-nspawn
environment. And salsa CI runner runs it under docker and it doesn't have
full privilege. Then it causes error with systemd package setup with run
systemd-machine-id-setup.
docker + systemd-nspawn + debootstrap(chroot) = systemd-machine-id-setup fail.
Attached patch would just ignore this error.
--
Regards,
Hideki Yamane henrich @ debian.org/iijmio-mail.jp
>From 957860aab5ae02885331219b49903e95c8023f7f Mon Sep 17 00:00:00 2001
From: Hideki Yamane <henr...@debian.org>
Date: Sat, 26 May 2018 22:25:50 +0900
Subject: [PATCH] Ignore systemd-machine-id-setup error for in some environment
In docker container, debootstraping (under chroot) is prevented
because of systemd-machine-id-setup error. This change ignores it.
(snip)
> Setting up systemd (238-4) ...
> Created symlink /etc/systemd/system/getty.target.wants/getty@tty1.service -> /lib/systemd/system/getty@.service.
> Created symlink /etc/systemd/system/multi-user.target.wants/remote-fs.target -> /lib/systemd/system/remote-fs.target.
> Created symlink /etc/systemd/system/sysinit.target.wants/systemd-timesyncd.service -> /lib/systemd/system/systemd-timesyncd.service.
> Initializing machine ID from random generator.
> Failed to mount /etc/machine-id: Operation not permitted
> dpkg: error processing package systemd (--install):
> installed systemd package post-installation script subprocess returned error exit status 1
> Processing triggers for libc-bin (2.27-3) ...
> Errors were encountered while processing:
> systemd
---
debian/systemd.postinst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/debian/systemd.postinst b/debian/systemd.postinst
index e289ac517..ebaf9752f 100644
--- a/debian/systemd.postinst
+++ b/debian/systemd.postinst
@@ -91,7 +91,7 @@ if [ -z "$2" ]; then
fi
# Create /etc/machine-id
-systemd-machine-id-setup
+systemd-machine-id-setup || true
# Setup system users and groups
addgroup --quiet --system systemd-journal
--
2.17.0
--- End Message ---
--- Begin Message ---
On Sun, 27 May 2018 01:46:35 +0200
Michael Biebl <bi...@debian.org> wrote:
> It would also ignore any other error, so I don't think we can apply the
> patch as is.
Make sense, my proposed patch is rough a bit.
And I've found debootstrap --minbase option can avoid to include systemd
so please forget it, sorry for the noise.
--
Regards,
Hideki Yamane henrich @ debian.org/iijmio-mail.jp
--- End Message ---
_______________________________________________
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
