When I do: $ sudo dnf install gimp dnf tries to install: gimp 2:2.10.12-3.module_f30+6174+bc22f659 and enables gimp:2.10 module/stream. The gimp-2.10.12-3.fc30 "regular" package is non installable in a trivial way via dnf. Why do we ship 2 different GIMPs? When I install gimp from the module, I'm afraid I will never be able to update it past 2.10, due to the "switching streams is not possible" design/bug of modularity reported at https://pagure.io/modularity/issue/151
More than a month have passed and there was no reply here. What's the idea behind this situation? Is it desired? Why? Or is unfinished work somehow?
Hi, I am not quite sure, why we have modular and non-modular gimp still available. My understanding is that modular gimp should become the single one supported and non-modular should be obsoleted/removed. The reason for coexistence of both versions was the modular version hadn't been available on some older fedora releases (< F29) and the intention was to move gimp to modular one. But now, I have strange feelings about modular way of packaging due some still unresolved issues/questions e.g. 1) How should we deal with streams when upstream release e.g. gimp-2.14, that should become default stream and all users should be able to upgrade to it? 2) What about python2 dependencies for GIMP in F31+?
1) exactly 2) they have FESCo exception, not sure what about them
BTW there was this https://fedoraproject.org/wiki/Changes/GIMP_as_a_Module but it was not submitted. Hence I don't understand why GIMP should become modular only.
1) How should we deal with streams when upstream release e.g. gimp-2.14, that should become default stream and all users should be able to upgrade to it? AFAIK, if you think most users always want to update to the latest Gimp, the default stream should be something like "latest", not a specific version. You can then package all the other versions you're maintaining as separate streams. (Presumably there are advantages of a "latest" stream versus non-modular packages, but for that you'll need someone more familiar with Modularity.) 2) What about python2 dependencies for GIMP in F31+? I expect that if modular Gimp becomes the only user of those Python 2 package, that package should eventually be moved to the Gimp module.
Anybody know how to do the equivalent of "dnf module disable gimp" in ansible?
For Fedora 32 devel, GIMP isn't even installable. I get the following error: Error: Problem: conflicting requests - nothing provides libmypaint-1.3.so.0()(64bit) needed by gimp-2:2.10.14-1.module_f32+6980+20383b7e.x86_64 GIMP is installable from flathub.org with flatpak. It is version 2.10.18. Who is not liking the themes provided in the newer versions of GIMP? The system theme isn't even viewable as the color contrast of unselected items makes them blend together. Also there seems to be way less tools showing by default and I'm not sure why. The most tools that show are 18 or 19... and it used to be ~36. Not sure what is going on. Maybe I have ancient GIMP settings that are messing up the newer releases?!?
Ok, I figured out the issues with the display and the icons listed. Went into Edit > Preference > Interface > Icon Theme and selected Legacy rather than the default of Symbolic... that made the icons colorful and actually viewable with the System theme selected. Under Edit > Preference > Interface > Toolbox I unselected "Use tool groups" and that made all of the tools show up again. I guess at some point upstream changed these defaults? Or did the Fedora packager? In any event, I think the way I've reconfigured it much more usable... and is what the regular user who doesn't want to have to go into the settings and figure it out themselves. I suspect it was upstream who made the changes... as on my wife's Microsoft Windows computer, she has the same interface deficiencies. I'm guessing if I went through the various release notes that I'd see when these changes were made, eh?
Gimp module for F32+ has been removed. Please, remove your modular version of gimp, disable gimp module and install RPM version available in F32.