sys-fs/cryptsetup: enable fips on stable

[tormath1]

this is required to enable fips mode on cryptsetup for stable release.

Signed-off-by: Mathieu Tortuyaux mtortuyaux@microsoft.com

---

• changelog entry
• CI: http://jenkins.infra.kinvolk.io:8080/job/os/job/manifest/5219/cldsv/

[pothos]

Since we only backport something that will be present when updating to a newer version I think it would be nice to have this stay in portage-stable. The move makes it harder to cherry-pick in the future.

Downstream patches that are not upstreamed to Gentoo would be lost on update but here this is probably not the case anymore because the newer versions have the flag.

[tormath1]

Since we only backport something that will be present when updating to a newer version I think it would be nice to have this stay in portage-stable. The move makes it harder to cherry-pick in the future.

Downstream patches that are not upstreamed to Gentoo would be lost on update but here this is probably not the case anymore because the newer versions have the flag.

@pothos I think I understand your point - but why would we need to cherry-pick this commits ? To me, once in Stable it should not have to move ?
Since this commits will be on flatcar-3033 they should not interfere with future versions of cryptsetup.

[pothos]

In the past there were cases where we updated software on the stable branch and for the LTS branch it is even a bit more likely that this can happen. Anyway, I just thought it can spare us some work and make diffing easier because I don't really see a benefit in the move.

[tormath1]

@pothos it was mostly to stay consistent with the concept of: flatcar modification -> ::coreos-overlay. Once the CI done, I'll move back cryptsetup to this overlay and simply apply the following commit on it: flatcar-archive/coreos-overlay@5495dbf