Unpushing broken or obsolete updates from testing

[Dominik 'Rathann' Mierzejewski]

On Friday, 06 July 2007 at 03:37, Kevin Kofler wrote:
> Why are updates lingering in updates-testing for weeks when:
> * they are known broken and/or
> * they have already been replaced by a new version, which is already in
>   stable?
> IMHO, that's really what the "unpush" option is for. For example, do we
> really need to have that obsolete Thunderbird RC sitting in testing
> forever when the actual release is already out in the stable updates?
> This also makes it harder to track down the legitimate updates which have
> been sitting in testing for way too long.

This is exactly the kind of thing that should be automated, i.e. run a
script once a week that'd check if there are any obsolete updates in
testing and delete them (notifying the owner perhaps).

Regards,
R.

-- 
Fedora contributor http://fedoraproject.org/wiki/DominikMierzejewski
Livna contributor http://rpm.livna.org MPlayer developer http://mplayerhq.hu
"Faith manages."
        -- Delenn to Lennier in Babylon 5:"Confessions and Lamentations"