@trumee Turns out, that's a python error. Install python2 and it should be fixed.
Search Criteria
Package Details: joplin 3.2.13-2
Package Actions
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: | AGPL-3.0-or-later |
Groups: | joplin |
Conflicts: | joplin-appimage, joplin-beta, joplin-beta-appimage, joplin-electron |
Submitter: | masterkorp |
Maintainer: | dosenpils |
Last Packager: | dosenpils |
Votes: | 268 |
Popularity: | 2.00 |
First Submitted: | 2018-04-18 16:33 (UTC) |
Last Updated: | 2025-03-12 23:14 (UTC) |
Dependencies (17)
- coreutils (coreutils-gitAUR, coreutils-selinuxAUR, coreutils-uutilsAUR, coreutils-uutils-symlinkAUR)
- libsecret
- nodejs (nodejs-gitAUR, python-nodejs-wheelAUR, nodejs-lts-iron, nodejs-lts-jod)
- python (python37AUR, python311AUR, python310AUR)
- electron (make)
- git (git-gitAUR, git-glAUR) (make)
- jq (jq-gitAUR, jaq-binAUR) (make)
- libgsf (libgsf-gitAUR) (make)
- libxcrypt-compat (make)
- node-gyp (corepackerAUR) (make)
- npm (corepackerAUR, python-nodejs-wheelAUR) (make)
- python (python37AUR, python311AUR, python310AUR) (make)
- python-setuptools (make)
- rsync (rsync-gitAUR, rsync-reflink-gitAUR, rsync-reflinkAUR) (make)
- yarn (yarn-pnpm-corepackAUR, corepackerAUR, yarn-berryAUR) (make)
- yq (make)
- libappindicator-gtk3 (optional) – for tray icon
Required by (0)
Sources (4)
Latest Comments
« First ‹ Previous 1 .. 21 22 23 24 25 26 27 28 29 30 31 .. 57 Next › Last »
loki7990 commented on 2021-04-05 17:50 (UTC)
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
Pinned Comments
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.
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