When building take into account all overrides which were done in bodhi/koji

[FrostyX]

Original issue: https://bugzilla.redhat.com/show_bug.cgi?id=1360251
Opened: 2016-07-26 10:48:12
Opened by: Igor Gnatenko

---

Igor Gnatenko commented at 2016-07-26 10:48:12:

no idea how exactly to do this, but would be nice to have.

---

Igor Gnatenko commented at 2016-07-26 10:56:13:

#1 use-case:

• https://lists.fedoraproject.org/archives/list/[email protected]/message/5DAXFPMJEIISHLKNCYTGYMDLBW2F5GKK/
  our CI uses all packages from Fedora and it uses COPR to build new packages. But current release is completely broken (see above), so I added override, but COPR doesn't use it -> CI is broken

#2 use-case:
it's obvious. if you do override in bodhi and build package in koji, you will get one package, if you do this from COPR you will get different package

---

Miroslav Suchý commented at 2016-07-27 14:11:16:

It can be probably handle by repo priorities.

---

Igor Gnatenko commented at 2016-07-27 14:19:49:

(In reply to Miroslav Suchý from comment #2)

It can be probably handle by repo priorities.

it's not about priorities as we don't have it in repos (yet).

---

commented at 2018-04-09 08:03:46:

(In reply to Igor Gnatenko from comment #1)

#1 use-case:
*
https://lists.fedoraproject.org/archives/list/[email protected]/
message/5DAXFPMJEIISHLKNCYTGYMDLBW2F5GKK/
our CI uses all packages from Fedora and it uses COPR to build new packages.
But current release is completely broken (see above), so I added override,
but COPR doesn't use it -> CI is broken

#2 use-case:
it's obvious. if you do override in bodhi and build package in koji, you
will get one package, if you do this from COPR you will get different package

Koji+Bodhi and COPR are (at the moment) completely separate systems. You can't expect any setting from Bodhi to propagate to COPR unless we would integrate it with Bodhi somehow first. Not saying it won't happen but it would be better now to try to solve the problem by what COPR provides on its own. Also note that COPR uses public mirrors to get packages, which is another factor here.

You should be able to do those overrides described in #1 use-case by setting up a repo with the override package and then using that repo as and additional repository for your copr and setting lower priority for it (see https://pagure.io/copr/copr/issue/97).

You may also just try to put URL to the override package (somewhere publicly avaiable) into Additional Packages for the given chroots where you want to build. I suppose, mock will use that buildroot package afterwards during the builddeps resolution phase.

---

Pavel Raiskup commented at 2020-12-14 09:43:53:

I think we could make use of mock --enablerepo=<pre-configured-id> (in our
case the id would be local) easier in Copr, would that help? Koji should
handle Copr requests just fine (infra ticket 9480).

[praiskup]

The work-around is to specify external build repositories, but still would be nice to have.

[praiskup]

Related infra question: https://pagure.io/fedora-infrastructure/issue/9480