Your message dated Sat, 16 Feb 2019 11:36:33 +0000
with message-id <1550316993.21192.50.ca...@adam-barratt.org.uk>
and subject line Closing bugs for updates included in 9.8
has caused the Debian Bug report #916632,
regarding stretch-pu: package nvidia-graphics-drivers/390.87-4~deb9u1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
916632: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916632
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian....@packages.debian.org
Usertags: pu
Hi,
I'd like to update the non-free nvidia-graphics-drivers in stretch to a
new major upstream release: 384 -> 390
But with that we finally reached a new legacy branch that will receive
updates from NVIDIA until the end of 2022. So any future updates in
stretch will only come from the 390 series and (hopefully) require no or
only minimal changes to the packaging. (Going beyond 390 will be a major
step: i386 and armhf driver support are dropped).
There is currently no CVE known to be fixed with this new release, but I
expect updates for CVE‑2018‑6260 soon.
This is a rebuild of the package in sid with some inappropriate changes
removed. As usual the diff is not minimal compared the the version
currently in stable, but to the versions in sid (this driver series is
also available as nvidia-graphics-drivers-legacy-390xx in sid and (soon)
stretch-backports). This will allow us to keep the packaging of the many
releases in sync and ease propagating future changes through all
packages.
The 390 driver has been available in stretch backports for a long
time already and we are not aware of any regressions.
There is infrastructure to generate debian/control - that will be made
use of in buster, for stretch it just regenerates the exisiting control
file (with comments removed).
We will be dropping three packages (*wayland*) that were only introduced
in a stretch point release. They have no users in stretch and for buster
the functionality will be provided by a separate source package in main.
The debdiff (excluding the blob parts) will be sent in a separate mail
due to size.
This pu needs to go into stable together with glx-alternatives (#916627)
for some changes in the diversions and alternatives.
I'll prepare further updates for nvidia-settings, nvidia-xconfig,
nvidia-modprobe, nvidia-persistenced to the 390.xx release series, too,
to keep the major version in sync with the driver - otherwise we may be
running an unsupported and untested combination of versions (which might
also confuse users due to the significant version skew).
But this will wait until after a new driver release has been published
(I'll either update this pu request or open a new one, depending on
progress) or until the next point release deadlines are announced.
But I'd prefer to see 390.xx in stretch-pu soon, to give it some early
exposure and have more time for testing, even if it means to have two
nvidia-graphics-drivers uploads to stretch-pu for the next point
release.
Andreas
--- End Message ---
--- Begin Message ---
Version: 9.8
Hi,
The update referenced by each of these bugs was included in this
morning's stretch point release.
Regards,
Adam
--- End Message ---
