Re: security update process failure

2011-09-06 Thread Steve Grubb
On Tuesday, September 06, 2011 09:02:17 AM Chuck Anderson wrote: > On Tue, Sep 06, 2011 at 08:57:01AM -0400, Genes MailLists wrote: > > libcap provides posix capabilities support - fair question would be > > > > how to get a list of applications which use libcap stuff it provides. > > > > rpm

Re: security update process failure

2011-09-06 Thread Michael Cronenworth
On 09/06/2011 07:57 AM, Genes MailLists wrote: > I suspect someone has or has written a tool to catalog these things - > > anyone? # lsof | grep libcap.so -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test

Re: security update process failure

2011-09-06 Thread Chuck Anderson
On Tue, Sep 06, 2011 at 08:57:01AM -0400, Genes MailLists wrote: > libcap provides posix capabilities support - fair question would be > how to get a list of applications which use libcap stuff it provides. > > rpm -q -l libcap > > shows these are provided: > > /lib64/libcap.so.2 > /lib64/l

Re: security update process failure

2011-09-06 Thread Genes MailLists
> On Sun, 2011-09-04 at 23:14 -0400, Chuck Anderson wrote: > >> I need guidance. I've installed the F14 libcap from updates-testing. >> I have no idea if it works or how to test it--it doesn't appear to >> "break" anything as far as normal operation of my system. Is that >> good enough to give

Re: security update process failure

2011-09-06 Thread Adam Williamson
On Sun, 2011-09-04 at 23:14 -0400, Chuck Anderson wrote: > I need guidance. I've installed the F14 libcap from updates-testing. > I have no idea if it works or how to test it--it doesn't appear to > "break" anything as far as normal operation of my system. Is that > good enough to give +1 karma

Re: security update process failure

2011-09-05 Thread Karsten Hopp
Am 05.09.2011 05:14, schrieb Rahul Sundaram: > On 09/05/2011 02:31 AM, Karsten Hopp wrote: > > Hi ! > > > > > > I'd call it a failure when a security update for a critical path package > > gets stuck in > > -updates-testing for 6 weeks. I'm talking about the F14 libcap update, > > where only o

Re: security update process failure

2011-09-04 Thread Chuck Anderson
On Mon, Sep 05, 2011 at 08:48:07AM +0530, Rahul Sundaram wrote: > On 09/05/2011 08:44 AM, Chuck Anderson wrote: > > So, I guess what I'm asking is, is it ok to give +1 to any/all > > packages if they work at all/we don't notice any regressions, or do we > > have to actually test what they are suppo

Re: security update process failure

2011-09-04 Thread Rahul Sundaram
On 09/05/2011 08:44 AM, Chuck Anderson wrote: > So, I guess what I'm asking is, is it ok to give +1 to any/all > packages if they work at all/we don't notice any regressions, or do we > have to actually test what they are supposed to fix? Thanks. It is ok to +1 if you don't notice any regressions

Re: security update process failure

2011-09-04 Thread Chuck Anderson
On Sun, Sep 04, 2011 at 05:34:43PM -0700, Adam Williamson wrote: > On Sun, 2011-09-04 at 23:01 +0200, Karsten Hopp wrote: > > Hi ! > > > > > > I'd call it a failure when a security update for a critical path package > > gets stuck in > > -updates-testing for 6 weeks. I'm talking about the F14 l

Re: security update process failure

2011-09-04 Thread Rahul Sundaram
On 09/05/2011 02:31 AM, Karsten Hopp wrote: > Hi ! > > > I'd call it a failure when a security update for a critical path package gets > stuck in > -updates-testing for 6 weeks. I'm talking about the F14 libcap update, where > only one > proventester cared to test the updated package and commen

Re: security update process failure

2011-09-04 Thread Peter Robinson
On Mon, Sep 5, 2011 at 1:34 AM, Adam Williamson wrote: > On Sun, 2011-09-04 at 23:01 +0200, Karsten Hopp wrote: >> Hi ! >> >> >> I'd call it a failure when a security update for a critical path package >> gets stuck in >> -updates-testing for 6 weeks. I'm talking about the F14 libcap update, wher

Re: security update process failure

2011-09-04 Thread Adam Williamson
On Sun, 2011-09-04 at 23:01 +0200, Karsten Hopp wrote: > Hi ! > > > I'd call it a failure when a security update for a critical path package gets > stuck in > -updates-testing for 6 weeks. I'm talking about the F14 libcap update, where > only one > proventester cared to test the updated packa