Koji: How to handle internal package moved to external repo?

[Dustin C. Hatch]

I have encountered a situation where a newer version of package I used
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 installed.
Now, though, that package, specifically the new version of it, is needed
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 my
build tag, Koji always prefers that version, even though it is older
than the version in the external repository. I have tried blocking the
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.

Thanks,

-- 
♫Dustin