SELinux RPM scriplet issue annoucement

Jonathan Dieter jdieter at
Sun Jan 19 18:32:26 UTC 2014

On Sun, 2014-01-19 at 19:15 +0100, drago01 wrote:
> On Sat, Jan 18, 2014 at 9:47 PM, Rahul Sundaram <metherid at> wrote:
> > Hi
> >
> > Since updates don't automatically fix the issue created by
> > 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

If scriptlet failures weren't fatal, we wouldn't have the problem we
have now with duplicate packages.  We could have just pushed the selinux
update, then bumped the release for all updates in the last few pushes,
and then rebuilt them.  If some of the scriptlets were vitally
important, they would get run with the new updates.

Am I missing something?  Is there any reason why scriptlet failures
should be fatal?


More information about the devel mailing list