| 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.50 |
| First Submitted: | 2018-04-18 16:33 (UTC) |
| Last Updated: | 2025-03-12 23:14 (UTC) |
I have exactly the same problem as @nunoun
==> Validating source files with sha256sums... joplin.desktop ... FAILED joplin-desktop.sh ... Passed joplin.sh ... Passed v1.0.135.zip ... Passed ==> ERROR: One or more files did not pass the validity check!
If I use the sha256sum suggested by @petsam I get the following error: ==> ERROR: Integrity checks (sha256) differ in size from the source array.
@petsam thank you that worked.
==> Validating source files with sha256sums... joplin.desktop ... FAILED joplin-desktop.sh ... Passed joplin.sh ... Passed v1.0.135.zip ... Passed ==> ERROR: One or more files did not pass the validity check!
If I use the sha256sum suggested by @petsam I get the following error: ==> ERROR: Integrity checks (sha256) differ in size from the source array.
New sha256sum for joplin.desktop 01bf4f7e311d79b7e309e158c46b6dd321194eb17e90f09db3ff41b75f35fffa
the sums of desktop.sh is invalid
Validating source files with sha256sums... joplin.desktop ... FAILED
You can skip te validation string, however this should be fixed regardless
He forgot to update the sha sums. Should be fixed soon.
Looks like the validation error is back again. I could not install the latest update.
Validazione di source file con sha256sums... joplin.desktop ... NON RIUSCITO
hi, the sha256 checksum for joplin.desktop has changed again. The correct you should be: 6768685a318bbdf3f0681197ca189b04d8640ac2764bdb8459af70ec4691c67b
if you change this in PKGBUILD at least you are able to compile and install manually. BRGDS
@gatlinnewhouse I cannot reproduce this. erro. since the makepkg comamnd should be launched from the main folder, in the pkg/ folder
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