On 22.07.2010 11:28, Paul Querna wrote:
On Thu, Jul 22, 2010 at 12:23 AM, Rainer Jung<rainer.j...@kippdata.de> wrote:
On 22.07.2010 07:46, Ruediger Pluem wrote:
On 07/22/2010 06:10 AM, William A. Rowe Jr. wrote:
On 7/21/2010 10:09 PM, Rainer Jung wrote:
On 22.07.2010 04:52, Paul Querna wrote:
Ack-- I could re-tag with libtool 1.x, if we don't want to ship a
modified apr-util.
I always use an external expat it seems :(
Thoughts?
For the ASF release re-tag would be enough. There's a few people though,
that already ran into the same problem with 2.2.15 (BZ49053). It's
possible some distros might run buildconf before providing their source
bundles, but it could also just have been those users themselves. The
info given in the issue does not clarify this.
Since the buildconf bug itself is not a regression and there are well
known workarounds I would say re-tag and fix with 2.2.17.
AIUI - this is a reroll, but the tag remains the same? If the source
files
in svn are nonvolatile, then going with libtool 1.x might be the ticket.
+1 to reroll. The tag can stay the same.
Don't know why Paul and me both used the wording re-tag when talking about a
procedure that doesn't change the svn sources. So yes, I meant re-roll.
re-rolled using libtool 1.x, tarballs in the same places.
EU mirror was updated quickly, but US mirror still shows the old files.
New ones are dated "22-Jul-2010 09:23", httpd-2.2.16.tar.gz.md5 is:
7f33f2c8b213ad758c009ae46d2795ed *httpd-2.2.16.tar.gz
Rainer
