how can this be in this update:
CryFS Version 1.0.3+0.g5d0cc367.dirty
WARNING! This is a development version based on git commit 5d0cc367. Please do not use in production!
how can this be in this update:
CryFS Version 1.0.3+0.g5d0cc367.dirty
WARNING! This is a development version based on git commit 5d0cc367. Please do not use in production!
As far as I can tell that package version is not available from extra repository or AUR
$ pamac search cryfs
sirikali-git 1.8.5.r2.0abe269-1 AUR
A Qt/C++ GUI front end to sshfs, ecryptfs-simple, cryfs, gocryptfs, securefs, fscrypt and encfs
sirikali-bin 1.8.6-2 AUR
A Qt/C++ GUI front end to sshfs, ecryptfs-simple, cryfs, gocryptfs, securefs, fscrypt and encfs
sirikali 1.8.6-1 AUR
A Qt/C++ GUI front end to sshfs, cryfs, gocryptfs, securefs, fscrypt and encfs
cryfs-git 0.10.2.r131.gd2e5ba7f-1 AUR
CryFS encrypts your files, so you can safely store them anywhere
cryfs 1.0.3-5 extra
Cryptographic filesystem for the cloud
cryfs has not been updated since April
$ pamac info cryfs
Name : cryfs
Version : 1.0.3-5
Description : Cryptographic filesystem for the cloud
URL : https://www.cryfs.org
Packager : Antonio Rojas <arojas@archlinux.org>
Build Date : Wed 29 Apr 2026 18:13:22 BST
cryfs-git in AUR is marked out of date
AUR (en) - Flag Comment
a821 flagged cryfs-git out-of-date on 2024-06-22 (UTC) for the following reason:git:// protocol is deprecated, please update to git+https://
It is not - just check the change log…
Perhaps you have build the git version and forgot about it?
I installed it from the official repository.
when I uninstalled it:
$ cryfs --version
zsh: command not found: cryfs
then reinstalled it:
$ cryfs --version
CryFS Version 1.0.3+0.g5d0cc367.dirty
WARNING! This is a development version based on git commit 5d0cc367. Please do not use in production!
I’m not sure if the message is new to this update, just noticed it.
Nope, it’s the repo version. I can confirm the issue, although I don’t really know why I have it installed. It’s listed as “explicitly installed”, and it’s an optional dependency of plasma-vault.
[nx-74205:/dev/pts/3][/home/aragorn]
[aragorn] > cryfs --version
CryFS Version 1.0.3+0.g5d0cc367.dirty
WARNING! This is a development version based on git commit 5d0cc367. Please do not use in production!
You’ll have to ask upstream about that. The 5d0cc367 commit is the 1.0.3 release tag.
EDIT: Turns out it’s due to the way Arch packaged it:
Please see comment from Antonio Rojas It’s not a development version. That message is displayed because the package is built from the git repo, not from a released tarball. – cryfs development version, do not use in production? / Newbie Corner / Arch Linux Forums Apparently the Arch Linux maintainer rebuild using the git source instead of a release tag - although the Arch Linux PKGBUILD reference the release tag - nothing we can do - it is how it![]()
It is a package inherited from Arch Linux extra repo
I installed it just to check this issue…
$ pamac info cryfs
Name : cryfs
Version : 1.0.3-5
Description : Cryptographic filesystem for the cloud
URL : https://www.cryfs.org
Licenses : LGPL-3.0-only
Repository : extra
Installed Size : 2,5 MB
Groups : --
Depends On : boost-libs fmt fuse2 glibc libgcc libgomp libstdc++ spdlog
Optional Dependencies : --
Required By : --
Optional For : --
Provides : --
Replaces : --
Conflicts With : --
Packager : Antonio Rojas <arojas@archlinux.org>
Build Date : ons 29 apr 2026 19:13:22 CEST
Install Date : fre 14 aug 2026 15:09:46 CEST
Install Reason : Explicitly installed
Validated By : Signature
Backup files : --
reported to the project: 1.0.3 release is "dirty" · Issue #559 · cryfs/cryfs · GitHub
I don’t know what to think…
The package was rebuilt using the same tag 1.0.3 - so for all intents and purposes it should use the same source
Cryptographic filesystem for the cloud packages: cryfs
Maybe it’s just some beta-testing flag somebody forgot to disable before compiling. ![]()
That warning makes the package status clear: this is a development build rather than the stable CryFS release. Keeping it out of production until the repository package is refreshed seems like the safest approach.
Please see comment from Antonio Rojas
It’s not a development version. That message is displayed because the package is built from the git repo, not from a released tarball.
– cryfs development version, do not use in production? / Newbie Corner / Arch Linux Forums
Apparently the Arch Linux maintainer rebuild using the git source instead of a release tag - although the Arch Linux PKGBUILD reference the release tag - nothing we can do - it is how it ![]()
Thanks for the correction. The warning reflects a git-source build, so my earlier description of it as a development version was too strong.