From: Henning Schild <henning.schild@siemens.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: isar-users <isar-users@googlegroups.com>
Subject: Re: bullseye CI jobs fail on systemd
Date: Mon, 23 Mar 2020 18:02:55 +0100 [thread overview]
Message-ID: <20200323180255.129ea249@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <dc09a23e-bffa-6af3-5036-ccb33c69198b@siemens.com>
Am Sun, 22 Mar 2020 18:09:49 +0100
schrieb Jan Kiszka <jan.kiszka@siemens.com>:
> On 21.03.20 09:30, [ext] Henning Schild wrote:
> > Hi,
> >
> > on several CI runs i saw bullseye failing on systemd postinst.
> > There is a new systemd version since 03/18 and i guess it might
> > just be a temporary upstream issue. I did not look further, instead
> > removed bullseye from CI for my builds.
> >
> > Setting up systemd (244.3-1) ...
> > 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/dbus-org.freedesktop.timesync1.service ->
> > /lib/systemd/system/systemd-timesyncd.service. Created symlink
> > /etc/systemd/system/sysinit.target.wants/systemd-timesyncd.service
> > -> /lib/systemd/system/systemd-timesyncd.service. Initializing
> > machine ID from random generator. dpkg: error processing package
> > systemd (--configure): installed systemd package post-installation
> > script subprocess returned error exit status 73
>
> I'm seeing this now as well - but only with your series applied (you
> can see that in our internal CI, nightly runs). Given this, we should
> look more closely to avoid overseeing some regression. Or we managed
> to trigger an upstream issues that no many see and, thus, should be
> reported.
Thanks! Got to love caches and multiconfig ;). At least this one seems
reproducible.
Henning
> Jan
>
prev parent reply other threads:[~2020-03-23 17:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-21 8:30 Henning Schild
2020-03-22 17:09 ` Jan Kiszka
2020-03-23 17:02 ` Henning Schild [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200323180255.129ea249@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox