On 09. 07. 20 20:19, Adam Williamson wrote:
On Thu, 2020-07-09 at 11:09 -0700, Adam Williamson wrote:
> On Thu, 2020-07-09 at 16:45 +0200, Igor Raits wrote:
>> On Thu, 2020-07-09 at 07:36 -0700, John M. Harris Jr wrote:
>>> On Thursday, July 9, 2020 5:24:59 AM MST Petr Pisar wrote:
>>>> DNF should perform "dnf mark install
fedora-repos-rawhide-modular"
>>>> action on
>>>> a system upgrade, because we want that package to be prensented on
>>>> the
>>>> system. However I worry that DNF does not possess a capability for
>>>> doing
>>>> it. (Except of injecting that command into some externally executed
>>>> script.)
>>>
>>> Unless I'm mistaken, it should only be present if the user manually
>>> installed
>>> it, and opted into modularity, right?
>>
>> No, it should be installed by default.
>
> Are you talking about upgrades here, or fresh installs?
>
> It is not being installed on fresh installs presently, and as I read
> the ticket, that was intended, per your comment:
>
https://pagure.io/fesco/issue/2114#comment-653352
> "Probably best way would be going back to "Boltron" (IIRC how that
> thing was called) and have modular repos in their own fedora-repos
> subpackage which are enabled by default, but the package **is not
> installed by default.**" (emphasis added)
Oh, looking at it again, now I see this:
https://pagure.io/fesco/issue/2406#comment-658315
which seems to suggest that FESCo expects fedora-repos-modular to be
installed out of the box. Well, in yesterday's and today's Rawhide
(default Server DVD install) it wasn't, openQA caught this. On my first
reading of #2114 I figured this was intentional and adjusted openQA to
install fedora-repos-modular , but it sounds like it's actually a bug
and comps and/or kickstarts and/or package dependencies will need to be
changed.
to be mergeable
before proceeding further.
Suddenly it was merged as part of
to avoid this situation.
Unfortunately, I wasn't sure if this is the best approach and it wasn't merged
right away. I was not expecting the fedora-repos change to be merged before we
figure this out :(
FTR the details are handled via