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

After the electron package was upgraded in my system to version 12.x, I started getting the following error when I tried to start joplin-desktop:

$ joplin-desktop
./@joplinapp-desktop: error while loading shared libraries: libicui18n.so.68: cannot open shared object file: No such file or directory

The version of icu I currently have installed is:

local/icu 69.1-1
    International Components for Unicode library

And the versions of electron are:

local/electron 12.0.4-2
    Build cross platform desktop apps with web technologies
local/electron11 11.4.3-2
    Build cross platform desktop apps with web technologies

Now that the default version of the electron package is 12.0.4, the joplin and joplin-desktop packages should probably use the electron11 package as a dependency until Joplin officially supports Electron 12.x.

I initially tried regenerating the packages with the latest electron (12.0.4-2) package but joplin-desktop would not start. To fix the issues I had to modify the electron dependency and set it to electron11. These are the changes I made to the PKGBUILD:

diff --git a/PKGBUILD b/PKGBUILD
index 0b84f90..c854958 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -11,11 +11,11 @@ pkgver=1.7.11
 groups=('joplin')
 pkgrel=2
 install="joplin.install"
-depends=('electron' 'gtk3' 'libexif' 'libgsf' 'libjpeg-turbo' 'libwebp' 'libxss' 'nodejs'
+depends=('electron11' 'gtk3' 'libexif' 'libgsf' 'libjpeg-turbo' 'libwebp' 'libxss' 'nodejs'
          'nss' 'orc' 'rsync' )
 optdepends=('libappindicator-gtk3: for tray icon')
 arch=('x86_64' 'i686')
-makedepends=('git' 'npm' 'python' 'rsync' 'jq' 'electron')
+makedepends=('git' 'npm' 'python' 'rsync' 'jq' 'electron11')
 url="https://joplinapp.org/"
 license=('MIT')
 source=("joplin.desktop" "joplin-desktop.sh" "joplin.sh"
@@ -137,7 +137,7 @@ package_joplin() {

 package_joplin-desktop() {
   pkgdesc="A note taking and to-do application with synchronization capabilities - Desktop"
-  depends=('electron' 'gtk3' 'libexif' 'libgsf' 'libjpeg-turbo' 'libwebp' 'libxss' 'nodejs'
+  depends=('electron11' 'gtk3' 'libexif' 'libgsf' 'libjpeg-turbo' 'libwebp' 'libxss' 'nodejs'
          'nss' 'orc')
   optdepends=('libappindicator-gtk3: for tray icon')
   conflicts=('joplin-desktop-electron')
@@ -149,8 +149,8 @@ package_joplin-desktop() {
   msg2 "Building Desktop with packaged Electron..."
   mkdir -p "${pkgdir}/usr/share/joplin-desktop"
   cd "${srcdir}/joplin-${pkgver}/packages/app-desktop"
-  electron_dir="/usr/lib/electron"
-  electron_version=$(cat /usr/lib/electron/version)
+  electron_dir="/usr/lib/electron11"
+  electron_version=$(cat /usr/lib/electron11/version)
   msg2 "Using Electron Version ${electron_version}"
   USE_HARD_LINKS=false npm run dist -- --publish=never  --linux  --x64 \
     --dir="dist/" -c.electronDist=$electron_dir -c.electronVersion=$electron_version

➜ joplin-desktop ./@joplinapp-desktop: error while loading shared libraries: libicui18n.so.68: cannot open shared object file: No such file or directory

The icu is 69 now (nice), so the repo is out of date?

I get this error while building, and it leaves several npm install processes running and maxing out my bandwidth.

==> Starting build()...
  -> npm cache directory: /home/txtsd/.cache/yay/joplin/src/npm-cache
  -> Installing dependencies through Lerna

> postinstall
> npm run bootstrap --no-ci && npm run build


> bootstrap
> lerna bootstrap --no-ci

lerna notice cli v3.22.1
lerna info versioning independent
lerna info Bootstrapping 9 packages
lerna info Installing external dependencies
lerna ERR! npm install --cache /home/txtsd/.cache/yay/joplin/src/npm-cache exited 1 in '@joplin/turndown'
lerna ERR! npm install --cache /home/txtsd/.cache/yay/joplin/src/npm-cache stderr:
npm ERR! code ERR_SOCKET_TIMEOUT
npm ERR! errno ERR_SOCKET_TIMEOUT
npm ERR! request to https://registry.npmjs.org/flat-cache/-/flat-cache-1.3.0.tgz failed, reason: Socket timeout

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/txtsd/.cache/yay/joplin/src/npm-cache/_logs/2021-04-18T07_18_49_739Z-debug.log

lerna ERR! npm install --cache /home/txtsd/.cache/yay/joplin/src/npm-cache exited 1 in '@joplin/turndown'
lerna WARN complete Waiting for 7 child processes to exit. CTRL-C to exit immediately.
npm ERR! code 1
npm ERR! path /home/txtsd/.cache/yay/joplin/src/joplin-1.7.11
npm ERR! command failed
npm ERR! command sh -c npm run bootstrap --no-ci && npm run build

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/txtsd/.cache/yay/joplin/src/npm-cache/_logs/2021-04-18T07_18_49_894Z-debug.log
==> ERROR: A failure occurred in build().
    Aborting...
error making: joplin (joplin-desktop)

Tried to rebuild this package this morning and I'n now getting the same error reported by @trumee. Any other workaround other than installing python2?

@trumee Turns out, that's a python error. Install python2 and it should be fixed.

It seems like libgsf doesn't show up in the Dependencies section even though it's defined in the PKGBUILD.

This breaks the build when using AUR helpers like yay. I'm not sure if libgsf needs to be added to the build dependencies list or if there's some other issue.

In the meantime anybody else running into this issue can just manually install libgsf so it isn't that huge an issue.

I am trying to install joplin-desktop 1.7.11 and getting the following error,

lerna ERR! npm install --cache /home/xx/.cache/pikaur/build/joplin/src/npm-cache stderr:
npm ERR! code 1
npm ERR! path /home/xx/.cache/pikaur/build/joplin/src/joplin-1.7.11/packages/tools/node_modules/sharp
npm ERR! command failed
npm ERR! command sh -c (node install/libvips && node install/dll-copy && prebuild-install --runtime=napi) || (node-gyp rebuild && node install/dll-copy)
npm ERR! info sharp Downloading https://github.com/lovell/sharp-libvips/releases/download/v8.9.1/libvips-8.9.1-linux-x64.tar.gz
npm ERR! gyp info it worked if it ends with ok
npm ERR! gyp info using node-gyp@3.8.0
npm ERR! gyp info using node@15.13.0 | linux | x64
npm ERR! gyp ERR! configure error 
npm ERR! gyp ERR! stack Error: Command failed: /usr/bin/python -c import sys; print "%s.%s.%s" % sys.version_info[:3];
npm ERR! gyp ERR! stack   File "<string>", line 1
npm ERR! gyp ERR! stack     import sys; print "%s.%s.%s" % sys.version_info[:3];
npm ERR! gyp ERR! stack                       ^
npm ERR! gyp ERR! stack SyntaxError: invalid syntax
npm ERR! gyp ERR! stack 
npm ERR! gyp ERR! stack     at ChildProcess.exithandler (node:child_process:326:12)
npm ERR! gyp ERR! stack     at ChildProcess.emit (node:events:369:20)
npm ERR! gyp ERR! stack     at maybeClose (node:internal/child_process:1067:16)
npm ERR! gyp ERR! stack     at Process.ChildProcess._handle.onexit (node:internal/child_process:301:5)
npm ERR! gyp ERR! System Linux 5.10.27-1-lts
npm ERR! gyp ERR! command "/usr/bin/node" "/home/xx/.cache/pikaur/build/joplin/src/joplin-1.7.11/packages/tools/node_modules/.bin/node-gyp" "rebuild"
npm ERR! gyp ERR! cwd /home/xx/.cache/pikaur/build/joplin/src/joplin-1.7.11/packages/tools/node_modules/sharp
npm ERR! gyp ERR! node -v v15.13.0
npm ERR! gyp ERR! node-gyp -v v3.8.0
npm ERR! gyp ERR! not ok

Please everyone. this package follows the stable releases of the projects, which at this time is 1.7.11, dont flag the package out of date without checking that.

@haven : I used the directions on Joplin's home page. That installed v1.6.3