Bug#1070334: libnet-frame-device-perl needs network access during build

Étienne Mollier emollier at debian.org
Sat May 4 16:19:52 BST 2024


Control: tags -1 + patch

Étienne Mollier, on 2024-05-03:
> Has someone an idea of better approach?

Answering to myself, the test suite does not actually attempt to
access the Internet, but it does attempt to access the device on
the build machine that can route by default to 1.1.1.1.  This is
not because it is a Cloudflare DNS, but merely because it is the
first usable ipv4 available at hand.  Especially in chroot-mode
unshare, there are no device leading to Internet exposed, thus
no device able to route to 1.1.1.1 with the default object
instanciation routine.

It turns out that the class can be told to construct objects
that refer to the loopback interface by asking for routes to the
loopback network (127/8 in ipv4, ::1/64 in ipv6).  I prepared a
patch in this direction and consider uploading soon.

Have a nice day,  :)
-- 
  .''`.  Étienne Mollier <emollier at debian.org>
 : :' :  pgp: 8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
 `. `'   sent from /dev/pts/2, please excuse my verbosity
   `-    on air: Allman Brothers Band - Statesboro Blues
-------------- next part --------------
A non-text attachment was scrubbed...
Name: loopback-test.patch
Type: text/x-diff
Size: 1706 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-perl-maintainers/attachments/20240504/ae305b0e/attachment.patch>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-perl-maintainers/attachments/20240504/ae305b0e/attachment.sig>


More information about the pkg-perl-maintainers mailing list