From Fedora Project Wiki

GIMP as a Module


This change sets a default module stream for the gimp module and removes the traditional non-modular package.


Current status

  • Targeted release: Fedora 30
  • Last updated: 2018-10-17
  • Tracker bug: <will be assigned by the Wrangler>

Detailed Description

Currently, GIMP is available as a traditional non-modular (’ursine’) package as well as in a module. From Fedora 29 on, either options are built from the exact same sources. Having to choose between them can confuse users and maintaining both is an unnecessary development burden.

Benefit to Fedora

Most of the time, when only one GIMP major version is available, this change reduces the risk to confuse users of GIMP about which options to install because there is only one. In times when new upstream major versions are published it allows introducing them into a stable Fedora release without breaking user experience. Not having to maintain the traditional package side-by-side with the modular one (both of which contain the exact same thing from a user's POV) reduces the maintainers' workload.


  • Proposal owners:
    • Get the default stream for the gimp module set as 2.10.
    • Retire the traditional package and its branch from dist-git.
  • Other developers: N/A (not a System Wide Change)

With Ursa Major and a default stream present, the produced content is available for building other traditional packages and shouldn’t affect third-party plugins etc. that build against GIMP.

  • Release engineering: #7873 (a check of an impact with Release Engineering is needed)
  • Policies and guidelines: N/A (not a System Wide Change)
  • Trademark approval: N/A (not needed for this Change)

Upgrade/compatibility impact

The upgrade experience of users coming from the traditional package depends on how packaging tools like DNF and PackageKit handle upgrades of traditional packages being replaced by modular content in the generic case (this is not specific to GIMP). If worst came to worst, users would have to manually enable the module on their systems.

N/A (not a System Wide Change)

How To Test

No special hardware is needed for testing. The system doesn't need to be prepared for testing this change except where otherwise noted. All activities using command line programs should be performed as the ’root’ user.

Installing the gimp package

Ensure that the gimp package isn't installed on your system.

Using package management software (dnf, GNOME Software), install GIMP and, as root, verify that the gimp module is enabled using stream 2.10 afterwards:

# dnf module list --enabled
gimp     2.10 [e]   devel, default [i]                    GIMP

N/A (not a System Wide Change)

User Experience

Users shouldn't notice significant changes, just that GIMP packages will be installed and updated from modular content.


There are various third party packages which extend GIMP. With Ursa Major present there shouldn't be noticeable changes for them.

N/A (not a System Wide Change)

Contingency Plan

  • Contingency mechanism: (What to do? Who will do it?) If needed, the proposal owners will either not remove or reinstate the traditional gimp package.
  • Contingency deadline: N/A (not a System Wide Change)
  • Blocks release? No
  • Blocks product? No


N/A (not a System Wide Change)

Release Notes