Re: Is dnf update --releasever=30 supposed to work with modules?

[Petr Šabata]

On Mon, Mar 04, 2019 at 08:56:26AM +0100, Miroslav Suchý wrote:
>  Dne 04. 03. 19 v 7:30 Richard W.M. Jones napsal(a):
>  > Bonus question: Are "Problem 1" (etc) in each section of the error
>  > message supposed to relate to each other in some way?  Or is the
>  > second list a new list of problems?
>  
>  
>  You mean this error:
>    - nothing provides module(platform:f30) needed by module
> stratis:1:20181215204600:a5b0195c-0.x86_64
>    - nothing provides module(platform:f30) needed by module
> standard-test-roles:3.0:3020190214144451:a5b0195c-0.x86_64
>    ...
>  
>  The dependency
>    module(platform:f30)
>  is virtual. There is no package which provides this. The dependency is put into an RPM
> transaction sack by DNF based on
>  PLATFORM_ID from *current* /etc/os-release 
Indeed.  I'm not sure whether we can reasonably support this
upgrade method, although suggestions welcome :|

The failure in this case isn't caused by modules, however; the
messages are informational.

P