copr-devel June 2023

copr-devel@lists.fedorahosted.org

4 participants
4 discussions

Mock/Copr default epel-8-* configuration to be changed
by Pavel Raiskup 29 Jul '25

29 Jul '25

Hello Fedora EPEL maintainers! First I don't feel comfortable announcing this, I'm not happy about the situation and so I don't want to be the lightning rod :-). But I believe that we can come to acceptable Copr/Mock solution and this needs to be discussed... so here we are. By the end of the year 2021 we have to fix our default EPEL 8 Mock configuration (mock-core-configs.rpm, /etc/mock/epel-8-*.cfg) as CentOS 8 goes EOL by then. The same thing needs to happen in Fedora Copr, with the epel-8-* chroots (side note, in Fedora Copr we use the mock-core-configs package for builds without any deployment specific modifications). I am proposing (as PR against mock upstream ATM [1]) to switch the default epel-* configuration from CentOS+EPEL to RHEL+EPEL as soon as possible (see the pull request [1]). This would bring some consequences, namely newly with epel-8* chroots, - builds will require a valid Red Hat subscription (the no-cost variant is OK as well, though [2]) - we will miss some build-time packages that Red Hat is not shipping, at least at the beginning till they are added (to RHEL CRB, or other currently unknown place). - cross-arch compilation can not be used, Red Hat subscriptions don't allow that (using QEMU and rpm --forcearch), [3] The positive thing is that the default configuration will be much closer to the official EPEL builds (because Fedora Koji EPEL builds are actually done also against RHEL). For the Fedora Copr builders, we already have the necessary Red Hat subscriptions in hand (will be deployed by the end of the year). So we will only loose the opportunity to build on emulated epel-8-armhfp permanently, and epel-8-s390x temporarily (as we already work on the native s390x support). Any thoughts? Feedback is needed here. [1] https://github.com/rpm-software-management/mock/pull/802 [2] https://rpm-software-management.github.io/mock/Feature-rhelchroots [3] https://bugzilla.redhat.com/show_bug.cgi?id=1912847 Pavel

11 22

Oracle Linux chroots (temporarily) available in Fedora Copr
by Pavel Raiskup 17 Jul '23

17 Jul '23

Hello, just a quick note - we enabled Oracle Linux chroots in Fedora Copr today, this is temporarily needed by OAMG/LEAPP team for their CI/CD system. Feel free to test those chroots, but please don't heavily depend on them as we don't know when we'll again drop them (preferably use epel/centos-stream chroots instead, they should provide similar build results). Pavel

2 2

Strange problem with builds failing very early
by Steven A. Falco 21 Jun '23

21 Jun '23

Hi - For a while the following project has been building fine: https://copr.fedorainfracloud.org/coprs/g/kicad/kicad-testing/builds/ In the last few days, the automatic builds have been failing very early, without too much useful information. However, manual builds that I trigger from my own ID work fine. Is there a way I can get more information on what is going wrong? I see a link in the builder-live.log.gz, but I'm not able to use that link. The following command gives me a 404, perhaps because the build was triggered by another member of the project: /usr/bin/copr-rpmbuild --verbose --drop-resultdir --srpm --task-url https://copr.fedorainfracloud.org/backend/get-srpm-build-task/6102419 ... Network error: Request client error on https://copr.fedorainfracloud.org/tmp/tmpf1cg4teq/kicad-testing.spec: 404 NOT FOUND Steve

1 1

Fedora Copr builders updated to Fedora 38
by Pavel Raiskup 14 Jun '23

14 Jun '23

Hello maintainers! Copr builders have been updated to Fedora 38 today (some old builders might still be running F37 ATM, but when they finish the task(s) they work on, they will be deleted). Our testsuite is passing just fine, so you _should_ be fine too :-). Please let us know if you have some troubles. There was one important change in Fedora 38 - RPM switched to the Sequoia crypto backend. It refuses SHA-1 in crypto; which basically disallows Mock to properly check EL6 GPG signatures. To allow further builds, we switched to gpgcheck=0 for all epel-6 chroots. If you know a better work-around, let me know. Pavel

3 8

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

copr-devel June 2023