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

Hello Team, Recently I installed Joplin Desktop App (v2.6.10-4) in my Arch Linux (with BSPWM). The installation went fine and I was able to sync my notes from Dropbox as well. I ran into a problem however and that was I couldn't write anything in editor layout nor can edit my existing notes. It's like editor is simply broken.

Console outputs the following issue. But I don't think this is correlated. Anyway I am posting it here

A page or script is accessing at least one of navigator.userAgent, navigator.appVersion, and navigator.platform. In a future version of Chrome, the amount of information available in the User Agent string will be reduced.
To fix this issue, replace the usage of navigator.userAgent, navigator.appVersion, and navigator.platform with feature detection, progressive enhancement, or migrate to navigator.userAgentData.
Note that for performance reasons, only the first access to one of the properties is shown.

Help is much appreciated. Thanks

@professed thank you! Had the below error

your user’s .npmrc file (${HOME}/.npmrc)
has a `globalconfig` and/or a `prefix` setting, which are incompatible with nvm.
Run `nvm use --delete-prefix v16.9.1` to unset it.

commented out the prefix line in the .npmrc file and everything continued successfully. *fixed formatting

would it be possible to change the python2 make dependency to python 3?

@manouchk: When building with makepkg, you can remove the source folder by using the -C flag.

That said, note that you need to answer yes to the prompt about the patch, and even then many people have ended up with a broken interface after building joplin with this PKGBUILD. You can try it and see if it works for you; if not, there's a link in the comments to another PKGBUILD that should work. (It didn't work for me, and I've ended up using the -appimage package for the moment instead.)

I hope that helps!

I got the same error as j0hannes.One suggestion made was "remove your src/ folder before using this version" but I don't know how to implement it.

Should have an explicit dependency on npm. Build fails without it.

Thanks a lot @professed ! Your procedure saved my life!

I see this error building it:

The next patch would create the file yarn.lock,
which already exists!  Assume -R? [n] 
Apply anyway? [n] 
Skipping patch.
1 out of 1 hunk ignored
==> ERROR: A failure occurred in prepare().

Thanks to Luis Carvalho and Rob Sears over on Github, I was able to successfully build and install both packages using the following procedure. The resulting Joplin Desktop application has a working interface.

First, install nvm from the AUR.

Next, clone Joplin from the AUR and navigate to the new joplin folder:

$ git clone https://aur.archlinux.org/joplin.git; cd joplin

Next, delete the existing PKGBUILD:

$ rm PKGBUILD

Then replace it with this new PKGBUILD file, courtesy of Luis Carvalho.

And finally, run makepkg to build/install Joplin and Joplin Desktop:

$ makepkg -si

Voila!

It was building with electron16. I tried with the other two versions I've got (13 and 11) but still had the same problem. Maybe it's not the electron version, or maybe these just aren't the right ones. shrug

Anyway, I realized there's an open issue about this on @masterkorp's github and there's even a comment there with a PKGBUILD that's supposed to work. I'll have a look at that when I next have time for this and will probably try building with it.