[releng] Issue #6696 `Repo out of f26-modularity tag`

[Adam Samalik]

asamalik reported a new issue against the project: `releng` that you are following:
``
The modularity team needs to be able to build modules using local module-build-service
(MBS). After some discussion on #fedora-modularity with @jkaluza and @psabata it appears I
need `f26-modularity` to appear at
[kojipkgs.fedoraproject.org/repos](https://kojipkgs.fedoraproject.org/repos/) so MBS can
use it as a buildroot for modules.

I probably want you to run `koji add-target f26-modularity-repo f26-modularity
f26-modularity`. (@jkaluza promised it's the right command)
``

To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/6696

[Petr Šabata]

psabata added a new comment to an issue you are following:
``
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.
``

To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/6696

[Petr Šabata]

psabata added a new comment to an issue you are following:
``
Another ping.
``

To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/6696

[Dennis Gilmore]

The status of the issue: `Repo out of f26-modularity tag` of project: `releng` has been
updated to: Closed as Invalid by ausil.

https://pagure.io/releng/issue/6696

[Dennis Gilmore]

ausil added a new comment to an issue you are following:
``
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
``

To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/6696

[Petr Šabata]

psabata added a new comment to an issue you are following:
``
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.
``

To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/6696

[Petr Šabata]

psabata added a new comment to an issue you are following:
``
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.
``

To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/6696

[Jan Kaluža]

jkaluza added a new comment to an issue you are following:
``
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...
``

To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/6696

[Petr Šabata]

psabata added a new comment to an issue you are following:
``
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.
``

To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/6696

[Dennis Gilmore]

ausil added a new comment to an issue you are following:
``
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.
``

To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/6696

[Dennis Gilmore]

The issue: `Repo out of f26-modularity tag` of project: `releng` has been assigned to
`ausil` by ausil.

https://pagure.io/releng/issue/6696

[Dennis Gilmore]

ausil added a new comment to an issue you are following:
``
```
[dennis@anubis ~]$ koji edit-tag f26-modularity --arches="aarch64 armv7hl i686 ppc64
ppc64le x86_64"
[dennis@anubis ~]$ koji taginfo f26-modularity
Tag: f26-modularity [411]
Arches: aarch64 armv7hl i686 ppc64 ppc64le x86_64
Groups: 
Tag options:
Inheritance:
  0    .... module-package-list [412]
[dennis@anubis ~]$ koji add-target module-bootstrap-f26 f26-modularity f26-modularity
[dennis@anubis ~]$
```
``

To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/6696

[Petr Šabata]

psabata added a new comment to an issue you are following:
``
@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.
``

To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/6696

[Petr Šabata]

psabata added a new comment to an issue you are following:
``
Tag changes requested in https://pagure.io/releng/issue/6868
``

To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/6696