This bug was fixed in the package squid3 - 3.1.19-1ubuntu1
---------------
squid3 (3.1.19-1ubuntu1) precise; urgency=low
* Merge from Debian testing. Remaining changes:
+ debian/control:
- Update maintainer.
+ debian/squid3.upstart, debian/rules, squid3.resolvconf,
debian/squid3.postinst, debian/squid3.postrm, debian/squid3.preinst,
debian/squid3.prerm: Convert init script to upstart
+ debian/control, debian/patches/99-ubuntu-ssl-cert-snakeoil: Use
snakeoil certificates.
+ debian/logrotate: Use sar-reports rather than sarg-maint. (LP: 26616)
+ debian/patches/90-cf.data.ubuntu.dpatch: Add an example refresh pattern
for debs. (foundations-lucid-local-report spec)
+ Add transitional dummy packages
* New upstream bugfix release fixes swap.state corruption, so squid will
now start after a reboot. (LP: #930252)
squid3 (3.1.19-1) unstable; urgency=low
* New upstream release
- Removed patch integrated upstream
+ 19-adaptation-compile
* debian/rules
- Enabled WCCPv2 support (Closes: #654877)
-- Christopher James Halse Rogers <r...@ubuntu.com> Tue, 21 Feb 2012
18:51:26 +1100
** Changed in: squid3 (Ubuntu)
Status: Triaged => Fix Released
--
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/930252
Title:
squid3 crashed with SIGABRT in fatal_dump()
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/930252/+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
