<div dir="ltr">On Mon, Sep 23, 2013 at 1:07 PM, Kevin Kofler <span dir="ltr"><<a href="mailto:kevin.kofler@chello.at" target="_blank">kevin.kofler@chello.at</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">Richard Shaw wrote:<br>
> The question is, since a "tqsllib" package will still be produced, what is<br>
> the proper steps to replace the existing tqsllib and do I need<br>
> Obsolete/Provides? I don't think so because the package name is the same<br>
> but I wanted to be sure.<br>
<br>
</div>* dist-git and pkgdb work on SRPMs, so you commit a dead.package and retire<br>
the package as normal (I think fedpkg retire will work fine even in this<br>
case), BUT<br>
* Obsoletes and Provides are NOT needed. Just make sure the new subpackage<br>
has an EVR higher than the previous standalone package.<br></blockquote><div><br></div><div>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.</div>
<div><br></div><div>As to the order, I would think I need the new packages in stable before retiring so we have a continuity of update path? </div><div><br></div><div>Thanks,</div><div>Richard</div></div></div></div>