Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1689460 - dnf system-upgrade download --refresh --releasever=30 --setopt=module_platform_id=platform:f30 --skip-broken --allowerasing upgraded gimp and libgit2 rpms to modules
Summary: dnf system-upgrade download --refresh --releasever=30 --setopt=module_platfor...
Keywords:
Status: NEW
Alias: None
Product: Fedora Modules
Classification: Fedora
Component: gimp
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Nils Philippsen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-15 23:50 UTC by Matt Fagnani
Modified: 2019-09-19 12:30 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Matt Fagnani 2019-03-15 23:50:54 UTC
Description of problem:

I tested upgrading from F29 to F30 with
sudo dnf system-upgrade download --refresh --releasever=30 --skip-broken --allowerasing

I got the following modular dependency errors.

Modular dependency problems:

 Problem 1: conflicting requests
  - nothing provides module(platform:f30) needed by module stratis:1:20181215204600:a5b0195c-0.i686
 Problem 2: conflicting requests
  - nothing provides module(platform:f30) needed by module standard-test-roles:3.0:3020190304181436:a5b0195c-0.i686
 Problem 3: conflicting requests
  - nothing provides module(platform:f30) needed by module ripgrep:latest:3020190305101905:a5b0195c-0.i686
 Problem 4: conflicting requests
  - nothing provides module(platform:f30) needed by module ninja:latest:3020190304180949:a5b0195c-0.i686
 Problem 5: conflicting requests
  - nothing provides module(platform:f30) needed by module meson:latest:3020190304180854:36245242-0.i686
 Problem 6: conflicting requests
  - nothing provides module(platform:f30) needed by module libgit2:0.27:3020190304180745:a5b0195c-0.i686
 Problem 7: conflicting requests
  - nothing provides module(platform:f30) needed by module gimp:2.10:3020190304180601:a5b0195c-0.i686
 Problem 8: conflicting requests
  - nothing provides module(platform:f30) needed by module fish:3:3020190301191132:602da195-0.i686
 Problem 9: conflicting requests
  - nothing provides module(platform:f30) needed by module exa:latest:3020190305101925:e50d0d19-0.i686
 Problem 10: conflicting requests
  - nothing provides module(platform:f30) needed by module dwm:6.1:3020190304180429:a5b0195c-0.i686
 Problem 11: conflicting requests
  - nothing provides module(platform:f30) needed by module bat:latest:3020190305101836:e50d0d19-0.i686
 Problem 12: conflicting requests
  - nothing provides module(platform:f30) needed by module avocado:stable:3020190304180315:a5b0195c-0.i686

Using the workaround mentioned in bug 1656509, I ran
dnf system-upgrade download --refresh --releasever=30 --setopt=module_platform_id=platform:f30 --skip-broken --allowerasing

The gimp, gimp-libs, and libgit2 rpms I have installed were going to be upgraded to modules from the F30 fedora-modular repo according to the following output:

Upgrading:
 gimp                        i686   2:2.10.8-5.module_f30+2942+858f82d0
                                                             fedora-modular   24 M
 gimp-libs                   i686   2:2.10.8-5.module_f30+2942+858f82d0
                                                             fedora-modular  2.5 M
 libgit2                     i686   0.27.8-1.module_f30+2959+693db98d
                                                             fedora-modular  469 k
...

A part showing the enabling of the gimp and libgit2 module streams was near the end of the dnf output.

Enabling module streams:
 gimp                               2.10                                          
 libgit2                            0.27                                          


Version-Release number of selected component (if applicable):
dnf-0:4.2.1-1.fc29.noarch
libdnf-0:0.28.0-1.fc29.i686
python3-dnf-plugin-system-upgrade-0:4.0.4-1.fc29.noarch
gimp-2:2.10.8-5.fc29.i686
gimp-libs-2:2.10.8-5.fc29.i686
libgit2-0:0.27.8-1.fc29.i686

How reproducible:
3 of 3 times

Steps to Reproduce:
In F29 with updates-testing enabled and gimp, gimp-libs, libgit2 rpms installed:
1. sudo dnf upgrade --refresh
2. sudo dnf system-upgrade download --refresh --releasever=30 --skip-broken --allowerasing
3. sudo dnf system-upgrade download --refresh --releasever=30 --setopt=module_platform_id=platform:f30 --skip-broken --allowerasing

Actual results:
When using the --setopt=module_platform_id=platform:f30 option with dnf system-upgrade, the gimp and libgit2 rpms were going to be converted to modules.

Expected results:
The gimp and libgit2 rpms would be upgraded to rpms as below.

Additional info:

When I ran sudo dnf system-upgrade download --refresh --releasever=30 --skip-broken --allowerasing, the gimp and libgit2 rpms were going to be upgraded as rpms as expected.

Upgrading:
...
gimp                        i686   2:2.10.8-7.fc30          fedora           24 M
...
 gimp-libs                   i686   2:2.10.8-7.fc30          fedora          2.5 M
...
libgit2                     i686   0.27.8-2.fc30            fedora          471 k

Comment 1 Jaroslav Mracek 2019-03-25 13:25:10 UTC
The issue is that gimp was moved into module and operation would result in:
Enabling module streams:
 gimp                              2.10


The workaround would be to disable module gimp (sudo dnf module disable gimp --releasever=30 --setopt=module_platform_id=platform:f30) before system upgrade or even after system-upgrade (sudo dnf module disable gimp) and then run "sudo dnf distro-sync" command.

Please could you explain whats wrong with gimp from the module or why you would prefer to consume non modular version?

Comment 2 Matt Fagnani 2019-03-26 00:37:03 UTC
Jaroslav, I haven't installed any Fedora modules, but I don't think something's wrong with the gimp or libgit2 modules themselves. I don't have a preference of using the gimp or libgit2 rpms or modules. I didn't expect that using the --setopt=module_platform_id=platform:f30 workaround would enable the gimp and libgit2 module streams based on what I read in bug 1656509. Since the gimp-2.10.8-7.fc30 and libgit2-0.27.8-2.fc30 rpms were in the F30 fedora repo and were used when I ran sudo dnf system-upgrade download --refresh --releasever=30 --skip-broken --allowerasing, and I didn't specify that the the gimp or libgit2 modules should be enabled using something like sudo dnf module enable gimp libgit2, I expected that the gimp and libgit2 rpms should be upgraded to those regular rpms. I found that using sudo dnf system-upgrade download --refresh --releasever=30 --disablerepo=*modul* --skip-broken --allowerasing also worked around the modular dependency problems since I don't have Fedora modules installed. Thanks for the workaround and looking into this issue.

Comment 3 Adam Samalik 2019-03-26 12:35:15 UTC
I'd say this works as expected because gimp:2.10 is a default stream in Fedora 30. The same would happen if you installed gimp using "dnf install gimp" on Fedora 30.

There shouldn't be a difference between consuming a traditional package or a package coming from a default module stream. We expect some content to move to the modular repository for various reasons, and defaults help you to install that content the same way you'd do before. So such moves shouldn't impact the user in any notable way.

Comment 4 Jaroslav Mracek 2019-04-04 12:17:09 UTC
I believe that the problem could be easily solved by removal of default stream from gimp module and to keep gimp in standard fedora repository. This also solves the issue with end of life of module stream. The current design of modularity in Fedora is not ready for this event. After removal of module stream from Fedora we can expect the real problem.

Comment 5 Miro Hrončok 2019-09-19 12:30:16 UTC
I've opened bz1753614 as a followup.


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