On 2017-07-23 21:40, Dennis Gilmore wrote:
El mié, 19-07-2017 a las 08:14 -0500, Dustin C. Hatch escribió:
> I have encountered a situation where a newer version of package I
> to build in my instance of Koji is now provided by an external
> repository. Until recently, everything has worked fine because the
> package was only a runtime dependency, so as long as the external
> repository was configured in Yum, the newer version would be
> Now, though, that package, specifically the new version of it, is
> at build time, and I cannot figure out how to make this work.
> Since there is a build of the package tagged, via inheritance, into
> build tag, Koji always prefers that version, even though it is older
> than the version in the external repository. I have tried blocking
> package, but this makes it unavailable entirely.
> Is there any way I can get around this problem. The only thing I can
> come up with is to remove the inherited tag and copy the builds in it
> directly into my new tag, but I am hoping there is a better or
> simpler way.
For EPEL when a package moves from EPEL to RHEL we untag all the builds
in the epel tags, block the package in the epel tag unblock it in the
-build tag so that the RHEL builds show up in the build root but we
ensure that people do not accidently build and ship a new version in
Thanks Dennis. I will see if I can make something like that work in my
The Fine Manual: