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

If you want to use the fcitx input method under wayland, please complete the following configuration:

cat .config/electron25-flags.conf 
--enable-wayland-ime
--ozone-platform=wayland

Updated to 3.7.21. I looked into some old issues:

• "Open secondary app instance" should work now. The root cause was Joplin's own CLI flag building and parsing logics are not compatible with the wrapper script this package shipped.
• Backup plugin also appears to work on my end? I didn't fix anything though.

@cjc7373 Thanks! Updated.

@cuihao The StartupWMClass in desktop file has been changed to appimagekit-joplin. Check https://github.com/laurent22/joplin/pull/16547

Warning: the @joplin/app-desktop tests that are executed as part of the build process are very memory hungry. Make sure you have around 48 GB of memory (including swap) available to prevent the OOMKiller from kicking in.

@cjc7373 Thanks! Updated.

Hi @cuihao, I'm testing 3.7 build on arm64. I noticed two errors. First is the dist path that's different on arm64, see the following diff:

@@ -120,7 +128,11 @@ package_joplin-desktop() {

     cd "${srcdir}/joplin-${pkgver}/packages/app-desktop"
     mkdir -p "${pkgdir}/usr/lib"
-    cp -vr dist/linux-unpacked/resources "${pkgdir}/usr/lib/${pkgname}"
+    if [[ $CARCH == aarch64 ]]; then
+        cp -vr dist/linux-arm64-unpacked/resources "${pkgdir}/usr/lib/${pkgname}"
+    else
+        cp -vr dist/linux-unpacked/resources "${pkgdir}/usr/lib/${pkgname}"
+    fi

     # Install icons
     while read -r size; do

The other is not related to arm64, it's something in cli-integration-tests which is importing a wrong module path. I patched it with something like

sed -i \
        's#`${__dirname}/build/main.js`#`${dirname(__dirname)}/build/main.js`#' \
        packages/app-cli/app/cli-integration-tests.test.ts

Apparently turndown is the library used to change html into markdown, not something I'm using the cli version for either. (I just use it to make a daily backup, and to search notes and display them.)

@bernieke Thank you! I added the allow-scripts flag.

I notice it still warns "@joplin/turndown" is blocked, though adding it to allow-scripts doesn't fix it. Let me know if this is causing real issues. I don't use joplin TUI much.

Npm 12 blocks dependency install scripts unless allowlisted, and only warns about this, without failing the build, resulting in a broken package.

To fix it the npm install command needs to be updated to: npm install -g --install-links --allow-scripts=keytar,sharp,sqlite3 --prefix "${pkgdir}/usr" *.tgz

@Thorin_Wolf What did you mean? There has always been one line of npm install because joplin TUI client is a nodejs package.

The latest version of the PKGBUILD includes a use of npm install when it was not there previously. Please look into this/do not install/update this package as it's something to be concerned about and is not considered valid.