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

I followed the suggestion of running sudo corepack enable but I have the habit of uninstalling build dependencies after building, so yarn was uninstalled. After I enabled corepack, installing yarn was failing because yarn already existed. I had to disable corepack, install yarn explicitly (yuck), and reenable corepack. then the build worked.

If the project can only be built with corepack, can we get rid of the build dependency on yarn? otherwise, is there a way to get yarn 3.3.1 globally? why is version from pacman 1.x?

I had the following error during joplin-desktop update:

  -> Installing package
{
  name: 'joplin',
  packageManager: 'yarn@3.3.1'
}
error This project's package.json defines "packageManager": "yarn@3.3.1". However the current global version of Yarn is 1.22.21.

Presence of the "packageManager" field indicates that the project is meant to be used with Corepack, a tool included by default with all official Node.js distributions starting from 16.9 and 14.19.
Corepack must currently be enabled by running corepack enable in your terminal. For more information, check out https://yarnpkg.com/corepack.

I successfully fixed the error by running:

$ sudo corepack enable

masterkorp: I've been using your PKGBUILD file to build the 2.13 series of releases by only changing pkgver= and updating sha256sums=. I just built version 2.13.13 today when I saw your comment.

At some point about a month ago, I ran: $ npm cache clean --force when I was experiencing build errors. Since then, I haven't had problems.

Unfortunately, while willing, I don't know what I can contribute to the conversation more than this; I appreciate your work in providing the build files.

Just for an update, I am having troubles upgrading the package to 2.13.10

https://discourse.joplinapp.org/t/cannot-build-for-arch-linux/34625

Any suggestions or ideas are welcome.

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.