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

@txtsd @masterkorp Add python2 to makedepends could fix this, or wait upstream (electron-rebuild) merge this pr. https://github.com/electron/electron-rebuild/pull/669

There is a problem building version 2.0.11-1 I got this error while building: curl: (33) HTTP server doesn't seem to support byte ranges. Cannot resume. ==> ERROR: Failure while downloading https://github.com/laurent22/joplin/archive/v2.0.11.tar.gz Aborting... error downloading sources: joplin (joplin-desktop)

As a reminder, this packages refers to the latest stable release of joplin.

@maderios That's not a solution for me. Maybe there's some way to prevent npm from spawning so many processes.

@txtsd I met same issue, so i tried joplin-beta. It compiles and works fine for me.

This happens everytime. npm install processes stay running and maxing out my bandwidth even after it has failed. How do I get around it?

==> Making package: joplin 1.8.5-1 (Mon 07 Jun 2021 02:17:57 PM IST)
==> Retrieving sources...
  -> Found joplin.desktop
  -> Found joplin-desktop.sh
  -> Found joplin.sh
  -> Found joplin-1.8.5.tar.gz
==> Validating source files with sha256sums...
    joplin.desktop ... Passed
    joplin-desktop.sh ... Passed
    joplin.sh ... Passed
    joplin-1.8.5.tar.gz ... Passed
==> Making package: joplin 1.8.5-1 (Mon 07 Jun 2021 02:18:00 PM IST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found joplin.desktop
  -> Found joplin-desktop.sh
  -> Found joplin.sh
  -> Found joplin-1.8.5.tar.gz
==> Validating source files with sha256sums...
    joplin.desktop ... Passed
    joplin-desktop.sh ... Passed
    joplin.sh ... Passed
    joplin-1.8.5.tar.gz ... Passed
==> Removing existing $srcdir/ directory...
==> Extracting sources...
  -> Extracting joplin-1.8.5.tar.gz with bsdtar
==> Starting prepare()...
  -> npm cache directory: /home/txtsd/.cache/yay/joplin/src/npm-cache
  -> Disabling husky (git hooks)
  -> Tweaking lerna.json
==> Sources are ready.
==> Making package: joplin 1.8.5-1 (Mon 07 Jun 2021 02:18:07 PM IST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> WARNING: Using existing $srcdir/ tree
==> Removing existing $pkgdir/ directory...
==> 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 ECONNRESET
npm ERR! network aborted
npm ERR! network This is a problem related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly.  See: 'npm help config'

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/txtsd/.cache/yay/joplin/src/npm-cache/_logs/2021-06-07T08_49_47_546Z-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.8.5
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-06-07T08_49_47_647Z-debug.log
==> ERROR: A failure occurred in build().
    Aborting...
error making: joplin (joplin joplin-desktop)

This package officially doesn't support aarch64 (aka. arm64), but I thought I would try building the package anyway by adding aarch64 to supported platforms. The package indeed builds without any errors, but for some reason the built binary is now amd64, even though my system definitely tells it it is aarch64. Apologies if this is out of the scope of this packge, but I would appreciate any help on fixing this.

npm ERR! semver.simplifyRange is not a function

joplin-beta 2.0.2-1 compiles successfully today

1.8.5-1 update was strange. It lasted more than 1 hour, took over 400MB and then failed. Why did it use npm and electron-builder if it's already in the system? Anyway, I had to remove it and install from snap, which uses a fraction of the disk space and installed in ca. 2 minutes.