Just a small ping here.

We map the bootstrap module to this tag in PDC and having the repo would be, while costly, helpful for, among other things:

• testing local builds against the bootstrap set (affects Base Runtime, mainly)
• having the repodata in one public place for Base Runtime build dependency resolution and tracking
• bootstrapping other disconnected releases / derived distros

Please, consider creating it. Thank you.

Another ping.

closing this as invalid, the cost of such a repo is too high, we have a consistent location for the repo from the modular compose already

The modular compose doesn't and won't contain packages included in this tag. This tag is used for bootstrapping purposes.

Since you repeatedly mention the cost, could you elaborate what it actually means for you? This repo rarely changes, if ever. We don't need it mirrored anywhere. Is it the disk space? Can't really think of anything else.

Once again, we need this repo! :)

Updating the old reasons listed above:

• testing local module builds against boostrap:f26 -- we have a workaround for that; mbs-build doesn't expect any koji repositories for modules and downloads tag contents for the user; also, ODCS will make this more user friendly, hence this is no longer a problem
• having the repodata in one public place for dependency tracking -- we currently use frozen traditional Fedora repositories plus a manually currated override repo; ODCS will also make this easier; no longer valid
• bootstrapping other disconnected releases / derived distros -- still relevant, however module-bootstrap-rawhide (which does have a repo!) can be used for this unless people want to fork F26 Boltron specifically; only partially relevant

I have two new arguments in favor of bootstrap:f26:

• we have a repo for its equivalent in f27/rawhide, module-bootstrap-rawhide, and it seems to be okay; doing so for Boltron would improve consistency across releases
• unless a working alternative solution is proposed, it's necessary to build any Boltron images -- the tag includes lorax and is passed to koji runroot by pungi; without a repository, koji has nowhere to install lorax from (there's more to this point but having a repo created from this specific tag would unblock F26 Boltron image builds at this point)

@ausil, I found a free slot in your calendar and scheduled a quick call about this. Let's see if we can make this happen or find some workaround.

Note that ideally Koji runroot handler could call newRepo instead of blindly calling waitrepo in a hope kojira will generate it. That waitrepo currently fails, because there is no target...

Which might be the preferred long term solution but for now a simple kojira managed repo would be easier to deploy. As agreed during the call, I'll create a new ticket for this.

anything we ship can not use koji repos, they do not have signed rpms. All of boltron needs to be coming from a compose.

however as we made the repos for rawhide we should do the same for f26, they however are not suitable for production uses.

@ausil Thank you! I intend to use this for koji runroot so that it can install lorax from the tag/repo which will in turn source RPMs from the (signed) modular compose and create the installer and other media using those. I hope that's fine. Later on even the bootstrap module should be rebuilt and signed. Someday.

To make this work in staging I also had to do two more things; my plan was to put it all in a new ticket but you were faster :)

• define the build group for the tag as runroot installs it for some reason
• set mock.package_manager to dnf as it fails to do so with yum

I'll make a new ticket for that.

Tag changes requested in https://pagure.io/releng/issue/6868