Summary: | sys-apps/systemd - symlinks in /etc/systemd/ should be fixed after SYMLINK_LIB=no conversion | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Alexander Tsoy <alexander> |
Component: | Current packages | Assignee: | Gentoo systemd Team <systemd> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | CC: | arthur, candrews, dschridde+gentoobugs, haavardw, tsmksubc, xdudka00 |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: | https://bugs.freedesktop.org/show_bug.cgi?id=68102 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 506276 |
Description
Alexander Tsoy
2014-05-12 12:52:54 UTC
Confirming this, since I just carried out the amd64 17.1 profile conversion and some my symlinks were invalid afterwards. It feels as though this ought to be part of the unsymlink-lib script, since the unconverted symlinks were installed by various packages rather than systemd itself. It seems easy enough to convert them: "systemctl enable <name>" removed the old symlink and installed a new one. Fixing the symlinks is generally unnecessary; in many cases, systemd ignores the symlink target and simply uses the name. This bug is about those symlinks that created due to Alias options in units: display-manager.service, dbus-org.freedesktop.*.service, etc. what is the status of this at present time? I added systemd_reenable calls to several packages that install units that utilize the Alias directive. Beyond that, I don't plan to take further action unless someone presents another problem. Thanks :) |