Hi all,
Per the Fedora Linux 44 schedule [1], we started a mass rebuild for
Fedora Linux 44 on 2026-01-16, after addressing initial blockers
related to toolchain and dependency changes (including gcc, boost, and
related updates). The Fedora Linux 44 mass rebuild has now concluded
today.
The mass rebuild was run for the changes listed at:
https://fedoraproject.org/wiki/Fedora_44_Mass_Rebuild#Driving_Features
The rebuild was carried out in a side tag (f44-rebuild) and has been
merged into f44.
Failures from the mass rebuild can be seen at:
https://kojipkgs.fedoraproject.org/mass-rebuild/f44-failures.html
Packages still needing rebuilding:
https://kojipkgs.fedoraproject.org/mass-rebuild/f44-need-rebuild.html
A total of 1,566 packages were identified as needing rebuilds as part
of this effort.
At the end of the mass rebuild, 1,242 builds have failed and will need
to be addressed by package maintainers.
In total, 22,016 builds have been successfully tagged into f44.
We also untagged the following builds from f44, as they would
otherwise break Rawhide Compose:
- authselect-1.7.0-3.fc44
- shadow-utils-4.19.0-4.fc44
- firefox-147.0-2.fc44
- net-snmp-5.9.5.2-3.fc44
FTBFS bugs will be filed shortly for the remaining failures.
Discussions related to the Fedora Linux 44 mass rebuild took place in
the releng issue tracker:
https://forge.fedoraproject.org/releng/tickets/issues/13150
Please be sure to let Release Engineering know if you notice any
issues with the reporting. You can reach us in
#releng:fedoraproject.org on Matrix, by emailing our list [2], or by
filing an issue in Forge [3].
Regards,
Samyak Jain
Fedora Release Engineering
[1] https://fedorapeople.org/groups/schedule/f-44/f-44-releng-tasks.html
[2] https://lists.fedoraproject.org/admin/lists/rel-eng.lists.fedoraproject.org/
[3] https://forge.fedoraproject.org/releng/tickets/issues/
team,
We have two regression [1,2] with the proposed (and merged) fix [3] so
unfortunately
this is not yet over: During the test day [TestDay], most testers booted
fine
so we merged [3]. During the previous weekend (10-11 Jan 2026), people
found boot issues [1] so [3] was untagged [4]. We are suspecting that this
is something
related to the filesystem (btrfs?) and this is why during the test day using
a Live OS did not catch it. Test Day was indeed useful, fix worked but not
for all
systems so clearly the fix needs to be revisited.
I ask you the following: From a stable system/grub, can you (RE)INSTALL
these instructions:
$ sudo dnf install -y koji
$ mkdir tmp & cd tmp
$ koji download-task 140906146 # aka [5], this is just a scratch build just
for x86_64, disable SB
$ sudo dnf install *.rpm
$ sudo reboot
The fix [5] contains [3] plus some instrumentation enabling debugging
('debug=all,-lexer,-scripting').
In case of FAILURE (you boot but end up in the grub prompt instead of the
grub menu) please
attach a video recording all the boot process and also in the comment
indicate your block/partition/fs
scheme with 'lsblk -f'. In case of SUCCESS, just provide the output of the
latter cmd. Video and log
can be attached on [1] as a new comment/attachment.
I am also preparing another test-day which will basically do the above
steps but I will wait hoping
that we will get enough results here first.
[1] https://bugzilla.redhat.com/show_bug.cgi?id=2427945
[2] https://bugzilla.redhat.com/show_bug.cgi?id=2422881
[3] https://src.fedoraproject.org/rpms/grub2/pull-request/198
[4] https://forge.fedoraproject.org/releng/tickets/issues/13157
[5] https://koji.fedoraproject.org/koji/taskinfo?taskID=141063848
[TestDay]
https://fedoraproject.org/wiki/Test_Day:2025-12-15_GRUB_out_of_memory_verif…