Bug#929521: Conflicts in upgrade to 418.74-1 with optimus setup

[Andreas Beckmann]

On 07/06/2019 18.12, Luca Boccassi wrote:
> Hi, this should be the list:
> 
> bbswitch bumblebee bumblebee-nvidia primus primus-libs primus-libs-ia32 
> nvidia-driver-libs-nonglvnd nvidia-driver-libs-nonglvnd-i386

Is this documented somewhere?

This can be minimized to
  apt-get install --install-recommends \
    nvidia-driver-libs-nonglvnd bumblebee-nvidia primus
if i386 is available as a foreign architecture.

That makes me think: should we have a primus-nvidia metapackage that
depends on these packages?

Which component in this stack did not work with libgl1-nvidia-glvnd-glx?
According to the existing Breaks this should be primus ...

Running
  apt-get install --install-recommends bumblebee-nvidia primus
in a minimal *stretch* chroot results in the installation of
  nvidia-driver nvidia-driver-libs libgl1-glvnd-nvidia-glx ...
which does not give a working setup?

Running
  apt-get install --install-recommends bumblebee-nvidia primus
in a minimal *buster* chroot results in the installation of
nvidia-kernel-dkms, but no driver or library components, which does not
sound useful either.

I'll send some piuparts logs to this bug later, dropping all Cc:s.
Testing stretch->buster upgrades with
* foreign arch i386 enabled and
* --install-recommends enabled
of the package set nvidia-driver-libs-nonglvnd bumblebee-nvidia primus
did not show problems. It pulled in some legacy-390xx packages, but not
the 390xx driver itself. It will be hard to reproduce the problem people
exerienced with some transient set of packages from testing installed.

We will probably have to review the Depends/Recommends/Suggests in the
bumblebee and primus packages ... to better cope with the driver:i386
removal.


Andreas