Open Bug 1503028 Opened 2 years ago Updated 10 months ago

Mach boostrap requires git, which isn't present in MozillaBuild

Categories

(Firefox Build System :: Bootstrap Configuration, defect)

x86_64
Windows 10
defect
Not set
normal

Tracking

(Not tracked)

People

(Reporter: TD-Linux, Unassigned)

References

Details

Attachments

(1 file)

Attached file mach bootstrap error
Following the instructions at the following URL doesn't work: https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Build_Instructions/Windows_Prerequisites

In particular, mach bootstrap now requires git, but no directions to install git are provided.
This is where the error happens:
  File "c:\users\mozilla\gecko-dev\python/mozversioncontrol\mozversioncontrol\__init__.py", line 460, in get_repository_object
    return GitRepository(path, git=git)

This is what the full corresponding code looks like:

    if os.path.isdir(os.path.join(path, '.hg')):
        return HgRepository(path, hg=hg)
    elif os.path.exists(os.path.join(path, '.git')):
        return GitRepository(path, git=git)
    else:
        raise InvalidRepoPath('Unknown VCS, or not a source checkout: %s' %
                              path)

IOW, it means there is no .hg directory in the directory you ran mach boostrap from, and there is a .git file or directory in it. Which under normal circumstances, would mean you have done a git clone, and thus, have git.
Ah yeah, I did this on a gecko-dev clone (because cloning mozilla-central was extremely slow on this machine).

I guess this can be a wontfix. It would be nice if start-shell.bat could pull in an existing git install automatically, though.

It would be nice if start-shell.bat could pull in an existing git install automatically, though.

See bug 1253212.

See Also: → 1253212

I hit this today also: I'm trying to set up moz-phab on a Windows machine; and it assumes git is in the system path and available to set up arcanist.

:tjr the moz-phab setup instructions are a known issue, see bug 1574008.

You need to log in before you can comment on or make changes to this bug.