Example of karma not being functional [Was:POSTUN scriptlet failure in rpm package cyrus-sasl]

[Ralf Corsepius]

On 03/11/2010 02:52 PM, Mat Booth wrote:
> Saw this in today's updates:
>
>
>    Cleanup        : cyrus-sasl-2.1.23-4.fc12.i686
>                                                     195/254
> groupdel: group 'saslauth' does not exist
> Non-fatal POSTUN scriptlet failure in rpm package cyrus-sasl
> warning: %postun(cyrus-sasl-2.1.23-4.fc12.i686) scriptlet failed, exit status 6

This case is a nice example demonstrating several defects in "applying 
karma votes for QA":


1. The update package was sitting in "updates-testing" since 2010-02-22.


2. It did receive +3 karma points before being pushed to "updates"
c.f. https://admin.fedoraproject.org/updates/cyrus-sasl-2.1.23-6.fc12
=> There are people who claim to have tested it and not having noticed 
anything unusual.


3. During today's update I was immediately "greeted" by the same error 
message Mat cites above and BZ'ed it.
c.f. https://bugzilla.redhat.com/show_bug.cgi?id=572399


4. Despite the fact this package had been pushed to "updates", I had 
been able to cast a karma vote on the package in bodhi.
c.f. https://admin.fedoraproject.org/updates/cyrus-sasl-2.1.23-6.fc12
=> A malfunction in bodhi


5. Unlike in many other similar cases before, the packager responded 
almost immediately and tried to provide an updated package (Thanks!).
However, due to the fact update-candidates are not immediately pushed to 
"updates-testing", this package is not available in "updates-testing".
=> "karma voting on packages in updates-testing" is not applicable in 
situations like these (being directly affect by a bug, the bug still 
"being hot")

Seemingly, other people who were affected by this bug did pick up the 
package from other sources (Most probably directly from bodhi) and 
provided feedback through BZ
c.f. https://bugzilla.redhat.com/show_bug.cgi?id=572399


Think about it, FESCO!

Ralf