[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: 1.3.0 tarballs up for testing/signing

From: David Anderson <david.anderson_at_calixo.net>
Date: 2005-12-30 07:46:22 CET

[Cc-ing back to the dev@ list]

Brent Graveland wrote:
> Correct me if I'm wrong, but the core.c files in subversion/bindings/
> swig/* still call this a -dev build (SVN_VER_TAG), and SVN_VER_NUMTAG
> is still 0.
> I'd guess the swig files need to be regenerated, right?

This is strange. It looks like the bindings should be regenerated, and yet the
version file is edited before the bindings code is generated in the distribution
script. That means SWIG should be picking up the right values (the wrong values
have been wiped just previous), and still manage to snatch defeat from the jaws
of victory.

Hmm, looking at it more closely... Okay, the fix (edit svn_version.h earlier in
the release process) is in trunk, but hasn't been merged to 1.3.x, and I'm
rolling using the 1.3.x dist.sh. Damn.

I'll reroll in the morning... Well, it is the morning, but when I get up.
Unless by then you've decided having wrong version numbers in swig code is not
that evil (which I doubt).

Committers, I think I can safely say (famous last words) that if your tests
passed on this tarball, reordering stuff shouldn't suddenly start breaking tests
- If my new tarball configures and builds, I think we can call it as "works".

Thanks for finding this,
- Dave.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Dec 30 07:47:11 2005

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.