This bug was fixed in the package squid - 2.7.STABLE9-4ubuntu2
---
squid (2.7.STABLE9-4ubuntu2) oneiric; urgency=low
* debian/postinst, debian/config:
- Fix upgrade failures where cache_dir type of null is in use by
checking that cache_dir points at a real directory or
The issue is that the post installation script attempts to chown the
cache_dir directory with appropriate permissions; however as cache_dir
null does not have a directory type it tried to chown the next argument
which in this configuration is no-store.
--
You received this bug notification
Adam
You could work around this by re-enabling the original cache_dir
configuration option during the upgrade and then restoring your
configuration once it had been completed.
** Changed in: squid (Ubuntu)
Importance: Undecided = Low
** Changed in: squid (Ubuntu)
Status: Confirmed =
Thanks for reporting this bug and any supporting documentation.
Since this bug has enough information provided for a developer to begin
work, I'm going to mark it as 'Triaged and let them handle it from here.
As the workaround is relatively easier I've set its importance as 'Low'.
Thanks for
** Changed in: squid (Ubuntu)
Assignee: (unassigned) = James Page (james-page)
** Changed in: squid (Ubuntu)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid in Ubuntu.
Great, James. I'm glad I could help out. I wouldn't think there are a
lot of people running squid without the cache, but my situation is a bit
unique, so it figures I'd find something a bit obscure. It should be an
easy fix, and thankfully the rest of the upgrade went fine.
--
You received
