From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6806575802439696384 X-Received: by 2002:a50:9384:: with SMTP id o4mr21957147eda.309.1584982978485; Mon, 23 Mar 2020 10:02:58 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a05:6402:c08:: with SMTP id co8ls787830edb.9.gmail; Mon, 23 Mar 2020 10:02:57 -0700 (PDT) X-Google-Smtp-Source: ADFU+vuHg0fIqVzxvJPGtETzBPdgGJIWgOdIiptgBnkkIOtu3gL9Jn3Ru7u+4c5P+reMvrM3EW18 X-Received: by 2002:aa7:c5d0:: with SMTP id h16mr17168032eds.236.1584982977958; Mon, 23 Mar 2020 10:02:57 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1584982977; cv=none; d=google.com; s=arc-20160816; b=kNKYlXhVd+NPn68Y5HQzIVbmntA8bNU7J/QNE2RwDoqlpzLGISeKEQXIFAZPdvlPc2 ZwEnToVv7YNZoBjM3M+woU9GJx3/KZ6hB1i3aM4KNvvHqpLqLOQUVHGz1GrO7vK7GKWT Ie2zn/e0NbKcXNrwdANFq0Y+R8v5KDifnFczX56eD7hKkHVNyAdrSjZQhc9wvvLNgG9o qbCt1gZvk/YLDFs+IdbFLMcm+H8X5BdyPZkCpXrBNcU5zxYdHpZDgH/1Ruu1DDojfeZ9 4UwttxHMzO7sGBVCX0+9q+GtClkIMJKwR6i1L92Owa5Vdz+rwU3Ca2CDwUT4ca/j7nr7 qldw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date; bh=5Wb1FbaugWRP9dp+8P35g++wo4qnoWkdk1R13WHiV4E=; b=RLs+KCViefgReMXnLrGVxNHGMZJqSLhhTmfYDthZ7TZKyOLzvsjt1SIlhwMHD9Y6vp lCiGLlocAZDq88YXNhNHYbyptaj5nANv2njIKCLwvgK6I0i3ERj+8+gT4gfpNv98UWa/ c/77n6E/rz21jQQMTkyvWU3h+4Fw5WmFpmELdc/wEDVOS0jEJxgCTQJC1fXSNQVjfE5v kx7rX/N10sza6/90H5Ij7vYoeD6MvIV2HKrDBEl6ZrgMjQDIQ9R0YUxcWFUiHVQYzwsD b1DNDjR+0VF8xdaktJXu1XuCBWjaAfKDxTIBzCN2f9+KdUx15RyEojGB+PYZmzjkwGgd 3B7g== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of henning.schild@siemens.com designates 194.138.37.40 as permitted sender) smtp.mailfrom=henning.schild@siemens.com; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=siemens.com Return-Path: Received: from gecko.sbs.de (gecko.sbs.de. [194.138.37.40]) by gmr-mx.google.com with ESMTPS id ck3si751255edb.5.2020.03.23.10.02.57 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 23 Mar 2020 10:02:57 -0700 (PDT) Received-SPF: pass (google.com: domain of henning.schild@siemens.com designates 194.138.37.40 as permitted sender) client-ip=194.138.37.40; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of henning.schild@siemens.com designates 194.138.37.40 as permitted sender) smtp.mailfrom=henning.schild@siemens.com; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=siemens.com Received: from mail2.sbs.de (mail2.sbs.de [192.129.41.66]) by gecko.sbs.de (8.15.2/8.15.2) with ESMTPS id 02NH2v95005784 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Mon, 23 Mar 2020 18:02:57 +0100 Received: from md1za8fc.ad001.siemens.net ([167.87.5.182]) by mail2.sbs.de (8.15.2/8.15.2) with ESMTP id 02NH2v1w017199; Mon, 23 Mar 2020 18:02:57 +0100 Date: Mon, 23 Mar 2020 18:02:55 +0100 From: Henning Schild To: Jan Kiszka Cc: isar-users Subject: Re: bullseye CI jobs fail on systemd Message-ID: <20200323180255.129ea249@md1za8fc.ad001.siemens.net> In-Reply-To: References: <20200321093017.3cbb6321@md1za8fc.ad001.siemens.net> X-Mailer: Claws Mail 3.17.4 (GTK+ 2.24.32; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-TUID: ryio3H7+DXiJ Am Sun, 22 Mar 2020 18:09:49 +0100 schrieb Jan Kiszka : > 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 >