On dinsdag 2 juni 2009 16:31:03 Brad King wrote:
> Hi Peter,
>
> I had the same problem this morning and then saw your message.
> I used 'ldd' to see what libraries the svn client uses, and
> then looked at which ones changed when I updated yesterday.
> Then I backed off one package at a time until
Brad King wrote:
OK, I got it to work. THANKS! In case anyone else is reading this
1) I added a stable debian repository in /etc/apt/sources.list
2) aptitude update
3) Checked versions of libneon27-gnutls using "v" key, removed bad one
and installed libneon27-gnutls (0.28.2-6.1)
cheers Pete
Peter Robinson wrote:
For what ever reason I was not able to downgrade as above.
If your /etc/apt/sources.list does not refer to 'stable' then the
method I posted may not work.
> I then
uninstalled the 0.28.4-1 version and installed the previous one from
/var/cache/apt/archives#
dpkg -i lib
Brad King wrote:
Hi Peter,
I had the same problem this morning and then saw your message.
I used 'ldd' to see what libraries the svn client uses, and
then looked at which ones changed when I updated yesterday.
Then I backed off one package at a time until the problem
went away.
My client works
Brad King wrote:
Then run 'sudo apt-get install libneon27-gnutls'. It should
downgrade the package.
Bad version: libneon27-gnutls (0.28.4-1)
Good version: libneon27-gnutls (0.28.2-6.1)
It looks like this is already known:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=529920
-Brad
--
Hi Peter,
I had the same problem this morning and then saw your message.
I used 'ldd' to see what libraries the svn client uses, and
then looked at which ones changed when I updated yesterday.
Then I backed off one package at a time until the problem
went away.
My client works again after downgr
6 matches
Mail list logo