How to upgrade Gimp to version 2.10

[Stevo]

What do you show for

Code: Select all

apt policy libgegl-0.4.0 libbabl-0.1-0

gimp 2.10.6 requires these versions:

Code: Select all

libgegl-0.4-0:
  Installed: 0.4.8-1~mx17+1
libbabl-0.1-0:
  Installed: 0.1.56-1~mx17+1

[Moltke]

What do you show for

Code: Select all

apt policy libgegl-0.4.0 libbabl-0.1-0

gimp 2.10.6 requires these versions:

Code: Select all

libgegl-0.4-0:
  Installed: 0.4.8-1~mx17+1
libbabl-0.1-0:
  Installed: 0.1.56-1~mx17+1

Code: Select all

apt policy libgegl-0.4.0 libbabl-0.1-0

shows

Code: Select all

libgegl-0.4-0:
  Instalados: 0.4.8-1~mx17+1
  Candidato:  0.4.8-1~mx17+1
  Tabla de versión:
 *** 0.4.8-1~mx17+1 100
        100 /var/lib/dpkg/status
libbabl-0.1-0:
  Instalados: 1:0.1.28-dmo1
  Candidato:  1:0.1.28-dmo1
  Tabla de versión:
 *** 1:0.1.28-dmo1 500
        500 https://www.deb-multimedia.org stable/main amd64 Packages
        100 /var/lib/dpkg/status
     0.1.18-1 500
        500 http://debian.ignum.cz/debian stretch/main amd64 Packages

Is that ok? What should I do?

[Stevo]

Aha! That a lower version of libbabl that's from deb-multimedia.org that they make seem higher by adding the "1:" at the beginning. So it's pretending to be a compatible version, but it's not, and you need to replace it with the actually higher version from the test repo.
I don't know if that will remove something from deb-multimedia that depends on it, but you can disable the deb-multimedia repo in Synaptic if it's enabled, and also temporarily enable our test repo there. Then you can close Synaptic and run

Code: Select all

sudo apt install libbabl-0.1-0=0.1.56-1~mx17+1

Hopefully that won't remove anything else; let us know if it does.

After that, disable the test repo in Synaptic or have the MX Package Installer do it by hitting the test repo tab there, but then leaving without doing anything. MXPI disables the test repo automatically after it's done with it.

[Moltke]

Hopefully that won't remove anything else; let us know if it does.

This "Hopefully" doesn't sound promising, not at all...Would it be a better and safer idea removing Gimp entirely and then reinstalling it via the repo test?
I don't want any sick-nasty side-effects from that process. I might as well just use the one from flatpak since it works just fine and leave that as it is for the sake of it.
Besides

Code: Select all

$ aptitude why libbabl-0.1-0

shows

Code: Select all

i   gimp-plugin-registry Depende libbabl-0.1-0

If I get it right it means that the package gimp-plugin-registry would be removed?

[Stevo]

It shouldn't as long as you have our version of libbabl installed. We have a compatible version of gimp-plugin-registry in our test repo: http://mxrepo.com/mx/testrepo/pool/test ... -registry/

That's the trouble with deb-multimedia adding epochs to system libraries--they masquerade as newer compatible upgrades when they aren't, causing these sort of runtime failures. They should just add the epochs to the actual userspace programs like gimp, if they must, and stop doing that to libraries.

[Moltke]

Ok, I just replaced the libbabl package following your instructions for the one from the test repo and now gimp works again. However, I ran it from the terminal to check for any errors and got this

Code: Select all

Missing fast-path babl conversion detected, Implementing missing babl fast paths
accelerates GEGL, GIMP and other software using babl, warnings are printed on
first occurance of formats used where a conversion has to be synthesized
programmatically by babl based on format description

*WARNING* missing babl fast path(s): "R'G'B' double" to "CIE Lab double"
*WARNING* missing babl fast path(s): "cairo-ARGB32" to "R'G'B'A u8"

Apart from this warning message everything else seems to be ok. Is it a bad thing? What does it mean apart from that the system seems unable to find the path for the mentioned packages in the warning? By the way, thanks for helping me out with this you're

One more question, should I enable the deb-multimedia repo again?

[Stevo]

We advise against using deb-multimedia whenever possible. Even when you might think you have to install something from it, there's often an alternative repository, such as for avidemux.

Everyone using that libbabl version gets that warning. It's nothing to worry about.

[Moltke]

Everyone using that libbabl version gets that warning. It's nothing to worry about.

good to know

We advise against using deb-multimedia whenever possible. Even when you might think you have to install something from it, there's often an alternative repository, such as for avidemux.

Ok, well I'll leave it disabled as per your suggestion. Thank you.