[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#844300: nvidia-driver-libs:amd64: upgrade failure due to dependency issue

reassign -1 dpkg 1.18.15

(cutting down heavily on the text)

 On Tue, Nov 22, 2016 at 02:43:35PM +0100, Vincent Lefevre wrote:
> --\ Packages to be upgraded (17)
> iuA nvidia-driver-libs                        367.57-1                 367.57-2
> --\ Packages being removed because they are no longer used (27)
> idA nvidia-driver-libs:i386         -180 kB   367.57-1                 367.57-2
> dpkg: error processing package nvidia-driver-libs:amd64 (--configure):
>  package nvidia-driver-libs:amd64 367.57-2 cannot be configured because nvidia-driver-libs:i386 is at a different version (367.57-1)

This looks like a bug in dpkg as it is not considering the removal of
nvidia-driver-libs:i386 as solution to the problem it runs into here
even through libapt has told it via selections that it wants it removed.

Reproducing is 'easy' with any M-A:same package which is installed for
two (or more) architectures in version 1 and one of the architectures is
upgraded to version 2 while the other is removed.

That said, you can see this bug with apt(itude) only as libapt
incorrectly detects a crossgrade here dropping the explicit remove.
As we (= libapt) want to eventually drop the explicit removes and other
frontends arguable have already like dselect I am reassigning to dpkg
– "fixing" (its closer to a workaround) this in libapt is partly done
already, so I don't need/want a clone.

In terms of the solution itself: I haven't looked closely, but apt tries
to not explore solutions caused by M-A:same version screw – aptitude
seems way more willing to suggest such solutions; that is okay I guess
as it is way more interactive, too.

Best regards

David Kalnischkies

Attachment: signature.asc
Description: PGP signature

Reply to: