Package name conflict with retired package

Toshio Kuratomi a.badger at
Thu Sep 19 23:47:07 UTC 2013

On Thu, Sep 19, 2013 at 3:35 PM, Sandro Mani <manisandro at> wrote:
>> We have no ability to rename a package in koji. im not opposed to
>> reusing the name. Just need some way to ensure its very clear the old
>> and new are different. Likely need to add a conflicts with the old one.
>> hopefully versions allow for upgrade okay, if not an epoch will need to
>> be added.
>> Dennis
> The last build of the "old" was for f17. The "new" avl is only available for
> f19 and newer. Should I add a
> Conflicts: avl < 3.32-1
> regardless? The version numbers allow for upgrades (i.e. old avl stopped at
> 0.3.5, new avl starts at 3.32).
I think so and a comment in the spec file about why it's there.

> One question which remains though is what to do with the EPEL branhces. Just
> keep them retired?
yeah, I'd leave them orphaned/retired in EPEL if there's no intention
to maintain the new package there at the moment.  It would be nice to
let people know that the old EPEL packages are unmaintained and that
the bugzilla/pkgdb description/etc are no longer for that package but
I can't figure out a way to do that other than sending a message to
the epel mailing list and hope anyone who cares reads that.


More information about the devel mailing list