On 6/24/25 19:46, Santiago Ruano Rincón wrote:
I plan to contact directly the sponsor to study the impact of
(officially) stopping supporting nvidia-graphics-driver. But before
that, it would be helpful to know if a full version backport is
technically possible or not. Help with that will be ve
On 6/23/25 20:51, Tobias Frost wrote:
However, the version in bullseye, version 470.256.02, is no longer
supported by nvidia (since July 2024) and there simply not enough
information available to actually fix the issues.
Would probably need a newer blob ...
Therefore I'd suggest to drop suppo
On 09/06/2023 16.27, Tobias Frost wrote:
Hi,
I'm currently triaging nvidia-cuda-toolkit for buster:
buster has 9.2.148-7+deb10u1, which is upstream version 9.2.148 with patch 1 [1]
This seems to be the latest upstream version from the 9.2 series, and
9.2.x seem to be EOL, so there is no new upst
Package: squid3-dbg
Version: 3.4.8-6+deb8u9
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: close -1
jessie-elts has squid3-dbg 3.4.8-6+deb8u9, but src:squid3 (and therefore
the squid3 binary package, too) is already at 3.5.23-5+deb8u4 in
jessie-elts, rendering the -
Hi,
I found another one in non-free:
jessie-lts has amd64-microcode 3.20181128.1~deb8u1 but stretch has only
3.20160316.3
amd64-microcode | 2.20160316.1~deb8u1 | jessie/non-free| source,
amd64, i386
amd64-microcode | 3.20160316.3 | stretch/non-free | source,
Hi,
I tried to find all the affected packages, but there is no
guarantee that the following list is complete. ;-)
These packages are out-of-sync since they have a version
in jessie-lts (or earlier -lts) that is newer than in the
subsequent release(s):
* libpam-tacplus https://bugs.debian.org/96
Hi,
I'd like to update src:nvidia-graphics-drivers in stretch from 390.138-1
to 390.141-1 which fixes CVE-2021-1056 (#979670).
For stable, the non-free nvidia drivers are usually updated to new
upstream releases fixing CVEs via stable-pu in point releases without
issuing DSA.
What needs to be don
Hi,
here comes the next round:
On 2017-01-10 16:13, Andreas Beckmann wrote:
> I've prepared a new upstream release of the proprietary nvidia graphics
> driver for wheezy-lts. This will fix several security bugs:
* New upstream legacy 304xx branch release 304.135 (2017-02-14).
On 2017-01-10 17:38, Chris Lamb wrote:
> Andreas Beckmann wrote:
>
>> I've prepared a new upstream release of the proprietary nvidia graphics
>> driver for wheezy-lts. This will fix several security bugs:
>
> Do you have a debdiff handy...? (Or, better still, di
Hi,
I've prepared a new upstream release of the proprietary nvidia graphics
driver for wheezy-lts. This will fix several security bugs:
* New upstream legacy 304xx branch release 304.134 (2016-12-14).
* Fixed CVE-2016-8826. (Closes: #848195)
* New upstream legacy 304xx branch release 304
e list of paths which are searched by
nvidia-bug-report.sh for kernel messages.
- Fixed a bug that caused kernel panics when using the NVIDIA driver on
v4.5 and newer Linux kernels built with CONFIG_DEBUG_VM_PGFLAGS.
* Improved compatibility with recent Linux kernels.
[ A
On 2016-10-31 23:17, Andreas Beckmann wrote:
> Please go ahead - probably we could use the fix (that someone produces
> for wheezy) for jessie and sid as well. Please put everything into git,
> branch wheezy, the repo is in collab-maint.
I have now a completely untested patch for t
On 2016-10-29 18:49, Adrian Bunk wrote:
> On Sun, Oct 23, 2016 at 08:59:47AM +0100, Chris Lamb wrote:
>> Hello dear maintainer(s),
>>
>> the Debian LTS team would like to fix the security issues which are
>> currently open in the Wheezy version of sendmail:
>> https://security-tracker.debian.org/tr
On 2015-10-05 10:15, Santiago Ruano Rincón wrote:
> the Debian LTS team recently reviewed the security issue(s) affecting your
> package in Squeeze:
> https://security-tracker.debian.org/tracker/CVE-2015-5950
>
> We decided that we would not prepare a squeeze security update (usually
> because the
14 matches
Mail list logo
