# F42 Blocker Review meeting
# Date: 2025-02-24
# Time: 17:00 UTC
# Location:
https://matrix.to/#/#blocker-review:fedoraproject.org?web-instance[element.…
Hi folks! It's time for a Fedora 42 blocker review meeting! We have 8
proposed blockers and 7 proposed freeze exceptions for Beta, and 2
proposed blockers for Final.
Here is a handy link which should show you the meeting time
in your local time:
https://www.timeanddate.com/worldclock/fixedtime.html?msg=Fedora+41+Blocker…
The meeting will be on Matrix. Click the link above to join in a web
client - you can authenticate with your FAS account - or use a
dedicated client of your choosing.
If you have time this weekend, you can take a look at the proposed or
accepted blockers before the meeting - the full lists can be found
here: https://qa.fedoraproject.org/blockerbugs/ .
Remember, you can also now vote on bugs outside of review meetings! If
you look at the bug list in the blockerbugs app, you'll see links
labeled "Vote!" next to all proposed blockers and freeze exceptions.
Those links take you to tickets where you can vote.
https://pagure.io/fedora-qa/blocker-review has instructions on how
exactly you do it. We usually go through the tickets shortly before the
meeting and apply any clear votes, so the meeting will just cover bugs
where there wasn't a clear outcome in the ticket voting yet. **THIS
MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!**
We'll be evaluating these bugs to see if they violate any of the
Release Criteria and warrant the blocking of a release if they're not
fixed. Information on the release criteria for F42 can be found on the
wiki [0].
For more information about the Blocker and Freeze exception process,
check out these links:
- https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process
- https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process
And for those of you who are curious how a Blocker Review Meeting
works - or how it's supposed to go and you want to run one - check out
the SOP on the wiki:
- https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting
Have a good weekend and see you on Monday!
[0] https://fedoraproject.org/wiki/Fedora_Release_Criteria
P.S. fun fact: every single Fedora 41 blocker meeting announcement said
"F10" in the first line because I typoed the edit from 40 to 41, and
nobody noticed...
--
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org
https://www.happyassassin.net
Among others I use a Radxa Rock Pi 4a with nvme disk.
The latest update to kernel 6.12.10 ended with a not bootable system. With the release kernel and the update kernel 6.8.10 everything worked flawlessly
I get:
[ OK ] Reached target bsasic.target - Basic System.
rk3399-dmc-freq ffa80000.dmc: Invalid operating-points in device tree.
rk3399-dmc-freq ffa80000.dmc: probe with driver rk3399-dmc-freq failed with error -22
[ OK ] Stopped systemd-vconsole-setup.service - Virtual Console Setup.
. . .
[ ...... ] dracut-initqueue[557]: Volume group "fedora" not foumd
[ ...... ] dracut-initqueue[557]: Cannot process volume group fedora
That cannot work, indeed, because the VG on this system was renamed due to LVM naming conflicts.
Additionally, the directory /etc/lvm/devices is empty, but it should contain a valid device file.
I can mount the EFI and the boot partitions of the nvme disk and access all files therein.
I would like to switch back to the previous kernel 6.8.10 and wondering how to do that in the dracut shell. If I remember correctly there is a tool available, but I don’t remember the details and my internet research didn't come up with anything useful.
I would greatly appreciate any advice on how to revert to the previous kernel.
Thanks
Peter
—
Peter Boy
https://fedoraproject.org/wiki/User:Pboy
PBoy(a)fedoraproject.org
Timezone: CET (UTC+1) / CEST (UTC+2)
Fedora Server Edition Working Group member
Fedora Docs team contributor and board member
Java developer and enthusiast