This bug report is being closed due to your last comment regarding this
being fixed with an update. For future reference you can manage the
status of your own bugs by clicking on the current status in the yellow
line and then choosing a new status in the revealed drop down box. You
can learn more
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed
It's fixed since then
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/272386
Title:
subversion doesn't permanently accept certificates
To manage notifications about this bug go to:
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
Had the same problem. After executing
sudo chown -R $USER:$USER ~/.subversion
it worked again
--
subversion doesn't permanently accept certificates
https://bugs.launchpad.net/bugs/272386
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I can still confirm this bug on a recently updated machine running hardy
heron. I added the backports repos and it updated subversion, though the
problem still exists.
** Changed in: subversion (Ubuntu)
Status: New = Confirmed
--
subversion doesn't permanently accept certificates
Subversion should tell about the issue that the files in ~/.subversion
are not writable.
--
subversion doesn't permanently accept certificates
https://bugs.launchpad.net/bugs/272386
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
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
it seems my ~/.subversion directory had wrong permissions and set owner and
group to root.
yet the fact that sourceforge certificate is considered unsafe is wrong
--
subversion doesn't permanently accept certificates
https://bugs.launchpad.net/bugs/272386
You received this bug notification
10 matches
Mail list logo
