Unpushing broken or obsolete updates from testing

Matthias Saou thias at spam.spam.spam.spam.spam.spam.spam.egg.and.spam.freshrpms.net
Mon Jul 16 14:53:47 UTC 2007


Jesse Keating wrote :

> On Mon, 16 Jul 2007 07:01:04 -0400
> Jesse Keating <jkeating at j2solutions.net> wrote:
> 
> > > You still need to manually unpush the broken updates when you do
> > > that, or they'll clutter Bodhi forever, and probably even show up in
> > > the testing repo again once the fixed version gets promoted to
> > > stable.  
> > 
> > 
> > Only the latest update will show up in the repo.
> 
> Whoops, I re-read what you wrote, and you are correct.  Pushing the
> correct build over to stable would unmask the incorrect build from
> -testing.  Of course, yum most likely wouldn't offer it as an update
> due to n-v-r, but still.

But we would then be back to the first (simple) scenario, where we have
an obsolete update needing to be cleaned, right? My concern is with
updated packages appearing in updates-testing, then "disappearing"
because they were considered broken, since those might stick around for
a while on many systems, not a good thing since bug reports might be
filed against the package long after it has disappeared.

Matthias

-- 
Clean custom Red Hat Linux rpm packages : http://freshrpms.net/
Fedora release 7 (Moonshine) - Linux kernel 2.6.21-1.3255.fc7
Load : 0.17 0.35 0.53




More information about the fedora-devel-list mailing list