copr-devel July 2022

copr-devel@lists.fedorahosted.org

4 participants
4 discussions

Re: [Copr] flug_m/duo_unix: flugm4 is requesting permissions change
by Matthew Roth 29 Jul '22

29 Jul '22

yes > On Jul 28, 2022, at 4:08 PM, root(a)copr-fe.aws.fedoraproject.org wrote: > > flugm4 asked for these changes: > > Admin: nothing -> request > > Project: flug_m/duo_unix

2 1

Outage: Upgrade of Copr servers - 2022-07-27 08:00 UTC
by Jakub Kadlčík 28 Jul '22

28 Jul '22

Hello, There will be an outage starting at: $ date --date '2022-07-27 08: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 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/10830

1 2

COPR modular odds
by Cristian Balint 14 Jul '22

14 Jul '22

Dear COPR Team, Would like to ask a few questions after hitting odds trying to use the modular features. My interest is the ability to have mixed stable/nightly releases (user switchable), so the modularity feature would be ideal. After looking at several related online resources including copr-framework source code I decided to ask right here: #1. Using specific modulemd.yaml, the new module +creates , +builds, +tags all components picked via repo/ref git path. $ copr build-module test --yaml dummy.yaml - But running once again (trying to add updated package) with updated ref/tags leads to errors: $ copr build-module test --yaml dummy.yaml "Module dummy-master-20220701234448 already exists" Q: Then how can add *newer* package builds to an existing module ? Q: Modular builds in the web-frontend expose +extra "Module:" tag, how can copr-cli launch builds into such a module-tag ? #2. Let's assume at #1 modules are created *once* as fixed object and it is not possible to add/alter with newer package builds: Q: How can one delete an existing module from COPR (assume it was created erroneously or obsoleted) ? Q: How can I avoid having (too) many separate *.repo for each separate module within a single project ? Q: Is there a unified way to add only once a *.repo (easy to advertise URL) and see all the modules within that project ? Thank you, ~Cristian.

2 1

Unplanned Copr outage - 2022-07-08 and 2022-07-09
by Pavel Raiskup 09 Jul '22

09 Jul '22

Copr failed to allocate VMs and assign VMs to the build task for several hours now, which lead to many build failures. Please restart the builds if you were affected. The issue is tracked here: https://pagure.io/copr/copr/issue/2066 Sorry for inconveniences. Pavel

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

copr-devel July 2022