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, 10 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, 10 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, 11 months
Fwd: [CentOS-devel] CentOS Stream enabled in Copr
by Miroslav Suchý
-------- Přeposlaná zpráva --------
Předmět: [CentOS-devel] CentOS Stream enabled in Copr
Datum: Tue, 15 Oct 2019 14:33:34 +0200
Od: Miroslav Suchý <msuchy(a)redhat.com>
Komu: The CentOS developers mailing list. <centos-devel(a)centos.org>
Hi.
FYI - I just added
centos-stream-x86_64
centos-stream-aarch64
centos-stream-ppc64le
to https://copr.fedorainfracloud.org/
You can build your packages for these chroots now.
--
Miroslav Suchy, RHCA
Red Hat, Associate Manager ABRT/Copr, #brno, #fedora-buildsys
_______________________________________________
CentOS-devel mailing list
CentOS-devel(a)centos.org
https://lists.centos.org/mailman/listinfo/centos-devel
3 years, 11 months
Does copr git support lfs?
by zdm@softvisio.net
I have git repo, that contains .spec file and .tar.gz archive with the
sources. .tar.gz commited to git as lfs object.
Seems, that currently copr build system can't clone git with lfs files
correctly?
3 years, 11 months
Let's Encrypt certificate expiration notice for domain "copr-be-dev.cloud.fedoraproject.org"
by Let's Encrypt Expiry Bot
Hello,
Your certificate (or certificates) for the names listed below will expire in 19 days (on 24 Oct 19 13:38 +0000). Please make sure to renew your certificate before then, or visitors to your website will encounter errors.
We recommend renewing certificates automatically when they have a third of their
total lifetime left. For Let's Encrypt's current 90-day certificates, that means
renewing 30 days before expiration. See
https://letsencrypt.org/docs/integration-guide/ for details.
copr-be-dev.cloud.fedoraproject.org
For any questions or support, please visit https://community.letsencrypt.org/. Unfortunately, we can't provide support by email.
For details about when we send these emails, please visit https://letsencrypt.org/docs/expiration-emails/. In particular, note that this reminder email is still sent if you've obtained a slightly different certificate by adding or removing names. If you've replaced this certificate with a newer one that covers more or fewer names than the list above, you may be able to ignore this message.
If you are receiving this email in error, unsubscribe at http://mandrillapp.com/track/unsub.php?u=30850198&id=82be867e409d4251be4f...
Regards,
The Let's Encrypt Team
3 years, 12 months