Package Details: joplin-desktop 2.8.8-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: MIT
Conflicts: joplin-desktop-electron
Submitter: masterkorp
Maintainer: masterkorp
Last Packager: masterkorp
Votes: 221
Popularity: 2.18
First Submitted: 2018-04-18 16:33 (UTC)
Last Updated: 2022-08-06 00:14 (UTC)

Pinned Comments

Kaffka commented on 2022-03-28 11:43 (UTC) (edited on 2022-03-28 11:47 (UTC) by Kaffka)

Thank you so much for keeping this build updated.

I got a minor build issue. Its probably an upstream issue, but since people look here first, I'll post my workaround.

The error:

$ yay -Scc; yay -S joplin-desktop
[...]
➤ YN0009: │ @joplin/app-clipper@workspace:packages/app-clipper couldn't be built successfully (exit code 1, logs can be found here: /tmp/xfs-81117b5e/build.log)
[...]

$ cat /tmp/xfs-81117b5e/build.log
[...]
Error: Cannot find module 'eslint-loader'
[...]

The Fix:

$ cd ~/.cache/yay/joplin/src/joplin-2.7.15/packages/app-clipper/
$ npm install --save-dev eslint-loader

$ cd ~/.cache/yay/joplin/
$ makepkg
$ sudo pacman -U joplin-desktop-2.7.15-4-x86_64.pkg.tar.zst

masterkorp commented on 2021-12-27 11:30 (UTC) (edited on 2021-12-27 11:32 (UTC) by masterkorp)

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

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

Paragoumba commented on 2022-08-08 16:39 (UTC)

@ikidd: All AUR packages are assumed to depend on base-devel which should not be added in the dependencies. See https://wiki.archlinux.org/title/PKGBUILD#makedepends

ikidd commented on 2022-08-07 22:11 (UTC)

On a fresh install, need to have base-devel or at least make installed, not part of the PKGBUILD dependencies.

valandil commented on 2022-08-05 02:21 (UTC)

I can confirm that @cuihao's version compiles fine in a clean chroot. I don't understand why the current PKGBUILD needs to huge a local cache and other complications while a simple yarn install seems to work.

Note that I wasn't able to build 2.9.1, but since it's a pre-release I haven't investigated why, just mentioning this as a heads-up.

cuihao commented on 2022-07-30 18:31 (UTC)

I'm maintaining my version of joplin / joplin-desktop PKGBUILD in the archlinuxcn repo: https://github.com/archlinuxcn/repo/tree/master/archlinuxcn/joplin Feel free to use the PKGBUILD or the compiled packages from archlinuxcn repo.

Disclaimer: I make sure the desktop client works on my machine before publishing a new version to the repo. But I don't use the CLI version so it's not tested.

valandil commented on 2022-07-29 18:50 (UTC)

I confirm that I was able to build trap000d's package, but I have two questions: * why did you merge joplin and joplin-desktop? * I cannot build this package in a clean chroot. Unfortunately it's hard to pinpoint the error, as the logs are said to be in /tmp/xxxx, but that doesn't seem to exist in the chroot. Maybe it's related to what a pinned comment says, and the main package.json is missing a dep?

trap000d commented on 2022-07-20 07:46 (UTC)

"To whom it may concern"

A month ago I've managed to build 2.8.8. You can find pkgbuild here:

https://github.com/trap000d/aur/tree/master/joplin

xavierbaez commented on 2022-07-11 22:03 (UTC)

➤ YN0007: │ @joplin/app-desktop@workspace:packages/app-desktop must be built because it never has been before or the last one failed ➤ YN0007: │ @fortawesome/fontawesome-svg-core@npm:1.2.36 must be built because it never has been before or the last one failed ➤ YN0007: │ @fortawesome/free-regular-svg-icons@npm:5.15.4 must be built because it never has been before or the last one failed ➤ YN0007: │ @fortawesome/free-solid-svg-icons@npm:5.15.4 must be built because it never has been before or the last one failed ➤ YN0009: │ root@workspace:. couldn't be built successfully (exit code 1, logs can be found here: /tmp/xfs-6c0ad799/build.log) ➤ YN0000: └ Completed in 4m 25s ➤ YN0000: Failed with errors in 9m 55s ==> ERROR: A failure occurred in build(). Aborting... -> error making: joplin (joplin-desktop)

masterkorp commented on 2022-07-08 14:00 (UTC)

@tomc yes, do you have any particular question?

tomc commented on 2022-07-08 11:43 (UTC)

@masterkorp Hi Alfredo, please could you confirm whether you are still willing and able to maintain this package? Thanks

gu1ll0me commented on 2022-06-05 15:04 (UTC) (edited on 2022-06-05 15:05 (UTC) by gu1ll0me)

@jost21 You can try this (thanks to tomc):

mkdir joplin ; cd joplin
wget https://github.com/archlinuxcn/repo/raw/69b44e1cf576ca261a4868906d5ab9f238570839/archlinuxcn/joplin/{PKGBUILD,joplin-desktop.desktop,joplin-desktop.sh}
makepkg -si

jost21 commented on 2022-06-03 10:17 (UTC)

I also wasn't able to build this package since last year. It's really too bad. Unfortunately neither of those two fixes suggested by tomc seem to work for me.

tomc commented on 2022-06-03 06:45 (UTC) (edited on 2022-06-03 06:46 (UTC) by tomc)

This package has had build issues since the upgrade to joplin 2.6.10 in december last year.

A fix is suggested here: https://github.com/alfredopalhares/arch-pkgbuilds/issues/112#issuecomment-1103266908.

In the same issue there's a link to a working PKGBUILD https://github.com/archlinuxcn/repo/blob/69b44e1cf576ca261a4868906d5ab9f238570839/archlinuxcn/joplin/PKGBUILD

mefistofeles commented on 2022-06-02 20:32 (UTC) (edited on 2022-06-02 20:37 (UTC) by mefistofeles)

I'm facing similar issues building this package. Log is https://bpa.st/CEYQ

Beomus commented on 2022-05-29 03:58 (UTC)

Hey, i'm getting a build issue..

$ paru -S joplin-desktop
[ various shit ]
➤ YN0009: │ root@workspace:. couldn't be built successfully (exit code 1, logs can be found here: /tmp/xfs-74af09b8/build.log)

the log

➤ YN0000: Done in 28s 242ms
    at makeError (/home/beomus/.cache/paru/clone/joplin/src/joplin-2.7.15/packages/tools/node_modules/execa/lib/error.js:59:11)
    at handlePromise (/home/beomus/.cache/paru/clone/joplin/src/joplin-2.7.15/packages/tools/node_modules/execa/index.js:114:26)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async fn (/home/beomus/.cache/paru/clone/joplin/src/joplin-2.7.15/gulpfile.js:35:5)

I don't have much (any) experience with nodeJS or npm, i have not the faintest idea what is going on..

weberval commented on 2022-05-24 11:38 (UTC)

Joplin fails while building in a chroot on my machine. @masterkorp can you please check if it builds correctly on your machine in a chroot (makechrootpkg)? Thank you!

ak2021 commented on 2022-05-17 11:25 (UTC) (edited on 2022-05-17 11:27 (UTC) by ak2021)

Anyone have a solution for this?


➤ YN0000: [@joplin/app-desktop]: Copying packages/app-desktop/node_modules/mark.js/dist/mark.min.js => packages/app-desktop/vendor/lib/mark.js/dist/mark.min.js
➤ YN0000: [@joplin/app-desktop]: Copying packages/lib/services/plugins/sandboxProxy.js => packages/app-desktop/vendor/lib/@joplin/lib/services/plugins/sandboxProxy.js
➤ YN0000: [@joplin/app-desktop]: [12:18:39] Finished 'copyApplicationAssets' after 12 s
➤ YN0000: [@joplin/app-desktop]: [12:18:39] Finished 'build' after 12 s
➤ YN0000: [@joplin/app-desktop]: Process exited (exit code 0), completed in 12s 461ms
➤ YN0000: Done in 12s 468ms
    at makeError (/var/tmp/pamac-build-user/joplin/src/joplin-2.7.15/packages/tools/node_modules/execa/lib/error.js:59:11)
    at handlePromise (/var/tmp/pamac-build-user/joplin/src/joplin-2.7.15/packages/tools/node_modules/execa/index.js:114:26)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async fn (/var/tmp/pamac-build-user/joplin/src/joplin-2.7.15/gulpfile.js:35:5)

mschaller commented on 2022-05-11 20:32 (UTC)

same to me and no idea what's going wrong. I will also try the appimage...

quenyen commented on 2022-05-06 14:39 (UTC)

Last time I tried to get this to build on manjaro Qonos version (I use i3 if it matters) I got the following....

➤ YN0007: │ @joplin/app-desktop@workspace:packages/app-desktop must be built because it never has been before or the last one failed ➤ YN0007: │ @fortawesome/fontawesome-svg-core@npm:1.2.36 must be built because it never has been before or the last one failed ➤ YN0007: │ @fortawesome/free-regular-svg-icons@npm:5.15.4 must be built because it never has been before or the last one failed ➤ YN0007: │ @fortawesome/free-solid-svg-icons@npm:5.15.4 must be built because it never has been before or the last one failed ➤ YN0009: │ root@workspace:. couldn't be built successfully (exit code 1, logs can be found here: /tmp/xfs-c033ce67/build.log) ➤ YN0000: └ Completed in 2m 1s ➤ YN0000: Failed with errors in 2m 19s ==> ERROR: A failure occurred in build(). Aborting... -> error making: joplin (joplin-desktop)

If anyone knows a work around...or what I am doing wrong I would be much obliged.

quenyen commented on 2022-05-06 14:39 (UTC)

Last time I tried to get this to build on manjaro Qonos version (I use i3 if it matters) I got the following....

➤ YN0007: │ @joplin/app-desktop@workspace:packages/app-desktop must be built because it never has been before or the last one failed ➤ YN0007: │ @fortawesome/fontawesome-svg-core@npm:1.2.36 must be built because it never has been before or the last one failed ➤ YN0007: │ @fortawesome/free-regular-svg-icons@npm:5.15.4 must be built because it never has been before or the last one failed ➤ YN0007: │ @fortawesome/free-solid-svg-icons@npm:5.15.4 must be built because it never has been before or the last one failed ➤ YN0009: │ root@workspace:. couldn't be built successfully (exit code 1, logs can be found here: /tmp/xfs-c033ce67/build.log) ➤ YN0000: └ Completed in 2m 1s ➤ YN0000: Failed with errors in 2m 19s ==> ERROR: A failure occurred in build(). Aborting... -> error making: joplin (joplin-desktop)

If anyone knows a work around...or what I am doing wrong I would be much obliged.

w1ezl commented on 2022-05-05 00:14 (UTC)

Buildfile is broken using app-image for now.

➤ YN0000: Done in 13s 478ms
    at makeError (/home/User/.cache/yay/joplin/src/joplin-2.7.15/packages/tools/node_modules/execa/lib/error.js:59:11)
    at handlePromise (/home/User/.cache/yay/joplin/src/joplin-2.7.15/packages/tools/node_modules/execa/index.js:114:26)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async fn (/home/User/.cache/yay/joplin/src/joplin-2.7.15/gulpfile.js:35:5)

ak2021 commented on 2022-05-04 15:05 (UTC)

Any know how to fix this


➤ YN0000: [@joplin/app-desktop]: gui/NoteEditor/NoteBody/CodeMirror/CodeMirror.tsx(868,4): error TS2786: 'ErrorBoundary' cannot be used as a JSX component.
➤ YN0000: [@joplin/app-desktop]:   Its instance type 'ErrorBoundary' is not a valid JSX element.
➤ YN0000: [@joplin/app-desktop]:     The types returned by 'render()' are incompatible between these types.
➤ YN0000: [@joplin/app-desktop]:       Type '{}' is not assignable to type 'ReactNode'.
➤ YN0000: [@joplin/app-desktop]:         Type '{}' is missing the following properties from type 'ReactPortal': key, children, type, props
➤ YN0000: [@joplin/app-desktop]: gui/Root.tsx(257,4): error TS2786: 'ErrorBoundary' cannot be used as a JSX component.
➤ YN0000: [@joplin/app-desktop]:   Its instance type 'ErrorBoundary' is not a valid JSX element.
➤ YN0000: [@joplin/app-desktop]: Process exited (exit code 2), completed in 8s 443ms
➤ YN0000: Done in 8s 452ms
    at makeError (/home/User/Downloads/joplin/src/joplin-2.7.15/packages/tools/node_modules/execa/lib/error.js:59:11)
    at handlePromise (/home/User/Downloads/joplin/src/joplin-2.7.15/packages/tools/node_modules/execa/index.js:114:26)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async fn (/home/User/Downloads/joplin/src/joplin-2.7.15/gulpfile.js:35:5)

linuxninja commented on 2022-05-04 00:45 (UTC)

Setup a new arch machine just for building joplin. Looks like a missing dependency declaration: libxss

soorajsp commented on 2022-05-02 04:48 (UTC) (edited on 2022-05-02 04:49 (UTC) by soorajsp)

➤ YN0009: │ root@workspace:. couldn't be built successfully (exit code 1, logs can be found here: /tmp/xfs-15d9f8ec/build.log) ➤ YN0000: └ Completed in 5m 30s` ➤ YN0000: Failed with errors in 6m 42s ==> ERROR: A failure occurred in build(). Aborting... error: failed to build 'joplin-2.7.15-4 (joplin-desktop)': error: packages failed to build: joplin-2.7.15-4 (joplin-desktop)

Logs from /tmp/xfs-15d9f8ec/build.log: https://pastebin.com/jnTi6YwJ

I couldn't understand what went wrong. Also did steps mentioned in https://github.com/alfredopalhares/arch-pkgbuilds/issues/112

zangoku commented on 2022-04-04 16:44 (UTC)

@blixawillbargeld I do not have a yarn.lock file. Totally clueless about this error.

blixawillbargeld commented on 2022-04-02 17:44 (UTC)

@zangoku I had the same error. You must remove yarn.lock from your homedir (at least that solved it for me using yay).

t0mab commented on 2022-04-01 09:53 (UTC)

For last update I had to pass NODE_OPTIONS=--openssl-legacy-provider in build dir :

npm build export NODE_OPTIONS=--openssl-legacy-provider

build/install is ok anyway thanks for the hard work !

zangoku commented on 2022-03-29 00:26 (UTC) (edited on 2022-03-29 00:27 (UTC) by zangoku)

Getting this with the right nodejs version

==> Starting build()...
  -> Yarn cache directory: /home/zangoku/.cache/paru/clone/joplin/src/yarn-cache
  -> Installing dependencies through Yarn 3...
➤ YN0065: Yarn will periodically gather anonymous telemetry: https://yarnpkg.com/advanced/telemetry
➤ YN0065: Run yarn config set --home enableTelemetry 0 to disable

Usage Error: The project in /home/zangoku/package.json doesn't seem to have been installed - running an install there might help

$ yarn install [--json] [--immutable] [--immutable-cache] [--check-cache] [--inline-builds] [--mode #0]
==> ERROR: A failure occurred in build().
    Aborting...
error: failed to build 'joplin-2.7.15-4 (joplin-desktop)': 

zangoku commented on 2022-03-28 23:07 (UTC)

I get the following: ==> Making package: joplin 2.7.15-4 (Mon 28 Mar 2022 07:02:51 PM) ==> Checking runtime dependencies... ==> Missing dependencies: -> nodejs>=17.3 ==> Checking buildtime dependencies... ==> ERROR: Could not resolve all dependencies. error: failed to build 'joplin-2.7.15-4 (joplin-desktop)':

I have nodejs-lts-erbium which is listed as one of the valid nodejs dependencies.

masterkorp commented on 2022-03-28 14:15 (UTC)

Thank you guys for the positive feedback! I will try and keep the package as lean as possible, it still as a lot to improve first.

Kaffka commented on 2022-03-28 11:43 (UTC) (edited on 2022-03-28 11:47 (UTC) by Kaffka)

Thank you so much for keeping this build updated.

I got a minor build issue. Its probably an upstream issue, but since people look here first, I'll post my workaround.

The error:

$ yay -Scc; yay -S joplin-desktop
[...]
➤ YN0009: │ @joplin/app-clipper@workspace:packages/app-clipper couldn't be built successfully (exit code 1, logs can be found here: /tmp/xfs-81117b5e/build.log)
[...]

$ cat /tmp/xfs-81117b5e/build.log
[...]
Error: Cannot find module 'eslint-loader'
[...]

The Fix:

$ cd ~/.cache/yay/joplin/src/joplin-2.7.15/packages/app-clipper/
$ npm install --save-dev eslint-loader

$ cd ~/.cache/yay/joplin/
$ makepkg
$ sudo pacman -U joplin-desktop-2.7.15-4-x86_64.pkg.tar.zst

thayne commented on 2022-03-28 06:35 (UTC)

I tried building the latest update, but ran into this error:

➤ YN0001: │ Error: @joplin/lib@npm:~2.7: No candidates found
    at R (/home/thayne/.node/corepack/yarn/3.1.1/yarn.js:441:7773)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async Promise.all (index 0)
    at async Promise.all (index 0)
    at async Ke.resolveEverything (/home/thayne/.node/corepack/yarn/3.1.1/yarn.js:441:8197)
    at async /home/thayne/.node/corepack/yarn/3.1.1/yarn.js:444:2138
    at async Fe.startTimerPromise (/home/thayne/.node/corepack/yarn/3.1.1/yarn.js:412:3730)
    at async Ke.install (/home/thayne/.node/corepack/yarn/3.1.1/yarn.js:444:2077)
    at async /home/thayne/.node/corepack/yarn/3.1.1/yarn.js:449:122

professed commented on 2022-03-27 19:35 (UTC)

I just wanted to second the earlier comment and say thank you for continuing your work on this package. It's obviously not been easy and people have not always been kind. But please know that your work is appreciated by many! The latest update is working nicely.

benoliver999 commented on 2022-03-27 14:46 (UTC)

Sorry for the redundant comment but I just wanted to say thanks for your work on this package, I know it's not been easy getting it to work properly. The latest update works great!

masterkorp commented on 2022-03-25 18:49 (UTC)

This package has been updated, if any problem arises, please report on Github.

jinmax100 commented on 2022-03-05 14:09 (UTC)

@Paragoumba I opted for joplin-desktop-bin package from AUR as well. It's like devs have abandoned the project. Raised issue in Github and it said to report in AUR, but here none seems to reply.

Paragoumba commented on 2022-02-24 13:52 (UTC)

I have the same problem as @jinmax100. I can't edit my notes and the UI has some weird bugs (icons not displaying and some text displaying with the wrong font). I tried the AppImage of the same version (2.6.10) and it works perfectly. It might be a compilation problem

jinmax100 commented on 2022-02-08 13:24 (UTC) (edited on 2022-02-08 13:31 (UTC) by jinmax100)

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

LT_Horn commented on 2022-02-07 19:32 (UTC) (edited on 2022-02-07 19:42 (UTC) by LT_Horn)

@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

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.

ouuan commented on 2022-01-18 02:55 (UTC)

Please remove --user root in PKGBUILD. Since npm 7, the --user option is no longer available. --user root not only doesn't fix the permission problem, but also installs the package called "root", which conflicts with other packages that also have the --user root option.

thurisaz commented on 2022-01-16 17:06 (UTC)

Yes, I'm having the same problems as @Darkmind2007, @gwenlune, and others -- at least the inability to edit and garbage in the editor. (I haven't used joplin much in the past day, so I don't know if lines from the editor are being rendered in the wrong area.)

I've assumed it was an upstream issue but haven't had a chance to look into it. I've also got joplin 2.6.10 installed on an Ubuntu 21.04 machine. I'm very busy today, but when I have some time I'll check if the same problems show up there -- that might help narrow down the problem.

gwenlune commented on 2022-01-15 20:42 (UTC)

same issue here, no solution found!

Darkmind2007 commented on 2022-01-15 16:31 (UTC) (edited on 2022-01-15 16:31 (UTC) by Darkmind2007)

@thurisaz, thanks for the update! I managed to build and install the package. However, I seem to experience the same issues with the editor that other people were mentioning here:

  • I cannot edit anything

  • The lines from editor sometimes are rendered even outside of the editor area

  • There's often garbage in the editor like "xxxxx"

Have you experienced the same issues? If so, did you manage to fix them?

thurisaz commented on 2022-01-15 12:05 (UTC) (edited on 2022-01-15 12:07 (UTC) by thurisaz)

Like several others posting here, I had trouble upgrading to 2.6.10. Since I've got it installed now, I wanted to share what worked for me in case that helps.

  • The build initially failed with an error about lerna not building. I didn't save the exact error message, but it was similar to what @Darkmind2007 reported in this comment or what @zangoku reported in another comment. It turned out this was because I hadn't updated in a while. Updating my installation fixed the lerna-related error.

  • However, the build still failed with an error about the version of node -- the same one @maderios has here. I had nodejs-lts-erbium installed, which provides version 12.22.8-1, as reported in the error message. Upgrading to a more recent version of nodejs is the solution, as the error message states. I upgraded to nodejs-lts-gallium (v. 16.13.1-1) and then the build worked fine, but according to the error message nodejs-lts-fermium (v. 14.18.2-1) should also provide a recent enough version.

In a nutshell, the build worked fine for me with:

  1. pacman -Syu
  2. pacman -S nodejs-lts-gallium
  3. makepkg -Cs and respond yes to the prompt.

I hope that's helpful to someone. Thanks for the package, @masterkorp! I'm happier using this than an AppImage, and I appreciate the effort you've put in to maintain it.

lordasgart commented on 2022-01-14 05:33 (UTC)

For 2.6.10 you actually have to confirm the yarn.lock warning with the string "yes". "Y" or "y" is not sufficient here.

karcher commented on 2022-01-09 11:07 (UTC)

Hi,

I have removed the cache/yay/joplin/src folder and answered yes to the prompt, but the update is still failing:

Run `npm audit` for details.
  -> Rearranging directory tree
  -> Fixing Directories Permissions
  -> Removing References to $pkgdir
  -> Removing References to $srcdir
  -> Fixing Permissions set by npm
  -> Installing LICENSE
  -> Installing Startup Script
==> Tidying install...
  -> Removing libtool files...
  -> Purging unwanted files...
  -> Removing static library files...
  -> Stripping unneeded symbols from binaries and libraries...
strip: Unable to recognise the format of the input file `./usr/share/joplin/node_modules/aws-crt/dist/bin/linux-arm64/aws-crt-nodejs.node'
  -> Compressing man and info pages...
==> Checking for packaging issues...
==> WARNING: Package contains reference to $srcdir
usr/share/joplin/node_modules/sharp/build/config.gypi
==> WARNING: Package contains reference to $pkgdir
usr/share/joplin/node_modules/sharp/build/config.gypi
usr/share/joplin/node_modules/sharp/build/Makefile
usr/share/joplin/node_modules/node-gyp/gyp/pylib/gyp/generator/__init__.pyc
usr/share/joplin/node_modules/node-gyp/gyp/pylib/gyp/generator/make.pyc
usr/share/joplin/node_modules/node-gyp/gyp/pylib/gyp/__init__.pyc
usr/share/joplin/node_modules/node-gyp/gyp/pylib/gyp/input.pyc
usr/share/joplin/node_modules/node-gyp/gyp/pylib/gyp/common.pyc
usr/share/joplin/node_modules/node-gyp/gyp/pylib/gyp/simple_copy.pyc
usr/share/joplin/node_modules/node-gyp/gyp/pylib/gyp/xcode_emulation.pyc
==> Creating package "joplin"...
  -> Generating .PKGINFO file...
  -> Generating .BUILDINFO file...
  -> Adding install file...
  -> Generating .MTREE file...
  -> Compressing package...
==> Starting package_joplin-desktop()...
  -> Building Desktop with packaged Electron...
  -> Using Electron Version 16.0.6
yarn run v1.22.17
warning From Yarn 1.0 onwards, scripts don't require "--" for options to be forwarded. In a future version, any explicit "--" will be forwarded as-is to the scripts.
$ npm run electronRebuild && npx electron-builder --publish=never --linux --x64 --dir=dist/

> @joplin/app-desktop@2.6.10 electronRebuild
> gulp electronRebuild

[11:28:19] Using gulpfile ~/.cache/yay/joplin/src/joplin-2.6.10/packages/app-desktop/gulpfile.js
[11:28:19] Starting 'electronRebuild'...
Running: yarn run electron-rebuild --force-abi 89
[11:28:19] 'electronRebuild' errored after 251 ms
[11:28:19] RangeError [ERR_CHILD_PROCESS_STDIO_MAXBUFFER]: stdout maxBuffer length exceeded
    at new NodeError (node:internal/errors:371:5)
    at Socket.onChildStdout (node:child_process:459:14)
    at Socket.emit (node:events:390:28)
    at Socket.emit (node:domain:537:15)
    at addChunk (node:internal/streams/readable:324:12)
    at readableAddChunk (node:internal/streams/readable:293:11)
    at Socket.Readable.push (node:internal/streams/readable:234:10)
    at Pipe.onStreamRead (node:internal/stream_base_commons:190:23)
    at Pipe.callbackTrampoline (node:internal/async_hooks:130:17)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
==> ERROR: A failure occurred in package_joplin-desktop().
    Aborting...
 -> error making: joplin (joplin-desktop)

meyznu commented on 2022-01-08 08:21 (UTC)

You may need to remove your src/ folder before using this version

What is 'src/' folder? Where should I remove it from?

So far, I get this while trying to install this package:

Error: Cannot find module 'code-point-at'
Require stack:
- /usr/lib/node_modules/npm/node_modules/node-gyp/node_modules/string-width/index.js
- /usr/lib/node_modules/npm/node_modules/node-gyp/node_modules/gauge/wide-truncate.js
- /usr/lib/node_modules/npm/node_modules/node-gyp/node_modules/gauge/render-template.js
- /usr/lib/node_modules/npm/node_modules/node-gyp/node_modules/gauge/plumbing.js
- /usr/lib/node_modules/npm/node_modules/node-gyp/node_modules/gauge/index.js
- /usr/lib/node_modules/npm/node_modules/node-gyp/node_modules/npmlog/log.js
- /usr/lib/node_modules/npm/node_modules/node-gyp/lib/node-gyp.js
- /usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js
    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15)

strubbl commented on 2022-01-06 13:45 (UTC) (edited on 2022-01-06 13:46 (UTC) by strubbl)

Is there any upstream issue to follow already?

At the moment, i cannot click into the edit window of a note to add text.

edit: sorry, i only saw your pinned comments and thought that they were the most recent ones. but below them there are newer ones.

maderios commented on 2022-01-05 18:15 (UTC)

I got error

error electron-builder@22.14.5: The engine "node" is incompatible with this module. Expected version ">=14.0.0". Got "12.22.8"
error Found incompatible module.
lerna ERR! yarn install --mutex network:42424 --non-interactive --cache /home/fre/ARCH-AUR/joplin/src/npm-cache --no-optional exited 1 in '@joplin/app-desktop'
lerna WARN complete Waiting for 3 child processes to exit. CTRL-C to exit immediately.
error Command failed with exit code 1.

Rhinoceros commented on 2022-01-04 23:31 (UTC)

Like the others, I would also have preferred to install this instead of the appimage version.

I'm sorry you feel that way @masterkorp. I actually think it's a good thing that people are posting build issues here (although I think that issues with the application itself should be posted upstream). I think maintainers should be notified of build issues, even if the commenter is incapable of providing the solution.

However, if you feel unable to fix this package, then perhaps you could post upstream or in the Arch forum for help? If the PKGBUILD is broken, I would certainly not want to discourage people from posting here.

(Also, I noticed that you maintain three other packages, all of which have been flagged as out of date. One is 2 months out of date, and another is 14 months! The last should probably be deleted. No offence, but if you do feel overwhelmed by maintaining packages in general, perhaps it would be a good idea to disown them.)

jost21 commented on 2022-01-04 16:23 (UTC)

@masterkorp I understand your frustration. I hope you continue maintaining the package and I really appreciate the work and time you put into this. I prefer this over flatpak, AppImage etc. and also having the CLI client.

Darkmind2007 commented on 2022-01-04 14:43 (UTC)

To be honest, even though the AppImage provides a solution (I haven't tried it, just following the other comments), I must say that I'd personally consider it as the last resort.

My preference would be to have as little AppImage apps on my PC as possible, only for products that are too difficult to integrate with the system. Otherwise app management becomes too much MacOS style, which doesn't seem like Arch way of doing things.

Just to be clear, I didn't mean to complain about the package quality leaving the comment with the error message. It was just to provide some debug data or in case someone else has already faced the same problem.

I'd be happy to help if I had more experience with electron and JS.

masterkorp commented on 2022-01-04 14:15 (UTC) (edited on 2022-01-04 14:16 (UTC) by masterkorp)

@madjoe I only follow stable branches too, this is the cost of properly packaging stuff. That package is there if anyone needs it, but it does not provide the joppin cli client.

I honestly just want to disown this package, with some many people just demanding that stuff works out of the box, but they do not provide or help with any helpfull solution.

madjoe commented on 2022-01-04 11:48 (UTC)

@Rhinoceros: Too many issues with this package. I agree, joplin-appimage simply works and besides, it only follows stable branches, which is a plus.

Rhinoceros commented on 2022-01-03 22:29 (UTC) (edited on 2022-01-03 22:30 (UTC) by Rhinoceros)

For anyone else unable to build this package, joplin-appimage works well as a replacement to joplin-desktop.

madjoe commented on 2022-01-02 19:16 (UTC) (edited on 2022-01-02 19:18 (UTC) by madjoe)

I updated to the most recent version and it seems that the internal editor doesn't work for both: existing notes and new ones. It seems like a known issue:

https://github.com/alfredopalhares/arch-pkgbuilds/issues/102

simona commented on 2022-01-02 07:22 (UTC) (edited on 2022-01-02 07:25 (UTC) by simona)

error /home/simona/.cache/yay/joplin/src/joplin-2.6.10/packages/tools/node_modules/sharp: Command failed.
Exit code: 7
Command: (node install/libvips && node install/dll-copy && prebuild-install --runtime=napi) || (node-gyp rebuild && node install/dll-copy)
Arguments:
Directory: /home/simona/.cache/yay/joplin/src/joplin-2.6.10/packages/tools/node_modules/sharp
Output:
info sharp Detected globally-installed libvips v8.12.1
info sharp Building from source via node-gyp
gyp info it worked if it ends with ok
gyp info using node-gyp@7.1.2
gyp info using node@17.3.0 | linux | x64
gyp info find Python using Python version 3.10.1 found at "/usr/bin/python3"
gyp ERR! UNCAUGHT EXCEPTION
gyp ERR! stack Error: Cannot find module 'request'
gyp ERR! stack Require stack:
gyp ERR! stack - /usr/lib/node_modules/npm/node_modules/node-gyp/lib/install.js
gyp ERR! stack - /usr/lib/node_modules/npm/node_modules/node-gyp/lib/node-gyp.js
gyp ERR! stack - /usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js
gyp ERR! stack at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15)
gyp ERR! stack at Function.Module._load (node:internal/modules/cjs/loader:778:27)
gyp ERR! stack at Module.require (node:internal/modules/cjs/loader:999:19)
gyp ERR! stack at require (node:internal/modules/cjs/helpers:102:18)
gyp ERR! stack at Object.<anonymous> (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/install.js:10:17)
gyp ERR! stack at Module._compile (node:internal/modules/cjs/loader:1097:14)
gyp ERR! stack at Object.Module._extensions..js (node:internal/modules/cjs/loader:1149:10)
gyp ERR! stack at Module.load (node:internal/modules/cjs/loader:975:32)
gyp ERR! stack at Function.Module._load (node:internal/modules/cjs/loader:822:12)
gyp ERR! stack at Module.require (node:internal/modules/cjs/loader:999:19) gyp ERR! System Linux 5.15.12-1-ck-generic-v3
gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /home/simona/.cache/yay/joplin/src/joplin-2.6.10/packages/tools/node_modules/sharp
gyp ERR! node -v v17.3.0
gyp ERR! node-gyp -v v7.1.2
gyp ERR! Node-gyp failed to build your package.
gyp ERR! Try to update npm and/or node-gyp and if it does not help file an issue with the package author.

lerna ERR! yarn install --mutex network:42424 --non-interactive --cache /home/simona/.cache/yay/joplin/src/npm-cache --no-optional exited 7 in '@joplin/tools'

Rhinoceros commented on 2022-01-01 23:44 (UTC)

Slightly different problem perhaps, but I also can't build as per this GitHub issue.

Darkmind2007 commented on 2022-01-01 13:53 (UTC)

The build fails with the following message (even after answering "yes" to all questions). Has anyone experienced this?

Error: Cannot find module './tools/copyApplicationAssets.js'
Require stack:
- /home/user/.cache/pacaur/joplin/src/joplin-2.6.10/packages/app-desktop/gulpfile.js
- /home/user/.cache/pacaur/joplin/src/joplin-2.6.10/packages/app-desktop/node_modules/gulp-cli/lib/shared/require-or-import.js
- /home/user/.cache/pacaur/joplin/src/joplin-2.6.10/packages/app-desktop/node_modules/gulp-cli/lib/versioned/^4.0.0/index.js
- /home/user/.cache/pacaur/joplin/src/joplin-2.6.10/packages/app-desktop/node_modules/gulp-cli/index.js
- /home/user/.cache/pacaur/joplin/src/joplin-2.6.10/packages/app-desktop/node_modules/gulp/bin/gulp.js
    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15)
    at Function.Module._load (node:internal/modules/cjs/loader:778:27)
    at Module.require (node:internal/modules/cjs/loader:999:19)
    at require (node:internal/modules/cjs/helpers:102:18)
    at Object.<anonymous> (/home/user/.cache/pacaur/joplin/src/joplin-2.6.10/packages/app-desktop/gulpfile.js:19:7)
    at Module._compile (node:internal/modules/cjs/loader:1097:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1149:10)
    at Module.load (node:internal/modules/cjs/loader:975:32)
    at Function.Module._load (node:internal/modules/cjs/loader:822:12)
    at Module.require (node:internal/modules/cjs/loader:999:19) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
    '/home/user/.cache/pacaur/joplin/src/joplin-2.6.10/packages/app-desktop/gulpfile.js',
    '/home/user/.cache/pacaur/joplin/src/joplin-2.6.10/packages/app-desktop/node_modules/gulp-cli/lib/shared/require-or-import.js',
    '/home/user/.cache/pacaur/joplin/src/joplin-2.6.10/packages/app-desktop/node_modules/gulp-cli/lib/versioned/^4.0.0/index.js',
    '/home/user/.cache/pacaur/joplin/src/joplin-2.6.10/packages/app-desktop/node_modules/gulp-cli/index.js',
    '/home/user/.cache/pacaur/joplin/src/joplin-2.6.10/packages/app-desktop/node_modules/gulp/bin/gulp.js'
  ]
}
lerna info lifecycle @joplin/app-desktop@2.6.10~postinstall: Failed to exec postinstall script
lerna ERR! lifecycle "postinstall" errored in "@joplin/app-desktop", exiting 1

waldher commented on 2021-12-29 08:50 (UTC)

Fixes for missing npm dependency and for the patch issue (yarn.lock was duplicated in one of the patch files):

https://gitlab.com/waldher/joplin/-/commit/5ce1a02f0afa3af8a6b054bc24f92d596b9d18ea

snack commented on 2021-12-28 08:28 (UTC) (edited on 2021-12-28 10:57 (UTC) by snack)

Just updated to 2.6.10-4. The note editor seems to be badly broken: it shows no text for some notes (which however are correctly displayed) while for others the source markdown is displayed and I can edit it, but the cursor is not visible.

Edit: the empty editor issue happens only when the window is resized below a certain dimension. For bigger or full-screen windows the content is displayed but the cursor is still missing.

Edit2:: I just installed joplin-appimage 2.6.10-1 and it works perfectly, so probably there are still issues with the build configuration of this package.

zangoku commented on 2021-12-28 08:28 (UTC)

update fails for me lerna ERR! yarn install --mutex network:42424 --non-interactive --cache /home/zangoku/.cache/paru/clone/joplin/src/npm-cache --no-optional exited 1 in '@joplin/lib' lerna WARN complete Waiting for 8 child processes to exit. CTRL-C to exit immediately. error Command failed with exit code 1. info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command. ==> ERROR: A failure occurred in build(). Aborting... error: failed to build 'joplin-2.6.10-4 (joplin-desktop)':

masterkorp commented on 2021-12-27 14:00 (UTC)

@linuxyz and @simona Update your system first node-gyp was just released to the repositories.

linuxyz commented on 2021-12-27 13:52 (UTC)

Same here with this "node-gyp" dependency missing:

:: error: Can't resolve dependencies for AUR package 'joplin-desktop': Version mismatch: joplin-desktop depends on: 'node-gyp>=8.4.1' found in 'PackageSource.REPO': '8.3.0-1'

simona commented on 2021-12-27 13:20 (UTC)

gyp ERR! cwd /home/simona/.cache/yay/joplin/src/joplin-2.6.10/packages/app-cli/node_modules/sharp
gyp ERR! node -v v17.3.0
gyp ERR! node-gyp -v v7.1.2
gyp ERR! Node-gyp failed to build your package.
gyp ERR! Try to update npm and/or node-gyp and if it does not help file an issue with the package author.

masterkorp commented on 2021-12-27 11:30 (UTC) (edited on 2021-12-27 11:32 (UTC) by masterkorp)

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

maderios commented on 2021-12-17 16:10 (UTC)

Latest is 2.6.9 https://github.com/laurent22/joplin/releases/

okmr commented on 2021-11-26 20:06 (UTC) (edited on 2021-11-26 20:09 (UTC) by okmr)

Update to 2.5.12 (only desktop-version):

  • Edit PKGBUILD:

# Maintainer: Alfredo Palhares <alfredo at palhares dot me>
# Contributor: Mark Wagie <mark dot wagie at tutanota dot com>
# Contributor:  Matteo Parolari
# Contributor: gardar <aur@gardar.net>

# Please contribute to:
# https://github.com/alfredopalhares/arch-pkgbuilds

pkgbase="joplin"
pkgname=('joplin-desktop')
pkgver=2.5.12
groups=('joplin')
pkgrel=1
install="joplin.install"
depends=('electron' 'gtk3' 'libexif' 'libgsf' 'libjpeg-turbo' 'libwebp' 'libxss' 'nodejs'
         'nss' 'orc' 'rsync' )
optdepends=('libappindicator-gtk3: for tray icon')
arch=('x86_64' 'i686')
makedepends=('git' 'npm' 'python2' 'rsync' 'jq' 'electron')
url="https://joplinapp.org/"
license=('MIT')
source=("joplin.desktop" "joplin-desktop.sh" "joplin.sh"
        "joplin-${pkgver}.tar.gz::https://github.com/laurent22/joplin/archive/v${pkgver}.tar.gz")
sha256sums=('c7c5d8b0ff9edb810ed901ea21352c9830bfa286f3c18b1292deca5b2f8febd2'
            'a450284fe66d89aa463d129ce8fff3a0a1a783a64209e4227ee47449d5737be8'
            'dc1236767ee055ea1d61f10e5266a23e70f3e611b405fe713ed24ca18ee9eeb5'
            '984c6300e8d30f2a935084fa5b583ec59708041ee886a98e3add7ca75b46f424')


# local npm cache directory
_npm_cache="npm-cache"

_get_cache() {
  if [[ "${_npm_cache}" =~ ^/ ]]; then
    printf "%s" "${_npm_cache}"
  else
    printf "%s" "${srcdir}/${_npm_cache}"
  fi
}

prepare() {
  local cache=$(_get_cache)
  msg2 "npm cache directory: $cache"

  msg2 "Disabling husky (git hooks)"
  sed -i '/"husky": ".*"/d' "${srcdir}/joplin-${pkgver}/package.json"

  msg2 "Tweaking lerna.json"
  local tmp_json="$(mktemp --tmpdir="$srcdir")"
  local lerna_json="${srcdir}/joplin-${pkgver}/lerna.json"
  # TODO: Add check for lerna.json file
  jq ".packages = [
        \"packages/app-desktop\",
        \"packages/fork-htmlparser2\", \"packages/fork-sax\",
        \"packages/lib\", \"packages/renderer\", \"packages/tools\",
        \"packages/turndown\", \"packages/turndown-plugin-gfm\"
        ] |
      . += {\"npmClient\": \"npm\", \"npmClientArgs\": [\"--cache $cache\"]}" \
    "$lerna_json" > "$tmp_json"
  cat "$tmp_json" > "$lerna_json"
  rm "$tmp_json"
}


build() {
  local cache=$(_get_cache)
  msg2 "npm cache directory: $cache"
  cd "${srcdir}/joplin-${pkgver}"

  # Force Lang
  # INFO: https://github.com/alfredopalhares/joplin-pkgbuild/issues/25
  export LANG=en_US.utf8

  msg2 "Installing dependencies through Lerna"
  npm install --cache "$cache"

}

#FIXME: These checks fail on some machines, even with the exit 0
# Something related with the number of allowed processes I guess
check() {
  cd "${srcdir}/joplin-${pkgver}"
  msg2 "Not Running any tests for now"
  #npm run test || exit 0
}



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'
         'nss' 'orc')
  optdepends=('libappindicator-gtk3: for tray icon')
  conflicts=('joplin-desktop-electron')

  # ./generateSha512.js fails if AppImage is not built
  mkdir -p "${srcdir}/joplin-${pkgver}/packages/app-desktop/dist/"
  touch "${srcdir}/joplin-${pkgver}/packages/app-desktop/dist/AppImage"

  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)
  msg2 "Using Electron Version ${electron_version}"
  # Current version of electron does not work
  USE_HARD_LINKS=false npm run dist -- --publish=never  --linux  --x64 \
    --dir="dist/"
    #--dir="dist/" -c.electronDist=$electron_dir -c.electronVersion=$electron_version

  # TODO: Cleanup app.asar file
  cd dist/linux-unpacked/
  cp -R "." "${pkgdir}/usr/share/joplin-desktop"

  msg2 "Installing LICENSE..."
  cd "${srcdir}/joplin-${pkgver}/"
  install -Dm644 LICENSE -t "${pkgdir}/usr/share/licenses/${pkgname}"

  msg2 "Installing startup script and desktop file..."
  cd "${srcdir}"
  install -Dm755 ${srcdir}/joplin-desktop.sh "${pkgdir}/usr/bin/joplin-desktop"
  install -Dm644 ${srcdir}/joplin.desktop -t "${pkgdir}/usr/share/applications"

  msg2 "Installing icons"
  local -r src_icon_dir="${srcdir}/joplin-${pkgver}/packages/app-desktop/build/icons"
  local -i size
  for size in 16 22 24 32 36 48 64 72 96 128 192 256 512; do
    [[ -f "${src_icon_dir}/${size}x${size}.png" ]] &&
      install -Dm644 \
        "${src_icon_dir}/${size}x${size}.png" \
        "${pkgdir}/usr/share/icons/hicolor/${size}x${size}/apps/joplin.png"
  done
}

maderios commented on 2021-11-20 12:02 (UTC)

From 12 days ago, latest stable release is 2.5.12 https://github.com/laurent22/joplin/releases/

evang commented on 2021-11-18 02:34 (UTC)

PKGBUILD seems to be missing the libgsf package which is required for build

benm commented on 2021-11-09 14:26 (UTC)

Is there a reason this has not yet been updated to 2.5.xx yet? There is a major bug fix for this version regarding TLS certificates.

maderios commented on 2021-11-08 13:01 (UTC)

@luz
Update PKGBUILD
Edit the file PKGBUILD and make necessary changes, i.e. bumping the version number.

Update checksums in the PKGBUILD file
updpkgsums

Update .SRCINFO file
makepkg --printsrcinfo > .SRCINFO

luz1 commented on 2021-11-08 12:50 (UTC)

Please update. The issue with the expired Let's encrypt certificate should be resolved in the latest version.

For those with the error: A current workaround is to set 'ignore TLS errors' in the settings.

maderios commented on 2021-10-18 09:38 (UTC)

Latest release is 2.4.12 (not 2.5.1)

gyurman commented on 2021-10-09 17:25 (UTC)

Not build for aarch64

madjoe commented on 2021-10-04 19:06 (UTC)

==> ERROR: PKGBUILD does not exist.

duckunix commented on 2021-09-30 12:13 (UTC) (edited on 2021-09-30 12:13 (UTC) by duckunix)

Diff to update to 2.4.9. Very light testing has been good so far.

diff --git a/PKGBUILD b/PKGBUILD
index 711d453..9cbc60d 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -8,7 +8,7 @@

 pkgbase="joplin"
 pkgname=('joplin' 'joplin-desktop')
-pkgver=2.3.5
+pkgver=2.4.9
 groups=('joplin')
 pkgrel=1
 install="joplin.install"
@@ -24,7 +24,7 @@ source=("joplin.desktop" "joplin-desktop.sh" "joplin.sh"
 sha256sums=('c7c5d8b0ff9edb810ed901ea21352c9830bfa286f3c18b1292deca5b2f8febd2'
             'a450284fe66d89aa463d129ce8fff3a0a1a783a64209e4227ee47449d5737be8'
             'dc1236767ee055ea1d61f10e5266a23e70f3e611b405fe713ed24ca18ee9eeb5'
-            '8d2b819940d0f22ac5dfda256508ef17b2e662a66cd31d25596af15d6cf59103')
+            'bdf672a43a89925a4b019177915c67bd8c24f574effa3251f12021baa25a8d2d')


 # local npm cache directory

gyurman commented on 2021-09-27 18:41 (UTC)

How can I install this for aarch64 proot? Please help me!

madjoe commented on 2021-08-31 11:02 (UTC)

The installation/update stuck for hours at:

install dependencies: verb installed leaf @joplin/app-desktop

maderios commented on 2021-08-20 09:41 (UTC)

To ensure the integrity of packages, make sure that the integrity variables contain correct values. These can be updated using the updpkgsums tool

PKGBUILD Integrity

luisnabais commented on 2021-08-19 17:15 (UTC)

For those who don't know how to update while the maintainer can't do it, just download the PKGBUILD file to a folder for the purpose, edit the file and change the version to 2.3.5, which downloads Joplin 2.3.5. Then run sha256sum <file> to get the sha256sum. Then edit PKGBUILD again and change the last sha256sum to the one from the last command and just run makepkg -i on the same folder as the PKGBUILD file.

Zesko commented on 2021-08-16 15:54 (UTC)

It is old because it is not compatible with sync in android. There is the current version 2.3.3 of Joplin-desktop. Please update it, thank you!

nirnakinho commented on 2021-08-15 18:11 (UTC)

Running the latest 2.2.7 gets me the following error:

/usr/bin/joplin-desktop: line 12:  7782 Trace/breakpoint trap   (core dumped) ./@joplinapp-desktop "$@"

The appimage variant runs without problems, though.

Rhinoceros commented on 2021-07-28 23:18 (UTC)

@ajgraves Looks like zebdo bumped to 2.2.1, but this is only a pre-release. Presumably that's why someone else reverted it.

maderios commented on 2021-07-28 18:55 (UTC)

@SandWarrior67 To avoid unneeded errors, don't use "Yay" or any Aur helper

moonaru commented on 2021-07-28 18:01 (UTC)

I have a strange problem with Electron. Error log: https://hastebin.com/redufuvila.typescript

ajgraves commented on 2021-07-28 15:42 (UTC)

I'm curious why this package was bumped to the 2.2 level but then dropped back down to the 2.1 line. I have the 2.2.1 update installed but don't want to downgrade just to keep the AUR package in line.

maderios commented on 2021-07-25 10:12 (UTC)

@alpha619 Manjaro is not Arch, packages are different. If you want to install Arch Aur package, install Arch first. It's easier now with new installer https://wiki.archlinux.org/title/Archinstall

alpha619 commented on 2021-07-25 09:59 (UTC) (edited on 2021-07-25 10:04 (UTC) by alpha619)

Cannot update on manjaro, always get "npm ERR! code ECONNRESET" or "npm ERR! code ERR_SOCKET_TIMEOUT" error.

XTREEMRAGE commented on 2021-07-20 19:13 (UTC)

@maderios Thanks for helping me out, that worked! I need to update my notes about this, never needed it :).

maderios commented on 2021-07-20 17:20 (UTC)

@XTREEMRAGE This happens when you don't update git repo or/and a previous package version is still present in your directory. Don't use any Aur any "helper", just do 'makepkg -sicC'

XTREEMRAGE commented on 2021-07-20 17:12 (UTC)

Somehow when I update this (v2.1.8-1), it still install v2.1.7... :| Anyone else have this issue?

Kido commented on 2021-07-20 06:29 (UTC)

Package still shows it's version as 2.1.8-1 in AUR. Check if you've updated .SRCINFO

maderios commented on 2021-07-19 11:46 (UTC)

Thanks for this update. It works fine.

soorajsp commented on 2021-07-13 16:42 (UTC)

Everytime I can't update as it throwws a new npm update. New minor version of npm available! 7.17.0 -> 7.19.1 Currently I'm in 1.8.7, then couldn't update to 2.0 as it said npm 6.xx - 7.xx was available.

anyway I could bypass this & install.

maderios commented on 2021-07-11 14:53 (UTC)

@mke21 Look here https://bbs.archlinux.org/viewtopic.php?id=130309
``` These boards are for the support of Arch Linux, and Arch ONLY If you have installed Archbang, Antergos, Chakra, Evo/Lution, Manjaro, Whatever, you are NOT running Arch Linux.

mke21 commented on 2021-07-11 14:10 (UTC)

Cannot update on Manjaro, I get an error 'PKGBUILD not exitst'

maderios commented on 2021-07-10 15:19 (UTC)

2.2.1 is out https://github.com/laurent22/joplin/releases/tag/v2.2.1

hazelnot commented on 2021-07-07 12:19 (UTC)

I don't care, stop being so condescending towards other people's preferences :^)

