Bug 1810173 - dependency problem updating to F32
Summary: dependency problem updating to F32
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: gimp
Version: rawhide
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: 2020-03-04 16:31 UTC by Alec Leamas
Modified: 2021-05-31 16:16 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-03-05 07:28:56 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Alec Leamas 2020-03-04 16:31:16 UTC
Description of problem:


Version-Release number of selected component (if applicable):


How reproducible: always


Steps to Reproduce:

sudo dnf --releasever=32 --setopt=module_platform_id=platform:f32 \
    --enablerepo=updates-testing --enablerepo=updates-testing-modular \
    distro-sync

Actual results:

gimp-2:2.10.14-1.module_f31+6993+669d73be.x86_64
  - package gimp-2:2.10.14-1.module_f32+6980+20383b7e.x86_64 requires libmypaint-1.3.so.0()(64bit), but none of the providers can be installed
  - libmypaint-1.4.0-1.fc31.x86_64 does not belong to a distupgrade repository
  - gimp-2:2.10.14-1.module_f31+6993+669d73be.x86_64 does not belong to a distupgrade repository

Expected results:

No errors w r t gimp


Additional info:

Done inresponse to , Miroslav Suchý's request of fedora-devel

Comment 1 Josef Ridky 2020-03-05 07:28:56 UTC
Gimp module has been removed from Fedora 32+ due of unsolved modularity issues.

For proper upgrade to f32, please, remove modular gimp, disable modular installation of gimp and install rpm package available on F32 [1].

[1]
# dnf module remove gimp
# dnf module disable gimp
# dnf install gimp

Closing as CANTFIX.

Comment 2 Zbigniew Jędrzejewski-Szmek 2020-03-06 13:05:08 UTC
Do any of the patches for #1804564 or #1767351 help here? Can we provide a solution that does not require manual commandline steps?

Comment 3 Jaroslav Mracek 2021-05-31 16:16:58 UTC
I guess that the issue is resolve by module autoreset during dnf system-upgrade.


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