While there is a curl bug here that older versions do not honor ipv6 addresses in no_proxy, there's no information here that explains why you think this caused a *regression* in autopkgtests. Tests attempting to use the http proxy to connect to ::1 will fail with or without adding ::1 to no_proxy. So how does having it listed in no_proxy cause a regression?
-- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1908136 Title: no_proxy=::1 is not honored by curl in Bionic and earlier versions Status in Auto Package Testing: New Status in curl package in Ubuntu: Fix Released Status in curl source package in Xenial: New Status in curl source package in Bionic: New Status in curl source package in Focal: Fix Released Bug description: Bionic: env no_proxy=::1 http_proxy=http://foo:8080 curl -v http://[::1]:80/bar.html * Could not resolve proxy: foo * Closing connection 0 curl: (5) Could not resolve proxy: foo Focal: $ env no_proxy=::1 http_proxy=http://foo:8080 curl -v http://[::1]:80/bar.html * Uses proxy env variable no_proxy == '::1' * Trying ::1:80... * TCP_NODELAY set * Immediate connect fail for ::1: Network is unreachable * Closing connection 0 curl: (7) Couldn't connect to server To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/1908136/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
