[Bug 481440] Re: svn status -u not working anymore since upgrade to karmic

Maarten Bezemer maarten.bezemer at gmail.com
Mon Apr 30 21:25:57 UTC 2012


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 with some of the updates. It would help us a lot if
you could test it on a currently supported Ubuntu version. When you test
it and it is still an issue, kindly upload the updated logs by running
apport-collect 481440 and any other logs that are relevant for this
particular issue.

** Changed in: subversion (Ubuntu)
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to subversion in Ubuntu.
https://bugs.launchpad.net/bugs/481440

Title:
  svn status -u not working anymore since upgrade to karmic

Status in “subversion” package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: subversion

  Upgraded from Jaunty to karmic last week, and using subversion now for
  the first time since that upgrade.

  It seems in some strange way the subversion client is now bound to
  gnome functionality for authenticating against servers and does use
  the authentication tokens alsready stored in my subversion config
  directory anymore, instead asking for some gnome "apps" keyring
  password, which I seem not to know.

  It looks like this:

  username at myhost:/path/to/workdir$ svn status -u
  Password for 'apps' GNOME keyring: 
  svn: OPTIONS of 'https://svn.project.org/svn/path/to/repository': authorization failed: Could not authenticate to server: rejected Basic challenge (https://svn.project.org)

  The client worked perfectly and for many months before this happened.

  While it might be not a too bad idea to use gnome keyring in general,
  I see it as a failure that svn does not revert to the "usual"
  authentication methods if that fails. That's not O.K., and I'm really
  in trouble now!

  
  $ lsb_release -rd
  Description:	Ubuntu 9.10
  Release:	9.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/subversion/+bug/481440/+subscriptions




More information about the foundations-bugs mailing list