[Bug 1448149] Re: Squid 3.3.8 incompatible with squidGuard 1.5-4

2015-10-26 Thread Deadwing
Here we are, 6 months later, and nothing has changed. 15.10 ships with the same incompatible Squid 3.3.8 and squidGuard 1.5-4. Unbelievable. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bu

[Bug 1448149] Re: Squid 3.3.8 incompatible with squidGuard 1.5-4

2015-05-26 Thread Robie Basak
As I said, I see no issue with updating the squidguard package 15.04 with a reversion of the patch I mentioned above, if as I understand the package is broken in 15.04 today and reverting the patch does actually fix the issue. Someone just needs to check this works, perform SRU verification, etc.

[Bug 1448149] Re: Squid 3.3.8 incompatible with squidGuard 1.5-4

2015-05-22 Thread Deadwing
Well, either squid has to move up to 3.4+ which you said is a non- starter, or squidGuard has to move back down to 1.5-2 which the Debian guys aren't likely to do. So that leaves us nowhere. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed

[Bug 1448149] Re: Squid 3.3.8 incompatible with squidGuard 1.5-4

2015-05-22 Thread Robie Basak
If this can be fixed as I asked in comment #3, and the squidguard package is completely broken otherwise, then an update to 15.04 would be fine. Someone just needs to check this works, perform SRU verification, etc. We should also look to add a dep8 test to squidguard to verify it works against th

[Bug 1448149] Re: Squid 3.3.8 incompatible with squidGuard 1.5-4

2015-05-22 Thread Deadwing
Is there going to be some resolution to this or will we have to wait until 15.10?? Frankly, I find it bizarre that they're packaging an ancient version of squid3 with a bleeding-edge version of squidGuard. I would think that using Ubuntu Server as a web proxy would be a fairly common thing, and i

[Bug 1448149] Re: Squid 3.3.8 incompatible with squidGuard 1.5-4

2015-05-01 Thread Robie Basak
Status is: squid3: Wishlist item to move to >= 3.4.0 in Vivid+1; no bug in Vivid. squidguard: "bug" in Vivid makes package unusable; no bug in Vivid+1 once squid3 is updated there. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the b

[Bug 1448149] Re: Squid 3.3.8 incompatible with squidGuard 1.5-4

2015-05-01 Thread Robie Basak
We can update squid3 to >= 3.4.0 in Vivid+1, but Vivid will need to stay on what it is since we can't make a backwards-incompatible change to it after release. To fix Vivid, can we revert the change squidguard that bumped syntax to >= 3.4.0? Do we just need to revert the one commit (http://anonscm.

[Bug 1448149] Re: Squid 3.3.8 incompatible with squidGuard 1.5-4

2015-04-30 Thread Robie Basak
** Tags added: upgrade-software-version ** Changed in: squid3 (Ubuntu) Status: New => Triaged ** Changed in: squid3 (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu.

[Bug 1448149] Re: Squid 3.3.8 incompatible with squidGuard 1.5-4

2015-04-25 Thread Deadwing
I emailed the maintainer and received this reply: > Can you please confirm that the squidGuard 1.5-4 will or won't work with > the shipping squid 3.3.8? This is right. The problem was, that squid3 have changed its redirector protocol several times. Until squid3 3.3.x older protocols were allowed.

[Bug 1448149] Re: Squid 3.3.8 incompatible with squidGuard 1.5-4

2015-04-24 Thread Deadwing
I should note that 14.10 shipped with squid 3.3.8 and squidGuard 1.5-2. 15.04 ships with squid 3.3.8 but squidGuard 1.5-4. The 1.5-4 changelog shows they made some changes to support squid 3.4 and how that was the new base version. No wonder 1.5-4 doesn't work with 3.3.8. >From Launchpad: squid