hi all,
I have a question about upgrade squid 3.5.26.
I was install squid 3.5.20 via yum in Centos 7, but now I need to upgrade squid 3.5.26 to test about the bug in delay_pools. But the least version of squid in Centos7 is 3.5.20.
my question ~ Can I just download the package "squid-3.5.26.tar.gz" and config it ? but I'm flesh in linux I don't know how to ./configure. I can't find any install step of squid.
or , I'm using the Unofficial packages and yum updatejust like this,,,
[squid]name=Squid repo for CentOS Linux - $basearch#IL mirrorbaseurl=http://www1.ngtech.co.il/repo/centos/$releasever/$basearch/failovermethod=pr...
any suggestion for me ?
here is my server info :
Linux 3.10.0-514.16.1.el7.x86_64 #1 SMP Wed Apr 12 15:04:24 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Thanks A lot~
Bear
On 07/24/2017 04:35 AM, Alex Tang wrote:
hi all,
I have a question about upgrade squid 3.5.26.
I was install squid 3.5.20 via yum in Centos 7, but now I need to upgrade squid 3.5.26 to test about the bug in delay_pools. But the least version of squid in Centos7 is 3.5.20.
my question ~ Can I just download the package "squid-3.5.26.tar.gz" and config it ? but I'm flesh in linux I don't know how to ./configure. I can't find any install step of squid.
There is only one version of squid released for CentOS-7, it will likely never be upgraded to a newer major version .. see the backporting link below.
or , I'm using the Unofficial packages and yum updatejust like this,,,
[squid]name=Squid repo for CentOS Linux - $basearch#IL mirrorbaseurl=http://www1.ngtech.co.il/repo/centos/$releasever/$basearch/failovermethod=pr...
any suggestion for me ?
here is my server info :
Linux 3.10.0-514.16.1.el7.x86_64 #1 SMP Wed Apr 12 15:04:24 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Red Hat does something called backporting:
https://access.redhat.com/security/updates/backporting
Since centOS uses the RHEL source code, we also inherit backporting.
Therefore, even though the version listed is 3.5.20, that does not mean that bugfixes or security updates from newer versions are not rolled in.
So, unless you want to maintain your own packages, you should stay with the version that comes with CentOS. Are you sure that issue is not addressed in a backport?