I might be wrong, but I don't think changing the dependency back to libecap2 (0.2.0) is the right way to go. The new libecap library (libecap3) is currently in transition and the squid3 build problem is blocking its migration. If we re-introduce the libecap2 dependency, then libecap3 won't be able to migrate to release - as squid3 will be blocking it with this dep. The right solution would be to fix squid3 to build with the new ecap library, possibly integrating changes from upstream.
That's just my 2 cents. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1496924 Title: squid3 FTBFS due to bad libecap3 dependency and logical-not- parentheses warning To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1496924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
