Processed: nvidia-graphics-drivers-tesla-470 470.223.02-4~deb12u1 flagged for acceptance

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> package release.debian.org
Limiting to bugs with field 'package' containing at least one of 
'release.debian.org'
Limit currently set to 'package':'release.debian.org'

> tags 1063737 = bookworm pending
Bug #1063737 [release.debian.org] bookworm-pu: package 
nvidia-graphics-drivers-tesla-470/470.223.02-4~deb12u1
Added tag(s) pending; removed tag(s) confirmed.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1063737: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063737
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1063737: nvidia-graphics-drivers-tesla-470 470.223.02-4~deb12u1 flagged for acceptance

[Jonathan Wiltshire]

package release.debian.org
tags 1063737 = bookworm pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bookworm.

Thanks for your contribution!

Upload details
==

Package: nvidia-graphics-drivers-tesla-470
Version: 470.223.02-4~deb12u1

Explanation: restore compatibility with newer Linux kernel builds; stop 
building nvidia-cuda-mps

Re: Planning for 12.6

[Cyril Brulebois]

Jonathan Wiltshire  (2024-02-12):
> 12.6 should be around 10th April, so please indicate availability for:
> 
> 6  April
> 13 April
> 20 April

Any of those should work.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#1063823: bullseye-pu: package nvidia-graphics-drivers/470.223.02-2

[Andreas Beckmann]

Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu

[ Reason ]
While preparing the update series for bookworm I realized that I had
missed in the last OPU some changes in
src:nvidia-graphics-drivers/bullseye that were added in
src:nvidia-graphics-drivers-tesa-470/bullseye.
To avoid confusion, these packages should stay in sync.
The relevant bug here is libnvidia-fbc1 not being built on arm64, even
though the library is available in the blob nowadays.

[ Impact ]
A package missing on arm64 (but no dependency problem).

[ Tests ]
Would require nvidia hardware and driver usage.

[ Risks ]
Low. All changes are already present in src:nvidia-graphics-drivers-tesa-470

[ Checklist ]
  [*] *all* changes are documented in the d/changelog
  [*] I reviewed all changes and I approve them
  [*] attach debdiff against the package in (old)stable
  [*] the issue is verified as fixed in unstable

