On 26 Sep 2017 6:37 pm, "Chris Adams" <linux@cmadams.net> wrote:
Once upon a time, James Hogarth <james.hogarth@gmail.com> said:
> You're correct that this isn't covering BR situations but I didn't want the
> scope of this to blow out to the less reasonable.
>
> First phase let's get the package off systems where it's not absolutely
> required or requested by the user...
>
> Then BR can be cleaned up in the background without affecting user systems.

Packages that BR net-tools (or its commands) may be expecting it to be
installed without explicitly specifying an install dependency, and just
happen to work because net-tools is pulled in by other deps.  The BRs
should be fixed as part of this change, or there may be unexpected
breakage.


That doesn't make sense. 

There is only net-tools on a system if a requires/recommends pulls it in or a user installs it. 

The presence of net-tools in a BR will not cause it to be an R for any install situations ...

If I have missed anything you're aware of that requires net-tools please add it to the tracking bug :)