FS#54718 - [systemd] Link to systemd-resolved.service should be absolut

Attached to Project: Arch Linux
Opened by Stefan (steinwanderer) - Thursday, 06 July 2017, 09:40 GMT
Last edited by Christian Hesse (eworm) - Thursday, 06 July 2017, 11:14 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Dave Reisner (falconindy)
Christian Hesse (eworm)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:

Upgrading systemd to 233.75-2 throws an error about "dbus-org.freedesktop.resolve1.service".
This is due to a relative link in "/etc/systemd/system/" and IMHO should be absolut.

Additional info:

* package version(s)

systemd 233.75-2

* config and/or log files etc.

$ pacman -Syu systemd
[...]
Warnung: konnte Dateiinformationen für etc/systemd/system/dbus-org.freedesktop.resolve1.service nicht ermitteln
[...]

$ ls -l /etc/systemd/system/dbus-org.freedesktop.resolve1.service
lrwxrwxrwx 1 root root 56 5. Jul 23:35 /etc/systemd/system/dbus-org.freedesktop.resolve1.service -> ../../../usr/lib/systemd/system/systemd-resolved.service

Steps to reproduce:

$ pacman -Syu systemd
and watch console

Note:

After manually recereating the link, the above error goes away.

$ ls -l /etc/systemd/system/dbus-org.freedesktop.resolve1.service
lrwxrwxrwx 1 root root 48 6. Jul 11:18 /etc/systemd/system/dbus-org.freedesktop.resolve1.service -> /usr/lib/systemd/system/systemd-resolved.service
This task depends upon

Closed by  Christian Hesse (eworm)
Thursday, 06 July 2017, 11:14 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed in SVN
Comment by Christian Hesse (eworm) - Thursday, 06 July 2017, 10:46 GMT
Looks like you deleted that file before update, no? The error message should appear only when the file does not exist at all.

Wondering why this does exist in /etc, though...
Comment by Christian Hesse (eworm) - Thursday, 06 July 2017, 11:06 GMT
This was an intentional change by upstream, see:
https://github.com/systemd/systemd/commit/4d1f490c9386d1a824ce8269de5ed7938cbf8096

The stupid thing is that this is enabled again on package update...

About the original issue... Probably you issue:
systemctl disable systemd-resolved.service

Loading...