Search Criteria
Package Details: joplin 1.0.216-1
| 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 |
| Upstream URL: | https://joplinapp.org/ |
| Keywords: | markdown note notetaking productivity |
| Licenses: | |
| Submitter: | masterkorp |
| Maintainer: | masterkorp |
| Last Packager: | masterkorp |
| Votes: | 115 |
| Popularity: | 16.13 |
| First Submitted: | 2018-04-18 16:33 |
| Last Updated: | 2020-06-02 09:55 |
Dependencies (14)
- gtk3 (gtk3-donnatella, gtk3-cosy, gtk3-adwaita-3-32-git, gtk3-classic, gtk3-ubuntu, gtk3-typeahead, gtk3-patched-filechooser-icon-view, gtk3-mushrooms)
- libexif
- libgsf
- libjpeg-turbo (libjpeg-turbo-git, mozjpeg-git, mozjpeg)
- libwebp (libwebp-git)
- libxss
- nodejs (nodejs-git, nodejs6-bin, nodejs-ipv6, nodejs-lts-dubnium, nodejs-lts-erbium)
- nss (nss-hg)
- orc
- git (git-git) (make)
- npm (npm53, npm4, nodejs6-bin) (make)
- python (python-dbg) (make)
- rsync (rsync-git, rsync-fadvise) (make)
- libappindicator-gtk3 (libappindicator-gtk3-ubuntu, libappindicator-bzr) (optional) – for tray icon
Latest Comments
1 2 3 4 5 6 ... Next › Last »
bedwardly-down commented on 2020-05-22 23:21
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.
thelazyoxymoron commented on 2020-05-22 20:45
@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.
malcolm commented on 2020-05-21 13:56
this version is very outdated. please do something
RockhopperP commented on 2020-05-15 08:17
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
ZeMoose commented on 2020-05-08 03:58
Should I be concerned about the hundreds of low and moderate severity vulnerabilities reported by npm during the build process?
avndp commented on 2020-05-06 02:47
Building fails all the time.
vv181 commented on 2020-04-29 21:52
@imlonghao
It still does not work.
I'll put the log here:https://pastebin.com/3CfZQ0NR
imlonghao commented on 2020-04-23 01:36
@Al3xG
sudo npm cache clean --force[1] does it help?[1] https://stackoverflow.com/questions/15393821/npm-err-cb-never-called
Al3xG commented on 2020-04-22 20:23
I'm having the same "cb() never called!" error with the last 1.0.201 build. Any way to sort this out please? Thanks.
thelazyoxymoron commented on 2020-04-14 17:15
Please update the PKGBUILD. The latest version out is 1.0.200.