DNF and Modularity

[Miroslav Suchý]

Hi,
I have to admit that I am a bit puzzled about DNF behavior with modularity.

I have installed repo files with modularity repos, but all of them are disabled. I have no
module enabled on my system
(F29 BTW). To be precise:
  output of `dnf module list`
  https://paste.fedoraproject.org/paste/3QvX2xv4OgVVmgckTnEQcQ

And every time I run `dnf upgrade` I get this output:

Problem 1: cannot install the best update candidate for package
bubblewrap-0.3.0-2.fc29.x86_64
  - package bubblewrap-0.3.0-2.module_2123+73a9ef6f.x86_64 is disabled
 Problem 2: cannot install the best update candidate for package
docker-distribution-2.6.2-7.git48294d9.fc28.x86_64
  - package docker-distribution-2.6.2-7.git48294d9.module_1641+02d06da9.x86_64 is
disabled
 Problem 3: cannot install the best update candidate for package eog-3.28.3-1.fc29.x86_64
  - package eog-3.28.3-1.module_2123+73a9ef6f.x86_64 is disabled
 Problem 4: cannot install the best update candidate for package
exempi-2.4.5-3.fc29.x86_64
  - package exempi-2.4.5-3.module_2123+73a9ef6f.x86_64 is disabled
 Problem 5: cannot install the best update candidate for package
flatpak-runtime-config-27-7.fc29.x86_64
  - package flatpak-runtime-config-27-7.module_2021+15e5e3e7.x86_64 is disabled
 Problem 6: cannot install the best update candidate for package
gimp-2:2.10.6-2.fc29.x86_64
  - package gimp-2:2.10.6-2.module_2129+8576126a.x86_64 is disabled
 Problem 7: cannot install the best update candidate for package
gimp-libs-2:2.10.6-2.fc29.x86_64
  - package gimp-libs-2:2.10.6-2.module_2129+8576126a.x86_64 is disabled
 Problem 8: cannot install the best update candidate for package
kubernetes-client-1.10.3-1.fc29.x86_64
  - package kubernetes-client-1.10.3-1.module_2132+faf1362b.x86_64 is disabled
 Problem 9: cannot install the best update candidate for package
libnghttp2-1.33.0-1.fc29.x86_64
  - package libnghttp2-1.33.0-1.module_2177+2526c218.x86_64 is disabled
 Problem 10: cannot install the best update candidate for package
libpeas-1.22.0-9.fc29.x86_64
  - package libpeas-1.22.0-9.module_2123+73a9ef6f.x86_64 is disabled
 Problem 11: cannot install the best update candidate for package
libpeas-gtk-1.22.0-9.fc29.x86_64
  - package libpeas-gtk-1.22.0-9.module_2123+73a9ef6f.x86_64 is disabled
 Problem 12: cannot install the best update candidate for package
libpeas-loader-python3-1.22.0-9.fc29.x86_64
  - package libpeas-loader-python3-1.22.0-9.module_2123+73a9ef6f.x86_64 is disabled
 Problem 13: cannot install the best update candidate for package
libuv-1:1.22.0-2.fc29.x86_64
  - package libuv-1:1.23.0-1.module_2177+2526c218.x86_64 is disabled
 Problem 14: cannot install the best update candidate for package
nghttp2-1.33.0-1.fc29.x86_64
  - package nghttp2-1.33.0-1.module_2177+2526c218.x86_64 is disabled
 Problem 15: cannot install the best update candidate for package
nodejs-1:10.11.0-1.fc29.x86_64
  - package nodejs-1:10.11.0-1.module_2200+adbac02b.x86_64 is disabled
 Problem 16: cannot install the best update candidate for package
npm-1:6.4.1-1.10.11.0.1.fc29.x86_64
  - package npm-1:6.4.1-1.10.11.0.1.module_2200+adbac02b.x86_64 is disabled
 Problem 17: cannot install the best update candidate for package
perl-DB_File-1.842-1.fc29.x86_64
  - package perl-DB_File-1.842-1.module_2073+eebc5b71.x86_64 is disabled
 Problem 18: cannot install the best update candidate for package
perl-HTTP-Tiny-0.076-1.fc29.noarch
  - package perl-HTTP-Tiny-0.076-1.module_2073+eebc5b71.noarch is disabled
 Problem 19: cannot install the best update candidate for package
perl-Thread-Queue-3.13-1.fc29.noarch
  - package perl-Thread-Queue-3.13-1.module_2073+eebc5b71.noarch is disabled

It does not matter if I pass `--best` option or not.
Why I - as a user - see this warnings/errors?

Is this an error or a feature?

Miroslav

[Petr Šabata]

