libedit update needs karma

[Adam Williamson]

On Fri, 2011-04-01 at 09:13 -0600, Jerry James wrote:

> > Yeah, handling cases like this where a somewhat 'obscure' library hits
> > critpath through deps is something I've been thinking about.
> > package-specific test cases would help, if someone would write them. :)
> > I think this gets to be critpath via the openssh and possibly ntp
> > requirements; it may help to know exactly what those apps _do_ with
> > libedit. But from a critpath perspective, this update is okay as long as
> > dependent critpath apps still work.
> >
> > It would be nice if Bodhi could say 'this update is critical path
> > because of the following dependency chain:', but I don't know how
> > practical that is...
> 
> And, as an aside, that update still only has karma of 2.  How do I
> tell if either of the respondents is a proventester?  Is that
> indicated in the feedback somehow?  

You probably know this now, but proven testers get a (proventester) next
to their FAS name in their feedback.

> This is my first experience with a
> critpath update, so I'm feeling pretty ignorant of how it's supposed
> to work.  If I still need a proventester, what kind of bribe do I need
> to offer?

Beer's the good old traditional standby. Or possibly a hot dog? :)
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net