![]() You should be asked for the password only once (per every username+remote_repository_url combination). Just as in case of HTTP, you must set username, but must not set password here to use the extension, in other cases it will revert to the default behaviour.Ĭonfigure the repository as above, then just pull and push (or email) as needed. hg/hgrc, or ~/.hgrc (the latter is usually preferable) and set there all standard email and smtp properties, including smtp username, but without smtp password. So, in both cases, it is effectively reverting to the default behaviour.Įdit either repository-local. If the username is not given, extension will prompt for credentials every time, also without saving the password. hg/hgrc, the extension will use them without using the password database. Simpler form with url-embedded name can also be used:īitbucket = if both the username and password are given in. hg/hgrc and save there the remote repository path and the username, but do not save the password. Refer to keyring docs for more details.Įdit repository-local. Still, if necessary, it can be configured using ~/keyringrc.cfg file ( keyringrc.cfg in the home directory of the current user). The most appropriate password backend should usually be picked automatically, without configuration. rcurial_keyring = /path/to/mercurial_keyring.py hgrc to enable the extension by adding following lines: ![]() Not only can the commit tool commit your changes, but it can also examine the state of your working directory and perform most routine maintenance tasks (add new files, detect renames, manage the ignore filter, etc). On Debian "Sid" the library can be also installed from the official archive (packages python-keyring, python-keyring-gnome and python-keyring-kwallet).Ī) Install mercurial_keyring as a module from PyPi:ī) Download, save this file anywhere on the system (preferably in hgext directory), and configure your. The commit tool is second most commonly used application after the Workbench. ![]() (or use any other method to install it from PIP). In case the password turns out incorrect (either because it was invalid, or because it was changed on the server) it just prompts the user again. Similarly, while sending emails via SMTP server which requires authorization, it prompts for the password on first use of given server, then saves it in the password database and reuses on successive runs. hg/hgrc, then for suitable password in the password database, and uses those credentials if found. On the next run it checks for the username in. The extension prompts for the HTTP password on the first pull/push to/from given remote repository (just like it is done by default), but saves the password (keyed by the combination of username and remote repository url) in the password database. ![]() Hg is a distributed version control, unlike other centralized ones, so you can commit even without a network connection available, since it is commiting to the local repository.Keyring extension uses services of the keyring library to securely save authentication passwords (HTTP/HTTPS and SMTP) using system specific password database (Gnome Keyring, KDE KWallet, OSXKe圜hain, dedicated solutions for Win32 and command line). Then you can proceed from the “Hg Workbench” dialog (available when you right click in Windows Explorer the folder name that contains the “.hg” subfolder) to sync the local changes with any external repository you’re using. ![]() Note that selecting the 3-state checkbox at the top selects/deselects all files quickly. The default seems to be to commit only modified files, thus if files have been removed or added you have to select them. After trying multiple times and even rebooting I realized that deleting that “wlock” file fixed the issue and could then open up TortoiseHg commit dialog again to retry the commit action (luckily it remembers the commit message from the last effort, you just have to select which files to commit again. This results in the Commit dialog never commiting changed/removed/added files and you have to press Close there and confirm cancelation of the commit action. It seems that sometimes TortoiseHg Mercurial (Hg) client on Windows fails to remove a 0-byte-sized file named “ wlock” (a write lock to avoid simultaneous write to a local repository) in the “.hg” subfolder that holds a local repository. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |