Closed
Bug 970233
Opened 12 years ago
Closed 12 years ago
mach mercurial-setup fails on bzexport
Categories
(Firefox Build System :: Mach Core, enhancement)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: daniel, Unassigned)
References
Details
Attachments
(1 file, 1 obsolete file)
|
3.25 KB,
text/plain
|
Details |
I have a few days old mozilla-central checkout on windows. Today I decided to run 'mach mercurial-setup' to make sure it was setup properly.
After invokation, I can no longer update with "hg pull" and as it then asks me to run mercurial-setup again to rectify, I did and it fails. See trace from my command windows.
Comment 1•12 years ago
|
||
I guess this is what happens when we make the old extension fatal instead of merely printing a warning.
Workaround: delete the reference to bzexport from your hgrc and re-run `mach mercurial-setup`.
I am curious how you entered this state. `mach mercurial-setup` should have switched bzexport to its new repo. It should never have pulled the bzexport revision that is causing it to abort immediately. Did you manually pull and update the bzexport repo?
Depends on: 968259
Flags: needinfo?(daniel)
I didn't have any bzexport anywhere to start with, I had just been doing hg pull manually when I figured I should make sure my hg setup was correct. I hadn't done any hg configs prior to that, only cloned and done pulls.
I removed bzexport from hgrc and I could use hg again. I'll try to rerun mercurial-setup and see what happens!
Updated•12 years ago
|
Comment 3•12 years ago
|
||
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Comment 4•12 years ago
|
||
Updated•12 years ago
|
Assignee: nobody → mcote
Comment 5•12 years ago
|
||
Comment on attachment 8420534 [details] [diff] [review]
Make redirect non-fatal
Wow bzexport did not do what I expected...
Attachment #8420534 -
Attachment is obsolete: true
Updated•12 years ago
|
Assignee: mcote → nobody
Updated•8 years ago
|
Product: Core → Firefox Build System
You need to log in
before you can comment on or make changes to this bug.
Description
•