Actually, compiling with yay works fine now. Weird. I guess it's alright after all.
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 .. 32 33 34 35 36 37 38 39 40 41 42 .. 54 Next › Last »
macxcool commented on 2020-03-18 23:51 (UTC)
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.
<deleted-account> 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.
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