On Wed, Sep 25, 2013 at 2:38 PM, Kevin Kofler wrote:
> Richard Shaw wrote:
> > 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 th
Richard Shaw wrote:
> 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.
Right.
> As to the o
On Mon, Sep 23, 2013 at 1:07 PM, Kevin Kofler 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 sam
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
After seeing many emails on packages that have not been properly
retired/depreciated I wanted to make sure I get this right.
Currently there is trustedqsl 1.13 and tqsllib 2.2 in Fedora. For whatever
reason these were developed seprately in the past even though they are
closely tied together and t