On Mon, Sep 24, 2018 at 10:02:39AM +0200, Miroslav Suchý wrote:
>  Hi,
>  I have to admit that I am a bit puzzled about DNF behavior with modularity.
>  
>  I have installed repo files with modularity repos, but all of them are disabled. I have
> no module enabled on my system
>  (F29 BTW). To be precise:
>    output of `dnf module list`
>    https://paste.fedoraproject.org/paste/3QvX2xv4OgVVmgckTnEQcQ
>  
>  And every time I run `dnf upgrade` I get this output:
>  
>  Problem 1: cannot install the best update candidate for package
> bubblewrap-0.3.0-2.fc29.x86_64
>    - package bubblewrap-0.3.0-2.module_2123+73a9ef6f.x86_64 is disabled
>   Problem 2: cannot install the best update candidate for package
> docker-distribution-2.6.2-7.git48294d9.fc28.x86_64
>    - package docker-distribution-2.6.2-7.git48294d9.module_1641+02d06da9.x86_64 is
> disabled
>   Problem 3: cannot install the best update candidate for package
> eog-3.28.3-1.fc29.x86_64
>    - package eog-3.28.3-1.module_2123+73a9ef6f.x86_64 is disabled
>   Problem 4: cannot install the best update candidate for package
> exempi-2.4.5-3.fc29.x86_64
>    - package exempi-2.4.5-3.module_2123+73a9ef6f.x86_64 is disabled
>   Problem 5: cannot install the best update candidate for package
> flatpak-runtime-config-27-7.fc29.x86_64
>    - package flatpak-runtime-config-27-7.module_2021+15e5e3e7.x86_64 is disabled
>   Problem 6: cannot install the best update candidate for package
> gimp-2:2.10.6-2.fc29.x86_64
>    - package gimp-2:2.10.6-2.module_2129+8576126a.x86_64 is disabled
>   Problem 7: cannot install the best update candidate for package
> gimp-libs-2:2.10.6-2.fc29.x86_64
>    - package gimp-libs-2:2.10.6-2.module_2129+8576126a.x86_64 is disabled
>   Problem 8: cannot install the best update candidate for package
> kubernetes-client-1.10.3-1.fc29.x86_64
>    - package kubernetes-client-1.10.3-1.module_2132+faf1362b.x86_64 is disabled
>   Problem 9: cannot install the best update candidate for package
> libnghttp2-1.33.0-1.fc29.x86_64
>    - package libnghttp2-1.33.0-1.module_2177+2526c218.x86_64 is disabled
>   Problem 10: cannot install the best update candidate for package
> libpeas-1.22.0-9.fc29.x86_64
>    - package libpeas-1.22.0-9.module_2123+73a9ef6f.x86_64 is disabled
>   Problem 11: cannot install the best update candidate for package
> libpeas-gtk-1.22.0-9.fc29.x86_64
>    - package libpeas-gtk-1.22.0-9.module_2123+73a9ef6f.x86_64 is disabled
>   Problem 12: cannot install the best update candidate for package
> libpeas-loader-python3-1.22.0-9.fc29.x86_64
>    - package libpeas-loader-python3-1.22.0-9.module_2123+73a9ef6f.x86_64 is disabled
>   Problem 13: cannot install the best update candidate for package
> libuv-1:1.22.0-2.fc29.x86_64
>    - package libuv-1:1.23.0-1.module_2177+2526c218.x86_64 is disabled
>   Problem 14: cannot install the best update candidate for package
> nghttp2-1.33.0-1.fc29.x86_64
>    - package nghttp2-1.33.0-1.module_2177+2526c218.x86_64 is disabled
>   Problem 15: cannot install the best update candidate for package
> nodejs-1:10.11.0-1.fc29.x86_64
>    - package nodejs-1:10.11.0-1.module_2200+adbac02b.x86_64 is disabled
>   Problem 16: cannot install the best update candidate for package
> npm-1:6.4.1-1.10.11.0.1.fc29.x86_64
>    - package npm-1:6.4.1-1.10.11.0.1.module_2200+adbac02b.x86_64 is disabled
>   Problem 17: cannot install the best update candidate for package
> perl-DB_File-1.842-1.fc29.x86_64
>    - package perl-DB_File-1.842-1.module_2073+eebc5b71.x86_64 is disabled
>   Problem 18: cannot install the best update candidate for package
> perl-HTTP-Tiny-0.076-1.fc29.noarch
>    - package perl-HTTP-Tiny-0.076-1.module_2073+eebc5b71.noarch is disabled
>   Problem 19: cannot install the best update candidate for package
> perl-Thread-Queue-3.13-1.fc29.noarch
>    - package perl-Thread-Queue-3.13-1.module_2073+eebc5b71.noarch is disabled
>  
>  It does not matter if I pass `--best` option or not.
>  Why I - as a user - see this warnings/errors?
>  
>  Is this an error or a feature? 
Definitely an error.

