Arch Linux User Repository

Hello everyone,

There was been several difficulties upgrading the Joplin due to major changes in the build system upstream.

I have finnally got version 2.6.10 working with pacthes, but remenber:

• You may need to remove your src/ folder before using this version

• The patches are still not perfect, you must say yes to a prompt

I will continue working on this later today, but its usable and stable, please remenber you can always report issues on the github repository.

Regards, Alfredo Palhares

Hello everyone,

I will be renaming the packages to its final form.

• joplin will contain the CLI application
• joplin-desktop will contain the Desktop version

Also, please for problems with the package, please open an issue on the Github repo, its really hard to provide support on the comments section, you can also email me.

If you have problems with the check() function, just run makepkg with the --nocheck flag.

Thank you for your patience. Regards, Alfredo Palhares

had the sync problem too... applied the temporary solutions of @cmach_socket and joplin 3.0.13 builds fine...

diff --git a/PKGBUILD b/PKGBUILD
index dd5c0a8..508c289 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -8,7 +8,7 @@

 pkgbase="joplin"
 pkgname=('joplin' 'joplin-desktop')
-pkgver=2.14.20
+pkgver=3.0.13
 groups=('joplin')
 pkgrel=1
 install="joplin.install"
@@ -24,7 +24,7 @@ source=("joplin.desktop" "joplin-desktop.sh" "joplin.sh"
 sha256sums=('c7c5d8b0ff9edb810ed901ea21352c9830bfa286f3c18b1292deca5b2f8febd2'
     'a450284fe66d89aa463d129ce8fff3a0a1a783a64209e4227ee47449d5737be8'
     'b6a8361cbc59e7dbc33bcc427274efb945d8d654bf013b12c7021be681f568e2'
-'919e9300e66bc6c24a282cbf93c43c228cdfe3227bdb1eaa50fdadef4734901b')
+'2bf91efec385801bb13b62b459e21c1eb80d35a772f517ba7d079eb91faa1f98')

 # local npm cache directory
 _yarn_cache="yarn-cache"
@@ -84,7 +84,7 @@ prepare() {
     # local lerna_json="${srcdir}/joplin-${pkgver}/lerna.json"

     msg2 "Deleting Unnecessary Packages"
-    rm -r "${srcdir}/joplin-${pkgver}/packages/app-mobile"
+    #rm -r "${srcdir}/joplin-${pkgver}/packages/app-mobile"
     rm -r "${srcdir}/joplin-${pkgver}/packages/app-clipper"
     rm -r "${srcdir}/joplin-${pkgver}/packages/server"
 }

@autape,

There is a temporary solution that you can edit the version of joplin in PKGBUILD and delete the line rm -r "${srcdir}/joplin-${pkgver}/packages/app-mobile"，which would fix an compile error.

The app now refuses to sync (one of the primary features for me): In order to synchronise, please upgrade your application to version 3.0.0+

Hello @masterkorp, I'm seconding @proledatarian's request for you to either fix/update the package, or accept the help offered by @cuihao (whose package built successfully).

the package doesn't build (canvas@npm:2.11.2 couldn't be built successfully (exit code 1...)), I opened an issue https://github.com/alfredopalhares/arch-pkgbuilds/issues/135 if anyone knows the solution, please post it here

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)