| 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: | 2.31 |
| First Submitted: | 2018-04-18 16:33 (UTC) |
| Last Updated: | 2025-03-12 23:14 (UTC) |
Build as of June 15 is failing. Failure starts at
/bin/sh: pkg-config: command not found gyp: Call to 'pkg-config --cflags libsecret-1' returned exit status 127 while in binding.gyp. while trying to load binding.gyp
with multiple gyp ERR! following. For what its worth, I am running Manjaro.
It’s not Zemoose’s fault. To keep certain packages from breaking and bugs from arising, Joplin’s main team is locking in specific versions. The dependencies have gotten managed better than they used to be but the whole “use new libraries where able to save time and code maintenance” approach is a bit problematic at times.
I wouldn’t recommend updating most packages if you can avoid it because of this.
@ZeMoose, just to be on the safe side, you should periodically check for npm update and resolve those security vulnerabilities by running npm audit fix.
this version is very outdated. please do something
Hey, all. My name is Brandon and I'm a member of the Joplin Team. I'm not one of the core devs but instead primarily am focused on Linux support and research.
Here's my credentials on the Forums: https://discourse.joplinapp.org/g/Team
Here's my main contribution to the project so far: https://github.com/laurent22/joplin/issues/3114
@ZeMoose, the dependencies of Joplin do concern me quite a bit myself. I'd love to hear which ones concern you the most.
If confronted with a 'fatal error: unknown table: settings' it helped me to
rm -rf ~/.config/Joplin/ ~/.config/joplin-desktop/
and reinstall joplin from the already compiled package.
Such was suggested here: https://discourse.joplinapp.org/t/solved-linux-fatal-error-unknown-table-settings/6253
Should I be concerned about the hundreds of low and moderate severity vulnerabilities reported by npm during the build process?
Building fails all the time.
@Al3xG sudo npm cache clean --force [1] does it help?
[1] https://stackoverflow.com/questions/15393821/npm-err-cb-never-called
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--nocheckflag.Thank you for your patience. Regards, Alfredo Palhares