On 16/09/2026 1:12 am, Vincent Lefevre wrote:
On 2026-09-16 00:14:12 +0700, Max Nikulin wrote:
To my taste your description of the issue is excessively generic.
Personally I prefer more specific scenarios like
Sometimes I am getting obscure errors like
[example chosen to avoid details on disabled IPv6]
wget http://42.be
--2026-09-08 19:32:28-- http://42.be/
Resolving 42.be (42.be)... 2001:470:1f15:29a::1
Connecting to 42.be (42.be)|2001:470:1f15:29a::1|:80... failed: Network is
unreachable.
[...] etc.
I don't understand what you mean. 42.be only has an IPv6 address,
and there is no SERVFAIL with it.
I was trying to avoid "failed: Address family not supported by protocol"
when IPv6 is disabled and the command above is the only example I have
found in this thread. Of course, it should be a host having both IPv4
and IPv6 addresses.
My point is that, reporting a bug, you should avoid non-essential steps
to reproduce it. More generic configuration that is closer to defaults
means that the scope of the issue is wider. It require less efforts to
try and to create debug environment. In this thread you see that mention
of disabled IPv6 may insult people. Reaction of developers might be similar.
Since error messages are different, it is better to describe primary
scenario with default IPv6 configuration (local addresses, no global
routing). The case with disabled IPv6 might be added later, saying that
it does not prevent attempt of connections using IPv6 addresses to hosts
having IPv4 addresses.
Your bug report lacks timestamps that proof that partial failure is
treated as success while the setting to quickly expunge negative results
from the cache is respected.
When possible, use standard tools like getent instead of custom programs
or scripts.
You may use this thread to figure out what kind of confusion and
objections may cause your bug report.
