OK. So when will this be fixed? This bug has been open for a year and 3 months already. It was reported in the previous LTS and is still present in the current LTS. That makes this bug over 2 years old.
Is having a crashing proxy server in two LTS releases acceptable? Is it acceptable especially considering there is a fix and that's to simply update the package to something more current? I notice this isn't even fixed for the next release, Quantal since the fix is only in squid 3.2 and Quantal is still reporting as using 3.1.20. Or was the fix for this backported from the upstream's 3.2 release to Quantal's 3.1.20 release? I don't see anything in http://bazaar.launchpad.net/~ubuntu- branches/ubuntu/quantal/squid3/quantal/files/head:/debian/patches/ (assuming that's the correct place to look) that indicates a patch for this issue. I guess once again, I will be rolling my own packages here again to fix what my distro won't. ~sigh~ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/496886 Title: Squid crashes with "assertion failed" authenticateUserAuthenticated To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/496886/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
