RE: [squid-users] Squid 3.4.5 is available

Hi Amos!

Does this mean that squid 3.4.4 is no longer supported on
RedHat Enterprise/Centos 5 (ships with autoconf 2.59)?
RHEL 6 comes with exactly 2.63, so any future update will
mean that RHEL6 may also become unsupported as well.

Just tracking upstream "authconf" is bound to produce similar
pains that I have already experienced with RRDTool on RH3,
RH4, RH5 systems.

I assume that the tar-balls will still get delivered with the
./configure files, so the "direct" need of autoconf versions
 may be less important for lots of people just compiling.
But it still may break at some point resulting in unexpected
behavior - probably during a really important bug-fix
release...

So I wonder if it is really a wise move to potentially cut off
people from security patches because they can no longer
compile squid on the system they want to use it on just
due to the build-tool dependencies.

Is there maybe a plan not to change build-tool versions
within a minor version (3.4, 3.5, ...) to somewhat avoid
such issues?

Thanks,
        Martin

-----Original Message-----
From: Amos Jeffries [mailto:squid3_at_treenet.co.nz]
Sent: Montag, 05. Mai 2014 15:05
To: squid-users_at_squid-cache.org
Subject: [squid-users] Squid 3.4.5 is available

The Squid HTTP Proxy team is very pleased to announce the availability
of the Squid-3.4.5 release!

This release is a bug fix release resolving several regression bugs
and portability issues found in the prior Squid releases.

The major changes to be aware of:

* Packaging toolchain updates

We have recently updated the machinery used to package Squid. As a
result of this the autotools and libtool software versions with embeded
components in the Squid packages have changed. Some of you have noticed
the 3.4.4.* beta releases made to ensure this transition went as
smoothly as possible.

NOTICE:
  For this release onwards in all series of Squid we will be
  tracking the autotools updates a lot closer than previously.

  Please be aware:
  The effect of this change is likely to be un-announced issues
  when compiling with very old tool chains.

autoconf: versions older than 2.63 are expected not to build. While this
is not exactly new, the likelihood of breakage when building with older
versions has increased.

automake: versions older than 1.14 were expected to have issues, but so
far none have been reported with at least automake 1.11. This situation
for older versions may change at any time without further warning.

libtool: the LTDL library used by libtoolize v2.4 is now required.
libtool v2.2 can still be used to build Squid but now requires the
./configure option --with-included-ltdl.

compiler: as before the requirement is "a C++ compiler". The Squid
Project performs continuous integration and pre-release testing with ICC
11+, Clang 3.3+ and several GCC 4.x. Other C++ compilers are expected to
work but are not regularly tested.
 A working C compiler is still also required by some libraries.

NOTICE: Please be aware our C++ language roadmap:
  As of this release we are officially beginning a transition
  to C++11. If the compiler offers support for -std=c++11, it
  will be used.

  While Squid-3.4 will continue to build on all GCC 4.x, please
  begin any necessary planning for the minimum required GCC
  version to become 4.8 later this calendar year.

* Bug #3371: CONNECT with data sent at once loses data

This long-standing bug in CONNECT requests has finally been resolved.
While uncommon for some time it has recently shown to be a large problem
with web browsers implementing SPDY/3 and was expected to get worse with
the upcoming HTTP/2.0 transition.

* Bug #3955, #3982 and other EUI issues have been resolved

These multiple regression bugs in 3.4 EUI handling have been preventing
Squid from logging EUI-48 and EUI-64 values properly. A blank MAC
address has been logged instead.

There remain some design issues surrounding EUI48/64 mapping which will
be fixed in later releases.

* logformat annotation redesign

NOTICE:
 This change may affect log analysis or other processing tools.

The output produced by the logformat %note token in earlier releases
included uncecessary URL-encoded quotations and value delimiters.
This release removes the quotation and makes the delimiter configurable
to produce much cleaner log content.

* Squid Project welcomes Android builds

With a remarkably simple addition we are pleased to announce support for
building Squid on Android, or cross-compiling for Android is now
supported. We look forward to seeing what will happen in this new arena.

 All users of Squid-3.4 are encouraged to upgrade to this release as
soon as possible.

 All users of older Squid versions are urged to upgrade as soon as
possible.

 See the ChangeLog for the full list of changes in this and earlier
 releases.

Please refer to the release notes at
http://www.squid-cache.org/Versions/v3/3.4/RELEASENOTES.html
when you are ready to make the switch to Squid-3.4

Upgrade tip:
  "squid -k parse" is starting to display even more
   useful hints about squid.conf changes.

This new release can be downloaded from our HTTP or FTP servers

 http://www.squid-cache.org/Versions/v3/3.4/
 ftp://ftp.squid-cache.org/pub/squid/
 ftp://ftp.squid-cache.org/pub/archive/3.4/

or the mirrors. For a list of mirror sites see

 http://www.squid-cache.org/Download/http-mirrors.html
 http://www.squid-cache.org/Download/mirrors.html

If you encounter any issues with this release please file a bug report.
http://bugs.squid-cache.org/

Amos Jeffries

This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement,
you may review at http://www.amdocs.com/email_disclaimer.asp
Received on Mon May 05 2014 - 14:09:20 MDT