Hello everyone,

Yesterday I did a fresh install of Ubuntu 16.04 and as usual, one the first things I do is install Krita.
When tried to install Krita through the Lime ppa I got the following output:

Code: Select all

The following packages have unmet dependencies:
 krita-2.9 : Depends: libgsl0ldbl (>= 1.9) but it is not installable
             Recommends: create-resources but it is not going to be installed
             Recommends: pstoedit but it is not going to be installed
             Recommends: kde-style-oxygen but it is not going to be installed or
                         kde-style-oxygen-qt4 but it is not going to be installed
             Recommends: krita-2.9-l10n but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

I'm able to install 2.9.7 using the default repositories but that's it. The kubuntu-ppa/backports version doesn't work either.

Anyone stumbled upon the same problem? Any help is appreciated.


Thanks

Yes, it's a known. In the meantime, please test the 3.0 Beta appimages!

Sadly the problem is something weird with Ubuntu's packaging. We're not sure why launchpad even allowed us to make 2.9 available for 16.04 when this dependency error is there.

The best you can do is install krita-3.0, as that's getting more and more stable everyday, or use the appimages, or build yourself, or content yourself with 2.9.7 untill 3.0 is officially released.

Pyteo wrote:Anyone stumbled upon the same problem? Any help is appreciated.

https://bugs.kde.org/show_bug.cgi?id=362806

Hey Pyteo, unfortunately I'm also in the same situation and :
- I can't work with Krita 3.0 beta ( I tried this morning *again* , I couldn't draw a single artwork with it... )
- 2.9.7 was not a good 2.9x release, and a lot of things are buggy in it ( tag/bundle/stabilizer)... I suffered a lot drawing last episode 16 with it.
Yes, I miss 2.9.11. To be productive this afternoon, my only solution is to reinstall another distro maybe...

Thank you everyone for quick replies

alright! This got solved just now!

Fixed now: https://bugs.kde.org/show_bug.cgi?id=362806

Awesome!

Thanks for the heads up.