Package Base Details: joplin

Git Clone URL: https://aur.archlinux.org/joplin.git (read-only, click to copy)
Keywords: markdown note notetaking productivity
Submitter: masterkorp
Maintainer: masterkorp
Last Packager: masterkorp
Votes: 257
Popularity: 1.78
First Submitted: 2018-04-18 16:33 (UTC)
Last Updated: 2024-04-06 17:49 (UTC)

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.

  • joplin will contain the CLI application
  • joplin-desktop will contain the Desktop version

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

Latest Comments

« First ‹ Previous 1 .. 30 31 32 33 34 35 36 37 38 39 40 .. 53 Next › Last »

RockhopperP commented on 2020-05-15 08:17 (UTC)

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 (UTC)

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 (UTC)

Building fails all the time.

vv181 commented on 2020-04-29 21:52 (UTC)

@imlonghao

It still does not work.

I'll put the log here:https://pastebin.com/3CfZQ0NR

imlonghao commented on 2020-04-23 01:36 (UTC)

@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 (UTC)

I'm having the same "cb() never called!" error with the last 1.0.201 build. Any way to sort this out please? Thanks.

siddharthagolu commented on 2020-04-14 17:15 (UTC)

Please update the PKGBUILD. The latest version out is 1.0.200.

roachsinai commented on 2020-03-31 14:08 (UTC)

Now, the version is 1.0.197.

Please update the PKGBUILD.

Choppa2 commented on 2020-03-30 04:04 (UTC)

I'm also having the cb() never called error while running makepkg -si. Hope this gets fixed soon.

gnaggnoyil commented on 2020-03-25 06:54 (UTC)

It also happens to me today where on some Archlinux machines installing this package through yay reports npm ERR! cb() never called! error while running makepkg directly did not cause this error. Strange.