> - good news is that I was wrong, I upgraded to neon 0.26 again, and svn
> works
>
> - the not-so-good news is that, am unable to figure what caused the error
> last week. Am suspecting my usage of the gentoo portage tree. Maybe some
> gentoo user could help me out here.
>
> This is what I did last week:
> emerge neon (which upgraded from whatever I had to 0.26)
> ran svn (gave me 'unable to find libneon.so.26' error) - This is
> where I doubt the portage tree
> copied /usr/lib/libneon.so.25 to /usr/lib/libneon.so.26 for testing
> purposes
> svn gave me the 'Malformed URL' error
>
> In an attempt to solve the problem:
> masked the neon 0.26 package and downgraded to 0.25.3
> svn worked
>
> Today, while trying to debug:
> unmasked neon 0.26
> emerge neon
> svn worked
>
> (Pl. note that I 'emerge sync'ed twice last week)
>
> Regards,
> Madan.
did u execute "revdep-rebuild"? (emerge gentoolkit)
cheers
Shirish
PS: Neon 0.26.x hashardcoded GSSAPI disabled on gentoo, change the ebuild,
if u need to use SSPI.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Sep 19 11:06:25 2006