Arch Linux User Repository

Thank you dosenpils and masterkorp for supporting the package.

I replaced the PKGBUILD with the version I wrote for the archlinuxcn repo. I will do my best to follow the latest nodejs and electron versions.

Please try to build in a clean chroot (i.e., with extra-x86_64-build from devtools package) if you have problems building the package.

For canvas issue:

UPD: I've tested the most recent Joplin version 2.14.21. Seems it has no build issues. No any extra patches needed. You just have to wait until it's tagged as 'Latest' and push updated PKGBUILD to AUR.

All below is related to version 2.14.20

https://github.com/Automattic/node-canvas/issues/2377#issuecomment-2085815152

Here the patch: https://github.com/trap000d/aur/blob/master/joplin-electron/0006-update-canvas-version.patch

With it yarn still complains for canvas@npm:2.11.2 (I have no idea where comes from, probably as other module dependency from yarn.lock). But then package builds and joplin runs. On the other hand, if I remove yarn.lock, then other errors come - with codemirror.

After all attempts to resolve dependencies I assume currently all is broken. The only way to correctly build the package is to downgrade node.

I get similar build errors:

➤ YN0009: │ canvas@npm:2.11.2 couldn't be built successfully (exit code 1, logs can be found here: /tmp/xfs-e3a2e8bc/build.log)
➤ YN0009: │ canvas@npm:2.11.2 couldn't be built successfully (exit code 1, logs can be found here: /tmp/xfs-96eb9712/build.log)
➤ YN0009: │ canvas@npm:2.11.2 couldn't be built successfully (exit code 1, logs can be found here: /tmp/xfs-2e34fcb7/build.log)

Looking in one of the log files, I see:

(node:394386) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
node-pre-gyp http GET https://github.com/Automattic/node-canvas/releases/download/v2.11.2/canvas-v2.11.2-node-v127-linux-glibc-x64.tar.gz
node-pre-gyp ERR! install response status 404 Not Found on https://github.com/Automattic/node-canvas/releases/download/v2.11.2/canvas-v2.11.2-node-v127-linux-glibc-x64.tar.gz 
node-pre-gyp WARN Pre-built binaries not installable for canvas@2.11.2 and node@22.0.0 (node-v127 ABI, glibc) (falling back to source compile with node-gyp) 
node-pre-gyp WARN Hit error response status 404 Not Found on https://github.com/Automattic/node-canvas/releases/download/v2.11.2/canvas-v2.11.2-node-v127-linux-glibc-x64.tar.gz 

It appears that a build script is trying to pull a build version of canvas that does not exist (v127). The latest on the git is v120.

No longer builds since last update:

➤ YN0007: │ husky@patch:husky@npm%3A3.1.0#./.yarn/patches/husky-npm-3.1.0-5cc13e4e34.patch::version=3.1.0&hash=d9603f&locator=root%40workspace%3A. must be built because it never has been before or the last one failed
➤ YN0007: │ keytar@npm:7.9.0 must be built because it never has been before or the last one failed
➤ YN0007: │ sharp@npm:0.33.2 must be built because it never has been before or the last one failed
➤ YN0007: │ sqlite3@npm:5.1.6 [ea905] must be built because it never has been before or the last one failed
➤ YN0007: │ canvas@npm:2.11.2 must be built because it never has been before or the last one failed
➤ YN0007: │ tesseract.js@npm:5.0.4 must be built because it never has been before or the last one failed
➤ YN0007: │ core-js@npm:3.33.1 must be built because it never has been before or the last one failed
➤ YN0007: │ core-js-pure@npm:3.33.1 must be built because it never has been before or the last one failed
➤ YN0007: │ @fortawesome/fontawesome-free@npm:5.15.4 must be built because it never has been before or the last one failed
➤ YN0007: │ electron@npm:26.5.0 must be built because it never has been before or the last one failed
➤ YN0007: │ @fortawesome/fontawesome-common-types@npm:0.2.36 must be built because it never has been before or the last one failed
➤ YN0007: │ @fortawesome/fontawesome-common-types@npm:6.4.2 must be built because it never has been before or the last one failed
➤ YN0007: │ @fortawesome/fontawesome-common-types@npm:6.1.2 must be built because it never has been before or the last one failed
➤ YN0007: │ root@workspace:. must be built because it never has been before or the last one failed
➤ YN0007: │ @fortawesome/fontawesome-svg-core@npm:1.2.36 must be built because it never has been before or the last one failed
➤ YN0007: │ @fortawesome/free-regular-svg-icons@npm:5.15.4 must be built because it never has been before or the last one failed
➤ YN0007: │ @fortawesome/free-solid-svg-icons@npm:5.15.4 must be built because it never has been before or the last one failed
➤ YN0007: │ @fortawesome/fontawesome-svg-core@npm:6.4.2 must be built because it never has been before or the last one failed
➤ YN0007: │ @fortawesome/free-brands-svg-icons@npm:6.4.2 must be built because it never has been before or the last one failed
➤ YN0007: │ @fortawesome/free-regular-svg-icons@npm:6.4.2 must be built because it never has been before or the last one failed
➤ YN0007: │ @fortawesome/free-solid-svg-icons@npm:6.4.2 must be built because it never has been before or the last one failed
➤ YN0007: │ @fortawesome/fontawesome-svg-core@npm:6.1.2 must be built because it never has been before or the last one failed
➤ YN0007: │ @fortawesome/free-solid-svg-icons@npm:6.1.2 must be built because it never has been before or the last one failed
➤ YN0009: │ root@workspace:. couldn't be built successfully (exit code 1, logs can be found here: /tmp/xfs-d9e20c07/build.log)
➤ YN0000: └ Completed in 42s 582ms
➤ YN0000: Failed with errors in 44s 593ms
==> ERROR: A failure occurred in build().

