How to properly depreciate a package that will be provided by another (trustedqsl/tqsllib)

Richard Shaw hobbes1069 at
Mon Sep 23 18:38:24 UTC 2013

On Mon, Sep 23, 2013 at 1:07 PM, Kevin Kofler <kevin.kofler at>wrote:

> Richard Shaw wrote:
> > The question is, since a "tqsllib" package will still be produced, what
> is
> > the proper steps to replace the existing tqsllib and do I need
> > Obsolete/Provides? I don't think so because the package name is the same
> > but I wanted to be sure.
> * dist-git and pkgdb work on SRPMs, so you commit a dead.package and retire
> the package as normal (I think fedpkg retire will work fine even in this
> case), BUT
> * Obsoletes and Provides are NOT needed. Just make sure the new subpackage
> has an EVR higher than the previous standalone package.

Thanks for the clarification Kevin... On a related note, the guidelines say
I should only retire a package that's not released since the package can
not get removed from released versions, so in this case I'm thinking that
would be f20 and rawhide.

As to the order, I would think I need the new packages in stable before
retiring so we have a continuity of update path?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the devel mailing list