Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • M mercurial_keyring
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 6
    • Issues 6
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • mercurial
  • mercurial_keyring
  • Issues
  • #11

Closed
Open
Created Oct 11, 2011 by Bitbucket Importer@bitbucket_importerOwner

keyring has stopped working with subrepos

Created originally on Bitbucket by jschenck (Jeff Schenck)

With mercurial 1.9.x, the keyring extension no longer works with repos containing subrepos. Normal operation (i.e, a single repo) is fine. When using suprepos, I'm prompted for my password once for each subrepo.

1.8.3 works well. I'm sticking there for now. I'm using the latest version of mercurial keyring (0.4.6), on a Linux (CentOS) box. Thanks for your help.

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