public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Andreas Sturmlechner <asturm@gentoo.org>
To: pr <pr@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] [RFC] News Item: sys-fs/cryfs-0.10.2 update
Date: Sat, 26 Oct 2019 20:39:51 +0200	[thread overview]
Message-ID: <2364611.2xGvymeTQd@tuxk10> (raw)

[-- Attachment #1: Type: text/plain, Size: 924 bytes --]

Title: sys-fs/cryfs-0.10.2 update 
Author: Andreas Sturmlechner <asturm@gentoo.org>
Content-Type: text/plain
Posted: 2019-10-26
Revision: 1
News-Item-Format: 1.0
Display-If-Installed: <sys-fs/cryfs-0.10

Internal changes in sys-fs/cryfs-0.10 [1] made it incompatible with encrypted
containers created with 0.9.x. No automatic migration of old containers is
provided. This requires manual upgrade planning.

Before updating, copy all data from cryfs containers to a temporary and secure
location. After 0.10.x update, move it back into a newly created container.

This is being made more complicated by conflicting boost dependencies:
- sys-fs/cryfs-0.9.x depends on sys-fs/cryfs-1.65.0
- sys-fs/cryfs-0.10.x depends on >=dev-libs/boost-1.65.1

Which means this update is going to be part of a bigger system update as
typically many boost consumers need to be rebuilt.

[1] https://github.com/cryfs/cryfs/releases/tag/0.10.1

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 618 bytes --]

             reply	other threads:[~2019-10-26 18:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-26 18:39 Andreas Sturmlechner [this message]
2019-10-26 20:57 ` [gentoo-dev] Re: [RFC] News Item v2: sys-fs/cryfs-0.10.2 update Andreas Sturmlechner
2019-10-28  0:38   ` [gentoo-dev] Re: [RFC] News Item v3: " Andreas Sturmlechner
2019-10-28 10:54     ` Ulrich Mueller
2019-10-29  9:58       ` Andreas Sturmlechner
2019-10-29 15:01       ` [gentoo-dev] [RFC] News Item v2: Desktop profile switching USE default to elogind Andreas Sturmlechner

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=2364611.2xGvymeTQd@tuxk10 \
    --to=asturm@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=pr@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