Bug #1764
closed
Wrong version of squid3 among the packages for pfSense 1.2.3
0%
Description
Same issue resolved with this commit:
http://redmine.pfsense.org/projects/pfsense-packages/repository/revisions/3bd2e6738affb0c731993dcdc06d756e23a0dd24
for pfSense 2.0 .
It's given me a great deal of grief on a production machine.
Updated by Jim Pingle almost 13 years ago
- Priority changed from High to Low
- Affected Version changed from 1.2.3 to All
Squid 3 is not and has never been recommended for general use. It's experimental at best. Please use squid 2.9.x if you need stability.
Updated by Fulvio Scapin over 12 years ago
Jim P wrote:
Squid 3 is not and has never been recommended for general use. It's experimental at best. Please use squid 2.9.x if you need stability.
No problem with its stability so far. The problem was tricking the package system into believing the package was version 3.1.14 instead of the 3.0.8, which is the only one actually available, when it automatically reinstalled some packages.
Unless you mean that being experimental the package version changes in a quite more liberal fashion than squid 2.9.x, although I hope that is not the case.
Updated by Fulvio Scapin over 12 years ago
Fulvio Scapin wrote:
Jim P wrote:
Squid 3 is not and has never been recommended for general use. It's experimental at best. Please use squid 2.9.x if you need stability.
No problem with its stability so far. The problem was tricking the package system into believing the package was version 3.1.14 instead of the 3.0.8, which is the only one actually available, when it automatically reinstalled some packages.
Unless you mean that being experimental the package version changes in a quite more liberal fashion than squid 2.9.x, although I hope that is not the case.
Updated by Jim Pingle over 12 years ago
No, I mean the squid3 package has been broken in some fashion the majority of the time, and when it works, you're lucky that it works. It hasn't had an active maintainer in quite some time.
Updated by Jim Pingle about 12 years ago
- Status changed from New to Resolved
Closing this out, it's seen some active work lately, issues are likely resolved, or at least need re-tested.