Closed Bug 1753259 Opened 3 years ago Closed 3 years ago

Interacting with HG fails after upgrading from MozillaBuild 3.4 to 4.0

Categories

(Firefox Build System :: Mach Core, defect)

defect

Tracking

(firefox98 fixed)

RESOLVED FIXED
98 Branch
Tracking Status
firefox98 --- fixed

People

(Reporter: mhentges, Assigned: mhentges)

References

Details

Attachments

(1 file)

This is because the path to hg is stored during configure, but the path changes with the new MozillaBuild release because we're now using hg with Python 3, not Python 2. So, %MOZILLABUILD%\python\Scripts\hg => %MOZILLABUILD%\python3\Scripts\hg.

The solution here is likely to attempt to use the "stored" hg path, but re-attempt to find a new hg if the stored path is incorrect.

Blocks: 1739443

Though not a panacea, this patch addresses existing usages of
get_repository_from_build_config() to fall back to
get_repository_object() if MissingVCSTool was encountered.

Ideally, we'd update substs["HG"] when we detect that it's changed,
but we don't have infrastructure to incrementally change configure
output.

So, other issues may creep up that will warrant a fresh
./mach configure.

Assignee: nobody → mhentges
Status: NEW → ASSIGNED
Pushed by mhentges@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/7d725eef2bc3 Try finding VCS tool if build config is outdated r=ahal
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → 98 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: