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
  • #21

Closed
Open
Created Nov 01, 2012 by Bitbucket Importer@bitbucket_importerOwner

extension throws exception when doing "hg pull" over ssh

Created originally on Bitbucket by Anonymous

When I use mercurial extension on my machine and do "hg pull" from a password protected repository, things are great.

However, if I "ssh" into the machine and do an "hg pull" I get the exception in the attachment. I use gnome-shell (Fedora 17) and gnome-keyring, so perhaps the keyring isn't accessible from an ssh session, but at least the extension should fall back to the normal password prompt.

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