copr-devel May 2023

copr-devel@lists.fedorahosted.org

3 participants
5 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

Outage: Upgrade of Copr servers - 2023-05-25 10:00 UTC
by Jakub Kadlcik 29 May '23

29 May '23

Hello, There will be an outage starting at: $ date --date '2023-05-25 10: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. Jakub

1 2

Re: Obsolete of DNF by DNF5 in RAWHIDE
by Miro Hrončok 26 May '23

26 May '23

On 24. 05. 23 9:40, Jaroslav Mracek wrote: > Hello, > > I have great news that the upcoming release of DNF5 will obsolete DNF in > rawhide (Fedora 39). The release is planned not before the end of May. The > change was already announced in > https://fedoraproject.org/wiki/Changes/ReplaceDnfWithDnf5 > <https://fedoraproject.org/wiki/Changes/ReplaceDnfWithDnf5>. It seem rawhide copr builds are broken... To reproduce, try: $ COPR=whatever $ copr create $COPR --repo='http://kojipkgs.fedoraproject.org/repos/rawhide/latest/$basearch/' --chroot fedora-rawhide-x86_64 --delete-after-days 7 $ copr add-package-distgit $COPR --name dummy-test-package-gloster --commit rawhide $ copr build-package $COPR --name dummy-test-package-gloster See https://copr.fedorainfracloud.org/coprs/churchyard/whatever/builds/ I get: ... Finish(bootstrap): dnf install Start(bootstrap): creating root cache Finish(bootstrap): creating root cache Finish(bootstrap): chroot init Start: chroot init INFO: mounting tmpfs at /var/lib/mock/fedora-rawhide-x86_64-1685094318.073555/root. INFO: calling preinit hooks INFO: enabled root cache INFO: enabled package manager cache Start: cleaning package manager metadata Finish: cleaning package manager metadata INFO: enabled HW Info plugin Mock Version: 3.5 INFO: Mock Version: 3.5 Start: dnf install Unknown argument "--allowerasing" for command "dnf5". Add "--help" for more information about the arguments. WARNING: Dnf command failed, retrying, attempt #2, sleeping 10s Unknown argument "--allowerasing" for command "dnf5". Add "--help" for more information about the arguments. WARNING: Dnf command failed, retrying, attempt #3, sleeping 10s Unknown argument "--allowerasing" for command "dnf5". Add "--help" for more information about the arguments. ERROR: Exception(/var/lib/copr-rpmbuild/workspace/workdir-0s4wy2p4/dummy-test-package-gloster/dummy-test-package-gloster.spec) Config(fedora-rawhide-x86_64) 1 minutes 26 seconds INFO: Results and/or logs in: /var/lib/copr-rpmbuild/results INFO: Cleaning up build root ('cleanup_on_failure=True') Start: clean chroot INFO: unmounting tmpfs. Finish: clean chroot ERROR: Command failed: # /usr/bin/systemd-nspawn -q -M fb947d9bf50448af8a0250f849d154de -D /var/lib/mock/fedora-rawhide-x86_64-bootstrap-1685094318.073555/root -a --capability=cap_ipc_lock --rlimit=RLIMIT_NOFILE=10240 --capability=cap_ipc_lock --bind=/tmp/mock-resolv.4as66jul:/etc/resolv.conf --console=pipe --setenv=TERM=vt100 --setenv=SHELL=/bin/bash --setenv=HOME=/var/lib/mock/fedora-rawhide-x86_64-1685094318.073555/root/installation-homedir --setenv=HOSTNAME=mock --setenv=PATH=/usr/bin:/bin:/usr/sbin:/sbin --setenv=PROMPT_COMMAND=printf "\033]0;<mock-chroot>\007" --setenv=PS1=<mock-chroot> \s-\v\$ --setenv=LANG=C.UTF-8 --setenv=LC_MESSAGES=C.UTF-8 --setenv=SYSTEMD_NSPAWN_TMPFS_TMP=0 --setenv=SYSTEMD_SECCOMP=0 --resolv-conf=off /usr/bin/dnf --installroot /var/lib/mock/fedora-rawhide-x86_64-1685094318.073555/root/ --releasever 39 --setopt=deltarpm=False --allowerasing --disableplugin=local --disableplugin=spacewalk --disableplugin=versionlock install @buildsys-build --setopt=tsflags=nocontexts --setopt=tsflags=nocontexts --setopt=tsflags=nocontexts Unknown argument "--allowerasing" for command "dnf5". Add "--help" for more information about the arguments. Copr build error: Mock build failed -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok

1 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

Disabling Fedora 36 chroots in Copr
by Jiri Kyjovsky 22 May '23

22 May '23

Hello, we have just disabled Fedora 36 chroots in Copr. According to the Fedora wiki [1], Fedora 36 reached the end of its life on 2023-05‑16 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: - fedora-36-x86_64 - fedora-36-i386 - fedora-36-ppc64le - fedora-36-aarch64 - fedora-36-armhfp - fedora-36-s390x Additionally, according to Outdated chroots removal policy [2], 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 [3]. [1] https://fedoraproject.org/wiki/End_of_life [2] https://docs.pagure.org/copr.copr/copr_outdated_chroots_removal_policy.html [3] http://frostyx.cz/posts/copr-removing-outdated-chroots Kind regards Jiri Kyjovsky

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

copr-devel May 2023