![]() > each time (as opposed to a once-only request for the password to use > Performing an authenticated operation now prompts for an SVN password ![]() The reporting appears to be broken regardless of whether GNOME Keyring support is used. > After updating subversion to the current version, it has stopped using On Tue, at 01:31:46PM +0200, Tim Van Holder wrote: To: Tim Van Holder Re: Bug#901387: subversion: GNOME Keyring support is missing Looks like some backend changes happened somewhere which dropped support for non-GUI credential prompting, making it look as though SVN wasn't using GNOME keyring. A further "svn up" just ran without a password prompt. Running "svn up" after that still prompted me for my SVN password first, but then popped up a window asking for a password to unlock the keyring. Looks like this may in part be a DBus thing instead.īased on I ran dbus-update-activation-environment -systemd DISPLAY. (It's also odd that svn -version doesn't report GNOME Keyring support.) However, I don't think I updated any packages alongside subversion, so this is an odd change in behaviour. The same happens with Seahorse, which fails to unlock the keyring. Jun 12 15:27:54 leeloo gnome-keyring-d: couldn't create system prompt: GDBus.Error.Spawn.ChildExited: Process exited with status 1 Jun 12 15:27:54 leeloo gcr-prompter: cannot open display: Jun 12 15:27:54 leeloo : Unable to init server: Could not connect: Connection refused Looking at /var/log/messages, it looks like it IS trying to do something with the keyring when I enter the password, I see Yes, libpam-gnome-keyring is installed (but I've never managed to have it work for SSH+X). That is why I expected the lock message to come from KWallet. GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DBĭate: Tue, 13:46:07 +0000 It has always worked in the past when svn was run, I got a prompt to unlock the default keyring (I run in SSH + X forwarding, so that doesn't happen automatically on login). ![]() I'm not sure how one normally unlocks the keyring, but it seems like That, I would assume you have something installed (likely the It's trying to use the keyring, but the keyring is locked. > before continuing with the SVN operation. > .IsLocked: Cannot create an item in a locked > ** Message: Remote error from secret service: > (as opposed to a once-only request for the password to use to unlock the > Performing an authenticated operation now prompts for an SVN password each time The reporting appears to be broken regardless of whether GNOME Keyring > After updating subversion to the current version, it has stopped using GNOME Versions of packages subversion suggests: Versions of packages subversion depends on: Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores) IsLocked: Cannot create an item in a lockedīefore continuing with the SVN operation. ** Message: Remote error from secret service: (as opposed to a once-only request for the password to use to unlock the Performing an authenticated operation now prompts for an SVN password each time It's very unlikely that you are using BDB repositories.Date: Tue, 13:31:46 +0200 Package: subversionĪfter updating subversion to the current version, it has stopped using GNOME Berkeley DB (BDB) repository backend is deprecated and hasn't been used for years by default. Persistence after an error can cause a repository to be “wedged,” asĭescribed in the section called “Berkeley DB Recovery”. There are database locks, used internally by the Berkeley DBīackend to prevent clashes between multiple programs trying toĪccess the database. The third column of svn status output, and removed by the svnĬleanup command, as described in the section called “Sometimes You This is the sort of lock indicated by an L in The second is administrative locks, used internally by Subversion to prevent clashes between multiple Subversion clients operating on There are two other sorts of “lock” with which Subversion sometimes The words “lock” and “locking” describe a mechanism for mutualĮxclusion between users to avoid clashing commits. In general a lock is applied by SubVersion when something un-common happen and particular cuncurrency scenarious, it to prevent unusual unexpected behaviour during next operations, for example a commit.
0 Comments
Leave a Reply. |