Mass bug: packages should not auto-enable systemd units
luto at mit.edu
Wed Apr 30 16:02:30 UTC 2014
Due to some confusion around how alternatives worked, I screwed up the
list of packages here. I've updated it below. I'll give it a few
more days before filing the actual bugs.
On Wed, Apr 23, 2014 at 4:59 PM, Andrew Lutomirski <luto at mit.edu> wrote:
> Hi everyone-
> This is a notice in accordance with the mass bug filing procedure.
> A number of packages install systemd units and enable them
> automatically. They should not. Please update these packages to use the
> macroized scriptlet
> If your package has an exception from FESCo permitting it to enable
> itself, please make sure that the service in question is listed in the
> appropriate preset file.
> There is a general exception described here:
> If your package falls under the general exception, then it is possible
> that no change is required. Nevertheless, if you are relying on the
> exception, please make sure that your rpm scripts are sensible. The
> exception is:
> In addition, any service which does not remain persistent on the
> system (aka, it "runs once then goes away"), does not listen to
> incoming connections during initialization, and does not require
> configuration to be functional may be enabled by default (but is not
> required to do so). An example of "runs once then goes away" service
> is iptables.
> Given that this issue can affect Fedora 20 users who install your
> package as a dependency, these bugs should be fixed in Fedora 20 and
> The tracker bug is here:
> I created it early because three of the bugs are pre-existing. Next
> week, I'll file bugs against the packages below. If you fix your
> package in the mean time, please let me know.
> After three weeks, provenpackagers may step in and fix these issues.
devel-announce mailing list
devel-announce at lists.fedoraproject.org
More information about the devel