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

[Luca Boccassi]

Control: severity -1 normal

On Mon, 2016-11-14 at 16:20 +0100, Vincent Lefevre wrote:
> On 2016-11-14 15:52:28 +0100, Diederik de Haas wrote:
> > On maandag 14 november 2016 15:12:14 CET Vincent Lefevre wrote:
> > > aptitude often ignores Recommends. So, you should not rely on it.
> > 
> > That's an incorrect statement.
> > Aptitude, and I think apt too, doesn't automatically install _new_ recommended 
> > packages for an already installed package. 
> > It does report "The following recommended packages will not be installed" (or 
> > sth along those lines). But that's far from ignoring it.
> 
> No, I do not always get these reports. Here I didn't even have any
> report that a recommended package would be removed: aptitude just
> said that <some list of packages> would be removed because they are
> no longer used.

I can't manage to reproduce this.

In the end, you shouldn't have let aptitude remove the packages. It can
happen from time to time on unstable to have temporary inconsistent
state in the apt tree (that's why it's called unstable), for example in
this case it was probably because the new amd64 version was up in the
repo but the i386 was still being built/published.

The solution is simply to reinstall what was removed, so there's nothing
that justifies holding he migration of 367.57-2 to stretch, which just
adds a patch to make it compatible with newer kernels which are about to
be uploaded and nothing else, so severity downgraded.

Kind regards,
Luca Boccassi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part
URL: <http://lists.alioth.debian.org/pipermail/pkg-nvidia-devel/attachments/20161122/c90b1ddf/attachment.sig>