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

[Stefan Tsanev]

I agree with Ghis, maybe a little more information before this update
could be in great use here. Some people with bumblebee and enabled
multiarch may find difficulties understanding why their system doesn't
want to continue updating anymore via apt. I sitll feel odd about this
upgrade and I'm glad, that I'm not the only one.

Greetings

2019-05-28 6:38 Гринуич+03:00, ghisvail at gmail.com <ghisvail at gmail.com>:
>> On Sun, 26 May 2019 23:16:48 +0100 Luca Boccassi <bluca at debian.org>
>> wrote:
>> > On Sun, 26 May 2019 at 22:45, <ghisvail at gmail.com> wrote:
>> > >
>> > > Le dimanche 26 mai 2019 à 19:44 +0100, Luca Boccassi a écrit :
>> > >
>> > >  Yes the 390xx series gets
>> > > installed if recommends are enabled, but that was intentional,
>> and
>> > > it's
>> > > sufficient to use --no-install-recommends and the existing series
>> was
>> > > upgrade just fine.
>> > >
>> >
>> > I wonder why the 390xx legacy drivers are being pulled now. It
>> > definitely was not the case when I initially setup my machine with
>> an
>> > older version of nvidia current.
>> >
>> > Indeed, `apt install --no-install-recommends bumblebee-nvidia
>> primus`
>> > does not pull the 390xx series.
>>
>> As the changelog says, it's to have a smooth update for i386 as the
>> mainline doesn't support it anymore.
>
> I wonder whether the upgrade path really is that smooth though.
>
> Afterall, both Stefan and I experienced conflicts in the upgrade
> process on the very same packages (nvidia-nonglvnd-vulkan-common and
> primus). Less experienced users may not feel confident performing the
> upgrade as a result, either by `synaptic` or `apt full-upgrade`
>
> Maybe displaying an explanation for this particular upgrade via
> NEWS.Debian could help? AFAIC, I was not aware that NVIDIA had indeed
> dropped support for 32-bit after release 390 of the drivers.
>
> Cheers,
> Ghis
>
>