First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 148306
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Paul de Vrieze <pauldv@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Thomas Capricelli <orzel@freehackers.org>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 148306 depends on: Show dependency tree
Bug 148306 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2006-09-20 02:23 0000
i updated my system today, and since then i can't use subversion on https://
URL (like kde svn).
It appears subversion has been bumped to 1.4 (i'm ~amd64)
So i thought it was the pb and went back to subversion 1.3.2-r3. Two things
* svn 1.4 changed my checkout automatically to the new 1.4 format=noxml, so i
can't use svn 1.3 anymore. This is important, maybe 1.4 shouldn't be unmasked
as soon, even for ~
* 1.3.2-r3 has the same problem. It seems(as read in bugs.gentoo.org) that neon
is often the source of problems, so i decided to unmerge neon-0.26.1 and
subversion, and go for what i was using yesterday : neon-0.25.5 and svn 1.3.2
(with no -r?)

And it goes well. It works ! Though i should tell you

Example of failure :
orzel kdeutils% svn up
svn: PROPFIND request failed on '/home/kde/branches/KDE/3.5/kdeutils'
svn: PROPFIND of '/home/kde/branches/KDE/3.5/kdeutils': SSL negotiation failed:
SSL alert received: Handshake failed (https://svn.kde.org)

------- Comment #1 From Jakub Moc (RETIRED) 2006-09-20 02:30:41 0000 -------
Need to re-emerge neon after openssl upgrade.

*** This bug has been marked as a duplicate of 147618 ***

------- Comment #2 From Thomas Capricelli 2006-09-20 02:44:24 0000 -------
i dont think this is right.
My failing neon-0.26.1 had actually been emerged after openssl-0.9.8c as seen
by genlop : 
     Tue Sep 19 19:46:46 2006 >>> dev-libs/openssl-0.9.8c-r2
     Tue Sep 19 22:15:52 2006 >>> net-misc/neon-0.26.1
     Wed Sep 20 10:49:26 2006 >>> dev-util/subversion-1.4.0
And this configuration fails to run.
As such, i dont see the bug as being a duplicate of 147618.

------- Comment #3 From Thomas Capricelli 2006-09-21 04:11:59 0000 -------
i've tried another time today : 
i unmerged neon and subversion
i recompiled both again
and i've got the same problem. So this is not just about recompiling neon

Some misc information :

 * dev-libs/openssl
     Wed May 10 12:23:53 2006 >>> dev-libs/openssl-0.9.7j
     Tue Sep 19 19:46:46 2006 >>> dev-libs/openssl-0.9.8c-r2
 * net-misc/neon
     Wed Sep 20 11:18:00 2006 >>> net-misc/neon-0.25.5
     Thu Sep 21 12:53:44 2006 >>> net-misc/neon-0.26.1
 * dev-util/subversion
     Wed Sep 20 11:05:32 2006 >>> dev-util/subversion-1.3.2-r3
     Wed Sep 20 11:22:36 2006 >>> dev-util/subversion-1.3.2
     Thu Sep 21 12:58:42 2006 >>> dev-util/subversion-1.4.0


my ldd : 

orzel@berlioz kde-3.5/kdeutils/kcalc% ldd /usr/bin/svn
        libsvn_client-1.so.0 => /usr/lib64/libsvn_client-1.so.0
(0x00002ab500456000)
        libsvn_wc-1.so.0 => /usr/lib64/libsvn_wc-1.so.0 (0x00002ab500580000)
        libsvn_ra-1.so.0 => /usr/lib64/libsvn_ra-1.so.0 (0x00002ab5006b4000)
        libsvn_diff-1.so.0 => /usr/lib64/libsvn_diff-1.so.0
(0x00002ab5007b8000)
        libsvn_ra_local-1.so.0 => /usr/lib64/libsvn_ra_local-1.so.0
(0x00002ab5008c0000)
        libsvn_repos-1.so.0 => /usr/lib64/libsvn_repos-1.so.0
(0x00002ab5009c7000)
        libsvn_fs-1.so.0 => /usr/lib64/libsvn_fs-1.so.0 (0x00002ab500ae9000)
        libsvn_fs_fs-1.so.0 => /usr/lib64/libsvn_fs_fs-1.so.0
(0x00002ab500bf0000)
        libsvn_fs_base-1.so.0 => /usr/lib64/libsvn_fs_base-1.so.0
(0x00002ab500d0d000)
        libsvn_ra_svn-1.so.0 => /usr/lib64/libsvn_ra_svn-1.so.0
(0x00002ab500e38000)
        libsvn_ra_dav-1.so.0 => /usr/lib64/libsvn_ra_dav-1.so.0
(0x00002ab500f4e000)
        libsvn_delta-1.so.0 => /usr/lib64/libsvn_delta-1.so.0
(0x00002ab50106b000)
        libsvn_subr-1.so.0 => /usr/lib64/libsvn_subr-1.so.0
(0x00002ab501176000)
        libaprutil-0.so.0 => /usr/lib64/libaprutil-0.so.0 (0x00002ab5012ac000)
        libdb-4.2.so => /usr/lib64/libdb-4.2.so (0x00002ab5013c4000)
        libapr-0.so.0 => /usr/lib64/libapr-0.so.0 (0x00002ab5015a5000)
        librt.so.1 => /lib/librt.so.1 (0x00002ab501704000)
        libm.so.6 => /lib/libm.so.6 (0x00002ab50180d000)
        libcrypt.so.1 => /lib/libcrypt.so.1 (0x00002ab501965000)
        libpthread.so.0 => /lib/libpthread.so.0 (0x00002ab501a9a000)
        libdl.so.2 => /lib/libdl.so.2 (0x00002ab501bb0000)
        libneon.so.26 => /usr/lib64/libneon.so.26 (0x00002ab501cb4000)
        libgnutls.so.12 => /usr/lib64/libgnutls.so.12 (0x00002ab501dd6000)
        libgcrypt.so.11 => /usr/lib64/libgcrypt.so.11 (0x00002ab501f5b000)
        libnsl.so.1 => /lib/libnsl.so.1 (0x00002ab5020a5000)
        libgpg-error.so.0 => /usr/lib64/libgpg-error.so.0 (0x00002ab5021bc000)
        libexpat.so.1 => /usr/lib64/libexpat.so.1 (0x00002ab5022bf000)
        libz.so.1 => /lib/libz.so.1 (0x00002ab5023ed000)
        libc.so.6 => /lib/libc.so.6 (0x00002ab502502000)
        /lib64/ld-linux-x86-64.so.2 (0x00002ab500339000)

------- Comment #4 From Paul de Vrieze 2006-09-21 11:53:50 0000 -------
I assume that you have actually got access to that host? I can't verify because
https is not available for anonymous svn. Could you try on different svn
servers too? Perhaps if it is possible for you, try with neon-0.25.5 .

------- Comment #5 From Thomas Capricelli 2006-09-21 13:27:16 0000 -------
of course, i can reach this host. see my comment 
https://bugs.gentoo.org/show_bug.cgi?id=148306#c0
(first for this bug)

where i explain how to get a working configuration

------- Comment #6 From Mark Keisler 2006-09-21 13:50:22 0000 -------
https works fine for anonymous svn access.
I had the same issue after updating subversion, but a rebuild of neon without
having to rebuild subversion fixed the issue for me.  neon also had a new flag
in that build (expat), but that shouldn't make a difference.

------- Comment #7 From Paul de Vrieze 2006-09-23 07:36:13 0000 -------
Could you give me the exact url you try to update (use "svn info" to get it if
you forgot it) and confirm that this one has anonymous read access (For example
by using a webbrowser to go there). I use https myself where the only
difference is that my openssl does not have a revision. And it just works.

------- Comment #8 From Thomas Capricelli 2006-09-23 07:46:31 0000 -------
This is the kde svn, and i dont think you can have anonymous access using this
url. (there are other ways, of course).
Moreover, i'm using a proxy to connect to it (through ~/.subversion/servers)

I've tried to connect using konqueror on the same url. I have to provide my
login/passwd, but then i can browse the files. Whether i'm using the proxy, or
not.

orzel@berlioz svn/kde-3.5/kdelibs% svn up
svn: PROPFIND request failed on '/home/kde/branches/KDE/3.5/kdelibs'
svn: PROPFIND of '/home/kde/branches/KDE/3.5/kdelibs': SSL negotiation failed:
SSL alert received: Handshake failed (https://svn.kde.org)
orzel@berlioz svn/kde-3.5/kdelibs% svn info
Path: .
URL: https://orzel@svn.kde.org/home/kde/branches/KDE/3.5/kdelibs

------- Comment #9 From Paul de Vrieze 2006-09-23 08:03:45 0000 -------
If you have the option (if you don't use other apps that require neon-0.26) to
use the 0.25 version. That one is better tested with subversion, although 0.26
does not give problems here in a similar setting. One thing I also remember as
possibly problematic is gnutls. If compiled with gnutls, please try neon
without gnutls (with openssl).

------- Comment #10 From Thomas Capricelli 2006-09-23 11:14:54 0000 -------
As i state in my first comment, i _does_ work with neon 0.25.5!!

About the ssl/tls problem. i have this : 
[ebuild   R   ] net-misc/neon-0.26.1  USE="gnutls nls ssl zlib -expat -socks5
-static" 0 kB

so i guess i'm already using the openssh thinguy.. no ?

------- Comment #11 From Thomas Capricelli 2006-09-23 11:17:43 0000 -------
I tried that just to check : 
USE=-ssl emerge neon -vta

[ebuild   R   ] net-misc/neon-0.26.1  USE="gnutls nls zlib -expat -socks5 -ssl*
-static" 0 kB

And doesn't work neither (same error):

svn: PROPFIND request failed on '/home/kde/branches/KDE/3.5/kde-common/admin'
svn: PROPFIND of '/home/kde/branches/KDE/3.5/kde-common/admin': SSL negotiation
failed: SSL alert received: Handshake failed (https://svn.kde.org)

------- Comment #12 From Paul de Vrieze 2006-09-23 11:21:38 0000 -------
No you use gnutls. Please try to add 
"net-misc -gnutls"
to your /etc/portage/package.use and rebuild neon.

Neon-0.25.5 does not try to use gnutls at all. I've seen some cases of gnutls
not working, so it's a likely cause of your troubles. If this works, please
confirm so the option for gnutls can be removed from neon.

------- Comment #13 From Paul de Vrieze 2006-09-23 11:25:41 0000 -------
The line should be "net-misc -gnutls ssl", not "net-misc -gnutls".

------- Comment #14 From Thomas Capricelli 2006-09-23 17:41:04 0000 -------
[ebuild  N    ] dev-util/subversion-1.4.0  USE="berkdb java nls perl python
-apache2 -bash-completion -emacs -nowebdav -ruby" 0 kB
[ebuild  N    ]  net-misc/neon-0.26.1  USE="nls ssl zlib -expat -gnutls -socks5
-static" 0 kB

this way, it works. So gnutls is probably to blame here indeed.
(sorry, i was focusing on the 'ssl' USE, and i missed the (obvious) gnutls.

------- Comment #15 From Thomas Capricelli 2007-06-13 18:11:20 0000 -------
it's over now i think.

First Last Prev Next    No search results available      Search page      Enter new bug