(retire nc6) never retired a package before

[Christopher]

Hi all,

I've never retired a package before, so I'm trying to figure out my way
through it for nc6.

Background:

  * nc was properly obsoleted by nmap-ncat, and retired (though, it hasn't
been removed from comps entirely)
  * nc6 should also be obsoleted by nmap-ncat with nc, but it never was.
Instead it was just orphaned, so I took it (before I fully understood the
situation).

What I'm wondering is:

Which branch should I retire this in, and work with nmap packager to add an
Obsoletes line for nc6? Just master/rawhide? Or all branches?

[Peter Robinson]

>  I've never retired a package before, so I'm trying to figure
> out my way
>  through it for nc6.
>
>  Background:
>
>    * nc was properly obsoleted by nmap-ncat, and retired (though, it hasn't
>  been removed from comps entirely)
>    * nc6 should also be obsoleted by nmap-ncat with nc, but it never was.
>  Instead it was just orphaned, so I took it (before I fully understood the
>  situation).
>
>  What I'm wondering is:
>
>  Which branch should I retire this in, and work with nmap packager to add an
>  Obsoletes line for nc6? Just master/rawhide? Or all branches? 
So you should add Provides, not just obsoletes to ensure a clean
upgrade between releases. Also ensure that any packages have their
dependencies to require the replacement, this just looks to be hadoop
and qt-virt-manager.

On branches, once a release is out you can't block a package, you can
push updates to other packages that obsolete/provide it so it's
replaced but because the f24 (as an example) is locked it'll always be
there, so you should just retire it in rawhide (master in the fedpkg
checkout) with a "fedpkg retire 'retirement message details'".

Peter

[Christopher]

On Mon, Jun 20, 2016 at 5:02 PM Peter Robinson <pbrobinson(a)gmail.com&gt; wrote:

>  > I've never retired a package before, so I'm trying to
> figure out my way
>  > through it for nc6.
>  >
>  > Background:
>  >
>  >   * nc was properly obsoleted by nmap-ncat, and retired (though, it
>  hasn't
>  > been removed from comps entirely)
>  >   * nc6 should also be obsoleted by nmap-ncat with nc, but it never was.
>  > Instead it was just orphaned, so I took it (before I fully understood the
>  > situation).
>  >
>  > What I'm wondering is:
>  >
>  > Which branch should I retire this in, and work with nmap packager to add
>  an
>  > Obsoletes line for nc6? Just master/rawhide? Or all branches?
>
>  So you should add Provides, not just obsoletes to ensure a clean
>  upgrade between releases. Also ensure that any packages have their
>  dependencies to require the replacement, this just looks to be hadoop
>  and qt-virt-manager.
>
>  
Thanks. I'll file a bug with nmap to add Provides/Obsoletes, since I'm not
a maintainer on that. I'm working on hadoop, and qt-virt-manager looks like
they've already addressed it.


>  On branches, once a release is out you can't block a package, you
> can
>  push updates to other packages that obsolete/provide it so it's
>  replaced but because the f24 (as an example) is locked it'll always be
>  there, so you should just retire it in rawhide (master in the fedpkg
>  checkout) with a "fedpkg retire 'retirement message details'".
>
>  
Okay, cool. I've retired the package in rawhide, then. Still need to submit
pull request to update comps.