Sorry to bother everyone, I'm encountering this error during the build and have no idea how to proceed.

➤ YN0000: [@joplin/app-desktop]: Process exited (exit code 1), completed in 16s 783ms
➤ YN0000: The command failed for workspaces that are depended upon by other workspaces; can't satisfy the dependency graph
➤ YN0000: Failed with errors in 35s 928ms
at makeError (/home/tom/.cache/yay/joplin/src/joplin-2.14.20/node_modules/execa/lib/error.js:60:11)
at handlePromise (/home/tom/.cache/yay/joplin/src/joplin-2.14.20/node_modules/execa/index.js:118:26)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at async execCommand (/home/tom/.cache/yay/joplin/src/joplin-2.14.20/gulpfile.js:27:17)
at async fn (/home/tom/.cache/yay/joplin/src/joplin-2.14.20/gulpfile.js:64:5)

Hello @masterkorp

I also have the same issue regarding GPG private key access.

It looks like the build is trying to sign a commit (my gitconfig turns on Git commit signing) :

➤ YN0000: [@joplin/app-desktop]: > git clone -- https://github.com/JackGruber/joplin-plugin-backup.git /home/###/aur/joplin/src/joplin-2.14.20/packages/default-plugins/plugin-sources/io.github.jackgruber.backup
➤ YN0000: [@joplin/app-desktop]: Cloning into '/home/###/aur/joplin/src/joplin-2.14.20/packages/default-plugins/plugin-sources/io.github.jackgruber.backup'...
➤ YN0000: [@joplin/app-desktop]:  Switching to commit 2d814a5466604daced108331d14aedf8e8414d62
➤ YN0000: [@joplin/app-desktop]: > git switch master
➤ YN0000: [@joplin/app-desktop]: Already on 'master'
➤ YN0000: [@joplin/app-desktop]: Your branch is up to date with 'origin/master'.
➤ YN0000: [@joplin/app-desktop]: > git checkout 2d814a5466604daced108331d14aedf8e8414d62
➤ YN0000: [@joplin/app-desktop]: Note: switching to '2d814a5466604daced108331d14aedf8e8414d62'.
➤ YN0000: [@joplin/app-desktop]:
➤ YN0000: [@joplin/app-desktop]: You are in 'detached HEAD' state. You can look around, make experimental
➤ YN0000: [@joplin/app-desktop]: changes and commit them, and you can discard any commits you make in this
➤ YN0000: [@joplin/app-desktop]: state without impacting any branches by switching back to a branch.
➤ YN0000: [@joplin/app-desktop]:
➤ YN0000: [@joplin/app-desktop]: If you want to create a new branch to retain commits you create, you may
➤ YN0000: [@joplin/app-desktop]: do so (now or later) by using -c with the switch command. Example:
➤ YN0000: [@joplin/app-desktop]:
➤ YN0000: [@joplin/app-desktop]:   git switch -c <new-branch-name>
➤ YN0000: [@joplin/app-desktop]:
➤ YN0000: [@joplin/app-desktop]: Or undo this operation with:
➤ YN0000: [@joplin/app-desktop]:
➤ YN0000: [@joplin/app-desktop]:   git switch -
➤ YN0000: [@joplin/app-desktop]:
➤ YN0000: [@joplin/app-desktop]: Turn off this advice by setting config variable advice.detachedHead to false
➤ YN0000: [@joplin/app-desktop]:
➤ YN0000: [@joplin/app-desktop]: HEAD is now at 2d814a5 Remove wrong section
➤ YN0000: [@joplin/app-desktop]: > git rev-parse --verify HEAD^{commit}
➤ YN0000: [@joplin/app-desktop]: 2d814a5466604daced108331d14aedf8e8414d62
➤ YN0000: [@joplin/app-desktop]:  Copying repository files...
➤ YN0000: [@joplin/app-desktop]:  Initializing repository.
➤ YN0000: [@joplin/app-desktop]: > git init . -b main
➤ YN0000: [@joplin/app-desktop]: Initialized empty Git repository in /tmp/default-plugin-buildqUQ6kM/.git/
➤ YN0000: [@joplin/app-desktop]:  Creating initial commit.
➤ YN0000: [@joplin/app-desktop]: > git add .
➤ YN0000: [@joplin/app-desktop]: > git config user.name "Build script"
➤ YN0000: [@joplin/app-desktop]: > git config user.email
➤ YN0000: [@joplin/app-desktop]: > git commit -m "Initial commit"
➤ YN0000: [@joplin/app-desktop]: error: Signing file /tmp/.git_signing_buffer_tmpS3jv5V
➤ YN0000: [@joplin/app-desktop]: Couldn't sign message (signer): agent refused operation?
➤ YN0000: [@joplin/app-desktop]: Signing /tmp/.git_signing_buffer_tmpS3jv5V failed: agent refused operation?
➤ YN0000: [@joplin/app-desktop]:
➤ YN0000: [@joplin/app-desktop]: fatal: failed to write commit object

hello @iyanmv build() does not access your keys in any way? Can you please explain more how is that accessing your system ?

Why does build() need to access my gpg private key?

Hello,

I went on this thread and tried to remove cache, then reinstalled the npm package. It worked for me.

Getting this build error.

error This project's package.json defines "packageManager": "yarn@3.3.1". However the current global version of Yarn is 1.22.22.

Presence of the "packageManager" field indicates that the project is meant to be used with Corepack, a tool included by default with all official Node.js distributions starting from 16.9 and 14.19.
Corepack must currently be enabled by running corepack enable in your terminal. For more information, check out https://yarnpkg.com/corepack

Please either update the package or accept the help offered by @cuihao.