Bug 1629396 - pungi generated a module repository with metadata and RPM inconsistency
Summary: pungi generated a module repository with metadata and RPM inconsistency
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: pungi
Version: 31
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Lubomír Sedlář
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-09-15 17:09 UTC by Kevin Fenzi
Modified: 2020-05-10 17:08 UTC (History)
16 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-10 17:08:03 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Kevin Fenzi 2018-09-15 17:09:16 UTC
dnf-3.5.1-1.fc30.noarch

No modules enabled: 
~ sudo dnf module list --installed                           
Last metadata expiration check: 0:16:32 ago on Sat 15 Sep 2018 09:46:49 AM PDT.
Error: No matching Modules to list

~ sudo dnf update -x gnutls\* -x libreoffice-core -x liborcus                                                      
Last metadata expiration check: 0:08:31 ago on Sat 15 Sep 2018 09:46:49 AM PDT.                   Dependencies resolved.

 Problem 1: cannot install the best update candidate for package gimp-libs-2:2.10.6-2.fc30.x86_64                     
  - package gimp-libs-2:2.10.6-2.module_2129+0d46cbd3.x86_64 is disabled                                              
 Problem 2: cannot install the best update candidate for package gnutls-3.6.2-4.fc29.x86_64                           
  - package gnutls-3.6.3-4.fc30.x86_64 is disabled
 Problem 3: cannot install the best update candidate for package gnutls-dane-3.6.2-4.fc29.x86_64                      
  - package gnutls-dane-3.6.3-4.fc30.x86_64 is disabled
 Problem 4: cannot install the best update candidate for package gnutls-utils-3.6.2-4.fc29.x86_64                     
  - package gnutls-utils-3.6.3-4.fc30.x86_64 is disabled
 Problem 5: cannot install the best update candidate for package libnghttp2-1.33.0-1.fc30.x86_64                      
  - package libnghttp2-1.33.0-1.module_2177+076c917f.x86_64 is disabled                                               
 Problem 6: cannot install the best update candidate for package liborcus-0.13.4-3.fc29.x86_64                        
  - package liborcus-0.14.0-1.fc30.x86_64 is disabled
=======================================================================================================================
 Package              Arch               Version                                     Repository                   Size
=======================================================================================================================
Upgrading:
 stratisd             x86_64             0.9.0-1.module_2156+f9892fa0                rawhide-modular             1.9 M

Transaction Summary
=======================================================================================================================
Upgrade  1 Package

Total download size: 1.9 M
Is this ok [y/N]: n

I'm not sure whats different about stratisd, it could be some problem with the rawhide modular repodata, but I don't expect an update to install from a module I never enabled.

Comment 1 Stephen Gallagher 2018-09-17 19:57:16 UTC
This looks like a solver bug in DNF somewhere. There is a stratisd-0.9.1-1.fc30 package in the Everything repository that should have been preferred, given that the stratisd module was neither enabled nor has a default stream set in Rawhide.

Comment 2 Stephen Gallagher 2018-09-17 20:04:07 UTC
OK, I was wrong. It looks like there's actually a repo-creation bug here. The Modular repository was created for F30 including these RPMs, but the modulemd YAML that matches them is missing from the repository. Thus, DNF ends up solving it as if it was a regular RPM (and the .module section of the release field sorts higher than the .fc30 one).

This is probably a pungi bug related to creating the repo after we untagged this module from Rawhide the other day. Somehow it still pulled in the RPMs but not the metadata. Reassigning to pungi.

Comment 3 Lubomír Sedlář 2018-09-18 07:50:50 UTC
Yup, this is a bug. There are two stratis modules with different contexts:
stratis-master-20180901144646.7a127764 and stratis-master-20180901144646.337c62b4. Only one of them is listed in the metadata.

This bug is actually already fixed in pungi 4.1.28. Please upgrade and that should fix the problem.

Comment 4 Kevin Fenzi 2018-09-18 16:57:37 UTC
I updated rawhide-composer to 4.1.28 yesterday, so we can check todays rawhide.

Comment 5 Ben Cotton 2019-08-13 17:04:43 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to '31'.

Comment 6 Ben Cotton 2019-08-13 19:43:34 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to 31.

Comment 7 Kevin Fenzi 2020-05-10 17:08:03 UTC
This was actually fixed long ago. :)


Note You need to log in before you can comment on or make changes to this bug.