[Bug 780593] Re: Something wicked happened resolving IPv6 address

2013-10-17 Thread James Page
** Changed in: squid-deb-proxy (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid-deb-proxy in Ubuntu. https://bugs.launchpad.net/bugs/780593 Title: Something wicked happened

[Bug 780593] Re: Something wicked happened resolving IPv6 address

2013-10-17 Thread James Page
** Changed in: squid-deb-proxy (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/780593 Title: Something wicked happened resolving IPv6 address To

[Bug 780593] Re: Something wicked happened resolving IPv6 address

2011-08-11 Thread Launchpad Bug Tracker
** Changed in: squid-deb-proxy (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/780593 Title: Something wicked happened resolving IPv6 address To manage

[Bug 780593] Re: Something wicked happened resolving IPv6 address

2011-06-23 Thread Thomas Mashos
While that's unfortunate to require everyone to manually install the squid-deb-proxy-client from natty, it would appear that since this is fixed in the code that this bug can be closed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 780593] Re: Something wicked happened resolving IPv6 address

2011-06-17 Thread Andrew Simpson
The bug was in the squid-deb-proxy-client which was (hopefully) fixed in Natty, but not patched in Maverick. Upgrading to the Natty squid-deb-proxy-client should fix your problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 780593] Re: Something wicked happened resolving IPv6 address

2011-05-10 Thread Thomas Mashos
Should also note that squid-deb-proxy-client is still from 10.10. I didn't update that as the other bug report said it was fixed in squid- deb-proxy. If installing the newer squid-deb-proxy is what is required to resolve this I can certainly test that, but it's more of an issue for users as they