copr-devel September 2022

copr-devel@lists.fedorahosted.org

5 participants
7 discussions

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

18 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

ATTENTION: Copr will be temporarily deleting failed and outdated builds after 7 days
by Jiri Kyjovsky 21 Oct '22

21 Oct '22

Hello, Due to problems with free disk storage, Copr will be temporarily deleting failed and outdated builds after 7 days instead of the default 14 days until migration to another disk storage takes place. Best regards Copr Team

4 3

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

Inconsistency of bash behaviour on fedora aarch64 and x86_64 images
by TommyLike Hu 28 Sep '22

28 Sep '22

Hey COPR Developers, Recently, I am trying to deploy COPR containers on an arm instance, except for the base image and resalloc pool tag issues, I also found there is a strange thing on bash command, check this code from dist-git [1] below: ``` if [ ! -w $REPODIR ] ; then echo "ERROR: You can not write to $REPODIR" echo "ERROR: You can not create repos" exit -1 fi ``` This would always fail in an aarch64 container which uses the identical dockerfile as the x86 ones. ``` FROM registry.fedoraproject.org/fedora:35 MAINTAINER copr-devel(a)lists.fedorahosted.org ``` Could this be a fedora issue? Considering I tried fedora 35/36/37 which all failed. [1]: https://github.com/release-engineering/dist-git/blob/738dc51b8dff6f06a3d4be…

3 7

Outage: Upgrade of Copr servers - 2022-09-21 13:00 UTC
by Jakub Kadlčík 21 Sep '22

21 Sep '22

Hello, There will be an outage starting at: $ date --date "2022-09-21 13: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/10906

2 1

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

02 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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

copr-devel September 2022