Armhfp chroots added to Copr
by Dominik Turecek
Hello,
we've enabled emulated armhfp chroots for F31 and rawhide
in Copr.
Note that the chroots are emulated on x86_64 builders using
forcearch [1], so expect that builds might behave differently
especially when you're doing some low-level coding.
Depending on how CPU intensive they are, they might
take up to ten times longer (and in some cases even more)
to finish than normal.
We're planning to enable more armhfp chroots later on based
the performance of the first two.
[1]: https://github.com/rpm-software-management/mock/wiki/Feature-forcearch
Dominik Tureček
3 years, 6 months
Temporarily using `best=False' for EPEL-8 builds in Copr
by Jakub Kadlcik
Hello,
currently, there is a problem with building EPEL-8 packages because of
DNF bugs regarding modularity (see RHBZ 1758459).
The only known workaround is to use DNF with `best=False'. Even though
it is something you don't really want to use longterm, we are patching
mock configs epel-8-* chroots, so there can be at least some EPEL-8
building in Copr.
(I am doing the change right now, but it won't affect already
spined-up builders. It will take a while until they get recycled and
use new configuration)
Once the DNF issues get resolved, we are going to drop those patches
and use `best=True` again.
For additional information, please see RHBZ 1756681 and RHBZ 1758467.
Thank you for understanding,
Jakub
3 years, 6 months
Backend storage clean-up
by Jakub Kadlcik
Hello,
we have decided that it is a time to go through Copr backend data and
clean it up a little. Due to several bugs forgetting to remove backend
data after removing their records from the database, _temporarily_
backing up some folder here and there, etc, we ended up with a lot of
unknown data, that should have been already deleted.
So, we wrote a script [1] to find data that should be deleted, and we
... haven't deleted it yet. Instead, we put it aside in a case there
were any false-positives by the script. If you want to be extra safe,
I am attaching a list of all of those files, you may check it.
If you find out, that we accidentally want to remove any of your data
that is still being used, please contact us immediately! Otherwise, we
are going to delete it once we are running out of disk space (which
may not take a lot of time)
[1] https://pagure.io/copr/copr/blob/master/f/backend/run/copr_print_results_...
Thank you for understanding,
Jakub
3 years, 6 months
aarch64 builders are extremly slow
by Jean-Marc Liger
Hi Team,
It takes many hours for aarch64 to finish builds that it takes only one
hour for ppc64le. Are there any tweaking ways to improve the build speed ?
Regards,
Jean-Marc
3 years, 6 months
Disabling RHEL 8 beta chroots in Copr
by Tomas Hrnciar
Hello,
we have just disabled RHEL 8 beta chroots in Copr. RHEL 8 beta reached the
end of its life and therefore we are disabling it in Copr. That effectively
means that from this moment, it is no longer possible to submit builds for
the following chroots: - rhelbeta-8-x86_64 - rhelbeta-8-aarch64.
Additionally, according to Outdated chroots removal policy [1], Copr is
going to preserve existing build results in those chroots for another 180
days and then automatically remove them unless you take an action and
prolong the chroots life span in your projects. Read more about this
feature in the Copr - Removing outdated chroots blog post [2].
[1]
https://docs.pagure.org/copr.copr/copr_outdated_chroots_removal_policy.html
[2] http://frostyx.cz/posts/copr-removing-outdated-chroots
Tomas
3 years, 6 months
