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

Closed
Open
Created Jul 10, 2013 by Bitbucket Importer@bitbucket_importerOwner

AttributeError: 'bundlerepository' object has no attribute 'capable'

Created originally on Bitbucket by Gili

I invoked the following command-line:

"hg transplant -s http://myrepo.com/hg/myproject"

and hit "y" to transplant a changeset. The following exception was thrown:

#!python

** Unknown exception encountered with possibly-broken third-party extension mercurial_keyring
** which supports versions unknown of Mercurial.
** Please disable mercurial_keyring and try your action again.
** If that fixes the bug please report it to the extension author.
** Python 2.7.3 (default, Apr 10 2012, 23:24:47) [MSC v.1500 64 bit (AMD64)]
** Mercurial Distributed SCM (version 2.6.2)
** Extensions loaded: mercurial_keyring, convert, rebase, transplant, mq, histed
it, purge
Traceback (most recent call last):
  File "hg", line 42, in <module>
  File "mercurial\dispatch.pyo", line 28, in run
  File "mercurial\dispatch.pyo", line 69, in dispatch
  File "mercurial\dispatch.pyo", line 97, in _runcatch
  File "mercurial\dispatch.pyo", line 778, in _dispatch
  File "mercurial\dispatch.pyo", line 549, in runcommand
  File "mercurial\dispatch.pyo", line 869, in _runcommand
  File "mercurial\dispatch.pyo", line 840, in checkargs
  File "mercurial\dispatch.pyo", line 775, in <lambda>
  File "mercurial\util.pyo", line 506, in check
  File "mercurial\extensions.pyo", line 143, in wrap
  File "mercurial\util.pyo", line 506, in check
  File "hgext\mq.pyo", line 3528, in mqcommand
  File "mercurial\util.pyo", line 506, in check
  File "hgext\transplant.pyo", line 662, in transplant
  File "hgext\transplant.pyo", line 157, in apply
  File "mercurial\localrepo.pyo", line 1662, in pull
  File "mercurial\discovery.pyo", line 32, in findcommonincoming
AttributeError: 'bundlerepository' object has no attribute 'capable'

This extension ships as part of TortoiseHg so I have no way of disabling it. Does the bug lie with mercurial_keyring, TortoiseHg, or Mercurial?

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