A while back I retired rubygem-qpid after going through the package rename process to make it rubygem-qpid_messaging. The newer package provides rubygem(qpid).
For some reason, over the past 2 weeks, I've started getting automated emails saying that rubygem-qpid has a dependency failure. And today I came in to find a Fedora 20 email listing packages that fail to build and it includes rubygem-qpid, even though that package is retired.
What do I need to do to fully retire the package? It's marked as retired in the package database, so I'm not sure what else I can do at this point...
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 07/29/2013 08:57 AM, Darryl L. Pierce wrote:
A while back I retired rubygem-qpid after going through the package rename process to make it rubygem-qpid_messaging. The newer package provides rubygem(qpid).
For some reason, over the past 2 weeks, I've started getting automated emails saying that rubygem-qpid has a dependency failure. And today I came in to find a Fedora 20 email listing packages that fail to build and it includes rubygem-qpid, even though that package is retired.
What do I need to do to fully retire the package? It's marked as retired in the package database, so I'm not sure what else I can do at this point...
It needs to also be blocked if it's not meant to be included in future releases. See https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
On Mon, Jul 29, 2013 at 09:09:41AM -0400, Stephen Gallagher wrote:
On 07/29/2013 08:57 AM, Darryl L. Pierce wrote:
A while back I retired rubygem-qpid after going through the package rename process to make it rubygem-qpid_messaging. The newer package provides rubygem(qpid).
For some reason, over the past 2 weeks, I've started getting automated emails saying that rubygem-qpid has a dependency failure. And today I came in to find a Fedora 20 email listing packages that fail to build and it includes rubygem-qpid, even though that package is retired.
What do I need to do to fully retire the package? It's marked as retired in the package database, so I'm not sure what else I can do at this point...
It needs to also be blocked if it's not meant to be included in future releases. See https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
I don't see anything that specifically says block there, but I did file a ticket to ask someone to check that no backend pieces are still trying to build rubygem-qpid.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 07/29/2013 09:18 AM, Darryl L. Pierce wrote:
On Mon, Jul 29, 2013 at 09:09:41AM -0400, Stephen Gallagher wrote:
On 07/29/2013 08:57 AM, Darryl L. Pierce wrote:
A while back I retired rubygem-qpid after going through the package rename process to make it rubygem-qpid_messaging. The newer package provides rubygem(qpid).
For some reason, over the past 2 weeks, I've started getting automated emails saying that rubygem-qpid has a dependency failure. And today I came in to find a Fedora 20 email listing packages that fail to build and it includes rubygem-qpid, even though that package is retired.
What do I need to do to fully retire the package? It's marked as retired in the package database, so I'm not sure what else I can do at this point...
It needs to also be blocked if it's not meant to be included in future releases. See https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
I don't see anything that specifically says block there, but I did file a ticket to ask someone to check that no backend pieces are still trying to build rubygem-qpid.
8. File a ticket for rel-eng (component koji) asking the package (or packages if there are many) to be blocked from the appropriate collections in which it is retired. You can mention several packages in one ticket.
packaging@lists.fedoraproject.org
-
Darryl L. Pierce -
Stephen Gallagher