Learn more about these different git repos.
Other Git URLs
@carlwgeorge and I discovered that if we have a COPR project build a package for EPEL 8 and want to use that as a dependency to replace an older build-side module-provided package, we can't, even though the build copr project is marked as a repo providing module hotfixes.
This is preventing us from building Caddy v2 for EPEL 8.
The build repo provides golang version 1.14, and we need that to build caddy. We don't want it in the main repo because we don't want it published to people and surprising them with a new golang when they don't need it.
golang
Hmm, apparently this works now, so nevermind?
Metadata Update from @ngompa: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
@ngompa yes, AFAIK it should work. We even have a test for this case
# When there is a project foo with module_hotfixes set to False, but using a project bar with # module_hotfixes set to True as an external repository, the bar should be used with that configuration
Sorry for the noise. It failed as recently as 2020-02-09, but indeed it works now. Thanks!
Login to comment on this ticket.