RFC: Simply the retirement procedure - trigger on dead.package

Ralph Bean rbean at redhat.com
Wed Nov 27 19:30:23 UTC 2013

On Wed, Nov 27, 2013 at 07:46:28PM +0100, Till Maas wrote:
> On Wed, Nov 27, 2013 at 12:35:13PM -0600, Bruno Wolff III wrote:
> > On Wed, Nov 27, 2013 at 19:21:53 +0100,
> >   Till Maas <opensource at till.name> wrote:
> > >
> > >What are your opinions about this? I already checked with Dennis
> > >Gilmore, he is ok with this.
> > 
> > Is there a fail against doing this in released versions? (Unless
> > there is a legal reason to do the retirement, we wouldn't want to do
> > that for a package in a release.)
> It will be done only for Rawhide and Branched (until the Final Change
> Deadline) and maybe EPEL if desired. Wether or not to e.g. retire
> packages for other releases without blocking them in Koji needs to be
> decided.
> Regards
> Till

Sounds like a good idea to me.  Also seems like it is important enough
to run inside the infrastructure environment so that it can be

The #fedora-apps team has been working on pkgdb2 which the authors
hope to deploy shortly after the F20 release.  Restricting retirement
rights to the automated process shouldn't be a problem.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 490 bytes
Desc: not available
URL: <http://lists.fedoraproject.org/pipermail/devel/attachments/20131127/7043cd98/attachment.sig>

More information about the devel mailing list