Ubuntu
squid-deb-proxy package

  1. Bug #1505670
  2. Comment #19

Comment 19 for bug 1505670

Revision history for this message
Rolf Leggewie (r0lf) wrote : Re: "uncaptured python exception"

Christian, thank you for stepping in. It seems you finally got the ball rolling here where I was unsuccessful in a good half dozen attempts in #ubuntu-devel and other venues. That's the good news I suppose.

I maintain my assessment of the situation of Ubuntu as stated in #16. I've been with Ubuntu since breezy or so. I've been very active in bug triage, I know the processes. I'm happy to back up my rant with facts, if you want to hear.

I also maintain that this bug ticket and the problem was clearly described including a test case in #7 and a clear analysis of where the problem is IN THE CODE right in #1. You don't need more bug triage at that point. You need a dev to look at the code and that did not happen, no matter the effort, here and elsewhere. I believe I even tried to get the patch sponsored but nobody dared touching mvo's stuff without an ACK.

I'm not sure, but it seems that both you and Miriam mistakenly assume that this bug can be triggered by some configuration on the computer where squid-deb-proxy-CLIENT is installed. As stated in #7 "this problem occurs whenever there is more than one host/IP discovered via avahi." in other words, a certain state of affairs with regards to the LAN (plus VPNs) is needed.