v1.8.1 is a pre-release not a stable release. I guess it should be unflagged.
Search Criteria
Package Details: joplin-desktop 3.0.14-1
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 - 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: | 263 |
Popularity: | 1.73 |
First Submitted: | 2018-04-18 16:33 (UTC) |
Last Updated: | 2024-07-29 19:54 (UTC) |
Dependencies (22)
- electron (electron-binAUR)
- gtk3 (gtk3-no_deadkeys_underlineAUR, gtk3-classicAUR, gtk3-classic-xfceAUR, gtk3-patched-filechooser-icon-viewAUR)
- libexif (libexif-gitAUR)
- libgsf (libgsf-gitAUR)
- libjpeg-turbo (mozjpeg-gitAUR, libjpeg-turbo-gitAUR, mozjpegAUR)
- libwebp (libwebp-gitAUR)
- libxss
- nodejs (nodejs-lts-fermiumAUR, nodejs-gitAUR, python-nodejs-wheelAUR, nodejs-lts-hydrogen, nodejs-lts-iron)
- nss (nss-hgAUR)
- orc
- electron (electron-binAUR) (make)
- git (git-gitAUR, git-glAUR) (make)
- jq (jq-gitAUR) (make)
- libgsf (libgsf-gitAUR) (make)
- node-gyp (corepackerAUR) (make)
- npm (corepackerAUR, python-nodejs-wheelAUR) (make)
- python (python37AUR, python311AUR, python310AUR) (make)
- python-setuptools (make)
- rsync (rsync-gitAUR, rsync-reflinkAUR, rsync-reflink-gitAUR) (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 .. 18 19 20 21 22 23 24 25 26 27 28 .. 54 Next › Last »
dwsong07 commented on 2021-03-30 04:23 (UTC)
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
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.
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