Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Linux Arm64 npm run init fails #14639

Closed
coreybruce opened this issue Mar 11, 2021 · 16 comments
Closed

Linux Arm64 npm run init fails #14639

coreybruce opened this issue Mar 11, 2021 · 16 comments
Assignees
Labels

Comments

@coreybruce
Copy link

Running npm run init fails and gives an error on Manjaro Arm64

npm run init

> brave@1.23.32 init
> node ./scripts/init.js

Performing initial checkout of brave-core
Cloning brave-core [undefined] into /home/corey/Stuff/brave-browser/src/brave...
-------------------------------------------------------------------------------
/home/corey/Stuff/brave-browser/src/brave
> git clone  .

fatal: repository 'undefined' does not exist

npm ERR! code 1
npm ERR! path /home/corey/Stuff/brave-browser
npm ERR! command failed
npm ERR! command sh -c node ./scripts/init.js

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/corey/.npm/_logs/2021-03-11T06_26_49_392Z-debug.log
[corey@manjaro-pi brave-browser]$ npm install

up to date, audited 29 packages in 8s

found 0 vulnerabilities
[corey@manjaro-pi brave-browser]$ npm run init

> brave@1.23.32 init
> node ./scripts/init.js

Performing initial checkout of brave-core
Cloning brave-core [undefined] into /home/corey/Stuff/brave-browser/src/brave...
node:internal/fs/utils:323
    throw err;
    ^

Error: EEXIST: file already exists, mkdir '/home/corey/Stuff/brave-browser/src/brave'
    at Object.mkdirSync (node:fs:1024:3)
    at Object.<anonymous> (/home/corey/Stuff/brave-browser/scripts/init.js:19:6)
    at Module._compile (node:internal/modules/cjs/loader:1092:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1121:10)
    at Module.load (node:internal/modules/cjs/loader:972:32)
    at Function.Module._load (node:internal/modules/cjs/loader:813:14)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:76:12)
    at node:internal/main/run_main_module:17:47 {
  errno: -17,
  syscall: 'mkdir',
  code: 'EEXIST',
  path: '/home/corey/Stuff/brave-browser/src/brave'
}
npm ERR! code 1
npm ERR! path /home/corey/Stuff/brave-browser
npm ERR! command failed
npm ERR! command sh -c node ./scripts/init.js

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/corey/.npm/_logs/2021-03-11T06_31_43_841Z-debug.log

Brave version (brave://version info)

Brave version: 1.23.32

@mihaiplesa
Copy link
Contributor

@coreybruce try with changes from this branch brave/brave-core#6927

@coreybruce
Copy link
Author

@mihaiplesa I will do some tests on my Raspberry pi 4

@coreybruce
Copy link
Author

@coreybruce try with changes from this branch brave/brave-core#6927

What is the branch called exactly sorry?

@mihaiplesa
Copy link
Contributor

@coreybruce mplesa-linux-arm64

@coreybruce
Copy link
Author

coreybruce commented Apr 4, 2021

Seems like the branch no longer exists, I checked on Braves branches and it says it doesn't exist and did git checkout and it said did not match any file(s) known to git it did weirdly work before on my original clone of the repo but I ran into a similar error when doing npm run init so I thought that maybe doing it on a fresh clone would be better but now the branch no longer exists

[corey@manjaro-pi Stuff]$ git clone https://github.com/brave/brave-browser
Cloning into 'brave-browser'...
remote: Enumerating objects: 242, done.
remote: Counting objects: 100% (242/242), done.
remote: Compressing objects: 100% (110/110), done.
remote: Total 35160 (delta 160), reused 207 (delta 132), pack-reused 34918
Receiving objects: 100% (35160/35160), 15.60 MiB | 4.04 MiB/s, done.
Resolving deltas: 100% (24303/24303), done.
[corey@manjaro-pi Stuff]$ cd brave-browser
[corey@manjaro-pi brave-browser]$ git checkout mplesa-linux-arm64
error: pathspec 'mplesa-linux-arm64' did not match any file(s) known to git
[corey@manjaro-pi brave-browser]$ git pull
Already up to date.
[corey@manjaro-pi brave-browser]$ git checkout mplesa-linux-arm64
error: pathspec 'mplesa-linux-arm64' did not match any file(s) known to git
[corey@manjaro-pi brave-browser]$ 

@mihaiplesa
Copy link
Contributor

Correct, the branch is in brave-core so you just have to pin it in https://github.com/brave/brave-browser/blob/master/package.json#L242

@coreybruce
Copy link
Author

How do I do that exactly?

@mihaiplesa
Copy link
Contributor

Just replace master with mplesa-linux-arm64.

@coreybruce
Copy link
Author

Ok thanks for letting me know, I'll get back to you with any feedback!

@coreybruce
Copy link
Author

Ok so I ran through the instructions again but ran into a issue after changing master to mplesa-linux-arm64v on package.json

[corey@manjaro-pi brave-browser]$ npm run init

> brave@1.25.23 init
> node ./scripts/init.js

Performing initial checkout of brave-core
Cloning brave-core [undefined] into /home/corey/Stuff/projects/brave-browser/src/brave...
-------------------------------------------------------------------------------
/home/corey/Stuff/projects/brave-browser/src/brave
> git clone  .

fatal: repository 'undefined' does not exist

@fmarier
Copy link
Member

fmarier commented Apr 21, 2021

@coreybruce You might be running into this problem: #13631 (i.e. using the wrong version of NPM)

@coreybruce
Copy link
Author

Ahh I see so it doesn't support the latest npm and needs the older version like 6.14.11 for example? will this also be fixed?

@mihaiplesa mihaiplesa self-assigned this Aug 16, 2021
@mihaiplesa
Copy link
Contributor

@coreybruce things should be in a better place now and we're also looking at upgrading to newer node and npm.

@coreybruce
Copy link
Author

@coreybruce things should be in a better place now and we're also looking at upgrading to newer node and npm.

Great news!

@bsclifton
Copy link
Member

Thanks for the report @coreybruce 😄 I'm de-duping reports of this issue and have it tracked with #19398 in case you wanted to subscribe 😄

@bsclifton bsclifton added the closed/duplicate Issue has already been reported label Nov 12, 2021
@coreybruce
Copy link
Author

Thanks for the report @coreybruce smile I'm de-duping reports of this issue and have it tracked with #19398 in case you wanted to subscribe smile

always glad to help out and thanks for the update! 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants