Why does build()
need to access my gpg private key?
Search Criteria
Package Details: joplin-desktop 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 - Desktop |
Upstream URL: | https://joplinapp.org/ |
Keywords: | markdown note notetaking productivity |
Licenses: | AGPL-3.0-or-later |
Groups: | joplin |
Conflicts: | joplin-desktop-electron |
Submitter: | masterkorp |
Maintainer: | dosenpils |
Last Packager: | dosenpils |
Votes: | 268 |
Popularity: | 3.20 |
First Submitted: | 2018-04-18 16:33 (UTC) |
Last Updated: | 2025-03-12 23:14 (UTC) |
Dependencies (23)
- electron
- gtk3 (gtk3-no_deadkeys_underlineAUR, gtk3-classic-xfceAUR, gtk3-classicAUR, 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-gitAUR, python-nodejs-wheelAUR, nodejs-lts-iron, nodejs-lts-jod)
- nss (nss-hgAUR)
- orc
- 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)
- Show 3 more dependencies...
Required by (0)
Sources (4)
Latest Comments
« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 .. 57 Next › Last »
iyanmv commented on 2024-04-08 01:13 (UTC)
brunofontes commented on 2024-04-01 12:21 (UTC)
Hello,
I went on this thread and tried to remove cache, then reinstalled the npm package. It worked for me.
phonemic commented on 2024-03-30 13:39 (UTC)
Getting this build error.
error This project's package.json defines "packageManager": "yarn@3.3.1". However the current global version of Yarn is 1.22.22.
Presence of the "packageManager" field indicates that the project is meant to be used with Corepack, a tool included by default with all official Node.js distributions starting from 16.9 and 14.19.
Corepack must currently be enabled by running corepack enable in your terminal. For more information, check out https://yarnpkg.com/corepack
dataprolet commented on 2024-03-26 23:20 (UTC)
Please either update the package or accept the help offered by @cuihao.
cuihao commented on 2024-03-18 22:41 (UTC)
Hi masterkorp, thank you for maintaining the package so far. I'm the maintainer of the joplin(-desktop) packages in the archlinuxcn repo. I have been using my version of PKGBUILD that at least builds so far with the latest version.
What do you think of using it? If you don't mind, I can help maintain the AUR package.
letscho commented on 2024-02-17 18:09 (UTC)
After installing this package I get this message:
Cannot find /usr/share/joplin/node_modules/joplin/app/
I tried both sudo corepack enable
and npm cache clean --force
, but it didn't help.
In the folder /usr/share/joplin
there is only:
package.json
package.tgz
README.md
yarn.lock
jcruz commented on 2024-02-12 15:12 (UTC)
I followed the suggestion of running sudo corepack enable
but I have the habit of uninstalling build dependencies after building, so yarn was uninstalled. After I enabled corepack, installing yarn was failing because yarn already existed. I had to disable corepack, install yarn explicitly (yuck), and reenable corepack. then the build worked.
If the project can only be built with corepack, can we get rid of the build dependency on yarn? otherwise, is there a way to get yarn 3.3.1 globally? why is version from pacman 1.x?
sergeimipt commented on 2024-01-07 14:22 (UTC)
I had the following error during joplin-desktop update:
-> Installing package
{
name: 'joplin',
packageManager: 'yarn@3.3.1'
}
error This project's package.json defines "packageManager": "yarn@3.3.1". However the current global version of Yarn is 1.22.21.
Presence of the "packageManager" field indicates that the project is meant to be used with Corepack, a tool included by default with all official Node.js distributions starting from 16.9 and 14.19.
Corepack must currently be enabled by running corepack enable in your terminal. For more information, check out https://yarnpkg.com/corepack.
I successfully fixed the error by running:
$ sudo corepack enable
tomacrisan commented on 2024-01-06 15:30 (UTC) (edited on 2024-01-06 15:33 (UTC) by tomacrisan)
masterkorp: I've been using your PKGBUILD file to build the 2.13 series of releases by only changing pkgver= and updating sha256sums=. I just built version 2.13.13 today when I saw your comment.
At some point about a month ago, I ran: $ npm cache clean --force
when I was experiencing build errors. Since then, I haven't had problems.
Unfortunately, while willing, I don't know what I can contribute to the conversation more than this; I appreciate your work in providing the build files.
masterkorp commented on 2023-12-23 17:50 (UTC)
Just for an update, I am having troubles upgrading the package to 2.13.10
https://discourse.joplinapp.org/t/cannot-build-for-arch-linux/34625
Any suggestions or ideas are welcome.
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