copr-devel August 2022

copr-devel@lists.fedorahosted.org

7 participants
9 discussions

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

Excluding older builds of packages from Fedora when testing new ones in Copr
by Miro Hrončok 24 May '23

24 May '23

Hello Copr users and developers. When we update packages in Fedora, we regularly use Copr to test the impact of the upgrade. For me, the procedure usually goes like this: 1) create a new copr with Fedora rawhide x86_64 chroot (and added Koji repo) $ copr create $COPR --repo='http://kojipkgs.fedoraproject.org/repos/rawhide/latest/$basearch/' --chroot fedora-rawhide-x86_64 --delete-after-days 30 2) define and build the updated package in the copr $ copr add-package-distgit $COPR --name $PKG --webhook-rebuild on --commit $BRANCH --namespace forks/$(whoami) $ copr build-package $COPR --name $PKG 3) get the list of dependent packages $ repoquery -q --repo=rawhide{,-source} [--whatrequires $spkg for each subpackage] --recursive | grep src$ | pkgname 4) define and build the depended packages in the copr $ parallel copr add-package-distgit $COPR --webhook-rebuild on --commit rawhide --name -- $(repoquery from above ...) $ parallel copr build-package $COPR --nowait --background --name -- $(repoquery from above ...) 5) analyze build failures, do a "control" rebuild in another copr if needed However, this procedure has a flaw. Let's say I'm working on upgrading python-click from 7.x to 8.x. And let's say a package (even transitively) BuildRequires: python3dist(click) < 8 The way that dnf dependency resolution works, that package will be built with Rawhide's python3-click 7.x and it will be marked as successful. However, I'd like to see a failure here to be notified that such package cannot be build and will be negatively impacted by the update. Is there a way to solve this? I have couple ideas, but none of them is fully working: A) Compose my own repo with the updated package and Rawhide content without it, use that repo in the copr. Pros: - this is similar to what will happen in Koji once the package is updated Cons: - this requires tooling that I don't think exists - this requires a place to put that repo to - the repo creation could take a lot of time and would need to be repeated on-demand each time rawhide changes - Copr's Fedora chroots always include Fedora repos (maybe I can use custom-1-x86_64 chroot?) B) Create a Fedora side tag, explicitly block the package from it, use that side tag's Koji repo. Pros: - same as (A) Cons: - I don't think on-demand side tags allow users to block packages - Copr's Fedora chroots always include Fedora repos (same as (A)) - this wastes Koji's resources a bit - requires waiting for the initial Koji regen-repo C) Block (exclude) python3-click < 8 from the chroot. Pros: - no custom repos required - no resources overhead - no time overhead Cons: - There is no way exclude packages in chroot settings. Mock settings possibly allow me to do this in config_opts['dnf.conf']. - The exclude could obfuscate root.log resolution problems logs. - Packager needs to figure out what exactly to exclude (possibly need to exclude all subpackage's NEVRAs from rawhide compose (and Koji buildroot if they differ)) Is there another way? If not, I think (C) is easiest to actually implement, if the chroot settings page in copr gains an "excludes" option. -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok

3 7

Running COPR on kubernetes cluster?
by TommyLike Hu 30 Sep '22

30 Sep '22

Hey COPR team, Is there any document on how to run a COPR server on the kubernetes cluster? Including the builder if it's possible.

3 8

Suggestion: Make it obvious where the build logs?
by Barry Scott 01 Sep '22

01 Sep '22

I'm looking at this page: https://copr.fedorainfracloud.org/coprs/barryascott/python-qt6/build/476920… Status: failed - Build failed. See logs for more details. I do not see an obvious link to the "logs" that it is telling to me view. After enough clicking I figured out that its in the chroot that I need to look. Maybe make "See logs for more details." link logs to the chroot? Barry

2 3

Removing fedora-37-armhfp chroot
by Jakub Kadlčík 30 Aug '22

30 Aug '22

Hello, today we were made aware that it is possible to build for fedora-37-armhfp in Copr and that such builds immediately fail. That is because the armhfp architecture was discontinued since Fedora 37, meaning that Fedora 36 is the last version that supports it. For more information, please read https://fedoraproject.org/wiki/Changes/RetireARMv7 The fedora-37-armhfp chroot was added into Copr accidentally, and I am now disabling it. Jakub

1 0

Outage: Upgrade of Copr servers - 2022-08-18 12:00 UTC
by Jakub Kadlčík 18 Aug '22

18 Aug '22

Hello, There will be an outage starting at: $ date --date '2022-08-18 12:00 UTC' The outage will last approximately 3 hours. The copr-backend storage (copr build results) will stay mostly online during this outage but some downtime is expected. Reason for outage: We're updating copr packages to the new versions which will bring new features and bugfixes. Affected Services: copr-frontend - https://copr.fedorainfracloud.org copr-backend - https://copr-be.cloud.fedoraproject.org/ Contact persons: @frostyx / @praiskup / @nikromen Please join #fedora-admin in irc.libera.chat or add comments to the ticket for this outage above. Ticket: https://pagure.io/fedora-infrastructure/issue/10855 Jakub

1 1

