A lot of not found and error 127 in yarn build

olivierlambert

Have you carefully read our documentation? There's a sentence in bold:

Please always use latest Node LTS.

That should be a good start

bern

I started from scratch with
node -v
v18.12.1

which is the latest LTS according to https://nodejs.org/en/

And I have the same errors.

I am on the same OS as the documentation:
lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 11 (bullseye)
Release: 11
Codename: bullseye

olivierlambert

Are you on the latest commit from master?

bern

I ran the command from the documentation:

git clone -b master https://github.com/vatesfr/xen-orchestra

olivierlambert

Does it ring any bell @julien-f ?

julien-f

@bern Don't forget the initial yarn to install the dependencies.

bern

Here are the commands from my history:

116 git clone -b master https://github.com/vatesfr/xen-orchestra
. . .
119 cd xen-orchestra/
. . .
121 yarn
122 yarn build

julien-f

@bern My bad, I missed your previous message on this

I don't know where the issue comes from then

bern

I reverted to a snapshot of a freshly installed Debian 11 and then I ran the following commands:

apt-get install build-essential redis-server libpng-dev git python3-minimal libvhdi-utils lvm2 cifs-utils

apt-get update

curl -fsSL https://deb.nodesource.com/setup_18.x | bash - && apt-get install -y nodejs

root@orchestrator:~# node -v
v18.12.1

root@orchestrator:~# which yarn
root@orchestrator:~# corepack enable
root@orchestrator:~# corepack prepare yarn@stable --activate
Preparing yarn@stable for immediate activation...
root@orchestrator:~# which yarn
/usr/bin/yarn
root@orchestrator:/opt/xen-orchestra# yarn -v
3.3.0

git clone -b master https://github.com/vatesfr/xen-orchestra

yarn

yarn build

It looks like I am out of luck on this.

Anonabhar

@bern I just built mine on Dev 11 a few days ago...

Make sure sudo is installed and do:

curl -fsSL https://deb.nodesource.com/setup_lts.x | sudo -E bash -

julien-f

@bern I believe the issue is that you are using Yarn 3 but XO is using Yarn 1 (classic).

I've made a change that should help with this, please fetch latest XO commit and try again yarn.

bern

@julien-f It works!!!

No more error in the yarn build output.

Thanks a lot!