Unwanted k3b removal (was Debugging apt's dist-upgrade decisions?)
Hello
On 2007-01-09 Christian Hammers wrote:
> * Second problem is that there are still ~100 packages marked for
> deletion. Most of them are probably ok but for some I would like to know
> how apt-get came to this decision. Is there some flag that lets apt-get
> say "x conflicts with y, removing y"?
Something with "dbus-1" vs "dbus" and "hal" till goes wrong and causes
trouble but I couldn't figure out more.
A problem that was easier to spot is the following unwanted removal of k3b:
* currently installed in sarge:
k3b 0.11.20-1
Depends: k3blibs, kdelibs4
k3blibs 0.11.20-1
kdelibs4 4:3.3.2-6.4
* wanted installed on future etch:
k3b 0.12.17-8
Depends: libk3b2 kdelibs4c2a
libk3b2 0.12.17-8
Conflicts: k3blibs
kdelibs4c2a 4:3.5.5a.dfsg.1-5
* Using "apt-get dist-upgrade":
...
Investigating libk3b2
Package libk3b2 has broken dep on k3blibs
Considering k3blibs 0 as a solution to libk3b2 0
Holding Back libk3b2 rather than change k3blibs
...
Investigating k3b
Package k3b has broken dep on libk3b2
Considering libk3b2 0 as a solution to k3b 0
Removing k3b rather than change libk3b2
...
Investigating k3blibs
Package k3blibs has broken dep on kdelibs4
Considering kdelibs4 12 as a solution to k3blibs 0
Removing k3blibs rather than change kdelibs4
...
-> I guess with "Holding Back libk3b2" apt means that it won't install it
newly because the "broken dep" is in fact a "Conflicts" which it does not
want to resolve. But why?
bye,
-christian-
Reply to: