Your message dated Fri, 20 Jun 2025 14:35:14 +0000
with message-id <[email protected]>
and subject line Bug#1107997: fixed in auto-apt-proxy 16.8
has caused the Debian Bug report #1107997,
regarding auto-apt-proxy: wrongly parses the gateway
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1107997: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1107997
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: auto-apt-proxy
Version: 11
Tags: patch
Severity: minor
Hi,
I noticed that auto-apt-proxy sometimes gets the parsing of the gateway
wrong. Consider the following routing table (from an incus container):
default via 192.168.77.1 dev host0 proto dhcp src 192.168.77.179 metric 1024
default dev host0 proto static scope link metric 2048
The parsing code is
ip route | awk '/default/ { print($3) }'
and what you get here is "192.168.77.1" and "host0". That host0 is not a
gateway but a network interface.
Consider using:
ip route | awk '/^default via / { print($3) }'
Now you may ask how one spots this kind of problem. Turns out that
auto-apt-proxy in bullseye works the same as the sid version except that
it doesn not cache its results. Hence it resolves host0 using LLMNR and
therefore takes five seconds per http request making autopkgtest time
out the testbed setup if you end up installing more than 1000 packages.
Anyway, can we fix the gateway parsing?
Helmut
diff --minimal -Nru auto-apt-proxy-16.7/auto-apt-proxy
auto-apt-proxy-16.7+nmu1/auto-apt-proxy
--- auto-apt-proxy-16.7/auto-apt-proxy 2025-05-19 04:20:27.000000000 +0200
+++ auto-apt-proxy-16.7+nmu1/auto-apt-proxy 2025-06-18 21:28:18.000000000
+0200
@@ -254,7 +254,7 @@
find_gateway() {
local gateway
- $ip "$@" route | awk '/default/ { print($3) }'
+ $ip "$@" route | awk '/^default via / { print($3) }'
}
resolve_getent() {
diff --minimal -Nru auto-apt-proxy-16.7/debian/changelog
auto-apt-proxy-16.7+nmu1/debian/changelog
--- auto-apt-proxy-16.7/debian/changelog 2025-05-19 04:20:27.000000000
+0200
+++ auto-apt-proxy-16.7+nmu1/debian/changelog 2025-06-18 21:28:19.000000000
+0200
@@ -1,3 +1,10 @@
+auto-apt-proxy (16.7+nmu1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix default route parsing. (Closes: #-1)
+
+ -- Helmut Grohne <[email protected]> Wed, 18 Jun 2025 21:28:19 +0200
+
auto-apt-proxy (16.7) unstable; urgency=medium
* Disable logging by default.
--- End Message ---
--- Begin Message ---
Source: auto-apt-proxy
Source-Version: 16.8
Done: Antonio Terceiro <[email protected]>
We believe that the bug you reported is fixed in the latest version of
auto-apt-proxy, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Antonio Terceiro <[email protected]> (supplier of updated auto-apt-proxy
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Fri, 20 Jun 2025 10:34:06 -0300
Source: auto-apt-proxy
Architecture: source
Version: 16.8
Distribution: unstable
Urgency: medium
Maintainer: Antonio Terceiro <[email protected]>
Changed-By: Antonio Terceiro <[email protected]>
Closes: 1107997
Changes:
auto-apt-proxy (16.8) unstable; urgency=medium
.
[ Antonio Terceiro ]
* Include timestamp in debug logs
* Fix typo when printing debug information for IPv6 gateway
* Log before trying to resolve apt-proxy
* Disambiguate ip the tool from ip as an address
* Lazy load addresses to be checked for a proxy
* Try options that require resolving names last
.
[ Helmut Grohne ]
* Make parsing the default gateway more strict (Closes: #1107997)
Checksums-Sha1:
92aab1b3e8667336f202430d2da0f28a59b22d40 1803 auto-apt-proxy_16.8.dsc
ff6bc3d7b3907d4d15821bbbfe73892ca7b036f3 21604 auto-apt-proxy_16.8.tar.xz
e846e422612abf4789c70d1e2b7d02a7527b8272 6219
auto-apt-proxy_16.8_source.buildinfo
Checksums-Sha256:
22aeda4b01d53a3c8889690615915c826ff647128c1adb71f62958a87bedcbb0 1803
auto-apt-proxy_16.8.dsc
7d9382f6db750966919bcfc0b555733db6bcd19f0337d4526c0c472f15eeff6b 21604
auto-apt-proxy_16.8.tar.xz
dfb048c0369ec4ebee482a7ede0d98d707f6b4347514e3c387d835dadd755039 6219
auto-apt-proxy_16.8_source.buildinfo
Files:
4fd3f907430c557ca93ed2326ffe7de4 1803 net optional auto-apt-proxy_16.8.dsc
bde82c7a82005c29851492582a9e0cdb 21604 net optional auto-apt-proxy_16.8.tar.xz
d6df41915810f641ed74ea4a5b5b984f 6219 net optional
auto-apt-proxy_16.8_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEst7mYDbECCn80PEM/A2xu81GC94FAmhVb0EACgkQ/A2xu81G
C96/SQ/9ELGzo5FmFi5TAC99tk4IH7St9Ya/DU/i9XUWGnncFiXQodNIbY5qYIYU
mDTAucvzbZr0YNa/G+ubENMUZQdlAzylQcbfv/bVY/OgD6U1uNupXb6nmVnZvTKB
PzzzKc5W+YhBgykLAXJIiaesV7lv5TqV5NWm/Sk8JiNtOdnqMMzySalGHin0Nkhq
OWR7UKqKLBa9xhNYkLe1Lj4nEQrCv/qh2ql4cn9m+jd8pyWgeMpLh3NG06lGUFnW
WEOlNGFYbo6hpmmxhMA6FQNvhcyJAExOEVDhzucJW8xKTm3RAQU0NN+At3ecFfVe
ZWgy4zvYhOBFFTCHVZzoSrleK5RYOGRg7EvEgwnInSBSdw/V0Mx9V7IKuVsvrVvi
mbkTGy3HIwyuL2Guf59q1oyHPI+jZIozCFMsijdutvzsGbnUVkMr818qzl8ahsj2
kzuL1NAc2RxdP1l+MZbGl/P8vsnl375U3W9wechZ9lrbo4fC4L1TqcQlMOE9Ga3z
fFEHktJV7gibQMVG39LULRRflgpBiX/thcIHtn4fa2X7o6F33V+v0eZuaBzx1G14
b6wWc7qiv4j0b96np1VMAR3PbM5dGkFGycVxLncM4/U1gC8OJ9zI0DnvxlIWh2Ix
rwMuA/4F5JDsk7j9iWp2XacwUb2CCcmMkPjN0swYxT/CZ9ipv9M=
=JblB
-----END PGP SIGNATURE-----
pgpQ71N3OWR4v.pgp
Description: PGP signature
--- End Message ---
