Your message dated Fri, 28 Mar 2025 18:52:38 +0000
with message-id <e1tyeoo-001nqi...@fasolo.debian.org>
and subject line Bug#1101459: fixed in auto-apt-proxy 16.5
has caused the Debian Bug report #1101459,
regarding auto-apt-proxy: Breaks apt-listbugs when avahi-browse is installed
but no proxy are present
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 ow...@bugs.debian.org
immediately.)
--
1101459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1101459
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: auto-apt-proxy
Version: 16.4
Severity: serious
Justification: breaks other software with no information about the reason
Hi,
A few days ago, I upgraded my system (sid).
auto-apt-proxy has been installed due to dependencies (no manual install).
Since the upgrade, apt-lsitbugs was always failing during package installation
with the following message:
====
apt install ... # or apt upgrade
[...]
Retrieving bug reports... 0% Fail
Error retrieving bug reports from the server with the following error message:
E: connect to ssl proxy failed with status 405 Method Not Allowed
It could be because your network is down, or because of broken proxy servers,
or the BTS server itself is down. Check network configuration and try again
Retry downloading bug information? [Y/n]
====
Not using proxy, I've been thinking of a problem on the bugs.debian.org
server.
As the problem was persistant, and not seeing bug reported to apt-listbugs, I
digged a bit on my system.
I discovered the auto-apt-proxy and saw (thanks to dpkg log) it has been
installed with my last upgrade.
Purging the package solved the issue.
Then, I reinstalled it and executed it with "bash -x auto-apt-proxy".
Several things in the traces hit me:
1) the "hit -oDebug::acquire::http=1 -o Acquire::http::Proxy::::1=DIRECT
'http://[::1]:8000'"
=> not sure that IPv6 address with '::' in it will works correctly with the
Acquire::http::Proxy::server notation...
(but I did not test it)
2) the end of the trace:
====
[...]
++ avahi-browse --terminate --no-db-lookup --resolve --parsable _apt_proxy._tcp
++ awk -F ';' '/^=;/ { print($7, $8, $9); exit}'
+ data=
++ echo ''
++ awk '{print($2)}'
+ ip=
++ echo ''
++ awk '{print($3)}'
+ port=
+ '[' -n '' ']'
++ proxy_url '' ''
++ case "$1" in
++ echo http://:
+ proxy=http://:
++ LANG=C.UTF-8
++ hit -o Acquire::http::Proxy::=DIRECT http://:
++ timeout 5 /usr/lib/apt/apt-helper -o Acquire::http::Proxy=DIRECT -o
Acquire::Retries=0 download-file -o Acquire::http::Proxy::=DIRECT http://:
/tmp/.auto-apt-proxy-2001/output
++ true
+ check='Err:1 http://:
Undetermined Error
E: Failed to fetch http:/ Undetermined Error
E: Download Failed'
+ echo 'Err:1 http://:
Undetermined Error
E: Failed to fetch http:/ Undetermined Error
E: Download Failed'
+ grep -q '111: Connection refused\|101: Network is unreachable'
+ echo http://:
+ return 0
+ cat /tmp/.auto-apt-proxy-2001/cache
http://:
+ cleanup
+ rm -f /tmp/.auto-apt-proxy-2001/output
====
It seems that when avahi-browse did not find anything, proxy_url is called with
two empty arguments
and generates a wrong http://: proxy url
And, even if errors are detected latter, this proxy is returned by
auto-apt-proxy
I do not know why "apt update" works with this proxy, but apt-listbugs does not.
Note that I have "https" apt sources, so I do not initially think about a local
[network] config problem.
I raised the severity of this bug because:
1) I do not explicitely ask the installation of auto-apt-proxy
2) the error message does not point to auto-apt-proxy (it took me some times to
understand the source of the problem)
3) I think I've a classical environment (no proxy but avahi-browse installed)
Regards
Vincent
-- System Information:
Debian Release: trixie/sid
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500,
'oldstable-updates'), (500, 'oldstable-security'), (500, 'unstable'), (500,
'testing'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armel
Kernel: Linux 6.12.17-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages auto-apt-proxy depends on:
ii apt 2.9.33
Versions of packages auto-apt-proxy recommends:
ii busybox-static [busybox] 1:1.37.0-4
ii iproute2 6.13.0-1
Versions of packages auto-apt-proxy suggests:
ii avahi-utils 0.8-16
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: auto-apt-proxy
Source-Version: 16.5
Done: Antonio Terceiro <terce...@debian.org>
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 1101...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Antonio Terceiro <terce...@debian.org> (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 ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Fri, 28 Mar 2025 14:53:06 -0300
Source: auto-apt-proxy
Architecture: source
Version: 16.5
Distribution: unstable
Urgency: medium
Maintainer: Antonio Terceiro <terce...@debian.org>
Changed-By: Antonio Terceiro <terce...@debian.org>
Closes: 1101459
Changes:
auto-apt-proxy (16.5) unstable; urgency=medium
.
* avahi: fix detection when no proxy is available (Closes: #1101459)
Checksums-Sha1:
bf8d393181cb5614b319c0cc858abcca5f65c2d8 1795 auto-apt-proxy_16.5.dsc
842a33488e15f718135138816b9c91478b6d1ec2 20584 auto-apt-proxy_16.5.tar.xz
826e709e514ce7eacf9fa8d2ee454a1ef1243214 7156
auto-apt-proxy_16.5_source.buildinfo
Checksums-Sha256:
d5b825b6549eeddcd5f88d25f289dfdef3b2bc43aab6270360da056c4fdc5db8 1795
auto-apt-proxy_16.5.dsc
beb019913cae76e1b06b02b8dce16dc057f891acfa1f29b36932401f0afe073b 20584
auto-apt-proxy_16.5.tar.xz
45d6fad3c5dfa08a2d632958e56504bd4bb85d859947ff0ed4aa6f3d30825f09 7156
auto-apt-proxy_16.5_source.buildinfo
Files:
d6956d18cf7974b7ddc4a7df32461f6a 1795 net optional auto-apt-proxy_16.5.dsc
f2cfdaaf19a53a20ed5699abdbd4cf26 20584 net optional auto-apt-proxy_16.5.tar.xz
d644372a3fc901aea8b35e6b9a7f49a5 7156 net optional
auto-apt-proxy_16.5_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEst7mYDbECCn80PEM/A2xu81GC94FAmfm6VgACgkQ/A2xu81G
C95Jzw/+IPHcTGOm1wiXLEJzDZGsKvKxAR2FUP2yiwR2EUjkmuE+NqtOw6k/rHIW
MWgujRruXJAKwzqKBZLXYg601EkqSHCFKgh8QVTOt32evkBXXaJzcJEhvTaEvnCM
XsM+XY6C7MwiHUaGD3PpNY7snAiVbsW3HgpPhMYDjM7/lTnvVoQ+JgvB1CGpyKar
EQFUSiZxThhqHP7aEBMNBNPbnnRmIMEjyTOpU/mlvigs4goRx8UxrsGO0vsonv/4
hYTDRp+0stR38NZtc7RaEpaMl07GwzuEyaB32ObGWN1QhJQI3qJ8KItadlVRsl/y
EwB3LW/1C6pAHupDt5rYNLtox5IrLavdt7aFuwUg020KMGeCaCivGnwgRxxtkGx/
PazuUA6JTNLfGcoJhAwRlxHy96yxh+GIZENm8jQ0CjZPDhi6B7n9GeiAfMymWWVJ
sOX0416p0RXcJ3NFjMsvQbHlAfux7IR4IW2sWnw/FFMDiI4VlVtSTrkRoQP6bD6O
Qyv/p4aJPbz+CDg55kARhph1QCEHpiGSAVo6wE5MmKtmpH33W8mwR4bQBvIHSFvq
vM/GB6uYWPwnhtrQP41mEf3dCz8i7xcpzBSRpZSq/u6X12ntwbUVtcMqDitK3PaQ
ISCBVZsRa1gNCfDZ8yFOBdufYJt6L5HWQWxkLwLDgBrjqgWLVQU=
=QC0y
-----END PGP SIGNATURE-----
pgpjiAUfoC7Ez.pgp
Description: PGP signature
--- End Message ---
