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

@zangoku I had the same error. You must remove yarn.lock from your homedir (at least that solved it for me using yay).

For last update I had to pass NODE_OPTIONS=--openssl-legacy-provider in build dir :

npm build export NODE_OPTIONS=--openssl-legacy-provider

build/install is ok anyway thanks for the hard work !

Getting this with the right nodejs version

==> Starting build()...
  -> Yarn cache directory: /home/zangoku/.cache/paru/clone/joplin/src/yarn-cache
  -> 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

Usage Error: The project in /home/zangoku/package.json doesn't seem to have been installed - running an install there might help

$ yarn install [--json] [--immutable] [--immutable-cache] [--check-cache] [--inline-builds] [--mode #0]
==> ERROR: A failure occurred in build().
    Aborting...
error: failed to build 'joplin-2.7.15-4 (joplin-desktop)': 

I get the following: ==> Making package: joplin 2.7.15-4 (Mon 28 Mar 2022 07:02:51 PM) ==> Checking runtime dependencies... ==> Missing dependencies: -> nodejs>=17.3 ==> Checking buildtime dependencies... ==> ERROR: Could not resolve all dependencies. error: failed to build 'joplin-2.7.15-4 (joplin-desktop)':

I have nodejs-lts-erbium which is listed as one of the valid nodejs dependencies.

Thank you guys for the positive feedback! I will try and keep the package as lean as possible, it still as a lot to improve first.

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

I tried building the latest update, but ran into this error:

➤ YN0001: │ Error: @joplin/lib@npm:~2.7: No candidates found
    at R (/home/thayne/.node/corepack/yarn/3.1.1/yarn.js:441:7773)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async Promise.all (index 0)
    at async Promise.all (index 0)
    at async Ke.resolveEverything (/home/thayne/.node/corepack/yarn/3.1.1/yarn.js:441:8197)
    at async /home/thayne/.node/corepack/yarn/3.1.1/yarn.js:444:2138
    at async Fe.startTimerPromise (/home/thayne/.node/corepack/yarn/3.1.1/yarn.js:412:3730)
    at async Ke.install (/home/thayne/.node/corepack/yarn/3.1.1/yarn.js:444:2077)
    at async /home/thayne/.node/corepack/yarn/3.1.1/yarn.js:449:122

I just wanted to second the earlier comment and say thank you for continuing your work on this package. It's obviously not been easy and people have not always been kind. But please know that your work is appreciated by many! The latest update is working nicely.

Sorry for the redundant comment but I just wanted to say thanks for your work on this package, I know it's not been easy getting it to work properly. The latest update works great!

This package has been updated, if any problem arises, please report on Github.