Package Details: joplin-desktop 3.2.13-2

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.36
First Submitted: 2018-04-18 16:33 (UTC)
Last Updated: 2025-03-12 23:14 (UTC)

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.

  • 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 .. 26 27 28 29 30 31 32 33 34 35 36 .. 57 Next › Last »

phonemic commented on 2020-12-21 13:08 (UTC)

@masterkorp --nocheck is still needed for the build to succeed. I agree, it would be great if you could test locally then push one commit when ready.

figue commented on 2020-12-21 11:50 (UTC)

with "makepkg -f" you can force the build. No need to bump if not necessary. Is better to make changes locally and, at the end, push the update to AUR, as Rhinoceros suggest.

Rhinoceros commented on 2020-12-21 11:07 (UTC) (edited on 2020-12-21 12:57 (UTC) by Rhinoceros)

@masterkorp Oh okay. Maybe I missed something. Can't you just makepkg locally without pushing changes? What else does the AUR do exactly?

masterkorp commented on 2020-12-21 10:40 (UTC)

@Rhinocerors

I need to test the releases, I absolutely no other way to test the releases and the multiple package integration of the AUR

Also, `--nocheck`` is not needed anymore even, the check function is a force pass.

Rhinoceros commented on 2020-12-20 22:38 (UTC) (edited on 2020-12-20 22:39 (UTC) by Rhinoceros)

@masterkorp Could you please stop pushing multiple updates? I've had to rebuild this so many times in the last few weeks. Can you please just put all your changes in one $pkgrel bump? There really shouldn't be any need for 12 bumps. Also, since the PKGBUILD is broken (check() still fails), it's quite annoying to re-install the same version 13 times.

EDIT: it's also worth pinning one of the comments about building with --nocheck

neoresin commented on 2020-12-20 19:14 (UTC)

Sorry to sound like a nooblet, but how do you do the --nocheck with aurutils? Anybody know?

karcher commented on 2020-12-20 17:35 (UTC)

@Schlaefer: Many thanks! Joplin works again!

Schlaefer commented on 2020-12-20 11:15 (UTC) (edited on 2020-12-20 11:18 (UTC) by Schlaefer)

Joplin's test-cases are currently failing. The workaround is the same as for joplin-desktop-electron that was mentioned by others: don't run the test-cases by disabling check (e.g. for yay):

yay -S --mflags="--nocheck" joplin-desktop

karcher commented on 2020-12-18 17:30 (UTC) (edited on 2020-12-18 17:34 (UTC) by karcher)

I cannot launch Joplin. I try to install this package and I'm getting this error:

joplin: Ran all test suites.
joplin: npm ERR! code ELIFECYCLE
joplin: npm ERR! errno 1
joplin: npm ERR! joplin@1.4.9 test: `jest --config=jest.config.js --runInBand --bail --forceExit`
joplin: npm ERR! Exit status 1
joplin: npm ERR! 
joplin: npm ERR! Failed at the joplin@1.4.9 test script.
joplin: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
joplin: npm ERR! A complete log of this run can be found in:
joplin: npm ERR!     /home/user/.npm/_logs/2020-12-18T17_26_03_638Z-debug.log
lerna ERR! npm run test exited 1 in 'joplin'
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! root@ test: `lerna run test --stream`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the root@ test script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/user/.npm/_logs/2020-12-18T17_26_03_685Z-debug.log
==> ERROR: A failure occurred in check().

$ yay -S --rebuild joplin-desktop-electron does not work!

$ makepkg -si does not work either!

$ npm -v 6.14.8

« First ‹ Previous 1 .. 26 27 28 29 30 31 32 33 34 35 36 .. 57 Next › Last »