Re: measuring success [was Re: Bodhi 0.7.5 release]

2010-07-06 Thread Kevin Kofler
Michael Schwendt wrote: > One can quickly see that several (if not many) of them are due > to orphans/retired packages in Fedora 12. And due to violated upgrade > paths (e.g. compat-db): That just proves that we should avoid retiring packages, but try to keep them alive as long as we can, even if

Re: measuring success [was Re: Bodhi 0.7.5 release]

2010-07-04 Thread Till Maas
On Sun, Jul 04, 2010 at 04:47:19PM +0200, Michael Schwendt wrote: > On Sun, 04 Jul 2010 14:40:20 +0200, Till wrote: > > > > It's fairly easy to verify other broken deps, too: > > > http://admin.fedoraproject.org/updates/compat-db-4.7.25-3.fc13 > > > > For me it is not that easy, because the infor

Re: measuring success [was Re: Bodhi 0.7.5 release]

2010-07-04 Thread Michael Schwendt
On Sun, 04 Jul 2010 14:40:20 +0200, Till wrote: > > It's fairly easy to verify other broken deps, too: > > http://admin.fedoraproject.org/updates/compat-db-4.7.25-3.fc13 > > For me it is not that easy, because the information is confusion (or not > clearly arranged) or not directly accessible, e.

Re: measuring success [was Re: Bodhi 0.7.5 release]

2010-07-04 Thread Till Maas
On Sun, Jul 04, 2010 at 02:06:08PM +0200, Michael Schwendt wrote: > On Sun, 04 Jul 2010 13:32:14 +0200, Till wrote: > > > On Sun, Jul 04, 2010 at 12:31:57PM +0200, Michael Schwendt wrote: > > > Broken deps in Fedora 13 + updates + updates-testing when > > > also enabling Fedora 12 + updates + u

Re: measuring success [was Re: Bodhi 0.7.5 release]

2010-07-04 Thread Michael Schwendt
On Sun, 04 Jul 2010 13:32:14 +0200, Till wrote: > On Sun, Jul 04, 2010 at 12:31:57PM +0200, Michael Schwendt wrote: > > Broken deps in Fedora 13 + updates + updates-testing when > > also enabling Fedora 12 + updates + updates-testing. > > > > One can quickly see that several (if not many) of t

Re: measuring success [was Re: Bodhi 0.7.5 release]

2010-07-04 Thread Till Maas
On Sun, Jul 04, 2010 at 12:31:57PM +0200, Michael Schwendt wrote: > Broken deps in Fedora 13 + updates + updates-testing when > also enabling Fedora 12 + updates + updates-testing. > > One can quickly see that several (if not many) of them are due > to orphans/retired packages in Fedora 12. And

Re: measuring success [was Re: Bodhi 0.7.5 release]

2010-07-04 Thread Michael Schwendt
Broken deps in Fedora 13 + updates + updates-testing when also enabling Fedora 12 + updates + updates-testing. One can quickly see that several (if not many) of them are due to orphans/retired packages in Fedora 12. And due to violated upgrade paths (e.g. compat-db): Summary of broken packages

Re: measuring success [was Re: Bodhi 0.7.5 release]

2010-07-03 Thread Adam Williamson
On Sat, 2010-07-03 at 20:40 +0200, Michael Schwendt wrote: > > That only handles a subset of the 'broken dependencies' problem. We've > > already had an example this year of a dependency issue the proposed > > autoqa depcheck test wouldn't catch, and Michael's script didn't - the > > nss-softokn

Re: measuring success [was Re: Bodhi 0.7.5 release]

2010-07-03 Thread Michael Schwendt
On Sat, 03 Jul 2010 10:05:07 -0700, Adam wrote: > On Fri, 2010-07-02 at 18:24 +0200, Ralf Corsepius wrote: > > On 07/02/2010 06:20 PM, Will Woods wrote: > > > > > > > The main reasons we want to perform testing are things like: to avoid > > > pushing updates with broken dependencies, or updates

Re: measuring success [was Re: Bodhi 0.7.5 release]

2010-07-03 Thread Adam Williamson
On Fri, 2010-07-02 at 18:24 +0200, Ralf Corsepius wrote: > On 07/02/2010 06:20 PM, Will Woods wrote: > > > > The main reasons we want to perform testing are things like: to avoid > > pushing updates with broken dependencies, or updates that cause serious > > regressions requiring manual intervent

Re: measuring success [was Re: Bodhi 0.7.5 release]

2010-07-03 Thread Kevin Kofler
Adam Miller wrote: > If there are any discrepancy with the proventesters critpath policy then > please feel free to file a ticket with FESCo and allow our elected > officials decide the fate of this. There isn't any such discrepancy, it's the policy which is broken and FESCo which refuses to unde

Re: measuring success [was Re: Bodhi 0.7.5 release]

2010-07-03 Thread Adam Miller
If there are any discrepancy with the proventesters critpath policy then please feel free to file a ticket with FESCo and allow our elected officials decide the fate of this. -AdamM (From Android) On Jul 2, 2010 8:16 PM, "Kevin Kofler" wrote: Will Woods wrote: > The main reasons we want to perf

Re: measuring success [was Re: Bodhi 0.7.5 release]

2010-07-02 Thread Kevin Kofler
Will Woods wrote: > The main reasons we want to perform testing are things like: to avoid > pushing updates with broken dependencies The right way to prevent that is to get AutoQA completed, which will, if it works as intended, automatically detect and throw out updates with broken dependencies

Re: measuring success [was Re: Bodhi 0.7.5 release]

2010-07-02 Thread Ralf Corsepius
On 07/02/2010 06:20 PM, Will Woods wrote: > The main reasons we want to perform testing are things like: to avoid > pushing updates with broken dependencies, or updates that cause serious > regressions requiring manual intervention / emergency update > replacements. That sort of thing. > Should b

measuring success [was Re: Bodhi 0.7.5 release]

2010-07-02 Thread Will Woods
On Thu, 2010-07-01 at 06:33 +0200, Kevin Kofler wrote: > Fedora Legacy has shown how well this works… not! > > I completely agree with Ralf Corsepius and Tom Lane on this subject: this > policy is very unhelpful, and applying it to security updates is just > totally insane. We're going to see m