Bug#765327: lintian fails if the machine has a link-local IPv6 nameserver configured

Niels Thykier niels at thykier.net
Thu Oct 16 14:42:20 UTC 2014


Control: reassign -1 libnet-dns-perl


On 2014-10-14 09:41, Philipp Kern wrote:
> Package: libnet-dns-perl,lintian
> Severity: normal
> 
> This is likely a bug in libnet-dns-perl but I wonder if there are network
> accesses from lintian.
> 

Hi,

Thanks for filing the bug.

This needs to be resolved in libnet-dns-perl (and possibly also
libemail-valid-perl).  IRT your concern about network access. It does
look like Net::DNS::Resolver will attempt to resolve some names during
initialisation, but Lintian does not use this feature of Email::Valid to
have it check the DNS name of the email.

> % lintian ./openclonk_5.5.1-1_amd64.changes
> warning: Cannot load check "binaries"
> unresolvable name: fe80::4ee6:76ff:fe51:ae30%eth0 at /usr/share/perl5/Email/Valid.pm line 41.
> Compilation failed in require at /usr/share/perl5/Lintian/Check.pm line 27.
> BEGIN failed--compilation aborted at /usr/share/perl5/Lintian/Check.pm line 27.
> Compilation failed in require at /usr/share/lintian/checks/binaries.pm line 30.
> BEGIN failed--compilation aborted at /usr/share/lintian/checks/binaries.pm line 30.
> Compilation failed in require at /usr/share/perl5/Lintian/CheckScript.pm line 253.
> 
> [...]
> 
> The message lintian displays is rather awkward: for a runtime error (runtime
> configuration not parsable) one gets compilation failed. But I guess the load
> is already guarded, hence the warning?
> 
> [...]
> 
> 

Honesty, I doubt there is much we can do about it on the Lintian side.
What happens is that Email::Valid will attempt (in "global/package"
scope) to initialise an instance of Net::DNS::Resolver.  Initialisation
fails and causes the module load to fail.
  This is a bit silly of course, since Email::Valid will never need that
object (when used by Lintian).

~Niels






More information about the pkg-perl-maintainers mailing list