Summary: | sys-fs/cryfs-0.10.2: CryFS needs a news item about upgrade path before/when it goes stable | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Zoltan Puskas <zoltan> |
Component: | Current packages | Assignee: | adebeus |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | proxy-maint |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://archives.gentoo.org/gentoo-dev/message/1a31f1fce6dc54c24dfb4f1946125d62 | ||
Whiteboard: | scheduled for 2019-10-28 | ||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 689034 |
Description
Zoltan Puskas
2019-07-21 07:07:09 UTC
Altough the idea is noble, in practise it falls short of: - package does not support parallel install (files conflict) - consequently, binaries are named identically, if you rename them, you'll have to create an eselect module; revdeps will all expect the standard naming - cryfs-0.9* depends on <boost-1.70, cryfs-0.10* depends on >=boost-1.70, boost is not slotted either, which means down- and upgrades are especially painful for the triggered slot rebuilds This is more smelling like a news item for stable users to temporarily store their data unencrypted, do the upgrade, and move their files back to a new encrypted storage. I see, so slotting would have unrealistic requirements. Alright, thanks for the explanation. Then @Andreas can you please make sure that there is a news item for this, as this can bite stable users? Also maybe keep 0.9.x and 0.10.x series in stable for a while in parallel allowing users to migrate easily. "When trying to migrate a file system from CryFS 0.9.3 or older, show an error message suggesting to first open it with 0.9.10 because we can't load that anymore." cryfs entered portage with version 0.9.7. So it appears to me we do not need to do anything here at all? The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ef111452b8fc7243d3a69e51bcc396498a01a50f commit ef111452b8fc7243d3a69e51bcc396498a01a50f Author: Andreas Sturmlechner <asturm@gentoo.org> AuthorDate: 2019-10-26 20:07:22 +0000 Commit: Andreas Sturmlechner <asturm@gentoo.org> CommitDate: 2019-10-26 20:15:17 +0000 sys-fs/cryfs: Revert "Add upper bound on boost-1.70" It appears to build just fine against boost-1.71.0. This reverts commit 4f8c83514f1d7664bcccdba3d8ffd3de7ef5325b. Bug: https://bugs.gentoo.org/690324 Signed-off-by: Andreas Sturmlechner <asturm@gentoo.org> sys-fs/cryfs/cryfs-0.9.9.ebuild | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) sorry, different issue. I was actually able to reproduce your message. However, the situation is not as dire as initially thought. The news item looks reasonable and informative engough, thanks for making it. I'll let the official devs approve it. |