FS#45885 - [namcap] Symlink points to non-existing X, but X provided by dependency. And related dep not needed.

Attached to Project: Arch Linux
Opened by James Harvey (jamespharvey20) - Tuesday, 04 August 2015, 00:09 GMT
Last edited by Jelle van der Waa (jelly) - Friday, 11 August 2023, 15:51 GMT
Task Type Bug Report
Category Arch Projects
Status Closed
Assigned To Kyle Keen (keenerd)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

On core/systemd (x86_64 223 and the upcoming 224 should do this too):

...
Checking systemd-sysvcompat-223-1-x86_64.pkg.tar.xz
systemd-sysvcompat E: Symlink (usr/bin/runlevel) points to non-existing systemctl
systemd-sysvcompat E: Symlink (usr/bin/reboot) points to non-existing systemctl
systemd-sysvcompat E: Symlink (usr/bin/shutdown) points to non-existing systemctl
systemd-sysvcompat E: Symlink (usr/bin/poweroff) points to non-existing systemctl
systemd-sysvcompat E: Symlink (usr/bin/halt) points to non-existing systemctl
systemd-sysvcompat E: Symlink (usr/bin/telinit) points to non-existing systemctl
systemd-sysvcompat E: Symlink (usr/bin/init) points to non-existing ../lib/systemd/systemd
<a semi-valid response snipped>
systemd-sysvcompat W: Dependency included and not needed ('systemd')

systemd-sysvcompat depends on systemd, which provides /usr/bin/systemctl and /usr/lib/systemd/systemd. So, once the depends are installed, the symlinks are no longer invalid.

Because of these symlinks, then, the dependency is needed for the symlinks to be valid.
This task depends upon

Closed by  Jelle van der Waa (jelly)
Friday, 11 August 2023, 15:51 GMT
Reason for closing:  Moved
Additional comments about closing:  https://gitlab.archlinux.org/pacman/namc ap/issues/44
Comment by Kyle Keen (keenerd) - Wednesday, 22 March 2017, 15:39 GMT
This is now half fixed with commit 1a44d4e747. The symlink errors are gone, but the dependency warning is still there. Won't be fully fixed until that is also handled.
Comment by Buggy McBugFace (bugbot) - Tuesday, 08 August 2023, 19:11 GMT
This is an automated comment as this bug is open for more then 2 years. Please reply if you still experience this bug otherwise this issue will be closed after 1 month.

Loading...