XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    A lot of not found and error 127 in yarn build

    Scheduled Pinned Locked Moved Solved Xen Orchestra
    17 Posts 5 Posters 2.4k Views 4 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • olivierlambertO Offline
      olivierlambert Vates 🪐 Co-Founder CEO
      last edited by

      And what about your Node version?

      B 1 Reply Last reply Reply Quote 0
      • B Offline
        bern @olivierlambert
        last edited by

        @olivierlambert
        node -v
        v19.2.0

        I don't know if it is related but in the output if yarn, there is a lot of :
        something "can't be found in the cache and will be fetched from the remote registry"

        1 Reply Last reply Reply Quote 0
        • olivierlambertO Offline
          olivierlambert Vates 🪐 Co-Founder CEO
          last edited by

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

          Please always use latest Node LTS.

          That should be a good start 🙂

          B 1 Reply Last reply Reply Quote 0
          • B Offline
            bern @olivierlambert
            last edited by

            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

            1 Reply Last reply Reply Quote 0
            • olivierlambertO Offline
              olivierlambert Vates 🪐 Co-Founder CEO
              last edited by

              Are you on the latest commit from master?

              B 1 Reply Last reply Reply Quote 0
              • B Offline
                bern @olivierlambert
                last edited by

                I ran the command from the documentation:

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

                julien-fJ 1 Reply Last reply Reply Quote 0
                • olivierlambertO Offline
                  olivierlambert Vates 🪐 Co-Founder CEO
                  last edited by

                  Does it ring any bell @julien-f ?

                  1 Reply Last reply Reply Quote 0
                  • julien-fJ Offline
                    julien-f Vates 🪐 Co-Founder XO Team @bern
                    last edited by

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

                    B 1 Reply Last reply Reply Quote 0
                    • B Offline
                      bern @julien-f
                      last edited by

                      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-fJ 1 Reply Last reply Reply Quote 0
                      • julien-fJ Offline
                        julien-f Vates 🪐 Co-Founder XO Team @bern
                        last edited by

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

                        I don't know where the issue comes from then 🤔

                        1 Reply Last reply Reply Quote 0
                        • B Offline
                          bern
                          last edited by

                          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. 😕

                          AnonabharA julien-fJ 2 Replies Last reply Reply Quote 0
                          • AnonabharA Offline
                            Anonabhar @bern
                            last edited by

                            @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 -
                            
                            1 Reply Last reply Reply Quote 0
                            • julien-fJ Offline
                              julien-f Vates 🪐 Co-Founder XO Team @bern
                              last edited by

                              @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.

                              B 1 Reply Last reply Reply Quote 1
                              • B Offline
                                bern @julien-f
                                last edited by

                                @julien-f It works!!!

                                No more error in the yarn build output.

                                Thanks a lot!

                                1 Reply Last reply Reply Quote 1
                                • olivierlambertO olivierlambert marked this topic as a question on
                                • olivierlambertO olivierlambert has marked this topic as solved on
                                • First post
                                  Last post