Latest upstream release: 3.2.3 Current version in Fedora Rawhide: 3.2.2 URL: ftp://ftp.squid-cache.org/pub/squid/ Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring
Fixed in squid-3.2.3-1.fc18.
Any chance of getting a build for F-17?
I am sorry, but rebase in f17 is against fedora updates policy. If you need version 3.2.3, you can find it in koji( https://koji.fedoraproject.org/koji/ ).
What rebase? 3.2.0.16 was a release candidate of this same major version. If anything, you shoud be required to update.
http://www.squid-cache.org/Versions/v3/3.2/
Correct. Squid-3.2.3 is a bugfix release in the Squid-3.2 series and should be pushed to F17 and F16.
I am sorry for mystification. F16 and F17 will be updated soon.
squid-3.2.3-2.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/FEDORA-2012-16962/squid-3.2.3-2.fc18
Squid-3.2.3 requires higher version of openssl than is present in F17. I would like to update Squid but it is not possible because of mentioned issue. I am sorry for any inconvenience.
(In reply to comment #9) > Squid-3.2.3 requires higher version of openssl than is present in F17. I > would like to update Squid but it is not possible because of mentioned > issue. I am sorry for any inconvenience. That is not true. I just built squid with --enable-ssl on F-17: --------------------- $ lsb_release -rd Description: Fedora release 17 (Beefy Miracle) Release: 17 $ src/squid -v Squid Cache: Version 3.2.3 configure options: '--enable-ssl' --enable-ltdl-convenience $ ldd src/squid linux-vdso.so.1 => (0x00007fff077f2000) libpthread.so.0 => /lib64/libpthread.so.0 (0x0000003ae8a00000) libcrypt.so.1 => /lib64/libcrypt.so.1 (0x0000003130800000) libssl.so.10 => /lib64/libssl.so.10 (0x0000003fc6a00000) libcrypto.so.10 => /lib64/libcrypto.so.10 (0x0000003af8e00000) libgssapi_krb5.so.2 => /lib64/libgssapi_krb5.so.2 (0x0000003fc6200000) libkrb5.so.3 => /lib64/libkrb5.so.3 (0x0000003fc6600000) libk5crypto.so.3 => /lib64/libk5crypto.so.3 (0x0000003af7200000) libcom_err.so.2 => /lib64/libcom_err.so.2 (0x0000003fc5e00000) libnsl.so.1 => /lib64/libnsl.so.1 (0x0000003afd600000) libresolv.so.2 => /lib64/libresolv.so.2 (0x0000003aea200000) librt.so.1 => /lib64/librt.so.1 (0x0000003ae9200000) libdl.so.2 => /lib64/libdl.so.2 (0x0000003ae8e00000) libstdc++.so.6 => /lib64/libstdc++.so.6 (0x0000003aefa00000) libm.so.6 => /lib64/libm.so.6 (0x0000003ae9600000) libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x0000003aeba00000) libc.so.6 => /lib64/libc.so.6 (0x0000003ae8600000) /lib64/ld-linux-x86-64.so.2 (0x0000003ae8200000) libfreebl3.so => /lib64/libfreebl3.so (0x0000003130400000) libz.so.1 => /lib64/libz.so.1 (0x0000003ae9a00000) libkrb5support.so.0 => /lib64/libkrb5support.so.0 (0x0000003af6e00000) libkeyutils.so.1 => /lib64/libkeyutils.so.1 (0x0000003af6600000) libselinux.so.1 => /lib64/libselinux.so.1 (0x0000003ae9e00000) $ rpm -qf /lib64/libssl.so.10 openssl-1.0.0j-2.fc17.x86_64 ---------------------
Also built RPMS from the f17 branch of the Fedora squid git on my F-17 machine. This is what I had to change in the spec to do it: --------------------------- diff --git a/squid.spec b/squid.spec index 7a6cd62..3b4ce3e 100644 --- a/squid.spec +++ b/squid.spec @@ -3,7 +3,7 @@ ## % define __find_requires %{SOURCE99} Name: squid -Version: 3.2.0.16 +Version: 3.2.3 Release: 1%{?dist} Summary: The Squid proxy caching server Epoch: 7 @@ -114,6 +114,7 @@ The squid-sysvinit contains SysV initscritps support. LDFLAGS="-pie" %configure \ + --disable-strict-error-checking \ --exec_prefix=/usr \ --libexecdir=%{_libdir}/squid \ --localstatedir=/var \ --------------------------- If --disable-strict-error-checking is not added to configure, it will fail in tools.cc, because a couple functions' return values are not checked. So, looks doable. PS. Master branch will indeed fail to build, not because of --enable-ssl, but because of --enable-crtd. There are patches floating around to fix that too. See this for instance: http://squid-web-proxy-cache.1019090.n4.nabble.com/attachment/4656119/0/certificate_db_cc_compile_fix_patch.txt
squid-3.2.3-2.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/squid-3.2.3-2.fc17
Openssl build issue was caused by configure option --enable-ssl-crtd. Since this option wasn't enabled in F17, I have successfully prepared update preserving F16 configure options and you can find it now in testing.
squid-3.2.3-2.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/squid-3.2.3-2.fc16
squid-3.2.3-2.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
squid-3.2.3-2.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.