Show More
@@ -1,3 +1,8 b'' | |||
|
1 | ||
|
2 | 1.2.1 | |
|
3 | ~~~~~~~~~~~~ | |
|
4 | ||
|
5 | Tested against hg 4.8 (no changes needed). | |
|
1 | 6 | |
|
2 | 7 | 1.2.0 |
|
3 | 8 | ~~~~~~~~~~~~ |
@@ -15,8 +20,6 b' handling (propts).' | |||
|
15 | 20 | Refreshing smtp monkeypatch to be a bit more like modern mercurials |
|
16 | 21 | (in particular, obligatory cert falidaton). |
|
17 | 22 | |
|
18 | ||
|
19 | ||
|
20 | 23 | 1.1.9 |
|
21 | 24 | ~~~~~~~~~~~~ |
|
22 | 25 |
@@ -365,6 +365,15 b' for further pointers in keyring_ documen' | |||
|
365 | 365 | list, or issue tracker. Typically it will turn out, that you need to |
|
366 | 366 | install some missing tool, or library, and reinstall keyring. |
|
367 | 367 | |
|
368 | .. note:: | |
|
369 | ||
|
370 | Depending on keyring_ version, installation of some dependency may | |
|
371 | resolve problem. For example (as of late 2018), I got KDE Wallet | |
|
372 | backend working with pip-installed keyring after:: | |
|
373 | ||
|
374 | pip install dbus-python | |
|
375 | ||
|
376 | ||
|
368 | 377 | If ``keyring`` command works, but mercurial with mercurial_keyring does not, |
|
369 | 378 | try enforcing proper backend (by means of ``keyringrc.cfg``, see above). |
|
370 | 379 | Only if this doesn't help, there may be a bug in mercurial_keyring. |
@@ -379,6 +388,7 b" Only if this doesn't help, there may be " | |||
|
379 | 388 | |
|
380 | 389 | |
|
381 | 390 | |
|
391 | ||
|
382 | 392 | History |
|
383 | 393 | ======================================================= |
|
384 | 394 |
General Comments 0
You need to be logged in to leave comments.
Login now