Description of problem:
On Fedora Rawhide, the postgresql module does not have the default stream and profile set. Therefore, DNF will not install the module using `dnf module install postgresql`. It will only enable it. Since modules should be able to install using the aforementioned command, I consider this a bug.
Steps to reproduce:
1. dnf module list postgresql
Modules should have the defaults set.
If you did not set the defaults on purpose, please share the reason and confirm that explicitely.
Hi, thanks for the report.
We do not have default streams set since we still have non-modularized rpm content available in regular repositories. Afaik there is still the issue with buildroot not being able to use default streams for modules, so until that is possible we will have to rely on regular repositories for the content.
Setting default profiles for the streams seems like a good idea though. Will look into it.
(In reply to Petr Kubat from comment #1)
> We do not have default streams set since we still have non-modularized rpm
> content available in regular repositories. Afaik there is still the issue
> with buildroot not being able to use default streams for modules, so until
> that is possible we will have to rely on regular repositories for the
Well, my original goal was to not bother users by modularity if they don't
want to be bothered (strict opt-in). That is -> they should have the good
old Fedora work-flow WRT PostgreSQL:
-> one default version of postgresql for particular Fedora version, and
-> hit postgresql-setup --upgrade after fedora distro upgrade
If they want to, they can easily move to modular postgresql (even if that
doesn't really mean different postgresql version).
I'm not saying you can not change this ... :-), just saying that even
if the modular build-requires worked fine - I wouldn't do that.
That seems like a plausible reason for the defaults not to be set.
From my perspective, I am not able to recognize if you do it on purpose, or if you just forgot to set it. Now, after clarification, I can whitelist the module and not bother you with that anymore, until you realize you want something else.
Is that ok?
The change has been merged, so I take this as fixed and I will verify in a compose.