Learn more about these different git repos.
Other Git URLs
The Fedora 41 schedule[1] has a mass rebuild scheduled for Wed 2024-07-17, We need to plan and coordinate all tasks in preparation for it. For the driving changes please refer[2].
Please note that if you need to exclude any packages from the rebuild, you can use the PKG_SKIP_LIST or add a noautobuild file to the root of your distgit repository. This will instruct the mass rebuild script to skip these packages. Previously, some OCaml packages were rebuilt, but they can now be opted out using this method if required.
[1] https://fedorapeople.org/groups/schedule/f-41/f-41-key-tasks.html [2] https://fedoraproject.org/wiki/Fedora_41_Mass_Rebuild#Driving_Features
Metadata Update from @jnsamyak: - Issue tagged with: f41, high-gain, high-trouble, mass rebuild
Metadata Update from @jnsamyak: - Issue assigned to jnsamyak
Thr koji tags and targets are created, and the request for the autosigning is sent to fedora-infra[1], along with the PR[2]
koji add-tag f41-rebuild --parent f41 koji add-target f41-rebuild f41-build
[1] https://pagure.io/fedora-infrastructure/issue/12060 [2] https://pagure.io/fedora-infra/ansible/pull-request/2152
@jnsamyak We need to revert the changes for the sbin-merge. I'll do that tomorrow morning. (CEST timezone, so a bit later than you). Please do not start the rebuild until that's done, because otherwise we'll have a mess with half-merged filesystem.
Hey @zbyszek
Yep, I'm aware of the revert and thanks for the comment, could you shoot me a message or another comment, when it's done?
Before starting, I'm currently looking at two blockers, one of which is resolved.
FYI: I have pinged tools folks about mass rebuild (glibc/gcc)
The PR to revert changes in filesystem was https://src.fedoraproject.org/rpms/filesystem/pull-request/16). I started a build for rawhide with those changes (https://koji.fedoraproject.org/koji/taskinfo?taskID=120613485) to let the CI run.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-dc46804837 is the bodhi update for the rebuilt filesystem. I think it's all fine, even though the CI didn't pass, see comments there. With that, the sbin-merge changes have all been revert in dist-gits, so the we're ready for the mass rebuild.
Please continue with the mass rebuild.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-dc46804837 is the bodhi update for the rebuilt filesystem. I think it's all fine, even though the CI didn't pass, see comments there. With that, the sbin-merge changes have all been revert in dist-gits, so the we're ready for the mass rebuild. Please continue with the mass rebuild.
Shouldn't those changes land in rawhide first? The update is stuck on failed CI, and the changes haven't reached the repositories, and filesystem package won't be rebuilt first.
The change was never present in rawhide, only in dist-git and in builds in a side tag. The side tag wasn't merged.
It's annoying that the update is stuck, but this doesn't block the mass rebuild.
The mass rebuild is scheduled for two hours post (!4-14:30 UTC) hopefully the change lands;
I guess it's fine now If we ran the mass rebuild before the commit was reverted as mentioned in the PR above by @zbyszek, in that case it would have picked up all those changes in the newly mass rebuilt packages as they are from the same git/source.
@zbyszek You didn't revert the glibc changes, and they are not fully conditionalized. Should we really start the mass rebuild with something that has seen only very limited testing?
Hey @zbyszek;
I was just talking to glibc folks, seems like the revert has not been done for the glibc sources.
https://src.fedoraproject.org/rpms/glibc/c/6756999ced04c544708632a1003e8b405fb94047?branch=rawhide
Also, can you make sure all the places this commit got reverted where this was done? Ex: glibc, I'm not sure what all the places were affected because of this; We should hold off until this is done;
Okay I see this from the mailing list;
[1] https://fedoraproject.org/wiki/Changes/Unify_bin_and_sbin [2] https://bodhi.fedoraproject.org/updates/FEDORA-2024-3aafcac6a8 https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/... [3] https://github.com/weldr/lorax/pull/1409 [4] https://github.com/coreos/fedora-coreos-tracker/issues/1714#issuecomment-222... [5] https://gitlab.com/fedora/bootc/tracker/-/issues/29 [6] https://src.fedoraproject.org/rpms/selinux-policy/pull-request/448 [7] https://src.fedoraproject.org/rpms/cifs-utils/c/934e038df9023177535e7cda5646... [8] https://src.fedoraproject.org/rpms/filesystem/pull-request/15 [9] https://src.fedoraproject.org/rpms/redhat-rpm-config/pull-request/308
I'm not sure if all PRs are merged but we need to make sure the dist-git ones affecting packages (hence mass rebuild) should be reverted back properly, to not cause any issue during the rebuild process.
If you look at 6756999ced04c544708632a1003e8b405fb94047, the changes are conditionalized on "%{_sbindir}" == "%{_bindir}". Thus, with the latest revert to rpm they are different, so glibc is built in the traditional form. In case of glibc, there are some minor changes that change the path reported by rpm from /sbin/ldconfig to /usr/sbin/ldconfig. Functionally, they are of course equivalent because /sbin is a symlink to /usr/sbin. That part of 6756999ced04c544708632a1003e8b405fb94047 remains, but it is a valid change that doesn't need to be reverted. FPC approved the move ~two months ago and this just implements it.
"%{_sbindir}" == "%{_bindir}"
rpm
/sbin/ldconfig
/usr/sbin/ldconfig
/sbin
/usr/sbin
So only two packages needed to be reverted: rpm and filesystem and that has been done.
Mass Rebuild has been fired off!
Mass rebuild completed and has been tagged in.
Full list at https://scrye.com/~kevin/fedora/f41-rebuild-tagging
I think we can close this now?
+1, closing this as done; The retirement issue is being fixed in another ticket!
Metadata Update from @jnsamyak: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.