That's not the problem here though.
The (temporary) solution for me is to preload libneon.so.27, so I
created and alias:
svn: aliased to LD_PRELOAD=/usr/lib/libneon.so.27 /usr/bin/svn
--
subversion doesn't permanently accept certificates
https://bugs.launchpad.net/bugs/272386
You received this
The problem vanished in hardy for me after a while, I dont know why
though, maybe another update from backports? I didnt think of it again
untill I faced the same problem on Intrepid after dist-upgrade.
--
subversion doesn't permanently accept certificates
https://bugs.launchpad.net/bugs/272386
Same problem here. I notice that svn is now linked against gnutls via
libneon27-gnutls (used to be openssl via libneon26/27?), I dont know if
that makes any difference as to what location svn will look for CA
certs?
I tried briefly now to use strace to see what is going on, and got even
more confu
I tested this like 2 months ago, and it doesnt really matter if it is in gutsy
and hardy, the problem is, as subject suggests, in fesity.
I've given up on waiting for this to be fixed in feisty, I dont have any feisty
machines left to upgrade. But I do know that the fix works!
--
feisty->gutsy
Confirmed, and this bug is worse than what it might appear.
All the PNG files in gtkam are corrupt, and fails to be viewed anywhere:
[EMAIL PROTECTED]:~# dpkg -L gtkam | grep png | xargs file
/usr/share/images/gtkam/gtkam-audio.png:
PNG image data, CORRUPTED,
