When exactly is the plan to start the F36 mass rebuild? I'm building right now: gcc-12.0.0-0.1.fc36 https://koji.fedoraproject.org/koji/taskinfo?taskID=81405309 gcc-12.0.0-0.1.1.fc36 https://koji.fedoraproject.org/koji/taskinfo?taskID=81406385 The former has the current ppc64le long double ABI, the latter has the one we'd like to switch to. If these builds finish before the mass rebuild, I'd like the latter to be used for the mass rebuild, but tag it only shortly before the mass rebuild in. If they don't finish soon enough and there is no way to delay mass rebuild for that, I'd like gcc-12.0.0-0.5.1.fc36 (new ppc64le ABI) to be tagged instead. I might start another pair of gccs in a few hours, there were some changes affecting some rawhide packages in the last few hours: https://gcc.gnu.org/r12-6691 https://gcc.gnu.org/r12-6694 in particular.
Another gcc build, this time with the new ppc64le ABI only: https://koji.fedoraproject.org/koji/taskinfo?taskID=81422139
Hi @jakub, thanks for this. The mass rebuild will start today 15:00 UTC but we will wait for the latest gcc build.
For gcc-12.0.1-0.1.1.fc36, I've now created https://bodhi.fedoraproject.org/updates/FEDORA-2022-4f38e093c7 and waiting for automated tests, gcc-12.0.1-0.2.fc36 s390x is still building, all other arches finished, dunno if the ETA is 30 minutes or 3 hours unfortunately.
Unfortunately the rawhide buildroot is currently busted for unrelated reasons:
Error: Problem 1: package dnf-4.10.0-1.fc36.noarch requires python3-dnf = 4.10.0-1.fc36, but none of the providers can be installed - package python3-dnf-4.10.0-1.fc36.noarch requires python3-rpm >= 4.14.0, but none of the providers can be installed - conflicting requests - nothing provides libimaevm.so.2()(64bit) needed by python3-rpm-4.17.0-4.fc36.x86_64 Problem 2: package python3-dnf-plugins-core-4.0.24-1.fc36.noarch requires python3-dnf >= 4.2.22, but none of the providers can be installed - package dnf-plugins-core-4.0.24-1.fc36.noarch requires python3-dnf-plugins-core = 4.0.24-1.fc36, but none of the providers can be installed - package python3-dnf-4.10.0-1.fc36.noarch requires python3-rpm >= 4.14.0, but none of the providers can be installed - conflicting requests - nothing provides libimaevm.so.2()(64bit) needed by python3-rpm-4.17.0-4.fc36.x86_64
https://kojipkgs.fedoraproject.org//work/tasks/7237/81457237/mock_output.log
This makes it impossible to perform basic validation on the gcc build.
Note, gcc-12.0.1-0.1.1.fc36 and corresponding annobin are already tagged into rawhide, but gcc-12.0.1-0.2.fc36 is still building.
Unfortunately the rawhide buildroot is currently busted for unrelated reasons: Error: Problem 1: package dnf-4.10.0-1.fc36.noarch requires python3-dnf = 4.10.0-1.fc36, but none of the providers can be installed - package python3-dnf-4.10.0-1.fc36.noarch requires python3-rpm >= 4.14.0, but none of the providers can be installed - conflicting requests - nothing provides libimaevm.so.2()(64bit) needed by python3-rpm-4.17.0-4.fc36.x86_64 Problem 2: package python3-dnf-plugins-core-4.0.24-1.fc36.noarch requires python3-dnf >= 4.2.22, but none of the providers can be installed - package dnf-plugins-core-4.0.24-1.fc36.noarch requires python3-dnf-plugins-core = 4.0.24-1.fc36, but none of the providers can be installed - package python3-dnf-4.10.0-1.fc36.noarch requires python3-rpm >= 4.14.0, but none of the providers can be installed - conflicting requests - nothing provides libimaevm.so.2()(64bit) needed by python3-rpm-4.17.0-4.fc36.x86_64 https://kojipkgs.fedoraproject.org//work/tasks/7237/81457237/mock_output.log This makes it impossible to perform basic validation on the gcc build.
https://bugzilla.redhat.com/show_bug.cgi?id=2042507
https://koji.fedoraproject.org/koji/taskinfo?taskID=81422139 aka gcc-12.0.1-0.2.fc36 finished building, but due to the #2042507 I can't rebuild annobin against it in the side-tag (even when the side-tag doesn't contain the problematic ima-evm-utils (but likely all src.rpm build jobs go elsewhere).
buildroot should be fixed now. @jakub can you build annobin so we can start the massrebuild?
Done, https://bodhi.fedoraproject.org/updates/FEDORA-2022-4f38e093c7 created, waiting now for the automated tests, will waive them afterwards if needed.
Sorry, wrong link, https://bodhi.fedoraproject.org/updates/FEDORA-2022-b9304b8204 created.
So both builds are in rawhide closing this and starting the rebuild in a few minutes.
Metadata Update from @humaton: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Indeed, thanks for waiting for it and sorry for the 4hrs delay.