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

You may need to remove your src/ folder before using this version

What is 'src/' folder? Where should I remove it from?

So far, I get this while trying to install this package:

Error: Cannot find module 'code-point-at'
Require stack:
- /usr/lib/node_modules/npm/node_modules/node-gyp/node_modules/string-width/index.js
- /usr/lib/node_modules/npm/node_modules/node-gyp/node_modules/gauge/wide-truncate.js
- /usr/lib/node_modules/npm/node_modules/node-gyp/node_modules/gauge/render-template.js
- /usr/lib/node_modules/npm/node_modules/node-gyp/node_modules/gauge/plumbing.js
- /usr/lib/node_modules/npm/node_modules/node-gyp/node_modules/gauge/index.js
- /usr/lib/node_modules/npm/node_modules/node-gyp/node_modules/npmlog/log.js
- /usr/lib/node_modules/npm/node_modules/node-gyp/lib/node-gyp.js
- /usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js
    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15)

Is there any upstream issue to follow already?

At the moment, i cannot click into the edit window of a note to add text.

edit: sorry, i only saw your pinned comments and thought that they were the most recent ones. but below them there are newer ones.

I got error

error electron-builder@22.14.5: The engine "node" is incompatible with this module. Expected version ">=14.0.0". Got "12.22.8"
error Found incompatible module.
lerna ERR! yarn install --mutex network:42424 --non-interactive --cache /home/fre/ARCH-AUR/joplin/src/npm-cache --no-optional exited 1 in '@joplin/app-desktop'
lerna WARN complete Waiting for 3 child processes to exit. CTRL-C to exit immediately.
error Command failed with exit code 1.

Like the others, I would also have preferred to install this instead of the appimage version.

I'm sorry you feel that way @masterkorp. I actually think it's a good thing that people are posting build issues here (although I think that issues with the application itself should be posted upstream). I think maintainers should be notified of build issues, even if the commenter is incapable of providing the solution.

However, if you feel unable to fix this package, then perhaps you could post upstream or in the Arch forum for help? If the PKGBUILD is broken, I would certainly not want to discourage people from posting here.

(Also, I noticed that you maintain three other packages, all of which have been flagged as out of date. One is 2 months out of date, and another is 14 months! The last should probably be deleted. No offence, but if you do feel overwhelmed by maintaining packages in general, perhaps it would be a good idea to disown them.)

@masterkorp I understand your frustration. I hope you continue maintaining the package and I really appreciate the work and time you put into this. I prefer this over flatpak, AppImage etc. and also having the CLI client.

To be honest, even though the AppImage provides a solution (I haven't tried it, just following the other comments), I must say that I'd personally consider it as the last resort.

My preference would be to have as little AppImage apps on my PC as possible, only for products that are too difficult to integrate with the system. Otherwise app management becomes too much MacOS style, which doesn't seem like Arch way of doing things.

Just to be clear, I didn't mean to complain about the package quality leaving the comment with the error message. It was just to provide some debug data or in case someone else has already faced the same problem.

I'd be happy to help if I had more experience with electron and JS.

@madjoe I only follow stable branches too, this is the cost of properly packaging stuff. That package is there if anyone needs it, but it does not provide the joppin cli client.

I honestly just want to disown this package, with some many people just demanding that stuff works out of the box, but they do not provide or help with any helpfull solution.

@Rhinoceros: Too many issues with this package. I agree, joplin-appimage simply works and besides, it only follows stable branches, which is a plus.

For anyone else unable to build this package, joplin-appimage works well as a replacement to joplin-desktop.