Show More
@@ -125,7 +125,9 b' details.' | |||
|
125 | 125 | default-keyring=keyring.backends.Gnome.Keyring |
|
126 | 126 | # default-keyring=keyring.backends.kwallet.Keyring |
|
127 | 127 | |
|
128 |
For list of known backends run ``pydoc keyring.backends`` |
|
|
128 | For list of known backends run ``pydoc keyring.backends`` or | |
|
129 | ``keyring --list-backends`` (which of those commands work, | |
|
130 | depends on the keyring_ version). | |
|
129 | 131 | |
|
130 | 132 | |
|
131 | 133 | ``hgrc`` configuration (HTTP) |
@@ -320,6 +322,61 b' The extension is monkey-patching the mer' | |||
|
320 | 322 | to replace the ``find_user_password`` method. Detailed order of operations |
|
321 | 323 | is described in the comments inside `the code`_. |
|
322 | 324 | |
|
325 | Frequent problems | |
|
326 | ======================================================= | |
|
327 | ||
|
328 | Most problems people face while using ``mercurial_keyring`` are in | |
|
329 | fact problems with ``keyring`` library and it's backends. In | |
|
330 | particular, those can manifest by: | |
|
331 | ||
|
332 | - technical errors mentioning sentences like ``No recommended backend | |
|
333 | was available. Install the keyrings.alt package…`` (or similar), | |
|
334 | ||
|
335 | - password prompts on every action (= passwords not being saved). | |
|
336 | ||
|
337 | Those almost always mean that *natural* keyring backend for given | |
|
338 | desktop type doesn't work, or is not present at all. For example, | |
|
339 | some necessary runtime component can be down (say, you use Linux, but | |
|
340 | have neither Gnome Keyring, nor KDE Wallet, running). Or appropriate | |
|
341 | backend is not installed because it could not be build during | |
|
342 | keyring_ library installation (maybe because some required library | |
|
343 | was not present at the moment of keyring installation, or maybe because compiler | |
|
344 | as such is not present on the system). | |
|
345 | ||
|
346 | To diagnose such problems, try using ``keyring`` utility, as described | |
|
347 | on keyring_ documentation page, for example by:: | |
|
348 | ||
|
349 | keyring --list-backends | |
|
350 | keyring -b keyrings.alt.Gnome.Keyring set testsvc testuser | |
|
351 | keyring -b keyrings.alt.Gnome.Keyring get testsvc testuser | |
|
352 | ||
|
353 | (of course using appropriate backend). If you miss the ``keyring`` command | |
|
354 | as such, try ``python -m keyring`` instead:: | |
|
355 | ||
|
356 | python -m keyring --list-backends | |
|
357 | python -m keyring -b keyrings.alt.Gnome.Keyring set testsvc testuser | |
|
358 | python -m keyring -b keyrings.alt.Gnome.Keyring get testsvc testuser | |
|
359 | ||
|
360 | If appropriate backend is missing (not listed), or doesn't work | |
|
361 | (second or third command fails), your keyring is broken. Try looking | |
|
362 | for further pointers in keyring_ documentation, that project mailing | |
|
363 | list, or issue tracker. Typically it will turn out, that you need to | |
|
364 | install some missing tool, or library, and reinstall keyring. | |
|
365 | ||
|
366 | If ``keyring`` command works, but mercurial with mercurial_keyring does not, | |
|
367 | try enforcing proper backend (by means of ``keyringrc.cfg``, see above). | |
|
368 | Only if this doesn't help, there may be a bug in mercurial_keyring. | |
|
369 | ||
|
370 | .. note:: | |
|
371 | ||
|
372 | By far easiest way to have properly working keyring is to use | |
|
373 | packaged binary version (like ``python-keyring`` Ubuntu package, or | |
|
374 | keyring bundled with TortoiseHG on some systems). If you pip-installed | |
|
375 | keyring and it doesn't work, you may consider ``pip uninstall keyring`` | |
|
376 | and look for binary package instead. | |
|
377 | ||
|
378 | ||
|
379 | ||
|
323 | 380 | History |
|
324 | 381 | ======================================================= |
|
325 | 382 |
General Comments 0
You need to be logged in to leave comments.
Login now