From: "Andreas Sturmlechner" <asturm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] data/gentoo-news:master commit in: 2019-10-29-cryfs-0_10-update/
Date: Tue, 29 Oct 2019 10:58:10 +0000 (UTC) [thread overview]
Message-ID: <1572346570.2c62ccd074937086eee3bd19a0c9ac7c21c54eef.asturm@gentoo> (raw)
commit: 2c62ccd074937086eee3bd19a0c9ac7c21c54eef
Author: Andreas Sturmlechner <asturm <AT> gentoo <DOT> org>
AuthorDate: Tue Oct 29 09:50:42 2019 +0000
Commit: Andreas Sturmlechner <asturm <AT> gentoo <DOT> org>
CommitDate: Tue Oct 29 10:56:10 2019 +0000
URL: https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=2c62ccd0
sys-fs/cryfs-0.10.2 upgrade instructions
Signed-off-by: Andreas Sturmlechner <asturm <AT> gentoo.org>
.../2019-10-29-cryfs-0_10-update.en.txt | 25 ++++++++++++++++++++++
1 file changed, 25 insertions(+)
diff --git a/2019-10-29-cryfs-0_10-update/2019-10-29-cryfs-0_10-update.en.txt b/2019-10-29-cryfs-0_10-update/2019-10-29-cryfs-0_10-update.en.txt
new file mode 100644
index 0000000..31c694f
--- /dev/null
+++ b/2019-10-29-cryfs-0_10-update/2019-10-29-cryfs-0_10-update.en.txt
@@ -0,0 +1,25 @@
+Title: sys-fs/cryfs-0.10.2 update
+Author: Andreas Sturmlechner <asturm@gentoo.org>
+Posted: 2019-10-29
+Revision: 1
+News-Item-Format: 2.0
+Display-If-Installed: <sys-fs/cryfs-0.10
+
+Filesystems created with CryFS 0.9.x are incompatible with the new storage
+format. [1] Migration is necessary before mounting with CryFS 0.10 and
+possible for old containers going back as far as CryFS 0.9.4. [2]
+
+However, upstream recommend to create new containers with 0.10 to avoid
+potential data loss from a failed migration, and in order to benefit from all
+performance advantages of the new format.
+
+Before updating, copy all data from cryfs containers to a temporary and secure
+location. After the update, move it back into a newly created container. Don't
+forget to remove the temporary files afterwards.
+
+Users of KDE Plasma Vaults should follow the same procedure. To check the type
+of existing containers, open them using the Vaults widget. It is part of the
+path as displayed in dolphin.
+
+[1] https://bugs.gentoo.org/690324
+[2] https://github.com/cryfs/cryfs/releases/tag/0.10.1
reply other threads:[~2019-10-29 10:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1572346570.2c62ccd074937086eee3bd19a0c9ac7c21c54eef.asturm@gentoo \
--to=asturm@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox