12th January 2017, 11:08
12th January 2017, 11:18
However it really propose to uninstall Digikam and at the installation it propose
5.3.0-0neon+16.04+build11
instead of 5.3.0-0neon+16.04+build2 which do not lead to conflict with Plasam 5.8.4.
5.3.0-0neon+16.04+build11
instead of 5.3.0-0neon+16.04+build2 which do not lead to conflict with Plasam 5.8.4.
12th January 2017, 11:31
So digikam can be reinstalled then and doesn't create any problem anymore ?
12th January 2017, 11:59
(12th January 2017, 11:31)leszek Wrote: [ -> ]So digikam can be reinstalled then and doesn't create any problem anymore ?
No this time it refuses packages are broken.
Is there any way to workaround this problem ?
12th January 2017, 12:00
Can you directly select the correct digikam version in synaptic that does install without any problem?
12th January 2017, 12:07
(12th January 2017, 12:00)leszek Wrote: [ -> ]Can you directly select the correct digikam version in synaptic that does install without any problem?
No, it refuses and I have the message broken packages and when I ask for reparing :
in french "impossible de corriger les problèmes, des paquets défecteux sont en mode garder en l'état"
unable to correct the problem, packages are in keep in that state mode.
I hope my translation from message is clear enough.
SM
12th January 2017, 12:12
So no matter what version you choose it refuses to install?
12th January 2017, 12:44
(12th January 2017, 12:12)leszek Wrote: [ -> ]So no matter what version you choose it refuses to install?Exactly, I also tried the digikam version of philip5 ppa and get the same problem.
There is a link between digikam 5.3.0 build11 and plasma 5.8.4. But this time I cant come back to build2 which was succefully install.
So a solution may be to offer the 5.3.0 build 2 version of digikam in servers ?
Sorry for the inconvenience.
SM
12th January 2017, 12:57
We cannot change the version in the repository as not all people have the backports-neon repo activated.
Can you please take a look at the digikam-data and digikam packages and see if they both are in the correct version.
You can also use this command to get a very detailed output on what is going wrong
Can you please take a look at the digikam-data and digikam packages and see if they both are in the correct version.
You can also use this command to get a very detailed output on what is going wrong
Code:
sudo apt-get install digikam -o "Debug::pkgProblemResolver=1"
12th January 2017, 13:10
(12th January 2017, 12:57)leszek Wrote: [ -> ]We cannot change the version in the repository as not all people have the backports-neon repo activated.The result :
Can you please take a look at the digikam-data and digikam packages and see if they both are in the correct version.
You can also use this command to get a very detailed output on what is going wrong
Code:sudo apt-get install digikam -o "Debug::pkgProblemResolver=1"
serge@serge-MacBookPro:~$ sudo apt-get install digikam -o "Debug::pkgProblemResolver=1"
[sudo] Mot de passe de serge :
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances
Lecture des informations d'état... Fait
Starting pkgProblemResolver with broken count: 2
Starting 2 pkgProblemResolver with broken count: 2
Investigating (0) digikam [ amd64 ] < none -> 4:5.3.0-0neon+16.04+build11 > ( graphics )
Broken digikam:amd64 Dépend on libmarblewidget-qt5-25 [ amd64 ] < none -> 4:16.08.2-0neon+16.04+build19 > ( libs )
Considering libmarblewidget-qt5-25:amd64 1 as a solution to digikam:amd64 9999
Reinst Failed early because of libastro1:amd64
Investigating (0) libkf5kipi32.0.0 [ amd64 ] < 16.12.0-0neon+16.04+build2 > ( libs )
Broken libkf5kipi32.0.0:amd64 Casse on libkf5kipi31.0.0 [ amd64 ] < none -> 16.08.2-0neon+16.04+build18 > ( libs )
Considering libkf5kipi31.0.0:amd64 -1 as a solution to libkf5kipi32.0.0:amd64 -2
Removing libkf5kipi32.0.0:amd64 rather than change libkf5kipi31.0.0:amd64
Investigating (1) digikam [ amd64 ] < none -> 4:5.3.0-0neon+16.04+build11 > ( graphics )
Broken digikam:amd64 Dépend on libmarblewidget-qt5-25 [ amd64 ] < none -> 4:16.08.2-0neon+16.04+build19 > ( libs )
Considering libmarblewidget-qt5-25:amd64 1 as a solution to digikam:amd64 9999
Done
Certains paquets ne peuvent être installés. Ceci peut signifier
que vous avez demandé l'impossible, ou bien, si vous utilisez
la distribution unstable, que certains paquets n'ont pas encore
été créés ou ne sont pas sortis d'Incoming.
L'information suivante devrait vous aider à résoudre la situation :
Les paquets suivants contiennent des dépendances non satisfaites :
digikam : Dépend: libmarblewidget-qt5-25 mais ne sera pas installé
E: Impossible de corriger les problèmes, des paquets défectueux sont en mode « garder en l'état ».
serge@serge-MacBookPro:~$