@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.
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: | MIT |
Groups: | joplin |
Conflicts: | joplin-desktop-electron |
Submitter: | masterkorp |
Maintainer: | masterkorp |
Last Packager: | masterkorp |
Votes: | 262 |
Popularity: | 1.51 |
First Submitted: | 2018-04-18 16:33 (UTC) |
Last Updated: | 2024-07-29 19:54 (UTC) |
« First ‹ Previous 1 .. 23 24 25 26 27 28 29 30 31 32 33 .. 54 Next › Last »
@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.
@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
Sorry to sound like a nooblet, but how do you do the --nocheck with aurutils? Anybody know?
@Schlaefer: Many thanks! Joplin works again!
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
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
npm 7.0.5-1 from community-testing fails to build with some obscure errors, npm 6.14.8-2 from community works fine.
@imlonghao yay -S --rebuild joplin-desktop-electron
commond can not work, i makepkg -s
build a new pkg, thank you!
@Dongsean yay -S --rebuild joplin-desktop-electron
@imlonghao i am a beginner, please tell me how to rebuild it.
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.
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