Learn more about these different git repos.
Other Git URLs
The fedora 34 schedule[1] has a mass rebuild scheduled for Jan 20 2021, We need to plan and coordinate all tasks in preparation for it.
[1] https://fedorapeople.org/groups/schedule/f-34/f-34-key-tasks.html
There's also boost ( https://pagure.io/fesco/issue/2524 ) which doesn't have a releng ticket?
But I talked with @trodgers and he planned to build the new boost today so it's just used in the mass rebuild and clean up any issues after that. (He's done test builds of all dependent packages and it's much less messy than previous boost upgrades).
There's also boost ( https://pagure.io/fesco/issue/2524 ) which doesn't have a releng ticket? But I talked with @trodgers and he planned to build the new boost today so it's just used in the mass rebuild and clean up any issues after that. (He's done test builds of all dependent packages and it's much less messy than previous boost upgrades).
https://fedoraproject.org/wiki/Changes/F34Boost175 has been updated with releng ticket #9954
There is currently an issue building Boost due to a regression in the most recent GCC package
should be fixed in gcc-11.0.0-0.15.fc34
Please wait for https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/Z4A3S5REIMZ2MSIOMYWRDTROCALCEF2K/ before starting this.
There is currently an issue building Boost due to a regression in the most recent GCC package should be fixed in gcc-11.0.0-0.15.fc34
There is a new issue with latest GCC -
https://pagure.io/releng/issue/9858#comment-711037
Which is affecting the Boost package build
Metadata Update from @mohanboddu: - Issue tagged with: high-gain, high-trouble, ops
Things that needs to be done before starting this mass rebuild:
make
Status on 32bit arm builders:
I lowered the memory on the builder building gcc right now to 8gb. So far it's still going and it's past where others have hit OOM kill.
I have things ready to just roll back to old f32 builders + old kernel.
So, please don't start the mass rebuild until I get in tomorrow and we discuss what we want to do. If it's just lowering memory it should be pretty easy to do quickly. Reinstalling will take a bit longer.
Mass rebuild is now done.
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.