Your message dated Tue, 9 Nov 2021 11:28:07 +0100
with message-id <[email protected]>
and subject line Re: Bug#987695: dig/kdig alternatives
has caused the Debian Bug report #932087,
regarding please use update-alternative for host and dig commands
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
932087: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932087
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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.
--- End Message ---
--- Begin Message ---
There seems to be an agreement that it's not a good idea to use
update-alternatives in this particular case of a debugging tool so I'm
closing this.
Cheers,
Jakub
On Fri, 30 Apr 2021 20:05:48 +0200 =?utf-8?Q?Ond=C5=99ej_Sur=C3=BD?= wrote:
> Yes, this has been discussed before and rejected for this exact
reason. I am not going to implement this.
>
> Ondrej
> --
> Ondřej Surý (He/Him)
>
> > On 30. 4. 2021, at 18:03, Chris Hofstaedtler wrote:
> >
> > Hello,
> >
> > please do not use alternatives for dig/kdig. These tools are
> > *debugging* tools, and while they are mostly compatible, they
> > diverge in certain ways, including various default settings.
> >
> > kdig also does not print its version number or identifies itself as
> > kdig.
> >
> > Its extremely important when debugging DNS problems or anything
> > else, that the tools one is using, are exactly the tools one expects
> > to be using, and not "transparently" something else.
> >
> > Please reconsider.
> >
> > Thanks,
> > Chris
> >
>
>
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
