#8879 Create pungi config for Rawhide/F32 ursa prime buildroot
Opened a month ago by sgallagh. Modified a month ago

  • Describe the issue
    Produce a buildroot compose of all modules with a default stream (or overrides) as determined by https://pagure.io/pungi/pull-request/1266 (which uses libmodulemd 2.8.0 helper functions to get these values)

  • When do you need this? (YYYY/MM/DD)
    2019-10-11

  • When is this no longer needed or useful? (YYYY/MM/DD)
    Fedora 32 EOL

  • If we cannot complete your request, what is the impact?
    Users cannot use the contents of default module streams in the buildroot for non-modular packages in Fedora 32

CC @mohanboddu @kevin @psabata


Enabling Ursa Major was only approved for EPEL8, see https://pagure.io/fesco/issue/2003#comment-603546. Don't enable this for Fedora without FESCo approval.

By the time I got to work on this, its kinda late Fri, so I wanna put my questions here:

  • Based on my understanding of the commit we need to add overrides dir which points to this location. Whats going to reside in there and how it will get populated?

  • We will use this pungi config to generate the buildroot compose, but it should be regenerated whenever there is a new module build of default stream or change in override, iiuc. How are we going to achieve this?

  • Are these overrides are created by users by making a PR to https://pagure.io/releng/fedora-module-defaults/blob/master/f/overrides or releng has to pick and choose?

These are the questions that I can think of now, may be there are more that we need to talk about.

By the time I got to work on this, its kinda late Fri, so I wanna put my questions here:

Based on my understanding of the commit we need to add overrides dir which points to this location. Whats going to reside in there and how it will get populated?

The purpose of that is for us to be able to add other streams into the buildroot (possibly overriding the runtime default) if we need to. @psabata might have some specific ones in mind already.

We will use this pungi config to generate the buildroot compose, but it should be regenerated whenever there is a new module build of default stream or change in override, iiuc. How are we going to achieve this?

I think the plan for now was to do it as a cron job and improve it later.

Are these overrides are created by users by making a PR to https://pagure.io/releng/fedora-module-defaults/blob/master/f/overrides or releng has to pick and choose?

The overrides dir should be releng's responsibility. It should generally not come from users.

These are the questions that I can think of now, may be there are more that we need to talk about.

Login to comment on this ticket.

Metadata