| 1 |
Title: sys-fs/cryfs-0.10.2 update |
| 2 |
Author: Andreas Sturmlechner <asturm@g.o> |
| 3 |
Content-Type: text/plain |
| 4 |
Posted: 2019-10-26 |
| 5 |
Revision: 1 |
| 6 |
News-Item-Format: 1.0 |
| 7 |
Display-If-Installed: <sys-fs/cryfs-0.10 |
| 8 |
|
| 9 |
Internal changes in sys-fs/cryfs-0.10 [1] made it incompatible with encrypted |
| 10 |
containers created with 0.9.x. No automatic migration of old containers is |
| 11 |
provided. This requires manual upgrade planning. |
| 12 |
|
| 13 |
Before updating, copy all data from cryfs containers to a temporary and secure |
| 14 |
location. After 0.10.x update, move it back into a newly created container. |
| 15 |
|
| 16 |
This is being made more complicated by conflicting boost dependencies: |
| 17 |
- sys-fs/cryfs-0.9.x depends on sys-fs/cryfs-1.65.0 |
| 18 |
- sys-fs/cryfs-0.10.x depends on >=dev-libs/boost-1.65.1 |
| 19 |
|
| 20 |
Which means this update is going to be part of a bigger system update as |
| 21 |
typically many boost consumers need to be rebuilt. |
| 22 |
|
| 23 |
[1] https://github.com/cryfs/cryfs/releases/tag/0.10.1 |
Archives