Your message dated Tue, 12 Oct 2021 14:33:50 +0200
with message-id <1dbe39b81851cc27a3642183262dff9fee019bb1.ca...@debian.org>
and subject line Re: systemd: systemctl preset-all fails to handle /lib/systemd 
-> /usr/lib/systemd transition
has caused the Debian Bug report #992847,
regarding systemd: systemctl preset-all fails to handle /lib/systemd -> 
/usr/lib/systemd transition
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.)


-- 
992847: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992847
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd
Version: 247.9-1
Severity: important

Hi,

this seems to be related to the "dh_installsystemd: Prefer
/usr/lib/systemd/ to /lib/systemd" change from debhelper v13.4.

Our daily Grml ISO builds started to fail a few days ago, because in
our chroots we have a symlink for
/etc/systemd/system/syslog.service, which points to
/lib/systemd/system/rsyslog.service (as it used to be in the rsyslog
packaging in the past):

| lrwxrwxrwx 1 root root 35 Aug 24 07:54 /etc/systemd/system/syslog.service -> 
/lib/systemd/system/rsyslog.service

Now, when invoking `systemctl preset-all` this fails as follows:

| # systemctl preset-all
| Unit /lib/systemd/system/cryptdisks.service is masked, ignoring.
| Unit /lib/systemd/system/mdadm-waitidle.service is masked, ignoring.
| Unit /lib/systemd/system/rcS.service is masked, ignoring.
| Unit /lib/systemd/system/sudo.service is masked, ignoring.
| Unit /lib/systemd/system/cryptdisks-early.service is masked, ignoring.
| Unit /lib/systemd/system/x11-common.service is masked, ignoring.
| Unit /lib/systemd/system/screen-cleanup.service is masked, ignoring.
| Unit /lib/systemd/system/rc.service is masked, ignoring.
| Unit /lib/systemd/system/mdadm.service is masked, ignoring.
| Unit /lib/systemd/system/nfs-common.service is masked, ignoring.
| Unit /lib/systemd/system/lvm2.service is masked, ignoring.
| Unit /lib/systemd/system/hwclock.service is masked, ignoring.
| Failed to preset unit, file /etc/systemd/system/syslog.service already exists 
and is a symlink to /lib/systemd/system/rsyslog.service.

When manually removing the /etc/systemd/system/syslog.service symlink,
then it works as expected:

| # rm /etc/systemd/system/syslog.service
| # systemctl preset-all
| Unit /lib/systemd/system/cryptdisks.service is masked, ignoring.
| Unit /lib/systemd/system/mdadm-waitidle.service is masked, ignoring.
| Unit /lib/systemd/system/rcS.service is masked, ignoring.
| Unit /lib/systemd/system/sudo.service is masked, ignoring.
| Unit /lib/systemd/system/cryptdisks-early.service is masked, ignoring.
| Unit /lib/systemd/system/x11-common.service is masked, ignoring.
| Unit /lib/systemd/system/screen-cleanup.service is masked, ignoring.
| Unit /lib/systemd/system/rc.service is masked, ignoring.
| Unit /lib/systemd/system/mdadm.service is masked, ignoring.
| Unit /lib/systemd/system/nfs-common.service is masked, ignoring.
| Unit /lib/systemd/system/lvm2.service is masked, ignoring.
| Unit /lib/systemd/system/hwclock.service is masked, ignoring.
| Created symlink /etc/systemd/system/syslog.service → 
/usr/lib/systemd/system/rsyslog.service.

The issue might have to be fixed from within the rsyslog package
itself, but given that this issue might affect further packages and
whoever relies on `systemctl preset-all`, I decided to report it
against systemd. Feel free to reassign as needed. Maybe also
to be considered RC severity?

regards
-mika-

Attachment: signature.asc
Description: Digital signature


--- End Message ---
--- Begin Message ---
On Mon, 27 Sep 2021 07:57:59 +0200 Michael Prokop <m...@debian.org> wrote:
> Hi,
> 
> * Michael Biebl [Sat Sep 25, 2021 at 10:12:53PM +0200]:
> > On Tue, 24 Aug 2021 10:07:59 +0200 Michael Prokop <m...@debian.org>
wrote:
> 
> > > this seems to be related to the "dh_installsystemd: Prefer
> > > /usr/lib/systemd/ to /lib/systemd" change from debhelper v13.4.
> 
> > Seems this change was reverted in debhelper 13.5.2 so I wonder what to
do
> > about this bug report.
> 
> If debhelper no longer places files in /usr/lib/systemd/ instead of
> /lib/systemd, then this bug report shouldn't be valid any longer, I guess?
> (Feel free to close it if you think it no longer applies, though if
> you'd prefer to keep it open until the overall situation has
> settled, please feel free to do so either, I'm fine both ways :))
> 
> > I guess the solution here is to wait for mandatory merged-/usr in
bookworm,
> > in wich case this will be moot anyway.
> 
> ACK
> 
> > I suppose, your Grml ISO build didn't have a merged-/usr file system, so
the
> > /etc/systemd/system/syslog.service was dangling, pointing at a file
> > /lib/systemd/system/rsyslog.service which was now
> > /usr/lib/systemd/system/rsyslog.service ?


The changes in debhelper have been rolled back and Simon is currently
working on https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994388 which
includes a moratorium for moving files from /lib to /usr/lib.

I will thus close this bug report, as systemd upstream never considered a
situation like this, where merged-usr was not mandatory but individual files
being moved to /usr. It is thus unlikely, that I can convince them to
support such a use case.

Regards,
Michael


Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---

Reply via email to