Accidentally enabled service after update from F16 to F17 - solutions?
mschmidt at redhat.com
Thu Jun 14 13:10:56 UTC 2012
On 06/14/2012 02:59 PM, Stanislav Ochotnicky wrote:
> +%triggerun -- jetty < 8.1.2-9
You already have one triggerun for jetty in the spec:
%triggerun -- jetty < 8.1.0-3
You're likely to hit this RPM bug:
> +/bin/systemctl --no-reload disable jetty.service >/dev/null 2>&1 ||:
> +/bin/systemctl --no-reload stop jetty.service >/dev/null 2>&1 ||:
> This trigger will do following:
> If we are updating from previous releases, we disable the service and
> stop it if it's running
I dislike this, because:
- You'd just break some users' systems for the sake of a different
subset of users.
- Some breakage during distribution upgrade is more tolerable than
breakage within regular updates.
Is a running jetty really _that_ dangerous? Why do we ship it at all
More information about the devel