[ Changes ]
nvidia-graphics-drivers (470.223.02-2) bullseye; urgency=medium

  * Build libnvidia-fbc1 for arm64, too.  (Closes: #1057078)
  * bug-control: Report information about more driver components.
  * nvidia-detect: Drop support for Tesla 450 drivers (EoL).
  * *-common: Drop alternative Suggests on EoL Tesla 450 packages that have
been turned into transitional packages.

 -- Andreas Beckmann   Tue, 13 Feb 2024 03:32:54 +0100

 debian/bug-control.mk  |  4 +++-
 debian/changelog   | 19 +++
 debian/control |  7 ++-
 debian/control.in  |  7 ++-
 debian/control.md5sum  |  8 
 debian/copyright   |  2 +-
 debian/detect/nvidia-detect.in | 18 +-
 debian/nvidia.NEWS |  9 +
 debian/rules   |  2 +-
 debian/rules.defs  |  1 -
 10 files changed, 42 insertions(+), 35 deletions(-)

The other changes are cleanup after
src:nvidia-graphics-drivers-tesla-450 has been turned into transitional
packages.

[ Other info ]
This can wait for the next point release, it does not need to go
through oldstable-updates.

Andreas
diff --git a/debian/bug-control.mk b/debian/bug-control.mk
index 899a92e1..75d3e710 100644
--- a/debian/bug-control.mk
+++ b/debian/bug-control.mk
@@ -41,11 +41,13 @@ define PACKAGE_STATUS
libcuda1-any
libcuda.so.1
libnvidia-ml.so.1
-   nvidia-settings
+   nvidia-cuda-mps
+   nvidia-settings$(-variant)
nvidia-xconfig
nvidia-support
nvidia-kernel-common
nvidia-modprobe
+   nvidia-persistenced
xserver-xorg
xserver-xorg-core
xserver-xorg-legacy
diff --git a/debian/changelog b/debian/changelog
index 0687cbcb..87b5a0da 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,13 @@
+nvidia-graphics-drivers (470.223.02-2) bullseye; urgency=medium
+
+  * Build libnvidia-fbc1 for arm64, too.  (Closes: #1057078)
+  * bug-control: Report information about more driver components.
+  * nvidia-detect: Drop support for Tesla 450 drivers (EoL).
+  * *-common: Drop alternative Suggests on EoL Tesla 450 packages that have
+been turned into transitional packages.
+
+ -- Andreas Beckmann   Tue, 13 Feb 2024 03:32:54 +0100
+
 nvidia-graphics-drivers (470.223.02-1) bullseye; urgency=medium
 
   * New upstream long term support branch release 470.223.02 (2023-10-31).
@@ -1064,6 +1074,15 @@ nvidia-graphics-drivers (455.23.04-1) experimental; 
urgency=medium
 
  -- Andreas Beckmann   Thu, 24 Sep 2020 21:52:54 +0200
 
+nvidia-graphics-drivers (450.248.02-4) UNRELEASED; urgency=medium
+
+  * The Tesla 450 driver series has been declared as End-of-Life by
+NVIDIA. No further updates fixing security issues, critical bugs, or
+adding support for new Xorg or Linux releases will be issued.
+https://docs.nvidia.com/datacenter/tesla/drivers/
+
+ -- Andreas Beckmann   Wed, 22 Nov 2023 14:13:01 +0100
+
 nvidia-graphics-drivers (450.248.02-3) UNRELEASED; urgency=medium
 
   * Revert backport of pin_user_pages changes.
diff --git a/debian/control b/debian/control
index eb5c5396..1ac158b5 100644
--- a/debian/control
+++ b/debian/control
@@ -476,7 +476,6 @@ Depends:
 Suggests:
  libegl-${nvidia-}0 [i386 amd64 ${arch:arm64} ${arch:ppc64el}]
  | libegl-nvidia-tesla-470-0 [i386 amd64 arm64 ppc64el]
- | libegl-nvidia-tesla-450-0 [i386 amd64 arm64 ppc64el]
  | libegl-nvidia-tesla-418-0 [i386 amd64 ppc64el]
  | libegl-nvidia-legacy-390xx0 [i386 amd64 armhf],
 Description: NVIDIA binary EGL driver - common files
@@ -546,7 +545,6 @@ Depends:
 Suggests:
  ${nvidia}-vulkan-icd [i386 amd64 ${arch:arm64} ${arch:ppc64el}]
  | nvidia-tesla-470-vulkan-icd [i386 amd64 arm64 ppc64el]
- | nvidia-tesla-450-vulkan-icd [i386 amd64 arm64 ppc64el]
  | nvidia-tesla-418-vulkan-icd [i386 amd64 ppc64el]
  | nvidia-legacy-390xx-vulkan-icd [i386 amd64],
 Conflicts:
@@ -877,7 +875,7 @@ Description: NVIDIA OpenGL-based Inband Frame Readback 
runtime libr

Bug#1063821: bullseye-pu: package python-dnslib/0.9.14-1

[Scott Kitterman]

Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu


[ Reason ]
Address no-dsa CVE.  CVE-2022-22846

[ Impact ]
Continued vulnerability to minor issue.

[ Tests ]
Package has tests which are run via autopkgtest and during the build.
Both pass locally with the added patch.

[ Risks ]
Risk is minimal.  Patch is from upstream and has been around for awhile
without known issues.  Change is trivial.

[ Checklist ]
  [X] *all* changes are documented in the d/changelog
  [X] I reviewed all changes and I approve them
  [X] attach debdiff against the package in (old)stable
  [X] the issue is verified as fixed in unstable

[ Changes ]
Add verify that the ID value in a DNS reply matches an ID value in a query.

[ Other info ]
I've only ever used this for running local tests to mock DNS responses,
which is not a case that's at risk for this issue, but it did occur to
me others may use it differently, so probably better to fix it.

Scott K
diff -Nru python-dnslib-0.9.14/debian/changelog 
python-dnslib-0.9.14/debian/changelog
--- python-dnslib-0.9.14/debian/changelog   2020-06-10 00:51:44.0 
-0400
+++ python-dnslib-0.9.14/debian/changelog   2024-02-12 19:43:55.0 
-0500
@@ -1,3 +1,9 @@
+python-dnslib (0.9.14-1+deb11u1) bullseye; urgency=medium
+
+  * Add d/p/0002-Validate-TXID-in-client.py.patch to address CVE-2022-22846
+
+ -- Scott Kitterman   Mon, 12 Feb 2024 19:43:55 -0500
+
 python-dnslib (0.9.14-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru 
python-dnslib-0.9.14/debian/patches/0002-Validate-TXID-in-client.py.patch 
python-dnslib-0.9.14/debian/patches/0002-Validate-TXID-in-client.py.patch
--- python-dnslib-0.9.14/debian/patches/0002-Validate-TXID-in-client.py.patch   
1969-12-31 19:00:00.0 -0500
+++ python-dnslib-0.9.14/debian/patches/0002-Validate-TXID-in-client.py.patch   
2024-02-12 19:42:50.0 -0500
@@ -0,0 +1,24 @@
+From: Scott Kitterman 
+Date: Sat, 12 Feb 2024 19:41:26 -0500
+Subject: Validate TXID in client.py
+Fixes CVE-2022-22846
+Origin: backport, 
https://github.com/paulc/dnslib/commit/76e8677699ed098387d502c57980f58da642aeba
+
+---
+ dnslib/client.py | 3 +++
+ 1 file changed, 3 insertions(+)
+
+diff --git a/dnslib/client.py b/dnslib/client.py
+index 628ea81..09572b6 100644
+--- a/dnslib/client.py
 b/dnslib/client.py
+@@ -76,6 +76,9 @@ if __name__ == '__main__':
+ a_pkt = q.send(address,port,tcp=args.tcp)
+ a = DNSRecord.parse(a_pkt)
+ 
++if q.header.id != a.header.id:
++raise DNSError('Response transaction id does not match query 
transaction id')
++
+ if a.header.tc and args.noretry == False:
+ # Truncated - retry in TCP mode
+ a_pkt = q.send(address,port,tcp=True)
diff -Nru python-dnslib-0.9.14/debian/patches/series 
python-dnslib-0.9.14/debian/patches/series
--- python-dnslib-0.9.14/debian/patches/series  2020-06-10 00:50:31.0 
-0400
+++ python-dnslib-0.9.14/debian/patches/series  2024-02-12 19:43:55.0 
-0500
@@ -1 +1,2 @@
 0001-Only-run-tests-for-python3.patch
+0002-Validate-TXID-in-client.py.patch

Bug#1063675: nvidia-graphics-drivers 525.147.05-6~deb12u1 flagged for acceptance

[Jonathan Wiltshire]

On Mon, Feb 12, 2024 at 08:07:36PM +0100, Patrick ZAJDA wrote:
> 
> 
> Le 12/02/2024 à 18:56, Jonathan Wiltshire a écrit :
> > package release.debian.org
> > tags 1063675 = bookworm pending
> > thanks
> > 
> > Hi,
> > 
> > The upload referenced by this bug report has been flagged for acceptance 
> > into the proposed-updates queue for Debian bookworm.
> > 
> > Thanks for your contribution!
> > 
> > Upload details
> > ==
> > 
> > Package: nvidia-graphics-drivers
> > Version: 525.147.05-6~deb12u1
> > 
> > Explanation: restore compatibility with newer Linux kernel builds; take 
> > over packages from nvidia-graphics-drivers-tesla; add new 
> > nvidia-suspend-common package
> > 
> So the update won't be available in bookworm-update and we must add
> proposed-update to our sources to be able to update to latest kernel?
> Or do I miss something?

It will be released in bookworm at the next point release, and all being
well earlier than that via bookworm-updates.

Testing of the packages through proposed-updates before then is
appreciated, as always.

-- 
Jonathan Wiltshire  j...@debian.org
Debian Developer http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51
ed25519/0x196418AAEB74C8A1: CA619D65A72A7BADFC96D280196418AAEB74C8A1

Re: Planning for 12.6

[Jonathan Wiltshire]

On Mon, Feb 12, 2024 at 06:29:36PM +, Adam D. Barratt wrote:
> On Mon, 2024-02-12 at 18:04 +, Jonathan Wiltshire wrote:
> > 12.6 should be around 10th April, so please indicate availability
> > for:
> > 
> > 7  April
> 
> I assume you mean the 6th here. That should be doable.

I did.

> > 13 April
> 
> Could work, but I would prefer not to for personal reasons.

I suspected as much :)

> > 20 April
> 
> I'll be returning from time abroad probably late the day before, so no
> from me.

Ok.


-- 
Jonathan Wiltshire  j...@debian.org
Debian Developer http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51
ed25519/0x196418AAEB74C8A1: CA619D65A72A7BADFC96D280196418AAEB74C8A1

Re: Planning for 12.6

[Steve McIntyre]

On Mon, Feb 12, 2024 at 06:04:17PM +, Jonathan Wiltshire wrote:
>Hi,
>
>12.6 should be around 10th April, so please indicate availability for:
>
>7  April
>13 April
>20 April

Any of those should work for me, assuming (re Adam) that you mean 6
April and not 7 April.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
Dance like no one's watching. Encrypt like everyone is.
 - @torproject

Re: Planning for 12.6

[Andrew M.A. Cater]

On Mon, Feb 12, 2024 at 06:04:17PM +, Jonathan Wiltshire wrote:
> Hi,
> 
> 12.6 should be around 10th April, so please indicate availability for:
> 
> 7  April
> 13 April
> 20 April
> 
> Thanks,
> 

Should be available for all these

Andy

> -- 
> Jonathan Wiltshire  j...@debian.org
> Debian Developer http://people.debian.org/~jmw
> 
> 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51
> ed25519/0x196418AAEB74C8A1: CA619D65A72A7BADFC96D280196418AAEB74C8A1
> 

Bug#1063770: transition: mupdf

[Victor Westerhuis]

On 12/02/2024 15:30, Kan-Ru Chen (陳侃如) wrote:

Package: release.debian.org
Severity: normal
X-Debbugs-Cc: mu...@packages.debian.org, pymu...@packages.debian.org, 
sio...@packages.debian.org, ippsam...@packages.debian.org
Control: affects -1 + src:mupdf
User: release.debian@packages.debian.org
Usertags: transition

Hi Release Team,

This is a somewhat unusual transition request. The libmupdf-dev package
used to only ship static library archives due to upstream preference.
Recently upstream started to provide makefiles for building shared library
so I think it's time to ship shared library in Debian.
I'm glad upstream has started providing support for shared libraries, 
especially with the library size of libmupdf.


I've uploaded the new version to experimental (binary package libmupdf23.10)
and tried to build the affected reverse build-deps (Cc'ed).

ippsample - doesn't seem to use mupdf at all
pymupdf - requires some changes. Likely also needs to update to new upstream 
version.
sioyek - requires some changes to drop extra linker flags.
I have prepared an updated version of sioyek at 
https://salsa.debian.org/viccie30/sioyek/-/tree/debian/experimental that 
builds and runs with the version of mupdf in experimental. Once the 
transition starts and the updated libmupdf-dev is uploaded to unstable, 
I will double-check the version of the mupdf dependency and upload the 
new version of sioyek.


Ben file:

title = "mupdf";
is_affected = .build-depends ~ "libmupdf-dev";
is_good = .depends ~ "libmupdf23.10";
is_bad = ! .depends ~ "libmupdf23.10";



--
Vriendelijke groet, Kind regards,

Victor Westerhuis

Processed: reassign 1063780 to nvidia-kernel-dkms, forcibly merging 1062932 1063780

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 1063780 nvidia-kernel-dkms
Bug #1063780 [nvidia-kernel-dkms v525.147.05-4~deb12u1 against 
linux-image-6.1.0-18-amd64 and linux-headers-6.1.0-18-amd64.] Package: 
linux-image-6.1.0-18-amd64, linux-headers-6.1.0-18-amd64, and 
nvidia-kernel-dkms v525.147.05-4~deb12u1
Warning: Unknown package 'v525.147.05-4~deb12u1'
Warning: Unknown package 'against'
Warning: Unknown package 'linux-headers-6.1.0-18-amd64.'
Bug reassigned from package 'nvidia-kernel-dkms v525.147.05-4~deb12u1 against 
linux-image-6.1.0-18-amd64 and linux-headers-6.1.0-18-amd64.' to 
'nvidia-kernel-dkms'.
Ignoring request to alter found versions of bug #1063780 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1063780 to the same values 
previously set
> forcemerge 1062932 1063780
Bug #1062932 {Done: Andreas Beckmann } [nvidia-kernel-dkms] 
nvidia-kernel-dkms: dkms module won't build against linux-image-6.1.0-18-amd64 
(6.1.76-1)
Bug #1063668 {Done: Andreas Beckmann } [nvidia-kernel-dkms] 
linux-image-6.1.0-18-amd64: Nvidia 525.147.05-4 issues
Bug #1063689 {Done: Andreas Beckmann } [nvidia-kernel-dkms] 
linux-image-6.1.0-18-amd64 not usable with NVIDIA GPU
Bug #1063713 {Done: Andreas Beckmann } [nvidia-kernel-dkms] 
linux-image-6.1.0-18-amd64: apt fails to install the kernel version, reports 
problem with building modules
Bug #1063717 {Done: Andreas Beckmann } [nvidia-kernel-dkms] 
cuda-drivers: Build of module nvidia.ko fails
Bug #1063729 {Done: Andreas Beckmann } [nvidia-kernel-dkms] 
Kernel panic after update from Debian 12.4 to 12.5 in command line and reboot
Bug #1063731 {Done: Andreas Beckmann } [nvidia-kernel-dkms] 
Kernel panic after update from Debian 12.4 to 12.5 in command line
Bug #1063780 [nvidia-kernel-dkms] Package: linux-image-6.1.0-18-amd64, 
linux-headers-6.1.0-18-amd64, and nvidia-kernel-dkms v525.147.05-4~deb12u1
Severity set to 'grave' from 'normal'
1063780 was not blocked by any bugs.
1063780 was not blocking any bugs.
Added blocking bug(s) of 1063780: 1063675
Marked Bug as done
Marked as fixed in versions nvidia-graphics-drivers/525.147.05-6, 
nvidia-graphics-drivers/525.147.05-6~deb12u1, and 
nvidia-graphics-drivers/535.54.03-1.
Marked as found in versions nvidia-graphics-drivers/525.147.05-4~deb12u1.
Added tag(s) patch and ftbfs.
Bug #1063668 {Done: Andreas Beckmann } [nvidia-kernel-dkms] 
linux-image-6.1.0-18-amd64: Nvidia 525.147.05-4 issues
Bug #1063689 {Done: Andreas Beckmann } [nvidia-kernel-dkms] 
linux-image-6.1.0-18-amd64 not usable with NVIDIA GPU
Bug #1063713 {Done: Andreas Beckmann } [nvidia-kernel-dkms] 
linux-image-6.1.0-18-amd64: apt fails to install the kernel version, reports 
problem with building modules
Bug #1063717 {Done: Andreas Beckmann } [nvidia-kernel-dkms] 
cuda-drivers: Build of module nvidia.ko fails
Bug #1063729 {Done: Andreas Beckmann } [nvidia-kernel-dkms] 
Kernel panic after update from Debian 12.4 to 12.5 in command line and reboot
Bug #1063731 {Done: Andreas Beckmann } [nvidia-kernel-dkms] 
Kernel panic after update from Debian 12.4 to 12.5 in command line
Merged 1062932 1063668 1063689 1063713 1063717 1063729 1063731 1063780
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1062932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062932
1063668: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063668
1063689: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063689
1063713: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063713
1063717: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063717
1063729: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063729
1063731: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063731
1063780: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063780
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Re: Planning for 12.6

[Emyr Williams]

I'm pretty sure I'm ok for all those dates, but will confirm.


Emyr

On 12/02/2024 18:04, Jonathan Wiltshire wrote:

Hi,

12.6 should be around 10th April, so please indicate availability for:

7  April
13 April
20 April

Thanks,

NEW changes in stable-new

[Debian FTP Masters]

Processing changes file: 
nvidia-settings_525.147.05-1~deb12u1_amd64-buildd.changes
  ACCEPT
Processing changes file: 
nvidia-settings_525.147.05-1~deb12u1_arm64-buildd.changes
  ACCEPT
Processing changes file: 
nvidia-settings_525.147.05-1~deb12u1_ppc64el-buildd.changes
  ACCEPT

Bug#1063736: snort removal from bullseye (Re: Bug#1063736: RM: snort -- RoQA; security issues, unmaintained)

[Moritz Muehlenhoff]

On Mon, Feb 12, 2024 at 06:16:48PM +, Jonathan Wiltshire wrote:
> On Mon, Feb 12, 2024 at 09:24:47AM +, Holger Levsen wrote:
> > hi,
> > 
> > On Sun, Feb 11, 2024 at 09:44:18PM +, Jonathan Wiltshire wrote:
> > > Requested by security team. Not in stable or testing.
> > 
> > once this has happened we should communicate this to our users via
> > debian-security-upload to bullseye.
> 
> Looping in security in case security support should be withdrawn earlier.
> (The removal won't happen until the next and final point release.)

That's fine, all current bugs are addressed in bullseye, except a
minor logrotate issue.

Cheers,
Moritz

Bug#1063675: nvidia-graphics-drivers 525.147.05-6~deb12u1 flagged for acceptance

[Patrick ZAJDA]

Le 12/02/2024 à 18:56, Jonathan Wiltshire a écrit :

package release.debian.org
tags 1063675 = bookworm pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bookworm.

Thanks for your contribution!

Upload details
==

Package: nvidia-graphics-drivers
Version: 525.147.05-6~deb12u1

Explanation: restore compatibility with newer Linux kernel builds; take over 
packages from nvidia-graphics-drivers-tesla; add new nvidia-suspend-common 
package

So the update won't be available in bookworm-update and we must add 
proposed-update to our sources to be able to update to latest kernel?

Or do I miss something?

Best regards,
--
Patrick ZAJDA


OpenPGP_0x9D4AD35BEA273DCA.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

NEW changes in stable-new

[Debian FTP Masters]

Processing changes file: 
nvidia-graphics-drivers_525.147.05-6~deb12u1_arm64-buildd.changes
  ACCEPT
Processing changes file: 
nvidia-graphics-drivers_525.147.05-6~deb12u1_armhf-buildd.changes
  ACCEPT
Processing changes file: 
nvidia-graphics-drivers_525.147.05-6~deb12u1_i386-buildd.changes
  ACCEPT
Processing changes file: 
nvidia-graphics-drivers_525.147.05-6~deb12u1_ppc64el-buildd.changes
  ACCEPT

Bug#1063675: bookworm-pu: package nvidia-graphics-drivers/525.147.05-6~deb12u1

[Sebastiaan Couwenberg]

Keeping an eye on the Release Calendar can help too:

 https://release.debian.org/release-calendar.ics

Kind Regards,

Bas

--
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

NEW changes in stable-new

[Debian FTP Masters]

Processing changes file: nvidia-settings_525.147.05-1~deb12u1_source.changes
  ACCEPT

Processed: nvidia-settings 525.147.05-1~deb12u1 flagged for acceptance

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> package release.debian.org
Limiting to bugs with field 'package' containing at least one of 
'release.debian.org'
Limit currently set to 'package':'release.debian.org'

> tags 1063742 = bookworm pending
Bug #1063742 [release.debian.org] bookworm-pu: package 
nvidia-settings/525.147.05-1~deb12u1
Added tag(s) pending; removed tag(s) confirmed.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1063742: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063742
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1063742: nvidia-settings 525.147.05-1~deb12u1 flagged for acceptance

[Jonathan Wiltshire]

package release.debian.org
tags 1063742 = bookworm pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bookworm.

Thanks for your contribution!

Upload details
==

Package: nvidia-settings
Version: 525.147.05-1~deb12u1

Explanation: also build for ppc64el

Re: Planning for 12.6

[Adam D. Barratt]

On Mon, 2024-02-12 at 18:04 +, Jonathan Wiltshire wrote:
> 12.6 should be around 10th April, so please indicate availability
> for:
> 
> 7  April

I assume you mean the 6th here. That should be doable.

> 13 April

Could work, but I would prefer not to for personal reasons.

> 20 April

I'll be returning from time abroad probably late the day before, so no
from me.

Regards,

Adam

Processed: Re: Bug#1055656: bookworm-pu: package ms-gsl/4.0.0-2+deb12u1

[Debian Bug Tracking System]

Processing control commands:

> tag -1 confirmed
Bug #1055656 [release.debian.org] bookworm-pu: package ms-gsl/4.0.0-2+deb12u1
Added tag(s) confirmed.

-- 
1055656: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055656
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1055656: bookworm-pu: package ms-gsl/4.0.0-2+deb12u1

[Jonathan Wiltshire]

Control: tag -1 confirmed

On Thu, Nov 09, 2023 at 09:00:09PM +0300, Nicholas Guriev wrote:
> [ Reason ]
> The libmsgsl-dev package in stable is currently incompatible with std::variant
> from GNU's libstdc++. To solve this issue, I propose a patch adding 
> conditional
> noexcept for the gsl::not_null template constructors.

Please go ahead.

Thanks,


-- 
Jonathan Wiltshire  j...@debian.org
Debian Developer http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51
ed25519/0x196418AAEB74C8A1: CA619D65A72A7BADFC96D280196418AAEB74C8A1

Bug#1063675: bookworm-pu: package nvidia-graphics-drivers/525.147.05-6~deb12u1

[Adam D. Barratt]

On Mon, 2024-02-12 at 17:59 +, Jonathan Wiltshire wrote:
> The point release dates go to
> debian-stable-annou...@lists.debian.org which
> is very low traffic.

Actually, that's one place they *don't* go in advance. The first mail
to -stable-announce is at the point that processing of uploads is
already frozen.

(They do go to -project@ldo, amongst others, which is also generally
not too busy.)

Sending to d-d-a would require a second mail in each case, as the main
announcement is to debian-release@ BCCed to several other lists and
team aliases. From memory of previous discussions, dda was avoided both
for that reason and because it doesn't really capture the right
audience (not everyone who cares about point releases is a DD, and
"many" DDs don't particularly care about stable updates).

If it would help, we could easily add an additional address to the
notification list.

Regards,

Adam

Processed: Re: Bug#1055036: bookworm-pu: package crmsh/4.4.1-1+deb12u1

[Debian Bug Tracking System]

Processing control commands:

> tag -1 moreinfo
Bug #1055036 [release.debian.org] bookworm-pu: package crmsh/4.4.1-1+deb12u1
Added tag(s) moreinfo.

-- 
1055036: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055036
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1055036: bookworm-pu: package crmsh/4.4.1-1+deb12u1

[Jonathan Wiltshire]

Control: tag -1 moreinfo

On Sun, Oct 29, 2023 at 10:16:25PM +0100, Valentin Vidic wrote:
> diff -Nru crmsh-4.4.1/debian/crmsh.postinst crmsh-4.4.1/debian/crmsh.postinst
> --- crmsh-4.4.1/debian/crmsh.postinst 1970-01-01 01:00:00.0 +0100
> +++ crmsh-4.4.1/debian/crmsh.postinst 2023-10-29 20:46:13.0 +0100
> @@ -0,0 +1,46 @@
> +#!/bin/sh
> +# postinst script for crmsh
> +#
> +# see: dh_installdeb(1)
> +
> +set -e
> +
> +# summary of how this script can be called:
> +#*  `configure' 
> +#*  `abort-upgrade' 
> +#*  `abort-remove' `in-favour' 
> +#  
> +#*  `abort-deconfigure' `in-favour'
> +#`removing'
> +#   
> +# for details, see http://www.debian.org/doc/debian-policy/ or
> +# the debian-policy package
> +#
> +
> +case "$1" in
> +configure)
> +mkdir -p /var/log/crmsh
> +chown hacluster:haclient /var/log/crmsh
> +chmod 0775 /var/log/crmsh
> +
> +touch /var/log/crmsh/crmsh.log
> +chown hacluster:haclient /var/log/crmsh/crmsh.log
> +chmod 0664 /var/log/crmsh/crmsh.log
> +;;

This will happen on every package update, no? What if the local
administrator has set other properties on the log file (e.g. to allow other
users to read it)?


-- 
Jonathan Wiltshire  j...@debian.org
Debian Developer http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51
ed25519/0x196418AAEB74C8A1: CA619D65A72A7BADFC96D280196418AAEB74C8A1

Bug#1063736: snort removal from bullseye (Re: Bug#1063736: RM: snort -- RoQA; security issues, unmaintained)

[Jonathan Wiltshire]

On Mon, Feb 12, 2024 at 09:24:47AM +, Holger Levsen wrote:
> hi,
> 
> On Sun, Feb 11, 2024 at 09:44:18PM +, Jonathan Wiltshire wrote:
> > Requested by security team. Not in stable or testing.
> 
> once this has happened we should communicate this to our users via
> debian-security-upload to bullseye.

Looping in security in case security support should be withdrawn earlier.
(The removal won't happen until the next and final point release.)

Thanks,

-- 
Jonathan Wiltshire  j...@debian.org
Debian Developer http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51
ed25519/0x196418AAEB74C8A1: CA619D65A72A7BADFC96D280196418AAEB74C8A1

NEW changes in stable-new

[Debian FTP Masters]

Processing changes file: 
nvidia-graphics-drivers_525.147.05-6~deb12u1_amd64.changes
  ACCEPT
Processing changes file: slurm-wlm-contrib_22.05.8-4+deb12u2_amd64.changes
  ACCEPT

Planning for 12.6

[Jonathan Wiltshire]

Hi,

12.6 should be around 10th April, so please indicate availability for:

7  April
13 April
20 April

Thanks,

-- 
Jonathan Wiltshire  j...@debian.org
Debian Developer http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51
ed25519/0x196418AAEB74C8A1: CA619D65A72A7BADFC96D280196418AAEB74C8A1



signature.asc
Description: PGP signature

Bug#1063675: bookworm-pu: package nvidia-graphics-drivers/525.147.05-6~deb12u1

[Jonathan Wiltshire]

On Mon, Feb 12, 2024 at 12:37:44AM +0100, Andreas Beckmann wrote:
> On 11/02/2024 21.36, Salvatore Bonaccorso wrote:
> > If I can add a comment: I (but note I'm not wearing a
> > nvidia-graphics-drivers maintainer hat) would support that, as there
> > are enough people affected by this. This is quite unfortunate and I'm
> > open to hear ideas how we can try to avoid such fallouts.
> 
> I was aware of the bug (#1062932) but not of the fact a point release was
> upcoming. Even if I had been aware of the point release I'm not sure if I
> had realized the impact of this bug to make me yell ;-)
> Perhaps once point release dates have been choosen, this could be announced
> to d-d-a@ as well.
> I'm not following debian-release@ ... -ENOTIME

The point release dates go to debian-stable-annou...@lists.debian.org which
is very low traffic. But I agree it's likely that it would have been a
hidden problem anyway.

> > As you know we are strictly following upstream stable series (and
> > trying our best to keep an eye on as well regression reports upstream,
> > but OOT modules are not explicitly tested, so neither the nvidia ones)
> 
> Are autopkgtests being run for proposed-updates? That should have shown the
> issue.
> 
> It was unfortunate that this upstream backported change appeared in
> proposed-updates first and in sid only a few days later. And the
> metapackages from linux-signed-amd64 are still depending on the version
> before this change was introduced ... so I only could reproduce the issue
> (and verify fixes) manually. (The module build test done during the package
> build did not use the regressing headers.)
> 
> Then I had to spent quite some time verifying that the issue only happened
> on amd64 and since the 460 series (despite of ppc64el having even more calls
> to pfn_valid() dating back to the 418 series).
> 
> Andreas
> 
> PS: @Salvatore: Looking forward to see some linux 6.8 packages in
> experimental s.t. I can throw them in my module build chroot to see what
> breaks next :-) Or do you already have some early build available somewhere
> while experimental is still preparing 6.7?

-- 
Jonathan Wiltshire  j...@debian.org
Debian Developer http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51
ed25519/0x196418AAEB74C8A1: CA619D65A72A7BADFC96D280196418AAEB74C8A1

Processed: nvidia-graphics-drivers 525.147.05-6~deb12u1 flagged for acceptance

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> package release.debian.org
Limiting to bugs with field 'package' containing at least one of 
'release.debian.org'
Limit currently set to 'package':'release.debian.org'

> tags 1063675 = bookworm pending
Bug #1063675 [release.debian.org] bookworm-pu: package 
nvidia-graphics-drivers/525.147.05-6~deb12u1
Added tag(s) pending; removed tag(s) confirmed.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1063675: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063675
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1063675: nvidia-graphics-drivers 525.147.05-6~deb12u1 flagged for acceptance

[Jonathan Wiltshire]

package release.debian.org
tags 1063675 = bookworm pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bookworm.

Thanks for your contribution!

Upload details
==

Package: nvidia-graphics-drivers
Version: 525.147.05-6~deb12u1

Explanation: restore compatibility with newer Linux kernel builds; take over 
packages from nvidia-graphics-drivers-tesla; add new nvidia-suspend-common 
package

Processed: transition: mupdf

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + src:mupdf
Bug #1063770 [release.debian.org] transition: mupdf
Added indication that 1063770 affects src:mupdf

-- 
1063770: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063770
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1063770: transition: mupdf

[陳侃如]

Package: release.debian.org
Severity: normal
X-Debbugs-Cc: mu...@packages.debian.org, pymu...@packages.debian.org, 
sio...@packages.debian.org, ippsam...@packages.debian.org
Control: affects -1 + src:mupdf
User: release.debian@packages.debian.org
Usertags: transition

Hi Release Team,

This is a somewhat unusual transition request. The libmupdf-dev package
used to only ship static library archives due to upstream preference.
Recently upstream started to provide makefiles for building shared library
so I think it's time to ship shared library in Debian.

I've uploaded the new version to experimental (binary package libmupdf23.10)
and tried to build the affected reverse build-deps (Cc'ed).

ippsample - doesn't seem to use mupdf at all
pymupdf - requires some changes. Likely also needs to update to new upstream 
version.
sioyek - requires some changes to drop extra linker flags.

Ben file:

title = "mupdf";
is_affected = .build-depends ~ "libmupdf-dev";
is_good = .depends ~ "libmupdf23.10";
is_bad = ! .depends ~ "libmupdf23.10";

Processed: snort removal from bullseye (Re: Bug#1063736: RM: snort -- RoQA; security issues, unmaintained)

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> clone 1063736 -1
Bug #1063736 [release.debian.org] RM: snort -- RoQA; security issues, 
unmaintained
Bug 1063736 cloned as bug 1063756
> reassign -1 debian-security-support
Bug #1063756 [release.debian.org] RM: snort -- RoQA; security issues, 
unmaintained
Bug reassigned from package 'release.debian.org' to 'debian-security-support'.
Ignoring request to alter found versions of bug #1063756 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1063756 to the same values 
previously set
> retitle -1 document snort situation in bullseye
Bug #1063756 [debian-security-support] RM: snort -- RoQA; security issues, 
unmaintained
Changed Bug title to 'document snort situation in bullseye' from 'RM: snort -- 
RoQA; security issues, unmaintained'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1063736: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063736
1063756: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063756
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1063736: snort removal from bullseye (Re: Bug#1063736: RM: snort -- RoQA; security issues, unmaintained)

[Holger Levsen]

clone 1063736 -1
reassign -1 debian-security-support
retitle -1 document snort situation in bullseye
thanks

hi,

On Sun, Feb 11, 2024 at 09:44:18PM +, Jonathan Wiltshire wrote:
> Package: release.debian.org
> Severity: normal
> Tags: bullseye
> User: release.debian@packages.debian.org
> Usertags: rm
> 
> Requested by security team. Not in stable or testing.

once this has happened we should communicate this to our users via
debian-security-upload to bullseye.


-- 
cheers,
Holger

 ⢀⣴⠾⠻⢶⣦⠀
 ⣾⠁⢠⠒⠀⣿⡁  holger@(debian|reproducible-builds|layer-acht).org
 ⢿⡄⠘⠷⠚⠋⠀  OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C
 ⠈⠳⣄

Deadly heatwaves, floods, storms, wildfires, droughts, crop failures... 
This is not “the new normal”. We’re at the very beginning of a climate and
ecological emergency, and extreme weather events will only become more and
more frequent.


signature.asc
Description: PGP signature