Comment 15 for bug 1505670

Thank, Miriam, for having a look. I only became aware of your response now by accident.

I'm not sure I understand what you did and what your results were. It appears that you got the issue of an "uncaptured python exception" at least once "when you removed squid-deb-proxy"? I really don't know what you mean there. Then you list the output of /usr/share/squid-deb-proxy-client/apt-avahi-discover twice, unchanged, but apparently get an IPv4 result once and an IPv6 result on the next, identical invocation.

The problem with squid-deb-proxy is easy to trigger. All it needs is two or more responses to the avahi discovery in your LAN. See the initial report where it shows three different IP numbers. These days, I believe an IPv4 and IPv6 response from the same server is actually enough.

Frankly, we don't need more bug triage here, it's all been laid out forever, we've had a working patch for years. The patch is as far as I can tell correct in that it is not simply a workaround. I assume you haven't looked at the code. What needs to be done here is for @mvo to finally comment on whether or not this is the correct way to fix it or reject the patch (and come up with an alternative patch).

Truth be told, the state of this bug is disgusting and demotivating. Ubuntu used to be about making Debian polished and usable. How come we dropped the ball so badly on this awesome USP?