Closed
Bug 1459924
Opened 7 years ago
Closed 7 years ago
failed to set up extension qimportbz: cannot import name Abort
Categories
(Developer Services :: Mercurial: mozext, defect)
Developer Services
Mercurial: mozext
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: RyanVM, Assigned: Callek)
References
Details
Attachments
(1 file, 1 obsolete file)
Traceback (most recent call last):
File "c:\mozilla-build\python\lib\site-packages\mercurial\extensions.py", line 215, in _runextsetup
extsetup(ui)
File "c:/Users/Ryan/.mozbuild/version-control-tools/hgext\qimportbz\__init__.py", line 212, in extsetup
'bz': bzhandler.Handler,
File "c:\mozilla-build\python\lib\site-packages\hgdemandimport\demandimportpy2.py", line 145, in __getattr__
self._load()
File "c:\mozilla-build\python\lib\site-packages\hgdemandimport\demandimportpy2.py", line 90, in _load
mod = _hgextimport(_origimport, head, globals, locals, None, level)
File "c:\mozilla-build\python\lib\site-packages\hgdemandimport\demandimportpy2.py", line 41, in _hgextimport
return importfunc(name, globals, *args, **kwargs)
File "c:/Users/Ryan/.mozbuild/version-control-tools/hgext\qimportbz\bzhandler.py", line 10, in <module>
from mercurial.util import Abort
ImportError: cannot import name Abort
*** failed to set up extension qimportbz: cannot import name Abort
Comment 1•7 years ago
|
||
Comment 2•7 years ago
|
||
Updated•7 years ago
|
Attachment #8974422 -
Attachment is obsolete: true
Assignee | ||
Updated•7 years ago
|
Assignee: nobody → bugspam.Callek
Comment 3•7 years ago
|
||
Comment on attachment 8974427 [details]
Bug 1459924 - failed to set up extension qimportbz: cannot import name Abort. r=gps
Gregory Szorc [:gps] has approved the revision.
https://phabricator.services.mozilla.com/D1249
Attachment #8974427 -
Flags: review+
Pushed by gszorc@mozilla.com:
https://hg.mozilla.org/hgcustom/version-control-tools/rev/6dd442f29a57
failed to set up extension qimportbz: cannot import name Abort. r=gps
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•