Arch Linux User Repository

Thank you so much for keeping this build updated.

I got a minor build issue. Its probably an upstream issue, but since people look here first, I'll post my workaround.

The error:

$ yay -Scc; yay -S joplin-desktop
[...]
➤ YN0009: │ @joplin/app-clipper@workspace:packages/app-clipper couldn't be built successfully (exit code 1, logs can be found here: /tmp/xfs-81117b5e/build.log)
[...]

$ cat /tmp/xfs-81117b5e/build.log
[...]
Error: Cannot find module 'eslint-loader'
[...]

The Fix:

$ cd ~/.cache/yay/joplin/src/joplin-2.7.15/packages/app-clipper/
$ npm install --save-dev eslint-loader

$ cd ~/.cache/yay/joplin/
$ makepkg
$ sudo pacman -U joplin-desktop-2.7.15-4-x86_64.pkg.tar.zst

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

Hi, I've been able to reproduce by removing libvips and running joplin. libvips is set up as a "make dependency" in the PKGBUILD (so if you passed the optional -r to makepkg then it will remove it at the end of the build) but it looks like it's needed for joplin (while joplin-desktop starts up fine). So, for now, manually installing libvips should do (please tell if it's not the case). I'll create an issue in https://github.com/alfredopalhares/arch-pkgbuilds/issues to investigate/fix.

% joplin
/usr/share/joplin/node_modules/sharp/lib/sharp.js:37
  throw new Error(help.join('\n'));
  ^

Error: 
Something went wrong installing the "sharp" module

libvips-cpp.so.42: cannot open shared object file: No such file or directory

Possible solutions:
- Install with verbose logging and look for errors: "npm install --ignore-scripts=false --foreground-scripts --verbose sharp"
- Install for the current linux-x64 runtime: "npm install --platform=linux --arch=x64 sharp"
- Consult the installation documentation: https://sharp.pixelplumbing.com/install
    at Object.<anonymous> (/usr/share/joplin/node_modules/sharp/lib/sharp.js:37:9)
    at Module._compile (node:internal/modules/cjs/loader:1376:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1435:10)
    at Module.load (node:internal/modules/cjs/loader:1207:32)
    at Module._load (node:internal/modules/cjs/loader:1023:12)
    at Module.require (node:internal/modules/cjs/loader:1235:19)
    at require (node:internal/modules/helpers:176:18)
    at Object.<anonymous> (/usr/share/joplin/node_modules/sharp/lib/constructor.js:11:1)
    at Module._compile (node:internal/modules/cjs/loader:1376:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1435:10)

Node.js v21.2.0

Hey spyrou, that error comes from yarnpkg, which is used by Joplin itself. It seems it wants to create the .yarn dir in the root. I can see few bugs reported around dir resolution, such as https://github.com/yarnpkg/berry/issues/3136 (Windows?) or https://github.com/yarnpkg/berry/issues/4908. I can't reproduce it though. Try to put yourself in the easiest scenario to figure out the cause/make it work: clone this repo in a new dir (no dir symlinks and no spaces) in your home dir (not root), cd into it and run makepkg -i as local user. I assume as well you didn't change anything about yarn configuration, otherwise you might want to reset/delete that customisation to start with a fresh yarn configuration (looks like yarn config list --verbose tells you where those config files are). Maybe run yarn cache clean?

Had to switch to joplin-appimage because joplin-desktop would not install due to a yarn issue:

-> Installing dependencies through Yarn 3...
➤ YN0065: Yarn will periodically gather anonymous telemetry: https://yarnpkg.com/advanced/telemetry
➤ YN0065: Run yarn config set --home enableTelemetry 0 to disable

Internal Error: ENOENT: no such file or directory, mkdir '/.yarn'
Error: ENOENT: no such file or directory, mkdir '/.yarn'
==> ERROR: A failure occurred in build().
    Aborting...
Finished with result: exit-code
Main processes terminated with: code=exited/status=4
Service runtime: 4.579s
CPU time consumed: 5.271s

Thanks anyway.

Hi, for the latest version gyp throws an exception and the build fails:

gyp ERR! stack Error: Cannot find module '@gar/promisify'
...
gyp ERR! System Linux 6.4.12-arch1-1
gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd path/to/joplin/pkg/joplin/usr/share/joplin/.yarn/unplugged/keytar-npm-7.9.0-682d6e5c1d/node_modules/keytar
gyp ERR! node -v v20.6.0
gyp ERR! node-gyp -v v9.3.1
gyp ERR! Node-gyp failed to build your package.
gyp ERR! Try to update npm and/or node-gyp and if it does not help file an issue with the package author.

Latest version v2.12.15 finally resolved the annoying issue that I noticed 4 months ago after updating to Gnome 44.1: it's now possible to close Joplin in maximised state and, when relaunched, it's visible and maximised.

Hi @jeremyjjbrown, that's quite unfortunate situation you are in. There's nothing wrong in the versions: you probably have installed "go-yq", which has the exact same executable "/usr/bin/yq" as "yq" so they can't co-exist. I'd first check if you really need "go-yq". If you do, please note that "yq" it's a build dependency for Joplin, so you could uninstall "go-yq", install "yq", build Joplin, uninstall "yq", install "go-yq".

I can't install because the package wants an old version of jq (3.2.2). 3.4 is installed

(4/4) checking for file conflicts                                                                                      [#######################################################################] 100%
error: failed to commit transaction (conflicting files)
yq: /usr/bin/yq exists in filesystem
Errors occurred, no packages were upgraded.
error installing repo packages