Package Details: cryptomator 1.19.3-1

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, as.skymatic)
Last Packager: as.skymatic
Votes: 83
Popularity: 2.01
First Submitted: 2016-04-03 17:36 (UTC)
Last Updated: 2026-06-29 13:51 (UTC)

Dependencies (10)

Required by (1)

Sources (2)

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.

Latest Comments

« First ‹ Previous 1 .. 7 8 9 10 11 12 13 14 15 16 17 .. 19 Next › Last »

Dwa30v commented on 2021-05-03 04:24 (UTC) 

Error: Failed to prepare transaction:
could not satisfy dependencies:
- unable to satisfy dependency 'java-environment=16' required by cryptomator

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.

Kreba commented on 2021-02-25 15:09 (UTC)

Erneuere cryptomator (1.5.12-2 -> 1.5.13-2)... Vorgang erfolgreich abgeschlossen.

Danke! - Thank you

ajgraves commented on 2021-02-25 14:14 (UTC)

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.

<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.

« First ‹ Previous 1 .. 7 8 9 10 11 12 13 14 15 16 17 .. 19 Next › Last »