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

Reply via email to