Bootstrap script fails with vcs git
Categories
(Firefox Build System :: Bootstrap Configuration, defect)
Tracking
(firefox106 affected)
Tracking | Status | |
---|---|---|
firefox106 | --- | affected |
People
(Reporter: mark, Assigned: tcampbell)
Details
Attachments
(2 files)
I've set up a new environment for building on Windows 11. Followed the documentation instructions on the source docs site.
- I installed VS2022, and the latest SDK for Windows 11
- I installed Mozillabuild-latest
- I installed Git for Windows (2.37)
- I grabbed the latest bootstrap.py script as instructed on the source site
- I attempted to perform a bootstrap using git as cvs, as documented
python3 bootstrap.py --vcs=git
The following error was thrown and I could not clone:
$ python3 bootstrap.py --vcs=git
Cloning into mozilla-unified using Git...
Destination directory for clone (leave empty to use default destination of mozilla-unified):
Attempting to add exclusion path to Microsoft Defender Antivirus for: C:\source\mozilla-unified
Attempting to add exclusion path to Microsoft Defender Antivirus for: C:\mozilla-build\
Attempting to add exclusion path to Microsoft Defender Antivirus for: C:\Users\mcwer\.mozbuild
Cloning Firefox Git repository to mozilla-unified
Could not bootstrap Firefox! Consider filing a bug.
Traceback (most recent call last):
File "C:\source\bootstrap.py", line 432, in <module>
sys.exit(main(sys.argv))
File "C:\source\bootstrap.py", line 399, in main
srcdir = clone(options)
File "C:\source\bootstrap.py", line 345, in clone
return git_clone_firefox(binary, dest, watchman)
File "C:\source\bootstrap.py", line 187, in git_clone_firefox
st = os.stat(cinnabar)
FileNotFoundError: [WinError 2] The system cannot find the file specified: 'C:\\Users\\mcwer\\AppData\\Local\\Temp\\tmpbslh20lb\\git-cinnabar-master\\git-cinnabar'
Assignee | ||
Comment 1•3 years ago
|
||
I hit the same problem. The contents of the git-cinnabar repo changed slightly. As well the git-cinnabar download.py
script checks git revisions, so this probably needs to just do a git depth=1 clone instead of using the github archive link.
Assignee | ||
Comment 2•3 years ago
|
||
The upstream git-cinnabar repo no longer has the git-cinnabar
scripts which
breaks the logic in mozboot. We no longer need to worry about making those files
executable and can simply use the download.py script to do the work. For the
current versions of download.py to work correctly, we need the git metadata to
exist, so use a --depth=1 clone instead.
Updated•3 years ago
|
Reporter | ||
Comment 4•3 years ago
|
||
Thanks for the quick fix :)
So, eh, do i have to patch this myself or how will this deployed? Can I just grab the new script somewhere?
Assignee | ||
Comment 5•3 years ago
|
||
The URL pointed to in the build instructions will automatically get the update in a couple hours. If you want something immediately, you can use https://hg.mozilla.org/integration/autoland/raw-file/default/python/mozboot/bin/bootstrap.py
(This is similar to the other url but from the integration branch, while the link in the docs is for nightly which will merge twice a day).
Comment 6•3 years ago
|
||
bugherder |
Reporter | ||
Comment 7•3 years ago
|
||
(In reply to Ted Campbell [:tcampbell] from comment #5)
The URL pointed to in the build instructions will automatically get the update in a couple hours. If you want something immediately, you can use https://hg.mozilla.org/integration/autoland/raw-file/default/python/mozboot/bin/bootstrap.py
(This is similar to the other url but from the integration branch, while the link in the docs is for nightly which will merge twice a day).
Thanks, I appreciate the instructions -- obviously not that much in a hurry for this, I was just wondering how and how fast the rollout would be for infra scripts like this :)
Reporter | ||
Comment 8•3 years ago
|
||
Unfortunately this didn't resolve the issue.
Seems the problem now is that cinnabar can't install because of a certificate issue?
Failure log attached.
Reporter | ||
Updated•3 years ago
|
Updated•3 years ago
|
Comment 9•3 years ago
|
||
That's a completely separate issue. Please file a new bug.
Reporter | ||
Comment 10•3 years ago
|
||
All right. Filed bug 1787370 for the follow-up
Description
•