Fedora 37 branched
by Pavel Raiskup 15 Aug '22

15 Aug '22

Hi, Fedora 37 has been branched recently. We started the branching process: https://docs.pagure.org/copr.copr/how_to_manage_chroots.html#branching-proc… ATM we submitted a task for copying fedora-rawhide builds into fedora-37, this should be finished in about 24 hours. Currently, updates for mock-core-configs (with F37 configs) are being submitted to Bodhi. But note that we can not enable F37 in Copr till there's a working compose and mirrors work (not at this moment). Pavel

1 1

Fedora Rawhide builds failing due to missing GPG key?
by Richard Shaw 15 Aug '22

15 Aug '22

Seeing this on all my rawhide builds: KEY-fedora-36-primary Public key for which-2.21-35.fc37.x86_64.rpm is not installed. Failing package is: which-2.21-35.fc37.x86_64 GPG Keys are configured as: file:///usr/share/distribution-gpg-keys/fedora/RPM-GPG-KEY-fedora-37-primary, file:///usr/share/distribution-gpg-keys/fedora/RPM-GPG-KEY-fedora-37-primary, file:///usr/share/distribution-gpg-keys/fedora/RPM-GPG-KEY-fedora-36-primary Public key for xxhash-libs-0.8.1-3.fc37.x86_64.rpm is not installed. Failing package is: xxhash-libs-0.8.1-3.fc37.x86_64 GPG Keys are configured as: file:///usr/share/distribution-gpg-keys/fedora/RPM-GPG-KEY-fedora-37-primary, file:///usr/share/distribution-gpg-keys/fedora/RPM-GPG-KEY-fedora-37-primary, file:///usr/share/distribution-gpg-keys/fedora/RPM-GPG-KEY-fedora-36-primary Public key for xz-5.2.5-10.fc37.x86_64.rpm is not installed. Failing package is: xz-5.2.5-10.fc37.x86_64 GPG Keys are configured as: file:///usr/share/distribution-gpg-keys/fedora/RPM-GPG-KEY-fedora-37-primary, file:///usr/share/distribution-gpg-keys/fedora/RPM-GPG-KEY-fedora-37-primary, file:///usr/share/distribution-gpg-keys/fedora/RPM-GPG-KEY-fedora-36-primary Public key for xz-libs-5.2.5-10.fc37.x86_64.rpm is not installed. Failing package is: xz-libs-5.2.5-10.fc37.x86_64 GPG Keys are configured as: file:///usr/share/distribution-gpg-keys/fedora/RPM-GPG-KEY-fedora-37-primary, file:///usr/share/distribution-gpg-keys/fedora/RPM-GPG-KEY-fedora-37-primary, file:///usr/share/distribution-gpg-keys/fedora/RPM-GPG-KEY-fedora-36-primary Public key for zip-3.0-33.fc37.x86_64.rpm is not installed. Failing package is: zip-3.0-33.fc37.x86_64 GPG Keys are configured as: file:///usr/share/distribution-gpg-keys/fedora/RPM-GPG-KEY-fedora-37-primary, file:///usr/share/distribution-gpg-keys/fedora/RPM-GPG-KEY-fedora-37-primary, file:///usr/share/distribution-gpg-keys/fedora/RPM-GPG-KEY-fedora-36-primary Public key for zlib-1.2.12-4.fc37.x86_64.rpm is not installed. Failing package is: zlib-1.2.12-4.fc37.x86_64 GPG Keys are configured as: file:///usr/share/distribution-gpg-keys/fedora/RPM-GPG-KEY-fedora-37-primary, file:///usr/share/distribution-gpg-keys/fedora/RPM-GPG-KEY-fedora-37-primary, file:///usr/share/distribution-gpg-keys/fedora/RPM-GPG-KEY-fedora-36-primary Public key for zstd-1.5.2-3.fc37.x86_64.rpm is not installed. Failing package is: zstd-1.5.2-3.fc37.x86_64 GPG Keys are configured as: file:///usr/share/distribution-gpg-keys/fedora/RPM-GPG-KEY-fedora-37-primary, file:///usr/share/distribution-gpg-keys/fedora/RPM-GPG-KEY-fedora-37-primary, file:///usr/share/distribution-gpg-keys/fedora/RPM-GPG-KEY-fedora-36-primary Error: GPG check FAILED Thanks, Richard

2 1

Configuring tito's CoprReleaser to upload to copr.fedorainfracloud.org
by Matt Hickford 03 Aug '22

03 Aug '22

Hi. Can anyone point to an example of configuring tito's CoprReleaser [2] to upload SRPM to copr.fedorainfracloud.org ? Currently my copr package [1] builds from a GitHub repo but that's a problem because the rpm build [1] requires internet access. Thanks for reading -Matt [0] my copr package https://copr.fedorainfracloud.org/coprs/matthickford/git-credential-manager/ [1] my rpm spec https://github.com/hickford/git-credential-manager/blob/rpm/git-credential-… [2] https://github.com/rpm-software-management/tito/blob/master/releasers.conf.… [3] https://docs.pagure.org/copr.copr/user_documentation.html#tito

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

copr-devel August 2022