Package: subversion
Version: 1.2.3dfsg1-3
Severity: grave
G'day.
I have run into a problem where I can't commit a change to my subversion
repository via HTTP/SSL.
The problem seems identical to the one described in this bug report, but
my issues continue despite running the version that claims
[Peter Samuelson]
Oh, doh! /usr/bin/svn will not use libneon25, so that accomplished
nothing.
I came up with several ways around this - the latest is to use
libneon24 but *not* link libssl0.9.8. There was never any reason for
us to link to openssl at all; this was a packaging bug.
Can you
Peter Samuelson wrote:
I came up with several ways around this - the latest is to use
libneon24 but *not* link libssl0.9.8. There was never any reason for
us to link to openssl at all; this was a packaging bug.
Can you please retest with my packages at
http://p12n.org/tmp/svn-336373/ ?
[Sven-Haegar Koch]
Having had the same problem, your test-packages recompiled locally
(just decreased the version number, I want the official one to
upgrade the test one when its released) fixes it for me.
Great! We'll close the bug on the next upload, then, unless Thomas
reports that this
Hi,
On Wed, 9 Nov 2005 06:00:01 -0600
Peter Samuelson [EMAIL PROTECTED] wrote:
Can you please retest with my packages at
http://p12n.org/tmp/svn-336373/ ?
I've tested them, and I've been able to import the whole uClibc source
code through https:// without any problem (while it was previously
Hi,
On Sun, 6 Nov 2005 13:47:01 -0600
Peter Samuelson [EMAIL PROTECTED] wrote:
Since you have a ready test case for this, can you try the neon
package at
http://www.barcikacomp.hu/deb/libneon25_0.25.4.dfsg-1_i386.deb, as
mentioned in Bug #335574?
With a Debian sid updated yesterday and your
[Thomas Petazzoni]
Since you have a ready test case for this, can you try the neon
package at
http://www.barcikacomp.hu/deb/libneon25_0.25.4.dfsg-1_i386.deb, as
mentioned in Bug #335574?
With a Debian sid updated yesterday and your package, it still doesn't
work:
Oh, doh!
[Peter Samuelson]
Oh, doh! /usr/bin/svn will not use libneon25, so that accomplished
nothing.
I'll build a new set of packages that use libneon25 instead
Well, now I see why Debian ships both neon24 and neon25. subversion
won't yet compile against neon25, and I don't have the time or
First, apologies for the delayed response - I didn't get the BTS mail
until the other day, possibly because of the known mail backlog
affecting certain Debian services.
svn: MKCOL of
'/svn/thomas/!svn/wrk/b82d4a0a-4a04-0410-8ac2-c33f329d32ff/uclibc-sos/trunk/test/string':
Could not read
[Thomas Petazzoni]
Maybe it's a problem around libneon24 (linked against openssl0.9.7)
and the fact that subversion is linked against openssl 0.9.8.
Since you have a ready test case for this, can you try the neon package
at http://www.barcikacomp.hu/deb/libneon25_0.25.4.dfsg-1_i386.deb, as
Package: subversion
Version: 1.2.3dfsg1-2
Severity: grave
Justification: renders package unusable
Hi,
While trying to import files inside a Subversion repository accessed
through https, I get the following error, fully reproducible (everytime
on the same directory):
svn: MKCOL of
11 matches
Mail list logo
