Re: digikam 3.0 not co-installable with some parts of KDE
On Sunday 17 March 2013 17:57:28 José Manuel Santamaría Lema wrote:
> But what about once you have upgraded to the qt-kde.d.n? Keeping the
> experimental lines in sources.list: do you still need to have the packages
> on hold to prevent an undesired upgrade to the 3.0.0 packages in
> experimental?
If experimental's priority is < 100 (= qt-kde.d.n.'s prio) then neither a safe-
upgrade or a full-upgrade will trigger an upgrade to the 3.0.0 packages.
If experimental's prio is >= 100 then a full-upgrade does want to upgrade
digikam to the 3.0.0 versions and suggest to remove a bunch of other packages
because of unresolved dependencies. A safe-upgrade (still) doesn't upgrade it to
version 3.0.0, but only says that there are 2 upgradeable packages (also
digikam-data).
With digikam on hold, neither full-upgrade or safe-upgrade wants to upgrade.
So 'normally' you don't need to put digikam on hold, unless you've changed
experimental's priority through /etc/apt/preferences(.d/).
HTH,
Diederik
Reply to: