Well, it passed tests, so this bug isn't a problem at least; I guess no new feature flags were added between 6.18.0 and 7.0.1. Beyond that, it's hard for me to say. The changelog between 6.18.0 and 7.0.1 is quite long and includes a lot of things that clearly aren't just bug fixes, which means it seems to be against the update policy: "As a result, we should avoid major updates of packages within a stable release. Updates should aim to fix bugs, and not introduce features, particularly when those features would materially affect the user or developer experience." But then, we know that policy isn't always strictly followed. I'm not enough of an xfs expert to guess how significant the danger in not following it here might be.
It's ultimately your choice, and FESCo's responsibility to oversee the update policy. I'm just giving advice here. :D But that's probably what I would suggest, yes.
For help debugging failed Fedora CI tests (fedora-ci.*), contact the Fedora CI team.
For help debugging failed Fedora CoreOS tests (coreos.*), contact the Fedora CoreOS team.
For help debugging failed openQA tests (update.*), contact the Fedora Quality team, who will usually investigate and diagnose all failures within 24 hours.
This update has been submitted for testing by preichl.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'failed'.
This breaks Server network install (because it uses XFS):
In general updating xfsprogs is sensitive and probably not a good idea for stable releases.
The specific issue here is likely https://bugzilla.redhat.com/show_bug.cgi?id=2429501 or similar, and so the fix would likely be backporting https://src.fedoraproject.org/rpms/grub2/c/f4f521acfd118f6f8ec624e87bc07bd3a26a9303?branch=rawhide to f43's grub2, but even if we fix that I'm not 100% sure the update is a great idea.
CC @nfrayer
Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
Thank you Adam for your comment. What do you think about update for fedora-44? FEDORA-2026-ce44c82f57
Well, it passed tests, so this bug isn't a problem at least; I guess no new feature flags were added between 6.18.0 and 7.0.1. Beyond that, it's hard for me to say. The changelog between 6.18.0 and 7.0.1 is quite long and includes a lot of things that clearly aren't just bug fixes, which means it seems to be against the update policy: "As a result, we should avoid major updates of packages within a stable release. Updates should aim to fix bugs, and not introduce features, particularly when those features would materially affect the user or developer experience." But then, we know that policy isn't always strictly followed. I'm not enough of an xfs expert to guess how significant the danger in not following it here might be.
This update has been pushed to testing.
Should I unpush this update and revert the commit in dist-git for f43?
@adamwill
It's ultimately your choice, and FESCo's responsibility to oversee the update policy. I'm just giving advice here. :D But that's probably what I would suggest, yes.
This update has been unpushed.