@maverick Hi Maverick,
I just tried a test build prep and it seems to work for me. I created a new user, xo_test and swapped to it, then:
xo_test@xo2:~$ mkdir build
xo_test@xo2:~$ cd build/
xo_test@xo2:~/build$ git clone https://github.com/sagemathinc/fuse-native
Cloning into 'fuse-native'...
remote: Enumerating objects: 409, done.
remote: Counting objects: 100% (409/409), done.
remote: Compressing objects: 100% (160/160), done.
remote: Total 409 (delta 259), reused 396 (delta 246), pack-reused 0
Receiving objects: 100% (409/409), 150.36 KiB | 2.64 MiB/s, done.
Resolving deltas: 100% (259/259), done.
xo_test@xo2:~/build$ git clone https://github.com/vatesfr/xen-orchestra.git
Cloning into 'xen-orchestra'...
remote: Enumerating objects: 119983, done.
remote: Counting objects: 100% (3095/3095), done.
remote: Compressing objects: 100% (1400/1400), done.
remote: Total 119983 (delta 2143), reused 2278 (delta 1654), pack-reused 116888
Receiving objects: 100% (119983/119983), 64.38 MiB | 9.78 MiB/s, done.
Resolving deltas: 100% (86309/86309), done.
xo_test@xo2:~/build$ cp -a fuse-native fuse-native.orig
xo_test@xo2:~/build/fuse-native$ nano -w fuse-native/package.json
xo_test@xo2:~/build$ diff -u fuse-native.orig fuse-native
Common subdirectories: fuse-native.orig/.git and fuse-native/.git
diff -u fuse-native.orig/package.json fuse-native/package.json
--- fuse-native.orig/package.json 2023-10-23 14:25:18.067638984 +0100
+++ fuse-native/package.json 2023-10-23 14:29:19.703990676 +0100
@@ -1,6 +1,6 @@
{
- "name": "@cocalc/fuse-native",
- "version": "2.4.0",
+ "name": "fuse-native",
+ "version": "2.2.6",
"description": "Node.js bindings for the FUSE api (Filesystem in Userspace)",
"main": "index.js",
"bin": {
@@ -28,7 +28,7 @@
},
"repository": {
"type": "git",
- "url": "https://github.com/sagemathinc/fuse-native.git"
+ "url": "https://github.com/fuse-friends/fuse-native.git"
},
"author": {
"name": "William Stein (SageMath, Inc.)",
@@ -44,7 +44,7 @@
"author": " ()",
"license": "MIT",
"bugs": {
- "url": "https://github.com/sagemathinc/fuse-native/issues"
+ "url": "https://github.com/fuse-friends/fuse-native/issues"
},
- "homepage": "https://github.com/sagemathinc/fuse-native"
+ "homepage": "https://github.com/fuse-friends/fuse-native"
}
Common subdirectories: fuse-native.orig/test and fuse-native/test
xo_test@xo2:~/build$ cp -a fuse-native xen-orchestra
xo_test@xo2:~/build$ cd xen-orchestra/
xo_test@xo2:~/build/xen-orchestra$ cd fuse-native/
xo_test@xo2:~/build/xen-orchestra/fuse-native$ yarn link
yarn link v1.22.19
success Registered "fuse-native".
info You can now run `yarn link "fuse-native"` in the projects where you want to use this package and it will be used instead.
Done in 0.15s.
xo_test@xo2:~/build/xen-orchestra/fuse-native$ cd ..
xo_test@xo2:~/build/xen-orchestra$ yarn link fuse-native
yarn link v1.22.19
success Using linked package for "fuse-native".
Done in 0.13s.
xo_test@xo2:~/build/xen-orchestra$ yarn
yarn install v1.22.19
[1/5] Validating package.json...
[2/5] Resolving packages...
[3/5] Fetching packages...
warning url-loader@1.1.2: Invalid bin field for "url-loader".
[4/5] Linking dependencies...
warning "workspace-aggregator-6dab12fa-fabf-4759-8627-2058ff251bdf > @vates/node-vsphere-soap > soap@1.0.0" has incorrect peer dependency "axios@^0.27.2".
warning Workspaces can only be enabled in private projects.
[5/5] Building fresh packages...
$ husky install
husky - Git hooks installed
Done in 425.65s.
I haven't kicked off the yarn build, but it was the yarn stage that failed for you.
Does the above help? [ As I said back in August, manually editing the package.json for sagemathinc's fuse-native to match the fuse-friends one that is called out in the xen-orchestra git tree is a completely horrible hack, but it does seem to work for me. ]
xo_test@xo2:~/build$ cat /etc/debian_version
12.2
Cheers,
Mark
EDIT 24/Oct/2023: The build needs node-gyp and node-gyp-build packages installing with npm, and the fuse libraries and devel packages and pkg-config for the operating system, along with the pre-reqs noted in the XO from the Sources build instructions in the wiki. The build host needs a decent amount of RAM - it built for me in 3GB but failed with 1GB. Once built, it runs fine for me with 1GB.