From: [email protected]

Re,

i had thought as i was using svn+ssh that libapr0 wouldn't matter. Yet downgrading libapr0 to 2.0.50-8 fixed the problem. Apparently libapr0 is
also involved in svn: and svn+ssh: transfers for some reason.

--
Best regards,
Kilian

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQBBIiUovdkzt4X+wX8RAmmFAJ9p5Vd0vw+LBOCQ7jv9zF7le7vk+gCcCT2g yfFKceQRs5Tjb9r6b0d05AE=
=272u
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)

From: [email protected]

[Kilian Krause]

i had thought as i was using svn+ssh that libapr0 wouldn't matter. Yet downgrading libapr0 to 2.0.50-8 fixed the problem.

Yes, known issue - libapr0 had an ABI compatibility problem just now.
Can you confirm that subversion 1.0.6-1.1 (should hit the archive soon)
works again?

Peter

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFBI2CCXk7sIRPQRh0RAm75AJ9XvloL2HOM69ZFLaMaE6z+0fy9XQCgozAY s8ztFqPZFJX7m9lKNCRfKfc=
=0c3n
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)

From: [email protected]

Hi Peter,

yep, works like a charm. ;)

Am Mi, den 18.08.2004 schrieb Peter Samuelson um 15:58:

[Kilian Krause]

i had thought as i was using svn+ssh that libapr0 wouldn't matter. Yet downgrading libapr0 to 2.0.50-8 fixed the problem.

Yes, known issue - libapr0 had an ABI compatibility problem just now.
Can you confirm that subversion 1.0.6-1.1 (should hit the archive soon)
works again?

Peter

--
Best regards,
Kilian

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQBBI2Javdkzt4X+wX8RAoM9AJ4jqyF/xn4s+eP3uMyTOaMpdgBN0gCfWdqJ rgb7JQa7cDOu4lSKcY+UplY=
=YkrG
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)