maderios commented on 2021-07-07 12:18 (UTC)

@hazelnot Aur helpers, "it's easier" but they cause build issues... :)

hazelnot commented on 2021-07-07 11:47 (UTC)

yay and pamac are AUR helpers, lots of people use them cause it's easier and it makes the AUR packages auto-update

maderios commented on 2021-07-06 21:36 (UTC)

What is "yay" and "pamac"? To compile and install Joplin, i just use 'makepkg -SicC'. It works fine now.

parsanoori commented on 2021-07-06 20:17 (UTC)

Got npm stuck for 4 hours at the state below while installing it via yay:

install dependencies: verb installed leaf @joplin/app-desktop

parsanoori commented on 2021-07-06 17:32 (UTC)

Got this while building using pamac:

npm ERR! code 1
npm ERR! path /var/cache/private/pamac/joplin/src/joplin-2.1.7/packages/app-cli/node_modules/keytar
npm ERR! command failed
npm ERR! command sh -c prebuild-install || node-gyp rebuild
npm ERR! gyp info it worked if it ends with ok
npm ERR! gyp info using node-gyp@5.1.1
npm ERR! gyp info using node@16.3.0 | linux | x64
npm ERR! gyp info find Python using Python version 3.9.5 found at "/usr/bin/python"
npm ERR! gyp WARN install got an error, rolling back install
npm ERR! gyp ERR! configure error 
npm ERR! gyp ERR! stack Error: EROFS: read-only file system, mkdir '/.cache'
npm ERR! gyp ERR! System Linux 5.4.124-1-MANJARO
npm ERR! gyp ERR! command "/usr/bin/node" "/var/cache/private/pamac/joplin/src/joplin-2.1.7/node_modules/.bin/node-gyp" "rebuild"
npm ERR! gyp ERR! cwd /var/cache/private/pamac/joplin/src/joplin-2.1.7/packages/app-cli/node_modules/keytar
npm ERR! gyp ERR! node -v v16.3.0
npm ERR! gyp ERR! node-gyp -v v5.1.1
npm ERR! gyp ERR! not ok

boredpanda commented on 2021-07-03 14:20 (UTC) (edited on 2021-07-03 14:20 (UTC) by boredpanda)

Note that there is a bug in 2.1.7 causing the desktop client to sync endlessly if you enable sharing (when used with Joplin server). Bug #5133 on Github. https://github.com/laurent22/joplin/issues/5133 This is fixed in 2.1.8.

Neural_oD commented on 2021-06-30 09:03 (UTC)

Hi. @masterkorp - just checking in on when you're likely to update to the latest version: 2.1.7 - seems to be the latest now as per 4 days ago.

Usually there's no issue in waiting, however, I've had some issues crop up, and the suggestions have been to upgrade to the 2.1.x version.

Thanks for your effort in this, you maintainers rock!

peeweep commented on 2021-06-25 01:41 (UTC)

@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

modnoob commented on 2021-06-18 12:43 (UTC)

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)

masterkorp commented on 2021-06-14 09:27 (UTC)

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

txtsd commented on 2021-06-07 17:33 (UTC)

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

maderios commented on 2021-06-07 17:25 (UTC)

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

txtsd commented on 2021-06-07 08:51 (UTC)

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)

Aperculum commented on 2021-06-07 06:40 (UTC)

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.

zangoku commented on 2021-06-02 14:26 (UTC)

npm ERR! semver.simplifyRange is not a function

maderios commented on 2021-05-30 15:59 (UTC)

joplin-beta 2.0.2-1 compiles successfully today

michaldybczak commented on 2021-05-27 21:48 (UTC) (edited on 2021-05-27 21:49 (UTC) by michaldybczak)

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.

duckunix commented on 2021-05-25 12:40 (UTC) (edited on 2021-05-26 11:18 (UTC) by duckunix)

Actually, sync is not working in this version for me, both CLI & GUI.

Update to 1.8.5 is straight forward:

diff --git a/PKGBUILD b/PKGBUILD
index 47e5a4e..a4e4c60 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -7,7 +7,7 @@

 pkgbase="joplin"
 pkgname=('joplin' 'joplin-desktop')
-pkgver=1.7.11
+pkgver=1.8.5
 groups=('joplin')
 pkgrel=4
 install="joplin.install"
@@ -23,7 +23,7 @@ source=("joplin.desktop" "joplin-desktop.sh" "joplin.sh"
 sha256sums=('c7c5d8b0ff9edb810ed901ea21352c9830bfa286f3c18b1292deca5b2f8febd2'
             'a450284fe66d89aa463d129ce8fff3a0a1a783a64209e4227ee47449d5737be8'
             'dc1236767ee055ea1d61f10e5266a23e70f3e611b405fe713ed24ca18ee9eeb5'
-            '06fccd715cddb15e0b8ada3a44e196fc8a4b1ad4e3fec466f872f92295f5733b')
+            '9cf1072ef603383eac3f73bd6ba9cd0ef7a05c00b61b797b21659ee6f8b7e0a4')

 # local npm cache directory
 _npm_cache="npm-cache"

madjoe commented on 2021-05-01 05:19 (UTC)

$ joplin-desktop 
./@joplinapp-desktop: error while loading shared libraries: libicui18n.so.68: cannot open shared object file: No such file or directory
$ pacman -F libicui18n.so
core/icu 67.1-1 [installed: 69.1-1]
usr/lib/libicui18n.so

Also, during the update 1.7.11-2 -> 1.7.11-4:

npm ERR! semver.simplifyRange is not a function
$ npm -v
7.11.1
$ semver -h
SemVer 7.3.5

radio_rogal commented on 2021-04-30 19:11 (UTC) (edited on 2021-04-30 19:13 (UTC) by radio_rogal)

==> WARNING: Package contains reference to $srcdir
usr/share/joplin-desktop/resources/app.asar

And pacman -Ql shows

joplin-desktop /usr/share/joplin-desktop/resources.pak
joplin-desktop /usr/share/joplin-desktop/resources/
joplin-desktop /usr/share/joplin-desktop/resources/app.asar
joplin-desktop /usr/share/joplin-desktop/resources/app.asar.unpacked/
joplin-desktop /usr/share/joplin-desktop/resources/app.asar.unpacked/node_modules/
joplin-desktop /usr/share/joplin-desktop/resources/app.asar.unpacked/node_modules/7zip-bin-linux/
joplin-desktop /usr/share/joplin-desktop/resources/app.asar.unpacked/node_modules/7zip-bin-linux/arm/
joplin-desktop /usr/share/joplin-desktop/resources/app.asar.unpacked/node_modules/7zip-bin-linux/arm/7za

nirnakinho commented on 2021-04-20 18:49 (UTC) (edited on 2021-04-20 18:57 (UTC) by nirnakinho)

Edit: I am getting the same build error as mentioned in issue https://github.com/alfredopalhares/arch-pkgbuilds/issues/81 (No need to do a big error log paste, when its in the gh issue already)

hazelnot commented on 2021-04-20 09:21 (UTC) (edited on 2021-04-20 10:29 (UTC) by hazelnot)

Can confirm that this doesn't work anymore because icu was updated to 69.1, and Joplin is looking for 68.x

Edit: re-building the package fixed the error, although now I'm just getting a blank white screen.

Edit: thanks for being so quick with the update! Everything works now.

jcomellas commented on 2021-04-19 14:54 (UTC)

@Frogboy To get Joplin working again you need to modify the PKGBUILD file to use the electron11 package as a dependency instead of electron as I suggested in the comment below yours. Check the diff at the end of my comment.

If you apply those changes and run makepkg -si you will end up with a working application.

Frogboy commented on 2021-04-19 14:46 (UTC)

No longer works after upgrading Electron, even after rebuilding. This porbably needs to be updated as well.

jcomellas commented on 2021-04-19 01:24 (UTC)

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

welovelain commented on 2021-04-18 21:48 (UTC)

➜ 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?

txtsd commented on 2021-04-18 07:20 (UTC)

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)

galvez_65 commented on 2021-04-17 15:25 (UTC)

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?

loki7990 commented on 2021-04-05 17:50 (UTC)

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

ocelotsloth commented on 2021-04-04 23:21 (UTC) (edited on 2021-04-04 23:21 (UTC) by ocelotsloth)

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.

trumee commented on 2021-04-02 14:47 (UTC) (edited on 2021-04-02 14:48 (UTC) by trumee)

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

masterkorp commented on 2021-04-01 15:37 (UTC)

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.

duckunix commented on 2021-03-30 20:08 (UTC)

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

haven commented on 2021-03-30 19:58 (UTC)

I'm also getting this npm related error. Please suggest how to proceed.

duckunix commented on 2021-03-30 11:07 (UTC)

@dwsong07 Good call. I missed the status.

dwsong07 commented on 2021-03-30 04:23 (UTC)

v1.8.1 is a pre-release not a stable release. I guess it should be unflagged.

duckunix commented on 2021-03-29 23:05 (UTC) (edited on 2021-03-29 23:05 (UTC) by duckunix)

Trying to build on v1.8.1, I get:

npm ERR! code EAI_AGAIN                                  
npm ERR! syscall getaddrinfo               
npm ERR! errno EAI_AGAIN                                
npm ERR! request to https://registry.npmjs.org/jsonparse/-/jsonparse-1.3.1.tgz failed, reason: getaddrinfo EAI_AGAIN registry.npmjs.org

duckunix commented on 2021-03-29 18:43 (UTC) (edited on 2021-03-29 18:44 (UTC) by duckunix)

Builds today are failing with:

npm ERR! code EAI_AGAIN
npm ERR! syscall getaddrinfo
npm ERR! errno EAI_AGAIN
npm ERR! request to https://registry.npmjs.org/jsx-ast-utils/-/jsx-ast-utils-3.1.0.tgz failed, reason: getaddrinfo EAI_AGAIN registry.npmjs.org

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

Eothred commented on 2021-03-24 08:49 (UTC)

For dependencies, I think you should define that at least version 12 is required for nodejs. I had nodejs-lts-dubnium installed, which made the terminal app crash on some functions.

Alukard commented on 2021-03-23 08:59 (UTC)

@joshsteele21 @masterkorp same issue with me, couldn't install using yay -S package_name. getting the same lerna error on every run.

but weirdly it get installed without any error on running makepkg -si in joplin directory in cache of yay.

jost21 commented on 2021-03-11 18:59 (UTC) (edited on 2021-03-11 19:00 (UTC) by jost21)

@masterkorp

I tried it probable 20+ times over the last 3 days. I tried deactivating my host file and I'm able to download the mentioned file manually.

lerna ERR! npm install --cache /var/tmp/pamac-build-***/joplin/src/npm-cache exited 1 in '@joplin/fork-sax'
lerna ERR! npm install --cache /var/tmp/pamac-build-***/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/resolve-from/-/resolve-from-1.0.1.tgz failed, reason: Socket timeout

This is the error with turndown

lerna ERR! npm install --cache /var/tmp/pamac-build-***/joplin/src/npm-cache exited 1 in '@joplin/turndown'
lerna ERR! npm install --cache /var/tmp/pamac-build-***/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/jsx-ast-utils/-/jsx-ast-utils-1.4.1.tgz failed, reason: Socket timeout

The build process always aborts at fork-sax or turndown

Is it possible that it is a problem with the npm installation/config?

masterkorp commented on 2021-03-10 10:17 (UTC)

@joshsteele21

That is a network error from NPN, I have no control over that. What happens if you retry ?

jost21 commented on 2021-03-09 18:33 (UTC)

Keep getting errors during installation:

lerna ERR! npm install --cache /home/***/.cache/yay/joplin/src/npm-cache exited 1 in '@joplin/fork-sax'
lerna ERR! npm install --cache /home/***/.cache/yay/joplin/src/npm-cache stderr:
npm ERR! code ERR_SOCKET_TIMEOUT

or sometimes a similar error with @joplin/turndown (I cannot reproduce it at the moment, therefore I cannot paste the exact error message. But I saw that error more than once during my attempts.)

I tried installing it with yay and the Manjaro GUI. The installation works, when I install it with the Joplin install script (wget -O - https://raw.githubusercontent.com/laurent22/joplin/dev/Joplin_install_and_update.sh | bash).

djipey commented on 2021-03-05 18:18 (UTC)

As mentioned before, at least libgsf is missing. Manually installing this dependency solved the problem for me.

floppy5.25 commented on 2021-03-04 21:16 (UTC) (edited on 2021-03-04 21:17 (UTC) by floppy5.25)

It will not build for me unless I install python2. Filed bug on github

masterkorp commented on 2021-02-23 10:29 (UTC)

@pur2evil,

In that case you can just edit the packagebuild and remove these 2

pur2evil commented on 2021-02-22 18:36 (UTC)

@masterkorp I was trying to install it with 'yay -S joplin' and failed.
Do note that I had not installed joplin-desktop before it.
Maybe joplin need those dependencies too?

masterkorp commented on 2021-02-22 11:09 (UTC)

@pur2evil ?

There are many cli clients? Do you mean makepkg ?

pur2evil commented on 2021-02-19 07:07 (UTC)

@masterkorp The CLI one.

masterkorp commented on 2021-02-18 17:08 (UTC)

@pur2evil

What client are you using ?

pur2evil commented on 2021-02-18 12:45 (UTC)

@masterkorp joplin-1.7.11-2 ==> Missing dependencies: -> libexif -> libgsf ==> Checking buildtime dependencies... ==> ERROR: Could not resolve all dependencies. error making: joplin

sunerpy commented on 2021-01-19 01:56 (UTC) (edited on 2021-01-19 07:02 (UTC) by sunerpy)

Hello,there is a sync error with version 1.6.7. When I open the application of joplin-desktop,something named "fetched items " will occur in the left lower corner. Although I have only 300 notes, the "fetched items" process can be going on always! I have waited it when the number was 10000+ but it was still going on .

Sorry, I had found the reason above. In the directory which named ".config", I found some directories just like "joplin" "Joplin" "@joplin" and etc. When I delete them all and then reset the sync method of joplin, it works normal.

professed commented on 2021-01-01 17:04 (UTC)

Thank you, @taken. Confirming that the following works:

yay -S --rebuild joplin-desktop

lucianf commented on 2020-12-31 22:58 (UTC)

here is the result of pacman -Ql joplin-desktop (I hope! because I haven't used pastebin before)!

https://pastebin.com/fta5ixhp

taken commented on 2020-12-31 21:00 (UTC) (edited on 2020-12-31 21:01 (UTC) by taken)

@lucianf I had the same error when upgrading to 1.5.14-1. The error was resolved following a rebuild of the package:

yay -S --rebuild joplin-desktop

masterkorp commented on 2020-12-31 19:05 (UTC)

@lucianf Can you paste the pacman -Ql joplin-desktop, do a pastebin please

lucianf commented on 2020-12-30 13:25 (UTC)

man I don't know what is happening, but after all these changes to this package, I have removed what I had installed on my system, then did a yay -S joplin-desktop and I still get this error when I try to run it:

$ joplin-desktop 
/usr/bin/joplin-desktop: line 12: ./@joplinapp-desktop: No such file or directory

Only the appimage works for me and that take quite a bit to load.

paro commented on 2020-12-30 12:45 (UTC)

@masterkorp From my own experience with other packages, trying to compile different packages with different dependencies in a single pkgbuild brings to only more problems. Anyway, cli version is shipped by joplin authors with different version numbers, so having two different pkgbuild is really the only solution.

masterkorp commented on 2020-12-30 12:28 (UTC)

@mprom, this is a limitation of the makepkg, you cant just built one packaege,

Edit the pkgname array, and remove the joplin-desktop that will work.

I am trying to do a workaround without having to create 2 separate packages. But I guess making a repository its the only response.

paro commented on 2020-12-30 12:16 (UTC)

@mprom Unfortunately, if you use this pkgbuild you have to "compile" both cli and desktop versions, and yes, this is very annoying for the ones who just want the cli version.

I'm splitting the pkgbuild in order to "fix" this behavior, and I will send my results to the maintainer.

mprom commented on 2020-12-30 11:43 (UTC)

Why does this package compile using Electron? Electron is a framework for developing GUI applications, and this is the CLI version.

masterkorp commented on 2020-12-29 16:14 (UTC)

Hello,

I have updated the package, to 1.5.12 The packages are now much smaller, I have also disabled the checks since I can't reproduce the error in any way. Enable them by uncommenting the line if you want. Please if you have any problems report to https://github.com/alfredopalhares/arch-pkgbuilds/issues

Hanzo commented on 2020-12-28 05:42 (UTC) (edited on 2020-12-28 07:39 (UTC) by Hanzo)

@gregLTS

Confirming. Since *-14 it changed to same:

$ yay -Ss joplin

aur/joplin-beta 1.5.11-1 (+3 0.93%) The latest pre-release - open source note taking and to-do application

aur/joplin-appimage 1.5.11-1 (+16 0.89%) The latest pre-released AppImage of Joplin - a cross-platform note taking and to-do app

aur/joplin-desktop 1.4.19-14 (+155 12.12%) A note taking and to-do application with synchronization capabilities - Desktop

aur/joplin 1.4.19-14 (+155 12.12%) (Installed: 1.4.19-12) A note taking and to-do application with synchronization capabilities - CLI App

You can see pkgdesk change on the last version https://aur.archlinux.org/cgit/aur.git/commit/?h=joplin&id=2c86bba5bb110f62689049bee0723779594c06a2

UPD:

  • Last upgrade ran without any failures.

  • After updgrade "joplin" became CLI only version and I had to install "joplin-desktop" in addition.

aur/joplin-desktop 1.4.19-14 (+155 12.10%) (Installed) A note taking and to-do application with synchronization capabilities - Desktop

aur/joplin 1.4.19-14 (+155 12.10%) (Installed) A note taking and to-do application with synchronization capabilities - CLI App

gregLTS commented on 2020-12-28 02:06 (UTC) (edited on 2020-12-28 02:25 (UTC) by gregLTS)

@Hanzo, I'm not sure where you're seeing those descriptions, but I'm getting completely different results.

A yay search gives the following description, which doesn't indicate that the package includes the desktop version:

aur/joplin 1.4.19-14 (+155 12.16) A note taking and to-do application with synchronization capabilities - CLI App

And when I check the AUR web interface (https://aur.archlinux.org/packages/?O=0&SeB=nd&K=joplin&outdated=&SB=n&SO=a&PP=50&do_Search=Go) I'm seeing the same thing:

joplin 1.4.19-14 155 12.16 Yes A note taking and to-do application with synchronization capabilities - CLI App

I can't find a combined package anywhere. I can confirm that my system is fully up-to-date.

Hanzo commented on 2020-12-27 16:05 (UTC)

@gregLTS

You need to install "joplin" and you'll have both. See description:

aur/joplin-desktop 1.4.19-13 (+155 12.27%) A note taking and to-do application with synchronization capabilities - Desktop

aur/joplin-cli 1.4.19-13 (+155 12.27%) A note taking and to-do application with synchronization capabilities - CLI App

aur/joplin 1.4.19-13 (+155 12.27%) (Installed: 1.4.19-12) A note taking and to-do application with synchronization capabilities - CLI and Desktop Version

gregLTS commented on 2020-12-27 06:05 (UTC)

@masterkorp, do you know when you're going to be renaming the packages? I want both the CLI and Desktop apps, so I tried to install both joplin and joplin-desktop, but I'm given the error that the packages conflict with each other.

Hanzo commented on 2020-12-26 21:42 (UTC) (edited on 2020-12-26 21:43 (UTC) by Hanzo)

@masterkorp

Built, as suggested, package-12 without checks (--nocheck) and suddenly arrived update-13 created just now ... Tried to install with yay and failed again with same check() issues.

If it's possible, please update us when we'll be able to update without those issues from AUR and not manually, because It's annoying to waste about half an hour just to fail in the end.

Rhinoceros commented on 2020-12-24 22:52 (UTC)

@masterkorp I appreciate that you'd prefer to use your Github page for issues, but there are some of us that prefer not to use Github for ideological or other reasons. The comments section of the AUR is really the "official" feedback area.

Also TBH it's not that hard to provide support here. Thank you for maintaining this package, but I maintain 12 times as many packages as you and find it perfectly workable, although admittedly this package does seem to have a lot of issues!

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

Rurisk commented on 2020-12-23 13:31 (UTC)

Thank you @paro

paro commented on 2020-12-23 13:21 (UTC)

I opened an issue on maintainer github (https://github.com/alfredopalhares/arch-pkgbuilds/issues/66) with various notes and comments. I'm fixing the pkgbuild and willing to share my solution if maintainer doesn't show up. For the time being, I'd suggest to simply compile the packages with makepkg and then install the joplin package alone (with pacman -U).

Rurisk commented on 2020-12-23 12:00 (UTC)

Hi all, I'm having problems with the current build I don't understand, hoping for some help. I first tried to update a few days ago and I got this error message:


joplin on  master [?]
➜  makepkg -si
==> WARNING: The package group has already been built, installing existing packages...
==> Installing joplin package group with pacman -U...
loading packages...
resolving dependencies...
looking for conflicting packages...
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: joplin and joplin-desktop-electron are in conflict
==> WARNING: Failed to install built package(s).
makepkg -si  6.68s user 2.74s system 109% cpu 8.598 total

I have tried uninstalling the previous packages and pulled the latest version each time one has become available over the past few days but to no avail. Any help would be greatly appreciated.

maciex commented on 2020-12-22 19:57 (UTC) (edited on 2020-12-22 19:57 (UTC) by maciex)

Hello, I'm trying to install this package but i have:

rror: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: joplin and joplin-desktop-electron are in conflict

I do not have joplin-desktop-electron installed.

greve commented on 2020-12-22 10:30 (UTC) (edited on 2020-12-22 11:24 (UTC) by greve)

When starting joplin-desktop:

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

I cannot recall when the last time was it worked, I completely lost track of what is going on with this package ...

EDIT: (Re)Did yay -S --mflags="--nocheck" joplin and it works again.

jmonger commented on 2020-12-21 13:08 (UTC)

@masterkorp --nocheck is still needed for the build to succeed. I agree, it would be great if you could test locally then push one commit when ready.

figue commented on 2020-12-21 11:50 (UTC)

with "makepkg -f" you can force the build. No need to bump if not necessary. Is better to make changes locally and, at the end, push the update to AUR, as Rhinoceros suggest.

Rhinoceros commented on 2020-12-21 11:07 (UTC) (edited on 2020-12-21 12:57 (UTC) by Rhinoceros)

@masterkorp Oh okay. Maybe I missed something. Can't you just makepkg locally without pushing changes? What else does the AUR do exactly?

masterkorp commented on 2020-12-21 10:40 (UTC)

@Rhinocerors

I need to test the releases, I absolutely no other way to test the releases and the multiple package integration of the AUR

Also, `--nocheck`` is not needed anymore even, the check function is a force pass.

Rhinoceros commented on 2020-12-20 22:38 (UTC) (edited on 2020-12-20 22:39 (UTC) by Rhinoceros)

@masterkorp Could you please stop pushing multiple updates? I've had to rebuild this so many times in the last few weeks. Can you please just put all your changes in one $pkgrel bump? There really shouldn't be any need for 12 bumps. Also, since the PKGBUILD is broken (check() still fails), it's quite annoying to re-install the same version 13 times.

EDIT: it's also worth pinning one of the comments about building with --nocheck

neoresin commented on 2020-12-20 19:14 (UTC)

Sorry to sound like a nooblet, but how do you do the --nocheck with aurutils? Anybody know?

karcher commented on 2020-12-20 17:35 (UTC)

@Schlaefer: Many thanks! Joplin works again!

Schlaefer commented on 2020-12-20 11:15 (UTC) (edited on 2020-12-20 11:18 (UTC) by Schlaefer)

Joplin's test-cases are currently failing. The workaround is the same as for joplin-desktop-electron that was mentioned by others: don't run the test-cases by disabling check (e.g. for yay):

yay -S --mflags="--nocheck" joplin-desktop

karcher commented on 2020-12-18 17:30 (UTC) (edited on 2020-12-18 17:34 (UTC) by karcher)

I cannot launch Joplin. I try to install this package and I'm getting this error:

joplin: Ran all test suites.
joplin: npm ERR! code ELIFECYCLE
joplin: npm ERR! errno 1
joplin: npm ERR! joplin@1.4.9 test: `jest --config=jest.config.js --runInBand --bail --forceExit`
joplin: npm ERR! Exit status 1
joplin: npm ERR! 
joplin: npm ERR! Failed at the joplin@1.4.9 test script.
joplin: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
joplin: npm ERR! A complete log of this run can be found in:
joplin: npm ERR!     /home/user/.npm/_logs/2020-12-18T17_26_03_638Z-debug.log
lerna ERR! npm run test exited 1 in 'joplin'
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! root@ test: `lerna run test --stream`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the root@ test script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/user/.npm/_logs/2020-12-18T17_26_03_685Z-debug.log
==> ERROR: A failure occurred in check().

$ yay -S --rebuild joplin-desktop-electron does not work!

$ makepkg -si does not work either!

$ npm -v 6.14.8

piernov commented on 2020-12-18 12:45 (UTC)

npm 7.0.5-1 from community-testing fails to build with some obscure errors, npm 6.14.8-2 from community works fine.

Dongsean commented on 2020-12-18 08:07 (UTC)

@imlonghao yay -S --rebuild joplin-desktop-electron commond can not work, i makepkg -s build a new pkg, thank you!

imlonghao commented on 2020-12-18 06:08 (UTC)

@Dongsean yay -S --rebuild joplin-desktop-electron

Dongsean commented on 2020-12-18 05:48 (UTC)

@imlonghao i am a beginner, please tell me how to rebuild it.

imlonghao commented on 2020-12-18 03:29 (UTC)

@Dongsean you can just rebuild it, should fix your re2 problem.

Dongsean commented on 2020-12-18 03:14 (UTC) (edited on 2020-12-18 03:15 (UTC) by Dongsean)

The joplin-desktop-electron 1.4.19-8 last updated in 2020-12-09 01:07, but electron and re2 last updated in 2020-12-15 02:54 UTC. Can we get a new PKGBUILD?

jmonger commented on 2020-12-17 13:29 (UTC)

The downgrade from @maykin and @ridgea works. Can we get a fix to the PKGBUILD?

galvez_65 commented on 2020-12-17 01:09 (UTC) (edited on 2020-12-18 02:55 (UTC) by galvez_65)

I am getting the same error as @lucianf /usr/bin/joplin-desktop: line 12: ./@joplinapp-desktop: No such file or directory I double checked the pkg folder and there is no @joplinapp-dektop file created. Does anyone know how to fix this?

update: commenting out

npm install compare-version # Joplin Cli needs this
./node_modules/.bin/lerna bootstrap

allows the package to build correctly. I have no idea how that affects joplin-cli as I don't use that

Also rebuilding seems to eliminate the re2 issue

professed commented on 2020-12-17 00:37 (UTC)

@Darkmind2007: The package was split to make it simpler for people to install only the CLI or the desktop version. You can (re)install the desktop version by installing the joplin-desktop-electron package.

You may need to pass the --nocheck flag to makepkg (see below) in order for the build of the desktop package to work, but this is a temporary bug.

Darkmind2007 commented on 2020-12-16 20:10 (UTC)

After the update today, "joplin 1.4.19-8" package only contains "joplin-cli". Any ideas why the desktop version was removed?

maykin commented on 2020-12-16 18:32 (UTC)

I needed to downgrade re2:

sudo pacman -U /var/cache/pacman/pkg/re2-1\:20201001-1-x86_64.pkg.tar.zst

jmonger commented on 2020-12-15 17:30 (UTC)

@ridgea Confirmed. I have the same issue.

ridgea commented on 2020-12-15 09:04 (UTC)

FYI: today electron package in my system was updated alongside with re2 (as a dependency) 11.1.0 _1 -> 11.1.0 _2 After that joplin-desktop didn't start, had to downgrade electron to the previous version (the new version requires newer re2, that contains libre2.so.9 when joplin requires libre2.so.8)

Jeff_WuYo commented on 2020-12-14 11:19 (UTC)

Somehow, I use systemd-networkd as my network manager, joplin failed no matter what flags I use. In the output, yay failed to get a appimage from github.com/electron-userland/electron-builder-binaries/release/download/appimage-12.0.1/appimage-12.0.1.7z

But if I use networkmanager from gnome, joplin installed as intended. I don't know if it's my resolved config problem or some other reason. It might be off topic.

lucianf commented on 2020-12-14 10:43 (UTC)

I tried installing joplin-desktop-electron even with the suggestions below but I get this error when running it:

/usr/bin/joplin-desktop: line 12: ./@joplinapp-desktop: No such file or directory

I can only run the joplin-cli version successfully. Any ideas?

Tucniak commented on 2020-12-11 07:12 (UTC)

yay -S --mflags="--nocheck" joplin-desktop-electron worked for me as well

jmonger commented on 2020-12-10 14:39 (UTC)

Confirmed that yay -S --mflags="--nocheck" joplin-desktop-electron works.

jmonger commented on 2020-12-10 13:30 (UTC)

@masterkorp Upgrade still doesn't work. See output below.

lerna ERR! npm run test exited 1 in 'joplin'
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! root@ test: `lerna run test --stream`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the root@ test script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/[user]/.npm/_logs/2020-12-10T13_09_05_372Z-debug.log
==> ERROR: A failure occurred in check().
    Aborting...

professed commented on 2020-12-08 18:40 (UTC)

@masterkorp: The package build for joplin-desktop-electron succeeds with `makepkg --nocheck'.

As expected, passing the --nocheck flag to yay also yields success (yay -S --mflags="--nocheck" joplin-desktop-electron).

I have opened an issue on GitHub as requested. Thank you for your help!!

masterkorp commented on 2020-12-08 17:14 (UTC)

@figue, I added that on the latest update.

masterkorp commented on 2020-12-08 17:13 (UTC)

@professed, that is on the check() function, it seems you run out of proceess spawning capabilites.

You can run makepkg --nocheck to see ?

You can you open an issue here? https://github.com/alfredopalhares/arch-pkgbuilds It would be easier for me.

masterkorp commented on 2020-12-08 17:13 (UTC)

@professed, that is on the check() function, it seems you run out of proceess spawning capabilites.

You can run makepkg --nocheck to see ?

You can you open an issue here? https://github.com/alfredopalhares/arch-pkgbuilds It would be easier for me.

figue commented on 2020-12-08 17:10 (UTC) (edited on 2020-12-08 17:14 (UTC) by figue)

I have to build the new splitted package with extra-x86_64-build (package release 1.4.19-1) then uninstall joplin and install joplin-desktop-electron (as I don't need the CLI). Whould be nice to print an advice in post-upgrade() for users to take it into account.

Edit: I have seen the message in latest commit. Thanks!

professed commented on 2020-12-08 17:03 (UTC)

@masterkorp: Just tried again after you updated the package. Same result. I tried `yay -S joplin-desktop-electron' for good measure to no avail. Here's the npm debug log of that run.

masterkorp commented on 2020-12-08 16:50 (UTC)

Hello,

Just updated the package again.

@jmonger, its because you do not have electron installed, this now uses packaged electron. I added that to makedpends.

If joplin desktop is not being installed, you need to tell your AUR client to, yay -S joplin-desktop-electron

juxuanu commented on 2020-12-08 14:36 (UTC)

Same here... What do you need to help troubleshoot this?

jmonger commented on 2020-12-08 14:24 (UTC)

Getting this error message at the end. Upgrading from 1.3.3.

cat: /usr/lib/electron/version: No such file or directory
==> ERROR: A failure occurred in package_joplin-desktop-electron().
    Aborting...

Blowtoad commented on 2020-12-08 11:15 (UTC)

@masterkorp I seem to be having the same problem. joplin-desktop is not being installed, while joplin-cli is (directly in /usr/share/joplin-cli)

masterkorp commented on 2020-12-08 10:40 (UTC)

@lilgeek its not suposed to be there, now its using the joplin-cli and joplin-desktop

@NatOsaka, can you give more context pn this problem ?

lilgeek commented on 2020-12-08 09:47 (UTC)

@masterkorp The error reported by NatOsaka is there after the latest update Latest update seems to not create /usr/share/joplin/joplin

SweetestRug commented on 2020-12-08 02:41 (UTC)

@NatOsaka: Could you help with which commit was rolled back and how? I am having the same issue.

NatOsaka commented on 2020-11-22 12:37 (UTC)

Latest update seems to not create /usr/share/joplin/joplin. I rolled back a commit and the joplin binary is correctly built.

imlonghao commented on 2020-11-06 03:38 (UTC)

@tag_enk can you try extra-x86_64-build build in a clean env?

tag_enk commented on 2020-11-06 03:34 (UTC)

anyone got a fix for this? nothing is working for me at this point

SweetestRug commented on 2020-11-01 22:22 (UTC)

On Manjaro (at least) Joplin 1.2.6-1 cli interface fails to start with a missing sqlite3 module error.

Following the comment by @Retro64XYZ on 2020-08-10, this can be fixed by:

cd /usr/share/joplin-cli
sudo npm install sqlite3 --unsafe-perm

I hope this can help someone else.

apastuszak commented on 2020-11-01 16:45 (UTC)

This package needs an electron dependency. It was failing to build for me.

I had electron-lts-carbon installed. Soon as I switched to community/electron 10.1.5-1, the package built and installed successfully.

mY1v6 commented on 2020-10-12 11:40 (UTC)

@bparsons I keep getting "error errno 6, error joplin@1.0.0 postinstall:" when using ur fork (tried with v1.1.4, v1.2.6, v1.3.1)

roachsinai commented on 2020-10-10 17:04 (UTC)

@masterkorp could you please update this package as the latest release no is 1.2.6. Thanks in advance!

bparsons commented on 2020-10-04 13:02 (UTC)

1.1.4 is the latest official release. If you are anxious for pre-releases, I pretty much keep up with those and have PKGBUILDs here: https://github.com/bparsons/joplin-pkgbuild

WGQuint10 commented on 2020-10-01 22:36 (UTC)

Here's a quick and hacky fix that nobody should use. I made no effort to actually identify the root problem. If you're desperate, you're desperate; use at your own risk.

sudo mkdir /usr/share/joplin-cli/build
sudo ln -s /usr/share/joplin-cli/lib /usr/share/joplin-cli/build/lib

masterkorp commented on 2020-09-30 13:48 (UTC)

Can you guys post of your problems on the github repo? I am having problems following everyone, one, because my packages works for me, even on a fresh system.

Retro64XYZ commented on 2020-09-29 16:12 (UTC) (edited on 2020-09-29 17:29 (UTC) by Retro64XYZ)

I am having the issue with the spellfix.so file as well. Any chance we could get this updated or can I help do so? I use this for work and REALLY need it fixed. I appreciate all your hard work but if I can help in any way, would love to.

roachsinai commented on 2020-09-29 08:08 (UTC)

Sorry, I misdeleted my previous comment.

@WatcherWhale Thanks for help! I have downgraded to 1.0.245 not work as told me need to upgrade when open GUI. In terminal joplin show empty notes. Did you have same situation? Or you use 242 directly and works well?

WatcherWhale commented on 2020-09-29 06:57 (UTC)

@roachsinai This issue is fixed in the upstream (https://github.com/laurent22/joplin/issues/3783). The package here must however be updated to at least 1.2.1 for this to work again. Currently, you can downgrade to an older version (like I did to version 1.0.242) and wait until the package gets updated.

FillFeile commented on 2020-09-26 09:21 (UTC)

Hi everyone, I'm running into an issue with the PKGBUILD of this package. The prebuild-install step complains about a missing module called 'fstream'. Please find the error below:

> prebuild-install || node-gyp rebuild

prebuild-install WARN install No prebuilt binaries found (target=14.12.0 runtime=node arch=x64 libc= platform=linux)
gyp ERR! UNCAUGHT EXCEPTION
gyp ERR! stack Error: Cannot find module 'fstream'
gyp ERR! stack Require stack:
gyp ERR! stack - /usr/lib/node_modules/npm/node_modules/node-gyp/node_modules/tar/lib/entry.js
gyp ERR! stack - /usr/lib/node_modules/npm/node_modules/node-gyp/node_modules/tar/lib/entry-writer.js
gyp ERR! stack - /usr/lib/node_modules/npm/node_modules/node-gyp/node_modules/tar/lib/pack.js
gyp ERR! stack - /usr/lib/node_modules/npm/node_modules/node-gyp/node_modules/tar/tar.js
gyp ERR! stack - /usr/lib/node_modules/npm/node_modules/node-gyp/lib/install.js
gyp ERR! stack - /usr/lib/node_modules/npm/node_modules/node-gyp/lib/node-gyp.js
gyp ERR! stack - /usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js
gyp ERR! stack     at Function.Module._resolveFilename (internal/modules/cjs/loader.js:893:15)
gyp ERR! stack     at Function.Module._load (internal/modules/cjs/loader.js:743:27)
gyp ERR! stack     at Module.require (internal/modules/cjs/loader.js:965:19)
gyp ERR! stack     at require (internal/modules/cjs/helpers.js:88:18)
gyp ERR! stack     at Object.<anonymous> (/usr/lib/node_modules/npm/node_modules/node-gyp/node_modules/tar/lib/entry.js:14:15)
gyp ERR! stack     at Module._compile (internal/modules/cjs/loader.js:1076:30)
gyp ERR! stack     at Object.Module._extensions..js (internal/modules/cjs/loader.js:1097:10)
gyp ERR! stack     at Module.load (internal/modules/cjs/loader.js:941:32)
gyp ERR! stack     at Function.Module._load (internal/modules/cjs/loader.js:782:14)
gyp ERR! stack     at Module.require (internal/modules/cjs/loader.js:965:19)
gyp ERR! System Linux 5.8.10-arch1-1
gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"

Any advise on that?

navarrothiago commented on 2020-09-25 20:44 (UTC) (edited on 2020-09-25 20:45 (UTC) by navarrothiago)

I have faced this error when opened CLI: ./build/lib/sql-extensions/spellfix.so: cannot open shared object file: No such file or directory . It was fixed in version CLI v1.2.1.

quenyen commented on 2020-09-25 15:16 (UTC)

Do you want a comaintainer masterkorp? I use this package and have a vested interest in keeping it up to date.

Konsole commented on 2020-09-24 11:00 (UTC)

Hello everyone, Does anyone know how to improve Cyrillic text within the editor? Having trouble with editing text, the cursor straight up just clips through some letters

the_z0id commented on 2020-09-16 09:48 (UTC)

@zero.0 Thank you for the hint. I will have a look at it.

zero.0 commented on 2020-09-14 19:24 (UTC)

@the_z0id

I had succsess installing it from Chaotic-AUR. Not sure if that suits you...

the_z0id commented on 2020-09-13 09:52 (UTC)

Now, it gives the following error:

> Joplin@1.0.245 dist /home/XXX/.cache/yay/joplin/src/joplin-1.0.245/ElectronClient
> electron-builder

  • electron-builder  version=22.3.2 os=5.4.64-1-MANJARO
  • loaded configuration  file=package.json ("build" field)
  • electron-rebuild not required if you use electron-builder, please consider to remove excess dependency from devDependencies

To ensure your native dependencies are always matched electron version, simply add script `"postinstall": "electron-builder install-app-deps" to your `package.json`
  • writing effective config  file=dist/builder-effective-config.yaml
  • skipped dependencies rebuild  reason=npmRebuild is set to false
  • packaging       platform=linux arch=x64 electron=8.2.5 appOutDir=dist/linux-unpacked
  • building        target=AppImage arch=x64 file=dist/Joplin-1.0.245.AppImage
  ⨯ cannot execute  cause=exit status 1
                    errorOut=Write failed because No space left on device
FATAL ERROR:Failed to write to output filesystem

                    command=/home/XXX/.cache/electron-builder/appimage/appimage-12.0.1/linux-x64/mksquashfs /home/XXX/.cache/yay/joplin/src/joplin-1.0.245/ElectronClient/dist/__appImage-x64 /home/XXX/.cache/yay/joplin/src/joplin-1.0.245/ElectronClient/dist/Joplin-1.0.245.AppImage -offset 188392 -all-root -noappend -no-progress -quiet -no-xattrs -no-fragments
                    workingDir=/home/XXX/.cache/yay/joplin/src/joplin-1.0.245/ElectronClient/dist/__appImage-x64
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! Joplin@1.0.245 dist: `electron-builder`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the Joplin@1.0.245 dist script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/XXX/.npm/_logs/2020-09-13T09_20_00_802Z-debug.log
==> ERROR: A failure occurred in build().
    Aborting...

It says there is not enough space, but there are more than 15 GB free. Any ideas?

the_z0id commented on 2020-09-11 15:07 (UTC) (edited on 2020-09-11 15:08 (UTC) by the_z0id)

At the moment, the installation hangs here:

extract:hermes-engine: sill extract  hermes-engine@0.2.1 extracted to /home/XXXXX/.cache/yay/joplin/src/joplin-1.0.245/ReactNativeClient/node_modules/.staging/hermes-engine-a5d159db (264376m)

Any suggestions?

Darkmind2007 commented on 2020-09-07 09:02 (UTC) (edited on 2020-09-07 11:15 (UTC) by Darkmind2007)

Sorry, how likely is a chance that v1.0.241 will be packaged soon? This release breaks backward compatibility and currently desktop cannot sync anymore due to mobile devices that have already upgraded the server storage

macxcool commented on 2020-08-31 15:37 (UTC) (edited on 2020-08-31 15:37 (UTC) by macxcool)

@masterkorp Thanks for unflagging that. Sorry for telling you something that you already know ;-) I hope you had a good vacation.

masterkorp commented on 2020-08-31 15:24 (UTC)

Hello everyone,

I was on vacations, I unflagged the package, I would like to remind you again, that that is is the latest stable release for joplin, I don't package pre-releases.

quenyen commented on 2020-08-27 13:30 (UTC)

Unflag it is up to date

macxcool commented on 2020-08-25 11:09 (UTC)

@mastercorp You can unflag it. Can you please do that?

bigbrozer commented on 2020-08-25 09:12 (UTC)

This package has been flagged out of date but beware v1.0.233 is still the latest "stable" release. Upper versions are still pre-releases. Details here: https://github.com/laurent22/joplin/releases

Retro64XYZ commented on 2020-08-10 17:15 (UTC) (edited on 2020-08-10 17:17 (UTC) by Retro64XYZ)

To fix the issue related to joplin-cli not running.

internal/modules/cjs/loader.js:1033
  throw err;
  ^

Error: Cannot find module 'immer'
Require stack:
- /usr/share/joplin-cli/lib/services/ResourceEditWatcher/reducer.js
- /usr/share/joplin-cli/lib/reducer.js
- /usr/share/joplin-cli/lib/BaseApplication.js
- /usr/share/joplin-cli/app.js
- /usr/share/joplin-cli/main.js
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:1030:15)
    at Function.Module._load (internal/modules/cjs/loader.js:899:27)
    at Module.require (internal/modules/cjs/loader.js:1090:19)
    at require (internal/modules/cjs/helpers.js:75:18)
    at Object.<anonymous> (/usr/share/joplin-cli/lib/services/ResourceEditWatcher/reducer.js:3:17)
    at Module._compile (internal/modules/cjs/loader.js:1201:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1221:10)
    at Module.load (internal/modules/cjs/loader.js:1050:32)
    at Function.Module._load (internal/modules/cjs/loader.js:938:14)
    at Module.require (internal/modules/cjs/loader.js:1090:19) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
    '/usr/share/joplin-cli/lib/services/ResourceEditWatcher/reducer.js',
    '/usr/share/joplin-cli/lib/reducer.js',
    '/usr/share/joplin-cli/lib/BaseApplication.js',
    '/usr/share/joplin-cli/app.js',
    '/usr/share/joplin-cli/main.js'
  ]
}

Run the following.

cd /usr/share/joplin-cli
sudo npm install immer --unsafe-perm
sudo npm install sqlite3 --unsafe-perm

This is a temporary fix but it will resolve the issue with complaints by joplin-cli that immer or sqlite3 are not available.

mprom commented on 2020-08-08 11:03 (UTC)

Installation currently crashes with this error:

> Joplin@1.0.233 dist /home/mp/.cache/yay/joplin/src/joplin-1.0.233/ElectronClient
> electron-builder

  • electron-builder  version=22.3.2 os=5.7.11-arch1-1
  • loaded configuration  file=package.json ("build" field)
  • electron-rebuild not required if you use electron-builder, please consider to remove excess dependency from devDependencies

To ensure your native dependencies are always matched electron version, simply add script `"postinstall": "electron-builder install-app-deps" to your `package.json`
  • writing effective config  file=dist/builder-effective-config.yaml
  • skipped dependencies rebuild  reason=npmRebuild is set to false
  • packaging       platform=linux arch=x64 electron=8.2.5 appOutDir=dist/linux-unpacked
  ⨯ Get https://github.com/electron/electron/releases/download/v8.2.5/electron-v8.2.5-linux-x64.zip: dial tcp: lookup github.com on [::1]:53: read udp [::1]:57377->[::1]:53: read: connection refused
github.com/develar/app-builder/pkg/download.(*Downloader).follow.func1
    /Volumes/data/Documents/app-builder/pkg/download/downloader.go:158
github.com/develar/app-builder/pkg/download.(*Downloader).follow
    /Volumes/data/Documents/app-builder/pkg/download/downloader.go:186
github.com/develar/app-builder/pkg/download.(*Downloader).Download
    /Volumes/data/Documents/app-builder/pkg/download/downloader.go:80
github.com/develar/app-builder/pkg/electron.(*ElectronDownloader).doDownload
    /Volumes/data/Documents/app-builder/pkg/electron/electronDownloader.go:192
github.com/develar/app-builder/pkg/electron.(*ElectronDownloader).Download
    /Volumes/data/Documents/app-builder/pkg/electron/electronDownloader.go:177
github.com/develar/app-builder/pkg/electron.downloadElectron.func1.1
    /Volumes/data/Documents/app-builder/pkg/electron/electronDownloader.go:73
github.com/develar/app-builder/pkg/util.MapAsyncConcurrency.func2
    /Volumes/data/Documents/app-builder/pkg/util/async.go:68
runtime.goexit
    /usr/local/Cellar/go/1.13.6/libexec/src/runtime/asm_amd64.s:1357  
  ⨯ /home/mp/.cache/yay/joplin/src/joplin-1.0.233/ElectronClient/node_modules/builder-util/node_modules/app-builder-bin/linux/x64/app-builder exited with code ERR_ELECTRON_BUILDER_CANNOT_EXECUTE  stackTrace=
                                                                                                                                                                                                      Error: /home/mp/.cache/yay/joplin/src/joplin-1.0.233/ElectronClient/node_modules/builder-util/node_modules/app-builder-bin/linux/x64/app-builder exited with code ERR_ELECTRON_BUILDER_CANNOT_EXECUTE

                                                                                                                                                                                                          at ChildProcess.<anonymous> (/home/mp/.cache/yay/joplin/src/joplin-1.0.233/ElectronClient/node_modules/builder-util/src/util.ts:239:14)
                                                                                                                                                                                                          at Object.onceWrapper (events.js:421:26)
                                                                                                                                                                                                          at ChildProcess.emit (events.js:314:20)
                                                                                                                                                                                                          at maybeClose (internal/child_process.js:1051:16)
                                                                                                                                                                                                          at Process.ChildProcess._handle.onexit (internal/child_process.js:287:5)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! Joplin@1.0.233 dist: `electron-builder`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the Joplin@1.0.233 dist script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/mp/.npm/_logs/2020-08-08T10_59_19_697Z-debug.log
==> ERROR: A failure occurred in build().
    Aborting...
error making: %!s(func() string=0x55574753ebb0)

allsyed commented on 2020-08-05 05:06 (UTC) (edited on 2020-08-05 05:07 (UTC) by allsyed)

Packages (1) joplin-1.0.233-1

Total Installed Size:  514.94 MiB

:: Proceed with installation? [Y/n] 

Half GB? Serioulsly

SweetestRug commented on 2020-08-03 16:14 (UTC)

Hi, as of 1.0.233, joplin builds fine. The GUI works well. However, on launching the cli version, it throws this error:

internal/modules/cjs/loader.js:1033
  throw err;
  ^

Error: Cannot find module 'immer'
Require stack:
- /usr/share/joplin-cli/lib/services/ResourceEditWatcher/reducer.js
- /usr/share/joplin-cli/lib/reducer.js
- /usr/share/joplin-cli/lib/BaseApplication.js
- /usr/share/joplin-cli/app.js
- /usr/share/joplin-cli/main.js
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:1030:15)
    at Function.Module._load (internal/modules/cjs/loader.js:899:27)
    at Module.require (internal/modules/cjs/loader.js:1090:19)
    at require (internal/modules/cjs/helpers.js:75:18)
    at Object.<anonymous> (/usr/share/joplin-cli/lib/services/ResourceEditWatcher/reducer.js:3:17)
    at Module._compile (internal/modules/cjs/loader.js:1201:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1221:10)
    at Module.load (internal/modules/cjs/loader.js:1050:32)
    at Function.Module._load (internal/modules/cjs/loader.js:938:14)
    at Module.require (internal/modules/cjs/loader.js:1090:19) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
    '/usr/share/joplin-cli/lib/services/ResourceEditWatcher/reducer.js',
    '/usr/share/joplin-cli/lib/reducer.js',
    '/usr/share/joplin-cli/lib/BaseApplication.js',
    '/usr/share/joplin-cli/app.js',
    '/usr/share/joplin-cli/main.js'
  ]
}

masterkorp commented on 2020-07-08 08:40 (UTC)

I would like to remmind that this package does not update to pre-releases

Deuchnord commented on 2020-06-25 12:49 (UTC) (edited on 2020-06-25 12:50 (UTC) by Deuchnord)

Can you copy the application icon to /usr/share/pixmaps/joplin.png and update the line 6 of the joplin.desktop to:

Icon=joplin

This will make it possible to customize it in icon themes.

SweetestRug commented on 2020-06-15 21:38 (UTC)

Build as of June 15 is failing. Failure starts at

/bin/sh: pkg-config: command not found gyp: Call to 'pkg-config --cflags libsecret-1' returned exit status 127 while in binding.gyp. while trying to load binding.gyp

with multiple gyp ERR! following. For what its worth, I am running Manjaro.

commented on 2020-05-22 23:21 (UTC)

It’s not Zemoose’s fault. To keep certain packages from breaking and bugs from arising, Joplin’s main team is locking in specific versions. The dependencies have gotten managed better than they used to be but the whole “use new libraries where able to save time and code maintenance” approach is a bit problematic at times.

I wouldn’t recommend updating most packages if you can avoid it because of this.

thelazyoxymoron commented on 2020-05-22 20:45 (UTC)

@ZeMoose, just to be on the safe side, you should periodically check for npm update and resolve those security vulnerabilities by running npm audit fix.

malcolm commented on 2020-05-21 13:56 (UTC)

this version is very outdated. please do something

commented on 2020-05-18 17:13 (UTC)

Hey, all. My name is Brandon and I'm a member of the Joplin Team. I'm not one of the core devs but instead primarily am focused on Linux support and research.

Here's my credentials on the Forums: https://discourse.joplinapp.org/g/Team

Here's my main contribution to the project so far: https://github.com/laurent22/joplin/issues/3114

@ZeMoose, the dependencies of Joplin do concern me quite a bit myself. I'd love to hear which ones concern you the most.

RockhopperP commented on 2020-05-15 08:17 (UTC)

If confronted with a 'fatal error: unknown table: settings' it helped me to rm -rf ~/.config/Joplin/ ~/.config/joplin-desktop/ and reinstall joplin from the already compiled package.

Such was suggested here: https://discourse.joplinapp.org/t/solved-linux-fatal-error-unknown-table-settings/6253

ZeMoose commented on 2020-05-08 03:58 (UTC)

Should I be concerned about the hundreds of low and moderate severity vulnerabilities reported by npm during the build process?

avndp commented on 2020-05-06 02:47 (UTC)

Building fails all the time.

vv181 commented on 2020-04-29 21:52 (UTC)

@imlonghao

It still does not work.

I'll put the log here:https://pastebin.com/3CfZQ0NR

imlonghao commented on 2020-04-23 01:36 (UTC)

@Al3xG sudo npm cache clean --force [1] does it help?

[1] https://stackoverflow.com/questions/15393821/npm-err-cb-never-called

Al3xG commented on 2020-04-22 20:23 (UTC)

I'm having the same "cb() never called!" error with the last 1.0.201 build. Any way to sort this out please? Thanks.

thelazyoxymoron commented on 2020-04-14 17:15 (UTC)

Please update the PKGBUILD. The latest version out is 1.0.200.

roachsinai commented on 2020-03-31 14:08 (UTC)

Now, the version is 1.0.197.

Please update the PKGBUILD.

Choppa2 commented on 2020-03-30 04:04 (UTC)

I'm also having the cb() never called error while running makepkg -si. Hope this gets fixed soon.

gnaggnoyil commented on 2020-03-25 06:54 (UTC)

It also happens to me today where on some Archlinux machines installing this package through yay reports npm ERR! cb() never called! error while running makepkg directly did not cause this error. Strange.

alitajelsir commented on 2020-03-20 04:00 (UTC)

I can confirm it's building now.

macxcool commented on 2020-03-18 23:51 (UTC)

Actually, compiling with yay works fine now. Weird. I guess it's alright after all.

macxcool commented on 2020-03-18 23:38 (UTC)

Interesting. I ran makepkg manually (I use yay normally). It worked fine. I'm going to try a clean build that way.

macxcool commented on 2020-03-18 23:02 (UTC)

@aliTajelsir @masterkorp @imlonghao I'm getting the same error "npm ERR! cb() never called!" I have my machine all up-to-date (-Syu) as well. I checked and yarn is installed. I was able to compile it in the previous iteration of the package.

commented on 2020-03-18 14:46 (UTC)

Missing yarn in makedepends

reeeeeeeeeeelity commented on 2020-03-18 06:22 (UTC)

@imlonghao I saw you have recently joined and adopted this package on archlinuxcn. Maybe you can start an alternative fork on AUR? This author doesn't seem too keen to maintain it accordingly to the guideline. There is plenty room for improvement.

  • Missing and extra depends.

  • separated CLI and Electron builds.

  • Building against system electron.

alitajelsir commented on 2020-03-16 18:36 (UTC) (edited on 2020-03-16 18:36 (UTC) by alitajelsir)

@masterkorp @imlonghao, I already did pacman -Syu but I did it again and then tried to build but without success. @paulstrait, I installed yarn with the same results. As I see I'm the only one with the npm issue so I'll look into my setup again and if it's not resolved I'll open an issue in GitHub. Thanks for the help.

paulstrait commented on 2020-03-16 17:39 (UTC)

Trap000d's fork works, but it needs yarn as a dependency but doesn't seem to realize that it does...

imlonghao commented on 2020-03-16 15:22 (UTC)

@AliTajelsir, I can build trap000d's fork successfully. You may do pacman -Syu before build the AUR package. @masterkorp, can you merge https://github.com/alfredopalhares/joplin-pkgbuild/pull/49 into master or add yarn as makedepend?

masterkorp commented on 2020-03-16 15:14 (UTC)

@AllTajedir

Can you do a pacman -Syu before and AUr update as well?

If the problem persits, can you please report it here?

https://github.com/alfredopalhares/joplin-pkgbuild/issues

Regards

alitajelsir commented on 2020-03-16 15:11 (UTC) (edited on 2020-03-16 15:11 (UTC) by alitajelsir)

Thanks @trap000d, but even with your repo I get the npm error:

npm ERR! cb() never called!

npm ERR! This is an error with npm itself. Please report this error at:
npm ERR!     <https://npm.community>

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/ali/GitHub/trap-joplin/joplin/src/npm-cache/_logs/2020-03-16T15_06_27_003Z-debug.log
==> ERROR: A failure occurred in build().

Looks like an issue specific to npm. Tried different solutions from their forum without success.

trap000d commented on 2020-03-16 01:17 (UTC)

AliTajelsir, This is because I've modified *.desktop file as well. Please clone full repo from https://github.com/trap000d/aur and build Joplin from there.

halcek commented on 2020-03-15 19:56 (UTC) (edited on 2020-03-15 19:58 (UTC) by halcek)

Even with yarn installed, while it builds, it certainly does not look, nor function as it should?

alitajelsir commented on 2020-03-15 12:11 (UTC)

I get the following error when trying to build:

npm ERR! cb() never called!

npm ERR! This is an error with npm itself. Please report this error at:
npm ERR!     <https://npm.community>

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/ali/GitHub/joplin/src/npm-cache/_logs/2020-03-15T11_54_48_382Z-debug.log
==> ERROR: A failure occurred in build().
    Aborting...

I've also tried @trap000d PKGBUILD but also unsuccessful with the following error:

==> Validating source files with sha256sums...
    joplin.desktop ... FAILED
    joplin-desktop.sh ... Passed
    joplin.sh ... Passed
    joplin-1.0.193.tar.gz ... Passed
==> ERROR: One or more files did not pass the validity check!

With @trap000d PKGBUILD and updated sha256sums I get the first npm error

famar commented on 2020-03-15 11:59 (UTC)

This is getting long. @masterkorp can you please add yarn as makedepend? Thanks

Rhinoceros commented on 2020-03-13 23:49 (UTC)

I also needed to install yarn to get this to build. I think it's only a makedepends though, because I was able to uninstall it and joplin still ran fine. Also is git really a makedependency (I didn't check)?

LaserTron commented on 2020-03-13 17:02 (UTC) (edited on 2020-03-13 17:02 (UTC) by LaserTron)

Just like that when I installed it I got

/var/tmp/pamac-build-nick/joplin/PKGBUILD: line 46: yarn: command not found ==> ERROR: A failure occurred in build(). Aborting...

I installed yarn, then it worked. Yarn should be added as a dependency.

SaltFactory commented on 2020-03-12 21:43 (UTC)

Thanks trap000d, your version worked for me.

trap000d commented on 2020-03-11 20:51 (UTC)

mightyBroccoli, Here is the PKGBUILD for 1.0.193 which works for me: https://github.com/trap000d/aur/blob/master/joplin/PKGBUILD

mightyBroccoli commented on 2020-03-11 17:07 (UTC)

There seems to be some issue with build process with the new stable version 1.0.193.

sl13kp commented on 2020-03-09 09:58 (UTC)

the best is appimage

masterkorp commented on 2020-03-04 11:07 (UTC)

Thank you fabious!!!

Fabius commented on 2020-03-03 11:40 (UTC)

People should really stop flagging this package as out-of-date every single day because a PRE-release came out... Please check this link: https://github.com/laurent22/joplin/releases/latest then stop. Take 5 to 10 minutes to read the release number. Then take some more time to accurately compare it with the version on the AUR: digit by digit!

trap000d commented on 2020-03-03 03:40 (UTC)

Build procedure has changed significantly since 1.0.185. I've spent an hour and built 1.0.187 successfully. The corresponding PKGBUILD can be found here: https://github.com/trap000d/aur/tree/master/joplin

As a side effect it also builds an AppImage archive. To disable AppImage one should patch the file joplin-1.0.187/ElectronClient/package.json: .... -"target": "AppImage" +"target": "dir" ....

reeeeeeeeeeelity commented on 2020-02-29 04:45 (UTC)

ICYMI, you can find pre-built Joplin package in http://chaotic.bangl.de/chaotic-aur/x86_64/ and http://repo.archlinuxcn.org

Perfi commented on 2020-02-29 04:41 (UTC)

If you're experiencing app locking on sync, consider looking through and possibly helping out with this issue:

https://github.com/laurent22/joplin/issues/2518

Kernel downgrade to 5.4 LTS seems (so I've heard) to work for now.

Perfi commented on 2020-02-17 06:56 (UTC) (edited on 2020-02-17 06:56 (UTC) by Perfi)

I have a PR for the current version, which seems to improve stability a bunch: https://github.com/alfredopalhares/joplin-pkgbuild/pull/45. @hvksmr1996 I simply removed the Version line in there, since the spec describes it at optional. Does that sound reasonable?

hvksmr1996 commented on 2020-02-17 04:29 (UTC)

Incorrect use of Version in your joplin.desktop file. It's meant to be version of free-desktop specs, not version of the application.

sl13kp commented on 2020-02-16 11:35 (UTC)

best mode: wget -O - https://raw.githubusercontent.com/laurent22/joplin/master/Joplin_install_and_update.sh | bash

and copy icon to your set.

justVisiting commented on 2020-02-13 03:23 (UTC)

I got exact the same error as Poetician earlier today. I think the dependency just had it's URL down. The Joplin package installs just fine for me now!

Poetician commented on 2020-02-12 21:41 (UTC)

Hi,

Tried the yay install and got this:

npm ERR! code E404 npm ERR! 404 Not Found - GET https://registry.npmjs.org/error-ex/-/error-ex-1.3.2.tgz npm ERR! 404 npm ERR! 404 'error-ex@1.3.2' is not in the npm registry. npm ERR! 404 You should bug the author to publish it (or use the name yourself!) npm ERR! 404 It was specified as a dependency of 'joplin-1.0.179'

Here's the link to my pastebin of the debug https://pastebin.com/bhkn8Fyr

Thanks

fzerorubigd commented on 2020-02-04 09:39 (UTC)

I've got this error for running joplin-desktop :

[2717597:0204/103108.572837:FATAL:setuid_sandbox_host.cc(157)] The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I'm aborting now. You need to make sure that /usr/share/joplin/chrome-sandbox is owned by root and has mode 4755.
/usr/bin/joplin-desktop: line 12: 2717597 Trace/breakpoint trap   (core dumped) ./joplin "$@"

chmod 4755 /usr/share/joplin/chrome-sandbox fix the problem (as a workaround)

masterkorp commented on 2020-01-30 14:44 (UTC)

@apolatynski

Please do pacman -Syu before

apolatynski commented on 2020-01-29 01:54 (UTC)

When trying to build the package, I get multiple errors about duplicate identifier 'Promise' like below:

tsc

node_modules/typescript/lib/lib.es2015.iterable.d.ts:217:11 - error TS2300: Duplicate identifier 'Promise'.

217 interface Promise<T> { } ~~~~~~~

../../../../node_modules/@types/es6-promise/index.d.ts:11:15 11 declare class Promise<T> implements Thenable<T> { ~~~~~~~ 'Promise' was also declared here. ../../../../node_modules/@types/es6-promise/index.d.ts:42:19 42 declare namespace Promise { ~~~~~~~ and here.

guoguojin commented on 2020-01-23 07:36 (UTC)

/usr/lib/node_modules/npm/node_modules/fs.realpath/old.js script had 2 errors when I tried to update to the release from 2020-01-21. Not sure if this is something that came with the Joplin build or whether something else on my system broke it.

The errors are on line 168 and 211 and easy enough to fix manually to get the build to work.

starkers commented on 2020-01-16 15:13 (UTC)

please fix .SRCINFO ;)

reeeeeeeeeeelity commented on 2020-01-11 11:55 (UTC)

According to https://wiki.archlinux.org/index.php/.SRCINFO

Pushing an edited PKGBUILD to the AUR without also updating its .SRCINFO will cause the AUR to serve stale metadata.

.SRCINFO files may be generated using makepkg.

$ makepkg --printsrcinfo > .SRCINFO

Please make the necessary change soon.

ManuelFte commented on 2020-01-11 03:42 (UTC)

I get this error:

failed to parse joplin: Line 30: key "pkgbase" can not occur after pkgbase or pkgname: pkgbase = joplin

marcush commented on 2020-01-08 00:31 (UTC)

@NutTool This should be fixed as of the update about 8 hours ago. This PKGBUILD doesn't use the npm package (which doesn't contain the desktop client) or the AppImage (which doesn't contain the terminal client). Instead it builds both from source.

The build process for the upstream is a little bit in flux at the moment and a change broke this package.

NutTool commented on 2020-01-07 23:29 (UTC)

There appears to be an issue with the way npm is being run. I mistakenly filed a bug upstream: https://github.com/laurent22/joplin/issues/2263

Arkaniad commented on 2020-01-04 20:34 (UTC)

Workaround for the current issue with .SRCINFO:

Clone AUR files from Git, remove the top block in .SRCINFO defining the old version of the package, makepkg -si and install manually. This should allow yay updates to proceed normally since it will not have to upgrade the package. yay seems to want to overwrite the .SRCINFO even if you make changes to it in your cache.

Maintainer simply needs to remove the duplicate block and push new manifest and then everything should be groovy.

matcharles commented on 2020-01-04 17:34 (UTC) (edited on 2020-01-04 17:37 (UTC) by matcharles)

I'm sorry but I am getting the same error :: Parsing SRCINFO (1/1): joplin failed to parse joplin: Line 30: key "pkgbase" can not occur after pkgbase or pkgname: pkgbase = joplin

And @louix in the .SRCINFO even if I remove the bottom (or the top one), it still throws off the same error (it's like it overwrites the .SRCINFO file when I try to install it with yay)

reeeeeeeeeeelity commented on 2020-01-03 17:02 (UTC)

Also, gconf should be removed from dep list.

louix commented on 2020-01-03 16:37 (UTC)

@ruigomes

I don't know why, but there are two "versions" of Joplin in .SRCINFO. Remove the bottom (old) one and it works.

ruigomes commented on 2020-01-03 14:39 (UTC)

I'm getting an error while trying to install this package:

:: Parsing SRCINFO (1/1): joplin failed to parse joplin: Line 30: key "pkgbase" can not occur after pkgbase or pkgname: pkgbase = joplin

reeeeeeeeeeelity commented on 2020-01-03 13:38 (UTC)

I don't know what the problem is but AUR and yay still suggest the latest version still being 175. Chaotic not being built, either.

Reteip commented on 2019-12-10 20:45 (UTC)

Thanks nirnakinho. This is my first time editing package builds. After your comment I realised what to do and it worked for me too. Cheers.

nirnakinho commented on 2019-12-10 19:48 (UTC)

It seems the maintainer forgot to commit the updated joplin.desktop to the git repository. If one does manually modify joplin.desktop to update the included version number to 0.175, the build works normally.

PopeRigby commented on 2019-12-10 16:54 (UTC) (edited on 2019-12-10 16:55 (UTC) by PopeRigby)

I found that I needed to do 'updpkgsums' after I modified joplin.desktop. Then I was able to install it.

Reteip commented on 2019-12-10 08:27 (UTC)

Building joplin... ==> Making package: joplin 1.0.175-1 (Tue 10 Dec 2019 18:25:44 AEST) etc ==> Validating source files with sha256sums... joplin.desktop ... FAILED

saimn commented on 2019-12-10 01:49 (UTC) (edited on 2019-12-10 01:50 (UTC) by saimn)

Thanks @masterkorp but I tried to remove it, and it keeps happening. With the new version it seems better (after fixing the sha256sum), but this is downloading and compiling way too much stuff. After 5 minutes I give up and will use the binary blob from Joplin for now :/

Plexcon commented on 2019-12-09 15:49 (UTC) (edited on 2019-12-09 16:20 (UTC) by Plexcon)

joplin 1.0.175-1

==> ERROR: One or more files did not pass the validation check!

Solution: Edit joplin.desktop v1.0.174 to v1.0.175 https://imgur.com/oFXHxah

masterkorp commented on 2019-12-09 11:57 (UTC)

Hello @saimn

You have a npm lock from a previous installation, please clean your npm folder.

saimn commented on 2019-12-06 11:51 (UTC) (edited on 2019-12-06 11:52 (UTC) by saimn)

Hi, I cannot install v1.0.174, Installation gets stuck on this:

==> Lancement de build()…
[       ...........] - extract:yargs: verb lock using /home/simon/.npm/_locks/staging-c941594f

masterkorp commented on 2019-11-11 13:55 (UTC)

@project9501 What aur manager are you using?

I will be very gladly help your but through this chat its not the easyies, can you open an issue at https://github.com/alfredopalhares/joplin-pkgbuild/issues

If you do not have an github account, you can send me an email directly :)

project9501 commented on 2019-11-10 16:54 (UTC) (edited on 2019-11-10 17:32 (UTC) by project9501)

@masterkorp I kind of figured but I'm not sure how to resolve? Like I gather there's a partial file somewhere but I don't know where -- it's not in the local cache dir and it's not where I have makepkg configured (/opt/aur). Can't "find" the file anywhere on the filesystem.

EDIT: Never mind, it was in /opt/aur/sources. We're good on this part at least.

masterkorp commented on 2019-11-10 15:25 (UTC)

@project32 this is a curl download error, its when downloading the package from the github repo.

project9501 commented on 2019-11-10 04:20 (UTC)

I'm having the same error as @gwenlune, excepting version is 1.0.170 and the initial byte position 9848724.

I'm not sure if this is actually an issue with the package or a problem with curl, as I'm not sure but my initial download might have halted. I however can't find any residual file in any of the usual places so I'm kinda stumped.

Self-Perfection commented on 2019-10-29 22:22 (UTC) (edited on 2019-10-29 22:24 (UTC) by Self-Perfection)

@annata83, just

# rm -r /usr/share/joplin/resources/app/node_modules/sqlite3/.vscode/

Whoa, still works! Ok, I'll save this optimization for later package updates:

# sed -i '/\[options\]/aNoExtract = /usr/share/joplin/resources/app/node_modules/sqlite3/.vscode/*' /etc/pacman.conf

masterkorp commented on 2019-10-29 22:11 (UTC)

@annata83 Hello, I did remove the vscode folder in the new release.

annata83 commented on 2019-10-28 18:18 (UTC)

@Self-Perfection How did you aprroach deleting vscode node module?

micman commented on 2019-10-25 00:08 (UTC)

Hi! For me it is not possible to install the pkg because of lack of space! I tried 3 times. The result was the same. After filling 1.7 GB in /tmp, the installation attempt finishes with a very long error message of this type:

cp: error writing '/tmp/yaourt-tmp-compx/aur-joplin/pkg/joplin/usr/share/joplin/swiftshader/libGLESv2.so': No space left on device
cp: error writing '/tmp/yaourt-tmp-compx/aur-joplin/pkg/joplin/usr/share/joplin/swiftshader/libEGL.so': No space left on device
cp: error writing '/tmp/yaourt-tmp-compx/aur-joplin/pkg/joplin/usr/share/joplin/v8_context_snapshot.bin': No space left on device
==> ERROR: A failure occurred in package().
    Aborting...
==> ERROR: Makepkg was unable to build joplin.
==> Restart building joplin ? [y/N]
==> -------------------------------

Bizarre! The partition has 23 GB of free space. (I utilize Manjaro.)

NB I don't know if it's important, but I have installed electron4. Nevertheless, joplin install his electron client.

tony_42 commented on 2019-10-21 10:29 (UTC) (edited on 2019-10-21 10:29 (UTC) by tony_42)

Other way to reduce the size of the package would be to use the package `electron4' I think. joplin comes with its own copy of electron (about 100M uncompressed), and that might not be needed.

Another possible space optimisation of the install would be to have joplin compress its sources into a .asar (some kind of tarball for electron); but having the javascript uncompressed on Linux is a choice made by the author of Joplin, so it might be needed, or it might not.

Last space optimisation I can think of would be to have two different packages, one for joplin-desktop and one for joplin-cli as I don't think they share ressources, I might be wrong.

Cheers.

Self-Perfection commented on 2019-10-20 15:46 (UTC) (edited on 2019-10-24 22:05 (UTC) by Self-Perfection)

Version 1.0.170 is damn big for such a simple app! 600MB uncompressed!

I wonder if it can be stripped down. Most prominent is /usr/share/joplin/resources/app/node_modules/sqlite3/.vscode. As I can guess from file path this is some kind of IDE internal cache and is not required. And it takes almost 150MB - 25% of installed app size!

UPD: I deleted /usr/share/joplin/resources/app/node_modules/sqlite3/.vscode and Joplin still works perfectly fine.

veras commented on 2019-09-11 12:02 (UTC)

@masterkorp https://qbin.io/detect-ltd-db3c

masterkorp commented on 2019-09-11 08:55 (UTC)

@veras can you give a more verbose error?

veras commented on 2019-09-11 07:41 (UTC)

Tried building (with yay and makepkg) and it errors at "Running: "/home/user/.cache/yay/joplin/src/joplin-1.0.167/ElectronClient/app/node_modules/.bin/electron-rebuild" "

Nebucatnetzer commented on 2019-09-10 20:34 (UTC)

I can confirm as well that it's upgrading now. Thanks a ton for your work. It's much nice to have the application as a real package instead of an appimage.

johnfocker commented on 2019-09-10 14:13 (UTC)

@masterkorp it now builds and runs smoothly here. Thanks!

tovo commented on 2019-09-10 14:08 (UTC)

Great, It works for me now! Cheers

masterkorp commented on 2019-09-10 13:54 (UTC)

@johnfocker, I did update, can you please re test?

johnfocker commented on 2019-09-10 10:15 (UTC)

Same problem as @Nebucatnetzer here.

gwenlune commented on 2019-09-08 21:10 (UTC) (edited on 2019-09-08 21:14 (UTC) by gwenlune)

I have the error :

-> Téléchargement de v1.0.165.zip…

** Resuming transfer from byte position 1331200

% Total    % Received % Xferd  Average Speed   Time    Time     Time  Current

                             Dload  Upload   Total   Spent    Left  Speed

100   123    0   123    0     0    544      0 --:--:-- --:--:-- --:--:--   544

0 20.6M    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0

curl: (33) HTTP server doesn't seem to support byte ranges. Cannot resume.

==> ERREUR : Erreur lors du téléchargement de <https://github.com/laurent22/joplin/archive/v1.0.165.zip>

 Abandon…

Error downloading sources: joplin

I don't find solution. Any idea ?

GsMFb924 commented on 2019-09-06 18:46 (UTC)

Per Hal5000, the package builds with the LTS node versions, electron desktop app works but the CLI gives us a module error: ~ $ joplin internal/modules/cjs/loader.js:638 throw err; Error: Cannot find module 'app-module-path'

Hal5000 commented on 2019-09-04 19:18 (UTC)

As a workaround to this problem, consider installing nodejs-lts-carbon for building. Solved the problem for me.

maclinuxfree commented on 2019-09-03 21:22 (UTC)

Same here as @Nebucatnetzer.

paulstrait commented on 2019-09-03 17:18 (UTC)

Same problem as @Nebucatnetzer.

tovo commented on 2019-09-03 08:06 (UTC)

Hi all, Same problem as @Nebucatnetzer here for an update from 1.0.161 version to the latest

Nebucatnetzer commented on 2019-09-02 16:53 (UTC)

I can't install the 1.165 version. I get the following error even after a clean build:

./src/async.h:29:52: warning: cast between incompatible function types from ‘void (*)(uv_async_t*, int)’ {aka ‘void (*)(uv_async_s*, int)’} to ‘uv_async_cb’ {aka ‘void (*)(uv_async_s*)’} [-Wcast-function-type]
make: *** [node_sqlite3.target.mk:125: Release/obj.target/node_sqlite3/src/database.o] Error 1
make: Leaving directory '/home/andreas/.cache/yay/joplin/src/joplin-1.0.165/ElectronClient/app/node_modules/sqlite3/build'
gyp ERR! build error 
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/lib/node_modules/node-gyp/lib/build.js:190:23)
gyp ERR! stack     at ChildProcess.emit (events.js:209:13)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:272:12)
gyp ERR! System Linux 5.2.9-arch1-1-ARCH
gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/node-gyp/bin/node-gyp.js" "build" "--fallback-to-build" "--module=/home/andreas/.cache/yay/joplin/src/joplin-1.0.165/ElectronClient/app/node_modules/sqlite3/lib/binding/node-v72-linux-x64/node_sqlite3.node" "--module_name=node_sqlite3" "--module_path=/home/andreas/.cache/yay/joplin/src/joplin-1.0.165/ElectronClient/app/node_modules/sqlite3/lib/binding/node-v72-linux-x64" "--napi_version=4" "--node_abi_napi=napi" "--napi_build_version=0" "--node_napi_label=node-v72"
gyp ERR! cwd /home/andreas/.cache/yay/joplin/src/joplin-1.0.165/ElectronClient/app/node_modules/sqlite3
gyp ERR! node -v v12.9.1
gyp ERR! node-gyp -v v5.0.2
gyp ERR! not ok 
node-pre-gyp ERR! build error 
node-pre-gyp ERR! stack Error: Failed to execute '/usr/bin/node /usr/lib/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --module=/home/andreas/.cache/yay/joplin/src/joplin-1.0.165/ElectronClient/app/node_modules/sqlite3/lib/binding/node-v72-linux-x64/node_sqlite3.node --module_name=node_sqlite3 --module_path=/home/andreas/.cache/yay/joplin/src/joplin-1.0.165/ElectronClient/app/node_modules/sqlite3/lib/binding/node-v72-linux-x64 --napi_version=4 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=node-v72' (1)
node-pre-gyp ERR! stack     at ChildProcess.<anonymous> (/home/andreas/.cache/yay/joplin/src/joplin-1.0.165/ElectronClient/app/node_modules/node-pre-gyp/lib/util/compile.js:83:29)
node-pre-gyp ERR! stack     at ChildProcess.emit (events.js:209:13)
node-pre-gyp ERR! stack     at maybeClose (internal/child_process.js:1021:16)
node-pre-gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5)
node-pre-gyp ERR! System Linux 5.2.9-arch1-1-ARCH
node-pre-gyp ERR! command "/usr/bin/node" "/home/andreas/.cache/yay/joplin/src/joplin-1.0.165/ElectronClient/app/node_modules/.bin/node-pre-gyp" "install" "--fallback-to-build"
node-pre-gyp ERR! cwd /home/andreas/.cache/yay/joplin/src/joplin-1.0.165/ElectronClient/app/node_modules/sqlite3
node-pre-gyp ERR! node -v v12.9.1
node-pre-gyp ERR! node-pre-gyp -v v0.11.0
node-pre-gyp ERR! not ok 
Failed to execute '/usr/bin/node /usr/lib/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --module=/home/andreas/.cache/yay/joplin/src/joplin-1.0.165/ElectronClient/app/node_modules/sqlite3/lib/binding/node-v72-linux-x64/node_sqlite3.node --module_name=node_sqlite3 --module_path=/home/andreas/.cache/yay/joplin/src/joplin-1.0.165/ElectronClient/app/node_modules/sqlite3/lib/binding/node-v72-linux-x64 --napi_version=4 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=node-v72' (1)
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: 7zip-bin-win@2.2.0 (node_modules/7zip-bin-win):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for 7zip-bin-win@2.2.0: wanted {"os":"win32","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: 7zip-bin-mac@1.0.1 (node_modules/7zip-bin-mac):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for 7zip-bin-mac@1.0.1: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.4 (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.4: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.0.6 (node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.0.6: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! sqlite3@4.0.6 install: `node-pre-gyp install --fallback-to-build`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the sqlite3@4.0.6 install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/andreas/.npm/_logs/2019-09-02T16_50_16_079Z-debug.log
==> ERROR: A failure occurred in build().
    Aborting...
Error making: joplin

hillbicks commented on 2019-07-20 17:59 (UTC)

@masterkorp: Could you please try this config in a clean environment? Since there are so many people with the same problem, it seems that it is something specific to your system. Maybe change the path to an absolute one?

I also don't see why joplin.desktop should be anywhere else than joplin.sh and joplin-desktop.sh. All three files are included in the source, yet joplin.desktop is the only file located in the parent dir according to your PKGBUILD. Can you check where the joplin.desktop is located on your system? I would assume it is in the parent dir, hence why it is working for you and failing for everybody else.

Thanks again

radio_rogal commented on 2019-07-07 16:09 (UTC) (edited on 2019-07-07 16:10 (UTC) by radio_rogal)

On my opinion you should remove these files from the package:

  • /usr/share/joplin/resources/app/node_modules/7zip-bin-linux/arm64/7za
  • /usr/share/joplin/resources/app/node_modules/7zip-bin-linux/ia32/7za
  • /usr/share/joplin/resources/app/node_modules/7zip-bin-linux/arm/7za

saturn_knight commented on 2019-06-27 01:12 (UTC)

@masterkorp Yes it does, if I don't edit the PKGBUILD file it fails. I just tried it again manually before posting this and still received the error:

install: cannot stat '../joplin.desktop': No such file or directory

masterkorp commented on 2019-06-25 16:06 (UTC)

@saturn_knight But cloning and using makepkg directly? Does it fail?

saturn_knight commented on 2019-06-14 10:14 (UTC)

I still have the same problem as @hillbicks. I use Pikaur, but it also fails when I manually use makepkg. I have to remove the ../ before joplin.desktop in order for it to build successfully. I don't understand what is different between our environments that on @masterkorp system it fails without the ../ but on ours it fails with it. There must be something strange going on somewhere...

hillbicks commented on 2019-06-13 20:25 (UTC)

@masterkorp:

It basically says file or directory not found, package helper is trizen. If you look through the last two or three pages, there are several more people with the same problem. If you need further info or logs, just let me know.

blixawillbargeld commented on 2019-06-12 15:53 (UTC)

Is there a way to install only the cli version of joplin?

masterkorp commented on 2019-06-11 10:48 (UTC)

@hillbicks I would remove it it would make it full.

But that is the actual command, it works with makepkg and AUR warpers like yay, what error are you getting?

hillbicks commented on 2019-06-06 17:08 (UTC)

@masterkorp Could you please fix the line 68 and remove the ../ before joplin.desktop in the pkgfile?

Thanks!

ceri commented on 2019-06-06 05:37 (UTC)

This doesn't build in a clean chroot.

Requires python as a makedep, and the following change:

from: install -Dm644 ../joplin.desktop ${pkgdir}/usr/share/applications/joplin.desktop

to: install -Dm644 joplin.desktop ${pkgdir}/usr/share/applications/joplin.desktop

nhrjr commented on 2019-06-05 09:47 (UTC)

@waasl I had the same problem, and your solution worked for me. Patching this would be nice.

zethex commented on 2019-06-01 02:06 (UTC)

Build fails if package python is not installed, the error is basically /bin/sh: python: command not found. So installing python fixed it for me. Maybe add it as a dependency?

kmaris commented on 2019-05-23 16:51 (UTC)

Also worth noting that after installing I needed to fix line endings in the gui startup script:

sudo dos2unix /usr/bin/joplin-desktop

kmaris commented on 2019-05-23 16:37 (UTC) (edited on 2019-05-23 16:37 (UTC) by kmaris)

Looks like some new SHA's are in order for joplin-1.0.152-1 joplin.desktop and joplin-desktop.sh:

diff --git a/PKGBUILD b/PKGBUILD
index 613ccfe..beb935b 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -15,8 +15,8 @@ url="https://joplin.cozic.net"
 license=("MIT")
 source=("${pkgname}.desktop" "joplin-desktop.sh" "joplin.sh"
         "https://github.com/laurent22/joplin/archive/v${pkgver}.zip")
-sha256sums=('42b0c2a2b1630a8d6dc3bdc9e30f083defd7e6f882d66c986fe8ff9cde12f77e'
-            '41bfdc95a6ee285eb644d05eb3bded72a83950d4720c3c8058ddd3c605cd625d'
+sha256sums=('fb2a62bbeb59bced766f182dc28c9c1c8379a2a762212fdadc542dadbae07ed3'
+            '9c90d407669c2b67887d7c7d9c6e1d3d19df39cfb099cd4d7aeb46c2e1727f9c'
             '5245da6f5f647d49fbe044b747994c9f5a8e98b3c2cd02757dd189426a677276'
             '4137235f9ac32ce0ec063f5b6d757aa75e2424ea89ba09eb0aa930cd00d0e600')

shscs911 commented on 2019-05-18 15:26 (UTC) (edited on 2019-05-18 15:27 (UTC) by shscs911)

@heyeshuang Thanks, mate. The upgrade finished flawlessly.

heyeshuang commented on 2019-05-18 14:25 (UTC) (edited on 2019-05-18 14:26 (UTC) by heyeshuang)

hello @shscs911 , I faced same problem as yours. Did you ever run npm config set registry or change your npm mirror? Some mirrors haven't sync the joplin-turndown-plugin-gfm@1.0.8 yet. Running

npm config set registry https://registry.npmjs.org

to change it back solved this problem.

shscs911 commented on 2019-05-16 13:50 (UTC)

@masterkorp No, I tried to update Joplin via Pamac as usual, but got this error instead. If I build it using makepkg will it get installed over the existing application or installed as another application? Sorry, I'm new to this.

masterkorp commented on 2019-05-15 10:46 (UTC)

I cannot reproduce this. @shscs911

Have you tried building with makepkg -fc ?

shscs911 commented on 2019-05-15 07:10 (UTC) (edited on 2019-05-15 07:21 (UTC) by shscs911)

My current version is Joplin 1.0.142. Cannot install the latest build (1.0.152):

npm ERR! code ETARGET
npm ERR! notarget No matching version found for joplin-turndown-plugin-gfm@1.0.8
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.
npm ERR! notarget 
npm ERR! notarget It was specified as a dependency of 'build'
npm ERR! notarget

Debug Log: https://pastebin.com/iTqHuPDB

waasl commented on 2019-05-02 07:07 (UTC)

sorry ignore my previous comment, it did not work.

the solution for me was to edit PKGBUILD line 68: from: install -Dm644 ../joplin.desktop ${pkgdir}/usr/share/applications/joplin.desktop

to: install -Dm644 joplin.desktop ${pkgdir}/usr/share/applications/joplin.desktop

(remove '../' before joplin.desktop)

waasl commented on 2019-05-02 06:37 (UTC)

I could not install: error something like: "cannot stat no such file or directory"

Fix: locate joplin.desktop install -Dm644 joplin.desktop ${pkgdir}/usr/share/applications/joplin.desktop

saturn_knight commented on 2019-04-12 10:16 (UTC) (edited on 2019-04-12 10:16 (UTC) by saturn_knight)

I was unable to build version 1.0.142-1 of the package without removing the ../ on the following line: install -Dm644 ../joplin.desktop ${pkgdir}/usr/share/applications/joplin.desktop

It gave an error that it couldn't stat the joplin.desktop file.

commented on 2019-04-12 08:43 (UTC)

I think the PKGBUILD needs a runtime dependency on libxss; electron seems to link this library, and the desktop app won't start if it's missing.

silicht commented on 2019-04-04 06:27 (UTC)

changing pkgver to 1.0.142 and last sha256sums to 11f22415dc49793c7f024f48c0b20ee04aa32254ee0d0a87f843d5f12c7527a3 seems to be enough for updating to 1.0.142.

jeagoss commented on 2019-03-31 01:15 (UTC)

The following patch was used to build in a clean chroot per https://wiki.archlinux.org/index.php/DeveloperWiki:Building_in_a_clean_chroot

https://pastebin.com/kLds16vg

CodeFox commented on 2019-03-06 14:21 (UTC)

@masterkorp is it possible to get this package updated to the right hash? the 135 version also has a bad hash sum check.

gonesimera commented on 2019-03-04 09:05 (UTC)

@sseneca Thank you, it is updating now.

sseneca commented on 2019-03-02 13:24 (UTC)

@nunoun and @gonesimera

You have to replace the sha256sum that @petsam posted with the first sha256sum found in the array "sha256sums".

So it should look like this:

sha256sums=('01bf4f7e311d79b7e309e158c46b6dd321194eb17e90f09db3ff41b75f35fffa'
            ...)

gonesimera commented on 2019-03-02 07:43 (UTC)

I have exactly the same problem as @nunoun

==> Validating source files with sha256sums... joplin.desktop ... FAILED joplin-desktop.sh ... Passed joplin.sh ... Passed v1.0.135.zip ... Passed ==> ERROR: One or more files did not pass the validity check!

If I use the sha256sum suggested by @petsam I get the following error: ==> ERROR: Integrity checks (sha256) differ in size from the source array.

Kunda commented on 2019-03-01 21:45 (UTC)

@petsam thank you that worked.

nunonun commented on 2019-03-01 09:24 (UTC) (edited on 2019-03-01 09:30 (UTC) by nunonun)

==> Validating source files with sha256sums... joplin.desktop ... FAILED joplin-desktop.sh ... Passed joplin.sh ... Passed v1.0.135.zip ... Passed ==> ERROR: One or more files did not pass the validity check!

If I use the sha256sum suggested by @petsam I get the following error: ==> ERROR: Integrity checks (sha256) differ in size from the source array.

petsam commented on 2019-02-28 20:54 (UTC)

New sha256sum for joplin.desktop 01bf4f7e311d79b7e309e158c46b6dd321194eb17e90f09db3ff41b75f35fffa

konig commented on 2019-02-28 14:05 (UTC) (edited on 2019-02-28 14:35 (UTC) by konig)

the sums of desktop.sh is invalid

Validating source files with sha256sums... joplin.desktop ... FAILED

You can skip te validation string, however this should be fixed regardless

griffin commented on 2019-02-27 17:36 (UTC)

He forgot to update the sha sums. Should be fixed soon.

rodneyck commented on 2019-02-27 16:17 (UTC)

Looks like the validation error is back again. I could not install the latest update.

simona commented on 2019-02-27 12:25 (UTC)

Validazione di source file con sha256sums... joplin.desktop ... NON RIUSCITO

hax commented on 2019-02-27 12:08 (UTC)

hi, the sha256 checksum for joplin.desktop has changed again. The correct you should be: 6768685a318bbdf3f0681197ca189b04d8640ac2764bdb8459af70ec4691c67b

if you change this in PKGBUILD at least you are able to compile and install manually. BRGDS

masterkorp commented on 2019-02-27 10:26 (UTC)

@gatlinnewhouse I cannot reproduce this. erro. since the makepkg comamnd should be launched from the main folder, in the pkg/ folder

gatlinnewhouse commented on 2019-02-18 16:33 (UTC)

I had an error in the PKGBUILD that made it so it would not install (with yay) unless I changed:

install -Dm644 ../joplin.desktop ${pkgdir}/usr/share/applications/joplin.desktop

to:

install -Dm644 joplin.desktop ${pkgdir}/usr/share/applications/joplin.desktop

i_magnific0 commented on 2019-02-03 11:16 (UTC)

Hi, thanks for maintaining. It seems joplin.desktop file was changed. It doesn't psas validation anymore. The new sha256 sum is: 0bd2d4f055d99a5c989dc7d6bce5e1217f161f1e3cf09c9fb8b0045347baae88

Cheers!

rodneyck commented on 2019-02-02 15:18 (UTC)

Same Validation error... ==> Validating source files with sha256sums... joplin.desktop ... FAILED joplin-desktop.sh ... Passed joplin.sh ... Passed v1.0.125.zip ... Passed ==> ERROR: One or more files did not pass the validity check!

FunctionalHacker commented on 2019-02-01 23:54 (UTC)

Yeah I can confirm, pkgsums need to be updated

simona commented on 2019-02-01 23:21 (UTC)

==> Validazione di source file con sha256sums... joplin.desktop ... NON RIUSCITO => ERRORE: Uno o più file non hanno superato il controllo di validità!

jeythekey commented on 2019-01-24 01:46 (UTC)

I had to remove '../' in front of joplin.desktop in L 68.

simona commented on 2019-01-22 22:18 (UTC)

eureka! successfull compiled. thanks.

simona commented on 2019-01-22 22:12 (UTC)

news to compile whithout workarounds?

simona commented on 2018-12-29 14:39 (UTC)

Package conflicts found: -> Installing nodejs-lts-carbon will remove: nodejs

commented on 2018-12-25 21:29 (UTC)

nodejs works fine. build with nodejs v11.5.0 was successful

sl89 commented on 2018-12-22 16:50 (UTC)

nodejs-lts-carbon and nodejs conflict, users will be asked to uninstall nodejs and all packages that depend on it to install joplin. If it is no longer required, as iboyperson says, please remove it as dependency.

KloolK commented on 2018-12-22 10:37 (UTC)

I had to install libxss for joplin-desktop to work. Without it, I'd get: ./joplin: error while loading shared libraries: libXss.so.1: cannot open shared object file: No such file or directory

tjquillan commented on 2018-12-21 21:53 (UTC)

1.0.119 fixed the requirement of nodejs-lts-carbon. It build fine with regular nodejs.

rodneyck commented on 2018-12-20 16:01 (UTC)

Can the maintainer please update. It is now several versions behind. Thank you.

tinux commented on 2018-12-12 15:28 (UTC) (edited on 2018-12-12 15:28 (UTC) by tinux)

Two small comments:

  • With nodejs-lts-carbon instead of nodejs this builds fine.
  • gconf is required to run it, not only for building.

nicoulaj commented on 2018-12-02 21:22 (UTC)

Does not build, 3 versions behind

simona commented on 2018-11-22 16:40 (UTC)

18649 verbose stack Error: sqlite3@3.1.13 install: node-pre-gyp install --fallback-to-build 18649 verbose stack Exit status 1 18649 verbose stack at EventEmitter.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:301:16) 18649 verbose stack at EventEmitter.emit (events.js:182:13) 18649 verbose stack at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14) 18649 verbose stack at ChildProcess.emit (events.js:182:13) 18649 verbose stack at maybeClose (internal/child_process.js:978:16) 18649 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:265:5) 18650 verbose pkgid sqlite3@3.1.13 18651 verbose cwd /home/simona/.cache/aurman/joplin/src/joplin-1.0.114/ElectronClient/app 18652 verbose Linux 4.19.3-1-ck-skylake 18653 verbose argv "/usr/bin/node" "/bin/npm" "install" 18654 verbose node v11.2.0 18655 verbose npm v6.4.1 18656 error code ELIFECYCLE 18657 error errno 1 18658 error sqlite3@3.1.13 install: node-pre-gyp install --fallback-to-build 18658 error Exit status 1 18659 error Failed at the sqlite3@3.1.13 install script. 18659 error This is probably not a problem with npm. There is likely additional logging output above. 18660 verbose exit [ 1, true ]

snoopy commented on 2018-11-21 01:35 (UTC)

FWIW this would not build on my system. With pdizzle's workaround it went through yay -S joplin successfully but wasn't actually installed.

Crossing my fingers for the next release.

pdizzle commented on 2018-11-19 02:00 (UTC) (edited on 2018-11-19 02:03 (UTC) by pdizzle)

for anyone that would like to install this, using nvm to switch node versions works. 8.12 lts did not work, 8.0 did for me:

https://github.com/creationix/nvm#usage

$ nvm install 8.0
$ nvm use 8.0

then makepkg or install from aur (yay, pacaur, aura, ...)

EDIT: installation succeeded, the desktop app seems to work, but CLI does not

teke commented on 2018-11-09 13:04 (UTC) (edited on 2018-11-09 13:09 (UTC) by teke)

Bonjour,

Snif (^_')

../src/async.h:29:52: warning: transtypage entre types de fonctions incompatibles de « void (*)(uv_async_t*, int) » {aka « void (*)(uv_async_s*, int) »} vers « uv_async_cb » {aka « void (*)(uv_async_s*) »} [-Wcast-function-type]
../src/database.cc: Au niveau global:
../src/database.cc:689:1: erreur fatale: ouverture du fichier de dépendances ./Release/.deps/Release/obj.target/node_sqlite3/src/database.o.d.raw: Aucun fichier ou dossier de ce type
compilation terminée.
make: *** [node_sqlite3.target.mk:121: Release/obj.target/node_sqlite3/src/database.o] Error 1
make : on quitte le répertoire « /tmp/yaourt-tmp-rc/aur-joplin/src/joplin-1.0.114/ElectronClient/app/node_modules/sqlite3/build »
gyp ERR! build error 
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/lib/node_modules/node-gyp/lib/build.js:262:23)
gyp ERR! stack     at ChildProcess.emit (events.js:182:13)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:246:12)
gyp ERR! System Linux 4.18.16-arch1-1-ARCH
gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/node-gyp/bin/node-gyp.js" "build" "--fallback-to-build" "--module=/tmp/yaourt-tmp-rc/aur-joplin/src/joplin-1.0.114/ElectronClient/app/node_modules/sqlite3/lib/binding/node-v67-linux-x64/node_sqlite3.node" "--module_name=node_sqlite3" "--module_path=/tmp/yaourt-tmp-rc/aur-joplin/src/joplin-1.0.114/ElectronClient/app/node_modules/sqlite3/lib/binding/node-v67-linux-x64"
gyp ERR! cwd /tmp/yaourt-tmp-rc/aur-joplin/src/joplin-1.0.114/ElectronClient/app/node_modules/sqlite3
gyp ERR! node -v v11.1.0
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok 
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: 7zip-bin-win@2.1.1 (node_modules/7zip-bin-win):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for 7zip-bin-win@2.1.1: wanted {"os":"win32","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: 7zip-bin-mac@1.0.1 (node_modules/7zip-bin-mac):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for 7zip-bin-mac@1.0.1: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.4 (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.4: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! sqlite3@3.1.13 install: `node-pre-gyp install --fallback-to-build`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the sqlite3@3.1.13 install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/rc/.npm/_logs/2018-11-09T13_00_14_543Z-debug.log
==> ERREUR : Une erreur s’est produite dans build().
    Abandon…
==> ERREUR : Makepkg n'a pas pu construire joplin.

simona commented on 2018-11-05 23:32 (UTC)

18636 warn optional SKIPPING OPTIONAL DEPENDENCY: 7zip-bin-win@2.1.1 (node_modules/7zip-bin-win): 18637 warn notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for 7zip-bin-win@2.1.1: wanted {"os":"win32","arch":"any"} (current: {"os":"linux","arch":"x64"}) 18638 verbose notsup SKIPPING OPTIONAL DEPENDENCY: Valid OS: win32 18638 verbose notsup SKIPPING OPTIONAL DEPENDENCY: Valid Arch: any 18638 verbose notsup SKIPPING OPTIONAL DEPENDENCY: Actual OS: linux 18638 verbose notsup SKIPPING OPTIONAL DEPENDENCY: Actual Arch: x64 18639 warn optional SKIPPING OPTIONAL DEPENDENCY: 7zip-bin-mac@1.0.1 (node_modules/7zip-bin-mac): 18640 warn notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for 7zip-bin-mac@1.0.1: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"}) 18641 verbose notsup SKIPPING OPTIONAL DEPENDENCY: Valid OS: darwin 18641 verbose notsup SKIPPING OPTIONAL DEPENDENCY: Valid Arch: any 18641 verbose notsup SKIPPING OPTIONAL DEPENDENCY: Actual OS: linux 18641 verbose notsup SKIPPING OPTIONAL DEPENDENCY: Actual Arch: x64 18642 warn optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.4 (node_modules/fsevents): 18643 warn notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.4: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"}) 18644 verbose notsup SKIPPING OPTIONAL DEPENDENCY: Valid OS: darwin 18644 verbose notsup SKIPPING OPTIONAL DEPENDENCY: Valid Arch: any 18644 verbose notsup SKIPPING OPTIONAL DEPENDENCY: Actual OS: linux 18644 verbose notsup SKIPPING OPTIONAL DEPENDENCY: Actual Arch: x64 18645 verbose stack Error: sqlite3@3.1.13 install: node-pre-gyp install --fallback-to-build 18645 verbose stack Exit status 1 18645 verbose stack at EventEmitter.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:301:16) 18645 verbose stack at EventEmitter.emit (events.js:182:13) 18645 verbose stack at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14) 18645 verbose stack at ChildProcess.emit (events.js:182:13) 18645 verbose stack at maybeClose (internal/child_process.js:970:16) 18645 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:257:5) 18646 verbose pkgid sqlite3@3.1.13 18647 verbose cwd /home/simona/.cache/aurman/joplin/src/joplin-1.0.114/ElectronClient/app 18648 verbose Linux 4.18.17-2-ck-skylake 18649 verbose argv "/usr/bin/node" "/bin/npm" "install" 18650 verbose node v11.1.0 18651 verbose npm v6.4.1 18652 error code ELIFECYCLE 18653 error errno 1 18654 error sqlite3@3.1.13 install: node-pre-gyp install --fallback-to-build 18654 error Exit status 1 18655 error Failed at the sqlite3@3.1.13 install script. 18655 error This is probably not a problem with npm. There is likely additional logging output above. 18656 verbose exit [ 1, true ]

sl89 commented on 2018-11-05 15:26 (UTC)

https://github.com/laurent22/joplin/issues/467 https://github.com/laurent22/joplin/commit/3fc54d7ffdb42efdd3a825a16dca6fc37e31c555

The sqlite version issue should have been fixed on v1.0.114, but apparently it hasn't. Probably somebody who understands this better than me should submit an issue.

nrth3rnlb commented on 2018-11-04 12:16 (UTC)

18648 verbose stack Error: sqlite3@3.1.13 install: `node-pre-gyp install --fallback-to-build`
18648 verbose stack Exit status 1
18648 verbose stack     at EventEmitter.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:301:16)
18648 verbose stack     at EventEmitter.emit (events.js:182:13)
18648 verbose stack     at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
18648 verbose stack     at ChildProcess.emit (events.js:182:13)
18648 verbose stack     at maybeClose (internal/child_process.js:970:16)
18648 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:257:5)
18649 verbose pkgid sqlite3@3.1.13

simona commented on 2018-10-31 21:37 (UTC)

npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! sqlite3@3.1.13 install: node-pre-gyp install --fallback-to-build npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the sqlite3@3.1.13 install script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

griffin commented on 2018-10-29 01:10 (UTC)

I just made a PR to update to the latest version. Node issues still seem to be in effect because of those sqlite compatibility issues expressed below, which I think is a Joplin based thing that needs to be fixed at that end, not PKGBUILD. Switching to Node 8 fixes that issue.

Phlogiston commented on 2018-10-23 18:59 (UTC)

Fails too here:

node-pre-gyp ERR! Tried to download(403): https://mapbox-node-binary.s3.amazonaws.com/sqlite3/v3.1.13/node-v64-linux-x64.tar.gz node-pre-gyp ERR! Pre-built binaries not found for sqlite3@3.1.13 and node@10.12.0 (node-v64 ABI) (falling back to source compile with node-gyp) node-pre-gyp ERR! Tried to download(undefined): https://mapbox-node-binary.s3.amazonaws.com/sqlite3/v3.1.13/node-v64-linux-x64.tar.gz node-pre-gyp ERR! Pre-built binaries not found for sqlite3@3.1.13 and node@10.12.0 (node-v64 ABI) (falling back to source compile with node-gyp)


emilhuseynli commented on 2018-10-23 12:37 (UTC)

Build fails for me after update to v1.0.111:

==> Removing existing $srcdir/ directory... ==> Extracting sources... -> Extracting v1.0.111.zip with bsdtar ==> Sources are ready. ==> Making package: joplin 1.0.111-1 (Tue 23 Oct 2018 02:36:22 PM CEST) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> WARNING: Using existing $srcdir/ tree ==> Starting build()... npm WARN tools@1.0.0 No description npm WARN tools@1.0.0 No repository field.

npm ERR! code E401 npm ERR! 401 Unauthorized: dashdash@1.14.1

npm ERR! A complete log of this run can be found in: npm ERR! /$HOME/.npm/_logs/2018-10-23T12_36_23_034Z-debug.log ==> ERROR: A failure occurred in build(). Aborting... Error making: joplin

griffin commented on 2018-10-13 04:58 (UTC)

Was able to install perfectly fine from pkgbuild with rsync and node 8.12.0. Using n to easily switch versions of node has been the best way for me to build. Updating AUR should be a go.

bjo commented on 2018-10-08 13:21 (UTC)

You updated the PKGBUILD in your git repo, but not in the AUR ;)

bjo commented on 2018-10-01 13:57 (UTC)

1.0.111 is out.

moonbas3 commented on 2018-09-17 07:38 (UTC) (edited on 2018-09-17 07:40 (UTC) by moonbas3)

I also needed a newer nodejs version for Atom so I couldn't just revert to the lts package.

What I did was to: force remove nodejs -> install nodejs-lts-carbon -> install Joplin -> remove nodejs-lts-carbon -> install back nodejs

FunctionalHacker commented on 2018-09-15 16:50 (UTC)

I installed this package on another machine that didn't build it, and had to manually install gconf, because joplin-desktop requires it to run. So gconf isn't just a build dependency it seems.

simona commented on 2018-09-10 18:11 (UTC)

I don't install nodejs-lts-carbon... they will do a real fix?

bjo commented on 2018-08-29 06:07 (UTC)

This is a known issue: https://github.com/masterkorp/joplin-pkgbuild/issues/9

jancici commented on 2018-08-28 19:36 (UTC)

I am trying so solve "node-gyp" error with installing nodejs-lts-carbon.

BUT

yay -S nodejs-lts-carbon resolving dependencies... looking for conflicting packages... :: nodejs-lts-carbon and nodejs are in conflict. Remove nodejs? [y/N] y error: failed to prepare transaction (could not satisfy dependencies) :: removing nodejs breaks dependency 'nodejs>=10' required by apm Error installing repo packages

sudo whoneeds.sh apm :( Required By : atom

simona commented on 2018-08-26 09:46 (UTC)

make: *** [sharp.target.mk:125: Release/obj.target/sharp/src/common.o] Error 1 make: uscita dalla directory "/home/simona/.cache/aurman/joplin/src/joplin-1.0.104/CliClient/build/node_modules/sharp/build" gyp ERR! build error gyp ERR! stack Error: make failed with exit code: 2 gyp ERR! stack at ChildProcess.onExit (/usr/lib/node_modules/node-gyp/lib/build.js:262:23) gyp ERR! stack at ChildProcess.emit (events.js:182:13) gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:239:12) gyp ERR! System Linux 4.18.4-zen1-1-zen gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/node-gyp/bin/node-gyp.js" "rebuild" gyp ERR! cwd /home/simona/.cache/aurman/joplin/src/joplin-1.0.104/CliClient/build/node_modules/sharp gyp ERR! node -v v10.9.0 gyp ERR! node-gyp -v v3.8.0 gyp ERR! not ok npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! sharp@0.18.4 install: node-gyp rebuild npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the sharp@0.18.4 install script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in: npm ERR! /home/simona/.npm/_logs/2018-08-26T09_45_24_243Z-debug.log ==> ERRORE: Si è verificato un errore in build().

erikfk commented on 2018-07-05 20:09 (UTC)

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

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

https://pastebin.com/3YSV8HeJ

felmey commented on 2018-06-17 16:32 (UTC) (edited on 2018-06-17 16:49 (UTC) by felmey)

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

@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 (UTC)

@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 (UTC)

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

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

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

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

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?

bossi commented on 2018-04-21 05:41 (UTC) (edited on 2018-04-21 05:48 (UTC) by bossi)

Thanks for setting up this AUR, masterkorp.

I'm not sure if this is the conventional way to contribute suggestions, please redirect me if not.

I ran into an issue where the CLI client failed to load a locales/index.js module (Error: Cannot find module '../locales/index.js' - officially discussed here).

As suggested by the author, the following patch in the PKGBUILD seems to fix the issue:

diff --git a/PKGBUILD b/PKGBUILD
index fa80d54..ad61b78 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -35,6 +35,8 @@ build() {
        "${srcdir}/${pkgname}-${pkgver}/CliClient/build/"
   rsync -a --delete "${srcdir}/${pkgname}-${pkgver}/ReactNativeClient/lib/" \
        "${srcdir}/${pkgname}-${pkgver}/CliClient/build/lib"
+  rsync -a --delete "${srcdir}/${pkgname}-${pkgver}/ReactNativeClient/locales/" \
+       "${srcdir}/${pkgname}-${pkgver}/CliClient/build/locales/"
   cp "package.json" "${srcdir}/${pkgname}-${pkgver}/CliClient/build"
   cp "package-lock.json" "${srcdir}/${pkgname}-${pkgver}/CliClient/build"

Cheers~

PS.: Big shout-out to the guys at the linux-mint podcast for spreading the word about Joplin!