Description of problem: In my copr project, https://copr.fedorainfracloud.org/coprs/waby38/4kopen I've enabled both fedora-33-armhfp & fedora-34-armhfp After sending a build generation from (example) copr-cli build waby38/4kopen ply-2.1.1-2.fc34.src.rpm => 2 x build success https://copr.fedorainfracloud.org/coprs/waby38/4kopen/build/2153615/ fedora-33-armhfp is ok, fedora-34-armhfp is broken https://download.copr.fedorainfracloud.org/results/waby38/4kopen/fedora-34-armhfp/02153615-ply/ => .rpm are build for fc35 armhfp => builder-live.log.gz show that they are using FC35 rpm for building https://download.copr.fedorainfracloud.org/results/waby38/4kopen/fedora-34-armhfp/02153615-ply/builder-live.log.gz Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. enable both fedora-33-armhfp & fedora-34-armhfp in settings=> project details => builds options 2. use "copr-cli build .src.rpm" to build your .rpm 3. check result in fedora-34-armhfp directory Actual results: content of fedora-34-armhfp is a FC35 armhfp build Expected results: fedora-34-armhfp should build for FC34 armhfp Additional info:
Thank you for the report and sorry for the late reply, this was missed by our radar.
Fix is here: https://pagure.io/fedora-infra/ansible/c/304432fc88957820670b1d0e2665c77fbac1350a?branch=main https://pagure.io/fedora-infra/ansible/c/3de1d7fa0d85cf6e708d5ca9325f013a4d5dcca2?branch=main Will be deployed to production tomorrow, via: https://pagure.io/fedora-infrastructure/issue/10034
Thanks for the fix, I confirm that now build are corrects for fedora 34/armhfp You can close this BZ
Thanks, closing then.