Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • M mercurial_keyring
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 7
    • Issues 7
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
    • Model experiments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • mercurialmercurial
  • mercurial_keyring
  • Issues
  • #44
Closed
Open
Issue created Jan 09, 2015 by Bitbucket Importer@bitbucket_importerOwner

isenabled() breaks keyring for older mercurial versions

Created originally on Bitbucket by eraserix (Christoph Mathys)

After updating to 0.6.3 on Ubuntu 14.04 (current LTS) I get the following error when firing up hg:

$ hg out
*** failed to import extension mercurial_keyring from mercurial_keyring.py: 'module' object has no attribute 'isenabled'

14.04 ships with mercurial 2.8.2. The function isenabled() however was not part of mercurial until 2.9.1.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking