Package Details: joplin-desktop 3.0.14-1

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 - Desktop
Upstream URL: https://joplinapp.org/
Keywords: markdown note notetaking productivity
Licenses: MIT
Groups: joplin
Conflicts: joplin-desktop-electron
Submitter: masterkorp
Maintainer: masterkorp
Last Packager: masterkorp
Votes: 262
Popularity: 1.54
First Submitted: 2018-04-18 16:33 (UTC)
Last Updated: 2024-07-29 19:54 (UTC)

Pinned Comments

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

« First ‹ Previous 1 .. 47 48 49 50 51 52 53 54 Next › Last »

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.

« First ‹ Previous 1 .. 47 48 49 50 51 52 53 54 Next › Last »