On Mon, 18 Sep 2006 20:58:24 +0530, Garrett Rooney
> On 9/18/06, Madan U Sreenivasan <firstname.lastname@example.org> wrote:
>> On Mon, 18 Sep 2006 20:10:41 +0530, Garrett Rooney
>> <email@example.com> wrote:
>> > On 9/18/06, Madan U Sreenivasan <firstname.lastname@example.org> wrote:
>> >> Hi,
>> >> After a couple of weeks of breaking my head over why svn on my
>> >> laptop
>> >> was not working ('Malformed URL' error), I figured with the help of
>> >> mailing list archive, that neon 0.26 has some problems.... I went
>> >> to
>> >> neon 0.25.3, and it works.
>> > Umm, care to be more specific about what didn't work? AFAIK 0.26
>> > should generally work, the only issues with it were compile warnings
>> > and some build system glue. If there are actual problems with it, I'd
>> > love to hear what the specifics are.
>> I used to get 'Malformed URL' errors during checkins. I had no success
>> trying to debug...
> Well, considering that you can make it happen, and others can't, it'd
> be great if you could get some neon debugging traces, or perhaps
> backtraces from where the errors are coming from.
Well, good news and not so good news....
- good news is that I was wrong, I upgraded to neon 0.26 again, and svn
- 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
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
Today, while trying to debug:
unmasked neon 0.26
(Pl. note that I 'emerge sync'ed twice last week)
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Tue Sep 19 08:11:07 2006