All who reported checksum issues, the checksum I got matched when the new version was released. It appears this is the second time that upstream has updated the package without bumping the version, causing a checksum mismatch. Give me a few minutes and I'll have this updated.
Search Criteria
Package Details: cryptomator 1.12.3-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/cryptomator.git (read-only, click to copy) |
|---|---|
| Package Base: | cryptomator |
| Description: | Multiplatform transparent client-side encryption of your files in the cloud. |
| Upstream URL: | https://cryptomator.org/ |
| Keywords: | cryptography encryption |
| Licenses: | GPL3 |
| Submitter: | Foxboron |
| Maintainer: | ajgraves (overheadhunter, SailReal) |
| Last Packager: | SailReal |
| Votes: | 79 |
| Popularity: | 0.30 |
| First Submitted: | 2016-04-03 17:36 (UTC) |
| Last Updated: | 2024-02-27 15:44 (UTC) |
Dependencies (10)
- alsa-lib
- fuse3 (fuse3-gitAUR)
- hicolor-icon-theme (hicolor-icon-theme-gitAUR)
- libnet (libnet-gitAUR)
- libxrender
- libxtst
- maven (mvnvmAUR) (make)
- unzip (unzip-natspecAUR, unzip-zstdAUR) (make)
- keepassxc-cryptomatorAUR (optional) – Use KeePassXC to store vault passwords
- ttf-hanazono (optional) – Install this font when using Japanese system language
Required by (1)
Sources (2)
ajgraves commented on 2021-02-25 14:14 (UTC)
<deleted-account> commented on 2021-02-25 14:13 (UTC)
Not sure where you're getting the sha256sum from, but the one in your PKGBUILD for the appimage causes the build to fail, where the one listed on https://cryptomator.org/downloads/linux/thanks/ works fine for me.
<deleted-account> commented on 2021-02-25 14:11 (UTC)
Not sure where you're getting the sha256sum from for the latest release, but the one listed on https://cryptomator.org/downloads/linux/thanks/ works fine for me where as the one in your PKGBUILD doesn't.
Kreba commented on 2021-02-25 13:03 (UTC)
Erstelle cryptomator... ==> Erstelle Paket: cryptomator 1.5.13-1 (Do 25 Feb 2021 14:01:47 CET) ==> Prüfe Laufzeit-Abhängigkeiten... ==> Prüfe Buildtime-Abhängigkeiten... ==> Empfange Quellen... -> cryptomator-1.5.13-1-x86_64.AppImage gefunden -> org.cryptomator.Cryptomator.desktop gefunden -> org.cryptomator.Cryptomator.png gefunden -> org.cryptomator.Cryptomator.svg gefunden -> cryptomator-vault.xml gefunden ==> Überprüfe source Dateien mit sha256sums... cryptomator-1.5.13-1-x86_64.AppImage ... FEHLGESCHLAGEN org.cryptomator.Cryptomator.desktop ... Durchgelaufen org.cryptomator.Cryptomator.png ... Durchgelaufen org.cryptomator.Cryptomator.svg ... Durchgelaufen cryptomator-vault.xml ... Durchgelaufen ==> FEHLER: Eine oder mehrere Dateien überstanden nicht die Gültigkeits-Prüfung! Fehler beim Erstellen von cryptomator
Viele Grüße und Danke!
plgonzalezrx8 commented on 2021-02-25 12:57 (UTC) (edited on 2021-02-25 13:12 (UTC) by plgonzalezrx8)
Same error as last time. It doesn't pass the validity check.
==> Validating source files with sha256sums...
cryptomator-1.5.13-1-x86_64.AppImage ... FAILED
==> ERROR: One or more files did not pass the validity check!
Failed to build cryptomator
Dwa30v commented on 2021-02-20 13:08 (UTC)
@ajgraves, thanks a lot!
ajgraves commented on 2021-02-20 12:41 (UTC)
@Dwa30v, it appears the package was updated by upstream without bumping the version number, so the checksum changed. I have pushed an update to the PKGBUILD to fix that.
Dwa30v commented on 2021-02-20 11:57 (UTC) (edited on 2021-02-20 11:57 (UTC) by Dwa30v)
==> Validating source files with sha256sums...
cryptomator-1.5.12-x86_64.AppImage ... FAILED
==> ERROR: One or more files did not pass the validity check!
Failed to build cryptomator
<deleted-account> commented on 2020-10-05 13:51 (UTC)
This software is open source software. However, PKGBUILD uses binaries. The correct package name is cryptomator-bin.
<deleted-account> commented on 2020-10-05 13:46 (UTC)
java-openjfx should be added to the dependent packages.
Pinned Comments
ajgraves commented on 2021-05-02 20:49 (UTC)
Everyone, with great thanks to @SailReal, this package now builds Cryptomator from source. If you wish to continue using the binary AppImage build, you need only to install
cryptomator-bin.We made this change to better align with the desires of the community (you've asked a few times to make this a "build from source" package) as well as better align to the package naming convention within the AUR.