Closed Bug 1542266 Opened 7 years ago Closed 6 years ago

Bootstrap fails to install evolve when it's already present in hgrc but not cloned

Categories

(Firefox Build System :: Bootstrap Configuration, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: bbouvier, Assigned: jwatt)

Details

Attachments

(1 file)

During the Mercurial wizard happening during mach bootstrap, the installation of evolve seems to fail with an unhelpful error message:

This wizard will guide you through configuring Mercurial for an optimal
experience contributing to Mozilla projects.

The wizard makes no changes without your permission.

To begin, press the enter/return key.


It looks like the setup wizard has already installed a copy of the
evolve extension on your machine, at /home/ben/.mozbuild/evolve.

(Relevant config option: extensions.evolve)

Would you like to update evolve to the latest version?  (Yn) 
abort: repository /home/ben/.mozbuild/evolve not found!

Is there anything I should do as a user to have evolve install correctly?

So I understood what's happening: there's a line in my global .hgrc file that indicates that I've got evolve installed in some directory. This is the case even though the directory it points to doesn't exist, because I synchronize my configuration files between my different machines, and this is a new machine.

So I see two possible courses of action here:

  • indicate that evolve is marked as being installed in the hgrc, but the directory it points to doesn't exist.
  • notice that the directory doesn't exist and just do an actual clone instead of an update

I'd prefer the second solution because it doesn't need any manual step. In the meanwhile, just removing the evolve = line from my hgrc had the bootstrap process install evolve as expected.

Summary: Bootstrap fails to install evolve → Bootstrap fails to install evolve when it's already present in hgrc but not cloned

This avoids us silently failing to install evolve on bootstraping in the case
that the user's config file specifies the path that we manage, but that
directory is missing (for example, if their config file is reused on a different
machine).

Assignee: nobody → jwatt

Pushed by bjones@mozilla.com:
https://hg.mozilla.org/hgcustom/version-control-tools/rev/4642efefaeb4
configwizard: check out evolve when we manage it but it's absent r=glob

Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: