[Bug 1939352] Re: FTBFS 4.13-10ubuntu3 error: ‘numeric_limits’ is not a member of ‘std’
Fix was released in Squid-4.15. Upstream URL for patch is http://www.squid- cache.org/Versions/v4/changesets/squid-4-cbeff29b6088830f14afd587f0fae4f9e0b28369.patch ** Changed in: squid Importance: Unknown => Undecided ** Changed in: squid Status: Unknown => New ** Changed in: squid Remote watch: github.com/onnx/onnx-tensorrt/issues #474 => None ** Changed in: squid Importance: Undecided => Medium ** Changed in: squid Status: New => 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/1939352 Title: FTBFS 4.13-10ubuntu3 error: ‘numeric_limits’ is not a member of ‘std’ To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/1939352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860807] Re: Please support SSL bumping with '--with-openssl' configure option
Please be aware the upstream fix is that Debian Legal and Technical teams finally decided to make it a matter of policy that OpenSSL was to be considered a core part of Debian rather than just a normal third- party library. That opens the GPL exception clause for incompatible core system licenses. I am not sure of the policy position Ubuntu has about OpenSSL. It will need to match that new Debian policy for the package to be imported from Debian with the --with-openssl option intact. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860807 Title: Please support SSL bumping with '--with-openssl' configure option To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/1860807/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891396] Re: build failure in riscV64
Oops, missed the build version number. >From the build log I see: > checking whether linking without -latomic works... yes A patch adjusting the configure.ac test logic to also check the exchange operator which is missing on riscv64 is the correct way to go. Please submit upstream PR if anyone wants to create and test such a patch. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891396 Title: build failure in riscV64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/1891396/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891396] Re: build failure in riscV64
The upstream patch http://www.squid- cache.org/Versions/v4/changesets/squid-4-f187e5cf415604d4fe839ba57120d846bfa1e672.patch which in includes in Squid-4.12 and later should resolve linking issues with libatomic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891396 Title: build failure in riscV64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/1891396/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 640511] Re: squid in lucid adds bogus port number to Host: line if one isn't provided (in original or via vport=)
Squid-2 has long been obsolete upstream. Now that affected Ubuntu are no longer supported we can close. ** Changed in: squid Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/640511 Title: squid in lucid adds bogus port number to Host: line if one isn't provided (in original or via vport=) To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/640511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1816006] Re: /var/run/squid (run_dir) no longer created on start up
Luigi has added a change in Debian 4.5-2 package that should resolve this. ** Also affects: squid (Debian) Importance: Undecided Status: New ** Changed in: squid (Debian) Status: New => 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/1816006 Title: /var/run/squid (run_dir) no longer created on start up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/1816006/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1098641] Re: visible_hostname defaults to hostname of first http_port IP, not get_hostname()
** Also affects: squid (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1098641 Title: visible_hostname defaults to hostname of first http_port IP, not get_hostname() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/1098641/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1794553] Re: squid crashed with SIGABRT in xassert()
IIRC this may be the result of a bug found in the src/ipc/TypedMsgHeader.* GCC-8 patch for 4.1. Debian received the fix for that in the GCC-8 changes formally accepted into 4.2. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1794553 Title: squid crashed with SIGABRT in xassert() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/1794553/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1780341] Re: squid should default to more human friendly timestamps
Squid already several contains such other formats. All they take is configuration. The default one is intended for fast machine interpretation, since that is the majority use-case for all Squid installations. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1780341 Title: squid should default to more human friendly timestamps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/1780341/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1022821] Re: squid crashed with SIGSEGV in __find_specmb()
This bug no longer exists in the squid binary packages built from Squid-3 sources in Xenial and later. ** Changed in: squid (Ubuntu) Status: New => 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/1022821 Title: squid crashed with SIGSEGV in __find_specmb() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/1022821/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1780944] Re: Please provide Squid-4
Ah, okay. So repo related rather than a end-user problem. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1780944 Title: Please provide Squid-4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/1780944/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1097032] Re: Please provide GNUTLS support in squid
squid v4 packages are now in Cosmic ** Changed in: squid3 (Ubuntu) Status: In Progress => 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/1097032 Title: Please provide GNUTLS support in squid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1097032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793131] Re: FTBFS gcc8
squid 4 packages are now in Cosmic ** Changed in: squid3 (Ubuntu) Status: In Progress => 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/1793131 Title: FTBFS gcc8 To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/1793131/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1416009] Re: Make squid package in 14.04 multithread supported
Squid-4 packages in Cosmic resolve this issue. ** Changed in: squid3 (Ubuntu) Status: Triaged => 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/1416009 Title: Make squid package in 14.04 multithread supported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1416009/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1780944] Re: Please provide Squid-4
Andreas: I'm working on migrating away from squid-dbg to squid-dbgsym now, so a new upload will happen. FYI: instructions from the the designers of the *-dbgsym system were that the only thing source packages do is drop old *-dbg binary packages from d/control files. debhelper compat level 9+ automation does the upgrade logic. The instructions also stated that maintainers must not attempt any manual dependency or Conflict tricks. Is there something radically different for Ubuntu? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1780944 Title: Please provide Squid-4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/1780944/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1780944] Re: Please provide Squid-4
** Description changed: Debian is now providing Squid-4.1. Please update the Ubuntu packages. - This will resolve Ubuntu bug #1097032, bug #16669, and bug #1793131 + This will resolve Ubuntu bug #1097032, bug #16669, bug #1793131, and bug + #1416009. UPDATE:: The v4.2 package now in Debian also contains a fix for bug #1103362. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1780944 Title: Please provide Squid-4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/1780944/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 420729] Re: squid stable permissions problems with log files
This was fixed by the "squid" binary package built from squid3 sources in Ubuntu Xenial and later. ** Changed in: squid (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/420729 Title: squid stable permissions problems with log files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/420729/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 223572] Re: ldap_auth library usage
This was fixed by the "squid" binary package built from squid3 sources in Ubuntu Xenial and later. Specifically the ldap_auth helper no longer exists - instead we have a collection of auth helpers using LDAP for different more-specific purposes. ** Changed in: squid (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/223572 Title: ldap_auth library usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/223572/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 594403] Re: cannot be made to cache responses with no LMT/Date/Expires
This was fixed by the "squid" binary package built from squid3 sources in Ubuntu Xenial and later. ** Changed in: squid (Ubuntu) Status: Triaged => 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/594403 Title: cannot be made to cache responses with no LMT/Date/Expires To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/594403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 685201] Re: shutdown_lifetime setting behavior does not match doc
Current (upstream) documentation says "until all active sockets are closed" - that means a lot more than just client sockets. ** Changed in: squid (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/685201 Title: shutdown_lifetime setting behavior does not match doc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/685201/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 629524] Re: squid not compiled with db_auth
This was fixed by the "squid" binary package built from squid3 sources in Ubuntu Xenial and later. ** Changed in: squid (Ubuntu) Status: Triaged => 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/629524 Title: squid not compiled with db_auth To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/629524/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 695718] Re: squid SIGABRT on bad url_rewriter
This was fixed by the "squid" binary package built from squid3 sources in Ubuntu Xenial and later. ** Changed in: squid (Ubuntu) Status: Triaged => 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/695718 Title: squid SIGABRT on bad url_rewriter To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/695718/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 958210] Re: squid ABRT due to storeLocateVaryRead()
This was fixed by the "squid" binary package built from squid3 sources in Ubuntu Xenial and later. ** Changed in: squid (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/958210 Title: squid ABRT due to storeLocateVaryRead() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/958210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1416009] Re: Make squid package in 14.04 multithread supported
This is a squid3 (v3.2+) package feature. "squid" package in the affected Ubuntu versions is v2.7. ** Package changed: squid (Ubuntu) => squid3 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1416009 Title: Make squid package in 14.04 multithread supported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1416009/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1780341] Re: squid should default to more human friendly timestamps
Squid logs are a customized timestamp format based on UNIX times but also including millisecond (and optionally nanosecond) resolution not available in strictly UNIX timestamps. This format and resolution is necessary for accuracy of log information - which is intended more for machine interpretation via log analysis tools, not human. Human timestamps are far to inaccurate and malleable for this type of data recording. They also vary depending on where in the world the reader is located, independent of where the proxy is located. Human calendar systems are a legal fiction, not a technical or scientific measure - the government of any country can redefine them at any time (and some do so even today). So the time of the recording matters as much as the value recorded in human systems. Mapping between the fixed and deterministic Squid log values and a readers local human system is the purpose of log analysis tools and far more easily done from UNIX-like timestamps than other types. For admin who wish to read the logs manually and provide inaccurate data to their analysis tools other formats are configurable. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1780341 Title: squid should default to more human friendly timestamps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/1780341/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1780944] Re: Please provide Squid-4
** Description changed: Debian is now providing Squid-4.1. Please update the Ubuntu packages. This will resolve Ubuntu bug #1097032 and bug #16669 UPDATE:: The v4.2 package now in Debian also contains a fix for bug - #1103362 + #1103362 and #1793131 ** Description changed: Debian is now providing Squid-4.1. Please update the Ubuntu packages. - This will resolve Ubuntu bug #1097032 and bug #16669 + This will resolve Ubuntu bugs #1097032, #16669, and #1793131 UPDATE:: The v4.2 package now in Debian also contains a fix for bug - #1103362 and #1793131 + #1103362. ** Description changed: Debian is now providing Squid-4.1. Please update the Ubuntu packages. - This will resolve Ubuntu bugs #1097032, #16669, and #1793131 + This will resolve Ubuntu bug #1097032, bug #16669, and bug #1793131 UPDATE:: The v4.2 package now in Debian also contains a fix for bug #1103362. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1780944 Title: Please provide Squid-4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/1780944/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793131] Re: FTBFS gcc8
For the record: All Squid-4+ versions have a hard GCC-5 minimal version requirement. Which should be fine for current Ubuntu. All Squid-3 versions have a GCC-7 or lower build requirement. Optimally GCC-6 or lower, as implemented in the build dependencies for the Debian 3.5.23+ packages. The Squid-4.x packages from Debian all integrate the upstream fix for this, as does the v4.1 package port in cosmic-proposed queue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793131 Title: FTBFS gcc8 To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/1793131/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787409] Re: apparmor profile incorrect for squidguard usage
Do these settings really need to be in the squid Apparmour profile? Can they be done in a Squidguard profile instead? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787409 Title: apparmor profile incorrect for squidguard usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1787409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1780944] Re: Please provide Squid-4
** Description changed: Debian is now providing Squid-4.1. Please update the Ubuntu packages. This will resolve Ubuntu bug #1097032 and bug #16669 + + UPDATE:: The v4.2 package now in Debian also contains a fix for bug + #1103362 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1780944 Title: Please provide Squid-4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/1780944/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1780944] Re: Please provide Squid-4
** Summary changed: - Please provide Squid-4.1 + Please provide Squid-4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1780944 Title: Please provide Squid-4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/1780944/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1780944] Re: Please provide Squid-4.1
Update FTR: 4.2 is now in the pipeline with the requested merges. Luigi informs me he intends to upload the new version to Debian sometime next week. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1780944 Title: Please provide Squid-4.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/1780944/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1780944] Re: Please provide Squid-4.1
Sure. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1780944 Title: Please provide Squid-4.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/1780944/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1780944] Re: Please provide Squid-4.1
The biggest thing will be that Ubuntu and Debian used different upgrade paths to move to 'squid' binary names. Most of the rest was pulled upstream for v4. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1780944 Title: Please provide Squid-4.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/1780944/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1780944] [NEW] Please provide Squid-4.1
Public bug reported: Debian is now providing Squid-4.1. Please update the Ubuntu packages. This will resolve Ubuntu bug #1097032 and bug #16669 ** Affects: squid3 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1780944 Title: Please provide Squid-4.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1780944/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 988802] Re: squid3 killed by ABRT signal. assertion failed: disk.cc377: "fd >= 0"
Upstream fixed this bug in release contained in Bionic. ** Changed in: squid3 (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/988802 Title: squid3 killed by ABRT signal. assertion failed: disk.cc377: "fd >= 0" To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/988802/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759684] Re: squid3 upstream bug 4477 - Linear search through in-memory nodes leads to 100% CPU usage
** Bug watch added: Squid Bugzilla #4477 http://bugs.squid-cache.org/show_bug.cgi?id=4477 ** Also affects: squid via http://bugs.squid-cache.org/show_bug.cgi?id=4477 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1759684 Title: squid3 upstream bug 4477 - Linear search through in-memory nodes leads to 100% CPU usage To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/1759684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1711950] Re: New release 3.5.27
Updated packages have been included in Bionic. ** Changed in: squid3 (Ubuntu) Status: New => 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/1711950 Title: New release 3.5.27 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1711950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1744184] Re: squid 3.3.8 serves duplicate certificates
The official package in Trusty does not contain OpenSSL support. This bug can only happen in unofficial custom builds of Squid. As noted in the ChangeLog upstream have a patch available such builds can use. And Trusty has been superceded by other Ubuntu versions containing that patch. Also please be aware the OpenSSL related code in Squid has been very volatile since 3.2. Best practice for custom builds is to use the latest upstream code instead of rebuilding possibly outdated distro packages. IMO this bug should be closed since it does not actually affect official Ubuntu packages. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1744184 Title: squid 3.3.8 serves duplicate certificates To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/1744184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1097032] Re: Please provide GNUTLS support in squid
Update: Squid-4 packages are now available from Debian experimental repository with basic GnuTLS support for reverse- or explicit- proxy use. These currently exclude SSL-Bump, TLS interception and related features. May require the latest Ubuntu or Debian as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1097032 Title: Please provide GNUTLS support in squid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1097032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1712668] Re: squid3: ftbfs with gcc7: dynamic exception specifications are deprecated
FWIW you managed to submit 6 identical bug reports upstream. The ID of the first was http://bugs.squid-cache.org/show_bug.cgi?id=4759, I've added the explanation there as to why I am not backported the particular patch upstream. There are probably also some other changes in corner features that got bundled in with other large Squid-4+ features or cosmetic patches that disqualify them in their current forms. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1712668 Title: squid3: ftbfs with gcc7: dynamic exception specifications are deprecated To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/1712668/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1572715] Re: Pinger crashed after squid installation
Backtrace information is required to fix this. The logs provided do not contain any mention of squid or pinger process. ** Changed in: squid3 (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1572715 Title: Pinger crashed after squid installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1572715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682736] Re: after 200 GB squid restart http://bugs.squid-cache.org/show_bug.cgi?id=3279
Why delete your data? that upstream bug being logged is just Squid informing you that it cannot perform If-Modified-Since (IMS) revalidation with an object. As it updates that object with a new fetch. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1682736 Title: after 200 GB squid restart http://bugs.squid- cache.org/show_bug.cgi?id=3279 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1682736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1679403] Re: Missing dep8 tests
The basic test that Squid application will start is already done by the squid package DEP-8 tests. Though that could be repeated as a test for this package with the simpler installation of only squid, squidclient and squid-langpack packages. What seems to be missing is a test that the right Content-Language error response is returned by Squid given an Accept-Language input header. A default installation of squid should reject all traffic, so is easy to test for that. Are there any other specific DEP-8 tests preferred for a package which simply installs translation files for another package? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1679403 Title: Missing dep8 tests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid-langpack/+bug/1679403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1659567] Re: empty ACL warning during cron.daily/logrotate
There is no way that I'm aware of in any current Squid. The check is a generic validity check used for all ACLs. Whether it is 'harmless' depends on future events at the time of checking. So just silencing or ignoring would leave a lot of nasty misconfigurations quietly accepted. That said; for an automated rotate 2>/dev/null seems reasonable. These types of thing should be caught and fixed on the previous startup or manual rotate attempts. Long-term I think we are going to have to add an explicit flag to indicate whether an ACL is allowed to be empty or not. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1659567 Title: empty ACL warning during cron.daily/logrotate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid-deb-proxy/+bug/1659567/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1665292] Re: Squid 3.5.12-1ubuntu7.3 - Xenial - SLOW Upload speed
FYI: If it was upstream then I suspect it is most likely this upstream change, none of the others had much performance gain in upstream tests: http://www.squid-cache.org/Versions/v3/3.5/changesets/squid-3.5-14061.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1665292 Title: Squid 3.5.12-1ubuntu7.3 - Xenial - SLOW Upload speed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1665292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1585828] Re: /usr/lib/squid/pinger:11:memcpy:Ip::Address::operator:Ip::Address::operator:Icmp6::Recv:main
Upstream fix included in 3.5.23-1ubuntu1. ** Changed in: squid3 (Ubuntu) Status: Triaged => 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/1585828 Title: /usr/lib/squid/pinger:11:memcpy:Ip::Address::operator:Ip::Address::operator:Icmp6::Recv:main To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1585828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1589567] Re: /usr/lib/squid/pinger:*** Error in `(pinger)': free(): invalid pointer: ADDR ***
Fix upstream included in 3.5.23-1ubuntu1. ** Changed in: squid3 (Ubuntu) Status: New => 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/1589567 Title: /usr/lib/squid/pinger:*** Error in `(pinger)': free(): invalid pointer: ADDR *** To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1589567/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1644538] Re: Please sync Squid 3.5 latest from Debian
Thanks. Yes, I recall a discussion about that change in the early 'installation script failure' bug reports, the one where others in the Ubuntu team got involved and the squid.maintscript got added. But I too can't find which one right now. - We have not had any repots of similar behaviour from Debian users, but did have several reports about the issue the lack of that init script line caused. So in balance I am procrastinating on taking it until Debian has a documented need/bug. The issue should disappear entirely with the upcoming 4.x package. I'm pulling in the adduser and Vcs-Browser patches. Though please note there was some discussion in debian-devel recently about these URLs that concluded the /cgit/ path segment should be /git/ so as not to depend on the cgit tool specifically. The web server now handles redirection itself from the generic URL syntax. I still dont think the snakeoil patch in its current form is correct for squid/3.x packages. The code to use those certs is not even compiled so at the very least a Depends relationship is bogus. The squidclient/3.x could Recommend since it supports HTTPS, but that is a separate package. And the documentation note I suspect has fooled at least some people into thinking they can use the HTTPS config options already. The rest it will need some testing. I hope to have some time for that this week to try to further minimize the diff, but no guarantees. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1644538 Title: Please sync Squid 3.5 latest from Debian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1644538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1644538] Re: Please sync Squid 3.5 latest from Debian
Any progress? I'm getting pings upstream about newer Ubuntu versions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1644538 Title: Please sync Squid 3.5 latest from Debian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1644538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1560429] Re: squid3: segfault when ftp passive mode is not available
Workaround is to configure "ftp_eprt off" for now. A possible fix patch is available at upstream Squid Project in 3.5.23 release. Though we are not sure of completeness yet so the upstream bug report is staying open for now. ** Bug watch added: Debian Bug tracker #793473 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793473 ** Also affects: squid3 (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793473 Importance: Unknown Status: Unknown ** Bug watch added: Squid Bugzilla #4004 http://bugs.squid-cache.org/show_bug.cgi?id=4004 ** Also affects: squid via http://bugs.squid-cache.org/show_bug.cgi?id=4004 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1560429 Title: squid3: segfault when ftp passive mode is not available To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/1560429/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1613914] Re: squid upgrade fails when user has custom cache_dir
Having a cache_dir at all is non-default. Squid-3 default is to run with a memory-only cache. The /var/spool/squid path is used as default run- time working directory. Which reminds me the proxies low-privilege user account is tied via home directory to the location the original machine install was done with. That probably has not been updated since before Trusty. Symlinks and mount points, either on the cache_dir directory, or below it need to be accounted for. As do SELinux policies, AppArmour policies - both the system ones and custom changes which do not show up in the squid.conf paths. Then there is the issue of other custom tools interacting with the cache_dir data. Not common but when it does happen it's usually custom software outside the package tracking system, which we dont have a clue about whether it can cope with the move. IMHO just leave it, the gain is cosmetic at best and surprisingly hard to do correctly without local knowledge only the admin has. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1613914 Title: squid upgrade fails when user has custom cache_dir To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1613914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1644538] Re: Please sync Squid 3.5 latest from Debian
Pretty sure it fixes bug #1585828. It should also fix bug #1572715 and bug #1589567 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1644538 Title: Please sync Squid 3.5 latest from Debian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1644538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1585828] Re: /usr/lib/squid/pinger:11:memcpy:Ip::Address::operator:Ip::Address::operator:Icmp6::Recv:main
I believe this was fixed upstream by http://www.squid- cache.org/Versions/v3/3.5/changesets/squid-3.5-14015.patch. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1585828 Title: /usr/lib/squid/pinger:11:memcpy:Ip::Address::operator:Ip::Address::operator:Icmp6::Recv:main To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1585828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1390132] Re: Cannot change the maximum number of filedescriptors
This was fixed upstream in 3.3.11. So the Squid v3.5 package in Xenial and later is fixed. ** Changed in: squid3 (Ubuntu) Status: Confirmed => Fix Released ** Bug watch added: Squid Bugzilla #3970 http://bugs.squid-cache.org/show_bug.cgi?id=3970 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1390132 Title: Cannot change the maximum number of filedescriptors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1390132/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1390132] Re: Cannot change the maximum number of filedescriptors
For the record upstream patch is at http://bugs.squid- cache.org/show_bug.cgi?id=3970 but requires the build system to be re- bootstrapped so it cannot be easily applied to downstream packages. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1390132 Title: Cannot change the maximum number of filedescriptors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1390132/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1390132] Re: Cannot change the maximum number of filedescriptors
Oops, that was the bug. I mean the patch is http://www.squid- cache.org/Versions/v3/3.3/changesets/squid-3.3-12662.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1390132 Title: Cannot change the maximum number of filedescriptors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1390132/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1644538] [NEW] Please sync Squid 3.5 latest from Debian
Public bug reported: Debian has a newer squid version (3.5.22) than Ubuntu that fixes several of the open bugs. ** Affects: squid3 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1644538 Title: Please sync Squid 3.5 latest from Debian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1644538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1613914] Re: squid upgrade fails when user has custom cache_dir
All these upgrade failures are because the Unbuntu package touches the cache_dir directory locations on upgrades. The upstream Debian package intentionally does not touch any existing cache_dir locations even if they contain the old 'squid3' folder names in order avoid this type of problem. Can somebody please revert that part of the install/upgrade scripts? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1613914 Title: squid upgrade fails when user has custom cache_dir To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1613914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1578940] Re: package squid3 3.3.8-1ubuntu6.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
*** This bug is a duplicate of bug 1568955 *** https://bugs.launchpad.net/bugs/1568955 ** This bug has been marked a duplicate of bug 1568955 package squid (not installed) failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1578940 Title: package squid3 3.3.8-1ubuntu6.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1578940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1617072] Re: package squid 3.5.12-1ubuntu7.2 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1
*** This bug is a duplicate of bug 1613914 *** https://bugs.launchpad.net/bugs/1613914 ** This bug is no longer a duplicate of bug 1625569 package squid 3.5.12-1ubuntu7.2 failed to install%Fupgrade: subprocess installed post-installation script returned error exit status 1 ** This bug has been marked a duplicate of bug 1613914 squid upgrade fails when user has custom cache_dir -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1617072 Title: package squid 3.5.12-1ubuntu7.2 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1617072/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1625569] Re: package squid 3.5.12-1ubuntu7.2 failed to install%Fupgrade: subprocess installed post-installation script returned error exit status 1
*** This bug is a duplicate of bug 1613914 *** https://bugs.launchpad.net/bugs/1613914 ** This bug has been marked a duplicate of bug 1613914 squid upgrade fails when user has custom cache_dir -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1625569 Title: package squid 3.5.12-1ubuntu7.2 failed to install%Fupgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1625569/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1528966] Re: error from /etc/resolvconf/update-libc.d/squid3
There should not be any such thing as /etc/resolvconf/update- libc.d/squid3 on a fresh Xenial install. The package and all its paths and scripts are now just 'squid'. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1528966 Title: error from /etc/resolvconf/update-libc.d/squid3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1528966/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1617072] Re: package squid 3.5.12-1ubuntu7.2 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1
*** This bug is a duplicate of bug 1625569 *** https://bugs.launchpad.net/bugs/1625569 ** This bug has been marked a duplicate of bug 1625569 package squid 3.5.12-1ubuntu7.2 failed to install%Fupgrade: subprocess installed post-installation script returned error exit status 1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1617072 Title: package squid 3.5.12-1ubuntu7.2 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1617072/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1620120] Re: Segfault in QDevelop -> libc
** Package changed: squid3 (Ubuntu) => qdevelop (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1620120 Title: Segfault in QDevelop -> libc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qdevelop/+bug/1620120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1391159] Re: squid3 is not built with helper /usr/lib/squid3/ext_time_quota_acl
Workaround is to build Squid3 yourself from source package with the helper enabled. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1391159 Title: squid3 is not built with helper /usr/lib/squid3/ext_time_quota_acl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1391159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1611185] Re: Error : Opening the cache
What make you think this is a bug in Squid? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1611185 Title: Error : Opening the cache To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1611185/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1576549] Re: Squid3 : Disable sslv3 if system is built with no sslv3
The Squid packages available in Xenial and later already contain a fix from upstream. ** Changed in: squid3 (Ubuntu) Status: New => 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/1576549 Title: Squid3 : Disable sslv3 if system is built with no sslv3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1576549/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1571174] Re: package squid3 failed to install/upgrade: dependency problems - leaving triggers unprocessed
** Summary changed: - package squid3 3.3.8-1ubuntu16.2 failed to install/upgrade: dependency problems - leaving triggers unprocessed + package squid3 failed to install/upgrade: dependency problems - leaving triggers unprocessed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1571174 Title: package squid3 failed to install/upgrade: dependency problems - leaving triggers unprocessed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1571174/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1576531] Re: package squid 3.5.12-1ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
*** This bug is a duplicate of bug 1571174 *** https://bugs.launchpad.net/bugs/1571174 ** This bug has been marked a duplicate of bug 1571174 package squid3 3.3.8-1ubuntu16.2 failed to install/upgrade: dependency problems - leaving triggers unprocessed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1576531 Title: package squid 3.5.12-1ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1576531/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1576938] Re: package squid3 not installed failed to install/upgrade: dependency problems - leaving triggers unprocessed
*** This bug is a duplicate of bug 1571174 *** https://bugs.launchpad.net/bugs/1571174 ** This bug is no longer a duplicate of bug 1576531 package squid 3.5.12-1ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 ** This bug has been marked a duplicate of bug 1571174 package squid3 3.3.8-1ubuntu16.2 failed to install/upgrade: dependency problems - leaving triggers unprocessed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1576938 Title: package squid3 not installed failed to install/upgrade: dependency problems - leaving triggers unprocessed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1576938/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1576645] Re: package squid3 3.5.12-1ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed
*** This bug is a duplicate of bug 1571174 *** https://bugs.launchpad.net/bugs/1571174 ** This bug is no longer a duplicate of bug 1576531 package squid 3.5.12-1ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 ** This bug has been marked a duplicate of bug 1571174 package squid3 3.3.8-1ubuntu16.2 failed to install/upgrade: dependency problems - leaving triggers unprocessed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1576645 Title: package squid3 3.5.12-1ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1576645/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1576936] Re: squid3 died during trusty->xenial upgrade
*** This bug is a duplicate of bug 1571174 *** https://bugs.launchpad.net/bugs/1571174 ** This bug has been marked a duplicate of bug 1571174 package squid3 3.3.8-1ubuntu16.2 failed to install/upgrade: dependency problems - leaving triggers unprocessed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1576936 Title: squid3 died during trusty->xenial upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1576936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1576645] Re: package squid3 3.5.12-1ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed
*** This bug is a duplicate of bug 1576531 *** https://bugs.launchpad.net/bugs/1576531 ** This bug has been marked a duplicate of bug 1576531 package squid 3.5.12-1ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1576645 Title: package squid3 3.5.12-1ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1576645/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1576938] Re: package squid3 not installed failed to install/upgrade: dependency problems - leaving triggers unprocessed
*** This bug is a duplicate of bug 1576531 *** https://bugs.launchpad.net/bugs/1576531 ** This bug has been marked a duplicate of bug 1576531 package squid 3.5.12-1ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1576938 Title: package squid3 not installed failed to install/upgrade: dependency problems - leaving triggers unprocessed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1576938/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1214379] Re: pinger crashed with SIGSEGV in malloc_consolidate()
Can you please provide a backtrace from the new crash? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1214379 Title: pinger crashed with SIGSEGV in malloc_consolidate() To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/1214379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1563202] Re: Calamaris 2.99.4.0-19 does not understand 'PINNED' method in squid3 3.3.8-1ubuntu6.6 (trusty)
This was fixed in the package in 15.10 Wily. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1563202 Title: Calamaris 2.99.4.0-19 does not understand 'PINNED' method in squid3 3.3.8-1ubuntu6.6 (trusty) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamaris/+bug/1563202/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1235681] Re: squid3 always run with -N option, incompatible with SMP option (workers)
This is fixed in the squid package now available in Xenial, which removes upstart integration. ** Changed in: squid3 (Ubuntu) Status: Triaged => 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/1235681 Title: squid3 always run with -N option, incompatible with SMP option (workers) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1235681/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1547640] Re: proxy tries ipv6 and gets 503 when no ipv6 routes
This is fixed in the squid package now available in Xenial. ** Changed in: squid3 (Ubuntu Xenial) Status: In Progress => 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/1547640 Title: proxy tries ipv6 and gets 503 when no ipv6 routes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1547640/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1214379] Re: pinger crashed with SIGSEGV in malloc_consolidate()
This is fixed in the squid package now available in Xenial. ** Changed in: squid3 (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/1214379 Title: pinger crashed with SIGSEGV in malloc_consolidate() To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/1214379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1532560] Re: pinger crash every night in IcmpPinger::Recv
This is fixed in the squid package now available in Xenial. ** Changed in: squid3 (Ubuntu) Status: New => 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/1532560 Title: pinger crash every night in IcmpPinger::Recv To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1532560/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1414754] Re: /etc/logrotate.d/squid3 fails to execute sarg-reports
This is fixed in the squid package now available in Xenial. ** Changed in: squid3 (Ubuntu) Status: New => 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/1414754 Title: /etc/logrotate.d/squid3 fails to execute sarg-reports To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1414754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1459638] Re: maximum_object_size has no effect in default configuration file
This is fixed in the squid package now available in Xenial. ** Changed in: squid3 (Ubuntu) Status: Triaged => 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/1459638 Title: maximum_object_size has no effect in default configuration file To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/1459638/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1213455] Re: pinger crashed with SIGSEGV in __strftime_internal()
This is fixed in the squid package now available in Xenial. ** Changed in: squid3 (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/1213455 Title: pinger crashed with SIGSEGV in __strftime_internal() To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/1213455/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1214379] Re: pinger crashed with SIGSEGV in malloc_consolidate()
** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2014-7141 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2014-7142 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1214379 Title: pinger crashed with SIGSEGV in malloc_consolidate() To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/1214379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1547640] Re: proxy tries ipv6 and gets 503 when no ipv6 routes
Andres, Because there is no way to distinguish between a local-only network and one using NAT without actually trying to connect to the IPs (which is exactly what Squid is doing - up to the limit of forward_max_tries). The problem is identical and far more widespread in IPv4. Disabling IPv4 whenever RFC1918 addresses were the only ones assigned would cut a huge number of networks connectivity. It simply comes down to the fact that despite some mistaken opinions to the contrary, IPv6 is mandatory for any network that wishes to communicate with the www. IPv4-only networks (even just on the global facing part) will face more and more inability to communicate as time passes. We can juggle some numbers to workaround the pain for a while. But in the end IPv6 is mandatory. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1547640 Title: proxy tries ipv6 and gets 503 when no ipv6 routes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1547640/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1547640] Re: proxy tries ipv6 and gets 503 when no ipv6 routes
And for the record. No Squid does not use libc getaddrinfo(). That API provides speed restrictions several orders of magnitude too slow for even small Squid installations. ** Description changed: Many people run squid (squid-deb-proxy, or maas-proxy) to provide ubuntu archive mirror caching and proxying. MAAS sets this up by default for users with the 'maas-proxy' package. On or about Friday February 19, this setup began to fail for many people. Users would see 'apt-get update' returning 503 errors. For me, I saw 503 on security.ubuntu.com addresses. - The reason for the failure was that the squid proxy began using ipv6 - addresses for instead of ipv4. The squid proxy host did not have ipv6 - connectivity and thus would fail. + The reason for the failure was that the DNS records for Ubuntu reacheda + threshold of 10 IPv6 entries. The squid proxy host did not have ipv6 + connectivity and with a limit of 10 retries the failover does not reach + any IPv4 addresses - thus would fail. The fix/workaround is to add the following to your squid config: - # http://www.squid-cache.org/Doc/config/dns_v4_first/ - dns_v4_first on + # http://www.squid-cache.org/Doc/config/forward_max_tries/ + forward_max_tries 25 The appropriate squid config file depends on what is running squid. maas-proxy: /usr/share/maas/maas-proxy.conf squid-deb-proxy: /etc/init/squid-deb-proxy.conf I'm not sure how this previously worked, nor what change was made. One change that was made in this time frame was a glibc update (2.19-0ubuntu6.6 to 2.19-0ubuntu6.7) for security (CVE-2013-7423 CVE-2014-9402 CVE-2015-1472 CVE-2015-1473). But it doesn't seem to make sense that that would change squid3 to start looking for records when it did not previously. i can verify that as late as - Thu Feb 18 06:36:07 EST 2016 + Thu Feb 18 06:36:07 EST 2016 i was seeing entries in my squid logs with - 1455713142.896335 10.7.2.103 TCP_REFRESH_UNMODIFIED/200 82620 GET http://security.ubuntu.com/ubuntu/dists/xenial-security/InRelease - HIER_DIRECT/91.189.88.149 - + 1455713142.896335 10.7.2.103 TCP_REFRESH_UNMODIFIED/200 82620 GET http://security.ubuntu.com/ubuntu/dists/xenial-security/InRelease - HIER_DIRECT/91.189.88.149 - but now i get - 1455879482.210 1 10.7.2.103 TCP_REFRESH_FAIL/200 635 GET http://security.ubuntu.com/ubuntu/dists/precise-security/main/i18n/Index - HIER_DIRECT/2001:67c:1562::14 - + 1455879482.210 1 10.7.2.103 TCP_REFRESH_FAIL/200 635 GET http://security.ubuntu.com/ubuntu/dists/precise-security/main/i18n/Index - HIER_DIRECT/2001:67c:1562::14 - -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1547640 Title: proxy tries ipv6 and gets 503 when no ipv6 routes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1547640/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1547640] Re: proxy tries ipv6 and gets 503 when no ipv6 routes
The upstream fix was http://www.squid- cache.org/Versions/v3/3.5/changesets/squid-3-12982.patch - which is to increase the number of IPs attempted to 25 instead of just 10. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1547640 Title: proxy tries ipv6 and gets 503 when no ipv6 routes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1547640/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1235681] Re: squid3 always run with -N option, incompatible with SMP option (workers)
For the record this usage of -N is an intentional addition for Upstart integration with Squid-3. It is needed to avoid those much worse process control start/stop issues mentioned in the report, and other less obvious problems around the system. The Ubuntu package dropping its Upstart integration patch as a whole will remove this issue. At cost of dropping back to SysVinit for process management. Squid-3.5 versions currently in Debian upstream contains different integration for dual compatibility with SysVinit and systemd which offers better behaviour (and those "service" commands), but this does not affect the Upstart support. Squid-4 versions (not yet packaged) will be coming with some changes that should make the -N option no longer needed for Upstart. That will need to be verified when the time comes, if Upstart intgration is still in the Ubuntu package at that point. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1235681 Title: squid3 always run with -N option, incompatible with SMP option (workers) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1235681/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1391159] Re: squid3 is not built with helper /usr/lib/squid3/ext_time_quota_acl
Fix for this has been added upstream in Debian package 3.5.14-1 ** Also affects: squid3 (Debian) Importance: Undecided Status: New ** Changed in: squid3 (Debian) Status: New => 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/1391159 Title: squid3 is not built with helper /usr/lib/squid3/ext_time_quota_acl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1391159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1544400] Re: squid3: systemctl reports squid is running when there is a bungled squid.conf and it has exited.
The squid3.service file is auto-generated. The actual upstream fix was: commit 6ac65f75a971a4a87c18766f3fe9969e91cef591 Author: Mathieu Parent Date: Thu Oct 8 09:40:50 2015 +0200 Set pidfile for systemd's sysv-generator This actually changes the followind settings (from systemctl cat squid.service): from: [Service] RemainAfterExit=yes to: [Service] RemainAfterExit=no PIDFile=/var/run/squid.pid diff --git a/debian/squid.rc b/debian/squid.rc index 204b676..a27fd88 100644 --- a/debian/squid.rc +++ b/debian/squid.rc @@ -4,6 +4,8 @@ # # Version: @(#)squid.rc 1.0 07-Jul-2006 lu...@debian.org # +# pidfile: /var/run/squid.pid +# ### BEGIN INIT INFO # Provides: squid # Required-Start:$network $remote_fs $syslog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1544400 Title: squid3: systemctl reports squid is running when there is a bungled squid.conf and it has exited. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1544400/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1473691] Re: squid: Update to latest upstream stable release (3.5)
** Description changed: - Squid's latest stable upstream version is currently 3.5 and fixes - important bugs, such as the inability to fall back to IPv4 if a websites - IPv6 connectivity is broken (e.g. http://readlist.com/lists/squid- - cache.org/squid-users/11/58389.html), #1213455, #1214379, #1459638, - #1448149, #1390132, #1423498 and #1532560. + Squid's latest upstream version is currently 3.5 and fixes important + bugs, such as the inability to fall back to IPv4 if a websites IPv6 + connectivity is broken (e.g. http://readlist.com/lists/squid-cache.org + /squid-users/11/58389.html), #1213455, #1214379, #1459638, #1448149, + #1390132, #1423498 and #1532560. Please update the package from 3.3.8 to the version that Debian already - has in its stable distribution. + has in its distribution. Question 268037 already asked the same - here's the filed bug. ** Summary changed: - squid: Update to latest upstream stable release (3.5) + squid: Update to latest upstream release (3.5) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1473691 Title: squid: Update to latest upstream release (3.5) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1473691/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1473691] Re: squid: Update to latest upstream stable release (3.5)
** Summary changed: - Update to latest upstream stable release (3.5) + squid: Update to latest upstream stable release (3.5) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1473691 Title: squid: Update to latest upstream stable release (3.5) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1473691/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1473691] Re: Update to latest upstream stable release (3.5)
** Description changed: Squid's latest stable upstream version is currently 3.5 and fixes important bugs, such as the inability to fall back to IPv4 if a websites IPv6 connectivity is broken (e.g. http://readlist.com/lists/squid- cache.org/squid-users/11/58389.html), #1213455, #1214379, #1459638, - #1448149, #1390132, and #1532560. + #1448149, #1390132, #1423498 and #1532560. Please update the package from 3.3.8 to the version that Debian already has in its stable distribution. Question 268037 already asked the same - here's the filed bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1473691 Title: squid: Update to latest upstream stable release (3.5) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1473691/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1473691] Re: Update to latest upstream stable release (3.5)
** Description changed: - Squid's latest stable upstream version is currently 3.5.7 and fixes + Squid's latest stable upstream version is currently 3.5 and fixes important bugs, such as the inability to fall back to IPv4 if a websites IPv6 connectivity is broken (e.g. http://readlist.com/lists/squid- - cache.org/squid-users/11/58389.html). Please update the package from - 3.3.8 to 3.5.7, or, at the very least, update it to version 3.4.8 that - Debian already has in its stable distribution (Jessie, and Wheezy - backports too). + cache.org/squid-users/11/58389.html), #1213455, #1214379, #1459638, + #1448149, #1390132, and #1532560. + + Please update the package from 3.3.8 to the version that Debian already + has in its stable distribution. Question 268037 already asked the same - here's the filed bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1473691 Title: Update to latest upstream stable release (3.5) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1473691/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1404876] Re: pinger assert failure: *** Error in `(pinger)': free(): invalid pointer: 0x00007f3b5e73ebf0 ***
*** This bug is a duplicate of bug 1214379 *** https://bugs.launchpad.net/bugs/1214379 ** This bug has been marked a duplicate of bug 1214379 pinger crashed with SIGSEGV in malloc_consolidate() -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1404876 Title: pinger assert failure: *** Error in `(pinger)': free(): invalid pointer: 0x7f3b5e73ebf0 *** To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/1404876/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1214806] Re: pinger crashed with SIGSEGV in __tzfile_compute()
*** This bug is a duplicate of bug 1213455 *** https://bugs.launchpad.net/bugs/1213455 ** This bug has been marked a duplicate of bug 1213455 pinger crashed with SIGSEGV in __strftime_internal() -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1214806 Title: pinger crashed with SIGSEGV in __tzfile_compute() To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/1214806/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 392077] Re: Squid crashes with "assertion failed" mem->swapout.sio
** Bug watch added: Squid Bugzilla #3852 http://bugs.squid-cache.org/show_bug.cgi?id=3852 ** Changed in: squid Importance: Medium => Unknown ** Changed in: squid Status: Invalid => Unknown ** Changed in: squid Remote watch: Squid Bugzilla #3453 => Squid Bugzilla #3852 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/392077 Title: Squid crashes with "assertion failed" mem->swapout.sio To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/392077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1081952] Re: squid 3.1.19 external_acl_type fail
I think this bug is not valid. The config does not meet the documented requirement that the script interpreter be a *full path* to the sript interpreter, or helper binary. "php" is not the full path to the PHP executable. The helper is also closing its stdin communication socket to Squid before sending any response back. When Squid receives that termination signal, the helper state will be shutdown and ERR used in place of any pending lookups. ** Changed in: squid3 (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1081952 Title: squid 3.1.19 external_acl_type fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1081952/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1236239] Re: pinger assert failure: *** Error in `(pinger)': free(): invalid next size (normal): 0x00007efffc4e7df0 ***
*** This bug is a duplicate of bug 1214379 *** https://bugs.launchpad.net/bugs/1214379 ** This bug has been marked a duplicate of bug 1214379 pinger crashed with SIGSEGV in malloc_consolidate() -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1236239 Title: pinger assert failure: *** Error in `(pinger)': free(): invalid next size (normal): 0x7efffc4e7df0 *** To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1236239/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1300064] Re: pinger crashed with SIGSEGV in __tzfile_compute()
*** This bug is a duplicate of bug 1213455 *** https://bugs.launchpad.net/bugs/1213455 ** This bug is no longer a duplicate of bug 1214806 pinger crashed with SIGSEGV in __tzfile_compute() ** This bug has been marked a duplicate of bug 1213455 pinger crashed with SIGSEGV in __strftime_internal() -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1300064 Title: pinger crashed with SIGSEGV in __tzfile_compute() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1300064/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
