Bug#931355: apt: unresolvable hostnames are wicked
On Tue, Jul 09, 2019 at 10:43:20AM +0200, Julian Andres Klode wrote:
> On Wed, Jul 03, 2019 at 01:04:28AM +0200, Thorsten Glaser wrote:
> > Package: apt
> > Version: 1.8.2
> > Severity: wishlist
> >
> > W: Failed to fetch http://mirror.lan.tarent.de/debian/dists/sid/InRelease Something wicked happened resolving 'mirror.lan.tarent.de:http' (-5 - No address associated with hostname)
> >
> > This is because I’m currently not in the VPN to $dayjob,
> > but unresolvable hostnames are not so special that they
> > are “wicked”, I think… perhaps, for them, a toned-down
> > warning is a bit more appropriate?
>
> Of course they're not, which is why we print something like
>
> E: Failed to fetch http://fdsfdijdfsds.exsapl/dodod Could not resolve 'fdsfdijdfsds.exsapl'
>
> when getaddrinfo() returns EAI_NONAME or EAI_SERVICE.
>
[...]
> If you can figure out what it returned, please tell us.
Nevermind. It returned EAI_NODATA, "this host exists but has no address". Any other
cases we should consider as "Could not resolve"?
--
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer i speak de, en
Reply to: