Package Details: joplin 1.0.104-2

Git Clone URL: https://aur.archlinux.org/joplin.git (read-only)
Package Base: joplin
Description: Joplin - a note taking and to-do application with synchronization capabilities for Windows, macOS, Linux, Android and iOS.
Upstream URL: https://joplin.cozic.net
Licenses: MIT
Provides: joplin, joplin-cli
Submitter: masterkorp
Maintainer: masterkorp
Last Packager: masterkorp
Votes: 5
Popularity: 1.609964
First Submitted: 2018-04-18 16:33
Last Updated: 2018-07-03 10:25

Latest Comments

erikfk commented on 2018-07-05 20:09

About the 'node-gyp rebuild' error, just install nodejs-lts-carbon or another lts release. Worked for me!

j1simon commented on 2018-07-03 10:45

Error: sharp@0.18.4 install: 'node-gyp rebuild'

https://pastebin.com/3YSV8HeJ

felmey commented on 2018-06-17 16:32

The latest Firefox and Chrome Web Clipper extensions are only compatible with Joplin 1.0.99+ according to the developer: https://github.com/laurent22/joplin/issues/629#issuecomment-397888946

This patch for PKGBUILD will allow you to install Joplin 1.0.99 and restore the Web Clipper functionality:


diff --git a/PKGBUILD b/PKGBUILD
index 3a4af2c..e99f2eb 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -4,7 +4,7 @@
 # https://github.com/masterkorp/joplin-pkgbuild

 pkgname=joplin
-pkgver=1.0.96
+pkgver=1.0.99
 pkgrel=1
 pkgdesc="Joplin - a note taking and to-do application with synchronization capabilities for Windows, macOS, Linux, Android and iOS."
 arch=("x86_64" "i686")
@@ -18,7 +18,7 @@ source=("${pkgname}.desktop" "joplin-desktop.sh" "joplin.sh"
 sha256sums=("9ee4a831a0853ddbdc7279629d8f9238d3737b570898be16176ba0968b53d43d"
             "5a3ace64906080adde5a5ea10ec9221fb2d94de770e6ee35b454aa30608b4097"
             "5e3424162814db56718b01740af1ef7c9b30e00f563040456eeb8b7eaca81427"
-            "8e8dfda2ddfdfc21ad808457265c19894e154193be44e4b3319984375e4af97a")
+            "514f2e9bba03c0ed342a7cdbffb5fc5b6a8a65097e9ef2b2c517cd60bed8cbf7")


 build() {

felmey commented on 2018-06-15 07:18

@bossi - Thanks for the link. I ended up getting Joplin to work by installing NVM using it to install nodejs-lts-carbon. Anyone who wants to try it check out these two links: https://wiki.archlinux.org/index.php/Node.js_ https://github.com/creationix/nvm

Once I followed those links, I removed the nodejs-lts-carbon in the two places it is listed in the PKGBUILD and the package installed and runs fine now.

bossi commented on 2018-05-20 04:39

@felmey - Yes, Joplin's dependencies have moved from nodejs to nodejs-lts-carbon, due to an incompatibility with the latest nodejs-10's sqlite libraries, it seems. This results in dependency conflicts if you have anything else installed that depends on nodejs as the two nodejs-packages are mutually exclusive.

Have a look here for further details.

felmey commented on 2018-05-19 03:44

There seems to be a problem with nodejs and it wants to install nodejs-lts-carbon but that breaks other dependencies... Anyone else have this problem?

bossi commented on 2018-05-05 11:13

Awesome, thanks @masterkorp,

I see you're listing your github repo in the sources, was just about to suggest. I'll continue using that space instead to track issues; happy to contribute back if I get a chance.

Best Regards~

masterkorp commented on 2018-05-03 09:59

Hello @bossi,

Yes, the AUR repository, its just for the code. I do have another repository on github https://github.com/masterkorp/joplin-pkgbuild

You are more than welcome to open an issue there, or even contribute directly.

Regards, Alfredo Palhares

bossi commented on 2018-05-02 22:13

Hi @masterkorp,

Not a problem at all, thanks for posting back though! I wasn't sure if this is the right channel to discuss these more specific, code-related issues (was looking for something closer to the repository itself but there isn't?). I have picked up your patch since, works all well on my end - I figured you had either seen my post or noticed the issue yourself. Cheers!

masterkorp commented on 2018-05-02 10:12

Hello @bossi,

Firts of all, sorry for the delay on the response, somehow I did not get propely notifed.

Thank you for you patch, but by now the packages has been fixed. Can you confirm it does work for you?

All comments