@Stevo:
Stevo wrote:OK, I found the problem.
Cool!
Stevo wrote:Digikam (thus kipi-plugins) depends on a library from Marble that's specific to the version, so the stock Stretch version of that is libmarblewidget-qt5-25, but the version in the test repo is libmarblewidget-qt5-28. So basically, you currently can't have both the test repo Marble and Digikam installed at the same time. This was a decision I made when I built them each in isolated "vanilla" Stretch pbuilders, but I can also rebuild Digikam against the test repo Marble. That will just force users to also upgrade Marble at the same time, which I was trying to stay away from, but I think that is appropriate in this one case.
Trying to understand that.
Why can't different libmarblewidget-qt5 versions simply coexist on one system?
Stevo wrote:Edit: BTW, the way to track down an issue like this with something like kipi-plugins-common is to try and install it on the command line. If it says it can't install because of a problem with sofor youme other package, then you try and install that other package on the CLI. Repeat the procedure until you get down to the package that is causing the root issue.
I understand. Thanks for the hint.
1) So I'll uninstall
Marble and install both the new
showfoto and the new
Marble from the MX Test Repo tomorrow.
Correct?
2) As far as I remember, installing
showfoto does not necessarily require installing
digikam.
Has digikam now become a showfoto dependency?
Greetings, wishing you a nice weekend, Joe