sys-kernel/dracut: Bump to 109 ahead of Gentoo stabilisation #3616
+27
−3,810
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
sys-kernel/dracut: Bump to 109
Gentoo is a bit behind with the stabilisation and I need new features. Bumping this required reordering the bootengine Dracut modules. See flatcar/bootengine#116.
While I was at it, I added some missing dependencies to coreos-kernel that make a difference to the resulting initrd.
I also stopped the symlinking of
libtolib64in the minimal initrd. Gentoo hasn't done this for a very long time because it's wrong. We don't do it anywhere else.How to use
Just see whether it boots.
Testing done
A Jenkins run has passed aside from known issues.
There is obviously a lot of churn in the changes report from files moving around. I also compared the non-binary initrd contents against a recent nightly. Changes to the initrd itself are just what you'd expect from the bump. None of them are unexplained.
I also manually tested provisioning with systemd-cryptenroll against the TPM.
changelog/directory (user-facing change, bug fix, security fix, update)/bootand/usrsize, packages, list files for any missing binaries, kernel modules, config files, kernel modules, etc.