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

Toshio Kuratomi a.badger at gmail.com
Wed Nov 27 19:35:04 UTC 2013

On Wed, Nov 27, 2013 at 07:21:53PM +0100, Till Maas wrote:
> Hi,
> while cleaning up retired packages (which I did not yet finish), I came
> up with an idea to simplify the retirement procedure to avoid
> inconsistencies. With the help of fedmsg I would like to make it enough
> wrt to koji and pkgdb to add a dead.package file to dist git to
> retire a package. When this happens, an automated process will retire
> the package in pkgdb and block the package in koji. This will make
> it impossible to only dead.package or only retire a package in pkgdb.
> To avoid problems with lost messages from fedmsg, a regular cleanup job
> can download a git checkout and check for any missed dead.package files.
> What are your opinions about this? I already checked with Dennis
> Gilmore, he is ok with this.
> My plan is to  first setup a service that triggers the retirement in
> pkgdb and when this seems to work ask Infrastructure do disable retiring
> packages for regular users in pkgdb.
Works for me -- depending on when this goes live, we might be making the
retirement change in pkgdb2 instead of pkgdb1.  (We're trying to get pkgdb2
live in January).  (And by we I mean pingou who is doing all of the hard
work on pkgdb2 ;-)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.fedoraproject.org/pipermail/devel/attachments/20131127/a339282d/attachment.sig>

More information about the devel mailing list