Package Details: joplin 3.2.13-2

Git Clone URL: https://aur.archlinux.org/joplin.git (read-only, click to copy)
Package Base: joplin
Description: A note taking and to-do application with synchronization capabilities - CLI App
Upstream URL: https://joplinapp.org/
Keywords: markdown note notetaking productivity
Licenses: AGPL-3.0-or-later
Groups: joplin
Conflicts: joplin-appimage, joplin-beta, joplin-beta-appimage, joplin-electron
Submitter: masterkorp
Maintainer: dosenpils
Last Packager: dosenpils
Votes: 268
Popularity: 1.96
First Submitted: 2018-04-18 16:33 (UTC)
Last Updated: 2025-03-12 23:14 (UTC)

Pinned Comments

masterkorp commented on 2020-12-24 19:58 (UTC) (edited on 2020-12-24 20:00 (UTC) by masterkorp)

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

Latest Comments

« First ‹ Previous 1 .. 10 11 12 13 14 15 16 17 18 19 20 .. 57 Next › Last »

thayne commented on 2022-02-02 09:09 (UTC)

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

thurisaz commented on 2022-01-31 17:59 (UTC)

@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!

manouchk commented on 2022-01-31 17:39 (UTC) (edited on 2022-01-31 17:41 (UTC) by manouchk)

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.

Tilduke commented on 2022-01-21 12:31 (UTC)

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

tovo commented on 2022-01-20 13:42 (UTC)

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

j0hannes commented on 2022-01-20 13:39 (UTC)

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().

professed commented on 2022-01-20 01:31 (UTC) (edited on 2022-01-21 15:38 (UTC) by professed)

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!

thurisaz commented on 2022-01-19 23:41 (UTC)

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.

thurisaz commented on 2022-01-19 22:34 (UTC)

I noticed a comment in the PKGBUILD about electron breaking the interface (# FIXME: Using packaged electron breaks the interface on line 168). According to @masterkorp's pinned comment, the package is "usable and stable", so I wonder if the editor issues we're having might be because of different electron versions?

I've got electron16, electron13, and electron11 installed. I didn't check which one was used when the package was built, but I might rebuild and check. @maderios, @gwenlune, @Darkmind2007, what electon versions have you got installed?

maderios commented on 2022-01-19 19:54 (UTC)

Build needs nodejs 16, 'nodejs-lts-gallium'. Then, same issue with editor than other users. I don't think it's upstream bug because appimage version works fine.

« First ‹ Previous 1 .. 10 11 12 13 14 15 16 17 18 19 20 .. 57 Next › Last »