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.

@tomacrisan, Could you provide more details? I'd like to make sure I don't have something messing my installation up. Mine compiles but just stays "connecting", times out after 2047 seconds. Meanwhile other devices (different OS) connect fine, same network, wondering if it's just my installation.

@dosenpils: I want to report the cause to my problems with building joplin using your PKGBUILD and it was clearly my fault. I found that I had a version of nodejs from 2023 installed under /usr/local/ that was unknown to the package manager but was executing before the nodejs-lts-iron package that is installed under /usr/.

The reason the joplin-beta PKGBUILD would work for me is that it would install a copy of nodejs of the required version in the build directory.

Thanks for your work in providing Joplin for the Arch community and apologies for any of your time I might have wasted.

Ever since 10b22a33a84bb603e76cfa2aebf5376fe8d2b561 I've not been able to connect to anything, unable to determine why either. Giving up. (Edit: Not saying it's this AUR or anything else, just mentioning the timing.) Edit: Fixed which commit.

not having the nodejs-lts-iorn dependency was good, some things on my system did not work well with it (only with the regular nodejs)

I get the build error below. nodejs and nodejs-lts-iron conflict.

==> Missing dependencies:
  -> nodejs-lts-iron

Sorry for the inconvenience, I have reverted the last two changes.

This is completely broken for me using Wayland since last major changes in the PKGBUILD...

dosenpils: Why did you decide to merge again joplin and joplin-desktop into a single package? I guess you should unpin the comments that are not relevant anymore. Also, I guess you should add joplin-desktop to the conflicts array, for people that installed it before.

Does it also build the mobile app which is not needed?

ild/joplin/src/joplin-3.2.13/packages/app-mobile/tools/../pluginAssets/mermaid/mermaid_render.js.base64.js"
➤ YN0000: │ root@workspace:. STDOUT ➤ YN0000: [@joplin/app-mobile]: [10:39:38] Finished 'encodeAssets' after 1.15 s
➤ YN0000: │ root@workspace:. STDOUT ➤ YN0000: [@joplin/app-mobile]: [10:39:38] Starting 'podInstall'...
➤ YN0000: │ root@workspace:. STDOUT ➤ YN0000: [@joplin/app-mobile]: [10:39:38] Finished 'podInstall' after 701 μs
➤ YN0000: │ root@workspace:. STDOUT ➤ YN0000: [@joplin/app-mobile]: [10:39:38] Finished 'build' after 4.63 min
➤ YN0000: │ root@workspace:. STDOUT ➤ YN0000: [@joplin/app-mobile]: Process exited (exit code 0), completed in 4m 46s
➤ YN0000: │ root@workspace:. STDOUT ➤ YN0000: Done in 5m 30s
➤ YN0000: │ root@workspace:. STDOUT ➤ YN0000: [joplin]: Process started

I just installed version 3.2.23-1 of the package and it installed the joplin-desktop application instead of the command line one. Is this on purpose? If so, that would we really disappointing...