You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Ben Reser <be...@reser.org> on 2012/12/27 21:54:00 UTC
1.6.20 up for testing/signing
The 1.6.20 release artifacts are now available for testing/signing.
Please get the tarballs from
https://dist.apache.org/repos/dist/dev/subversion
and add your signatures there. I plan to try and release on January
4th so please try and get your votes/signatures in place by January
3rd EOD. Thanks!
Please note the following known test failures (perhaps most easily
triggered with APR-1.4.6):
log_tests.py 30: log -g should ignore cyclic merges
Can fail because 1.6.x is missing r1293229, which fixed occasionally
missing merged-via notifications.
diff_tests.py 32: repos-wc diff showing added entries with props
Can fail because this test is missing various tweaks to account
for random output order of 'svn diff' (this is independent of the
APR 1.4.6 hash order problem).
ruby swig test 'test_dump'
Can fail because 1.6.x is missing r966458, which sorted property
listings in dump files in alphabetical order, and this test does
not parse dump files and sort properties for comparison.
Re: 1.6.20 up for testing/signing
Posted by Ben Reser <be...@reser.org>.
On Fri, Jan 4, 2013 at 12:46 PM, Ben Reser <be...@reser.org> wrote:
> Voting is at
> UNIX: 3
> Windows: 2
>
> Anyone working on doing the last Windows vote so I can release today?
Hate to be a nag but we are still lacking a Windows vote on this.
Re: 1.6.20 up for testing/signing
Posted by Ben Reser <be...@reser.org>.
On Thu, Dec 27, 2012 at 12:54 PM, Ben Reser <be...@reser.org> wrote:
> The 1.6.20 release artifacts are now available for testing/signing.
> Please get the tarballs from
> https://dist.apache.org/repos/dist/dev/subversion
> and add your signatures there. I plan to try and release on January
> 4th so please try and get your votes/signatures in place by January
> 3rd EOD. Thanks!
Voting is at
UNIX: 3
Windows: 2
Anyone working on doing the last Windows vote so I can release today?
Re: 1.6.20 up for testing/signing
Posted by Stefan Sperling <st...@apache.org>.
On Thu, Jan 03, 2013 at 12:26:22AM -0800, Ben Reser wrote:
> On Fri, Dec 28, 2012 at 8:38 AM, Stefan Sperling <st...@apache.org> wrote:
> > Summary: +1 to release
>
> I noticed you signed the zip file. Just wanting to clarify that your
> vote is for UNIX only right?
Yes, it's just that the release.py target signs all the files.
Re: 1.6.20 up for testing/signing
Posted by Ben Reser <be...@reser.org>.
On Fri, Dec 28, 2012 at 8:38 AM, Stefan Sperling <st...@apache.org> wrote:
> Summary: +1 to release
>
> Tested: [bdb | fsfs] x [ra_local | ra_svn | ra_neon | ra_serf]
> swig bindings
> javahl bindings
>
> Test results: Tests passed, except:
> ra_local-bdb:
> FAIL: diff_tests.py 32: repos-wc diff showing added entries with props
> ra_neon-bdb:
> FAIL: svnadmin_tests.py 20: concurrent mergeinfo commits invalidate pred-count
> ra_neon-fsfs:
> FAIL: diff_tests.py 32: repos-wc diff showing added entries with props
> ra_svn-fsfs:
> FAIL: log_tests.py 30: log -g should ignore cyclic merges
> ruby bindings: test_dump(SvnReposTest)
>
> These failures are expected.
> I remember svnadmin_test 20 failing before on 1.6.x.
>
> Platform: OpenBSD 5.2 amd64
I noticed you signed the zip file. Just wanting to clarify that your
vote is for UNIX only right?
Re: 1.6.20 up for testing/signing
Posted by Stefan Sperling <st...@apache.org>.
On Thu, Dec 27, 2012 at 12:54:00PM -0800, Ben Reser wrote:
> The 1.6.20 release artifacts are now available for testing/signing.
> Please get the tarballs from
> https://dist.apache.org/repos/dist/dev/subversion
> and add your signatures there. I plan to try and release on January
> 4th so please try and get your votes/signatures in place by January
> 3rd EOD. Thanks!
>
> Please note the following known test failures (perhaps most easily
> triggered with APR-1.4.6):
>
> log_tests.py 30: log -g should ignore cyclic merges
> Can fail because 1.6.x is missing r1293229, which fixed occasionally
> missing merged-via notifications.
>
> diff_tests.py 32: repos-wc diff showing added entries with props
> Can fail because this test is missing various tweaks to account
> for random output order of 'svn diff' (this is independent of the
> APR 1.4.6 hash order problem).
>
> ruby swig test 'test_dump'
> Can fail because 1.6.x is missing r966458, which sorted property
> listings in dump files in alphabetical order, and this test does
> not parse dump files and sort properties for comparison.
Summary: +1 to release
Tested: [bdb | fsfs] x [ra_local | ra_svn | ra_neon | ra_serf]
swig bindings
javahl bindings
Test results: Tests passed, except:
ra_local-bdb:
FAIL: diff_tests.py 32: repos-wc diff showing added entries with props
ra_neon-bdb:
FAIL: svnadmin_tests.py 20: concurrent mergeinfo commits invalidate pred-count
ra_neon-fsfs:
FAIL: diff_tests.py 32: repos-wc diff showing added entries with props
ra_svn-fsfs:
FAIL: log_tests.py 30: log -g should ignore cyclic merges
ruby bindings: test_dump(SvnReposTest)
These failures are expected.
I remember svnadmin_test 20 failing before on 1.6.x.
Platform: OpenBSD 5.2 amd64
Dependencies:
bdb: 4.7.25
GNU-iconv: 1.14
apr: 1.4.6
apr-util: 1.4.1
httpd: 2.2.22
neon: 0.29.6
serf: 1.1.0
cyrus-sasl: 2.1.25
sqlite: 3071201
openssl: 1.0.1c
swig: 1.3.36
python: 2.7.3
perl: 5.12.2
ruby: 1.8.7-p358
java: 1.7.0_03
Signatures:
subversion-1.6.20.tar.gz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (OpenBSD)
iQEcBAABAgAGBQJQ3cnEAAoJEE99uqmaWblzNmUIAI0b4rAAV24jANeU1sD7YRZ1
lis9hG2fGP8L3tJNhlnbLWsZN8LpSXww4+Jwik9reJy0k9yiLI/DYcjLj0nKliZw
lRD1aX+AWT3GZWbpEYZ/PsK8wpWVN6tEa858C43T1BVOXsbm8D6g4xF284NhZQEt
2CH4mDqPWrena/FFwEiXh5QpvEc0xvD/wnbQAYSkT7ExZ1jP3UIm8BLK1ZJ4E09r
CCMBeklyaRwzVRmLNCWj3xMvlrDWeLYoWbXVilDyWgMWafqtKnFZ2DpSXryB/6I1
2wGNTMO3NIqyyg8IhcaZxl60zw+p59dUwGBvQboyq1p65xYYWvqWpGreNRAhILE=
=EfjK
-----END PGP SIGNATURE-----
subversion-1.6.20.tar.bz2
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (OpenBSD)
iQEcBAABAgAGBQJQ3cnMAAoJEE99uqmaWblz6NkH/2VXIRF8bzuLdVoyLZvdVRxT
mXHEgeaGOKSuKSQgGJaax916TL6z9SbAcV4+wJAmBCmG1vFynLXMp2NuEaFsB9rB
wHXh+sE4fKGXWXx2fm6JQ4VUipxL73aCxRP1ZCYW4zMAuIWt0N3U8WOqYGHUzD//
r92WV+rQJ1ZbQ5mHV7Gb4fjGHPMg0K8B821jfo2vn6E2Bn7jUQ966QeIeXgHQW6f
9JCXCkcP5zd0+YKymgtpC4yfGE037Y2V5ctpK33bzr/Eqs6tx/Y2nN/pMSiRi3If
FC7LURaU9simUXtLWGP8JhvM2oh2TSp7nL+QX10cn2jzGT+zj0pnEyBYHbOaPRU=
=NeLN
-----END PGP SIGNATURE-----
Re: 1.6.20 up for testing/signing
Posted by Philip Herron <ph...@wandisco.com>.
On 03/01/13 00:22, Philip Martin wrote:
> Philip Herron <ph...@wandisco.com> writes:
>
>> On 02/01/13 19:22, Ben Reser wrote:
>>> On Wed, Jan 2, 2013 at 11:12 AM, Paul Burba <pt...@gmail.com> wrote:
>>>> Gah, sorry about that. Fixed.
>>>
>>> Thanks, no big deal.
>>>
>> I seem to be having issues getting --with-kwallet on rhel 6 to work.
>>
>> kwallet.h lives in /usr/include/kde4 and it wants to link against
>> libkdecore.so which is in -L/usr/lib64/kde4 prob just /usr/lib/kde4 on
>> 32bit.
>>
>> Not sure how might fighting i wanted to do tried to:
>>
>> CFLAGS="-I/usr/include/kde4"
>> CXXFLAGS="-I/usr/include/kde4"
>> LDFLAGS="-L/usr/lib64/kde4"
>>
>> But still didnt get any luck i think the flags were being overwitten for
>> that test of kwallet.h. Thinking i might just leave it out of this
>> release for us because i've been fighting with it all after noon.
>
> Did 1.6.19 work? I don't think Subversion's build system has changed,
> has rhel changed?
>
>> Debian 5 wouldn't build because needing libserf >= 0.3.0 i could try and
>> remove libserf from the build but tempted to see this as a push to stop
>> support for debian 5. Since i bet later releases of 1.7 will want this also.
>
> Serf is optional in 1.6.x, it only gets built if you configure using
> --with-serf.
>
Hmm its a fresh buildbot i made, so i think its probably right i might
try and see what i can do some other day.
I think subversion really needs a hadoop project like bigtop now because
packaging reliably across all platforms seems very hidden with many
caveats like ubuntu 12.04 you need to repackage libserf to remove the
libserf-private bug etc.
I wonder if other parties are interested in doing something like this.
The biggest frustration i have at the moment is the sate of upstream
patches there doesn't seem to be a reliable way to finding these etc to
keep things uniform. I've had alot of mixed luck with the upstream
patches from when i joined wandisco in August esp on debian based
distro's. I might try and fork apache bigtop and see what i come up with
over the coming months and post up.
--Phil
Re: 1.6.20 up for testing/signing
Posted by Philip Martin <ph...@wandisco.com>.
Philip Herron <ph...@wandisco.com> writes:
> On 02/01/13 19:22, Ben Reser wrote:
>> On Wed, Jan 2, 2013 at 11:12 AM, Paul Burba <pt...@gmail.com> wrote:
>>> Gah, sorry about that. Fixed.
>>
>> Thanks, no big deal.
>>
> I seem to be having issues getting --with-kwallet on rhel 6 to work.
>
> kwallet.h lives in /usr/include/kde4 and it wants to link against
> libkdecore.so which is in -L/usr/lib64/kde4 prob just /usr/lib/kde4 on
> 32bit.
>
> Not sure how might fighting i wanted to do tried to:
>
> CFLAGS="-I/usr/include/kde4"
> CXXFLAGS="-I/usr/include/kde4"
> LDFLAGS="-L/usr/lib64/kde4"
>
> But still didnt get any luck i think the flags were being overwitten for
> that test of kwallet.h. Thinking i might just leave it out of this
> release for us because i've been fighting with it all after noon.
Did 1.6.19 work? I don't think Subversion's build system has changed,
has rhel changed?
> Debian 5 wouldn't build because needing libserf >= 0.3.0 i could try and
> remove libserf from the build but tempted to see this as a push to stop
> support for debian 5. Since i bet later releases of 1.7 will want this also.
Serf is optional in 1.6.x, it only gets built if you configure using
--with-serf.
--
Certified & Supported Apache Subversion Downloads:
http://www.wandisco.com/subversion/download
Re: 1.6.20 up for testing/signing
Posted by Philip Martin <ph...@wandisco.com>.
Philip Herron <ph...@wandisco.com> writes:
> aptitude shows me i am on 0.2.0-1 from archive.debian.org since this is
> lenny.
All 1.6.x releases require serf to be at least 0.3.0. If you build 1.6
on this platform in the past you must have built it without serf or used
a different serf package or patched the Subversion source code.
--
Certified & Supported Apache Subversion Downloads:
http://www.wandisco.com/subversion/download
Re: 1.6.20 up for testing/signing
Posted by Philip Herron <ph...@wandisco.com>.
On 03/01/13 00:53, Philip Martin wrote:
> Philip Herron <ph...@wandisco.com> writes:
>
>> For the libserf thing on debian 5 i get
>>
>> /home/wandisco/SUBVERSION/BUILDS/subversion-1.6.20-1356654074.89/subversion/libsvn_ra_serf/ra_serf.h:40:2:
>> error: #error Please update your version of serf to at least 0.3.0.
>
> Did this work with 1.6.19? I don't think Subversion changed this for
> 1.6.20.
>
> Further, Debian doesn't appear to package anything less than 0.3.1.
> Which version of serf do you have installed?
>
aptitude shows me i am on 0.2.0-1 from archive.debian.org since this is
lenny.
Re: 1.6.20 up for testing/signing
Posted by Philip Martin <ph...@wandisco.com>.
Philip Herron <ph...@wandisco.com> writes:
> For the libserf thing on debian 5 i get
>
> /home/wandisco/SUBVERSION/BUILDS/subversion-1.6.20-1356654074.89/subversion/libsvn_ra_serf/ra_serf.h:40:2:
> error: #error Please update your version of serf to at least 0.3.0.
Did this work with 1.6.19? I don't think Subversion changed this for
1.6.20.
Further, Debian doesn't appear to package anything less than 0.3.1.
Which version of serf do you have installed?
--
Certified & Supported Apache Subversion Downloads:
http://www.wandisco.com/subversion/download
Re: 1.6.20 up for testing/signing
Posted by Philip Herron <ph...@wandisco.com>.
On 03/01/13 00:30, Ben Reser wrote:
> This is somewhat offtopic for the release.
>
> On Wed, Jan 2, 2013 at 3:26 PM, Philip Herron
> <ph...@wandisco.com> wrote:
>> Debian 5 wouldn't build because needing libserf >= 0.3.0 i could try and
>> remove libserf from the build but tempted to see this as a push to stop
>> support for debian 5. Since i bet later releases of 1.7 will want this also.
>
> For newer releases I think we've bumped the required version of
> libserf even more than that. The older versions have known bugs. So
> if it's a choice of building your own libserf or using whatever comes
> with the OS, you're probably better off building your own.
>
> As philipm already pointed out Serf doesn't build unless you
> specifically ask for it with 1.6/1.7. I changed that a while back in
> trunk, so that won't be an issue for 1.8 where Serf is the only HTTP
> library we support.
>
For the libserf thing on debian 5 i get
/home/wandisco/SUBVERSION/BUILDS/subversion-1.6.20-1356654074.89/subversion/libsvn_ra_serf/ra_serf.h:40:2:
error: #error Please update your version of serf to at least 0.3.0.
I think overall i don't think packaging my own libserf as well is a good
idea on lenny old-stable. And packing without libserf seems like not
enough to gain when i will probably get this error now in future
releases so seems like a good idea to shoot debian 5 support now instead
of trying to maintain it with our own packaged dependencies. Since it
will mean a lot of messing with debian rules and control and install
files just for not enough to gain.
Re: 1.6.20 up for testing/signing
Posted by Ben Reser <be...@reser.org>.
This is somewhat offtopic for the release.
On Wed, Jan 2, 2013 at 3:26 PM, Philip Herron
<ph...@wandisco.com> wrote:
> Debian 5 wouldn't build because needing libserf >= 0.3.0 i could try and
> remove libserf from the build but tempted to see this as a push to stop
> support for debian 5. Since i bet later releases of 1.7 will want this also.
For newer releases I think we've bumped the required version of
libserf even more than that. The older versions have known bugs. So
if it's a choice of building your own libserf or using whatever comes
with the OS, you're probably better off building your own.
As philipm already pointed out Serf doesn't build unless you
specifically ask for it with 1.6/1.7. I changed that a while back in
trunk, so that won't be an issue for 1.8 where Serf is the only HTTP
library we support.
Re: 1.6.20 up for testing/signing
Posted by Philip Herron <ph...@wandisco.com>.
On 02/01/13 19:22, Ben Reser wrote:
> On Wed, Jan 2, 2013 at 11:12 AM, Paul Burba <pt...@gmail.com> wrote:
>> Gah, sorry about that. Fixed.
>
> Thanks, no big deal.
>
I seem to be having issues getting --with-kwallet on rhel 6 to work.
kwallet.h lives in /usr/include/kde4 and it wants to link against
libkdecore.so which is in -L/usr/lib64/kde4 prob just /usr/lib/kde4 on
32bit.
Not sure how might fighting i wanted to do tried to:
CFLAGS="-I/usr/include/kde4"
CXXFLAGS="-I/usr/include/kde4"
LDFLAGS="-L/usr/lib64/kde4"
But still didnt get any luck i think the flags were being overwitten for
that test of kwallet.h. Thinking i might just leave it out of this
release for us because i've been fighting with it all after noon.
Debian 5 wouldn't build because needing libserf >= 0.3.0 i could try and
remove libserf from the build but tempted to see this as a push to stop
support for debian 5. Since i bet later releases of 1.7 will want this also.
--Phil
Re: 1.6.20 up for testing/signing
Posted by Ben Reser <be...@reser.org>.
On Wed, Jan 2, 2013 at 11:12 AM, Paul Burba <pt...@gmail.com> wrote:
> Gah, sorry about that. Fixed.
Thanks, no big deal.
Re: 1.6.20 up for testing/signing
Posted by Paul Burba <pt...@gmail.com>.
On Wed, Jan 2, 2013 at 2:04 PM, Ben Reser <be...@reser.org> wrote:
> On Wed, Jan 2, 2013 at 10:51 AM, Paul Burba <pt...@gmail.com> wrote:
>> SIGNATURE:
>> -----------
>> user: "Paul T. Burba <pb...@collab.net>"
>> 4096-bit RSA key, ID 56F3D7BC, created 2012-12-11
>>
>> For https://dist.apache.org/repos/dist/dev/subversion/subversion-1.6.20.zip:
>>
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v2.0.17 (MingW32)
>>
>> iQIcBAABCgAGBQJQ5E7gAAoJEGTdwHFW89e8Mc0P/jSJ/tTY7NQnyaUsstkRXbOX
>> NfS2oFe40xII7kwgd/NrMVdMdEKypQc74UGCPkklQEceCcjy2ZF2cFGhZw2yHbGB
>> Irn4yo/2YuTAonwWcZOEVBeJTE5Y1d1G5v+mVj+TS2CqbvR+YXtMU8nLuWzsf7tz
>> eDq60RI+yqZ8LTn9V5kz+IsBZo3UcXCbXey2eQrLQR62kFFlJMdjmM/jDKdURL/P
>> JxtPFIBA/ib9KtJyeD49tbvO7Uy7v+8Q0IN+Fg2jNqccq65XWrwwwz98A8tqlnof
>> 6llwdAFar/a/nP/4g7hNPRJeEEwHsKLpJ5aOBQ6InAHsODoOp67mmxbnpllbkoXP
>> c5RLy0MQALVkQcJCNOYEkCfIpcGAS8JcNfRp3/hfbdefoC7P4Sbls0177eZw8emz
>> thdOATXkNTcC1hkqtqANiKwxCVNEK/JNzRr6tplGwVXCDSnHIh5CC0Sj1GSHEjRe
>> krJE3FotbRoicybEj7kCPQjVL+3sUSxbKsTNZigZBthrqqT+sLAJpvuwdF3YjxwM
>> Xg+g2veqSfWrQR40EfuFAiT9/ZZU05wUzUn2h244UmCcklN1x5Z1wG9COriu7WZD
>> O3eXll4cUHWtkn3SKNUdBT9lxaxtoVguh7XL10laH5aP6YFfm8yx47Zz/vw/iFgQ
>> 0rBkaaqEW5ScVPSz4Yl2
>> =WxY2
>> -----END PGP SIGNATURE-----
>
> You applied the signature to the wrong file, can you please fix:
>
> [[[
> BAD SIGNATURE for subversion-deps-1.6.20.zip.asc
> key id: 64DDC07156F3D7BC
> ]]]
Gah, sorry about that. Fixed.
--
Paul T. Burba
CollabNet, Inc. -- www.collab.net -- Enterprise Cloud Development
Skype: ptburba
Re: 1.6.20 up for testing/signing
Posted by Ben Reser <be...@reser.org>.
On Wed, Jan 2, 2013 at 10:51 AM, Paul Burba <pt...@gmail.com> wrote:
> SIGNATURE:
> -----------
> user: "Paul T. Burba <pb...@collab.net>"
> 4096-bit RSA key, ID 56F3D7BC, created 2012-12-11
>
> For https://dist.apache.org/repos/dist/dev/subversion/subversion-1.6.20.zip:
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.17 (MingW32)
>
> iQIcBAABCgAGBQJQ5E7gAAoJEGTdwHFW89e8Mc0P/jSJ/tTY7NQnyaUsstkRXbOX
> NfS2oFe40xII7kwgd/NrMVdMdEKypQc74UGCPkklQEceCcjy2ZF2cFGhZw2yHbGB
> Irn4yo/2YuTAonwWcZOEVBeJTE5Y1d1G5v+mVj+TS2CqbvR+YXtMU8nLuWzsf7tz
> eDq60RI+yqZ8LTn9V5kz+IsBZo3UcXCbXey2eQrLQR62kFFlJMdjmM/jDKdURL/P
> JxtPFIBA/ib9KtJyeD49tbvO7Uy7v+8Q0IN+Fg2jNqccq65XWrwwwz98A8tqlnof
> 6llwdAFar/a/nP/4g7hNPRJeEEwHsKLpJ5aOBQ6InAHsODoOp67mmxbnpllbkoXP
> c5RLy0MQALVkQcJCNOYEkCfIpcGAS8JcNfRp3/hfbdefoC7P4Sbls0177eZw8emz
> thdOATXkNTcC1hkqtqANiKwxCVNEK/JNzRr6tplGwVXCDSnHIh5CC0Sj1GSHEjRe
> krJE3FotbRoicybEj7kCPQjVL+3sUSxbKsTNZigZBthrqqT+sLAJpvuwdF3YjxwM
> Xg+g2veqSfWrQR40EfuFAiT9/ZZU05wUzUn2h244UmCcklN1x5Z1wG9COriu7WZD
> O3eXll4cUHWtkn3SKNUdBT9lxaxtoVguh7XL10laH5aP6YFfm8yx47Zz/vw/iFgQ
> 0rBkaaqEW5ScVPSz4Yl2
> =WxY2
> -----END PGP SIGNATURE-----
You applied the signature to the wrong file, can you please fix:
[[[
BAD SIGNATURE for subversion-deps-1.6.20.zip.asc
key id: 64DDC07156F3D7BC
]]]
Re: 1.6.20 up for testing/signing
Posted by Paul Burba <pt...@gmail.com>.
On Thu, Dec 27, 2012 at 3:54 PM, Ben Reser <be...@reser.org> wrote:
> The 1.6.20 release artifacts are now available for testing/signing.
> Please get the tarballs from
> https://dist.apache.org/repos/dist/dev/subversion
> and add your signatures there. I plan to try and release on January
> 4th so please try and get your votes/signatures in place by January
> 3rd EOD. Thanks!
>
> Please note the following known test failures (perhaps most easily
> triggered with APR-1.4.6):
>
> log_tests.py 30: log -g should ignore cyclic merges
> Can fail because 1.6.x is missing r1293229, which fixed occasionally
> missing merged-via notifications.
>
> diff_tests.py 32: repos-wc diff showing added entries with props
> Can fail because this test is missing various tweaks to account
> for random output order of 'svn diff' (this is independent of the
> APR 1.4.6 hash order problem).
>
> ruby swig test 'test_dump'
> Can fail because 1.6.x is missing r966458, which sorted property
> listings in dump files in alphabetical order, and this test does
> not parse dump files and sort properties for comparison.
VERIFIED:
---------
Sig for https://dist.apache.org/repos/dist/dev/subversion/subversion-1.6.20.zip:
>gpg2 --verify subversion-1.6.20.zip.asc
gpg: WARNING: multiple signatures detected. Only the first will be checked.
gpg: Signature made 12/27/12 15:14:53 Eastern Standard Time using RSA
key ID 16A0DE01
gpg: Good signature from "Ben Reser <be...@reser.org>"
gpg: aka "Ben Reser <br...@apache.org>"
gpg: aka "Ben Reser <be...@wandisco.com>"
gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the owner.
Primary key fingerprint: 19BB CAEF 7B19 B280 A0E2 175E 62D4 8FAD 16A0 DE01
SHA1 of https://dist.apache.org/repos/dist/dev/subversion/subversion-1.6.20.zip
is 8b5fd5d187a89cc8009e8219b955c25dff3f871b
Other than the expected differences in
subversion/include/svn_version.h,
https://dist.apache.org/repos/dist/dev/subversion/subversion-1.6.20.zip
is identical to
https://svn.apache.org/repos/asf/subversion/branches/1.6.x@1426281
TESTED:
-------
JavaHL Bindings
Ruby Bindings (patched as described here:
http://svn.haxx.se/dev/archive-2011-06/0682.shtml)
[ fsfs | bdb ] x [ file | svn | http (neon) | http (serf) ]
RESULTS:
--------
All tests pass with the exception of 'FAIL: diff_tests.py 32:
repos-wc diff showing added entries with props' which failed in the
following (this is expected with APR 1.4.6):
[ bdb | fsfs ] x [ file ]
[ bdb | fsfs ] x [ http(neon) ]
[ bdb ] x [ http(serf) ]
+1 to release
PLATFORM:
---------
MS Windows 7 Home Premium Service Pack 1
Microsoft Visual Studio 2008 Version 9.0.30729.1 SP
DEPENDENCIES:
-------------
APR: 1.4.6
APR-UTIL: 1.4.1
Neon: 0.29.5
zlib: 1.2.4
OpenSSL: 0.9.8q
Apache: 2.2.22
BDB: 4.8.30
sqlite: 3.7.7.1
Python: 2.7.2 (ActivePython 2.7.2.5)
Perl: 5.14.2
Ruby: ruby 1.8.7
java: 1.6.0_21
junit: 4.8.2
swig: 1.3.40
serf: 0.7.2[1]
[1] I experienced the same build failures with serf 1.1.1 that Johan
reported elsethread.
SIGNATURE:
-----------
user: "Paul T. Burba <pb...@collab.net>"
4096-bit RSA key, ID 56F3D7BC, created 2012-12-11
For https://dist.apache.org/repos/dist/dev/subversion/subversion-1.6.20.zip:
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
iQIcBAABCgAGBQJQ5E7gAAoJEGTdwHFW89e8Mc0P/jSJ/tTY7NQnyaUsstkRXbOX
NfS2oFe40xII7kwgd/NrMVdMdEKypQc74UGCPkklQEceCcjy2ZF2cFGhZw2yHbGB
Irn4yo/2YuTAonwWcZOEVBeJTE5Y1d1G5v+mVj+TS2CqbvR+YXtMU8nLuWzsf7tz
eDq60RI+yqZ8LTn9V5kz+IsBZo3UcXCbXey2eQrLQR62kFFlJMdjmM/jDKdURL/P
JxtPFIBA/ib9KtJyeD49tbvO7Uy7v+8Q0IN+Fg2jNqccq65XWrwwwz98A8tqlnof
6llwdAFar/a/nP/4g7hNPRJeEEwHsKLpJ5aOBQ6InAHsODoOp67mmxbnpllbkoXP
c5RLy0MQALVkQcJCNOYEkCfIpcGAS8JcNfRp3/hfbdefoC7P4Sbls0177eZw8emz
thdOATXkNTcC1hkqtqANiKwxCVNEK/JNzRr6tplGwVXCDSnHIh5CC0Sj1GSHEjRe
krJE3FotbRoicybEj7kCPQjVL+3sUSxbKsTNZigZBthrqqT+sLAJpvuwdF3YjxwM
Xg+g2veqSfWrQR40EfuFAiT9/ZZU05wUzUn2h244UmCcklN1x5Z1wG9COriu7WZD
O3eXll4cUHWtkn3SKNUdBT9lxaxtoVguh7XL10laH5aP6YFfm8yx47Zz/vw/iFgQ
0rBkaaqEW5ScVPSz4Yl2
=WxY2
-----END PGP SIGNATURE-----
--
Paul T. Burba
CollabNet, Inc. -- www.collab.net -- Enterprise Cloud Development
Skype: ptburba
Re: 1.6.20 up for testing/signing
Posted by Ben Reser <be...@reser.org>.
On Mon, Dec 31, 2012 at 4:35 AM, Bert Huijben <be...@qqmail.nl> wrote:
> I think the necessary patches are in
> ^/subversion/branches/subversion/branches/1.6.x-serf-1-win32
I think the reason 1.6.x doesn't have serf-1 fixes is because we've
been trying to limit 1.6.x to security and stability fixes. Serf is
an optional dependency in 1.6.x.
Re: 1.6.20 up for testing/signing
Posted by Johan Corveleyn <jc...@gmail.com>.
On Mon, Dec 31, 2012 at 1:35 PM, Bert Huijben <be...@qqmail.nl> wrote:
>
>
>> -----Original Message-----
>> From: Daniel Shahaf [mailto:d.s@daniel.shahaf.name]
>> Sent: maandag 31 december 2012 08:55
>> To: Johan Corveleyn
>> Cc: Ben Reser; Subversion Development
>> Subject: Re: 1.6.20 up for testing/signing
>>
>> Johan Corveleyn wrote on Mon, Dec 31, 2012 at 01:50:19 +0100:
>> > I remember I could successfully build 1.6.19 with serf-0.7.1, so maybe
>> > I'll just do that for 1.6.20 too. However, maybe it's easy to fix
>> > this? The problem seems to be that, from serf-1.0 onwards, the
>> > resulting lib file is serf-1.lib. With serf-0.7.1 it was still named
>> > serf.lib. I'm not very familiar with the build system, so I don't know
>> > off hand how / where to fix this. Maybe someone else here knows, or
>> > can point me in the right direction?
>>
>> ENOTBERT but --- assuming libsvn_ra_serf-1.6.x supports serf-1.x in the
>> first place --- it should be a matter of s/serf/serf-1/ in the right
>> place.
>>
>> trunk suggests that place is get_win_libs():
>>
>> % grep -nR serf-'[012%]' build gen-make.py -l
>> build/transform_libtool_scripts.sh
>> build/generator/gen_win.py
>> build/ac-macros/serf.m4
>> % grep -nR serf-'[012%]' build/generator/gen_win.py
>> 1017: serflib = 'serf-%d.lib' % self.serf_ver_maj
>> 1166: serflib = 'serf-%d.lib' % self.serf_ver_maj
>
> I think the necessary patches are in
> ^/subversion/branches/subversion/branches/1.6.x-serf-1-win32
Thanks, Bert. I tried it (locally patched my subversion-1.6.20 (from
subversion-1.6.20.zip) with your changes). But unfortunately, I then
run into other problems:
libsvn_ra_serf-1.lib(util.obj) : error LNK2019: unresolved external
symbol _serf_bucket_snapshot referenced in function _setup_request
[C:\research\svn\client_build\subversion-1.6.20\build\win32\vcnet-vcproj\libsvn_ra_dll_vcnet.vcxproj]
libsvn_ra_serf-1.lib(util.obj) : error LNK2019: unresolved external
symbol _serf_bucket_restore_snapshot referenced in function
_setup_request [C:\research\svn\client_build\subversion-1.6.20\build\win32\vcnet-vcproj\libsvn_ra_dll_vcnet.vcxproj]
..\..\..\Release\subversion\libsvn_ra\libsvn_ra-1.dll : fatal error
LNK1120: 2 unresolved externals
[C:\research\svn\client_build\subversion-1.6.20\build\win32\vcnet-vcproj\libsvn_ra_dll_vcnet.vcxproj]
Should we try further, or should we just drop this, and instead try
again building with serf-0.7.1 on Windows (which does work)?
--
Johan
RE: 1.6.20 up for testing/signing
Posted by Bert Huijben <be...@qqmail.nl>.
> -----Original Message-----
> From: Daniel Shahaf [mailto:d.s@daniel.shahaf.name]
> Sent: maandag 31 december 2012 08:55
> To: Johan Corveleyn
> Cc: Ben Reser; Subversion Development
> Subject: Re: 1.6.20 up for testing/signing
>
> Johan Corveleyn wrote on Mon, Dec 31, 2012 at 01:50:19 +0100:
> > I remember I could successfully build 1.6.19 with serf-0.7.1, so maybe
> > I'll just do that for 1.6.20 too. However, maybe it's easy to fix
> > this? The problem seems to be that, from serf-1.0 onwards, the
> > resulting lib file is serf-1.lib. With serf-0.7.1 it was still named
> > serf.lib. I'm not very familiar with the build system, so I don't know
> > off hand how / where to fix this. Maybe someone else here knows, or
> > can point me in the right direction?
>
> ENOTBERT but --- assuming libsvn_ra_serf-1.6.x supports serf-1.x in the
> first place --- it should be a matter of s/serf/serf-1/ in the right
> place.
>
> trunk suggests that place is get_win_libs():
>
> % grep -nR serf-'[012%]' build gen-make.py -l
> build/transform_libtool_scripts.sh
> build/generator/gen_win.py
> build/ac-macros/serf.m4
> % grep -nR serf-'[012%]' build/generator/gen_win.py
> 1017: serflib = 'serf-%d.lib' % self.serf_ver_maj
> 1166: serflib = 'serf-%d.lib' % self.serf_ver_maj
I think the necessary patches are in
^/subversion/branches/subversion/branches/1.6.x-serf-1-win32
Bert
Re: 1.6.20 up for testing/signing
Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
Johan Corveleyn wrote on Mon, Dec 31, 2012 at 01:50:19 +0100:
> I remember I could successfully build 1.6.19 with serf-0.7.1, so maybe
> I'll just do that for 1.6.20 too. However, maybe it's easy to fix
> this? The problem seems to be that, from serf-1.0 onwards, the
> resulting lib file is serf-1.lib. With serf-0.7.1 it was still named
> serf.lib. I'm not very familiar with the build system, so I don't know
> off hand how / where to fix this. Maybe someone else here knows, or
> can point me in the right direction?
ENOTBERT but --- assuming libsvn_ra_serf-1.6.x supports serf-1.x in the
first place --- it should be a matter of s/serf/serf-1/ in the right
place.
trunk suggests that place is get_win_libs():
% grep -nR serf-'[012%]' build gen-make.py -l
build/transform_libtool_scripts.sh
build/generator/gen_win.py
build/ac-macros/serf.m4
% grep -nR serf-'[012%]' build/generator/gen_win.py
1017: serflib = 'serf-%d.lib' % self.serf_ver_maj
1166: serflib = 'serf-%d.lib' % self.serf_ver_maj
HTH
Re: 1.6.20 up for testing/signing
Posted by Johan Corveleyn <jc...@gmail.com>.
On Thu, Dec 27, 2012 at 9:54 PM, Ben Reser <be...@reser.org> wrote:
> The 1.6.20 release artifacts are now available for testing/signing.
> Please get the tarballs from
> https://dist.apache.org/repos/dist/dev/subversion
> and add your signatures there. I plan to try and release on January
> 4th so please try and get your votes/signatures in place by January
> 3rd EOD. Thanks!
When trying to build this with serf-1.1.1, on Windows (VC 2010, after
converting the 2008 version of the solution created by gen-make.py
(which doesn't support 2010-format in 1.6.x)), I get the following
link error:
LINK : fatal error LNK1181: cannot open input file 'serf.lib'
[C:\research\svn\client_build\subversion-1.6.20\build\win32\vcnet-vcproj\test_ra_local_vcnet.vcxproj]
I remember I could successfully build 1.6.19 with serf-0.7.1, so maybe
I'll just do that for 1.6.20 too. However, maybe it's easy to fix
this? The problem seems to be that, from serf-1.0 onwards, the
resulting lib file is serf-1.lib. With serf-0.7.1 it was still named
serf.lib. I'm not very familiar with the build system, so I don't know
off hand how / where to fix this. Maybe someone else here knows, or
can point me in the right direction?
Note: I have no problems building 1.7.x or trunk with serf-1.x, so it
seems to be a buildscript-bug that has been fixed in 1.7.x, but not
backported to 1.6.
--
Johan
Re: 1.6.20 up for testing/signing
Posted by Branko Čibej <br...@wandisco.com>.
Summary:
+1 to release
Platform
Mac OS X 10.8.2 Mountain Lion, build 12C2034
Standard dependencies:
clang(++) 4.1/LLVM 3.1svn
APR 1.4.5
APR-Util 1.3.12
zlib 1.2.5
httpd 2.2.22
OpenSSL 0.9.8r
SQLite 3.7.12
Java 1.6.0_37
Python 2.7.2
Perl 5.12.4
Dependencies from homebrew:
Neon 0.29.6
BDB 5.3.21
Swig 2.0.8
Other dependencies:
JUnit 4.10
ctypesgen svn-r141
Verified:
Tarball contents and signatures
(fsfs, bdb) x (local, svnserve, dav+neon)
check-javahl
check-ctypes-python
check-swig-pl
Issues:
- check-ctypes-python fails:
Traceback (most recent call last):
File "test/run_all.py", line 5, in <module>
import setup_path
File "/Users/brane/src/svn/rel/1.6.x/subversion/bindings/ctypes-python/test/setup_path.py", line 14, in <module>
import csvn.core
File "/Users/brane/src/svn/rel/1.6.x/subversion/bindings/ctypes-python/csvn/core/__init__.py", line 118, in <module>
f.argtypes = [POINTER(POINTER(svn_auth_provider_object_t)), POINTER(apr_pool_t)]
NameError: name 'svn_auth_provider_object_t' is not defined
- swig-py and swig-rb do not build out-of-tree, and they
do not build at all on 64-bit Mac OS due to defaulting
to unversal build. (Known issue)
GPG Signatures:
$ cat subversion-1.6.20.tar.gz.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (Darwin)
iQEbBAABCgAGBQJQ5Y9rAAoJECm4ktDIYoUBKx4H+PjiJzwZpSuZs1JfA5XrXNrG
TywfvripR8VN/HM080dQOaN7tWgY10LK09Sh3Kd5zgjhg8ODpcHooXfgt+g3n4tU
pt0lBZWNDyIa3VClwYzZrMgFodcT9GQvOgMwilEM7Au44vBHn+VlPnatvLfhSwPS
A0NCkKg9JEdKs8v8ZCuVx1FA/G8unRSxgonR0utxkml5xGJdUs82SUvDfIZlGqut
bfkPnOgaUdMOiGtjXZzMMEFvl9Mks4BQ4XH1R4eHVJKgCUiM/B1k43/4uJ2jCo8X
cY8LJUWehfBuP3Yk0no/Y7JmVd/vp880ytraRD99mKF8SbxCBHz2RXJMlvT6Xg==
=G0tV
-----END PGP SIGNATURE-----
$ cat subversion-1.6.20.tar.bz2.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (Darwin)
iQEcBAABCgAGBQJQ5Y9jAAoJECm4ktDIYoUB+noIAJ5yoaecW3Df0kQ6FYkd7ZBl
batWnDJxOzh9GctQSfsMsSWfoJpMFJdBvvlU0vNaNja3iglKzUUMddnx2HCh5Zmr
tSHJEfV7cK107YrvgfVeKGW47228m0xJ/KMWTheECKStEuOuLG0Q5yEXIEgU6nwk
+ACVbACBBCnLbrSvNA++3fXWNm315LbKNVthgLx4I0nKZKubrGlHTDa08Uomm669
mrxuf0qcYoNQS0f1N7bEs6PzBSFn67i5WhHU0iUV+JiqWLWQcBhXpCB4Q5R05Ba6
1HfRBZ0bxhmwaiW5qnPzCPVp8/ojzTokai9ZtHV0HnG2vD0tgn2WPyDkzYxmOic=
=Sh4K
-----END PGP SIGNATURE-----
--
Branko Čibej
Director of Subversion | WANdisco | www.wandisco.com
Re: 1.6.20 up for testing/signing
Posted by Philip Martin <ph...@wandisco.com>.
Summary:
+1 to release
Platform:
Linux (Debian/wheezy)
Tested:
(local, svn, svn+sasl, serf, neon) x (fsfs, fsfs/pack/shard, bdb)
swig-pl, swig-py, swig-rb
javahl x (fsfs, bdb)
Results:
Testsuite fails for diff_tests.py 32, log_tests.py 30, and Ruby SWIG
dump_test. These are known problems and not a regression.
Local dependencies:
apache2-threaded-dev : 2.2.22-12
libapr1-dev : 1.4.6-3
libaprutil1-dev : 1.4.1-3
libdb5.1-dev : 5.1.29-5
libneon27-dev : 0.29.6-3
libsasl2-dev : 2.1.25.dfsg1-6
libsqlite3-dev : 3.7.13-1
perl : 5.14.2-16
python2.7-dev : 2.7.3~rc2-2.1
ruby1.8-dev : 1.8.7.358-6
openjdk-7-jdk : 7u3-2.1.3-1
serf : 1.2.x@1708
subversion-1.6.20.tar.bz2
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iQEcBAABCAAGBQJQ5HIzAAoJEHbXiOHtGlmcGkQH/AlkqTDNcbCZltcLCMsom/GE
bHokP1a/oguVSOsLbDtM3j4FG3MVsxDFfz9RVigzTAvoN6hFtfe1vBuFn/WWBclR
dZuYMjMYBmhloDnCzRJy8cYNj0jv2Q5FsvuqwFwq8S2vXMxn4E9UBajKw+kPuRdT
K20XtLzEDVB3MQK7hehAwKrKX1+bxQQ4YIo9EK/ERxszWsXWCgWurXqnTAlgKcpt
ykwj6NMqMylWtII0K5oLoCzAf0buXCJhO5bBUrFaNSzA7/Qd8jHpsA6ogtqALGhr
lh2z2wETFpTH9wZ2yQ31aC7wx/AKep63SjKoQxgVOOxKpm8H2P9rWbfZEdowll4=
=ETpa
-----END PGP SIGNATURE-----
subversion-1.60.20.tar.gz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iQEcBAABCAAGBQJQ5HIzAAoJEHbXiOHtGlmc0zEH/0bDjrrTxQ7z5G7/itO5ReV4
NuvYWpJUGaC4LDIuXk7yZNgOJOrUNie7BrFiGfQXSxKPvq8eIfN8GFS/Q64Y2Da8
nZnWQRrtML/fU8p01K5/PnkC9sP4b4e8J+oxzTwe4QsFJ/SmC/yWnIYeENGjKzXS
y1bXqcLmzmYWWLKB+TMgWwVZbDH1u7aXOXGKy0p1XKab05y/VeVs9GO3jCt8oRtL
TeplFreXkIvnjZdMkjZqKIXoRQ4s3PlJ+UWkfsXc6QPgHVHPH4/0DHTCgp7kBXSU
aEdSVElDULbnsZF5wm9A2gmwF/8no41ZO/yl04R/ZtyCFfMXmEaqY4hbvXizgBE=
=G3vu
-----END PGP SIGNATURE-----
--
Certified & Supported Apache Subversion Downloads:
http://www.wandisco.com/subversion/download
Re: 1.6.20 up for testing/signing
Posted by Ben Reser <be...@reser.org>.
On Thu, Dec 27, 2012 at 12:54 PM, Ben Reser <be...@reser.org> wrote:
> The 1.6.20 release artifacts are now available for testing/signing.
> Please get the tarballs from
> https://dist.apache.org/repos/dist/dev/subversion
> and add your signatures there. I plan to try and release on January
> 4th so please try and get your votes/signatures in place by January
> 3rd EOD. Thanks!
Voting is at
UNIX: 2
Windows: 2
Hopefully we can get the one more vote for each platform in the next
24 hours or so.
Re: 1.6.20 up for testing/signing
Posted by Johan Corveleyn <jc...@gmail.com>.
On Thu, Dec 27, 2012 at 9:54 PM, Ben Reser <be...@reser.org> wrote:
> The 1.6.20 release artifacts are now available for testing/signing.
> Please get the tarballs from
> https://dist.apache.org/repos/dist/dev/subversion
> and add your signatures there. I plan to try and release on January
> 4th so please try and get your votes/signatures in place by January
> 3rd EOD. Thanks!
>
> Please note the following known test failures (perhaps most easily
> triggered with APR-1.4.6):
>
> log_tests.py 30: log -g should ignore cyclic merges
> Can fail because 1.6.x is missing r1293229, which fixed occasionally
> missing merged-via notifications.
>
> diff_tests.py 32: repos-wc diff showing added entries with props
> Can fail because this test is missing various tweaks to account
> for random output order of 'svn diff' (this is independent of the
> APR 1.4.6 hash order problem).
>
> ruby swig test 'test_dump'
> Can fail because 1.6.x is missing r966458, which sorted property
> listings in dump files in alphabetical order, and this test does
> not parse dump files and sort properties for comparison.
Summary
-------
+1 to release
Platform
--------
Windows XP (32 bit) SP3
Microsoft Visual Studio 2010 SP1
Verified
--------
Signature and sha1 for subversion-1.6.20.zip.
Contents of subversion-1.6.20.zip are identical to tags/1.6.20, and to
branches/1.6.x@1426281 (except for expected differences in svn_version.h).
Tested
------
[ Release build ] x [ fsfs ] x [ file | svn | neon | serf ]
Results
-------
All tests pass (which is expected because I'm still using APR 1.4.5)
Dependencies
------------
Httpd 2.2.22
Apr 1.4.5
Apr-Util 1.4.1
Apr-Iconv 1.2.1
Neon 0.29.6
OpenSSL 1.0.0d
SQLite 3.7.14.1
ZLib 1.2.6
Serf 0.7.1
(as mentioned elsethread, there are build problems for 1.6 with serf 1.x,
but these are considered non-blocking -- using serf 0.7.1 instead)
Signature
---------
subversion-1.6.20.zip:
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
iQIcBAABCgAGBQJQ5KL9AAoJELWc5tYBDIqtRyMQAJxjtCnGidB+zEQVXbPNvFrC
kL0eQ/dzmVDnVZPkviEmHWdtBQACtzJiHiQ8nEgjEeP+fAjeaGiir7dYDIoHtMLx
zWYeqOp1+TgHI1r0tVeaGHjo0wXZsNlrFm+Vp6sjoRn4tv3SbPIaGFCO66vRV33a
UE9fpMk6YOIUiUsWbtcjSTLHINrAxd2wYCCvV/OCTUch+XHLGfEEeg6f9fywicKk
MuPq8Tdo45kiXUjU+c/27bIK0dCv8eEbleiZnpwkYVCIYs1Y7gtHBQZXTaUizbdj
wEbAxZeYXZOxlsITmGwZNbz8tN0eZQDLPU4vhRymYr+rCEWVYfoiNpxj9eyQtv+t
mC9QSbWGTvCaCE4TMEySpEiDMn/MxvYDfObjtOc/BOKPEF/W/cDYgpNYMneadvl2
YwReQaUyXzZuVXKYFDit01rw7gkvOxnwmvcE1e/B8JNgyp9xD5xqlVLC7YOYgUG/
Ia4deMj0XexJZvnL5awW+e8O7BDRWoAw4lr2WNY812dOOhLzAtBFAgMyYKM6RM1T
ZyaJlHIjV+vc8/tsu8MD7JuP26QySx0focfgIk8h2xLENUu6Afi/GutQrC8nbEXS
28ixddk9VBn2WR1lqCn9i0FFoHKXbx8+som9IABQlZmvMznbZkAEVWnibUS2X69s
zDcZZMbkUuQROtK8UXmQ
=pQgS
-----END PGP SIGNATURE-----
--
Johan
Re: 1.6.20 up for testing/signing
Posted by Mark Phippard <ma...@gmail.com>.
SUMMARY:
+1 to release
PLATFORM:
Windows 7
VS 2008 SP1
Java 1.6
COMPONENTS:
Apache 2.2.15
OpenSSL 1.0.0a
Neon 0.29.6
ZLib 1.2.4
VERIFIED:
signature and sha1
TESTED:
JavaHL
ra_local | ra_svn
RESULTS:
All passed
SIGNATURES:
subversion-1.6.20.zip
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
iEYEABECAAYFAlDsc/cACgkQJl34oANalqlLmwCfei6wOm1yUNQ3JTk3DciiPd3M
GEEAnjKlyHkhYw0WRbwM/CYEoMX5Qn5t
=69eR
-----END PGP SIGNATURE-----
--
Thanks
Mark Phippard
http://markphip.blogspot.com/