I have changed default branch for our github.com projects:
(all but copr which already used main)
To change it it your local checkout please do:
git branch -m master main
git fetch origin
git branch -u origin/main main
It mainly affects:
And, yes, I changed the default branch for github pages generator too. So the blog should work correctly.
Miroslav Suchy, RHCA
Red Hat, Associate Manager, Community Packaging Tools, #brno, #fedora-buildsys
Since ld.gold segfault on Fedora 33 and rawhide when it uses more than
one thread , I switched my Chromium builds to use ld.bfd a few months
ago. The change increased the build time, but at least the build didn't
fail in 1 hour due to ld.gold segfault.
It seems that Chromium 87 increases the build time further with its
Ozone platform. Now it is very hard to get successful builds of Chromium
87 on Copr. After submitting Chromium 87.0.4280.66 builds for more than
10 times, I still couldn't get successful builds for all chroots. Even
if there were successful builds in some chroots, the build time was
pretty close to the limit. For example, this build  took 29h 50m for
Fedora 33, and this build  took 29h 52m for Fedora rawhide.
Is it possible to raise the limit again? Given that Chromium keeps
increasing the build time for the past 2 years, I think we should raise
the limit to 48 hours this time.
we observe more and more people using Copr for rebuilding large amounts
of packages from some third-party repositories. We have projects
providing all python packages, R packages, we have projects providing
all Fedora packages rebuilt with some proposal change, etc.
These are all valid use-cases and Copr should be able to sustain such
loads (even though we still have some bottlenecks to get rid of).
To make the mass-rebuilding experience better for new users, we put
together a short list of best practices.
If you think that some useful tip is missing, let us know.
Thank you and happy building,