SELinux RPM scriplet issue annoucement
drago01 at gmail.com
Sun Jan 19 19:00:44 UTC 2014
On Sun, Jan 19, 2014 at 7:32 PM, Jonathan Dieter <jdieter at lesbg.com> wrote:
> On Sun, 2014-01-19 at 19:15 +0100, drago01 wrote:
>> On Sat, Jan 18, 2014 at 9:47 PM, Rahul Sundaram <metherid at gmail.com> wrote:
>> > Hi
>> > Since updates don't automatically fix the issue created by
>> > https://bugzilla.redhat.com/show_bug.cgi?id=1054350 and users are required
>> > to run a set of steps as a workaround, shouldn't this be announced via the
>> > fedora announce list and posted in the Fedora website prominently as well?
>> So it happened .. how do we prevent it in the future? How did it pass testing?
> Should we modify rpm so scriptlet failures aren't fatal? This is the
> second time in the last six months or so that I've seen scriptlet
> failures cause major update problems in Fedora, solely because they are
> fatal (see https://bugzilla.redhat.com/show_bug.cgi?id=989145).
Well updates should be atomic so you either have the previous
(working) start or the new working state and thing in between.
Yes this requires a bit of work but isn't impossible (requires some
infra at a lower level though).
More information about the devel