enterprise-support team mailing list archive

[Robie Basak <1448149@xxxxxxxxxxxxxxxxxx>]

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.debian.org/cgit/collab-
maint/squidguard.git/commit/?id=19e5ee293c04c605eb927d45688d2f0583cf9680)
or is there something else necessary too?

** Also affects: squidguard (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: squidguard (Ubuntu)
       Status: New => Triaged

** Changed in: squidguard (Ubuntu)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Ubuntu
Server/Client Support Team, which is subscribed to squid3 in Ubuntu.
Matching subscriptions: Ubuntu Server/Client Support Team
https://bugs.launchpad.net/bugs/1448149

Title:
  Squid 3.3.8 incompatible with squidGuard 1.5-4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1448149/+subscriptions