Could be another case of
https://bugzilla.redhat.com/show_bug.cgi?id=1629396, but it
should have been fixed last week.  Is your repo current?
Could you check for the presence of modular repodata (the
*modules.yaml.gz) file.

P

>  
>  Miroslav
>  _______________________________________________
>  devel mailing list -- devel(a)lists.fedoraproject.org
>  To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
>  List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives:
> https://lists.fedoraproject.org/archives/list/[e-mail]

[M A Young]

On Mon, 24 Sep 2018, Petr Šabata wrote:

>  On Mon, Sep 24, 2018 at 10:02:39AM +0200, Miroslav Suchý wrote:
>  > Hi,
>  > I have to admit that I am a bit puzzled about DNF behavior with modularity.
>  > 
>  > I have installed repo files with modularity repos, but all of them are disabled. I
> have no module enabled on my system
>  > (F29 BTW). To be precise:
>  >   output of `dnf module list`
>  >   https://paste.fedoraproject.org/paste/3QvX2xv4OgVVmgckTnEQcQ
>  > 
>  > And every time I run `dnf upgrade` I get this output:
>  > 
>  > Problem 1: cannot install the best update candidate for package
> bubblewrap-0.3.0-2.fc29.x86_64
>  >   - package bubblewrap-0.3.0-2.module_2123+73a9ef6f.x86_64 is disabled
>  >  Problem 2: cannot install the best update candidate for package
> docker-distribution-2.6.2-7.git48294d9.fc28.x86_64
>  >   - package docker-distribution-2.6.2-7.git48294d9.module_1641+02d06da9.x86_64 is
> disabled
>  >  Problem 3: cannot install the best update candidate for package
> eog-3.28.3-1.fc29.x86_64
>  >   - package eog-3.28.3-1.module_2123+73a9ef6f.x86_64 is disabled
>  >  Problem 4: cannot install the best update candidate for package
> exempi-2.4.5-3.fc29.x86_64
>  >   - package exempi-2.4.5-3.module_2123+73a9ef6f.x86_64 is disabled
>  >  Problem 5: cannot install the best update candidate for package
> flatpak-runtime-config-27-7.fc29.x86_64
>  >   - package flatpak-runtime-config-27-7.module_2021+15e5e3e7.x86_64 is disabled
>  >  Problem 6: cannot install the best update candidate for package
> gimp-2:2.10.6-2.fc29.x86_64
>  >   - package gimp-2:2.10.6-2.module_2129+8576126a.x86_64 is disabled
>  >  Problem 7: cannot install the best update candidate for package
> gimp-libs-2:2.10.6-2.fc29.x86_64
>  >   - package gimp-libs-2:2.10.6-2.module_2129+8576126a.x86_64 is disabled
>  >  Problem 8: cannot install the best update candidate for package
> kubernetes-client-1.10.3-1.fc29.x86_64
>  >   - package kubernetes-client-1.10.3-1.module_2132+faf1362b.x86_64 is disabled
>  >  Problem 9: cannot install the best update candidate for package
> libnghttp2-1.33.0-1.fc29.x86_64
>  >   - package libnghttp2-1.33.0-1.module_2177+2526c218.x86_64 is disabled
>  >  Problem 10: cannot install the best update candidate for package
> libpeas-1.22.0-9.fc29.x86_64
>  >   - package libpeas-1.22.0-9.module_2123+73a9ef6f.x86_64 is disabled
>  >  Problem 11: cannot install the best update candidate for package
> libpeas-gtk-1.22.0-9.fc29.x86_64
>  >   - package libpeas-gtk-1.22.0-9.module_2123+73a9ef6f.x86_64 is disabled
>  >  Problem 12: cannot install the best update candidate for package
> libpeas-loader-python3-1.22.0-9.fc29.x86_64
>  >   - package libpeas-loader-python3-1.22.0-9.module_2123+73a9ef6f.x86_64 is disabled
>  >  Problem 13: cannot install the best update candidate for package
> libuv-1:1.22.0-2.fc29.x86_64
>  >   - package libuv-1:1.23.0-1.module_2177+2526c218.x86_64 is disabled
>  >  Problem 14: cannot install the best update candidate for package
> nghttp2-1.33.0-1.fc29.x86_64
>  >   - package nghttp2-1.33.0-1.module_2177+2526c218.x86_64 is disabled
>  >  Problem 15: cannot install the best update candidate for package
> nodejs-1:10.11.0-1.fc29.x86_64
>  >   - package nodejs-1:10.11.0-1.module_2200+adbac02b.x86_64 is disabled
>  >  Problem 16: cannot install the best update candidate for package
> npm-1:6.4.1-1.10.11.0.1.fc29.x86_64
>  >   - package npm-1:6.4.1-1.10.11.0.1.module_2200+adbac02b.x86_64 is disabled
>  >  Problem 17: cannot install the best update candidate for package
> perl-DB_File-1.842-1.fc29.x86_64
>  >   - package perl-DB_File-1.842-1.module_2073+eebc5b71.x86_64 is disabled
>  >  Problem 18: cannot install the best update candidate for package
> perl-HTTP-Tiny-0.076-1.fc29.noarch
>  >   - package perl-HTTP-Tiny-0.076-1.module_2073+eebc5b71.noarch is disabled
>  >  Problem 19: cannot install the best update candidate for package
> perl-Thread-Queue-3.13-1.fc29.noarch
>  >   - package perl-Thread-Queue-3.13-1.module_2073+eebc5b71.noarch is disabled
>  > 
>  > It does not matter if I pass `--best` option or not.
>  > Why I - as a user - see this warnings/errors?
>  > 
>  > Is this an error or a feature?
>  
>  Definitely an error.
>  
>  Could be another case of
>  https://bugzilla.redhat.com/show_bug.cgi?id=1629396, but it
>  should have been fixed last week.  Is your repo current?
>  Could you check for the presence of modular repodata (the
>  *modules.yaml.gz) file. 
the dnf upgrade problem looks to me like
https://bugzilla.redhat.com/show_bug.cgi?id=1616118

	Michael Young

[Kevin Fenzi]

On 09/24/2018 03:24 AM, M A Young wrote:
>  On Mon, 24 Sep 2018, Petr Šabata wrote:
>  
> >
> > Definitely an error.
> >
> > Could be another case of
> > https://bugzilla.redhat.com/show_bug.cgi?id=1629396, but it
> > should have been fixed last week.  Is your repo current?
> > Could you check for the presence of modular repodata (the
> > *modules.yaml.gz) file.
>  
>  the dnf upgrade problem looks to me like
>  https://bugzilla.redhat.com/show_bug.cgi?id=1616118 

It's actually fallout from https://pagure.io/releng/issue/7827

Basically we are building flatpaks from modules, but then the modules
are getting into the normal module stream. They shouldn't and we need to
setup some different tagging for them to avoid it.

kevin

[Adam Williamson]

On Mon, 2018-09-24 at 08:17 -0700, Kevin Fenzi wrote:
>  On 09/24/2018 03:24 AM, M A Young wrote:
>  > On Mon, 24 Sep 2018, Petr Šabata wrote:
>  > 
>  > > Definitely an error.
>  > > 
>  > > Could be another case of
>  > > https://bugzilla.redhat.com/show_bug.cgi?id=1629396, but it
>  > > should have been fixed last week.  Is your repo current?
>  > > Could you check for the presence of modular repodata (the
>  > > *modules.yaml.gz) file.
>  > 
>  > the dnf upgrade problem looks to me like
>  > https://bugzilla.redhat.com/show_bug.cgi?id=1616118
>  
>  It's actually fallout from https://pagure.io/releng/issue/7827
>  
>  Basically we are building flatpaks from modules, but then the modules
>  are getting into the normal module stream. They shouldn't and we need to
>  setup some different tagging for them to avoid it. 
Well, that's part of it, but dnf actually printing these messages is
kind of a bug regardless. Even without that problem, there are always
likely to be some "real" modules that have packages in them which are
ahead of the non-modular package, and thus this bug will be prone to
happen so long as dnf doesn't just treat this as a normal situation and
print no warning message.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net

[Miroslav Suchý]

Dne 24.9.2018 v 17:17 Kevin Fenzi napsal(a):
>  On 09/24/2018 03:24 AM, M A Young wrote:
> > On Mon, 24 Sep 2018, Petr Šabata wrote:
> >
> >>
> >> Definitely an error.
> >>
> >> Could be another case of
> >> https://bugzilla.redhat.com/show_bug.cgi?id=1629396, but it
> >> should have been fixed last week.  Is your repo current?
> >> Could you check for the presence of modular repodata (the
> >> *modules.yaml.gz) file.
> >
> > the dnf upgrade problem looks to me like
> > https://bugzilla.redhat.com/show_bug.cgi?id=1616118
>  
>  
>  It's actually fallout from https://pagure.io/releng/issue/7827
>  
>  Basically we are building flatpaks from modules, but then the modules
>  are getting into the normal module stream. They shouldn't and we need to
>  setup some different tagging for them to avoid it. 
I do not believe this is the case. I do not have installed bubblewrap from module. I have
bubblewrap from F29. The
problem is that

bubblewrap-0.3.0-2.module_2123+73a9ef6f.x86_64 > bubblewrap-0.3.0-2.fc29.x86_64

And DNF put the module version into sack, despite the fact that I have all modules
disabled.

I thin that BZ 1616118 correctly describe it.

Miroslav