Package: knot-host Version: 2.7.6-2 Severity: normal I am on Buster 10.0.
The knot-host package provides the 'host' command, or at least so says the package's own description. However, bug #741645 for knot-dnsutils (which was also applied to knot-host) was submitted a couple years ago about conflicts with the 'host', 'dig' and 'nsupdate' commands that are provided by the dnsutils and bind9-host packages. That bug concluded with removing the conflicting commands from the knot packages with the mention that update-alternatives seems the better option, which I agree is a reasonable solution. Problem is the knot-host and knot-dnsutils packages never actually had any update-alternatives configuration added to them. They therefore no longer provide the 'host', 'dig', or 'nsupdate' commands that their package descriptions claim they do, at least not under those specific command names. I'm using these packages to provide those commands. The change didn't impact me until Debian Buster (Stretch's version didn't have this change applied), so once I upgraded dists I noticed, otherwise I would've commented on the earlier bug report and change considerably sooner. Basically, the knot-host and knot-dnsutils packages should provide update-alternatives functionality, and that is the purpose of this bug report, which should be applied to both packages. Through this method they would provide the 'host', 'dig' and 'nsupdate' commands they previously did. Yes I can set that up manually, but I shouldn't have to. These packages should have the alternatives functionality included. Thank you.
