$ rpm -qf /lib/systemd/system/remote-fs-pre.target.wants/NetworkManager-wait-online.service NetworkManager-0.9.7.0-12.git20121004.fc18.x86_64 $ rpm -qf /lib/systemd/system/remote-fs-pre.target.wants/ file /lib/systemd/system/remote-fs-pre.target.wants is not owned by any package I am not sure if the directory should be owned by NetworkManager, or by systemd, but it should not be left unowned ( as this is one of the standard target, I would vote for systemd, but feel free to disagree and move the bug to systemd )
I figure systemd shouldn't own all possible .wants/ dirs. Instead the packages in question should jointly own the .wants/ dirs wherever they hook themselves into. We probably should get FPC involved to standardize this in the packaging policy.
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle. Changing version to '23'. (As we did not run this process for some time, it could affect also pre-Fedora 23 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora23
Since other .wants directories are owned by the respective packages, this particular one should be owned by NetworkManager.
Hm, what exactly are you proposing? That various packages should co-own the .wants dirs?
On F23: $ rpm -qf /usr/lib/systemd/system/kexec.target.wants/ plymouth-0.8.9-10.2013.08.14.fc23.x86_64 $ rpm -qf /usr/lib/systemd/system/sysinit.target.wants/ systemd-222-7.fc23.x86_64 initscripts-9.64-1.fc23.x86_64 plymouth-0.8.9-10.2013.08.14.fc23.x86_64 $ rpm -qf /usr/lib/systemd/system/nfs.target.wants/ nfs-utils-1.3.2-11.fc23.x86_64 ... All I'm saying is that /usr/lib/systemd/system/remote-fs-pre.target.wants/ should be owned by NetworkManager.
Yes, we should do that.
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
still valid
[lkundrak@belphegor NetworkManager]$ rpm -ql NetworkManager |grep wait-online /usr/lib/systemd/system/NetworkManager-wait-online.service /usr/lib/systemd/system/network-online.target.wants/NetworkManager-wait-online.service [lkundrak@belphegor NetworkManager]$ rpm -qf /usr/lib/systemd/system/network-online.target.wants/NetworkManager-wait-online.service NetworkManager-1.7.1-17181.08cc81d450.fc25.x86_64 [lkundrak@belphegor NetworkManager]$ rpm -qf /usr/lib/systemd/system/network-online.target.wants NetworkManager-1.7.1-17181.08cc81d450.fc25.x86_64 [lkundrak@belphegor NetworkManager]$ Since the following commit to dist-git we seem to be doing the right thing already: 64aa00035dca29737ef893289ced0f103ac5bbe6 Author: Dan Williams <dcbw> Date: Wed May 15 10:13:45 2013 -0500 Fix systemd leftovers