You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by "Hyrum K. Wright" <hy...@mail.utexas.edu> on 2009/02/16 21:14:17 UTC
1.6.0-rc1 tarballs up for signing/testing
Good afternoon,
I'm pleased to announce that Subversion 1.6.0-rc1 is up for testing
and signing. The magic revision is r35896.
http://orac.ece.utexas.edu/pub/svn/1.6.0-rc1/
As usual, signatures from full committers back to me, and enthusiastic
tester feedback is welcome. At this point, this candidate is not yet
blessed for wide release, so please don't make it available to people
not interested in test-driving the new release. Please especially
test the serf RA layer, and consider including it in your typical
testing routine.
Distro package maintainers, please to NOT include any pre-release
builds, even blessed, into operating system distros. The reasons for
not doing so were very eloquently outlined by Karl in a mail, which is
summarized at the above address.
The quick version is: we don't guarantee compatibility between the pre-
releases and the final release, so if people install the release
candidate, all their repositories and working copies might break
unrepairably when they upgrade to 1.6.0 proper. We don't want that
kind of bad publicity, and neither do you.
-Hyrum
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1173277
Re: 1.6.0-rc1 tarballs up for signing/testing
Posted by Branko Cibej <br...@xbc.nu>.
Paul Burba wrote:
> On Thu, Feb 19, 2009 at 9:48 AM, Branko Cibej <br...@xbc.nu> wrote:
>
>> Branko Čibej wrote:
>>
>>> All tests pass except fs-test 18 over BDB:
>>>
>>> svn_tests: Berkeley DB error for filesystem
>>> 'test-repo-merging-commit' while reading filesystem revision:
>>> Invalid argument
>>> svn_tests: bdb: illegal record number of 0
>>> FAIL: lt-fs-test 18: merging commit
>>>
>>>
>> What's the deal with this test anyway? Why is it expected to fail, and
>> if so, why is it not marked as XFail?
>>
>> -- Brane
>>
>
> Hi Brane,
>
> You might have missed this from earlier in this thread:
>
> On Wed, Feb 18, 2009 at 9:48 AM, Paul Burba <pt...@gmail.com> wrote:
>
>
>> [ bdb ] x [ file ]
>>
>> FAIL: fs-test.exe 18: merging commit
>>
>> The XFail on this test was incorrectly removed in r35347. It was set
>> back to XFail on trunk in r35945 (see also r35948).
>>
Oh! Thanks; sorry for the noise.
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1192304
Re: 1.6.0-rc1 tarballs up for signing/testing
Posted by Paul Burba <pt...@gmail.com>.
On Thu, Feb 19, 2009 at 9:48 AM, Branko Cibej <br...@xbc.nu> wrote:
> Branko Čibej wrote:
>> All tests pass except fs-test 18 over BDB:
>>
>> svn_tests: Berkeley DB error for filesystem
>> 'test-repo-merging-commit' while reading filesystem revision:
>> Invalid argument
>> svn_tests: bdb: illegal record number of 0
>> FAIL: lt-fs-test 18: merging commit
>>
>
> What's the deal with this test anyway? Why is it expected to fail, and
> if so, why is it not marked as XFail?
>
> -- Brane
Hi Brane,
You might have missed this from earlier in this thread:
On Wed, Feb 18, 2009 at 9:48 AM, Paul Burba <pt...@gmail.com> wrote:
> [ bdb ] x [ file ]
>
> FAIL: fs-test.exe 18: merging commit
>
> The XFail on this test was incorrectly removed in r35347. It was set
> back to XFail on trunk in r35945 (see also r35948).
Paul
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1192259
Re: 1.6.0-rc1 tarballs up for signing/testing
Posted by Branko Cibej <br...@xbc.nu>.
Branko Čibej wrote:
> All tests pass except fs-test 18 over BDB:
>
> svn_tests: Berkeley DB error for filesystem
> 'test-repo-merging-commit' while reading filesystem revision:
> Invalid argument
> svn_tests: bdb: illegal record number of 0
> FAIL: lt-fs-test 18: merging commit
>
What's the deal with this test anyway? Why is it expected to fail, and
if so, why is it not marked as XFail?
-- Brane
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1192178
Re: 1.6.0-rc1 tarballs up for signing/testing
Posted by Branko Cibej <br...@xbc.nu>.
Summary:
+0 to release.
Platform:
Linux; Ubuntu 8.10 (intrepid)
Tested:
1.6.0-rc1 tarball with dependencies from the standard distro
-- this means no serf testing, as the serf lib in intrepid is too old.
(local,svn,neon) x (fsfs,bdb)
Verified md5sums and sha1sums
Verified that .tar.gz and .tar.bz2 archives unpack to identical trees.
Results:
All tests pass except fs-test 18 over BDB:
svn_tests: Berkeley DB error for filesystem
'test-repo-merging-commit' while reading filesystem revision:
Invalid argument
svn_tests: bdb: illegal record number of 0
FAIL: lt-fs-test 18: merging commit
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1192162
Re: 1.6.0-rc1 tarballs up for signing/testing
Posted by Paul Burba <pt...@gmail.com>.
On Mon, Feb 16, 2009 at 4:14 PM, Hyrum K. Wright
<hy...@mail.utexas.edu> wrote:
> Good afternoon,
>
> I'm pleased to announce that Subversion 1.6.0-rc1 is up for testing
> and signing. The magic revision is r35896.
>
> http://orac.ece.utexas.edu/pub/svn/1.6.0-rc1/
>
> As usual, signatures from full committers back to me, and enthusiastic
> tester feedback is welcome. At this point, this candidate is not yet
> blessed for wide release, so please don't make it available to people
> not interested in test-driving the new release. Please especially
> test the serf RA layer, and consider including it in your typical
> testing routine.
>
> Distro package maintainers, please to NOT include any pre-release
> builds, even blessed, into operating system distros. The reasons for
> not doing so were very eloquently outlined by Karl in a mail, which is
> summarized at the above address.
>
> The quick version is: we don't guarantee compatibility between the pre-
> releases and the final release, so if people install the release
> candidate, all their repositories and working copies might break
> unrepairably when they upgrade to 1.6.0 proper. We don't want that
> kind of bad publicity, and neither do you.
>
> -Hyrum
TESTED:
-------
[ fsfs | bdb ] x [ file | svn | http (neon) ]
JavaHL Bindings
SUCCESSFULLY BUILT BUT NOT TESTED:
----------------------------------
Python Bindings
Perl Bindings
SUMMARY:
--------
+1 to release.
RESULTS:
--------
JavaHL: Pass
[ fsfs | bdb ] x [ file | svn | http (neon) ]: All pass except as noted below:
[ fsfs | bdb ] x [ file | svn | http (neon) ]
basic_tests.py 12: 'basic revert command' failed due a problem with
that test on Windows with Python 2.5+. I fixed this on trunk in
r35930. With that fix applied to 1.6.x this test passed all
variations. As this was simply a problem with the test suite it does
not prevent release.
[ bdb ] x [ http (neon) ]
FAIL: tree_conflict_tests.py 10: merge file: del/rpl/mv onto not-same
FAIL: tree_conflict_tests.py 11: merge file: del/rpl/mv onto not-file
FAIL: tree_conflict_tests.py 12: merge file: add onto not-none
FAIL: tree_conflict_tests.py 16: merge dir: add onto not-none
[ bdb ] x [ svn ]
FAIL: tree_conflict_tests.py 9: merge file: modify onto not-file
FAIL: tree_conflict_tests.py 10: merge file: del/rpl/mv onto not-same
FAIL: tree_conflict_tests.py 11: merge file: del/rpl/mv onto not-file
FAIL: tree_conflict_tests.py 12: merge file: add onto not-none
FAIL: tree_conflict_tests.py 13: merge dir: modify onto not-dir
FAIL: tree_conflict_tests.py 16: merge dir: add onto not-none
All of the above tree_conflict_tests.py failures were due to the
inability of the tests to delete the repository when building multiple
sandboxes. I fixed this on trunk in r35943. After merging that
change to 1.6.x all of these tests passed. Again, this was a problem
with the test suite and is not sufficient to stop release.
[ bdb ] x [ file ]
FAIL: fs-test.exe 18: merging commit
The XFail on this test was incorrectly removed in r35347. It was set
back to XFail on trunk in r35945 (see also r35948). In the course of
investigating these failures I found a bug in the fsfs implementation
of svn_fs_commit_txn(): If the commit failed, the *NEW_REV argument
was not set to SVN_INVALID_REVNUM as the API promises:
* @note Success or failure of the commit of @a txn is determined by
* examining the value of @a *new_rev upon this function's return. If
* the value is a valid revision number, the commit was successful,
* even though a non-@c NULL function return value may indicate that
* something else went wrong.
*/
svn_error_t *
svn_fs_commit_txn(const char **conflict_p,
svn_revnum_t *new_rev,
svn_fs_txn_t *txn,
apr_pool_t *pool);
This was fixed in r35950, but given that this bug has existed since
the dawn of FSFS in 1.1.0, it seems all callers are relying on the
returned error and/or the value of **CONFLICT_P rather than the value
of *NEW_REV. So nominating this for backport to 1.6.1 seems
sufficient.
VERIFIED:
-------
http://orac.ece.utexas.edu/pub/svn/1.6.0-rc1/stingray/subversion-1.6.0-rc1.zip:
MD5:
SHA1: f05c3ae8d3223cccc6991dbd670d4b68def8febe
Excepting subversion/include/svn_version.h the contents of
http://orac.ece.utexas.edu/pub/svn/1.6.0-rc1/stingray/subversion-1.6.0-rc1.zip
match http://svn.collab.net/repos/svn/branches/1.6.x@35896.
PLATFORM:
---------
Microsoft Windows XP Professional Service Pack 3 (Build 2600)
AMD Athlon(tm) 64 X2 Dual Core Processor 4400+ 2211.2 Mhz 2 GB RAM
Microsoft Visual Studio 2008 Professional Version 9.0.21022.8 RTM
Microsoft .NET Framework Version 3.5
DEPENDENCIES:
-------------
APR: 1.3.3
APR-UTIL: 1.3.4
Neon: 0.28.2
zlib: 1.2.3
OpenSSL: 0.9.8h
Apache: 2.2.10
BDB: 4.7.25
sqlite: 3.6.10
Python: ActivePython 2.6.1.1
java: 1.6.0_07
swig: 1.3.36
SIGNATURE:
-----------
user: "Paul T. Burba <pt...@gmail.com>"
1024-bit DSA key, ID 53FCDC55, created 2006-06-21
http://orac.ece.utexas.edu/pub/svn/1.6.0-rc1/stingray/subversion-1.6.0-rc1.zip:
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (MingW32)
iD8DBQBJmtXc2RaJMFP83FURAsZ7AJ420xEXCtMfXeqNLyF74bxc7rLiqACdHIWE
emJePmbTb+7LZF1Euko2Czw=
=hCN4
-----END PGP SIGNATURE-----
Paul
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1186391
Re: 1.6.0-rc1 tarballs up for signing/testing
Posted by "C. Michael Pilato" <cm...@collab.net>.
Hyrum K. Wright wrote:
> Good afternoon,
>
> I'm pleased to announce that Subversion 1.6.0-rc1 is up for testing
> and signing. The magic revision is r35896.
>
> http://orac.ece.utexas.edu/pub/svn/1.6.0-rc1/
Summary:
+1 to release.
Platform:
Ubuntu 8.10 (intrepid) Linux.
Tested:
1.6.0-rc1 tarball with local dependencies (not from deps tarball)
(local,svn,serf,neon) x (fsfs,bdb) + py + rb + javahl
Results:
All tests pass *except* fs-test 18 over BDB, which is exactly what is
expected of this tarball based on current knowledge of the codebase.
MD5 Checksums:
a78b51fceec431ed4a5cc775bf94f56b subversion-1.6.0-rc1.tar.bz2
d1e88c271dc37de60c9162439c5c7570 subversion-1.6.0-rc1.tar.gz
cc79fb5d5a5f7178b9da1a8bba643517 subversion-deps-1.6.0-rc1.tar.bz2
e4acc971396b742e7870542485d7145b subversion-deps-1.6.0-rc1.tar.gz
GPG Signatures:
::: subversion-1.6.0-rc1.tar.bz2.asc :::
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEABECAAYFAkmcSqcACgkQokEGqRcG/W5oSQCgm//6VRM2wK/LH3R01ANp2uYY
JgMAoM6TqPLs3sGtSTMerzsRIe0ufU2q
=uPu/
-----END PGP SIGNATURE-----
::: subversion-1.6.0-rc1.tar.gz.asc :::
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEABECAAYFAkmcSqsACgkQokEGqRcG/W6b+gCgpgIUNiF4yqd17qCe7cYhqui3
Zx4AoI1/itaI9XmAFt/X35yAwxw3fx2k
=M6g+
-----END PGP SIGNATURE-----
::: subversion-deps-1.6.0-rc1.tar.bz2.asc :::
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEABECAAYFAkmcSqgACgkQokEGqRcG/W6jgQCfcohzw65i/wEG64cha7tRrQq2
WW4AoLjpnoiVZGB3GYmPbThb8moQxSmf
=L8mR
-----END PGP SIGNATURE-----
::: subversion-deps-1.6.0-rc1.tar.gz.asc :::
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEABECAAYFAkmcSq0ACgkQokEGqRcG/W6AGQCgpBCiSjH1svTiwmjq1MJvStMS
m0QAoIgUMN4ZfY/ivG3PEEvnABtxb4V1
=2Epy
-----END PGP SIGNATURE-----
--
C. Michael Pilato <cm...@collab.net>
CollabNet <> www.collab.net <> Distributed Development On Demand
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1187510
Re: 1.6.0-rc1 tarballs up for signing/testing
Posted by Mark Phippard <ma...@gmail.com>.
Here are my signatures for Windows.
Platform: XP-SP3 with MSVC 6
Tested:
JavaHL
ra_local X fsfs | BDB
ra_svn X fsfs | BDB
Results:
No problems with fsfs
BDB had some problems that look like problems in the tests, not the application.
ra_local:
FAIL: lt-fs-test 18: merging commit
ra_svn:
Do not have results handy but there were 7 tree conflict test
failures. Looking in the logs, it was a recurrence of a problem we've
had in Windows tests in the past where they get an error deleting the
repository as part of cleanup. We had this problem in 1.5 too,
although someone eventually fixed this. So hopefully something
similar can be done.
I do not feel like this should block the release, so I am attaching my sigs.
subversion-1.6.0-rc1.zip
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)
iEYEABECAAYFAkmayz4ACgkQJl34oANalqkShgCghHCk+cqfB0MEoG7VIvBR1pBE
GUsAnjXYN29MEPnFxxFp/5qjgNQAcpjd
=wIQC
-----END PGP SIGNATURE-----
subversion-deps-1.6.0-rc1.zip
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)
iEYEABECAAYFAkmay0gACgkQJl34oANalqmJPACeNkF+M94aAO/xow9BsYqqgrK/
PxQAn2SBRo63XMyLliFKVNoBDwzMMeh+
=wotR
-----END PGP SIGNATURE-----
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1179268
RE: 1.6.0-rc1 tarballs up for signing/testing
Posted by Bert Huijben <rh...@sharpsvn.net>.
> -----Original Message-----
> From: Bert Huijben [mailto:rhuijben@sharpsvn.net]
> Sent: woensdag 18 februari 2009 23:44
> To: dev@subversion.tigris.org; 'Hyrum K. Wright'
> Subject: RE: 1.6.0-rc1 tarballs up for signing/testing
>
> > -----Original Message-----
> > From: Arfrever Frehtes Taifersar Arahesis
> > [mailto:Arfrever.FTA@GMail.Com]
> > Sent: Wednesday, February 18, 2009 10:27 PM
> > To: Hyrum K. Wright; dev@subversion.tigris.org
> > Subject: Re: 1.6.0-rc1 tarballs up for signing/testing
> >
> > SUMMARY:
> >
> > +1 to release.
> >
> > TESTED:
> >
> > [ fsfs | bdb ] x [ ra_local | ra_svn | ra_neon | ra_serf ]
> > ctypes-python
> > swig-pl
> > swig-py
> > swig-rb
> > javahl
> >
> > RESULTS:
> >
> > All tests passed except:
> >
> > bdb x [ ra_local | ra_svn | ra_neon | ra_serf ]: fs-test 18:
> > merging commit
> > [ fsfs | bdb ] x ra_neon: commit_tests.py 54: 'svn commit --
> > changelist=foo' above a conflict
> > [ fsfs | bdb ] x ra_neon: copy_tests.py 34: delete file scheduled
> > for replace
> > [ fsfs | bdb ] x ra_serf: externals_tests.py 3: update to lose an
> > external module
> > [ fsfs | bdb ] x ra_serf: externals_tests.py 6: update changes
> > under an external module
> > [ fsfs | bdb ] x ra_serf: externals_tests.py 7: commit and update
> > additional externals
> > [ fsfs | bdb ] x ra_serf: externals_tests.py 16: place a file
> > external into a directory external
> > [ fsfs | bdb ] x ra_serf: svnsync_tests.py 15: verify that copies
> > from unreadable dirs work
>
> 2:52 <@Bert> Arfrever provided a +1 for release with 2 neon and 5 serf
> failures.. (And I'm still looking at that
> ra_neon crash)
> 22:52 <@Arfrever> Bert: I assumed that ra_serf is still experimental :)
> 22:53 <@gstein> ra_serf should be considered "supported"
> 22:53 <@gstein> it *works* after all
> 22:53 <@Arfrever> But 5 tests failed...
> 22:54 <@gstein> on all platforms? or is that something spcific to windows
> and/or bert's system?
> 22:55 <@gstein> oh. wait. your system.
> 22:56 <@Arfrever> externals_tests.py 3: abort
> 22:56 <@Arfrever> externals_tests.py 6: abort
> 22:56 <@Arfrever> externals_tests.py 7: abort
> 22:56 <@Arfrever> externals_tests.py 16: abort
> 22:56 <@Arfrever> svnsync_tests.py 15: abort
>
> If these are not local errors at Arfever, I think we should fix these
issues
> before release.
After r35968, I vote -0 on releasing rc0 as a release candidate and -1 on
releasing this version as 1.6.0.
And I'll continue running the tests to get more information on the serf
aborts I got. (Both neon failures are gone after merging r35968)
Bert
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1191176
Re: 1.6.0-rc1 tarballs up for signing/testing
Posted by Arfrever Frehtes Taifersar Arahesis <Ar...@GMail.Com>.
2009-02-18 23:56:18 Mark Phippard napisał(a):
> On Wed, Feb 18, 2009 at 5:44 PM, Bert Huijben <rh...@sharpsvn.net> wrote:
> >> -----Original Message-----
> >> From: Arfrever Frehtes Taifersar Arahesis
> >> [mailto:Arfrever.FTA@GMail.Com]
> >> Sent: Wednesday, February 18, 2009 10:27 PM
> >> To: Hyrum K. Wright; dev@subversion.tigris.org
> >> Subject: Re: 1.6.0-rc1 tarballs up for signing/testing
> >>
> >> SUMMARY:
> >>
> >> +1 to release.
> >>
> >> TESTED:
> >>
> >> [ fsfs | bdb ] x [ ra_local | ra_svn | ra_neon | ra_serf ]
> >> ctypes-python
> >> swig-pl
> >> swig-py
> >> swig-rb
> >> javahl
> >>
> >> RESULTS:
> >>
> >> All tests passed except:
> >>
> >> bdb x [ ra_local | ra_svn | ra_neon | ra_serf ]: fs-test 18:
> >> merging commit
> >> [ fsfs | bdb ] x ra_neon: commit_tests.py 54: 'svn commit --
> >> changelist=foo' above a conflict
> >> [ fsfs | bdb ] x ra_neon: copy_tests.py 34: delete file scheduled
> >> for replace
> >> [ fsfs | bdb ] x ra_serf: externals_tests.py 3: update to lose an
> >> external module
> >> [ fsfs | bdb ] x ra_serf: externals_tests.py 6: update changes
> >> under an external module
> >> [ fsfs | bdb ] x ra_serf: externals_tests.py 7: commit and update
> >> additional externals
> >> [ fsfs | bdb ] x ra_serf: externals_tests.py 16: place a file
> >> external into a directory external
> >> [ fsfs | bdb ] x ra_serf: svnsync_tests.py 15: verify that copies
> >> from unreadable dirs work
> >
> > 2:52 <@Bert> Arfrever provided a +1 for release with 2 neon and 5 serf
> > failures.. (And I'm still looking at that
> > ra_neon crash)
> > 22:52 <@Arfrever> Bert: I assumed that ra_serf is still experimental :)
> > 22:53 <@gstein> ra_serf should be considered "supported"
> > 22:53 <@gstein> it *works* after all
> > 22:53 <@Arfrever> But 5 tests failed...
> > 22:54 <@gstein> on all platforms? or is that something spcific to windows
> > and/or bert's system?
> > 22:55 <@gstein> oh. wait. your system.
> > 22:56 <@Arfrever> externals_tests.py 3: abort
> > 22:56 <@Arfrever> externals_tests.py 6: abort
> > 22:56 <@Arfrever> externals_tests.py 7: abort
> > 22:56 <@Arfrever> externals_tests.py 16: abort
> > 22:56 <@Arfrever> svnsync_tests.py 15: abort
> >
> > If these are not local errors at Arfever, I think we should fix these issues
> > before release.
>
> The buildbot passed all tests for serf and neon as did cmpilato and
> Senthil.
The buildbot was also passing all ra_serf tests when I reported segmentation
fault during merge_tests.py "merge fails if subtree is deleted on src":
http://svn.haxx.se/dev/archive-2008-12/0381.shtml
http://svn.haxx.se/dev/archive-2008-12/0383.shtml
http://svn.haxx.se/dev/archive-2008-12/0384.shtml
http://svn.haxx.se/dev/archive-2008-12/0447.shtml
--
Arfrever Frehtes Taifersar Arahesis
Re: 1.6.0-rc1 tarballs up for signing/testing
Posted by Paul Burba <pt...@gmail.com>.
On Wed, Feb 18, 2009 at 5:56 PM, Mark Phippard <ma...@gmail.com> wrote:
> On Wed, Feb 18, 2009 at 5:44 PM, Bert Huijben <rh...@sharpsvn.net> wrote:
>>> -----Original Message-----
>>> From: Arfrever Frehtes Taifersar Arahesis
>>> [mailto:Arfrever.FTA@GMail.Com]
>>> Sent: Wednesday, February 18, 2009 10:27 PM
>>> To: Hyrum K. Wright; dev@subversion.tigris.org
>>> Subject: Re: 1.6.0-rc1 tarballs up for signing/testing
>>>
>>> SUMMARY:
>>>
>>> +1 to release.
>>>
>>> TESTED:
>>>
>>> [ fsfs | bdb ] x [ ra_local | ra_svn | ra_neon | ra_serf ]
>>> ctypes-python
>>> swig-pl
>>> swig-py
>>> swig-rb
>>> javahl
>>>
>>> RESULTS:
>>>
>>> All tests passed except:
>>>
>>> bdb x [ ra_local | ra_svn | ra_neon | ra_serf ]: fs-test 18:
>>> merging commit
>>> [ fsfs | bdb ] x ra_neon: commit_tests.py 54: 'svn commit --
>>> changelist=foo' above a conflict
>>> [ fsfs | bdb ] x ra_neon: copy_tests.py 34: delete file scheduled
>>> for replace
>>> [ fsfs | bdb ] x ra_serf: externals_tests.py 3: update to lose an
>>> external module
>>> [ fsfs | bdb ] x ra_serf: externals_tests.py 6: update changes
>>> under an external module
>>> [ fsfs | bdb ] x ra_serf: externals_tests.py 7: commit and update
>>> additional externals
>>> [ fsfs | bdb ] x ra_serf: externals_tests.py 16: place a file
>>> external into a directory external
>>> [ fsfs | bdb ] x ra_serf: svnsync_tests.py 15: verify that copies
>>> from unreadable dirs work
>>
>> 2:52 <@Bert> Arfrever provided a +1 for release with 2 neon and 5 serf
>> failures.. (And I'm still looking at that
>> ra_neon crash)
>> 22:52 <@Arfrever> Bert: I assumed that ra_serf is still experimental :)
>> 22:53 <@gstein> ra_serf should be considered "supported"
>> 22:53 <@gstein> it *works* after all
>> 22:53 <@Arfrever> But 5 tests failed...
>> 22:54 <@gstein> on all platforms? or is that something spcific to windows
>> and/or bert's system?
>> 22:55 <@gstein> oh. wait. your system.
>> 22:56 <@Arfrever> externals_tests.py 3: abort
>> 22:56 <@Arfrever> externals_tests.py 6: abort
>> 22:56 <@Arfrever> externals_tests.py 7: abort
>> 22:56 <@Arfrever> externals_tests.py 16: abort
>> 22:56 <@Arfrever> svnsync_tests.py 15: abort
>>
>> If these are not local errors at Arfever, I think we should fix these issues
>> before release.
>
> The buildbot passed all tests for serf and neon as did cmpilato and
> Senthil. Also, all Neon and Serf tests passed for pburba, except for
> the BDB tests he reported and has since fixed in the test suite.
Minor correction, I didn't test serf.
Paul
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1188638
Re: 1.6.0-rc1 tarballs up for signing/testing
Posted by Mark Phippard <ma...@gmail.com>.
On Wed, Feb 18, 2009 at 5:44 PM, Bert Huijben <rh...@sharpsvn.net> wrote:
>> -----Original Message-----
>> From: Arfrever Frehtes Taifersar Arahesis
>> [mailto:Arfrever.FTA@GMail.Com]
>> Sent: Wednesday, February 18, 2009 10:27 PM
>> To: Hyrum K. Wright; dev@subversion.tigris.org
>> Subject: Re: 1.6.0-rc1 tarballs up for signing/testing
>>
>> SUMMARY:
>>
>> +1 to release.
>>
>> TESTED:
>>
>> [ fsfs | bdb ] x [ ra_local | ra_svn | ra_neon | ra_serf ]
>> ctypes-python
>> swig-pl
>> swig-py
>> swig-rb
>> javahl
>>
>> RESULTS:
>>
>> All tests passed except:
>>
>> bdb x [ ra_local | ra_svn | ra_neon | ra_serf ]: fs-test 18:
>> merging commit
>> [ fsfs | bdb ] x ra_neon: commit_tests.py 54: 'svn commit --
>> changelist=foo' above a conflict
>> [ fsfs | bdb ] x ra_neon: copy_tests.py 34: delete file scheduled
>> for replace
>> [ fsfs | bdb ] x ra_serf: externals_tests.py 3: update to lose an
>> external module
>> [ fsfs | bdb ] x ra_serf: externals_tests.py 6: update changes
>> under an external module
>> [ fsfs | bdb ] x ra_serf: externals_tests.py 7: commit and update
>> additional externals
>> [ fsfs | bdb ] x ra_serf: externals_tests.py 16: place a file
>> external into a directory external
>> [ fsfs | bdb ] x ra_serf: svnsync_tests.py 15: verify that copies
>> from unreadable dirs work
>
> 2:52 <@Bert> Arfrever provided a +1 for release with 2 neon and 5 serf
> failures.. (And I'm still looking at that
> ra_neon crash)
> 22:52 <@Arfrever> Bert: I assumed that ra_serf is still experimental :)
> 22:53 <@gstein> ra_serf should be considered "supported"
> 22:53 <@gstein> it *works* after all
> 22:53 <@Arfrever> But 5 tests failed...
> 22:54 <@gstein> on all platforms? or is that something spcific to windows
> and/or bert's system?
> 22:55 <@gstein> oh. wait. your system.
> 22:56 <@Arfrever> externals_tests.py 3: abort
> 22:56 <@Arfrever> externals_tests.py 6: abort
> 22:56 <@Arfrever> externals_tests.py 7: abort
> 22:56 <@Arfrever> externals_tests.py 16: abort
> 22:56 <@Arfrever> svnsync_tests.py 15: abort
>
> If these are not local errors at Arfever, I think we should fix these issues
> before release.
The buildbot passed all tests for serf and neon as did cmpilato and
Senthil. Also, all Neon and Serf tests passed for pburba, except for
the BDB tests he reported and has since fixed in the test suite.
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1188545
RE: 1.6.0-rc1 tarballs up for signing/testing
Posted by Bert Huijben <rh...@sharpsvn.net>.
> -----Original Message-----
> From: Arfrever Frehtes Taifersar Arahesis
> [mailto:Arfrever.FTA@GMail.Com]
> Sent: Wednesday, February 18, 2009 10:27 PM
> To: Hyrum K. Wright; dev@subversion.tigris.org
> Subject: Re: 1.6.0-rc1 tarballs up for signing/testing
>
> SUMMARY:
>
> +1 to release.
>
> TESTED:
>
> [ fsfs | bdb ] x [ ra_local | ra_svn | ra_neon | ra_serf ]
> ctypes-python
> swig-pl
> swig-py
> swig-rb
> javahl
>
> RESULTS:
>
> All tests passed except:
>
> bdb x [ ra_local | ra_svn | ra_neon | ra_serf ]: fs-test 18:
> merging commit
> [ fsfs | bdb ] x ra_neon: commit_tests.py 54: 'svn commit --
> changelist=foo' above a conflict
> [ fsfs | bdb ] x ra_neon: copy_tests.py 34: delete file scheduled
> for replace
> [ fsfs | bdb ] x ra_serf: externals_tests.py 3: update to lose an
> external module
> [ fsfs | bdb ] x ra_serf: externals_tests.py 6: update changes
> under an external module
> [ fsfs | bdb ] x ra_serf: externals_tests.py 7: commit and update
> additional externals
> [ fsfs | bdb ] x ra_serf: externals_tests.py 16: place a file
> external into a directory external
> [ fsfs | bdb ] x ra_serf: svnsync_tests.py 15: verify that copies
> from unreadable dirs work
2:52 <@Bert> Arfrever provided a +1 for release with 2 neon and 5 serf
failures.. (And I'm still looking at that
ra_neon crash)
22:52 <@Arfrever> Bert: I assumed that ra_serf is still experimental :)
22:53 <@gstein> ra_serf should be considered "supported"
22:53 <@gstein> it *works* after all
22:53 <@Arfrever> But 5 tests failed...
22:54 <@gstein> on all platforms? or is that something spcific to windows
and/or bert's system?
22:55 <@gstein> oh. wait. your system.
22:56 <@Arfrever> externals_tests.py 3: abort
22:56 <@Arfrever> externals_tests.py 6: abort
22:56 <@Arfrever> externals_tests.py 7: abort
22:56 <@Arfrever> externals_tests.py 16: abort
22:56 <@Arfrever> svnsync_tests.py 15: abort
If these are not local errors at Arfever, I think we should fix these issues
before release.
My current test status is [fsfs | bdb] x [ local | svn ] ok on Windows Vista
But I see svn.exe crashes in both ra_neon and ra_serf running the tests and
until I can explain these issues as local glitch I will not vote for
release.
Bert
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1188506
Re: 1.6.0-rc1 tarballs up for signing/testing
Posted by Arfrever Frehtes Taifersar Arahesis <Ar...@GMail.Com>.
SUMMARY:
+1 to release.
TESTED:
[ fsfs | bdb ] x [ ra_local | ra_svn | ra_neon | ra_serf ]
ctypes-python
swig-pl
swig-py
swig-rb
javahl
RESULTS:
All tests passed except:
bdb x [ ra_local | ra_svn | ra_neon | ra_serf ]: fs-test 18: merging commit
[ fsfs | bdb ] x ra_neon: commit_tests.py 54: 'svn commit --changelist=foo' above a conflict
[ fsfs | bdb ] x ra_neon: copy_tests.py 34: delete file scheduled for replace
[ fsfs | bdb ] x ra_serf: externals_tests.py 3: update to lose an external module
[ fsfs | bdb ] x ra_serf: externals_tests.py 6: update changes under an external module
[ fsfs | bdb ] x ra_serf: externals_tests.py 7: commit and update additional externals
[ fsfs | bdb ] x ra_serf: externals_tests.py 16: place a file external into a directory external
[ fsfs | bdb ] x ra_serf: svnsync_tests.py 15: verify that copies from unreadable dirs work
ctypes-python with Python 2.6.*: All tests
javahl: testDiff (Test broken with non-English locale.)
SYSTEM:
Gentoo GNU/Linux (~amd64)
GLibC 2.9_p20081201
GCC 4.3.3
GNU Binutils 2.19.51.0.2
DEPENDENCIES:
APR 1.4 (1.4.x branch)
APR-Util 1.4 (1.4.x branch)
Neon 0.29_pre1626 (trunk r1626)
Serf 0.3.1_pre1218 (trunk r1218)
GnuTLS 2.7.5
OpenSSL 0.9.8j
Apache 2.4 (trunk)
Berkeley DB 4.7.25_p1
Ctypesgen r68
Perl 5.8.8
Python 2.5.4 (ctypes-python only)
Python 2.6.1 (ctypes-python and swig-py)
Ruby 1.8.6_p287
Sun JDK 1.6.0.12
JUnit 4.5
SHA1 CHECKSUMS:
46fc00c32e68b5487306a36fbd90632b7db5d236 subversion-1.6.0-rc1.tar.bz2
56b01bd6849cea8640b1198f856a3de73e2ce8fa subversion-1.6.0-rc1.tar.gz
GPG SIGNATURES:
::: subversion-1.6.0-rc1.tar.bz2 :::
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.10 (GNU/Linux)
iEYEABECAAYFAkmceo4ACgkQYM9qgQ/zOWMY2ACgsJwp0VQ2SbRO13pJ5gvDu1LM
NOEAn33K2d6kUHCmddKCWTnHrJwn5Mam
=kdkd
-----END PGP SIGNATURE-----
::: subversion-1.6.0-rc1.tar.gz :::
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.10 (GNU/Linux)
iEYEABECAAYFAkmcepQACgkQYM9qgQ/zOWN52wCgrkhGGxbjiSbxXreY7r8WWhiH
+koAn1x4Wpv8p2fi3DP8bf8lCKaEF0SE
=RvDl
-----END PGP SIGNATURE-----
GPG KEY:
Arfrever Frehtes Taifersar Arahesis [1024D/0FF33963] with fingerprint:
F699 87DA C1B7 BF23 B85F 13A5 60CF 6A81 0FF3 3963
--
Arfrever Frehtes Taifersar Arahesis
Re: 1.6.0-rc1 tarballs up for signing/testing
Posted by Karl Heinz Marbaise <kh...@gmx.de>.
Hi there,
i have tested the tarballs on Mac OS 10.5.6 with Darwin Ports...
mac:subversion-1.6.0-rc1 km$ ./configure
mac:subversion-1.6.0-rc1 km$ make
mac:subversion-1.6.0-rc1 km$ make check
Running all tests in auth-test [1/67]...success
Running all tests in cache-test [2/67]...success
Running all tests in checksum-test [3/67]...success
Running all tests in client-test [4/67]...success
Running all tests in compat-test [5/67]...success
Running all tests in config-test [6/67]...success
Running all tests in diff-diff3-test [7/67]...success
Running all tests in dirent_uri-test [8/67]...success
Running all tests in error-test [9/67]...success
Running all tests in fs-pack-test [10/67]...success
Running all tests in fs-test [11/67]...success
Running all tests in hashdump-test [12/67]...success
Running all tests in locks-test [13/67]...success
Running all tests in mergeinfo-test [14/67]...success
Running all tests in opt-test [15/67]...success
Running all tests in path-test [16/67]...success
Running all tests in ra-local-test [17/67]...success
Running all tests in random-test [18/67]...success
Running all tests in repos-test [19/67]...success
Running all tests in revision-test [20/67]...success
Running all tests in skel-test [21/67]...success
Running all tests in stream-test [22/67]...success
Running all tests in string-test [23/67]...success
Running all tests in target-test [24/67]...success
Running all tests in time-test [25/67]...success
Running all tests in translate-test [26/67]...success
Running all tests in tree-conflict-data-test [27/67]...success
Running all tests in utf-test [28/67]...success
Running all tests in window-test [29/67]...success
Running all tests in getopt_tests.py [30/67]...success
Running all tests in basic_tests.py [31/67]...success
Running all tests in checkout_tests.py [32/67]...success
Running all tests in commit_tests.py [33/67]...success
Running all tests in update_tests.py [34/67]...success
Running all tests in switch_tests.py [35/67]...success
Running all tests in prop_tests.py [36/67]...success
Running all tests in schedule_tests.py [37/67]...success
Running all tests in log_tests.py [38/67]...success
Running all tests in copy_tests.py [39/67]...success
Running all tests in diff_tests.py [40/67]...success
Running all tests in export_tests.py [41/67]...success
Running all tests in externals_tests.py [42/67]...success
Running all tests in merge_tests.py [43/67]...success
Running all tests in merge_authz_tests.py [44/67]...success
Running all tests in revert_tests.py [45/67]...success
Running all tests in mergeinfo_tests.py [46/67]...success
Running all tests in stat_tests.py [47/67]...success
Running all tests in trans_tests.py [48/67]...success
Running all tests in autoprop_tests.py [49/67]...success
Running all tests in blame_tests.py [50/67]...success
Running all tests in special_tests.py [51/67]...success
Running all tests in svnadmin_tests.py [52/67]...success
Running all tests in svnlook_tests.py [53/67]...success
Running all tests in svnversion_tests.py [54/67]...success
Running all tests in utf8_tests.py [55/67]...success
Running all tests in history_tests.py [56/67]...success
Running all tests in lock_tests.py [57/67]...success
Running all tests in cat_tests.py [58/67]...success
Running all tests in import_tests.py [59/67]...success
Running all tests in svnsync_tests.py [60/67]...success
Running all tests in authz_tests.py [61/67]...success
Running all tests in depth_tests.py [62/67]...success
Running all tests in svndumpfilter_tests.py [63/67]...success
Running all tests in changelist_tests.py [64/67]...success
Running all tests in info_tests.py [65/67]...success
Running all tests in tree_conflict_tests.py [66/67]...success
Running all tests in resolved_tests.py [67/67]...success
At least one test was SKIPPED, checking
/Users/km/testsvn/subversion-1.6.0-rc1/tests.log
SKIP: cache-test 2: basic memcache svn_cache test
SKIP: cache-test 3: memcache svn_cache with very long keys
SKIP: update_tests.py 32: update wc on the root of a Windows (virtual)
drive
SKIP: merge_tests.py 101: commits to subtrees added by merge wreak havoc
SKIP: merge_authz_tests.py 1: skipped paths get overriding mergeinfo
SKIP: utf8_tests.py 1: conversion of paths and logs to/from utf8
SKIP: svnsync_tests.py 14: verify that unreadable content is not synced
SKIP: svnsync_tests.py 15: verify that copies from unreadable dirs work
SKIP: svnsync_tests.py 16: verify copies with mods from unreadable dirs
SKIP: svnsync_tests.py 17: verify copies with mods from unreadable dirs
+copy
SKIP: authz_tests.py 1: authz issue #2486 - open root
SKIP: authz_tests.py 2: authz issue #2486 - open directory
SKIP: authz_tests.py 3: broken authz files cause errors
SKIP: authz_tests.py 4: test authz for read operations
SKIP: authz_tests.py 5: test authz for write operations
SKIP: authz_tests.py 6: test authz for checkout
SKIP: authz_tests.py 7: test authz for log and tracing path changes
SKIP: authz_tests.py 8: test authz for checkout and update
SKIP: authz_tests.py 9: test authz for export with unreadable subfolder
SKIP: authz_tests.py 10: test authz for aliases
SKIP: authz_tests.py 11: test the authz validation rules
SKIP: authz_tests.py 12: test authz for locking
SKIP: authz_tests.py 13: authz issue #2712
SKIP: authz_tests.py 14: switched to directory, no read access on parents
At least one test XFAILED, checking
/Users/km/testsvn/subversion-1.6.0-rc1/tests.log
XFAIL: locks-test 9: able to reserve a name (lock non-existent path)
XFAIL: locks-test 10: directory locks (kinda)
XFAIL: tree-conflict-data-test 3: detect broken tree conflict data
XFAIL: basic_tests.py 38: remotely remove directories from two repositories
XFAIL: update_tests.py 50: tree conflicts 2.3: skip on 2nd update
XFAIL: switch_tests.py 10: switch a file to a dir and back to the file
XFAIL: log_tests.py 21: test log -c on range of changes
XFAIL: diff_tests.py 28: diff a renamed directory
XFAIL: diff_tests.py 49: diff URL against working copy with local mods
XFAIL: diff_tests.py 50: diff -r1 of removed file to its local addition
XFAIL: merge_tests.py 33: merge a replacement of a directory
XFAIL: merge_tests.py 34: replace both dir and one of its children
XFAIL: merge_tests.py 55: avoid repeated merges for cyclic merging
XFAIL: merge_tests.py 72: merge target with non inheritable mergeinfo
XFAIL: merge_tests.py 91: merge added subtree
XFAIL: merge_tests.py 115: tree conflicts 5.1: leaf edit, tree del
XFAIL: merge_tests.py 116: tree conflicts 5.2: leaf del, tree del
XFAIL: merge_tests.py 120: tree conflicts 5.1: leaf edit (no ci), tree del
XFAIL: merge_tests.py 121: tree conflicts 5.2: leaf del (no ci), tree del
XFAIL: merge_tests.py 125: merge prior to rename src existence still
dels src
XFAIL: revert_tests.py 4: revert a moved file
XFAIL: mergeinfo_tests.py 4: 'mergeinfo' with uninteresting source selection
XFAIL: special_tests.py 10: diff a symlink to a directory
XFAIL: info_tests.py 2: info on added file
XFAIL: tree_conflict_tests.py 14: merge dir: del/rpl/mv onto not-same
Summary of test results:
24 tests SKIPPED
25 tests XFAILED
mac:subversion-1.6.0-rc1 km$
Kind regards
Karl Heinz Marbaise
--
SoftwareEntwicklung Beratung Schulung Tel.: +49 (0) 2405 / 415 893
Dipl.Ing.(FH) Karl Heinz Marbaise ICQ#: 135949029
Hauptstrasse 177 USt.IdNr: DE191347579
52146 Würselen http://www.soebes.de
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1174139
Re: 1.6.0-rc1 tarballs up for signing/testing
Posted by Arfrever Frehtes Taifersar Arahesis <Ar...@GMail.Com>.
2009-02-17 14:59:52 Branko Cibej napisał(a):
> Would be nice if whoever made the BDB configury quite incomprehensible
> had at least updated INSTALL or perhaps made the help output marginally
> enlightening.
I updated INSTALL in r35938.
I will merge it later to 1.6.x branch.
> (Yeah I figured it out after reading berkeley-db.m4. Not my idea of
> friendly.)
--
Arfrever Frehtes Taifersar Arahesis
Re: 1.6.0-rc1 tarballs up for signing/testing
Posted by Branko Cibej <br...@xbc.nu>.
Would be nice if whoever made the BDB configury quite incomprehensible
had at least updated INSTALL or perhaps made the help output marginally
enlightening.
(Yeah I figured it out after reading berkeley-db.m4. Not my idea of
friendly.)
-- Brane
Hyrum K. Wright wrote:
> Good afternoon,
>
> I'm pleased to announce that Subversion 1.6.0-rc1 is up for testing
> and signing. The magic revision is r35896.
>
> http://orac.ece.utexas.edu/pub/svn/1.6.0-rc1/
>
> As usual, signatures from full committers back to me, and enthusiastic
> tester feedback is welcome. At this point, this candidate is not yet
> blessed for wide release, so please don't make it available to people
> not interested in test-driving the new release. Please especially
> test the serf RA layer, and consider including it in your typical
> testing routine.
>
> Distro package maintainers, please to NOT include any pre-release
> builds, even blessed, into operating system distros. The reasons for
> not doing so were very eloquently outlined by Karl in a mail, which is
> summarized at the above address.
>
> The quick version is: we don't guarantee compatibility between the pre-
> releases and the final release, so if people install the release
> candidate, all their repositories and working copies might break
> unrepairably when they upgrade to 1.6.0 proper. We don't want that
> kind of bad publicity, and neither do you.
>
> -Hyrum
>
> ------------------------------------------------------
> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1173277
>
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1178955
Re: 1.6.0-rc1 tarballs up for signing/testing
Posted by Senthil Kumaran S <se...@collab.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hyrum K. Wright wrote:
> Good afternoon,
>
> I'm pleased to announce that Subversion 1.6.0-rc1 is up for testing
> and signing. The magic revision is r35896.
>
> http://orac.ece.utexas.edu/pub/svn/1.6.0-rc1/
Tested:
1.6.0-rc1 tarball with local dependencies (nothing from deps tarball)
(ra_local, ra_svn, ra_serf, ra_neon) x (fsfs, bdb)
Dependencies:
APR 1.3.3
APR-UTIL 1.3.4
Apache httpd 2.2.9
Neon 0.28.2
Serf 0.3.0
DB 4.7.25
sqlite 3.5.9
OpenSSL 0.9.8g
Environment:
Ubuntu Intrepid (recently updated)
Linux 2.6.27-11-generic #1 SMP i686 GNU/Linux
Results:
All tests PASSED expect for:
FAIL: lt-fs-test 18: merging commit (in all layers only on BDB)
md5sums:
a78b51fceec431ed4a5cc775bf94f56b subversion-1.6.0-rc1.tar.bz2
d1e88c271dc37de60c9162439c5c7570 subversion-1.6.0-rc1.tar.gz
GPG Signatures:
subversion-1.6.0-rc1.tar.bz2.asc
- -----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEABECAAYFAkmagdIACgkQ9o1G+2zNQDib4gCgrYFknJqFeFideNadJeK1m6jQ
kzQAoMQFBQI+ruY3/lWd9DdEyvNBF6ux
=qzqJ
- -----END PGP SIGNATURE-----
subversion-1.6.0-rc1.tar.gz.asc
- -----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEABECAAYFAkmagfwACgkQ9o1G+2zNQDhwKwCeMwX6ILR0yv7jo7jwk+QGYopA
2KYAn0emZ+tEDSSvdknUP+zNqhJu5iso
=7Jrb
- -----END PGP SIGNATURE-----
Thank You.
- --
Senthil Kumaran S
http://www.stylesen.org/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkma3qcACgkQ9o1G+2zNQDiDGQCgiON7dXSxHGW+V3YKgdISzC6K
wrsAnA+h103cWdKVml8pBwIzerl5BTMT
=1bnI
-----END PGP SIGNATURE-----
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1179536