Bug#1071266: bookworm-pu: package software-properties/0.99.30-4.1~deb12u1
Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: Julian Andres Klode , Matthias Klumpp
Control: affects -1 + src:software-properties
[ Reason ]
software-properties-qt/bookworm has taken over
software-properties-kde/bullseye but lacks corresponding
Breaks+Replaces. As a result file conflicts may happen on certain
upgrade paths.
[ Impact ]
Upgrade failures that may need manual interaction to resolve.
[ Tests ]
Manual upgrade tests with the fixed package.
[ Risks ]
Low, Conflicts+Replaces against a ackage not in bookowrm.
[ 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 ]
software-properties (0.99.30-4.1~deb12u1) bookworm; urgency=medium
* Non-maintainer upload.
* Rebuild for bookworm.
-- Andreas Beckmann Fri, 17 May 2024 14:23:15 +0200
software-properties (0.99.30-4.1) unstable; urgency=medium
* Non-maintainer upload.
* software-properties-qt: Add Conflicts+Replaces: software-properties-kde
for smoother upgrades from bullseye. (Closes: #1034993)
-- Andreas Beckmann Sat, 27 Apr 2024 21:08:49 +0200
[ Other info ]
The package has already been uploaded.
Andreas
diff --git a/debian/changelog b/debian/changelog
index 8c9ea885..b36e9017 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,18 @@
+software-properties (0.99.30-4.1~deb12u1) bookworm; urgency=medium
+
+ * Non-maintainer upload.
+ * Rebuild for bookworm.
+
+ -- Andreas Beckmann Fri, 17 May 2024 14:23:15 +0200
+
+software-properties (0.99.30-4.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * software-properties-qt: Add Conflicts+Replaces: software-properties-kde
+for smoother upgrades from bullseye. (Closes: #1034993)
+
+ -- Andreas Beckmann Sat, 27 Apr 2024 21:08:49 +0200
+
software-properties (0.99.30-4) unstable; urgency=medium
* py3-software-properties: Depend on lazr.restfulclient (Closes: #1029047)
diff --git a/debian/control b/debian/control
index 94d20bd7..790eaae4 100644
--- a/debian/control
+++ b/debian/control
@@ -109,6 +109,8 @@ Depends: debconf-kde-helper,
${misc:Depends},
${python3:Depends}
Suggests: plasma-discover
+Conflicts: software-properties-kde
+Replaces: software-properties-kde
Description: manage the repositories that you install software from (Qt)
This software provides an abstraction of the used apt repositories.
It allows you to easily manage your distribution and independent software
Bug#1071055: nmu: gauche-gl_0.6-4
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu nmu gauche-gl_0.6-4 . ANY . unstable . -m "Rebuild against libgauche-0.98-0." not a transition since the affected packages are in sid only Andreas
Bug#1071042: nmu: pytorch-cluster_1.6.3-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu nmu pytorch-cluster_1.6.3-1 . ANY . unstable . -m "Rebuild against pytorch 2.1" python3-torch-cluster currently has an unsatisfiable dependency on libtorch2.0 Andreas
Bug#1069641: right versions
On Mon, 22 Apr 2024 09:31:00 +0200 Alexandre Rossi wrote: Hi, With the right versions, sorry for the noise. nmu uwsgi-plugin-php_0.0.15 . ANY . unstable . -m "rebuild against new uwsgi.h" nmu uwsgi-plugin-luajit_0.0.8 . ANY . unstable . -m "rebuild against new uwsgi.h" nmu uwsgi-plugin-mongo_0.0.9 . ANY . unstable . -m "rebuild against new uwsgi.h" binNMUs requests need the source version, not the binary package version and no +b# suffix (it's possible the request a specific binNMU version number, but the default (next number) is fine here) Andreas
Bug#1065013: nvidia-graphics-drivers 470.239.06-1 flagged for acceptance
On 05/05/2024 20.52, Adam D Barratt wrote: Package: nvidia-graphics-drivers Version: 470.239.06-1 Explanation: upstream security fixes [CVE-2022-42265 CVE-2024-0074 CVE-2024-0078] Can we push these packages to bullseye-updates? The kernel change that recently caused problems for the nvidia modules in bookworm has now reached bullseye, too: #1070726, but the new upstream already sitting in bullseye-pu is sufficient to fix that. Therefore I'd recommend to push these packages to bullseye-updates: nvidia-graphics-drivers | 470.239.06-1 nvidia-settings | 470.239.06-1 nvidia-graphics-drivers-tesla-470 | 470.239.06-1~deb11u1 (tha would imply that temporarily the version of nvidia-graphics-drivers-tesla-470 in bullseye-updates is higher than the one in bookworm-updates) Andreas
Bug#1067106: bullseye-pu: package nvidia-settings/470.239.06-1
Hi Adam, while accepting the nvidia stack yesterday (many thanks for that!) you missed to tag etc. this bug, while the package was accepted (perhaps attributed to a different bug?). Andreas
Bug#1070466: bookworm-pu: package dm-writeboost/2.2.17-0.2~deb12u1
Package: release.debian.org Severity: normal Tags: bookworm User: release.debian@packages.debian.org Usertags: pu [ Reason ] A change from Linux v6.9-rc1 got backported to v6.1.83 and breaks building the dm-writeboost module (dm_io() got an extra parameter). I'd like to update dm-writeboost to a new upstream release, the only functional change is that fix (patch by me), everything else is documentation and metadata updates. On the Debian side there are some autopkgtest and metadata improvements. I'd prefer getting the full package from sid instead of just cherry-picking the fix. [ Impact ] The module cannot be built for the kernel in bookworm-security (or any future kernels in bookworm). [ Tests ] pkg-autopkgtest-dkms takes care of that ;-) [ Risks ] Low. [ 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 ] dm-writeboost (2.2.17-0.2~deb12u1) bookworm; urgency=medium * Non-maintainer upload. * Rebuild for bookworm. -- Andreas Beckmann Sun, 05 May 2024 20:42:46 +0200 dm-writeboost (2.2.17-0.2) unstable; urgency=medium * Non-maintainer upload. * Fix misspelled autopkgtest dependency. -- Andreas Beckmann Sun, 05 May 2024 04:21:59 +0200 dm-writeboost (2.2.17-0.1) unstable; urgency=medium [ Andreas Beckmann ] * Non-maintainer upload. * New upstream release [May 2024]. (Closes: #1069878) * Update upstream metadata. * dkms.conf: Set BUILD_EXCLUSIVE_KERNEL_MIN="3.9". * Fix autopkgtest dependencies. (Closes: #1069600) [ Andrea Righi ] * Skip I/O-intensive autopkgtest on small systems (LP: #2012947) -- Andreas Beckmann Sat, 04 May 2024 09:21:27 +0200 [ Other info ] This is a rebuild of the package from sid with no further changes. Andreas diff --git a/ChangeLog b/ChangeLog index e6f0c3c..53bcd7b 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,9 @@ +2024-05-01 Akira Hayakawa + + * v2.2.17 + * Fix build error with 6.9 kernel and backports + * Improve dkms.conf + 2023-02-11 Akira Hayakawa * v2.2.16 diff --git a/Makefile b/Makefile index 581d373..aa6b6ea 100644 --- a/Makefile +++ b/Makefile @@ -1,4 +1,4 @@ -MODULE_VERSION ?= 2.2.15 +MODULE_VERSION ?= 2.2.17 DKMS_DIR := /usr/src/dm-writeboost-$(MODULE_VERSION) DKMS_KEY := -m dm-writeboost -v $(MODULE_VERSION) diff --git a/README.md b/README.md index f5d280d..ddd1f88 100644 --- a/README.md +++ b/README.md @@ -1,8 +1,5 @@ # dm-writeboost -[](https://github.com/akiradeveloper/dm-writeboost) -[](https://paypal.me/akiradeveloper) - Log-structured Caching for Linux ## Overview @@ -42,15 +39,11 @@ As a further extension, dm-writeboost supports read-caching which also writes da ## Distribution Packages - [Debian](https://packages.debian.org/search?keywords=dm-writeboost-dkms) - [Ubuntu](https://packages.ubuntu.com/search?keywords=dm-writeboost-dkms) -- [CentOS/Fedora](https://copr.fedorainfracloud.org/coprs/khara/dm-writeboost/) -- [Arch](https://aur.archlinux.org/packages/dm-writeboost/) -- Momonga ## Related Projects * https://github.com/akiradeveloper/dm-writeboost-tools: Tools to help users analyze the state of the cache device * https://gitlab.com/onlyjob/writeboost: A management tool including init script * https://github.com/akiradeveloper/device-mapper-tests: Testing framework written in Rust -* https://github.com/kazuhisya/dm-writeboost-rpm: Providing RPM packages ## Related works * Y. Hu and Q. Yang -- DCD Disk Caching Disk: A New Approach for Boosting I/O Performance (1995) @@ -65,7 +58,7 @@ Awarded by Japanese OSS Encouragement Award. Thanks! ## License ``` -Copyright (C) 2012-2023 Akira Hayakawa +Copyright (C) 2012-2024 Akira Hayakawa This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by diff --git a/debian/changelog b/debian/changelog index b27c491..5fa74b3 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,31 @@ +dm-writeboost (2.2.17-0.2~deb12u1) bookworm; urgency=medium + + * Non-maintainer upload. + * Rebuild for bookworm. + + -- Andreas Beckmann Sun, 05 May 2024 20:42:46 +0200 + +dm-writeboost (2.2.17-0.2) unstable; urgency=medium + + * Non-maintainer upload. + * Fix misspelled autopkgtest dependency. + + -- Andreas Beckmann Sun, 05 May 2024 04:21:59 +0200 + +dm-writeboost (2.2.17-0.1) unstable; urgency=medium + + [ Andreas Beckmann ] + * Non-maintainer upload. + * New upstream release [May 2024]. (Closes: #1069878) + * Update upstream metadata. + * dkms.conf: Set BUILD_EXCLUSIVE_KERNEL_MIN="3.9". + * Fix autopkgtest dependencies. (Closes: #1069600) + + [ Andrea Righi ] + * Skip I/O-i
please clear extra-depends for armnn
src:armnn is stuck on i386,mips64el,ppc64el: https://buildd.debian.org/status/package.php?p=armnn There is an unsatisfiable Extra-Depends: libarm-compute-dev (>= 23.08+dfsg-3.1) while the package has restricted that B-D to the three architectures where the package exists: amd64, armhf, arm64 Please clear the wrong Extra-Depends. andreas
Bug#1067821: bookworm-pu: package nvidia-graphics-drivers/535.161.08-2~deb12u1
On 28/04/2024 22.39, Adam D. Barratt wrote: On Sun, 2024-04-28 at 13:43 +0200, Andreas Beckmann wrote: Please reject nvidia-graphics-drivers/535.161.08-1~deb12u1, nvidia- driver-full is uninstallable on ppc64el (but that was hidden by the other t64 transition blockers). Done, thanks for letting us know. nvidia-graphics-drivers (and the remainder of the 535 nvidia driver stack) has migrated to testing, so I've uploaded 535.161.08-2~deb12u1 and now the 535 stack should be ready for inclusion in the next bookworm point release. Andreas
Bug#1070271: nmu: 64-bit time_t rebuilds for experimental
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu The package in sid had a renaming t64 transition, but experimental already has a different SOVERSION, so only a binNMU is needed. nmu openmm_8.1.0+dfsg-2 . ANY . experimental . -m "Rebuild for time_t" nmu opensubdiv_3.6.0-1 . ANY . experimental . -m "Rebuild for time_t" nmu protobuf_3.25.2-1 . ANY . experimental . -m "Rebuild for time_t" nmu opencascade_7.7.1+dfsg1-1~exp2 . ANY . experimental . -m "Rebuild for time_t" Andreas
Bug#1070230: nmu: osmo-msc_1.9.0+dfsg1-2 osmo-sgsn_1.9.0+dfsg1-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu nmu osmo-msc_1.9.0+dfsg1-2 . ANY . unstable . -m "Rebuild against libosmo-sccp with t64 renaming reverted." nmu osmo-sgsn_1.9.0+dfsg1-3 . ANY . unstable . -m "Rebuild against libosmo-sccp with t64 renaming reverted." libosmo-sccp has been restricted to 64-bit architectures and therefore the t64 renaming has been reverted. The reverse dependencies (which have been removed from the 32-bit architectures) now need another binNMU. Andreas
Bug#1070040: bookworm-pu: package dm-writeboost/???
On 30/04/2024 07.40, Paul Gevers wrote: On 30-04-2024 12:43 a.m., Andreas Beckmann wrote: Testsuite: autopkgtest-pkg-dkms Right. I was talking about Testsuite-Triggers in the sources file generated by dpkg. Perhaps you can spot what's wrong with this setup s.t. it does not trigger as intended. I hope it's clear now. Thanks. That really explains why it's not working as I expected. At least for most packages. nvidia-graphics-drivers got lucky because there is also a (manual) test for building the module from the -source package with m-a which also has the linux-doc dependency. Related, for future reference, we also have the hint-testsuite-triggers [1] restriction in autopkgtest. I know, but using that for every package would be against the spirit of Testsuite: autopkgtest-foo ;-) Can you point me to the code that evaluates dpkg's Testsuite-Triggers to schedule these tests? Maybe it's possible to convert dpkg's Testsuite field to a (hardcoded) list of additional triggers ... Andreas
Bug#1070040: bookworm-pu: package dm-writeboost/???
On 29/04/2024 19.49, Paul Gevers wrote: As I hinted at in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069600#25, once there's an *test* dependency relation with linux, this will be tested. There should be a test dependency on linux-doc, but unfortunately I cannot find any record that the uploads of src:linux to sid or bookworm-pu triggered a test for src:dm-writeboost. Nor any trace of the regression this should have caused. But I could be looking at the wrong places. All *-dkms packages in bookworm (and trixie) do have Testsuite: autopkgtest-pkg-dkms and with autodep8 >= 0.26 (bookworm has 0.28) this should generate for src:dm-writeboost: Tests: test-dm-writeboost.sh Restrictions: needs-root, isolation-machine Depends: dm-writeboost-dkms, linux-image-generic, linux-header-generic, stress-ng, dmsetup, sudo, Test-Command: /usr/lib/dkms/dkms-autopkgtest Restrictions: needs-root, breaks-testbed, allow-stderr, superficial, Depends: dkms, openssl, linux-doc, Features: test-name=dkms-autopkgtest (The dependencies for the first test contain unreleased changes that will try to fix the isolation-machine test, so you might see fewer deps on the package currently in the archive.) (The dependencies for the second test intentionally exclude dm-writeboost-dkms because we first need to disable dkms autoinstall before installing *-dkms (otherwise we could only get a non-verbose package installation failure). Then we can run the module build step by step and with improved error reporting including dumping make.log on failure.) I chose linux-doc because * it is a real package built from src:linux * it does have an unversioned name * it is available on all architectures * it is available on all releases since (old)+stable for more 'old' releases than I could remember or lookup easily ;-) Perhaps you can spot what's wrong with this setup s.t. it does not trigger as intended. Andreas
Bug#1070040: bookworm-pu: package dm-writeboost/???
Package: release.debian.org Severity: normal Tags: bookworm User: release.debian@packages.debian.org Usertags: pu Control: block 1069878 with -1 Control: affects -1 + src:dm-writeboost Hi, the 6.1.85-1 kernel in bookworm-pu causes module build failures for dm-writeboost-dkms (#1069878) and rapiddisk-dkms (#1069945). While these are not fixed in sid, yet, I wanted to make you aware of them to avoid repeating the debacle we had with nvidia-kernel-dkms in the last point release. These failures could show up as autopkgtest failures in bookworm-pu. Are they flagged somewhere in your tooling s.t. they don't go unnoticed? All other dkms modules from bookworm built fine (tested on amd64 only, two days ago) with the updated linux-headers-* from bookworm-pu. Andreas
Bug#1067821: bookworm-pu: package nvidia-graphics-drivers/535.161.08-2~deb12u1
Control: retitle -1 bookworm-pu: package
nvidia-graphics-drivers/535.161.08-2~deb12u1
On 29/03/2024 19.40, Adam D. Barratt wrote:
On Thu, 2024-03-28 at 18:40 +0100, Andreas Beckmann wrote:
The whole nvidia stack has now been uploaded,
src:nvidia-graphics-drivers is sitting in NEW.
It's now in stable-new.
Please reject nvidia-graphics-drivers/535.161.08-1~deb12u1, nvidia-
driver-full is uninstallable on ppc64el (but that was hidden by the
other t64 transition blockers).
We have a bit of an issue in terms of accepting / shipping the 535
bookworm stack, however. The upload of 535 to unstable is blocked from
Looks like there is now some progress and if 535.161.08-2 (just
uploaded) migrates to testing, we can revisit this pu stack.
Incremental debdiff 535.161.08-1..535.161.08-2 attached.
Andreas
diff --git a/debian/changelog b/debian/changelog
index 7e6f2e315..cf2d8c680 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+nvidia-graphics-drivers (535.161.08-2) unstable; urgency=medium
+
+ * nvidia-driver-full: libnvidia-fbc1 and libnvidia-rtcore are not available
+on ppc64el.
+ * Add autopkgtest testing the installation of the full driver suite.
+
+ -- Andreas Beckmann Sun, 28 Apr 2024 13:28:15 +0200
+
nvidia-graphics-drivers (535.161.08-1) unstable; urgency=medium
* New upstream Tesla branch release 535.161.08 (2024-03-18).
diff --git a/debian/control b/debian/control
index c01198f98..538524ed7 100644
--- a/debian/control
+++ b/debian/control
@@ -80,10 +80,10 @@ Depends:
lib${nvidia}-encode1 (= ${binary:Version}),
${nvidia}-vulkan-icd (= ${binary:Version}),
lib${nvidia}-allocator1 (= ${binary:Version}),
- lib${nvidia}-rtcore (= ${binary:Version}),
+ lib${nvidia}-rtcore (= ${binary:Version}) [amd64 ${arch:arm64}],
${nvidia}-smi (= ${binary:Version}),
lib${nvidia-if-variant}cudadebugger1 (= ${binary:Version}),
- lib${nvidia}-fbc1 (= ${binary:Version}),
+ lib${nvidia}-fbc1 (= ${binary:Version}) [amd64 ${arch:arm64}],
lib${nvidia-if-variant}nvoptix1 (= ${binary:Version}) [amd64 ${arch:arm64}],
lib${nvidia}-opticalflow1 (= ${binary:Version}),
lib${nvidia}-ngx1 (= ${binary:Version}) [amd64],
diff --git a/debian/control.in b/debian/control.in
index 9c19a6c02..bc9f61dcd 100644
--- a/debian/control.in
+++ b/debian/control.in
@@ -79,10 +79,10 @@ Depends:
lib${nvidia}-encode1 (= ${binary:Version}),
${nvidia}-vulkan-icd (= ${binary:Version}),
lib${nvidia}-allocator1 (= ${binary:Version}),
- lib${nvidia}-rtcore (= ${binary:Version}),
+ lib${nvidia}-rtcore (= ${binary:Version}) [amd64 ${arch:arm64}],
${nvidia}-smi (= ${binary:Version}),
lib${nvidia-if-variant}cudadebugger1 (= ${binary:Version}),
- lib${nvidia}-fbc1 (= ${binary:Version}),
+ lib${nvidia}-fbc1 (= ${binary:Version}) [amd64 ${arch:arm64}],
lib${nvidia-if-variant}nvoptix1 (= ${binary:Version}) [amd64 ${arch:arm64}],
lib${nvidia}-opticalflow1 (= ${binary:Version}),
lib${nvidia}-ngx1 (= ${binary:Version}) [amd64],
diff --git a/debian/control.md5sum b/debian/control.md5sum
index 361efa496..b9e101228 100644
--- a/debian/control.md5sum
+++ b/debian/control.md5sum
@@ -1,5 +1,5 @@
-bc10d759d2eb2349dc7e680acf66292a debian/control
-c7413097130730ca439b199809dd468c debian/control.in
+2157da7b2be9063b142d96b9c5fdb963 debian/control
+0bfa7c4c3f1e01a3629ab367ce3d343c debian/control.in
8489c83cfe0171c9de6d052c01a6d19b debian/gen-control.pl
f874047700ddfc1543f70d430f0f8110 debian/rules
7f525d302e0e76e1de1f4e6cce0efbe8 debian/rules.defs
diff --git a/debian/tests/control b/debian/tests/control
index a53e52825..e83896aef 100644
--- a/debian/tests/control
+++ b/debian/tests/control
@@ -18,3 +18,12 @@ Depends:
nvidia-detect,
Restrictions:
superficial,
+
+Test-Command: true
+Features: test-name=full-install
+Architecture: amd64 arm64 ppc64el
+Depends:
+ nvidia-driver-full,
+ linux-headers-generic,
+Restrictions:
+ superficial,
diff --git a/debian/tests/control.in b/debian/tests/control.in
index c8184ac22..d771e7694 100644
--- a/debian/tests/control.in
+++ b/debian/tests/control.in
@@ -18,3 +18,12 @@ Depends:
nvidia-detect,
Restrictions:
superficial,
+
+Test-Command: true
+Features: test-name=full-install
+Architecture: #AUTOPKGTEST_ARCH_LIST#
+Depends:
+ #NVIDIA#-driver-full,
+ linux-headers-generic,
+Restrictions:
+ superficial,
Bug#1069880: bullseye-pu: package cpu/1.4.3-14~deb11u1
Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
Control: block 1067439 with -1
Control: affects -1 + src:cpu
[ Reason ]
The last QA upload four years ago fixed a FTBFS (multiple definitions of
a global variable) by replacing that variable with an extern declaration
and zero definitions. This didn't result in a linker error (missing
symbol) because it happens in a plugin library and thus is only detected
at runtime when the plugin gets loaded (i.e. always).
So let's ship the plugin with *one* definition of the global variable
;-)
[ Impact ]
cpu stays unusable, but nobody noticed that for the last 4 years and two
stable releases ...
[ Tests ]
Added a smoketest autopkgtest that detects the current failure.
[ Risks ]
We can't make the current situation much worse ;-)
[ 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
[x] the issue is verified as fixed in bookworm-pu
[ Changes ]
* Actually provide a definition of globalLdap. (Closes: #1067439)
* Add smoke test.
[ Other info ]
n/a
Andreas
diff --git a/debian/changelog b/debian/changelog
index ec0f291..5487744 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,25 @@
+cpu (1.4.3-14~deb11u1) bullseye; urgency=medium
+
+ * QA upload.
+ * Rebuild for bullseye.
+
+ -- Andreas Beckmann Fri, 26 Apr 2024 11:52:39 +0200
+
+cpu (1.4.3-14~deb12u1) bookworm; urgency=medium
+
+ * QA upload.
+ * Rebuild for bookworm.
+
+ -- Andreas Beckmann Mon, 25 Mar 2024 21:37:56 +0100
+
+cpu (1.4.3-14) unstable; urgency=medium
+
+ * QA upload.
+ * Actually provide a definition of globalLdap. (Closes: #1067439)
+ * Add smoke test.
+
+ -- Andreas Beckmann Sat, 23 Mar 2024 14:39:06 +0100
+
cpu (1.4.3-13) unstable; urgency=medium
* QA upload.
diff --git a/debian/gbp.conf b/debian/gbp.conf
new file mode 100644
index 000..9048820
--- /dev/null
+++ b/debian/gbp.conf
@@ -0,0 +1,2 @@
+[DEFAULT]
+debian-branch = main
diff --git a/debian/patches/14_use-extern.patch
b/debian/patches/14_use-extern.patch
index 774b581..26b0b19 100644
--- a/debian/patches/14_use-extern.patch
+++ b/debian/patches/14_use-extern.patch
@@ -1,10 +1,11 @@
Description: Fix ftbfs with GCC-10
Bug-Debian: https://bugs.debian.org/957106
+Bug-Debian: https://bugs.debian.org/1067439
---
cpu-1.4.3.orig/src/include/plugins/ldap/ldap.h
-+++ cpu-1.4.3/src/include/plugins/ldap/ldap.h
+--- a/src/include/plugins/ldap/ldap.h
b/src/include/plugins/ldap/ldap.h
@@ -106,7 +106,7 @@ typedef struct CPU_ldap {
Parser * parse;
} CPU_ldap;
@@ -14,3 +15,14 @@ Bug-Debian: https://bugs.debian.org/957106
int parseCommand(int argc, char *argv[]);
void printHelp(int op);
+--- a/src/plugins/ldap/ldap.c
b/src/plugins/ldap/ldap.c
+@@ -26,6 +26,8 @@
+ #include
+ #include "plugins/ldap/ldap.h"
+
++CPU_ldap * globalLdap;
++
+ int verbose;
+ int operation;
+
diff --git a/debian/tests/control b/debian/tests/control
new file mode 100644
index 000..7633658
--- /dev/null
+++ b/debian/tests/control
@@ -0,0 +1,8 @@
+Test-Command: /usr/sbin/cpu || /usr/sbin/cpu 2>&1 | grep ^usage:
+Features: test-name=smoketest
+Depends:
+ cpu,
+Restrictions:
+ superficial,
+ needs-root,
+ allow-stderr,
Bug#1065053: bullseye-pu: package nvidia-graphics-drivers-tesla-470/470.239.06-1~deb11u1
On 24/04/2024 23.15, Jonathan Wiltshire wrote: Is this apparent duplication correct? Sorry not to have spotted it before. Yes, that's exactly how I want it. The history of n-g-d as part of n-g-d-tesla-470. The changelog entry is duplicated because of the CVE list, otherwise it would have been a simple "Rebuild is Tesla 470 driver". Fortunately this package duplication (regular and tesla driver of the same version in one release) has been solved from bookworm (-pu(-new)) onwards. Andreas
Bug#1069297: bullseye-pu: package reportbug/7.10.3+deb11u2
Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: Reportbug Maintainers
Control: affects -1 + src:reportbug
[ Reason ]
After the release of bookworm, we should rotate the release codenames in
reportbug/bullseye again to keep reportbug/bullseye useful. Fixed in
sid/bookworm via #1034260.
[ Impact ]
Requires manual error prone adjustments if templates for e.g. some
release.debian.org bug classes are not available.
[ Tests ]
This bug report. :-)
[ Risks ]
low, only data update
[ 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 ]
+reportbug (7.10.3+deb11u2) bullseye; urgency=medium
+
+ * Rotate suite names after the bookworm release.
+
+ -- Andreas Beckmann Fri, 19 Apr 2024 15:45:33 +0200
[ Other info ]
n/a
Andreas
diff -Nru reportbug-7.10.3+deb11u1/debian/changelog
reportbug-7.10.3+deb11u2/debian/changelog
--- reportbug-7.10.3+deb11u1/debian/changelog 2021-09-06 17:35:39.0
+0200
+++ reportbug-7.10.3+deb11u2/debian/changelog 2024-04-19 15:45:33.0
+0200
@@ -1,3 +1,9 @@
+reportbug (7.10.3+deb11u2) bullseye; urgency=medium
+
+ * Rotate suite names after the bookworm release.
+
+ -- Andreas Beckmann Fri, 19 Apr 2024 15:45:33 +0200
+
reportbug (7.10.3+deb11u1) bullseye; urgency=medium
[ Thomas Goirand ]
diff -Nru reportbug-7.10.3+deb11u1/reportbug/__init__.py
reportbug-7.10.3+deb11u2/reportbug/__init__.py
--- reportbug-7.10.3+deb11u1/reportbug/__init__.py 2021-09-06
17:35:39.0 +0200
+++ reportbug-7.10.3+deb11u2/reportbug/__init__.py 2024-04-19
15:45:33.0 +0200
@@ -25,7 +25,7 @@
__all__ = ['bugreport', 'utils', 'urlutils', 'checkbuildd', 'checkversions',
'debbugs', 'exceptions', 'submit', 'tempfile', 'mailer']
-VERSION_NUMBER = "7.10.3+deb11u1"
+VERSION_NUMBER = "7.10.3+deb11u2"
VERSION = "reportbug " + VERSION_NUMBER
COPYRIGHT = VERSION + '\nCopyright (C) 1999-2008 Chris Lawrence
' + \
diff -Nru reportbug-7.10.3+deb11u1/reportbug/utils.py
reportbug-7.10.3+deb11u2/reportbug/utils.py
--- reportbug-7.10.3+deb11u1/reportbug/utils.py 2021-09-06 17:35:39.0
+0200
+++ reportbug-7.10.3+deb11u2/reportbug/utils.py 2024-04-19 15:45:33.0
+0200
@@ -95,13 +95,14 @@
'/usr/man', '/usr/doc', '/usr/bin']
# A map between codenames and suites
-CODENAME2SUITE = {'wheezy': 'oldoldoldoldstable',
- 'jessie': 'oldoldoldstable',
- 'stretch': 'oldoldstable',
- 'buster': 'oldstable',
- 'bullseye': 'stable',
- 'bookworm': 'testing',
- 'trixie': 'next-testing',
+CODENAME2SUITE = {'wheezy': 'oldoldoldoldoldstable',
+ 'jessie': 'oldoldoldoldstable',
+ 'stretch': 'oldoldoldstable',
+ 'buster': 'oldoldstable',
+ 'bullseye': 'oldstable',
+ 'bookworm': 'stable',
+ 'trixie': 'testing',
+ 'forky': 'next-testing',
'sid': 'unstable',
'experimental': 'experimental'}
SUITE2CODENAME = dict([(suite, codename) for codename, suite in
list(CODENAME2SUITE.items())])
Bug#1069295: bookworm-pu: package python-asdf/2.14.3-1+deb12u1
Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: Ole Streicher
Control: block 1054581 with -1
Control: affects -1 + src:python-asdf
[ Reason ]
python3-asdf has an internal dependency on asdf-unit-schemas which is
neither mapped to a package dependency nor does it exist in the archive.
This internal dependency (which only exists for backward compatibility
but is not required) has been patched out in sid, let's backport this.
[ Impact ]
Some usage paths of python3-asdf are failing because of unsatisfied
requirements.
[ Tests ]
python3 -c 'import pkg_resources; pkg_resources.require("asdf")'
does no longer fail with the updated package.
[ Risks ]
Low. Removes unneeded requirements.
[ 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 ]
+python-asdf (2.14.3-1+deb12u1) bookworm; urgency=medium
+
+ [ Andreas Beckmann ]
+ * Non-maintainer upload.
+ * Backport dependency fix from 3.0.0-2.
+
+ [ Ole Streicher ]
+ * Remove asdf-unit-schemas as a dependency (Closes: #1054581)
+
+ -- Andreas Beckmann Fri, 19 Apr 2024 14:06:08 +0200
[ Other info ]
n/a
Andreas
diff -Nru python-asdf-2.14.3/debian/changelog
python-asdf-2.14.3/debian/changelog
--- python-asdf-2.14.3/debian/changelog 2022-12-20 11:26:17.0 +0100
+++ python-asdf-2.14.3/debian/changelog 2024-04-19 14:06:08.0 +0200
@@ -1,3 +1,14 @@
+python-asdf (2.14.3-1+deb12u1) bookworm; urgency=medium
+
+ [ Andreas Beckmann ]
+ * Non-maintainer upload.
+ * Backport dependency fix from 3.0.0-2.
+
+ [ Ole Streicher ]
+ * Remove asdf-unit-schemas as a dependency (Closes: #1054581)
+
+ -- Andreas Beckmann Fri, 19 Apr 2024 14:06:08 +0200
+
python-asdf (2.14.3-1) unstable; urgency=medium
* New upstream version 2.14.3
diff -Nru
python-asdf-2.14.3/debian/patches/Remove-asdf-unit-schemas-as-a-dependency.patch
python-asdf-2.14.3/debian/patches/Remove-asdf-unit-schemas-as-a-dependency.patch
---
python-asdf-2.14.3/debian/patches/Remove-asdf-unit-schemas-as-a-dependency.patch
1970-01-01 01:00:00.0 +0100
+++
python-asdf-2.14.3/debian/patches/Remove-asdf-unit-schemas-as-a-dependency.patch
2024-04-19 14:06:08.0 +0200
@@ -0,0 +1,22 @@
+From: Ole Streicher
+Date: Fri, 27 Oct 2023 09:12:53 +0200
+Subject: Remove asdf-unit-schemas as a dependency
+
+This dependency was only added for backward compatibility and is no
+strict requirement.
+
+Closes: #1054581
+---
+ pyproject.toml | 1 -
+ 1 file changed, 1 deletion(-)
+
+--- a/pyproject.toml
b/pyproject.toml
+@@ -18,7 +18,6 @@ classifiers = [
+ dependencies = [
+ 'asdf-standard >=1.0.1',
+ 'asdf-transform-schemas >=0.3.0',
+-'asdf-unit-schemas >= 0.1.0',
+ 'importlib_resources >=3; python_version <"3.9"',
+ 'importlib-metadata >=4.11.4',
+ 'jmespath >=0.6.2',
diff -Nru python-asdf-2.14.3/debian/patches/series
python-asdf-2.14.3/debian/patches/series
--- python-asdf-2.14.3/debian/patches/series2022-12-20 11:26:17.0
+0100
+++ python-asdf-2.14.3/debian/patches/series2024-04-19 14:06:08.0
+0200
@@ -6,3 +6,4 @@
Disable-fetching-of-latest-patch-in-test.patch
Remove-dependency-on-sphinx-asdf.patch
Ignore-Astropy-deprecation-warnings-in-tests.patch
+Remove-asdf-unit-schemas-as-a-dependency.patch
Bug#1069291: bookworm-pu: package comitup/1.38-2~deb12u1
Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: David Steele
Control: block 1041447 with -1
Control: tag -1 + src:comitup
[ Reason ]
On certain upgrade paths installation/upgrade will fail if a masked
service file from a previous installation is still present.
[ Impact ]
This is mostly triggered by QA tests.
[ Tests ]
Local piuparts tests of the affected upgrade path.
[ Risks ]
Low. Unmasking a not masked service is a no-op.
[ 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 ]
-comitup (1.38-1.1) unstable; urgency=medium
+comitup (1.38-2~deb12u1) bookworm; urgency=medium
* Non-maintainer upload.
- * No source change upload to rebuild with debhelper 13.10.
+ * Rebuild for bookworm.
- -- Michael Biebl Sat, 15 Oct 2022 11:57:26 +0200
+ -- Andreas Beckmann Fri, 19 Apr 2024 14:56:56 +0200
+
+comitup (1.38-2) unstable; urgency=medium
+
+ * Ensure service is unmasked in post install (Closes: #1041447).
+
+ -- David Steele Fri, 28 Jul 2023 17:12:44 -0400
There is also a new autopkgtest, but it is unrelated to this issue.
[ Other info ]
This is a rebuild of the package that has been in sid and testing for 5
months before it got superseded by a new upstream release.
Andreas
diff -Nru comitup-1.38/debian/changelog comitup-1.38/debian/changelog
--- comitup-1.38/debian/changelog 2022-10-15 11:57:26.0 +0200
+++ comitup-1.38/debian/changelog 2024-04-19 14:56:56.0 +0200
@@ -1,9 +1,15 @@
-comitup (1.38-1.1) unstable; urgency=medium
+comitup (1.38-2~deb12u1) bookworm; urgency=medium
* Non-maintainer upload.
- * No source change upload to rebuild with debhelper 13.10.
+ * Rebuild for bookworm.
- -- Michael Biebl Sat, 15 Oct 2022 11:57:26 +0200
+ -- Andreas Beckmann Fri, 19 Apr 2024 14:56:56 +0200
+
+comitup (1.38-2) unstable; urgency=medium
+
+ * Ensure service is unmasked in post install (Closes: #1041447).
+
+ -- David Steele Fri, 28 Jul 2023 17:12:44 -0400
comitup (1.38-1) unstable; urgency=medium
diff -Nru comitup-1.38/debian/comitup.postinst
comitup-1.38/debian/comitup.postinst
--- comitup-1.38/debian/comitup.postinst2022-07-08 04:51:57.0
+0200
+++ comitup-1.38/debian/comitup.postinst2023-07-28 21:02:12.0
+0200
@@ -12,6 +12,7 @@
rm -f /etc/NetworkManager/dnsmasq-shared.d/nm-dns-sabotage.conf
fi
+systemctl unmask comitup
systemctl enable comitup
python3 /usr/share/comitup/comitup/wificheck.py || true
diff -Nru comitup-1.38/debian/tests/control comitup-1.38/debian/tests/control
--- comitup-1.38/debian/tests/control 2022-07-08 04:51:57.0 +0200
+++ comitup-1.38/debian/tests/control 2023-07-28 03:54:33.0 +0200
@@ -1,4 +1,5 @@
Test-Command: py.test-3 test/test_config.py test/test_persist.py test/test_web*
+Features: test-name=pytest
Depends:
@,
@builddeps@,
@@ -8,3 +9,6 @@
python3-dev,
libdbus-glib-1-dev,
libdbus-1-dev
+
+Tests: fileloc
+Depends: @, bash
diff -Nru comitup-1.38/debian/tests/fileloc comitup-1.38/debian/tests/fileloc
--- comitup-1.38/debian/tests/fileloc 1970-01-01 01:00:00.0 +0100
+++ comitup-1.38/debian/tests/fileloc 2023-07-28 03:54:33.0 +0200
@@ -0,0 +1,20 @@
+#!/bin/bash
+
+declare -a Paths=("/etc/comitup.conf" \
+ "/etc/dbus-1/system.d/comitup-dbus.conf" \
+ "/lib/systemd/system/comitup.service" \
+ "/usr/share/comitup/comitup-cmd" \
+ "/usr/share/comitup/web/comitupweb.py"\
+ "/usr/sbin/comitup" \
+ "/var/lib/comitup" \
+ "/usr/share/comitup/comitup/comitup.py")
+
+retval=0
+for path in ${Paths[@]}; do
+if [ ! -e $path ]; then
+echo "Not found - $path"
+retval=1
+fi
+done
+
+exit $retval
Bug#1069286: bookworm-pu: package dcmtk/3.6.7-9~deb12u1
Package: release.debian.org Severity: normal Tags: bookworm User: release.debian@packages.debian.org Usertags: pu X-Debbugs-Cc: Andreas Tille [ Reason ] postrm purge may fail on removing an obsolete directory due to usage of rm -f without -r [ Impact ] Users need to manually clean up cruft in order to purge the package. [ Tests ] Local piuparts tests of the affetced upgrade path. [ Risks ] Low. Trivial fix. [ 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 ] +dcmtk (3.6.7-9~deb12u1) bookworm; urgency=medium + + * Team upload. + * Rebuild for bookworm. + + -- Andreas Beckmann Fri, 19 Apr 2024 13:06:33 +0200 + +dcmtk (3.6.7-9) unstable; urgency=medium + + * Team upload. + * Fix postrm +Closes: #1038776 + + -- Andreas Tille Thu, 22 Jun 2023 09:53:48 +0200 [ Other info ] This is a rebuild of the package from testing with no further changes. The fixed package has already been uploaded. Andreas diff --git a/debian/changelog b/debian/changelog index 07333ee..ef6b5c9 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,18 @@ +dcmtk (3.6.7-9~deb12u1) bookworm; urgency=medium + + * Team upload. + * Rebuild for bookworm. + + -- Andreas Beckmann Fri, 19 Apr 2024 13:06:33 +0200 + +dcmtk (3.6.7-9) unstable; urgency=medium + + * Team upload. + * Fix postrm +Closes: #1038776 + + -- Andreas Tille Thu, 22 Jun 2023 09:53:48 +0200 + dcmtk (3.6.7-8) unstable; urgency=medium * d/patches: Fix CVE-2022-43272. Closes: #1027165 diff --git a/debian/dcmtk.postrm b/debian/dcmtk.postrm index 98e717c..b8efc7e 100644 --- a/debian/dcmtk.postrm +++ b/debian/dcmtk.postrm @@ -15,7 +15,7 @@ if [ "$1" = "purge" ] ; then fi if [ -d /var/lib/dcmtk/db/STORESCP ]; then - rm -f /var/lib/dcmtk/db/STORESCP + rm -rf /var/lib/dcmtk/db/STORESCP fi fi
Bug#1069284: bookworm-pu: package libmail-dkim-perl/1.20230212-2~deb12u1
Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: gregor herrmann
Control: block 1040438 with -1
Control: affects -1 + src:libmail-dkim-perl
[ Reason ]
A missing dependency causes dkimproxy-verify to fail upon execution.
[ Impact ]
Requires manual installation of another package to make it usable.
[ Tests ]
- Extended autopkgtests to cover this case.
- Manual installation and testing of the fixed package in a minimal
bookworm chroot.
[ Risks ]
- Low, only adding a dependency.
[ 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 ]
+libmail-dkim-perl (1.20230212-2~deb12u1) bookworm; urgency=medium
+
+ * Non-maintainer upload.
+ * Rebuild for bookworm.
+
+ -- Andreas Beckmann Fri, 19 Apr 2024 11:50:51 +0200
+
+libmail-dkim-perl (1.20230212-2) unstable; urgency=medium
+
+ * Team upload.
+ * Add scripts to autopkgtest's syntax.t. Cf. #1040438.
+ * Add a runtime dependency on libgetopt-long-descriptive-perl.
+Thanks to Colin Watson for the bug report. (Closes: #1040438)
+
+ -- gregor herrmann Thu, 06 Jul 2023 17:38:48 +0200
[ Other info ]
This is a no-change rebuild of a package that has been in sid and
testing last July (before it got superseded by a newer upstream release).
Andreas
diff --git a/debian/changelog b/debian/changelog
index 5a8ba26..d5b9865 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,19 @@
+libmail-dkim-perl (1.20230212-2~deb12u1) bookworm; urgency=medium
+
+ * Non-maintainer upload.
+ * Rebuild for bookworm.
+
+ -- Andreas Beckmann Fri, 19 Apr 2024 11:50:51 +0200
+
+libmail-dkim-perl (1.20230212-2) unstable; urgency=medium
+
+ * Team upload.
+ * Add scripts to autopkgtest's syntax.t. Cf. #1040438.
+ * Add a runtime dependency on libgetopt-long-descriptive-perl.
+Thanks to Colin Watson for the bug report. (Closes: #1040438)
+
+ -- gregor herrmann Thu, 06 Jul 2023 17:38:48 +0200
+
libmail-dkim-perl (1.20230212-1) unstable; urgency=medium
* Team upload.
diff --git a/debian/control b/debian/control
index 8a61df6..b410f05 100644
--- a/debian/control
+++ b/debian/control
@@ -28,6 +28,7 @@ Depends: ${misc:Depends},
libcrypt-openssl-rsa-perl,
libdigest-sha-perl,
liberror-perl,
+ libgetopt-long-descriptive-perl,
libmail-authenticationresults-perl,
libmailtools-perl,
libnet-dns-perl
diff --git a/debian/tests/pkg-perl/syntax-extra
b/debian/tests/pkg-perl/syntax-extra
new file mode 100644
index 000..f0dd09f
--- /dev/null
+++ b/debian/tests/pkg-perl/syntax-extra
@@ -0,0 +1 @@
+usr/bin/dkimproxy-
Bug#1069281: bookworm-pu: package what-is-python/13+deb12u1
Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: Matthias Klose
Control: block 1034995 with -1
Control: affects -1 + src:what-is-python
[ Reason ]
A missing Breaks+Replaces relationship can cause a file conflict on
/usr/bin/pydoc on upgrades from bullseye to bookworm. #1034995
[ Impact ]
Users may need to manually remove an obsolete package to progress with
the upgrade.
[ Tests ]
Manually installed the resulting python-is-python3 package on a minimal
bookworm chroot with python-dev-is-python2 from bullseye installed.
[ Risks ]
Low. python*-is-* are leaf packages with no reverse dependencies.
[ 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
The B+R fix has been backported from unstable
[ Changes ]
+what-is-python (13+deb12u1) bookworm; urgency=medium
+
+ [ Andreas Beckmann ]
+ * Non-maintainer upload.
+ * Bump version to 11.2.
(specific to bookworm)
+ * Fix version mangling for NMU, stable or backports uploads, i.e. versions
+with a suffix starting with a non-digit ([.+~]).
(not yet in sid (not needed for maintainer uploads to sid), but proposed
(#1069278), mandatory for a version like 13+foo)
+
+ [ Matthias Klose ]
+ * python-is-python3: Add breaks/replaces to python-dev-is-python2.
+Closes: #1034995.
(backported from 14)
+
+ -- Andreas Beckmann Fri, 19 Apr 2024 10:19:38 +0200
$ debdiff python-is-python3_3.11.1-3_all.deb
python-is-python3_3.11.2-1+deb12u1_all.deb
File lists identical (after any substitutions)
Control files: lines which differ (wdiff format)
Breaks: python, {+python-dev-is-python2,+} python-dev-is-python3 (<< 3.11.1-2),
python-is-python2, python-is-python2-but-deprecated, python-minimal
Installed-Size: [-15-] {+16+}
Replaces: python, {+python-dev-is-python2,+} python-dev-is-python3 (<<
3.11.1-2), python-is-python2, python-is-python2-but-deprecated, python-minimal
Source: what-is-python [-(13)-] {+(13+deb12u1)+}
Version: [-3.11.1-3-] {+3.11.2-1+deb12u1+}
[ Other info ]
Bookworm has python3.11 3.11.2-6 (or soon 3.11.2-6+deb12u1).
So far what-is-python has generated binary packages versioned as
3.11.1-* or 3.11.4-*, therefore switching bookworm to 3.11.2-* is safe
and consistent with the python3.11 version in bookworm.
Andreas
diff -Nru what-is-python-13/debian/changelog
what-is-python-13+deb12u1/debian/changelog
--- what-is-python-13/debian/changelog 2023-01-08 08:19:39.0 +0100
+++ what-is-python-13+deb12u1/debian/changelog 2024-04-19 10:19:38.0
+0200
@@ -1,3 +1,17 @@
+what-is-python (13+deb12u1) bookworm; urgency=medium
+
+ [ Andreas Beckmann ]
+ * Non-maintainer upload.
+ * Bump version to 11.2.
+ * Fix version mangling for NMU, stable or backports uploads, i.e. versions
+with a suffix starting with a non-digit ([.+~]).
+
+ [ Matthias Klose ]
+ * python-is-python3: Add breaks/replaces to python-dev-is-python2.
+Closes: #1034995.
+
+ -- Andreas Beckmann Fri, 19 Apr 2024 10:19:38 +0200
+
what-is-python (13) unstable; urgency=medium
* Fix versioned breaks/replaces: Closes: #1027951.
diff -Nru what-is-python-13/debian/control
what-is-python-13+deb12u1/debian/control
--- what-is-python-13/debian/control2023-01-08 08:19:39.0 +0100
+++ what-is-python-13+deb12u1/debian/control2024-04-19 10:18:52.0
+0200
@@ -11,9 +11,9 @@
Multi-Arch: allowed
Depends: ${misc:Depends}, python3
Breaks: python-is-python2, python-is-python2-but-deprecated, python,
python-minimal,
- python-dev-is-python3 (<< 3.11.1-2)
+ python-dev-is-python3 (<< 3.11.1-2), python-dev-is-python2
Replaces: python-is-python2, python-is-python2-but-deprecated, python,
python-minimal,
- python-dev-is-python3 (<< 3.11.1-2)
+ python-dev-is-python3 (<< 3.11.1-2), python-dev-is-python2
XB-Cnf-Ignore-Commands: python
Description: symlinks /usr/bin/python to python3
Starting with the Debian 11 (bullseye) and Ubuntu 20.04 LTS (focal)
diff -Nru what-is-python-13/debian/rules what-is-python-13+deb12u1/debian/rules
--- what-is-python-13/debian/rules 2023-01-03 10:17:21.0 +0100
+++ what-is-python-13+deb12u1/debian/rules 2024-04-19 10:19:38.0
+0200
@@ -1,7 +1,10 @@
#!/usr/bin/make -f
include /usr/share/dpkg/default.mk
-v3 := 3.11.1-$(shell expr $(DEB_VERSION) - 10)
+DEB_VERSION_BASE= $(firstword $(subst +, ,$(subst ~, ,$(subst .,
,$(DEB_VERSION)
+DEB_VERSION_SUFFIX = $(patsubst $(DEB_VERSION_BASE)%,%,$(DEB_VERSION))
+
+v3 := 3.11.2-$(shell expr $(DEB_VERSION_BASE) - 12)$(DEB_VERSION_SUFFIX)
%:
dh $@
Bug#1069274: bookworm-pu: package pdudaemon/0.0.8.58.g597052b-1+deb12u1
Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: Sjoerd Simons
Control: block 1060768 with -1
Control: affects -1 + src:pdudaemon
[ Reason ]
Lack of a python3-aiohttp dependency causes pdudaemon to emit a
traceback upon start. (#1060768)
[ Impact ]
User need to manually install an extra package to use pdudaemon.
[ Tests ]
Manual installation of the updated package in a minial bookworm chroot.
pdudaemon --help no longer fails.
[ Risks ]
Low. Only adding a dependency.
[ 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
dependency seems to get generated automatically by newer upstream
releases and/or toolchain
[ Changes ]
pdudaemon (0.0.8.58.g597052b-1+deb12u1) bookworm; urgency=medium
* Non-maintainer upload.
* Add dependency on python3-aiohttp. (Closes: #1060768)
-- Andreas Beckmann Fri, 19 Apr 2024 09:32:42 +0200
$ debdiff pdudaemon_0.0.8.58.g597052b-1_all.deb
pdudaemon_0.0.8.58.g597052b-1+deb12u1_all.deb
File lists identical (after any substitutions)
Control files: lines which differ (wdiff format)
Depends: {+python3-aiohttp,+} python3-hid, python3-paramiko, python3-pexpect,
python3-pyasn1, python3-pysnmp4, python3-requests, python3-serial,
python3-systemd, python3-usb, python3:any
Version: [-0.0.8.58.g597052b-1-] {+0.0.8.58.g597052b-1+deb12u1+}
[ Other info ]
I'll immediately upload the fixed package.
Andreas
diff --git a/debian/changelog b/debian/changelog
index 1ef3aa0..0f5605d 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+pdudaemon (0.0.8.58.g597052b-1+deb12u1) bookworm; urgency=medium
+
+ * Non-maintainer upload.
+ * Add dependency on python3-aiohttp. (Closes: #1060768)
+
+ -- Andreas Beckmann Fri, 19 Apr 2024 09:32:42 +0200
+
pdudaemon (0.0.8.58.g597052b-1) unstable; urgency=medium
* New upstream version 0.0.8.58.g597052b
diff --git a/debian/control b/debian/control
index ee3f5e6..bfd8f48 100644
--- a/debian/control
+++ b/debian/control
@@ -31,6 +31,7 @@ Vcs-Browser: https://github.com/pdudaemon/pkg-pdudaemon
Package: pdudaemon
Architecture: all
Depends: ${misc:Depends},
+ python3-aiohttp,
${python3:Depends}
Recommends: telnet, openssh-client
Description: daemon for controlling PDUs
diff --git a/debian/gbp.conf b/debian/gbp.conf
index 9692402..0f5e2b8 100644
--- a/debian/gbp.conf
+++ b/debian/gbp.conf
@@ -3,7 +3,7 @@
# Use upstream-vcs-tag to allow the full upstream history to be included
# Note that this does require having the upstream tag available in the
# repository
-debian-branch=debian/main
+debian-branch=debian/bookworm
upstream-branch=upstream/latest
#upstream-vcs-tag=%(version)s
pristine-tar=true
Bug#1069084: nmu: apt-move_4.2.27-6
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu nmu apt-move_4.2.27-6 . ANY . unstable . -m "Rebuild for 64-bit time_t." According to https://bugs.debian.org/1065069 the previous nmu may have picked up too old build dependencies and built with the wrong ABI on 32-bit t64 architectures. Andreas
Bug#1068719: RM: ruby-arel/9.0.0-2 -- RoQA; obsolete, integrated into ruby-activerecord, incompatible with ruby-activerecord 6.1.x
Package: release.debian.org Severity: normal Tags: bookworm User: release.debian@packages.debian.org Usertags: rm X-Debbugs-Cc: Georg Faerber Control: block -1 with 1068715 Please remove the obsolete ruby-arel from bookworm. The functionality is now integrated into ruby-activerecord and the separately packaged ruby-arel is incompatible with the ruby-activerecord version in bookworm, causing schleuder maintainer scripts to fail if installed. There is a superfluous build-dependency on ruby-arel in src:ruby-premailer-rails, dropping that is handled in pu request #1068715. pu request #1068717 tracks adding Breaks+Replaces against ruby-arel to ruby-activerecord to ensure removal of the obsolete and incompatible package on upgrades. Andreas
Bug#1068717: bookworm-pu: package rails/2:6.1.7.3+dfsg-2~deb12u1
Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: Georg Faerber
Control: block -1 with 1068715
[ Reason ]
The obsolete (but unfortunately still in bookworm present) ruby-arel is
not compatible with ruby-activerecord in bookworm (which now integrates
ruby-arel functionality), causing schleuder to fail in its maintainer
scripts during upgrades.
Let's add Breaks+Replaces to ruby-activerecord to ensure ruby-arel gets
removed on upgrades from bookworm. This may make ruby-arel uninstallable
in stable, so let's follow up with a RM request for that.
[ Impact ]
Failures on some upgrade paths of schleuder if the obsolete ruby-arel is
still installed.
[ Tests ]
Local piuparts tests upgrading schleuder with old ruby-arel installed
showed proper removal of ruby-arel and no more errors.
[ Risks ]
Uninstallability of the obsolete ruby-arel which should not have been in
bookworm at all.
[ 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 ]
debian/changelog | 16
debian/control | 2 ++
debian/gbp.conf | 2 +-
3 files changed, 19 insertions(+), 1 deletion(-)
[ Other info ]
This is a rebuild of a package that has been in sid and testing for a
long time (but is now superseded by further uploads with changes not
appropriate for stable).
Andreas
diff --git a/debian/changelog b/debian/changelog
index e0710e15..c3d33ee2 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,19 @@
+rails (2:6.1.7.3+dfsg-2~deb12u1) bookworm; urgency=medium
+
+ * Non-maintainer upload.
+ * Rebuild for bookworm.
+
+ -- Andreas Beckmann Tue, 09 Apr 2024 18:24:31 +0200
+
+rails (2:6.1.7.3+dfsg-2) unstable; urgency=medium
+
+ * debian/control:
+- Declare that ruby-activerecord breaks and replaces ruby-arel: it was
+ merged five years ago, is therefore obsolete and to be removed.
+ (Closes: #1038935)
+
+ -- Georg Faerber Sun, 25 Jun 2023 11:53:59 +
+
rails (2:6.1.7.3+dfsg-1) unstable; urgency=medium
* Team upload.
diff --git a/debian/control b/debian/control
index fc8d64d5..9e01f2b9 100644
--- a/debian/control
+++ b/debian/control
@@ -134,6 +134,7 @@ Depends: ruby:any (>= 1:2.5.0),
Breaks: ruby-activerecord-import (<< 1.0.5~),
ruby-activerecord-nulldb-adapter (<< 0.8.0~),
ruby-acts-as-taggable-on (<< 6.5~),
+ruby-arel,
ruby-delayed-job-active-record (<< 4.1.6-3~),
ruby-enumerize (<< 2.4.0~),
ruby-has-secure-token (<< 1.0.0-3~),
@@ -146,6 +147,7 @@ Description: object-relational mapper framework (part of
Rails)
a persistent domain model by mapping database tables to Ruby classes.
Strong conventions for associations, validations, aggregations,
migrations, and testing come baked-in.
+Replaces: ruby-arel,
XB-Ruby-Versions: ${ruby:Versions}
X-DhRuby-Root: activerecord/
diff --git a/debian/gbp.conf b/debian/gbp.conf
index 584b9683..1190046b 100644
--- a/debian/gbp.conf
+++ b/debian/gbp.conf
@@ -4,7 +4,7 @@ sign-tags = True
upstream-tag = upstream/%(version)s
upstream-branch = upstream
-debian-branch = master
+debian-branch = bookworm
[pq]
patch-numbers = False
Bug#1068715: bookworm-pu: package ruby-premailer-rails/1.10.3-4~deb12u1
Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: Georg Faerber
[ Reason ]
In order to get rid of the obsolete and incompatible ruby-arel,
ruby-premailer-rails has to drop its superfluous build dependency on it.
ruby-arel is nowadays integrated into ruby-actionmailer and the
incompatible ruby-arel version fortunately does not get used during
build.
[ Impact ]
Failures on some upgrade paths of schleuder if the obsolete ruby-arel is
still installed.
[ Tests ]
The package still builds ;-)
[ Risks ]
Low, dropping of a superfluous B-D could only cause a FTBFS and the
package would therefore be excluded from -pu.
[ 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 ]
debian/.gitattributes | 3 +++
debian/changelog | 15 +++
debian/control| 7 +++
3 files changed, 21 insertions(+), 4 deletions(-)
ruby-premailer-rails (1.10.3-4~deb12u1) bookworm; urgency=medium
* Non-maintainer upload.
* Rebuild for bookworm.
-- Andreas Beckmann Tue, 09 Apr 2024 16:56:10 +0200
ruby-premailer-rails (1.10.3-4) unstable; urgency=medium
* debian/control:
- Drop Build-Depends on ruby-arel, which is obsolete and part of rails
since five years. (Closes: #1039035)
-- Georg Faerber Sat, 24 Jun 2023 22:31:11 +
It also drops the version constraint on the ruby-actionmailer
(build-)dependency which has been satisfied since jessie at least.
[ Other info ]
This is a rebuild of a package that has been in sid and testing for a
long time (but is now superseded by a new upstream release).
Andreas
diff --git a/debian/.gitattributes b/debian/.gitattributes
new file mode 100644
index 000..74e43f3
--- /dev/null
+++ b/debian/.gitattributes
@@ -0,0 +1,3 @@
+.gitattributes export-ignore
+gbp.conf export-ignore
+salsa-ci.yml export-ignore
\ No newline at end of file
diff --git a/debian/changelog b/debian/changelog
index 0ed9fdc..5e9ead3 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,18 @@
+ruby-premailer-rails (1.10.3-4~deb12u1) bookworm; urgency=medium
+
+ * Non-maintainer upload.
+ * Rebuild for bookworm.
+
+ -- Andreas Beckmann Tue, 09 Apr 2024 16:56:10 +0200
+
+ruby-premailer-rails (1.10.3-4) unstable; urgency=medium
+
+ * debian/control:
+- Drop Build-Depends on ruby-arel, which is obsolete and part of rails
+ since five years. (Closes: #1039035)
+
+ -- Georg Faerber Sat, 24 Jun 2023 22:31:11 +
+
ruby-premailer-rails (1.10.3-3) unstable; urgency=medium
* Team upload
diff --git a/debian/control b/debian/control
index ece4ea5..9f756d7 100644
--- a/debian/control
+++ b/debian/control
@@ -1,19 +1,18 @@
Source: ruby-premailer-rails
Section: ruby
Priority: optional
-Maintainer: Debian Ruby Extras Maintainers
+Maintainer: Debian Ruby Team
Uploaders: Balasankar C
Build-Depends: debhelper-compat (= 12),
gem2deb,
rake,
- ruby-actionmailer (>= 2:3.0~),
+ ruby-actionmailer,
ruby-byebug,
ruby-coveralls,
ruby-premailer (>= 1.11.1~),
ruby-rspec,
ruby-simplecov,
ruby-rails,
- ruby-arel
Standards-Version: 4.5.0
Vcs-Git: https://salsa.debian.org/ruby-team/ruby-premailer-rails.git
Vcs-Browser: https://salsa.debian.org/ruby-team/ruby-premailer-rails
@@ -25,7 +24,7 @@ Package: ruby-premailer-rails
Architecture: all
XB-Ruby-Versions: ${ruby:Versions}
Depends: ruby | ruby-interpreter,
- ruby-actionmailer (>= 2:3.0~),
+ ruby-actionmailer,
ruby-premailer (>= 1.11.1~),
${misc:Depends},
${shlibs:Depends}
Bug#1068695: bookworm-pu: package json-smart/2.2-2+deb12u1
Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: Bastien Roucariès
Control: affects -1 + src:json-smart
Control: block 1039985 with -1
Control: block 1033474 with -1
[ Reason ]
Two CVEs were fixed in buster-lts, but not yet in bullseye or later,
causing version skew on upgrades:
json-smart | 2.2-1 | stretch | source
json-smart | 2.2-2 | buster | source
json-smart | 2.2-2 | bullseye| source
json-smart | 2.2-2 | bookworm| source
json-smart | 2.2-2 | trixie | source
json-smart | 2.2-2 | sid | source
json-smart | 2.2-2+deb10u1 | buster-security | source
[ Impact ]
Unfixed CVEs.
Versions going backward and confusing QA tools.
[ Tests ]
Build-time testsuite contains a new test.
[ Risks ]
Fixed version in buster-lts for one year already.
[ 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
NMU in DELAYED
[ Changes ]
debian/changelog | 33 +
debian/control | 4 +-
.../patches/0004-CVE-2021-31684-Fix-indexOf.patch | 27
...70-stack-overflow-due-to-excessive-recurs.patch | 156 +
debian/patches/01-bundle-dependencies.patch| 15 +-
debian/patches/02-ignore-failing-tests.patch | 16 ++-
debian/patches/series | 2 +
7 files changed, 244 insertions(+), 9 deletions(-)
json-smart (2.2-2+deb12u1) bookworm; urgency=medium
* Non-maintainer upload.
* Rebuild for bookworm. (Closes: #1039985)
-- Andreas Beckmann Tue, 09 Apr 2024 10:01:36 +0200
json-smart (2.2-2+deb11u1) bullseye; urgency=medium
* Non-maintainer upload.
* Update Vcs-* URLs to point to salsa.debian.org.
* Rebuild for bullseye. (Closes: #1039985)
-- Andreas Beckmann Tue, 09 Apr 2024 09:36:58 +0200
json-smart (2.2-2+deb10u1) buster-security; urgency=high
* Non-maintainer upload by the LTS team.
* CVE-2023-1370: stack overflow due to excessive recursion
When reaching a ‘[‘ or ‘{‘ character in the JSON input, the code
parses an array or an object respectively. It was discovered that the
code does not have any limit to the nesting of such arrays or
objects. Since the parsing of nested arrays and objects is done
recursively, nesting too many of them can cause a stack exhaustion
(stack overflow) and crash the software. (Closes: #1033474)
* CVE-2021-31684: Fix indexOf
A vulnerability was discovered in the indexOf function of
JSONParserByteArray in JSON Smart versions 1.3 and 2.4
which causes a denial of service (DOS)
via a crafted web request.
-- Bastien Roucariès Wed, 29 Mar 2023 22:21:33 +
[ Other info ]
n/a
Andreas
diff --git a/debian/changelog b/debian/changelog
index 70116d2..877457c 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,36 @@
+json-smart (2.2-2+deb12u1) bookworm; urgency=medium
+
+ * Non-maintainer upload.
+ * Rebuild for bookworm. (Closes: #1039985)
+
+ -- Andreas Beckmann Tue, 09 Apr 2024 10:01:36 +0200
+
+json-smart (2.2-2+deb11u1) bullseye; urgency=medium
+
+ * Non-maintainer upload.
+ * Update Vcs-* URLs to point to salsa.debian.org.
+ * Rebuild for bullseye. (Closes: #1039985)
+
+ -- Andreas Beckmann Tue, 09 Apr 2024 09:36:58 +0200
+
+json-smart (2.2-2+deb10u1) buster-security; urgency=high
+
+ * Non-maintainer upload by the LTS team.
+ * CVE-2023-1370: stack overflow due to excessive recursion
+When reaching a ‘[‘ or ‘{‘ character in the JSON input, the code
+parses an array or an object respectively. It was discovered that the
+code does not have any limit to the nesting of such arrays or
+objects. Since the parsing of nested arrays and objects is done
+recursively, nesting too many of them can cause a stack exhaustion
+(stack overflow) and crash the software. (Closes: #1033474)
+ * CVE-2021-31684: Fix indexOf
+A vulnerability was discovered in the indexOf function of
+JSONParserByteArray in JSON Smart versions 1.3 and 2.4
+which causes a denial of service (DOS)
+via a crafted web request.
+
+ -- Bastien Roucariès Wed, 29 Mar 2023 22:21:33 +
+
json-smart (2.2-2) unstable; urgency=medium
* Team upload.
diff --git a/debian/control b/debian/control
index 6488a01..deb7c40 100644
--- a/debian/control
+++ b/debian/control
@@ -6,8 +6,8 @@ Uploaders: Emmanuel Bourg
Build-Depends: debhelper (>= 10), default-jdk, maven-debian-helper (>= 1.5)
Build-Depends-Indep: libmaven-bundle-plugin-java, junit
Standards-Version: 4.1.1
-Vcs-Git: https://anonscm.debian.org/git/pkg-java/json-smart.git
-Vcs-Browser: https://anonscm.debian.org/cgit/pkg-java/json-smart.git
+Vcs-Browser:
Bug#1068694: bullseye-pu: package json-smart/2.2-2+deb11u1
Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: Bastien Roucariès
Control: affects -1 + src:json-smart
Control: block 1039985 with -1
Control: block 1033474 with -1
[ Reason ]
Two CVEs were fixed in buster-lts, but not yet in bullseye or later,
causing version skew on upgrades:
json-smart | 2.2-1 | stretch | source
json-smart | 2.2-2 | buster | source
json-smart | 2.2-2 | bullseye| source
json-smart | 2.2-2 | bookworm| source
json-smart | 2.2-2 | trixie | source
json-smart | 2.2-2 | sid | source
json-smart | 2.2-2+deb10u1 | buster-security | source
[ Impact ]
Unfixed CVEs.
Versions going backward and confusing QA tools.
[ Tests ]
Build-time testsuite contains a new test.
[ Risks ]
Fixed version in buster-lts for one year already.
[ 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
NMU in DELAYED
[ Changes ]
debian/changelog | 26
debian/control | 4 +-
.../patches/0004-CVE-2021-31684-Fix-indexOf.patch | 27
...70-stack-overflow-due-to-excessive-recurs.patch | 156 +
debian/patches/01-bundle-dependencies.patch| 15 +-
debian/patches/02-ignore-failing-tests.patch | 16 ++-
debian/patches/series | 2 +
7 files changed, 237 insertions(+), 9 deletions(-)
json-smart (2.2-2+deb11u1) bullseye; urgency=medium
* Non-maintainer upload.
* Update Vcs-* URLs to point to salsa.debian.org.
* Rebuild for bullseye. (Closes: #1039985)
-- Andreas Beckmann Tue, 09 Apr 2024 09:36:58 +0200
json-smart (2.2-2+deb10u1) buster-security; urgency=high
* Non-maintainer upload by the LTS team.
* CVE-2023-1370: stack overflow due to excessive recursion
When reaching a ‘[‘ or ‘{‘ character in the JSON input, the code
parses an array or an object respectively. It was discovered that the
code does not have any limit to the nesting of such arrays or
objects. Since the parsing of nested arrays and objects is done
recursively, nesting too many of them can cause a stack exhaustion
(stack overflow) and crash the software. (Closes: #1033474)
* CVE-2021-31684: Fix indexOf
A vulnerability was discovered in the indexOf function of
JSONParserByteArray in JSON Smart versions 1.3 and 2.4
which causes a denial of service (DOS)
via a crafted web request.
-- Bastien Roucariès Wed, 29 Mar 2023 22:21:33 +
[ Other info ]
n/a
Andreas
diff --git a/debian/changelog b/debian/changelog
index 70116d2..f9cd61d 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,29 @@
+json-smart (2.2-2+deb11u1) bullseye; urgency=medium
+
+ * Non-maintainer upload.
+ * Update Vcs-* URLs to point to salsa.debian.org.
+ * Rebuild for bullseye. (Closes: #1039985)
+
+ -- Andreas Beckmann Tue, 09 Apr 2024 09:36:58 +0200
+
+json-smart (2.2-2+deb10u1) buster-security; urgency=high
+
+ * Non-maintainer upload by the LTS team.
+ * CVE-2023-1370: stack overflow due to excessive recursion
+When reaching a ‘[‘ or ‘{‘ character in the JSON input, the code
+parses an array or an object respectively. It was discovered that the
+code does not have any limit to the nesting of such arrays or
+objects. Since the parsing of nested arrays and objects is done
+recursively, nesting too many of them can cause a stack exhaustion
+(stack overflow) and crash the software. (Closes: #1033474)
+ * CVE-2021-31684: Fix indexOf
+A vulnerability was discovered in the indexOf function of
+JSONParserByteArray in JSON Smart versions 1.3 and 2.4
+which causes a denial of service (DOS)
+via a crafted web request.
+
+ -- Bastien Roucariès Wed, 29 Mar 2023 22:21:33 +
+
json-smart (2.2-2) unstable; urgency=medium
* Team upload.
diff --git a/debian/control b/debian/control
index 6488a01..deb7c40 100644
--- a/debian/control
+++ b/debian/control
@@ -6,8 +6,8 @@ Uploaders: Emmanuel Bourg
Build-Depends: debhelper (>= 10), default-jdk, maven-debian-helper (>= 1.5)
Build-Depends-Indep: libmaven-bundle-plugin-java, junit
Standards-Version: 4.1.1
-Vcs-Git: https://anonscm.debian.org/git/pkg-java/json-smart.git
-Vcs-Browser: https://anonscm.debian.org/cgit/pkg-java/json-smart.git
+Vcs-Browser: https://salsa.debian.org/java-team/json-smart
+Vcs-Git: https://salsa.debian.org/java-team/json-smart.git
Homepage: http://netplex.github.io/json-smart/
Package: libjson-smart-java
diff --git a/debian/patches/0004-CVE-2021-31684-Fix-indexOf.patch
b/debian/patches/0004-CVE-2021-31684-Fix-indexOf.patch
new file mode 100644
index 000..d085f43
--- /dev/null
+++ b/
Bug#1068016: bookworm-pu: package node-babel7/7.20.15+ds1+~cs214.269.168-3+deb12u2
Control: tag -1 - confirmed + moreinfo Control: block -1 with 1063530 On 29/03/2024 18.08, Adam D. Barratt wrote: On Fri, 2024-03-29 at 17:41 +0100, Andreas Beckmann wrote: To smoothen some upgrade paths from buster -> bullseye -> bookworm we need to add some Breaks+Replaces against obsolete packages. node-babel7 currently FTBFS due to nodejs 18.19 in bookworm (+security), that seems to require a fix in node-undici first (#1063530) and probably a followup fix from node-babel7 7.20.15+ds1+~cs214.269.168-6, so maybe we should just rebuild the sid version as 7.20.15+ds1+~cs214.269.168-6~deb12u1 Andreas
Bug#1068242: bookworm-pu: package libtool/2.4.7-7~deb12u1
Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: Alastair McKinstry
[ Reason ]
I'd like to rebuild libtool from sid in order to fix two RC bugs:
* missing Conflicts against an obsolete (now virtual) package name
causing file conflicts on some upgrade paths of systems initially
installed while the obsolete package was still a real package
* incorrect detection of the += feature causing problems for packages
using it
[ Impact ]
Some upgrade paths not working (mostly triggered by QA tools).
Operator += not working.
[ Tests ]
Manual piuparts upgrade tests of the affected upgrade paths.
Both changes have been in sid since July without followup issues.
[ Risks ]
In case of regression, we could revert each of the two fixes
separately.
[ 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 ]
+libtool (2.4.7-7~deb12u1) bookworm; urgency=medium
+
+ * Non-maintainer upload.
+ * Rebuild for bookworm.
+ * Reinstate obsolete Breaks, Provides.
+
+ -- Andreas Beckmann Thu, 28 Mar 2024 13:23:40 +0100
+
+libtool (2.4.7-7) unstable; urgency=medium
+
+ * Remove obsole Breaks: for oldstable , Provides: libltdl7-dev
+ * Replace Breaks: libltdl3-dev with Conflicts: libltdl3-dev.
+Thanks Andreas Beckmann. Closes: #1041229
+
+ -- Alastair McKinstry Mon, 17 Jul 2023 16:03:58 +0100
+
+libtool (2.4.7-6) unstable; urgency=medium
+
+ * Incorrect check for += operator causes func_append to fail
+Patch from Ernesto Alfonso. Closes: #1039612
+ * Standards-Version: 4.6.2
+ * Add Breaks/Replaces on libtldl3-dev. Closes: #1039583
+
+ -- Alastair McKinstry Sat, 15 Jul 2023 09:09:39 +0100
changelog | 25
control |4 +
patches/0090-shell-op.patch | 126
patches/series |1
4 files changed, 155 insertions(+), 1 deletion(-)
[ Other info ]
This is a rebuild of the package from sid with the removal of some
obsolete Breaks/Replaces reverted to minimize the diff from stable.
There is an unneeded and useless (because misspelled) Replaces being
added. I'm not fixing (i.e. dropping) that because it's harmless and I
do not want to deviate from sid too much.
Andreas
diff -Nru libtool-2.4.7/debian/changelog libtool-2.4.7/debian/changelog
--- libtool-2.4.7/debian/changelog 2022-11-23 12:34:12.0 +0100
+++ libtool-2.4.7/debian/changelog 2024-03-28 13:23:40.0 +0100
@@ -1,3 +1,28 @@
+libtool (2.4.7-7~deb12u1) bookworm; urgency=medium
+
+ * Non-maintainer upload.
+ * Rebuild for bookworm.
+ * Reinstate obsolete Breaks, Provides.
+
+ -- Andreas Beckmann Thu, 28 Mar 2024 13:23:40 +0100
+
+libtool (2.4.7-7) unstable; urgency=medium
+
+ * Remove obsole Breaks: for oldstable , Provides: libltdl7-dev
+ * Replace Breaks: libltdl3-dev with Conflicts: libltdl3-dev.
+Thanks Andreas Beckmann. Closes: #1041229
+
+ -- Alastair McKinstry Mon, 17 Jul 2023 16:03:58 +0100
+
+libtool (2.4.7-6) unstable; urgency=medium
+
+ * Incorrect check for += operator causes func_append to fail
+Patch from Ernesto Alfonso. Closes: #1039612
+ * Standards-Version: 4.6.2
+ * Add Breaks/Replaces on libtldl3-dev. Closes: #1039583
+
+ -- Alastair McKinstry Sat, 15 Jul 2023 09:09:39 +0100
+
libtool (2.4.7-5) unstable; urgency=medium
* Standards-Version: 4.6.1
diff -Nru libtool-2.4.7/debian/control libtool-2.4.7/debian/control
--- libtool-2.4.7/debian/control2022-11-23 12:34:12.0 +0100
+++ libtool-2.4.7/debian/control2024-03-28 13:23:32.0 +0100
@@ -13,7 +13,7 @@
Section: devel
Priority: optional
Maintainer: Alastair McKinstry
-Standards-Version: 4.6.1
+Standards-Version: 4.6.2
Rules-Requires-Root: no
Homepage: https://www.gnu.org/software/libtool/
Vcs-Browser: https://salsa.debian.org:/mckinstry/libtool.git
@@ -96,6 +96,8 @@
Section: libdevel
Suggests: libtool-doc
Provides: libltdl3-dev, libltdl7-dev
+Conflicts: libltdl3-dev
+Replaces: libbtldl3-dev
Recommends: libtool
Depends: libltdl7 (= ${binary:Version}), ${misc:Depends}, ${automake}
Description: System independent dlopen wrapper for GNU libtool (headers)
diff -Nru libtool-2.4.7/debian/patches/0090-shell-op.patch
libtool-2.4.7/debian/patches/0090-shell-op.patch
--- libtool-2.4.7/debian/patches/0090-shell-op.patch1970-01-01
01:00:00.0 +0100
+++ libtool-2.4.7/debian/patches/0090-shell-op.patch2023-07-17
17:03:58.0 +0200
@@ -0,0 +1,126 @@
+Author: Ernesto Alfonso
+Description: Incorrect check for += operator causes func_append to fail
+Bug-Origin: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039612
+Forwarded: no
+Last-Updated: 2023-07-15
+
+--- a/bootstrap
b/bootstrap
+@@ -227,7 +227,7 @@
+
+ # Source
Bug#1067821: bookworm-pu: package nvidia-graphics-drivers/535.161.08-1~deb12u1
On 29/03/2024 19.40, Adam D. Barratt wrote: libnvidia-pkcs11-openssl3 is a reverse dependency of libcuda1 (seems to get dlopen()ed by it), so we cannot avoid the openssl dependency without risking cuda breakage in sid. Would uploading the 535 stack to testing-proposed-updates be helpful? Would we be better to ship the 525 packages that are already in p-u and revisit 535 for 12.7, Then let's stick to the 525 from -pu for now and hope the 64bit time_t transition is over next time. ;-) or skip those updates as well and just include 535 when we can? The 525 packages are also in stable-updates for fixing module build breakage caused by some backported changes in src:linux in the last point release. So skipping them is no option ;-) Andreas PS: nvidia-modprobe should be independent of the driver stack and t64 transition and could be included in 12.6
Bug#1068016: bookworm-pu: package node-babel7/7.20.15+ds1+~cs214.269.168-3+deb12u2
Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: Yadd
Control: block 1037234 with -1
Control: affects -1 + src:node-babel7
[ Reason ]
To smoothen some upgrade paths from buster -> bullseye -> bookworm we
need to add some Breaks+Replaces against obsolete packages.
[ Impact ]
Some upgrade paths failing with file conflicts, mostly affecting QA
tests.
[ Tests ]
Manual piuparts tests of some affected upgrade paths.
[ Risks ]
Low, adds Breaks+Replaces against packages no longer in the archive.
[ 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 ]
Add Breaks+Replaces against all old node-babel package names predating
version 7, cherry-picked from sid.
[ Other info ]
This package is effectively the same as 7.20.15+ds1+~cs214.269.168-5
that has been in sid at some point, so we could also upload it as
7.20.15+ds1+~cs214.269.168-5~deb12u1 instead.
Andreas
diff --git a/debian/changelog b/debian/changelog
index abcadf21f..106794aa7 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,15 @@
+node-babel7 (7.20.15+ds1+~cs214.269.168-3+deb12u2) bookworm; urgency=medium
+
+ [ Andreas Beckmann ]
+ * Non-maintainer upload.
+ * Backport Breaks+Replaces fixes from 7.20.15+ds1+~cs214.269.168-4.
+
+ [ Yadd ]
+ * Add missing Breaks+Replaces against all node-babel-* that were in Debian 10
+(Closes: #1037234)
+
+ -- Andreas Beckmann Fri, 29 Mar 2024 17:29:05 +0100
+
node-babel7 (7.20.15+ds1+~cs214.269.168-3+deb12u1) bookworm-security;
urgency=medium
* Team upload
diff --git a/debian/control b/debian/control
index e5dba9547..ca8f614e1 100644
--- a/debian/control
+++ b/debian/control
@@ -120,8 +120,92 @@ Depends: ${misc:Depends}
Suggests: node-babel-plugin-polyfill-es-shims
, node-babel7-debug
Breaks: node-babel-core (<< 6.26.0+repack-3~)
+ , node-babel-cli (<< 7)
, node-babel-code-frame (<< 7)
-Replaces: node-babel-code-frame (<< 7)
+ , node-babel-generator (<< 7)
+ , node-babel-helper-bindify-decorators (<< 7)
+ , node-babel-helper-builder-binary-assignment-operator-visitor (<< 7)
+ , node-babel-helper-builder-react-jsx (<< 7)
+ , node-babel-helper-call-delegate (<< 7)
+ , node-babel-helper-explode-assignable-expression (<< 7)
+ , node-babel-helper-explode-class (<< 7)
+ , node-babel-helper-function-name (<< 7)
+ , node-babel-helper-hoist-variables (<< 7)
+ , node-babel-helper-optimise-call-expression (<< 7)
+ , node-babel-helper-remap-async-to-generator (<< 7)
+ , node-babel-helper-replace-supers (<< 7)
+ , node-babel-helpers (<< 7)
+ , node-babel-plugin-external-helpers (<< 7)
+ , node-babel-plugin-syntax-async-generators (<< 7)
+ , node-babel-plugin-syntax-class-properties (<< 7)
+ , node-babel-plugin-syntax-decorators (<< 7)
+ , node-babel-plugin-syntax-do-expressions (<< 7)
+ , node-babel-plugin-syntax-dynamic-import (<< 7)
+ , node-babel-plugin-syntax-flow (<< 7)
+ , node-babel-plugin-syntax-function-bind (<< 7)
+ , node-babel-plugin-syntax-jsx (<< 7)
+ , node-babel-plugin-syntax-object-rest-spread (<< 7)
+ , node-babel-plugin-transform-async-to-generator (<< 7)
+ , node-babel-plugin-transform-exponentiation-operator (<< 7)
+ , node-babel-plugin-transform-flow-strip-types (<< 7)
+ , node-babel-plugin-transform-jscript (<< 7)
+ , node-babel-plugin-transform-proto-to-assign (<< 7)
+ , node-babel-plugin-transform-react-display-name (<< 7)
+ , node-babel-plugin-transform-react-jsx (<< 7)
+ , node-babel-plugin-transform-react-jsx-self (<< 7)
+ , node-babel-plugin-transform-react-jsx-source (<< 7)
+ , node-babel-plugin-transform-regenerator (<< 7)
+ , node-babel-plugin-transform-runtime (<< 7)
+ , node-babel-plugin-transform-strict-mode (<< 7)
+ , node-babel-preset-env (<< 7)
+ , node-babel-preset-flow (<< 7)
+ , node-babel-preset-react (<< 7)
+ , node-babel-register (<< 7)
+ , node-babel-template (<< 7)
+ , node-babel-traverse (<< 7)
+Replaces: node-babel-cli (<< 7)
+ , node-babel-code-frame (<< 7)
+ , node-babel-generator (<< 7)
+ , node-babel-helper-bindify-decorators (<< 7)
+ , node-babel-helper-builder-binary-assignment-operator-visitor (<< 7)
+ , node-babel-helper-builder-react-jsx (<< 7)
+ , node-babel-helper-call-delegate (<< 7)
+ , node-babel-helper-explode-assignable-expression (<< 7)
+ , node-babel-helper-explode-class (<< 7)
+ , node-babel-helper-function-name (<< 7)
+ , node-babel-helper-hoist-variables (<< 7)
+ , node-babel-helper-optimise-call-expression (<< 7)
+ , node-b
Bug#1067980: bookworm-pu: package gpaste/43.1-3+deb12u1
Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: Jérémy Lal
Control: affects -1 + src:gpaste
Control: block 1038751 with -1
[ Reason ]
In order to smoothen upgrade paths I'd like to add some Breaks+Replaces
to bookworm. This avoids a file conflict in case libgpaste6 (last
released with stretch) is still installed.
[ Impact ]
Failing upgrade paths in some more exotic QA tests.
[ Tests ]
Manual piuparts upgrade tests of the affected upgrade paths.
[ Risks ]
Low. Adds Breaks+Replaces against a package no longer in the archive.
[ 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 ]
Add Breaks+Replaces against a long obsolete library package.
[ Other info ]
n/a
Andreas
diff --git a/debian/changelog b/debian/changelog
index ff0b2c9..11feafb 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,14 @@
+gpaste (43.1-3+deb12u1) bookworm; urgency=medium
+
+ [ Andreas Beckmann ]
+ * Non-maintainer upload.
+ * Backport Breaks+Replaces fix from 44.0-1.
+
+ [ Jérémy Lal ]
+ * Breaks+Replaces: libgpaste6 (<< 3.24). Closes: #1038751
+
+ -- Andreas Beckmann Fri, 29 Mar 2024 15:27:53 +0100
+
gpaste (43.1-3) unstable; urgency=medium
[ Jeremy Bicha ]
diff --git a/debian/control b/debian/control
index 2865ee6..eb9b308 100644
--- a/debian/control
+++ b/debian/control
@@ -56,8 +56,8 @@ Package: libgpaste-2-common
Section: libs
Architecture: all
Depends: ${misc:Depends}
-Breaks: libgpaste-common
-Replaces: libgpaste-common
+Breaks: libgpaste-common, libgpaste6 (<< 3.24)
+Replaces: libgpaste-common, libgpaste6 (<< 3.24)
Multi-Arch: foreign
Description: Clipboard management system for GNOME - shared files
GPaste manages clipboard history and allows easy access to it using
Bug#1067821: bookworm-pu: package nvidia-graphics-drivers/535.161.08-1~deb12u1
On 27/03/2024 21.10, Adam D. Barratt wrote: Please go ahead, bearing in mind that the window for 12.6 closes over the coming weekend. The whole nvidia stack has now been uploaded, src:nvidia-graphics-drivers is sitting in NEW. Andreas
Bug#1067888: bookworm-pu: package libesmtp/1.1.0-3.1~deb12u1
Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
Control: block 1043058 with -1
Control: affects -1 + src:libesmtp
[ Reason ]
libesmtp6 uses Replaces without corresponding Breaks, leaving a crippled
libesmtp5 package behind. Version the Replaces and add matching Breaks
to ensure the obsolete libesmtp5 gets removed rather than crippled.
[ Impact ]
QA tools failing due to libesmtp5 losing files.
[ Tests ]
Manual piuparts upgrade tests of the affected upgrade paths.
[ Risks ]
Low, adds B+R against a package no longer in the archive.
[ 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 ]
+libesmtp (1.1.0-3.1~deb12u1) bookworm; urgency=medium
+
+ * Non-maintainer upload.
+ * Rebuild for bookworm.
+
+ -- Andreas Beckmann Thu, 28 Mar 2024 12:08:24 +0100
+
+libesmtp (1.1.0-3.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * libesmtp6: Add versioned Replaces and Breaks against
+libesmtp5 (<< 1.0.6-1~) (Closes: #1043058)
+
+ -- Salvatore Bonaccorso Sat, 19 Aug 2023 12:04:32 +0200
changelog | 15 +++
control |3 ++-
2 files changed, 17 insertions(+), 1 deletion(-)
[ Other info ]
This is a rebuild of the package from sid with no further changes.
I'll directly upload the fixed package after filing this bug.
Andreas
diff -Nru libesmtp-1.1.0/debian/changelog libesmtp-1.1.0/debian/changelog
--- libesmtp-1.1.0/debian/changelog 2021-10-24 19:55:32.0 +0200
+++ libesmtp-1.1.0/debian/changelog 2024-03-28 12:08:24.0 +0100
@@ -1,3 +1,18 @@
+libesmtp (1.1.0-3.1~deb12u1) bookworm; urgency=medium
+
+ * Non-maintainer upload.
+ * Rebuild for bookworm.
+
+ -- Andreas Beckmann Thu, 28 Mar 2024 12:08:24 +0100
+
+libesmtp (1.1.0-3.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * libesmtp6: Add versioned Replaces and Breaks against
+libesmtp5 (<< 1.0.6-1~) (Closes: #1043058)
+
+ -- Salvatore Bonaccorso Sat, 19 Aug 2023 12:04:32 +0200
+
libesmtp (1.1.0-3) unstable; urgency=medium
* debian: Clean up build environment
diff -Nru libesmtp-1.1.0/debian/control libesmtp-1.1.0/debian/control
--- libesmtp-1.1.0/debian/control 2021-10-24 19:34:07.0 +0200
+++ libesmtp-1.1.0/debian/control 2023-08-19 12:04:32.0 +0200
@@ -17,7 +17,8 @@
Architecture: any
Multi-Arch: same
Depends: ${shlibs:Depends}, ${misc:Depends}
-Replaces: libesmtp5
+Replaces: libesmtp5 (<< 1.0.6-1~)
+Breaks: libesmtp5 (<< 1.0.6-1~)
Description: LibESMTP SMTP client library
LibESMTP is a library to manage posting (or submission of) electronic
mail using SMTP to a preconfigured Mail Transport Agent (MTA) such as
Bug#1067843: bookworm-pu: package nvidia-open-gpu-kernel-modules/535.161.08-1~deb12u1
Package: release.debian.org Severity: normal Tags: bookworm User: release.debian@packages.debian.org Usertags: pu [ Reason ] We need to update src:nvidia-open-gpu-kernel-modules to a new upstream version to stay in sync with src:nvidia-graphics-drivers (for a matching firmware-nvidia-gsp upstream version) and to fix some CVEs. [ Impact ] A graphics driver with some open CVEs. [ Tests ] Only installability and module buildability have been tested, everything else would require nvidia hardware. [ Risks ] Upgrading the nvidia driver stack in stable to new upstream releases has already been done in the past. [ Checklist ] [*] *all* changes are documented in the d/changelog The changelog entries for the uploads to sid and bookworm are still missing. [.] I reviewed all changes and I approve them The upstream changes are exceed any reasonably reviewable size. [.] attach debdiff against the package in (old)stable Only for debian/* [ ] the issue is verified as fixed in unstable I'm currently doing interoperability tests with src:nvidia-graphics-drivers. (These two source packages need to be updated together due to the strict firmware dependency.) An upload to bookworm will only happen after the package is in sid. [ Changes ] The full upstream diffstat summary is 1766 files changed, 321746 insertions(+), 112788 deletions(-) and thus I treat this as "unreviewed blob". (Parts of this are firmware blobs as hexdump in C source const char[] format.) debian/.gitignore | 1 + debian/bug-control.mk | 8 +- debian/changelog | 114 +++-- debian/control | 5 +- debian/copyright | 4 +- debian/patches/hmm.patch | 17 +++ ...-minimum-supported-kernel-version-to-3.10.patch | 4 +- ...-remove-empty-lines-from-uts_release-outp.patch | 6 +- debian/patches/module/0034-fix-typos.patch | 48 + debian/patches/module/bashisms.patch | 2 +- debian/patches/module/cc_version_check-gcc5.patch | 2 +- .../module/conftest-prefer-arch-headers.patch | 2 +- debian/patches/module/conftest-verbose.patch | 14 +-- debian/patches/module/ppc64el.patch| 19 debian/patches/module/series.in| 2 +- debian/patches/module/use-kbuild-compiler.patch| 2 +- debian/patches/module/use-kbuild-flags.patch | 2 +- debian/patches/series | 1 + debian/patches/typos.patch | 20 ++-- debian/rules | 9 +- debian/rules.defs | 2 +- debian/source/lintian-overrides| 3 - debian/sync.sh | 1 + There are only minor packaging changes, these have been synced from src:nvidia-graphics-drivers. [ Other info ] This is a rebuild of the package from sid with no further changes. Andreas nvidia-open-gpu-kernel-modules_535.diff.xz Description: application/xz
Bug#1067821: bookworm-pu: package nvidia-graphics-drivers/535.161.08-1~deb12u1
Package: release.debian.org Severity: normal Tags: bookworm User: release.debian@packages.debian.org Usertags: pu [ Reason ] In order to receive further upstream support (i.e. CVE fixes), we need to switch src:nvidia-graphics-drivers from the 525 series (EoL 12/2023) to the 535 series, a new LTSB branch sufficient for the lifetime of bookworm. (The first 535 beta appeared during deep freeze of bookworm.) This driver supports a superset of the GPUs supported by the 525 drivers, no GPUs have been dropped. New metapackage: nvidia-driver-full Removed package: libnvidia-compiler (internal library) New package: libnvidia-pkcs11-openssl3 (internal library) [ Impact ] A proprietary driver with unfixed CVEs. [ Tests ] Only installability and module build tests, everything else would require use of nvidia hardware and driver. [ Risks ] Switching nvidia driver branches and updating to new upstream releases in stable has been done in the past. [ Checklist ] [*] *all* changes are documented in the d/changelog The final changelog entries for uploads to sid and bookworm are still missing, but I expect no further changes than that. [*] I reviewed all changes and I approve them (Excluding the blobs.) [*] attach debdiff against the package in (old)stable (Excluding the blobs.) [ ] the issue is verified as fixed in unstable I'm currently doing interoperability tests with src:nvidia-open-gpu-kernel-modules. (These two source packages need to be updated together due to the strict firmware dependency.) An upload to bookworm will only happen after the package is in sid. [ Changes ] debian/README.source | 4 +- debian/changelog | 548 ++--- debian/control | 85 +++- debian/control.in | 83 +++- debian/control.md5sum | 6 +- debian/copyright | 525 +--- debian/firmware-nvidia-gsp.install.in | 1 + debian/gbp.conf| 2 +- debian/libcuda1.lintian-overrides.in | 2 +- debian/libcuda1.symbols| 17 + debian/libnvcuvid1.symbols | 8 + debian/libnvidia-compiler.install.in | 1 - debian/libnvidia-compiler.symbols.in | 25 - debian/libnvidia-encode1.symbols | 8 + debian/libnvidia-glcore.lintian-overrides.in | 1 + debian/libnvidia-glvkspirv.symbols.in | 5 + debian/libnvidia-ml1.symbols | 36 +- debian/libnvidia-ngx1.symbols | 4 + debian/libnvidia-nvvm4.symbols | 20 +- debian/libnvidia-pkcs11-openssl3.install.in| 1 + ...libnvidia-pkcs11-openssl3.lintian-overrides.in} | 10 +- debian/libnvidia-pkcs11-openssl3.symbols.in| 2 + .../libnvidia-ptxjitcompiler1.lintian-overrides.in | 4 +- debian/libnvidia-rtcore.lintian-overrides.in | 2 +- debian/libnvoptix1.install.in | 1 + debian/not-installed.in| 2 + debian/nv-readme-open.ids | 5 + debian/nv-readme.ids | 17 + debian/nvidia-alternative.postinst.in | 1 + debian/nvidia-opencl-icd.lintian-overrides.in | 2 +- debian/patches/man-fixes-nvidia-smi.patch | 69 +-- ...-minimum-supported-kernel-version-to-3.10.patch | 4 +- ...-remove-empty-lines-from-uts_release-outp.patch | 6 +- debian/patches/module/0034-fix-typos.patch | 24 +- ...35-fix-build-w-kernel-6.1.76-6.6.15-6.7.3.patch | 99 debian/patches/module/bashisms.patch | 2 +- debian/patches/module/cc_version_check-gcc5.patch | 2 +- .../module/conftest-prefer-arch-headers.patch | 2 +- debian/patches/module/conftest-verbose.patch | 14 +- debian/patches/module/ppc64el.patch| 19 - debian/patches/module/series.in| 2 - debian/patches/module/use-kbuild-compiler.patch| 2 +- debian/patches/module/use-kbuild-flags.patch | 2 +- debian/rules | 27 +- debian/watch | 4 +- 45 files changed, 1156 insertions(+), 550 deletions(-) Besides the three new/removed packages there are only minor packaging changes this time. [ Other info ] This is a rebuild of the package from sid with no further changes. This update will require updates of nvidia-settings, nvidia-xconfig, nvidia-persistenced, nvidia-modprobe to keep the major version in sync (and therefore avoid user confusion). These packages will most likely be untouched on further updates of src:nvidia-graphics-drivers 535.*. There will be no update of
Bug#1067745: bookworm-pu: package nvidia-settings/535.171.04-1~deb12u1
Package: release.debian.org Severity: normal Tags: bookworm User: release.debian@packages.debian.org Usertags: pu [ Reason ] In order to upgrade src:nvidia-graphics-drivers to the 535 LTS series (the 525 series currently in stable is already EoL), we need to update some additional packages (some driver components can be built from source and reside in contrib). [ Impact ] Driver components of different major versions may not work well together (untested combinations) or at least confuse users. In nvidia-driver there is a versioned (major part only) Recommends on nvidia-settings that would otherwise be unsatisfiable. [ Tests ] Would require nvidia hardware and driver usage. [ Risks ] Low. Upgrading the nvidia driver stack to new upstream releases in stable has been done in the past. [ Checklist ] [*] *all* changes are documented in the d/changelog [.] I reviewed all changes and I approve them (excluding a review of the upstream changes) [*] attach debdiff against the package in (old)stable [*] the issue is verified as fixed in unstable [ Changes ] +nvidia-settings (535.171.04-1~deb12u1) bookworm; urgency=medium + + * Rebuild for bookworm. + + -- Andreas Beckmann Tue, 26 Mar 2024 10:53:55 +0100 + +nvidia-settings (535.171.04-1) unstable; urgency=medium + + * New upstream release 535.171.04. +- Updated the nvidia-settings control panel to ensure that the entire + Display Configuration page can be used when the Layout window is shown. +- Updated the nvidia-settings control panel to allow the primary display + to be set on any GPU in a multi-GPU system. + * New upstream release 535.146.02. +- Fixed a bug that caused the nvidia-settings control panel to crash + when running on Wayland with newer versions of libwayland-client. + * New upstream release 535.54.03. +- Fixed a bug that prevented SLI Mosaic controls from being displayed in + * New upstream release 535.43.02. +- Added power usage and power limits information to nvidia-settings + PowerMizer page. + the nvidia-settings control panel when using GSP Firmware. + + -- Andreas Beckmann Mon, 25 Mar 2024 11:28:14 +0100 + +nvidia-settings (530.41.03-1) unstable; urgency=medium + + * New upstream release 530.41.03. + * Switch B-D from pkg-config to pkgconf. + + -- Andreas Beckmann Tue, 19 Mar 2024 19:47:39 +0100 - pkg-config was already a transitional package in bookworm. debian/changelog | 32 debian/control |2 debian/patches/12_nvidia-settings.desktop.diff |2 doc/nvidia-settings.desktop|2 doc/version.mk |2 samples/version.mk |2 src/Makefile |4 src/gtk+-2.x/ctkappprofile.c |7 src/gtk+-2.x/ctkdisplayconfig.c| 184 +++- src/gtk+-2.x/ctkdisplayconfig.h|1 src/gtk+-2.x/ctkdisplaydevice.c| 74 + src/gtk+-2.x/ctkdisplaylayout.c| 23 src/gtk+-2.x/ctkevent.c|5 src/gtk+-2.x/ctkframelock.c| 351 +++- src/gtk+-2.x/ctkframelock.h|5 src/gtk+-2.x/ctkgridlicense.c | 424 -- src/gtk+-2.x/ctkgridlicense.h |4 src/gtk+-2.x/ctkpowermizer.c | 148 +++ src/gtk+-2.x/ctkpowermizer.h |6 src/libXNVCtrl/NVCtrl.h| 33 src/libXNVCtrl/version.mk |2 src/libXNVCtrlAttributes/NvCtrlAttributes.h|8 src/libXNVCtrlAttributes/NvCtrlAttributesNvml.c| 275 +++--- src/libXNVCtrlAttributes/NvCtrlAttributesPrivate.h | 81 +- src/nv_grid_dbus.h |6 src/nvml.h | 840 ++--- src/parse.c| 10 src/version.mk |2 src/wayland-connector.c|5 version.mk |2 30 files changed, 1941 insertions(+), 601 deletions(-) [ Other info ] This is a rebuild of the package from sid with no further changes. I do not plan to update src:libxnvctrl in main (which uses a copy of the same source tarball as src:nvidia-settins in contrib) from the 525 to the 535 series. Andreas nvidia-settings_535.171.04-1~deb12u1.diff.xz Description: application/xz
Bug#1067742: bookworm-pu: package nvidia-xconfig/535.171.04-1~deb12u1
Package: release.debian.org Severity: normal Tags: bookworm User: release.debian@packages.debian.org Usertags: pu [ Reason ] In order to upgrade src:nvidia-graphics-drivers to the 535 LTS series (the 525 series currently in stable is already EoL), we need to update some additional packages (some driver components can be built from source and reside in contrib). [ Impact ] Driver components of different major versions may not work well together (untested combinations) or at least confuse users. [ Tests ] Would require nvidia hardware and driver usage. [ Risks ] Low. Upgrading the nvidia driver stack to new upstream releases in stable has been done in the past. [ 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-xconfig (535.171.04-1~deb12u1) bookworm; urgency=medium + + * Rebuild for bookworm. + + -- Andreas Beckmann Tue, 26 Mar 2024 10:42:46 +0100 + +nvidia-xconfig (535.171.04-1) unstable; urgency=medium + + * New upstream release. + + -- Andreas Beckmann Mon, 25 Mar 2024 11:01:38 +0100 + +nvidia-xconfig (530.41.03-1) unstable; urgency=medium + + * New upstream release. + + -- Andreas Beckmann Tue, 19 Mar 2024 18:19:15 +0100 + +nvidia-xconfig (525.147.05-1) unstable; urgency=medium + + * New upstream release. + * Switch B-D from pkg-config to pkgconf. + + -- Andreas Beckmann Mon, 12 Feb 2024 01:00:28 +0100 - pkg-config was already a transitional package in bookworm. - Upstream changes are only the version bump. [ Other info ] This is a rebuild of the package from sid with no further changes. Andreas diff --git a/debian/changelog b/debian/changelog index 7388e99..c4aae45 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,28 @@ +nvidia-xconfig (535.171.04-1~deb12u1) bookworm; urgency=medium + + * Rebuild for bookworm. + + -- Andreas Beckmann Tue, 26 Mar 2024 10:42:46 +0100 + +nvidia-xconfig (535.171.04-1) unstable; urgency=medium + + * New upstream release. + + -- Andreas Beckmann Mon, 25 Mar 2024 11:01:38 +0100 + +nvidia-xconfig (530.41.03-1) unstable; urgency=medium + + * New upstream release. + + -- Andreas Beckmann Tue, 19 Mar 2024 18:19:15 +0100 + +nvidia-xconfig (525.147.05-1) unstable; urgency=medium + + * New upstream release. + * Switch B-D from pkg-config to pkgconf. + + -- Andreas Beckmann Mon, 12 Feb 2024 01:00:28 +0100 + nvidia-xconfig (525.85.05-1) unstable; urgency=medium * New upstream release. diff --git a/debian/control b/debian/control index cb08ba1..409c3aa 100644 --- a/debian/control +++ b/debian/control @@ -7,7 +7,7 @@ Uploaders: Build-Depends: debhelper-compat (= 13), m4, - pkg-config, + pkgconf, xserver-xorg-dev, Rules-Requires-Root: no Standards-Version: 4.6.2 diff --git a/debian/copyright b/debian/copyright index 074b28c..a187e54 100644 --- a/debian/copyright +++ b/debian/copyright @@ -124,8 +124,9 @@ Copyright: (c) 1997-2001 by The XFree86 Project, Inc. License: other-XFree Files: debian/* -Copyright: © 2005 Randall Donald - © 2010-2023 Andreas Beckmann +Copyright: + © 2005 Randall Donald + © 2010-2024 Andreas Beckmann License: GPL-2+ License: GPL-2 diff --git a/debian/salsa-ci.yml b/debian/salsa-ci.yml index 24a535b..d0f7c0e 100644 --- a/debian/salsa-ci.yml +++ b/debian/salsa-ci.yml @@ -1,7 +1,6 @@ --- include: - - https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/salsa-ci.yml - - https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/pipeline-jobs.yml + - https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/recipes/debian.yml variables: SALSA_CI_COMPONENTS: 'main contrib' diff --git a/version.mk b/version.mk index 36f5738..89404cd 100644 --- a/version.mk +++ b/version.mk @@ -1,4 +1,4 @@ -NVIDIA_VERSION = 525.85.05 +NVIDIA_VERSION = 535.171.04 # This file. VERSION_MK_FILE := $(lastword $(MAKEFILE_LIST))
Bug#1067739: bookworm-pu: package nvidia-persistenced/535.171.04-1~deb12u1
Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
[ Reason ]
In order to upgrade src:nvidia-graphics-drivers to the 535 LTS series
(the 525 series currently in stable is already EoL), we need to update
some additional packages (some driver components can be built from
source and reside in contrib).
[ Impact ]
Driver components of different major versions may not work well together
(untested combinations) or at least confuse users.
[ Tests ]
Would require nvidia hardware and driver usage.
[ Risks ]
Low. Upgrading the nvidia driver stack to new upstream releases in
stable has been done in the past.
[ 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-persistenced (535.171.04-1~deb12u1) bookworm; urgency=medium
+
+ * Rebuild for bookworm.
+
+ -- Andreas Beckmann Tue, 26 Mar 2024 01:13:10 +0100
+
+nvidia-persistenced (535.171.04-1) unstable; urgency=medium
+
+ * New upstream release.
+
+ -- Andreas Beckmann Mon, 25 Mar 2024 10:51:19 +0100
+
+nvidia-persistenced (530.41.03-1) unstable; urgency=medium
+
+ * New upstream release.
+ * Switch B-D from pkg-config to pkgconf.
+
+ -- Andreas Beckmann Tue, 19 Mar 2024 17:59:21 +0100
+
+nvidia-persistenced (525.147.05-1) unstable; urgency=medium
+
+ * New upstream release.
+ * Update the list of supported drivers.
+
+ -- Andreas Beckmann Fri, 26 Jan 2024 23:34:41 +0100
- pkg-config was already a transitional package in bookworm.
- The transitional -tesla driver packages have been removed from
dependency alternatives.
[ Other info ]
This is a rebuild of the package from sid with no further changes.
Andreas
diff --git a/debian/changelog b/debian/changelog
index 4a6ead7..4cd4301 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,29 @@
+nvidia-persistenced (535.171.04-1~deb12u1) bookworm; urgency=medium
+
+ * Rebuild for bookworm.
+
+ -- Andreas Beckmann Tue, 26 Mar 2024 01:13:10 +0100
+
+nvidia-persistenced (535.171.04-1) unstable; urgency=medium
+
+ * New upstream release.
+
+ -- Andreas Beckmann Mon, 25 Mar 2024 10:51:19 +0100
+
+nvidia-persistenced (530.41.03-1) unstable; urgency=medium
+
+ * New upstream release.
+ * Switch B-D from pkg-config to pkgconf.
+
+ -- Andreas Beckmann Tue, 19 Mar 2024 17:59:21 +0100
+
+nvidia-persistenced (525.147.05-1) unstable; urgency=medium
+
+ * New upstream release.
+ * Update the list of supported drivers.
+
+ -- Andreas Beckmann Fri, 26 Jan 2024 23:34:41 +0100
+
nvidia-persistenced (525.85.05-1) unstable; urgency=medium
* New upstream release.
diff --git a/debian/control b/debian/control
index 488080e..a55bf29 100644
--- a/debian/control
+++ b/debian/control
@@ -6,7 +6,7 @@ Uploaders:
Andreas Beckmann ,
Build-Depends:
debhelper-compat (= 13),
- pkg-config,
+ pkgconf,
libtirpc-dev,
m4,
Rules-Requires-Root: no
@@ -21,8 +21,7 @@ Multi-Arch: foreign
Pre-Depends:
${misc:Pre-Depends}
Depends:
- libnvidia-cfg1 [!i386 !armhf !ppc64el]
- | libnvidia-tesla-cfg1 [amd64 arm64 ppc64el]
+ libnvidia-cfg1 [!i386 !armhf]
| libnvidia-tesla-470-cfg1 [amd64 arm64 ppc64el]
| libnvidia-cfg.so.1
| libnvidia-cfg1-any,
diff --git a/debian/copyright b/debian/copyright
index 929b9c2..61fef5c 100644
--- a/debian/copyright
+++ b/debian/copyright
@@ -9,12 +9,12 @@ Disclaimer:
NVIDIA drivers in non-free.
Files: *
-Copyright: Copyright (C) 2004-2022 NVIDIA Corporation
+Copyright: Copyright (C) 2004-2023 NVIDIA Corporation
License: Expat
Files: debian/*
Copyright:
- © 2014-2023 Andreas Beckmann
+ © 2014-2024 Andreas Beckmann
License: Expat
License: Expat
diff --git a/debian/salsa-ci.yml b/debian/salsa-ci.yml
index 14fa000..c3d1fdf 100644
--- a/debian/salsa-ci.yml
+++ b/debian/salsa-ci.yml
@@ -1,7 +1,6 @@
---
include:
- - https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/salsa-ci.yml
- -
https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/pipeline-jobs.yml
+ -
https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/recipes/debian.yml
variables:
SALSA_CI_COMPONENTS: 'main contrib non-free'
diff --git a/nv-ioctl-numa.h b/nv-ioctl-numa.h
index 3fad820..1d456ec 100644
--- a/nv-ioctl-numa.h
+++ b/nv-ioctl-numa.h
@@ -62,6 +62,7 @@ typedef struct nv_ioctl_numa_info
uint64_t memblock_size __aligned(8);
uint64_t numa_mem_addr __aligned(8);
uint64_t numa_mem_size __aligned(8);
+uint8_t use_auto_online;
nv_offline_addresses_t offline_addresses __aligned(8);
} nv_ioctl_numa_info_t;
diff --git a/nvidia-numa.c b/nvidia-numa.c
index afc8fe4..0fbd287 100644
--- a/nvidia-numa.c
+++ b/nvidia-numa.c
@@ -1,5 +1,5 @@
/*
- * Copyright (c) 2018, NVIDIA CORPORATION.
+ * Copyright (c) 2018-2023, NVIDIA CORPORATION.
*
* Permission is hereby granted, free of charge, to any person
Bug#1067564: bookworm-pu: package cpu/1.4.3-14~deb12u1
Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
Control: block 1067439 withh -1
Control: affects -1 + src:cpu
[ Reason ]
The last QA upload four years ago fixed a FTBFS (multiple definitions of
a global variable) by replacing that variable with an extern declaration
and zero definitions. This didn't result in a linker error (missing
symbol) because it happens in a plugin library and thus is only detected
at runtime when the plugin gets loaded (i.e. always).
So let's ship the plugin with *one* definition of the global variable
;-)
[ Impact ]
cpu stays unusable, but nobody noticed that for the last 4 years and two
stable releases ...
[ Tests ]
Added a smoke test autopkgtest that detects the current failure.
[ Risks ]
We can't make the current situation much worse ;-)
[ 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 ]
* Actually provide a definition of globalLdap. (Closes: #1067439)
[ Other info ]
n/a
Andreas
diff --git a/debian/changelog b/debian/changelog
index ec0f291..a5aa4a2 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,18 @@
+cpu (1.4.3-14~deb12u1) bookworm; urgency=medium
+
+ * QA upload.
+ * Rebuild or bookworm.
+
+ -- Andreas Beckmann Sat, 23 Mar 2024 18:03:59 +0100
+
+cpu (1.4.3-14) unstable; urgency=medium
+
+ * QA upload.
+ * Actually provide a definition of globalLdap. (Closes: #1067439)
+ * Add smoke test.
+
+ -- Andreas Beckmann Sat, 23 Mar 2024 14:39:06 +0100
+
cpu (1.4.3-13) unstable; urgency=medium
* QA upload.
diff --git a/debian/gbp.conf b/debian/gbp.conf
new file mode 100644
index 000..9048820
--- /dev/null
+++ b/debian/gbp.conf
@@ -0,0 +1,2 @@
+[DEFAULT]
+debian-branch = main
diff --git a/debian/patches/14_use-extern.patch
b/debian/patches/14_use-extern.patch
index 774b581..26b0b19 100644
--- a/debian/patches/14_use-extern.patch
+++ b/debian/patches/14_use-extern.patch
@@ -1,10 +1,11 @@
Description: Fix ftbfs with GCC-10
Bug-Debian: https://bugs.debian.org/957106
+Bug-Debian: https://bugs.debian.org/1067439
---
cpu-1.4.3.orig/src/include/plugins/ldap/ldap.h
-+++ cpu-1.4.3/src/include/plugins/ldap/ldap.h
+--- a/src/include/plugins/ldap/ldap.h
b/src/include/plugins/ldap/ldap.h
@@ -106,7 +106,7 @@ typedef struct CPU_ldap {
Parser * parse;
} CPU_ldap;
@@ -14,3 +15,14 @@ Bug-Debian: https://bugs.debian.org/957106
int parseCommand(int argc, char *argv[]);
void printHelp(int op);
+--- a/src/plugins/ldap/ldap.c
b/src/plugins/ldap/ldap.c
+@@ -26,6 +26,8 @@
+ #include
+ #include "plugins/ldap/ldap.h"
+
++CPU_ldap * globalLdap;
++
+ int verbose;
+ int operation;
+
diff --git a/debian/tests/control b/debian/tests/control
new file mode 100644
index 000..7633658
--- /dev/null
+++ b/debian/tests/control
@@ -0,0 +1,8 @@
+Test-Command: /usr/sbin/cpu || /usr/sbin/cpu 2>&1 | grep ^usage:
+Features: test-name=smoketest
+Depends:
+ cpu,
+Restrictions:
+ superficial,
+ needs-root,
+ allow-stderr,
Bug#1067149: bookworm-pu: package hovercraft/2.7-6~deb12u1
Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
Control: affects -1 + src:hovercraft
Control: block 1025655 with -1
Control: affects 1067148 + src:hovercraft
Control: block 1025655 with 1067148
[ Reason ]
hovercraft is unusable w/o python3-setuptools
[ Impact ]
hovercraft is unusable without manual installation of additional
packages.
[ Tests ]
New autopkgtest smoke test running hovercraft --help.
[ Risks ]
Low. Only adds a dependency and a test.
[ 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 ]
hovercraft (2.7-6~deb12u1) bookworm; urgency=medium
* Rebuild for bookworm.
-- Andreas Beckmann Tue, 19 Mar 2024 11:55:51 +0100
hovercraft (2.7-6) unstable; urgency=medium
* QA upload.
* Add smoke test.
* Add Depends: python3-setuptools. (Closes: #1025655)
-- Andreas Beckmann Tue, 19 Mar 2024 02:12:55 +0100
[ Other info ]
This is a rebuild of the package from sid with no further changes.
Andreas
diff --git a/debian/changelog b/debian/changelog
index 1eeff73..c13b370 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,17 @@
+hovercraft (2.7-6~deb12u1) bookworm; urgency=medium
+
+ * Rebuild for bookworm.
+
+ -- Andreas Beckmann Tue, 19 Mar 2024 11:55:51 +0100
+
+hovercraft (2.7-6) unstable; urgency=medium
+
+ * QA upload.
+ * Add smoke test.
+ * Add Depends: python3-setuptools. (Closes: #1025655)
+
+ -- Andreas Beckmann Tue, 19 Mar 2024 02:12:55 +0100
+
hovercraft (2.7-5) unstable; urgency=medium
* QA upload.
diff --git a/debian/control b/debian/control
index 149ab2d..5150f54 100644
--- a/debian/control
+++ b/debian/control
@@ -25,6 +25,7 @@ Architecture: all
Depends:
libjs-impress (>= 1.0.0~),
python3-docutils,
+ python3-setuptools,
${misc:Depends},
${python3:Depends},
${sphinxdoc:Depends},
diff --git a/debian/tests/control b/debian/tests/control
index b289ad2..af04031 100644
--- a/debian/tests/control
+++ b/debian/tests/control
@@ -3,3 +3,10 @@ Depends:
@,
@builddeps@,
python3-all,
+
+Test-Command: hovercraft --help
+Features: test-name=hovercraft_--help
+Depends:
+ hovercraft,
+Restrictions:
+ superficial,
Bug#1067148: bullseye-pu: package hovercraft/2.7-2+deb11u1
Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
[ Reason ]
hovercraft is unusable w/o python3-setuptools
[ Impact ]
hovercraft is unusable without manual installation of additional
packages.
[ Tests ]
New autopkgtest smoke test running hovercraft --help.
[ Risks ]
Low. Only adds a dependency and a test.
[ 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 ]
hovercraft (2.7-2+deb11u1) bullseye; urgency=medium
* QA upload.
* Add smoke test.
* Add Depends: python3-setuptools. (Closes: #1025655)
-- Andreas Beckmann Tue, 19 Mar 2024 03:15:54 +0100
[ Other info ]
n/a
Andreas
diff --git a/debian/changelog b/debian/changelog
index a35d2ac..97452e4 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+hovercraft (2.7-2+deb11u1) bullseye; urgency=medium
+
+ * QA upload.
+ * Add smoke test.
+ * Add Depends: python3-setuptools. (Closes: #1025655)
+
+ -- Andreas Beckmann Tue, 19 Mar 2024 03:15:54 +0100
+
hovercraft (2.7-2) unstable; urgency=medium
* debian/control
diff --git a/debian/control b/debian/control
index bc6999e..8df4020 100644
--- a/debian/control
+++ b/debian/control
@@ -25,6 +25,7 @@ Package: hovercraft
Architecture: all
Depends: python3-docutils,
libjs-impress (>= 1.0.0~),
+ python3-setuptools,
${misc:Depends},
${python3:Depends},
${sphinxdoc:Depends}
diff --git a/debian/gbp.conf b/debian/gbp.conf
index 3879982..f41fd29 100644
--- a/debian/gbp.conf
+++ b/debian/gbp.conf
@@ -1,2 +1,2 @@
[DEFAULT]
-debian-branch=debian/master
+debian-branch=debian/bullseye
diff --git a/debian/tests/control b/debian/tests/control
index e1568a0..17e33a3 100644
--- a/debian/tests/control
+++ b/debian/tests/control
@@ -1,2 +1,9 @@
Tests: hovercraft
Depends: @, @builddeps@
+
+Test-Command: hovercraft --help
+Features: test-name=hovercraft_--help
+Depends:
+ hovercraft,
+Restrictions:
+ superficial,
Bug#1067106: bullseye-pu: package nvidia-settings/470.239.06-1
Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
[ Reason ]
As a followup for enabling src:nvidia-graphics-drivers on ppc64el
(to be in sync with sid), we need to enable building the nvidia-settings
binary package for ppc64el, too.
Lets switch to the latest 470.* upstream release at the same time (to be
in sync again with the driver package), this only has some typo
corrections and the version bump as upstream changes.
[ Impact ]
nvidia-driver:ppc64el has unsatisfiable Recomends.
[ Tests ]
Would require ppc64el hardware with nvidia GPU and nvidia driver usage.
[ Risks ]
There are no risky changes to the binary packages that were previously
built.
[ 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-settings (470.239.06-1) bullseye; urgency=medium
* New upstream release 470.141.03.
* Build for ppc64el.
* Upload to bullseye.
-- Andreas Beckmann Mon, 18 Mar 2024 14:38:21 +0100
debian/changelog | 8
debian/control| 2 +-
debian/gbp.conf | 2 +-
doc/version.mk| 2 +-
samples/version.mk| 2 +-
src/libXNVCtrl/version.mk | 2 +-
src/nvml.h| 41 +
src/version.mk| 2 +-
version.mk| 2 +-
9 files changed, 36 insertions(+), 27 deletions(-)
[ Other info ]
I'm not planning to backport the split of src:libxnvctrl from
src:nvidia-settings to bullseye.
Andreas
diff --git a/debian/changelog b/debian/changelog
index 54f627f..504c78e 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+nvidia-settings (470.239.06-1) bullseye; urgency=medium
+
+ * New upstream release 470.141.03.
+ * Build for ppc64el.
+ * Upload to bullseye.
+
+ -- Andreas Beckmann Mon, 18 Mar 2024 14:38:21 +0100
+
nvidia-settings (470.141.03-1~deb11u1) bullseye; urgency=medium
* Rebuild for bullseye.
diff --git a/debian/control b/debian/control
index 281c4ff..3d776af 100644
--- a/debian/control
+++ b/debian/control
@@ -26,7 +26,7 @@ Vcs-Git:
https://salsa.debian.org/nvidia-team/nvidia-settings.git
Package: nvidia-settings
Section: contrib/x11
-Architecture: amd64 arm64
+Architecture: amd64 arm64 ppc64el
Pre-Depends:
nvidia-installer-cleanup,
Depends:
diff --git a/debian/gbp.conf b/debian/gbp.conf
index 8ebcf1c..5cca736 100644
--- a/debian/gbp.conf
+++ b/debian/gbp.conf
@@ -1,5 +1,5 @@
[DEFAULT]
upstream-vcs-tag = %(version)s
upstream-branch = upstream
-debian-branch = master
+debian-branch = bullseye
debian-tag = debian/%(version)s
diff --git a/doc/version.mk b/doc/version.mk
index cca9ae5..7a608de 100644
--- a/doc/version.mk
+++ b/doc/version.mk
@@ -1,4 +1,4 @@
-NVIDIA_VERSION = 470.141.03
+NVIDIA_VERSION = 470.239.06
# This file.
VERSION_MK_FILE := $(lastword $(MAKEFILE_LIST))
diff --git a/samples/version.mk b/samples/version.mk
index cca9ae5..7a608de 100644
--- a/samples/version.mk
+++ b/samples/version.mk
@@ -1,4 +1,4 @@
-NVIDIA_VERSION = 470.141.03
+NVIDIA_VERSION = 470.239.06
# This file.
VERSION_MK_FILE := $(lastword $(MAKEFILE_LIST))
diff --git a/src/libXNVCtrl/version.mk b/src/libXNVCtrl/version.mk
index cca9ae5..7a608de 100644
--- a/src/libXNVCtrl/version.mk
+++ b/src/libXNVCtrl/version.mk
@@ -1,4 +1,4 @@
-NVIDIA_VERSION = 470.141.03
+NVIDIA_VERSION = 470.239.06
# This file.
VERSION_MK_FILE := $(lastword $(MAKEFILE_LIST))
diff --git a/src/nvml.h b/src/nvml.h
index 4bd1a9e..1db12bf 100644
--- a/src/nvml.h
+++ b/src/nvml.h
@@ -403,6 +403,7 @@ typedef enum nvmlGpuP2PStatus_enum
{
NVML_P2P_STATUS_OK = 0,
NVML_P2P_STATUS_CHIPSET_NOT_SUPPORED,
+NVML_P2P_STATUS_CHIPSET_NOT_SUPPORTED =
NVML_P2P_STATUS_CHIPSET_NOT_SUPPORED,
NVML_P2P_STATUS_GPU_NOT_SUPPORTED,
NVML_P2P_STATUS_IOH_TOPOLOGY_NOT_SUPPORTED,
NVML_P2P_STATUS_DISABLED_BY_REGKEY,
@@ -1813,7 +1814,7 @@ typedef struct nvmlEncoderSessionInfo_st
*/
typedef enum nvmlFBCSessionType_enum
{
-NVML_FBC_SESSION_TYPE_UNKNOWN = 0, //!< Unknwon
+NVML_FBC_SESSION_TYPE_UNKNOWN = 0, //!< Unknown
NVML_FBC_SESSION_TYPE_TOSYS, //!< ToSys
NVML_FBC_SESSION_TYPE_CUDA,//!< Cuda
NVML_FBC_SESSION_TYPE_VID, //!< Vid
@@ -4258,10 +4259,10 @@ nvmlReturn_t DECLDIR nvmlDeviceGetEncoderStats
(nvmlDevice_t device, unsigned in
* Retrieves information about active encoder sessions on a target device.
*
* An array of active encoder sessions is returned in the caller-supplied
buffer pointed at by \a sessionInfos. The
- * array elememt count is passed in \a sessionCount, and \a sessionCount is
used to return the number of sessions
+ * array element count is passed in \a sessionCount, and \a sessionCount is
used to return the num
Bug#1065653: bookworm-pu: package nvidia-modprobe/535.161.07-1~deb12u1
Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
[ Reason ]
In preparation to switching bookworm from the nvidia-graphics-drivers
525.* series (production branch, EoL) to the 535.* series (long term
support branch, receives updates until July 2026), we need to update
nvidia-modprobe again. We already have a 535 release in bookworm, but
there was recently a new option being added.
[ Impact ]
nvidia-modprobe differing in features from the upstream version shipped
with the corresponding nvidia driver version.
[ Tests ]
Testing the new option would require a Grace Hopper chip.
[ Risks ]
Low. Adds a new option, other codepaths unaffected.
[ 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 ]
No additional packaging changes.
[ Other info ]
This is a rebuild of the package from sid with no further changes.
Andreas
diff --git a/debian/changelog b/debian/changelog
index dcd403b..7d25e6a 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,15 @@
+nvidia-modprobe (535.161.07-1~deb12u1) bookworm; urgency=medium
+
+ * Rebuild for bookworm.
+
+ -- Andreas Beckmann Fri, 08 Mar 2024 09:26:40 +0100
+
+nvidia-modprobe (535.161.07-1) unstable; urgency=medium
+
+ * New upstream release.
+
+ -- Andreas Beckmann Thu, 07 Mar 2024 14:36:38 +0100
+
nvidia-modprobe (535.54.03-1~deb12u1) bookworm; urgency=medium
* Rebuild for bookworm.
diff --git a/debian/copyright b/debian/copyright
index 26ebb3f..e65d0a5 100644
--- a/debian/copyright
+++ b/debian/copyright
@@ -27,7 +27,7 @@ License: Expat
Files: debian/*
Copyright:
- © 2014-2023 Andreas Beckmann
+ © 2014-2024 Andreas Beckmann
License: Expat
License: Expat
diff --git a/debian/salsa-ci.yml b/debian/salsa-ci.yml
index 33c3a64..8424db4 100644
--- a/debian/salsa-ci.yml
+++ b/debian/salsa-ci.yml
@@ -1,4 +1,3 @@
---
include:
- - https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/salsa-ci.yml
- -
https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/pipeline-jobs.yml
+ -
https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/recipes/debian.yml
diff --git a/modprobe-utils/nvidia-modprobe-utils.c
b/modprobe-utils/nvidia-modprobe-utils.c
index 1a2144f..a0b7e3d 100644
--- a/modprobe-utils/nvidia-modprobe-utils.c
+++ b/modprobe-utils/nvidia-modprobe-utils.c
@@ -1059,4 +1059,45 @@ int nvidia_cap_get_file_state(const char* cap_file_path)
cap_file_path, uid, gid, mode);
}
+/*
+ * Attempt to enable auto onlining mode online_movable
+ */
+int nvidia_enable_auto_online_movable(const int print_errors)
+{
+int fd;
+const char path_to_file[] =
"/sys/devices/system/memory/auto_online_blocks";
+const char str[] = "online_movable";
+ssize_t write_count;
+
+fd = open(path_to_file, O_RDWR, 0);
+if (fd < 0)
+{
+if (print_errors)
+{
+fprintf(stderr,
+"NVIDIA: failed to open `%s`: %s.\n",
+path_to_file, strerror(errno));
+}
+return 0;
+}
+
+write_count = write(fd, str, sizeof(str));
+if (write_count != sizeof(str))
+{
+if (print_errors)
+{
+fprintf(stderr,
+"NVIDIA: unable to write to `%s`: %s.\n",
+path_to_file, strerror(errno));
+}
+
+close(fd);
+return 0;
+}
+
+close(fd);
+
+return 1;
+}
+
#endif /* NV_LINUX */
diff --git a/modprobe-utils/nvidia-modprobe-utils.h
b/modprobe-utils/nvidia-modprobe-utils.h
index ebc01e1..dff221d 100644
--- a/modprobe-utils/nvidia-modprobe-utils.h
+++ b/modprobe-utils/nvidia-modprobe-utils.h
@@ -85,6 +85,7 @@ int nvidia_cap_mknod(const char* cap_file_path, int *minor);
int nvidia_cap_get_file_state(const char* cap_file_path);
int nvidia_get_chardev_major(const char *name);
int nvidia_msr_modprobe(void);
+int nvidia_enable_auto_online_movable(const int print_errors);
#endif /* NV_LINUX */
diff --git a/nvidia-modprobe.1.m4 b/nvidia-modprobe.1.m4
index 4f15e50..aba284e 100644
--- a/nvidia-modprobe.1.m4
+++ b/nvidia-modprobe.1.m4
@@ -28,7 +28,7 @@ nvidia\-modprobe \- Load the NVIDIA kernel module and create
NVIDIA character de
.SH DESCRIPTION
The
.B nvidia\-modprobe
-utility is used by user-space NVIDIA driver components to make sure the NVIDIA
kernel module is loaded and that the NVIDIA character device files are present.
These facilities are normally provided by Linux distribution configuration
systems such as udev. When possible, it is recommended to use your Linux
distribution's native mechanisms for managing kernel module loading and device
file creation. This utility is provided as a fallback to work out-of-the-box
in a distribution-inde
Bug#1065053: bullseye-pu: package nvidia-graphics-drivers-tesla-470/470.239.06-1~deb11u1
Package: release.debian.org Severity: normal Tags: bullseye User: release.debian@packages.debian.org Usertags: pu [ Reason ] Let's update nvidia-graphics-drivers-tesla-470 in bookworm to a new upstream release fixing a few CVEs. The only effective packaging change resulting from switching src:nvidia-graphics-drivers to the Tesla 470 series is that nvidia-cuda-mps is now built there instead of here, but both packages are of the same opstream version. [ Impact ] A proprietary graphics driver with some unfixed CVEs. [ Tests ] Only the module has been build-tested. Everything else would require use of nvidia hardware and non-free driver. [ Risks ] Updating the nvidia driver packages in (old)stable to new upstream releases is an established practice. [ Checklist ] [*] *all* changes are documented in the d/changelog [*] I reviewed all changes and I approve them (Excluding the blob parts.) [*] attach debdiff against the package in (old)stable (Excluding the blob parts.) [*] the issue is verified as fixed in unstable [ Changes ] nvidia-graphics-drivers-tesla-470 (470.239.06-1~deb11u1) bullseye; urgency=medium * Rebuild for bullseye. -- Andreas Beckmann Thu, 29 Feb 2024 09:58:07 +0100 nvidia-graphics-drivers-tesla-470 (470.239.06-1~deb12u1) bookworm; urgency=medium * Rebuild for bookworm. -- Andreas Beckmann Thu, 29 Feb 2024 02:41:42 +0100 nvidia-graphics-drivers-tesla-470 (470.239.06-1) unstable; urgency=medium * New upstream long term support branch release 470.239.06 (2024-02-22). * Fixed CVE-2024-0074, CVE-2024-0078, CVE-2022-42265. (Closes: #1064989) https://nvidia.custhelp.com/app/answers/detail/a_id/5520 * Improved compatibility with recent Linux kernels. [ Andreas Beckmann ] * Refresh patches. -- Andreas Beckmann Wed, 28 Feb 2024 02:22:39 +0100 nvidia-graphics-drivers (470.239.06-1) bullseye; urgency=medium * New upstream long term support branch release 470.239.06 (2024-02-22). * Fixed CVE-2024-0074, CVE-2024-0078, CVE-2022-42265. (Closes: #1064983) https://nvidia.custhelp.com/app/answers/detail/a_id/5520 * Improved compatibility with recent Linux kernels. [ Andreas Beckmann ] * Refresh patches. * Upload to bullseye. -- Andreas Beckmann Thu, 29 Feb 2024 00:25:42 +0100 nvidia-graphics-drivers-tesla-470 (470.223.02-4~deb12u1) bookworm; urgency=medium * Rebuild for bookworm. -- Andreas Beckmann Tue, 13 Feb 2024 00:00:08 +0100 nvidia-graphics-drivers-tesla-470 (470.223.02-4) unstable; urgency=medium * Apply pfn_valid patch from gentoo to fix kernel module build for Linux 6.1.76, 6.6.15, 6.7.3, 6.8. (Closes: #1063361) * Update lintian overrides. -- Andreas Beckmann Thu, 08 Feb 2024 14:23:21 +0100 nvidia-graphics-drivers-tesla-470 (470.223.02-3) unstable; urgency=medium * nvidia-cuda-mps is again built from src:nvidia-graphics-drivers. -- Andreas Beckmann Thu, 25 Jan 2024 19:48:07 +0100 nvidia-graphics-drivers (470.223.02-3) UNRELEASED; urgency=medium * Switch src:nvidia-graphics-drivers to the Tesla 470 driver series. * Build for ppc64el. * Build all unversioned packages from src:nvidia-graphics-drivers. * New Romanian (ro) debconf translations by Remus-Gabriel Chelu. -- Andreas Beckmann Thu, 25 Jan 2024 19:48:07 +0100 debian/README.source | 63 ++- debian/bug-control.mk | 4 +- debian/changelog | 113 +- debian/control | 17 - debian/control.in | 7 +- debian/control.md5sum | 8 +- debian/copyright | 7 +- debian/detect/nvidia-418.ids | 304 -- debian/detect/nvidia-470.ids | 439 - debian/detect/nvidia-detect.in | 92 ++--- debian/libnvidia-eglcore.lintian-overrides.in | 1 + debian/libnvidia-glcore.lintian-overrides.in | 1 + ...anagement-features-were-not-yet-in-Linux.patch} | 14 +- ...-includes-to-fix-module-build-for-ppc64el.patch | 30 ++ debian/module/debian/patches/0034-fix-typos.patch | 62 +++ debian/module/debian/patches/bashisms.patch| 2 +- .../debian/patches/cc_version_check-gcc5.patch | 2 +- debian/module/debian/patches/ppc64el.patch | 19 - debian/module/debian/patches/series.in | 5 +- debian/not-installed.in| 5 + debian/nvidia-detect.install | 4 +- debian/nvidia.NEWS | 9 + debian/patches/legacy-470.patch| 2 +- debian/po/ro.po| 81 debian/rules | 15 +- debian/rules.defs | 9 +- debian/source/lintian-overrides
Bug#1065052: bookworm-pu: package nvidia-graphics-drivers-tesla-470/470.239.06-1~deb12u1
Package: release.debian.org Severity: normal Tags: bookworm User: release.debian@packages.debian.org Usertags: pu [ Reason ] Let's update nvidia-graphics-drivers-tesla-470 in bookworm to a new upstream release fixing a few CVEs. This release also contains an upstream fix for the issue we recently fixed via stable-updates. No need for stable-updates this time. No additional packaging changes this time (besides refreshing/reordering the patches) [ Impact ] A proprietary graphics driver with some unfixed CVEs. [ Tests ] Only the module has been build-tested. Everything else would require use of nvidia hardware and non-free driver. [ Risks ] Updating the nvidia driver packages in (old)stable to new upstream releases is an established practice. [ Checklist ] [*] *all* changes are documented in the d/changelog [*] I reviewed all changes and I approve them (Excluding the blob parts.) [*] attach debdiff against the package in (old)stable (Excluding the blob parts.) [*] the issue is verified as fixed in unstable [ Changes ] nvidia-graphics-drivers-tesla-470 (470.239.06-1~deb12u1) bookworm; urgency=medium * Rebuild for bookworm. -- Andreas Beckmann Thu, 29 Feb 2024 02:41:42 +0100 nvidia-graphics-drivers-tesla-470 (470.239.06-1) unstable; urgency=medium * New upstream long term support branch release 470.239.06 (2024-02-22). * Fixed CVE-2024-0074, CVE-2024-0078, CVE-2022-42265. (Closes: #1064989) https://nvidia.custhelp.com/app/answers/detail/a_id/5520 * Improved compatibility with recent Linux kernels. [ Andreas Beckmann ] * Refresh patches. -- Andreas Beckmann Wed, 28 Feb 2024 02:22:39 +0100 debian/README.source | 2 +- debian/changelog | 56 +++- debian/control.md5sum | 2 +- ...anagement-features-were-not-yet-in-Linux.patch} | 14 ++- ...-includes-to-fix-module-build-for-ppc64el.patch | 30 +++ debian/module/debian/patches/0034-fix-typos.patch | 18 +++- ...35-fix-build-w-kernel-6.1.76-6.6.15-6.7.3.patch | 99 -- debian/module/debian/patches/bashisms.patch| 2 +- .../debian/patches/cc_version_check-gcc5.patch | 2 +- debian/module/debian/patches/ppc64el.patch | 19 - debian/module/debian/patches/series.in | 5 +- debian/patches/legacy-470.patch| 2 +- debian/rules | 4 +- debian/source/lintian-overrides| 1 + 14 files changed, 122 insertions(+), 134 deletions(-) [ Other info ] This is a rebuild of the package from sid with no further changes. Andreas ngd-tesla-470-470.239.06-1~deb12u1.diff.xz Description: application/xz
Bug#1065013: bullseye-pu: package nvidia-graphics-drivers/470.239.06-1
Package: release.debian.org Severity: normal Tags: bullseye User: release.debian@packages.debian.org Usertags: pu Control: affects -1 + src:nvidia-graphics-drivers [ Reason ] Let's update nvidia-graphics-drivers in bullseye to a new upstream release to fix some CVEs. At the same time I'll switch to the Tesla driver series, i.e. add blobs for ppc64el and enable building the package for ppc64el. (S.t. it is in line with the handling of nvidia-graphics-drivers in stable and sid.) nvidia-cuda-mps will be built from this package instead of src:n-g-d-tesla-470. That makes the package essentially identical to src:nvidia-graphics-drivers-tesla-470. [ Impact ] A proprietary graphics driver with some unfixed CVEs. [ Tests ] The module can only be build-tested, everything else would require use of nvidia hardware and driver. [ Risks ] Updating n-g-d in oldstable to a new upstream release has been done previously without problems. [ Checklist ] [*] *all* changes are documented in the d/changelog [*] I reviewed all changes and I approve them (excluding the blobs) [*] attach debdiff against the package in (old)stable (excluding the binary .run file) [.] the issue is verified as fixed in unstable (so far as src:nvidia-graphics-drivers-tesla-470, src:nvidia-graphics-drivers is still being prepared) [ Changes ] nvidia-graphics-drivers (470.239.06-1) bullseye; urgency=medium * New upstream long term support branch release 470.239.06 (2024-02-22). * Fixed CVE-2024-0074, CVE-2024-0078, CVE-2022-42265. (Closes: #1064983) https://nvidia.custhelp.com/app/answers/detail/a_id/5520 * Improved compatibility with recent Linux kernels. [ Andreas Beckmann ] * Refresh patches. * Upload to bullseye. -- Andreas Beckmann Thu, 29 Feb 2024 00:25:42 +0100 nvidia-graphics-drivers (470.223.02-4) UNRELEASED; urgency=medium * Apply pfn_valid patch from gentoo to fix kernel module build for Linux 6.1.76, 6.6.15, 6.7.3, 6.8. (Closes: #1063361) * Update lintian overrides. -- Andreas Beckmann Thu, 08 Feb 2024 14:23:21 +0100 nvidia-graphics-drivers (470.223.02-3) UNRELEASED; urgency=medium * Switch src:nvidia-graphics-drivers to the Tesla 470 driver series. * Build for ppc64el. * Build all unversioned packages from src:nvidia-graphics-drivers. * New Romanian (ro) debconf translations by Remus-Gabriel Chelu. -- Andreas Beckmann Thu, 25 Jan 2024 19:48:07 +0100 debian/README.source | 63 ++- debian/bug-control.mk | 4 +- debian/changelog | 359 +++-- debian/control | 79 ++-- debian/control.in | 2 +- debian/control.md5sum | 8 +- debian/copyright | 8 +- debian/detect/nvidia-418.ids | 304 -- debian/detect/nvidia-470.ids | 439 - debian/detect/nvidia-detect.in | 76 ++-- debian/gbp.conf| 1 + debian/libnvidia-eglcore.lintian-overrides.in | 1 + debian/libnvidia-glcore.lintian-overrides.in | 1 + ...anagement-features-were-not-yet-in-Linux.patch} | 14 +- ...-includes-to-fix-module-build-for-ppc64el.patch | 30 ++ debian/module/debian/patches/0034-fix-typos.patch | 62 +++ debian/module/debian/patches/bashisms.patch| 2 +- .../debian/patches/cc_version_check-gcc5.patch | 2 +- debian/module/debian/patches/ppc64el.patch | 19 - debian/module/debian/patches/series.in | 5 +- debian/not-installed.in| 5 - debian/nvidia-detect.install | 4 +- debian/patches/legacy-470.patch| 2 +- debian/po/ro.po| 81 debian/rules | 15 +- debian/rules.defs | 9 +- debian/source/lintian-overrides| 1 + debian/tests/autopkgtest-pkg-dkms.conf | 2 +- debian/tests/control | 10 +- debian/tests/control.in| 8 + debian/watch | 8 +- debian/watch.in| 8 +- 32 files changed, 685 insertions(+), 947 deletions(-) The big changelog delta comes from changelog unification when switching to the Tesla drivers. The patch mentioned in 470.223.02-4 has been superseded by the new upstream release. The nvidia-detect changes are part of the switch to the Tesla driver. [ Other info ] This time there is no need to expedite this update via stable-updates. Deviating from stable, I'll not turn src:nvidia-graphics-drivers-tesla-470 into transitional packages (even if it will be identical to src:nvidia
temporarily ignoring autopkgtest failure of src:papi?
Hi, papi currently fails to migrate due to a new superficial autopkgtest failing on !amd64. Fixing that will require making papi-examples arch:any instead of arch:all, but I'd like not to make any further changes right now to not interfere with the 64bit time_t transition. Will fix that after the transition is over. Could you add a hint s.t. the current version (7 days old, needed 5) migrates before papi gets NMUed for the transition? Thanks Andreas
Bug#1057089: bookworm-pu: package usrmerge/37~deb12u1
On 30/11/2023 09.49, Marco d'Itri wrote: On Nov 29, Andreas Beckmann wrote: Improve the usrmerge experience in bookworm. Great idea, thank you for working on this! The bookworm branch and a signed tag can be found in https://salsa.debian.org/anbe/usrmerge.git (IIRC merge requests don't handle tags, therefore I'm not creating one.) Andreas
Bug#1063675: bookworm-pu: package nvidia-graphics-drivers/525.147.05-6~deb12u1
On 15/02/2024 19.54, Jonathan Wiltshire wrote: >Revised draft: ACK. This update addresses problems in three non-free driver packages supporing s/supporing/supporting/ Andreas
Bug#1063675: bookworm-pu: package nvidia-graphics-drivers/525.147.05-6~deb12u1
On 15/02/2024 18.44, Jonathan Wiltshire wrote: On Thu, Feb 15, 2024 at 02:24:05PM +0100, Andreas Beckmann wrote: On 14/02/2024 11.01, Jonathan Wiltshire wrote: On Sun, Feb 11, 2024 at 11:23:00PM +0100, Andreas Beckmann wrote: We need to push 4 packages together to stable-updates: nvidia-graphics-drivers nvidia-settings nvidia-graphics-drivers-tesla-470 nvidia-graphics-drivers-tesla According to my list there's just nvidia-graphics-drivers-tesla missing now; does that match yours? Seems installable in sid now, so just uploaded to PU. These 4 should be ready for stable-updates. Thanks; accepted all four, and the builds have just come in. I can release as early as tonight (19:52) but I don't know if that's a bit of a rush. Should I hang on until tomorrow evening in case of any late-breaking issues? Tomorrow is probably better. We also need to put some thought into an announcement text. Here's a draft starting point: === This update addresses problems in four non-free packages to support nVidia graphics cards. three non-free driver packages ? The Linux kernel update included in Debian 12.5 marked two functions as GPL-only, making them inaccessible to non-free kernel modules. not correct ... The Linux kernel update in Debian 12.5 changed an inlined function to call two GPL-only symbols, making that function inaccessible to non-free kernel modules. As a result, the nVidia kernel modules cannot be built via DKMS at installation time for the updated kernel. This issue could not be resolved in time for the release of Debian 12.5. (And perhaps something along this:) Additionally src:nvidia-graphics-drivers and src:nvidia-settings have been enabled to build for ppc64el, in order to turn src:nvidia-graphics-drivers-tesla into transitional packages to ease future updates. The following packages have been updated to correct the problem. , as well as fixing detection of Tesla 470 compatibility: Drop, that was a regression introduced in -6 and -6~deb12u1, it only existed for a few days. PackageFixed version ===== nvidia-graphics-drivers nvidia-graphics-drivers-tesla nvidia-graphics-drivers-tesla-470 nvidia-settings If you use the affected packages, we recommend you upgrade to these versions. === Feedback? Thanks,
Bug#1063675: bookworm-pu: package nvidia-graphics-drivers/525.147.05-6~deb12u1
On 14/02/2024 11.01, Jonathan Wiltshire wrote: On Sun, Feb 11, 2024 at 11:23:00PM +0100, Andreas Beckmann wrote: We need to push 4 packages together to stable-updates: nvidia-graphics-drivers nvidia-settings nvidia-graphics-drivers-tesla-470 nvidia-graphics-drivers-tesla According to my list there's just nvidia-graphics-drivers-tesla missing now; does that match yours? Seems installable in sid now, so just uploaded to PU. These 4 should be ready for stable-updates. Andreas
Bug#1063933: bookworm-pu: package nvidia-graphics-drivers/525.147.05-7~deb12u1
Package: release.debian.org Severity: normal Tags: bookworm User: release.debian@packages.debian.org Usertags: pu [ Reason ] Regression in nvidia-detect, introduced in 525.147.05-6~deb12u1. [ Impact ] nvidia-detect does not detect cards supported by nvidia-graphics-drivers-tesla-470. [ Tests ] Manual verification of the nvidia-detect fix. [ Risks ] Low. [ 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 (525.147.05-7~deb12u1) bookworm; urgency=medium * Rebuild for bookworm. -- Andreas Beckmann Thu, 15 Feb 2024 01:08:15 +0100 nvidia-graphics-drivers (525.147.05-7) unstable; urgency=medium * nvidia-detect: Fix mismerge breaking Tesla 470 detection. (Closes: #1063910) * Relax dh-dkms build-dependency, satisfied in stable. -- Andreas Beckmann Thu, 15 Feb 2024 00:55:07 +0100 debian/README.source | 2 +- debian/changelog | 17 - debian/control | 1 - debian/control.in | 1 - debian/control.md5sum | 4 ++-- debian/control.models | 2 +- debian/detect/nvidia-detect.in | 2 +- 7 files changed, 21 insertions(+), 8 deletions(-) The versioned dh-dkms B-D has been dropped, because dh-sequence-dkms is sufficient. Simplifies bullseye backports. [ Other info ] I'll directly upload the package after filing this bug. Andreas diff --git a/debian/README.source b/debian/README.source index 8e720253..a03295fa 100644 --- a/debian/README.source +++ b/debian/README.source @@ -65,7 +65,7 @@ The branch structure in the GIT repository tesla-450/transition-470 bullseye,sidtesla-460/transition-470 460 EoL (bullseye) 470, tesla-460/main tesla-460/main EoL (bullseye),(sid)tesla-470/main, tesla-460/transition-470 -tesla-460/transition-470 bullseye,sid +tesla-460/transition-470 bullseye,sidtesla/transition 470 bullseye525, tesla-470/main tesla-470/mainbullseye,bookworm,sid tesla/525 525 EoL bookworm,sid535, tesla/525 diff --git a/debian/changelog b/debian/changelog index b6adb99f..3427ffdd 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,17 @@ +nvidia-graphics-drivers (525.147.05-7~deb12u1) bookworm; urgency=medium + + * Rebuild for bookworm. + + -- Andreas Beckmann Thu, 15 Feb 2024 01:08:15 +0100 + +nvidia-graphics-drivers (525.147.05-7) unstable; urgency=medium + + * nvidia-detect: Fix mismerge breaking Tesla 470 detection. +(Closes: #1063910) + * Relax dh-dkms build-dependency, satisfied in stable. + + -- Andreas Beckmann Thu, 15 Feb 2024 00:55:07 +0100 + nvidia-graphics-drivers (525.147.05-6~deb12u1) bookworm; urgency=medium * Rebuild for bookworm. @@ -1413,7 +1427,7 @@ nvidia-graphics-drivers (460.106.00-14) UNRELEASED; urgency=medium * Apply pfn_valid patch from gentoo to fix kernel module build for Linux 6.1.76, 6.6.15, 6.7.3, 6.8. - -- Andreas Beckmann Wed, 07 Feb 2024 04:12:22 +0100 + -- Andreas Beckmann Tue, 13 Feb 2024 14:49:02 +0100 nvidia-graphics-drivers (460.106.00-13) UNRELEASED; urgency=medium @@ -1559,6 +1573,7 @@ nvidia-graphics-drivers (460.106.00-1) UNRELEASED; urgency=medium * bug-script: Show the nvidia and glx alternatives (470.82.00-1). * nvidia-alternative: libnvidia-cfg.so.1 on its own is not sufficient to activate a nvidia alternative (470.82.00-1). +(Closes: #996595) * Fix bashisms in upstream scripts (470.82.00-1). * Drop the unusable leftover non-GLVND libegl1-nvidia package (470.82.00-1). diff --git a/debian/control b/debian/control index 22264293..abd62e11 100644 --- a/debian/control +++ b/debian/control @@ -13,7 +13,6 @@ Build-Depends: debhelper-compat (= 13), Build-Depends-Arch: dh-sequence-dkms, - dh-dkms (>= 3.0.3-4~), dh-exec, libnvidia-egl-wayland1, libvulkan1 (>= 1.0.42), diff --git a/debian/control.in b/debian/control.in index ed4b6497..994d241e 100644 --- a/debian/control.in +++ b/debian/control.in @@ -11,7 +11,6 @@ Build-Depends: debhelper-compat (= 13), Build-Depends-Arch: dh-sequence-dkms, - dh-dkms (>= 3.0.3-4~), dh-exec, libnvidia-egl-wayland1, libvulkan1 (>= 1.0.42), diff --git a/debian/control.md5sum b/debian/control.md5sum index 0b1209ee..1341f552 100644 --- a/debian/control.md5sum +++ b/debian/control.md5sum @@ -1,5 +1,5 @@ -10952fe89c0b1063bfb28b01dfd73b70 debian/control -ae28324bcc8c570835da30b9d493 debian/control.in +82088c2f83b089d86f743cb5ee877305 debian/control +2f126ed9154b517184ccbac554b1f690 debian/control.in 8489c83cfe0171c9de6d052c01a6d19b debian/gen-control.pl 98a9e959f8732af1a963c2adfb0879ca debian/rules 7f525d302e0e76e1de1f4e6cce0efbe8 debian/rules.def
Bug#1063914: bookworm-pu: package nvidia-graphics-drivers-tesla/525.147.05-7~deb12u1
Package: release.debian.org Severity: normal Tags: bookworm User: release.debian@packages.debian.org Usertags: pu [ Reason ] After integrating src:nvidia-graphics-drivers-tesla into src:nvidia-graphics-drivers we can turn src:nvidia-graphics-drivers-tesla into transitional packages. The pfn_valid patch is also needed for this package. (The transitional packages are not empty but still have their original content. This scheme has been used with previous transitional packages: tesla-450 -> tesla-470, tesla-460 -> tesla-450, tesla-510 -> tesla.) [ Impact ] nvidia-graphics-drivers-tesla is currently unusable in stable due to the module build regression in the point release last weekend.. [ Tests ] Would require use of nvidia hardware and driver. Intial installation tests were done, more installation and upgrade tests with piuparts will follow once the package is in proposed-updates. [ Risks ] The transitional packages need to be checked thoroughly, there were still some dependency issues with -6 in sid. [ 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 ] This package update contains the changes from src:nvidia-graphics-drivers 525.147.05-6~deb12u1 and then turning the packages into transitionals. nvidia-graphics-drivers-tesla (525.147.05-7~deb12u1) bookworm; urgency=medium * Rebuild for bookworm. -- Andreas Beckmann Wed, 14 Feb 2024 17:43:16 +0100 nvidia-graphics-drivers-tesla (525.147.05-7) unstable; urgency=medium * Relax the dependencies on libnvidia*-glcore/libnvidia*-eglcore for the transitional packages. -- Andreas Beckmann Wed, 14 Feb 2024 16:14:35 +0100 nvidia-graphics-drivers (525.147.05-7) UNRELEASED; urgency=medium * nvidia-detect: Fix mismerge breaking Tesla 470 detection. * Relax dh-dkms build-dependency, satisfied in stable. -- Andreas Beckmann Wed, 14 Feb 2024 12:46:50 +0100 nvidia-graphics-drivers (525.147.05-6~deb12u1) bookworm; urgency=medium * Rebuild for bookworm. -- Andreas Beckmann Sun, 11 Feb 2024 02:35:05 +0100 nvidia-graphics-drivers (525.147.05-6) unstable; urgency=medium * Apply pfn_valid patch from gentoo to fix kernel module build for Linux 6.1.76, 6.6.15, 6.7.3, 6.8. (Closes: #1063363, #1062932) * nvidia-detect: Tesla and regular driver packages have been merged. * nvidia-detect: Add superficial autopkgtest for checking codename support. * Update lintian overrides. -- Andreas Beckmann Fri, 09 Feb 2024 20:43:30 +0100 nvidia-graphics-drivers-tesla (525.147.05-6) unstable; urgency=medium * Turn metapackages into transitional packages to aid switching to nvidia-graphics-drivers. * Provide less virtual packages. * Remove the Tesla driver from the nvidia alternative. -- Andreas Beckmann Sun, 04 Feb 2024 00:06:52 +0100 nvidia-graphics-drivers-tesla (525.147.05-5) unstable; urgency=medium * Rebuild as Tesla driver. -- Andreas Beckmann Thu, 25 Jan 2024 21:46:30 +0100 nvidia-graphics-drivers (525.147.05-5) unstable; urgency=medium * Switch src:nvidia-graphics-drivers to the Tesla driver series. * Build for ppc64el. * Build all unversioned packages from src:nvidia-graphics-drivers. * Enable nvidia-suspend-common. (Closes: #1059581, #1056557, #1062281) * nvidia-suspend-common: Depend on kbd for chvt. (Closes: #1058081) * New Romanian (ro) debconf translations by Remus-Gabriel Chelu. (Closes: #1059590) -- Andreas Beckmann Tue, 23 Jan 2024 18:13:36 +0100 debian/README.source | 63 ++- debian/bug-control.mk | 4 +- debian/changelog | 211 -- debian/control | 162 +--- debian/control.in | 295 +++--- debian/control.md5sum | 8 +- debian/control.models | 2 +- debian/copyright | 7 +- debian/detect/nvidia-418.ids | 304 -- debian/detect/nvidia-470.ids | 439 - debian/detect/nvidia-detect.in | 119 +++--- debian/detect/nvidia-tesla.ids | 370 - debian/gbp.conf| 2 +- debian/libnvidia-eglcore.lintian-overrides.in | 1 + debian/libnvidia-glcore.lintian-overrides.in | 1 + debian/not-installed.in| 9 +- debian/nvidia-alternative.postinst.in | 2 +- debian/nvidia-alternative.preinst.in | 7 + debian/nvidia-detect.install | 5 +- debian/nvidia-suspend-common.lintian-overrides | 3 - debian/nvidia.NEWS | 25 ++ debian/pa
Bug#1063823: bullseye-pu: package nvidia-graphics-drivers/470.223.02-2
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
Bug#1063675: bookworm-pu: package nvidia-graphics-drivers/525.147.05-6~deb12u1
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 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?
Bug#1063742: bookworm-pu: package nvidia-settings/525.147.05-1~deb12u1
Package: release.debian.org Severity: normal Tags: bookworm User: release.debian@packages.debian.org Usertags: pu Control: affects -1 +1 src:nvidia-settings [ Reason ] In order to enable building src:nvidia-graphics-drivers for ppc64el (part of the unification with src:nvidia-graphics-drivers-tesla), we also need to enable building src:nvidia-settings for ppc64el, otherwise we get some unsatisfiable dependency. (I'm not trying some magic to use nvidia-settings-tesla which is already built for ppc64el to satisfy that dependency.) [ Impact ] Uninstallable nvidia driver package on ppc64el. [ Tests ] Would require use of nvidia hardware and driver. [ Risks ] Low. No relevant changes besides enabling the package for another architecture. [ 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-settings (525.147.05-1~deb12u1) bookworm; urgency=medium * Rebuild for bookworm. -- Andreas Beckmann Sun, 11 Feb 2024 23:27:34 +0100 nvidia-settings (525.147.05-1) unstable; urgency=medium * New upstream release 525.147.05. * Build for ppc64el. -- Andreas Beckmann Fri, 26 Jan 2024 19:29:45 +0100 debian/changelog | 13 + debian/control| 2 +- debian/copyright | 2 +- debian/salsa-ci.yml | 3 +-- doc/version.mk| 2 +- samples/version.mk| 2 +- src/libXNVCtrl/version.mk | 2 +- src/version.mk| 2 +- version.mk| 2 +- 9 files changed, 21 insertions(+), 9 deletions(-) This is a new upstream release but the only change is the version bump. Since I had to upload the package anyway, I used the latest upstream to be in sync again with the driver. [ Other info ] The is a rebuild of the package from sid with no further changes. Andreas diff --git a/debian/changelog b/debian/changelog index 4c8ff6b..07ad2e7 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,16 @@ +nvidia-settings (525.147.05-1~deb12u1) bookworm; urgency=medium + + * Rebuild for bookworm. + + -- Andreas Beckmann Sun, 11 Feb 2024 23:27:34 +0100 + +nvidia-settings (525.147.05-1) unstable; urgency=medium + + * New upstream release 525.147.05. + * Build for ppc64el. + + -- Andreas Beckmann Fri, 26 Jan 2024 19:29:45 +0100 + nvidia-settings (525.125.06-1~deb12u1) bookworm; urgency=medium * Rebuild for bookworm. diff --git a/debian/control b/debian/control index 20fd7fa..3cd072a 100644 --- a/debian/control +++ b/debian/control @@ -26,7 +26,7 @@ Vcs-Browser: https://salsa.debian.org/nvidia-team/nvidia-settings Vcs-Git: https://salsa.debian.org/nvidia-team/nvidia-settings.git Package: nvidia-settings -Architecture: amd64 arm64 +Architecture: amd64 arm64 ppc64el Pre-Depends: nvidia-installer-cleanup, Depends: diff --git a/debian/copyright b/debian/copyright index d41447d..a606761 100644 --- a/debian/copyright +++ b/debian/copyright @@ -102,7 +102,7 @@ License: Expat Files: debian/* Copyright: © 2004-2010 Randall Donald © 2009-2010 Fathi Boudra - © 2011-2023 Andreas Beckmann + © 2011-2024 Andreas Beckmann © 2017 Luca Boccassi License: GPL-2 diff --git a/debian/salsa-ci.yml b/debian/salsa-ci.yml index 14fa000..c3d1fdf 100644 --- a/debian/salsa-ci.yml +++ b/debian/salsa-ci.yml @@ -1,7 +1,6 @@ --- include: - - https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/salsa-ci.yml - - https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/pipeline-jobs.yml + - https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/recipes/debian.yml variables: SALSA_CI_COMPONENTS: 'main contrib non-free' diff --git a/doc/version.mk b/doc/version.mk index 33fa123..dae35ac 100644 --- a/doc/version.mk +++ b/doc/version.mk @@ -1,4 +1,4 @@ -NVIDIA_VERSION = 525.125.06 +NVIDIA_VERSION = 525.147.05 # This file. VERSION_MK_FILE := $(lastword $(MAKEFILE_LIST)) diff --git a/samples/version.mk b/samples/version.mk index 33fa123..dae35ac 100644 --- a/samples/version.mk +++ b/samples/version.mk @@ -1,4 +1,4 @@ -NVIDIA_VERSION = 525.125.06 +NVIDIA_VERSION = 525.147.05 # This file. VERSION_MK_FILE := $(lastword $(MAKEFILE_LIST)) diff --git a/src/libXNVCtrl/version.mk b/src/libXNVCtrl/version.mk index 33fa123..dae35ac 100644 --- a/src/libXNVCtrl/version.mk +++ b/src/libXNVCtrl/version.mk @@ -1,4 +1,4 @@ -NVIDIA_VERSION = 525.125.06 +NVIDIA_VERSION = 525.147.05 # This file. VERSION_MK_FILE := $(lastword $(MAKEFILE_LIST)) diff --git a/src/version.mk b/src/version.mk index 33fa123..dae35ac 100644 --- a/src/version.mk +++ b/src/version.mk @@ -1,4 +1,4 @@ -NVIDIA_VERSION = 525.125.06 +NVIDIA_VERSION = 525.147.05 # This file. VERSION_MK_FILE := $(lastword $(MAKEFILE_LIST)) diff --git a/version.mk b/version.mk index 33fa123..dae35ac 100644 --- a/version.mk +++ b/version.mk
Bug#1063675: bookworm-pu: package nvidia-graphics-drivers/525.147.05-6~deb12u1
On 11/02/2024 23.13, Jonathan Wiltshire wrote: Yes, I've been watching the trickle of bugs being merged. As soon as Andreas has chance to upload I'll get it out via stable-updates and an SUA issued. src:nvidia-graphics-drivers is already in stable-NEW due to nvidia-suspend-common. We need to push 4 packages together to stable-updates: nvidia-graphics-drivers nvidia-settings nvidia-graphics-drivers-tesla-470 nvidia-graphics-drivers-tesla Andreas
Bug#1063737: bookworm-pu: package nvidia-graphics-drivers-tesla-470/470.223.02-4~deb12u1
Package: release.debian.org Severity: normal Tags: bookworm User: release.debian@packages.debian.org Usertags: pu [ Reason ] 1) A backported (by upstream) change in Linux 6.1.76 (included in today's point release) broke compilation of the non-free nvidia kernel module. A patched version of the driver is available in sid. 2) After merging src:nvidia-graphics-drivers-tesla into src:nvidia-graphics-drivers (PU request for src:nvidia-graphics-drivers is already approved), the nvidia-cuda-mps package will be built from src:nvidia-graphics-drivers, so stop building it here. [ Impact ] Users are unable to use Tesla 470 variant of the non-free nvidia module. [ Tests ] Only module building can be (and has been) tested. Everything else requires use of nvidia hardware and the driver. [ Risks ] Rebuilding nvidia driver packages from sid for stable is an established practice. [ 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-tesla-470 (470.223.02-4~deb12u1) bookworm; urgency=medium * Rebuild for bookworm. -- Andreas Beckmann Sun, 11 Feb 2024 22:11:51 +0100 nvidia-graphics-drivers-tesla-470 (470.223.02-4) unstable; urgency=medium * Apply pfn_valid patch from gentoo to fix kernel module build for Linux 6.1.76, 6.6.15, 6.7.3, 6.8. (Closes: #1063361) * Update lintian overrides. -- Andreas Beckmann Thu, 08 Feb 2024 14:23:21 +0100 nvidia-graphics-drivers-tesla-470 (470.223.02-3) unstable; urgency=medium * nvidia-cuda-mps is again built from src:nvidia-graphics-drivers. -- Andreas Beckmann Thu, 25 Jan 2024 19:48:07 +0100 nvidia-graphics-drivers-tesla-470 (470.223.02-2~deb11u1) bullseye; urgency=medium * Rebuild for bullseye. -- Andreas Beckmann Sun, 03 Dec 2023 13:31:00 +0100 debian/README.source | 61 ++- debian/bug-control.mk | 4 +- debian/changelog | 59 ++- debian/control | 17 - debian/control.in | 7 +- debian/control.md5sum | 8 +- debian/copyright | 7 +- debian/detect/nvidia-418.ids | 304 -- debian/detect/nvidia-470.ids | 439 - debian/detect/nvidia-detect.in | 92 ++--- debian/libnvidia-eglcore.lintian-overrides.in | 1 + debian/libnvidia-glcore.lintian-overrides.in | 1 + debian/module/debian/patches/0034-fix-typos.patch | 48 +++ ...35-fix-build-w-kernel-6.1.76-6.6.15-6.7.3.patch | 99 + debian/module/debian/patches/series.in | 2 + debian/not-installed.in| 5 + debian/nvidia-detect.install | 4 +- debian/nvidia.NEWS | 9 + debian/po/ro.po| 81 debian/rules | 11 +- debian/rules.defs | 9 +- debian/tests/control | 8 + debian/tests/control.in| 8 + debian/watch | 4 +- debian/watch.in| 4 +- 25 files changed, 387 insertions(+), 905 deletions(-) - The nvidia-detect changes are irrelevant here since nvidia-detect is not built from this source package. They are present anyway since I'm keeping all the nvidia driver packaging branches in sync to minimize the difference between them. - unifying src:nvidia-graphics-drivers and src:nvidia-graphics-drivers-tesla brought some changelog synchronization changes as well as packaging synchronization bits [ Other info ] This package too should be made available quickly since several users are affected. stable-updates might be a good idea (once all 4 packages are available in stable-pu: nvidia-graphics-drivers, nvidia-settings, nvidia-graphics-drivers-tesla, nvidia-graphics-drivers-tesla-470). Andreas ngd-tesla-470-470.223.02-4~deb12u1.diff.xz Description: application/xz
Bug#1063675: bookworm-pu: package nvidia-graphics-drivers/525.147.05-6~deb12u1
Package: release.debian.org Severity: normal Tags: bookworm User: release.debian@packages.debian.org Usertags: pu Control: affects -1 + src:nvidia-graphics-drivers Control: block 1063363 with -1 Control: block 1062932 with -1 [ Reason ] 1) A backported (by upstream) change in Linux 6.1.76 (included in today's point release) broke compilation of the non-free nvidia kernel module. A patched version of the driver is available in sid. 2) In order to simplify future maintenance of the many Nvidia driver packages (also in stable and oldstable) I'm going to remove the distinction between "normal" and "Tesla" drivers (they were at the same version in stable anyway). The Tesla specific bits (src:nvidia-graphics-drivers-tesla) will be merged into src:nvidia-graphics-drivers (that mainly means addition of the ppc64el architecture to these packages, and building some binary packages from src:nvidia-graphics-drivers instead: nvidia-powerd, nvidia-cuda-mps). nvidia-detect has been updated, too, as it no longer needs to distinguish the Tesla variants. There will be one further update to src:nvidia-graphics-drivers-tesla in stable that turns these packages into transitional packages depending on their counterparts from src:nvidia-graphics-drivers. (Separate PU request upcoming.) There will also be a PU request for nvidia-settings, as we need to enable building that on ppc64el. (The src:nvidia-settings-tesla package will then become obsolete.) 3) In order to better integrate the nvidia driver with the system power management, a new package nvidia-suspend-common is being introduced which properly ships and enables some systemd units that were previously only being shipped as examples. These power management changes are an enhancement for the 525 series, but seem to be required in the 535 series. (We will have to switch to the 535 LTSB series in stable soon, as 525 has reached EoL. 535 will be supported till mid 2026, so that will be the last driver branch switch for bookworm.) nvidia-suspend-common was already prepared in the previous pu update, but not yet enabled on stable as it hadn't undergone enough testing. As no new issues have popped up on sid, I'm confident to enable this in stable now. [ Impact ] Users are unable to use the non-free nvidia module. [ Tests ] Only module building can be (and has been) tested. Everything else requires use of nvidia hardware and the driver. [ Risks ] This time there is no new upstream release involved, but some larger packaging changes which have been taken unchanged from sid. I prefer to not mix a new upstream version in there as well. [ 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 (525.147.05-6~deb12u1) bookworm; urgency=medium * Rebuild for bookworm. -- Andreas Beckmann Sat, 10 Feb 2024 22:03:15 +0100 nvidia-graphics-drivers (525.147.05-6) unstable; urgency=medium * Apply pfn_valid patch from gentoo to fix kernel module build for Linux 6.1.76, 6.6.15, 6.7.3, 6.8. (Closes: #1063363, #1062932) * nvidia-detect: Tesla and regular driver packages have been merged. * nvidia-detect: Add superficial autopkgtest for checking codename support. * Update lintian overrides. -- Andreas Beckmann Fri, 09 Feb 2024 20:43:30 +0100 nvidia-graphics-drivers (525.147.05-5) unstable; urgency=medium * Switch src:nvidia-graphics-drivers to the Tesla driver series. * Build for ppc64el. * Build all unversioned packages from src:nvidia-graphics-drivers. * Enable nvidia-suspend-common. (Closes: #1059581, #1056557, #1062281) * nvidia-suspend-common: Depend on kbd for chvt. (Closes: #1058081) * New Romanian (ro) debconf translations by Remus-Gabriel Chelu. (Closes: #1059590) -- Andreas Beckmann Tue, 23 Jan 2024 18:13:36 +0100 debian/README.source | 61 ++- debian/bug-control.mk | 4 +- debian/changelog | 406 +-- debian/control | 116 -- debian/control.in | 14 +- debian/control.md5sum | 8 +- debian/copyright | 8 +- debian/detect/nvidia-418.ids | 304 -- debian/detect/nvidia-470.ids | 439 - debian/detect/nvidia-detect.in | 117 +++--- debian/detect/nvidia-tesla.ids | 370 - debian/gbp.conf| 1 + debian/libnvidia-eglcore.lintian-overrides.in | 1 + debian/libnvidia-glcore.lintian-overrides.in | 1 + debian/not-installed.in| 17 - debian/n
Re: openjdk-8 vs. nvidia-openjdk-8-jre
Thomas, if I understand correctly, openjdk-8 is only needed for ancient
third-party software, not for anything in the Debian (main) archive.
But as such software still has a significant userbase, openjdk-8 ist
still being maintained by you and others and in other distributions.
On 19/01/2024 03.38, Thorsten Glaser wrote:
The other side would be nvidia-openjdk-8-jre is in non-free and only
available for two architectures, so less people would install it, and
it’s JRE-only, AFAICT. If worry about people installing openjdk-8 is
a factor, I can understand the split, but from a technical PoV I don’t
see the duplication as a good solution.
nvidia-visual-profiler (which is a customized ancient eclipse with some
proprietary plugins) from src:nvidia-cuda-toolkit in non-free
unfortunately still requires openjdk-8 (and I don't expect that to
change before the visual-profiler gets dropped at some point by upstream
(but I haven't heard any rumours about that, yet)).
nvidia-openjdk-8-jre is simply a repack of the openjdk-8-jre{,-headless}
binary packages from sid (only for amd64 and ppc64el which have
nvidia-visual-profiler, not for arm64 which got CUDA support w/o
visual-profiler a few years later) and it would be trivial to drop that
from src:nvidia-cuda-toolkit (we already do that on Ubuntu and use
openjdk-8-jre there instead).
I'd be in favor of switching to official openjdk-8 packages in main, as
it would simplify my nvidia-cuda-toolkit work ;-) And openjdk-8 in sid
seems to be still well maintained today (it didn't look that way a few
years ago).
Options are probably: keep things as is, drop nvidia-openjdk-8-jre in
favour of openjdk-8 in trixie/sid, or drop it everywhere and build
openjdk-8 for {,{,old}old}stable as well. I don’t mind any, I just
wondered and wanted to provide an impulse to think about this.
If it's going to be reintroduced to (old)*stable/testing, we should
ensure that no package in the archive accidentally pulls it in as part
of its dependency resolution ... i.e. there are no leftover openjdk-8-*
(build) dependency alternatives.
And having openjdk-8-* installed manually should not satisfy the openjdk
(build) dependency of any package in the archive via virtual packages.
Andreas
Bug#1059597: transition: papi
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition I'd like to update papi from libpapi7.0 to libpapi7.1. Only starpu needs a binNMU (builds fine locally). I'll upload a binNMU of starpu-contrib myself since it cannot be autobuilt due to the non-free nvidia-cuda-tookit build-dependency. https://release.debian.org/transitions/html/auto-papi.html Ben file: title = "papi"; is_affected = .depends ~ "libpapi7.0" | .depends ~ "libpapi7.1"; is_good = .depends ~ "libpapi7.1"; is_bad = .depends ~ "libpapi7.0"; Andreas
Bug#1056222: REGRESSIONS! Re: debian-edu-artwork 2.12.3-2~deb12u1 flagged for acceptance
On Fri, 24 Nov 2023 14:35:19 + Adam D Barratt wrote: Package: debian-edu-artwork Version: 2.12.3-2~deb12u1 Explanation: provide an Emerald theme based artwork for Debian Edu 12 This update causes some regressions (#1057815) - it modifies a conffile (/etc/plymouth/plymouthd.conf) - which actually causes dpkg prompting due to modified conffiles on upgrades from bullseye to bookworm+pu Andreas
Bug#1057330: bullseye-pu: package midge/0.2.41+dfsg-1~deb11u1
Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
[ Reason ]
This is a rebuild of the package from sid (and bookworm-pu) to
remove some likely not dfsg-free files.
[ Impact ]
Some possibly not dfsg-free files are installed.
[ Tests ]
none
[ Risks ]
Low, the removed files were only shipped as examples.
There are some additional packaging changes compared to the rebuilt
package going to bookwork-pu, e.g. the switch to source format 3.0.
But I'd prefer not reverting them to produce a new package with even
less testing.
[ 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 ]
Same changes as in 0.2.41+dfsg-1~deb12u1 (bookworm-pu), plus these
changes that happened between 0.2.41-2.1 (bullseye) and 0.2.41-4
(bookworm):
* Convert to 3.0 (quilt) format (Closes: #1007522).
* Set maintainer to Debian QA Group. (see #840288)
* debian/rules: Add build-{arch,indep}. (Closes: #998976)
$ debdiff midge_0.2.41-2.1_all.deb midge_0.2.41+dfsg-1~deb11u1_all.deb
[The following lists of changes regard files as different if they have
different names, permissions or owners.]
Files in first .deb but not in second
-
-rw-r--r-- root/root /usr/share/doc/midge/examples/covers/bobby_brown.mg
-rw-r--r-- root/root
/usr/share/doc/midge/examples/covers/dont_fear_the_reaper.mg
-rw-r--r-- root/root /usr/share/doc/midge/examples/covers/motorhead.mg
-rw-r--r-- root/root /usr/share/doc/midge/examples/covers/one_drop.mg
-rw-r--r-- root/root /usr/share/doc/midge/examples/covers/paranoid.mg
-rw-r--r-- root/root /usr/share/doc/midge/examples/covers/stir_it_up.mg
-rw-r--r-- root/root
/usr/share/doc/midge/examples/covers/too_much_to_dream.mg
-rw-r--r-- root/root /usr/share/doc/midge/examples/covers/wieh.mg
-rw-r--r-- root/root
/usr/share/doc/midge/examples/covers/wish_you_were_here.mg
Control files: lines which differ (wdiff format)
Installed-Size: [-356-] {+340+}
Maintainer: [-Mario Lang -] {+Debian QA Group
+}
Version: [-0.2.41-2.1-] {+0.2.41+dfsg-1~deb11u1+}
[ Other info ]
n/a
Andreas
diff --git a/debian/changelog b/debian/changelog
index efc66ca..eb75fb1 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,41 @@
+midge (0.2.41+dfsg-1~deb11u1) bullseye; urgency=medium
+
+ * QA upload.
+ * Rebuild for bullseye.
+
+ -- Andreas Beckmann Sun, 03 Dec 2023 14:56:30 +0100
+
+midge (0.2.41+dfsg-1~deb12u1) bookworm; urgency=medium
+
+ * QA upload.
+ * Rebuild for bookworm.
+
+ -- Andreas Beckmann Sun, 03 Dec 2023 00:08:22 +0100
+
+midge (0.2.41+dfsg-1) unstable; urgency=medium
+
+ * QA upload.
+ * Switch to copyright-format 1.0.
+ * Repack without examples/covers/*. (Closes: #1056147)
+ * Import package history into GIT.
+
+ -- Andreas Beckmann Wed, 22 Nov 2023 14:07:43 +0100
+
+midge (0.2.41-4) unstable; urgency=medium
+
+ * QA upload.
+ * Convert to 3.0 (quilt) format (Closes: #1007522).
+
+ -- Bastian Germann Thu, 25 Aug 2022 13:52:16 +0200
+
+midge (0.2.41-3) unstable; urgency=medium
+
+ * QA upload.
+ * Set maintainer to Debian QA Group. (see #840288)
+ * debian/rules: Add build-{arch,indep}. (Closes: #998976)
+
+ -- Adrian Bunk Mon, 27 Dec 2021 20:30:06 +0200
+
midge (0.2.41-2.1) unstable; urgency=medium
* Non-maintainer upload.
@@ -64,4 +102,3 @@ midge (0.2.33-1) unstable; urgency=low
* Initial release.
-- David Riley Sat, 24 Aug 2002 22:02:22 +0100
-
diff --git a/debian/control b/debian/control
index 014741e..1df44bd 100644
--- a/debian/control
+++ b/debian/control
@@ -1,10 +1,12 @@
Source: midge
Section: sound
Priority: optional
-Maintainer: Mario Lang
+Maintainer: Debian QA Group
Build-Depends: debhelper (>= 10)
Standards-Version: 3.9.8
Homepage: http://www.undef.org.uk/code/midge
+Vcs-Browser: https://salsa.debian.org/debian/midge
+Vcs-Git: https://salsa.debian.org/debian/midge.git
Package: midge
Architecture: all
diff --git a/debian/copyright b/debian/copyright
index a2e2cfd..a5ebdcc 100644
--- a/debian/copyright
+++ b/debian/copyright
@@ -1,13 +1,29 @@
-This package was debianized by David Riley on Wed
Jan 23 10:34:27 GMT 2002
+Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
+Source: http://www.undef.org.uk/code/midge/
+Upstream-Name: Midge
+Upstream-Contact: David Riley
+Files-Excluded:
+ examples/covers
-It was downloaded from http://www.undef.org.uk/code/midge/
+Files:
+ *
+Copyright:
+ (c) 1999-2002 David Riley
+License: GPL-2.0+
-Upstream author: David Riley
-
-This software is copyright (c) 1999-2002 David Riley.
-
-You are free to distribute this software under the terms of
-the GNU General Public License.
-On Debian systems, the complete text of the GNU General Pub
Bug#1057089: bullseye-pu: package usrmerge/37~deb12u1
Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: usrme...@packages.debian.org
Control: affects -1 + src:usrmerge
[ Reason ]
Improve the usrmerge experience in bookworm.
A few more ancient packages were found that need to be removed first for
usrmerge to succeed, add versioned Breaks against them.
Depending on the time a system was bootstrapped or converted, there may
be biarch directories/links not owned by any package
(e.g. /usr/libx32 and /libx32 -> /usr/libx32)
Since these are now handled by the respective packages from src:glibc,
bootstrapping and conversion no longer create them and we can clean them
up if they are empty and not owned by a package.
Clarify errors in case something goes wrong during usrmerge conversion.
[ Impact ]
Unclear errors if something fails.
Failing usrmerge conversion if certain ancient packages are installed.
Leftover unowned files that may disappear on certain upgrade paths and
confuse CI tools.
Inconsistent handling of /etc/shells and shells.state.
[ Tests ]
Local piuparts tests of bookworm (w/ updated package) and various
distupgrade tests from bullseye (or earlier) to bookworm (w/ updated
package).
[ Risks ]
Low.
[ 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 ]
+usrmerge (37~deb12u1) bookworm; urgency=medium
+
+ * Rebuild for bookworm.
+
+ -- Andreas Beckmann Mon, 27 Nov 2023 11:35:49 +0100
+
+usrmerge (37) unstable; urgency=medium
+
+ [ Johannes Schauer Marin Rodrigues ]
+ * Use $DPKG_ROOT in usr-is-merged.postinst. (Closes: #1050755)
+
+ -- Marco d'Itri Tue, 29 Aug 2023 02:14:10 +0200
+
+usrmerge (36) unstable; urgency=medium
+
+ * Added code by Andreas Beckmann to clean up the biarch libraries
+directories when they are not needed. (Closes: #1038853)
+ * Changed postinst to not run convert-etc-shells again on already
+converted systems and to run update-shells to make sure that the
+new shells.state file introduced in bookworm is up to date.
+(Closes: #1033167)
+ * Improved the instructions to deal with a mounted /lib/modules/,
+which can also happen on some Xen-based systems. (Closes: 1034346)
+ * Greatly improved the error messages when commands execution fails
+(see #1037362).
+ * Added a versioned conflict with libc-bin, only relevant for the
+conversion script. (Closes: #1037362)
+ * Added a versioned conflict with dhcpcd. (Closes: #1038832)
+ * Added a versioned conflict with libparted1.8-10. (Closes: #1038832)
+ * Added a versioned conflict with lustre-utils. (Closes: #1038832)
+
+ -- Marco d'Itri Sun, 27 Aug 2023 13:56:49 +0200
convert-usrmerge | 34 +++---
debian/README.Debian | 6 ++
debian/changelog | 33 +
debian/control| 9 -
debian/usr-is-merged.postinst | 28
debian/usrmerge.postinst | 28 ++--
6 files changed, 116 insertions(+), 22 deletions(-)
[ Other info ]
This is a rebuild of a package that was previously in sid and testing.
(The current version (38) in sid made usrmerge mandatory in all cases
and is not applicable to bookworm (which supports the usrmerge opt-out.)
Andreas
diff --git a/convert-usrmerge b/convert-usrmerge
index e9398f5..00200f3 100755
--- a/convert-usrmerge
+++ b/convert-usrmerge
@@ -28,6 +28,8 @@ my %Ignore_In_Root = map { $_ => 1 } qw(
/lib/udev/hwdb.bin
);
+$ENV{LC_ALL} = 'C';
+
check_free_space();
check_overlayfs();
@@ -217,9 +219,11 @@ sub convert_file {
# To prevent a failure later, the regular files of the libraries used by
# cp and mv must be converted before of the symlinks that point to them.
sub early_conversion_files {
+ no autodie qw(close);
+
open(my $fh, '-|', 'ldd /bin/cp');
my @ldd = <$fh>;
- close $fh;
+ close $fh or fatal("Failed to execute 'ldd /bin/cp'");
# the libraries
my @list = grep { $_ } map { /^\s+\S+ => (\/\S+) / and $1 } @ldd;
@@ -340,9 +344,9 @@ END
##
sub check_free_space {
- local $ENV{LC_ALL} = 'C';
- my $fh;
+ no autodie qw(close);
+ my $fh;
open($fh, '-|', 'stat --dereference --file-system --format="%i" /');
my $root_id = <$fh>;
die "stat / failed" if not defined $root_id;
@@ -361,14 +365,14 @@ sub check_free_space {
my $free = $free_blocks * ($bs / 1024);
my @dirs = grep { -e $_ } directories_to_merge();
- open($fh, '-|',
- "du --summarize --no-dereference --total --block-size=1K
@dirs");
+ my $c
Bug#1057084: bullseye-pu: package nvidia-graphics-drivers-tesla-450/450.248.02-4~deb11u1
Package: release.debian.org Severity: normal Tags: bullseye User: release.debian@packages.debian.org Usertags: pu [ Reason ] The Tesla 450 driver series has reached End of Life. I'd like to turn it into transitional packages to ease switching to the Tesla 470 driver series. We did the same with the Tesla 460 series after that reached EoL last year. The 470 series supports a superset of GPUs, so this switch is not a regression in terms of supported devices or features. [ Impact ] A proprietary EoL graphics driver with more CVEs open. [ Tests ] Only module building has been tested. Anything else would require certain hardware and driver usage. [ Risks ] Low. The same changes have been applied to src:nvidia-graphics-drivers-tesla-470 last year. [ 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 ] There are patches making the module compatible with recent kernels. While these are not needed for oldstable or the transitional packages, I don't want to deviate from what is in sid. There are only minor additional packaging changes. debian/README.source| 19 +- debian/changelog| 84 +++- debian/control | 149 +- debian/control.in | 288 +- debian/control.md5sum | 8 +- debian/gbp.conf | 2 +- ...atch => 0010-backport-pci-dma-changes-for-ppc64el-from-470.223.02.patch} | 21 +- .../patches/0027-backport-get_user_pages-changes-from-520.56.06.patch | 379 ++ .../debian/patches/0028-backport-get_user_pages-changes-from-525.53.patch | 222 .../patches/0029-backport-get_user_pages-changes-from-525.53-uvm-part.patch | 93 + .../patches/0030-backport-get_user_pages-changes-from-535.86.05.patch | 392 .../debian/patches/0031-backport-asm-page.h-changes-from-470.223.02.patch | 69 +++ .../patches/0032-backport-drm_gem_prime_handle_to_fd-changes-from-470.patch | 54 + .../patches/0033-refuse-to-load-legacy-module-if-IBT-is-enabled.patch | 63 ++ debian/module/debian/patches/conftest-verbose.patch | 6 +- debian/module/debian/patches/series.in | 9 +- debian/nvidia-alternative.postinst.in | 2 +- debian/nvidia-alternative.preinst.in| 7 + debian/nvidia-options.conf.in | 6 +- debian/nvidia.NEWS | 13 ++ debian/rules| 7 +- debian/rules.defs | 5 +- debian/tests/control| 8 +- debian/tests/control.in | 8 +- 24 files changed, 1584 insertions(+), 330 deletions(-) [ Other info ] This is a rebuild of the package from sid with no further changes. Ideally this is the last time we have to touch this package in oldstable ;-) Andreas ngd-tesla-450-trans-450.248.02-4~deb11u1.diff.xz Description: application/xz
Bug#1057071: bookworm-pu: package rust-sd/0.7.6-1+deb12u1
Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: rust...@packages.debian.org
[ Reason ]
squeeze had a sd binary package built from (unrelated) src:sd at
version 0.74-1 which is higher than the 0.7.6-1 currently in bookworm
from src:rust-sd, violating version ordering contraints.
0.80 is a made up version higher than any src:sd version ever in the
archive and lower than src:rust-sd 1.0 in sid.
[ Impact ]
Upgrade failures in CI.
[ Tests ]
Local piuparts tests of (hopefully) all affected upgrade paths.
[ Risks ]
Low, the package has no rdepends that could be affectd by the changed
version number.
[ 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 ]
Add the '0.80.really.' prefix to the binary package, needs pkg-info.mk.
$ debdiff sd_0.7.6-1+b3_amd64.deb sd_0.80.really.0.7.6-1+deb12u1_amd64.deb
[The following lists of changes regard files as different if they have
different names, permissions or owners.]
Files in first .deb but not in second
-
-rw-r--r-- root/root /usr/share/doc/sd/changelog.Debian.amd64.gz
Control files: lines which differ (wdiff format)
Installed-Size: [-1919-] {+1918+}
Source: rust-sd [-(0.7.6-1)-] {+(0.7.6-1+deb12u1)+}
Version: [-0.7.6-1+b3-] {+0.80.really.0.7.6-1+deb12u1+}
X-Cargo-Built-Using: rust-aho-corasick (= 0.7.19-1), rust-ansi-term (=
0.12.1-1), rust-atty (= 0.2.14-2), rust-bitflags (= [-1.3.2-2),-] {+1.3.2-3),+}
rust-cfg-if (= 1.0.0-1), rust-clap-2 (= 2.34.0-3), rust-crossbeam-channel (=
0.5.6-1), rust-crossbeam-deque (= 0.8.1-1), rust-crossbeam-epoch (= 0.9.13-1),
rust-crossbeam-utils (= 0.8.12-1), rust-either (= 1.6.1-1), rust-fastrand (=
1.8.0-1), rust-lazy-static (= 1.4.0-2), rust-libc (= 0.2.139-1), rust-memchr (=
2.5.0-1), rust-memmap (= 0.7.0-1), rust-memoffset (= 0.6.5-1), rust-num-cpus (=
1.14.0-1), rust-rayon-core (= 1.10.1-1), rust-rayon (= 1.6.1-1), rust-regex (=
[-1.7.0-1),-] {+1.7.1-1),+} rust-regex-syntax (= 0.6.27-1), rust-remove-dir-all
(= 0.7.0-1), rust-scopeguard (= 1.1.0-1), rust-smawk (= 0.3.1-2), rust-strsim
(= 0.10.0-1), rust-structopt (= 0.3.26-2), rust-tempfile (= 3.3.0-1),
rust-textwrap (= 0.16.0-2), rust-thiserror (= [-1.0.37-1),-] {+1.0.38-1),+}
rust-unescape (= 0.1.0-1), rust-unicode-linebreak (= 0.1.4-1),
rust-unicode-width (= 0.1.10-1), rust-vec-map (= 0.8.1-2), rustc (=
1.63.0+dfsg1-2)
[ Other info ]
n/a
Andreas
diff -Nru rust-sd-0.7.6/debian/changelog rust-sd-0.7.6/debian/changelog
--- rust-sd-0.7.6/debian/changelog 2022-10-09 03:54:37.0 +0200
+++ rust-sd-0.7.6/debian/changelog 2023-11-28 22:27:45.0 +0100
@@ -1,3 +1,12 @@
+rust-sd (0.7.6-1+deb12u1) bookworm; urgency=medium
+
+ * Non-maintainer upload.
+ * Prefix the version of the binary package with '0.80.really.' to sort
+between 0.74-1 in squeeze (from unrelated src:sd) and 1.0.0-1 in sid.
+(Closes: #1037192)
+
+ -- Andreas Beckmann Tue, 28 Nov 2023 22:27:45 +0100
+
rust-sd (0.7.6-1) unstable; urgency=medium
* Package sd 0.7.6 from crates.io using debcargo 2.5.0
diff -Nru rust-sd-0.7.6/debian/rules rust-sd-0.7.6/debian/rules
--- rust-sd-0.7.6/debian/rules 2022-10-09 03:54:37.0 +0200
+++ rust-sd-0.7.6/debian/rules 2023-11-28 22:27:45.0 +0100
@@ -1,7 +1,13 @@
#!/usr/bin/make -f
+
+include /usr/share/dpkg/pkg-info.mk
+
%:
dh $@ --buildsystem cargo
override_dh_installman:
cp $$(find . -name sd.1 | grep release) debian/sd.1
dh_installman -O--buildsystem=cargo
+
+override_dh_gencontrol:
+ dh_gencontrol -- -v0.80.really.$(DEB_VERSION)
Bug#1057070: bookworm-pu: package adequate/0.15.9~deb12u1
Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
[ Reason ]
This is a rebuild of the package from sid to fix the autopkgtests on
!amd64. The symbol-size-mismatch issue can only happen on amd64,
therefore it cannot be reproduced elsewhere. Skip the specific test on
!amd64 (in a generic way).
[ Impact ]
Only failing autopkgtests.
[ Tests ]
autopkgtests in sid passed.
[ Risks ]
Low, only autopkgtests affected.
[ 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 ]
Fix suppression of some perl warnings.
Add support for skipping the build of some test packages.
Skip generating the symbol-size-mismatch test package if the symbol to
be tested has a size of 0.
adequate | 3 ++-
debian/changelog | 27 +++
tests/testpkg/debian/rules | 8
3 files changed, 37 insertions(+), 1 deletion(-)
[ Other info ]
n/a
Andreas
diff --git a/adequate b/adequate
index 0267a0e..dee5442 100755
--- a/adequate
+++ b/adequate
@@ -25,7 +25,8 @@ use warnings;
use v5.14;
no feature 'unicode_strings';
-no if $] >= 5.018, warnings => 'experimental::smartmatch';
+no if $] >= 5.017011, warnings => 'experimental::smartmatch';
+no if $] >= 5.037010, warnings => 'deprecated::smartmatch';
use Attribute::Handlers;
use Cwd;
diff --git a/debian/changelog b/debian/changelog
index f049be2..09eb42b 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,30 @@
+adequate (0.15.9~deb12u1) bookworm; urgency=medium
+
+ * QA upload.
+ * Rebuild for bookworm.
+
+ -- Andreas Beckmann Wed, 29 Nov 2023 07:29:20 +0100
+
+adequate (0.15.9) unstable; urgency=medium
+
+ * QA upload.
+ * Skip symbol-size-mismatch test on architectures where array symbols don't
+include a specific length. (Closes: #1050066)
+
+ -- Andreas Beckmann Thu, 23 Nov 2023 10:06:17 +0100
+
+adequate (0.15.8) unstable; urgency=medium
+
+ * QA upload.
+ * Disable deprecation warnings about smartmatch, given, when in Perl
+5.38.
+This is only a band aid but it buys us time before the feature will be
+removed in perl 5.42 in roughly 2 years.
+Also fix version comparison for smartmatch being experimental warnings.
+(Closes: #1043228)
+
+ -- gregor herrmann Tue, 08 Aug 2023 18:06:34 +0200
+
adequate (0.15.7) unstable; urgency=medium
* QA upload.
diff --git a/tests/testpkg/debian/rules b/tests/testpkg/debian/rules
index f2ad455..f21ebd2 100755
--- a/tests/testpkg/debian/rules
+++ b/tests/testpkg/debian/rules
@@ -35,6 +35,8 @@ override_dh_auto_install:
ln -sf lib$(at)-symsize.so.0 $(tmp)/lib$(at)-symsize.so
$(CC) symsize.c -L$(tmp) -o $(tmp)/$(at)-symsize -l$(at)-symsize
$(CC) -shared -Wl,--soname=lib$(at)-symsize.so.0
-DADEQUATE_SYMBOL_SIZE=42 lib.c -o $(tmp)/lib$(at)-symsize.so.0
+ readelf --wide --symbols $(tmp)/$(at)-symsize | grep
this_symbol_size_varies
+ test "$$(readelf --wide --symbols $(tmp)/$(at)-symsize | grep
this_symbol_size_varies | head -n 1 | awk '{print $$3}')" != "0" || touch
$(tmp)/skip-symbol-size-mismatch
# undefined-symbol
$(CC) -shared -Wl,--soname=lib$(at)-versioning.so.0 lib.c -o
$(tmp)/lib$(at)-versioning.so.0
ln -sf lib$(at)-versioning.so.0 $(tmp)/lib$(at)-versioning.so
@@ -60,6 +62,12 @@ override_dh_strip:
# we build binaries with missing symbols
override_dh_shlibdeps:
+override_dh_gencontrol:
+ dh_gencontrol $(patsubst $(tmp)/skip-%,-N adequate-testpkg-%,$(wildcard
$(tmp)/skip-*))
+
+override_dh_builddeb:
+ dh_builddeb $(patsubst $(tmp)/skip-%,-N adequate-testpkg-%,$(wildcard
$(tmp)/skip-*))
+
execute_after_dh_builddeb:
rm
debian/adequate-testpkg-obsolete-conffile/etc/adequate/test-obsolete-conffile
sed -i -e '/test-obsolete/d'
debian/adequate-testpkg-obsolete-conffile/DEBIAN/conffiles
Bug#1057069: bookworm-pu: package midge/0.2.41+dfsg-1~deb12u1
Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
[ Reason ]
This is a rebuild of the package from sid to remove some likely not
dfsg-free files.
[ Impact ]
Some possibly not dfsg-free files are installed.
[ Tests ]
none
[ Risks ]
Low, the removed files were only shipped as examples.
[ 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 ]
Modernized d/copyright in order to use files-Excluded for repacking.
debian/changelog| 17 -
debian/control | 2 ++
debian/copyright| 38
+++---
debian/gbp.conf | 2 ++
debian/rules| 5 +
debian/watch| 2 +-
examples/covers/bobby_brown.mg | 141
-
examples/covers/dont_fear_the_reaper.mg | 46
--
examples/covers/motorhead.mg| 60
examples/covers/one_drop.mg | 71
---
examples/covers/paranoid.mg | 38
--
examples/covers/stir_it_up.mg | 105
-
examples/covers/too_much_to_dream.mg| 207
---
examples/covers/wieh.mg | 82
--
examples/covers/wish_you_were_here.mg | 78
--
15 files changed, 49 insertions(+), 845 deletions(-)
$ debdiff midge_0.2.41-4_all.deb midge_0.2.41+dfsg-1~deb12u1_all.deb
[The following lists of changes regard files as different if they have
different names, permissions or owners.]
Files in first .deb but not in second
-
-rw-r--r-- root/root /usr/share/doc/midge/examples/covers/bobby_brown.mg
-rw-r--r-- root/root
/usr/share/doc/midge/examples/covers/dont_fear_the_reaper.mg
-rw-r--r-- root/root /usr/share/doc/midge/examples/covers/motorhead.mg
-rw-r--r-- root/root /usr/share/doc/midge/examples/covers/one_drop.mg
-rw-r--r-- root/root /usr/share/doc/midge/examples/covers/paranoid.mg
-rw-r--r-- root/root /usr/share/doc/midge/examples/covers/stir_it_up.mg
-rw-r--r-- root/root
/usr/share/doc/midge/examples/covers/too_much_to_dream.mg
-rw-r--r-- root/root /usr/share/doc/midge/examples/covers/wieh.mg
-rw-r--r-- root/root
/usr/share/doc/midge/examples/covers/wish_you_were_here.mg
Control files: lines which differ (wdiff format)
Installed-Size: [-356-] {+339+}
Version: [-0.2.41-4-] {+0.2.41+dfsg-1~deb12u1+}
[ Other info ]
n/a
Andreas
diff --git a/debian/changelog b/debian/changelog
index b1294a4..6023474 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,19 @@
+midge (0.2.41+dfsg-1~deb12u1) bookworm; urgency=medium
+
+ * QA upload.
+ * Rebuild for bookworm.
+
+ -- Andreas Beckmann Wed, 29 Nov 2023 07:07:30 +0100
+
+midge (0.2.41+dfsg-1) unstable; urgency=medium
+
+ * QA upload.
+ * Switch to copyright-format 1.0.
+ * Repack without examples/covers/*. (Closes: #1056147)
+ * Import package history into GIT.
+
+ -- Andreas Beckmann Wed, 22 Nov 2023 14:07:43 +0100
+
midge (0.2.41-4) unstable; urgency=medium
* QA upload.
@@ -79,4 +95,3 @@ midge (0.2.33-1) unstable; urgency=low
* Initial release.
-- David Riley Sat, 24 Aug 2002 22:02:22 +0100
-
diff --git a/debian/control b/debian/control
index b891d40..1df44bd 100644
--- a/debian/control
+++ b/debian/control
@@ -5,6 +5,8 @@ Maintainer: Debian QA Group
Build-Depends: debhelper (>= 10)
Standards-Version: 3.9.8
Homepage: http://www.undef.org.uk/code/midge
+Vcs-Browser: https://salsa.debian.org/debian/midge
+Vcs-Git: https://salsa.debian.org/debian/midge.git
Package: midge
Architecture: all
diff --git a/debian/copyright b/debian/copyright
index a2e2cfd..a5ebdcc 100644
--- a/debian/copyright
+++ b/debian/copyright
@@ -1,13 +1,29 @@
-This package was debianized by David Riley on Wed
Jan 23 10:34:27 GMT 2002
+Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
+Source: http://www.undef.org
Bug#1056987: bullseye-pu: package ca-certificates-java/20230710~deb12u1
ch /var/lib/ca-certificates-java/fresh
+ fi
+
update_cacerts
fi
diff --git a/debian/ca-certificates-java.triggers
b/debian/ca-certificates-java.triggers
index bde4336..e97bbf5 100644
--- a/debian/ca-certificates-java.triggers
+++ b/debian/ca-certificates-java.triggers
@@ -1,3 +1,2 @@
-interest update-ca-certificates-java
-interest update-ca-certificates-java-fresh
-interest /usr/lib/jvm
+interest-await update-ca-certificates-java
+interest-await update-ca-certificates-java-fresh
diff --git a/debian/changelog b/debian/changelog
index d6bb30f..80a833c 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,38 @@
+ca-certificates-java (20230710~deb12u1) bookworm; urgency=medium
+
+ * Non-maintainer upload.
+ * Rebuild for bookworm. (Closes: #1041419, #1037478, #929685)
+
+ -- Andreas Beckmann Mon, 27 Nov 2023 14:32:55 +0100
+
+ca-certificates-java (20230710) unstable; urgency=medium
+
+ * Add apt-utils to the test dependencies.
+
+ -- Matthias Klose Mon, 10 Jul 2023 09:59:59 +0200
+
+ca-certificates-java (20230707) unstable; urgency=medium
+
+ [ Vladimir Petko ]
+ * Resolve circular JRE dependency:
+- debian/ca-certificates-java.postinst: remove setup_path from "configure"
+ stage.
+- debian/ca-certificates-java.postinst: do "fresh" update if cacerts file
is
+ not found. Certificates are refreshed only in response to the trigger
+ activated by OpenJDK packages.
+- debian/ca-certificates-java.postinst: fix cacert enumeration command for
+ Java 8.
+- debian/control: remove JRE dependency.
+- debian/control: add Breaks condition.
+- debian/tests: add smoke tests.
+- debian/ca-certificates-java.triggers: remove file trigger /usr/jvm,
+ explicitly declare triggers as -await.
+
+ [ Matthias Klose ]
+ * Adjust the breaks for Debian versions.
+
+ -- Matthias Klose Fri, 07 Jul 2023 11:13:17 +0200
+
ca-certificates-java (20230620~deb12u1) bookworm; urgency=medium
* Non-maintainer upload.
diff --git a/debian/control b/debian/control
index 88c04e9..6d93f7b 100644
--- a/debian/control
+++ b/debian/control
@@ -20,7 +20,13 @@ Multi-Arch: foreign
Depends:
ca-certificates (>= 20210120),
${misc:Depends},
- default-jre-headless (>= 2:1.8) | java8-runtime-headless,
+Breaks: openjdk-8-jre-headless (<< 8u382~b04-2~),
+openjdk-11-jre-headless (<< 11.0.19+7~1~),
+openjdk-17-jre-headless (<< 17.0.8~6-3~),
+openjdk-18-jre-headless (<< 18.0.2+9-2ubuntu1~),
+openjdk-19-jre-headless (<< 19.0.2+7-0ubuntu4~),
+openjdk-20-jre-headless (<< 20.0.1+9~1~),
+openjdk-21-jre-headless (<< 21~9ea-1~)
Description: Common CA certificates (JKS keystore)
This package uses the hooks of the ca-certificates package to update the
cacerts JKS keystore used for many java runtimes.
diff --git a/debian/tests/can-convert-keystore
b/debian/tests/can-convert-keystore
new file mode 100644
index 000..b5cdf80
--- /dev/null
+++ b/debian/tests/can-convert-keystore
@@ -0,0 +1,26 @@
+#!/bin/bash
+
+set -e
+
+# GIVEN a PKCS12 Java keystore
+ETCCERTSDIR=/etc/ssl/certs
+CACERTS=$ETCCERTSDIR/java/cacerts
+rm $CACERTS
+keytool -importcert -noprompt -alias Amazon -file
/etc/ssl/certs/Amazon_Root_CA_1.pem -trustcacerts -storepass changeit
-storetype PKCS12 -keystore test.store 2> /dev/null
+apt-get remove -y ca-certificates-java
+
+mkdir -p /etc/ssl/certs/java/
+mkdir -p /var/lib/ca-certificates-java/
+mv test.store $CACERTS
+# WHEN ca-certificates-java is requested to convert the keystore
+touch /var/lib/ca-certificates-java/convert_pkcs12_keystore_to_jks
+
+# THEN conversion is successful
+output=`mktemp`
+apt-get install -y openjdk-8-jre-headless | tee ${output}
+
+if [[ $(grep -L "Entry for alias amazon successfully imported." ${output}) ]];
+then
+echo "Certificates were not imported !!!"
+exit 255
+fi
diff --git a/debian/tests/can-install-jre b/debian/tests/can-install-jre
new file mode 100644
index 000..ce6879e
--- /dev/null
+++ b/debian/tests/can-install-jre
@@ -0,0 +1,28 @@
+#!/bin/bash
+
+set -e
+
+versions=$(apt-cache search jre-headless | awk '{print $1}')
+for version in ${versions}
+do
+# WHEN openjdk-jre-headless package is installed from scratch
+
+# Java 18 is EOL 09.2022 but is present in Lunar so that we could do clean
+# builds. Ignore it in certificate tests
+if [[ ${version} == "openjdk-18-jre-headless" ]];
+then
+continue
+fi
+output=`mktemp`
+echo "installing ${version}"
+apt-get install -y ${version} | tee ${output}
+# THEN installation is successfull
+# AND certificates are updated
+if [[ $(grep -L "Adding debian:Amazon_Root_CA_1.pem" ${output}) ]]; then
+echo "Certificates were not imported !!!"
+exit 255
+fi
+rm $output
+# purge in order to remove keytstore
+apt-get purge -y ca
Bug#1056958: bookworm-pu: package nvidia-graphics-drivers-tesla/525.147.05-3~deb12u1
Package: release.debian.org Severity: normal Tags: bookworm User: release.debian@packages.debian.org Usertags: pu [ Reason ] In oder to fix CVE-2023-31022 we need to upgrade nvidia-graphics-drivers-tesla to a new upstream release. [ Impact ] A proprietary graphics driver with more CVEs open. [ Tests ] Only module building has been tested. Anything else would require certain hardware and driver usage. [ Risks ] Low. Upgrading to a new nvidia driver release in (old-)stable is an established procedure. [ Checklist ] [+] *all* changes are documented in the d/changelog [+] I reviewed all changes and I approve them (excluding the blobs) [+] attach debdiff against the package in (old)stable (excluding the blobs) [+] the issue is verified as fixed in unstable [ Changes ] There is infrastructure prepared for a new binary package (nvidia-suspend-common) that will not yet be enabled in the backport for bookworm (but it is built in sid). (I expect that to be enabled once we switch to the 535 series in bookworm.) There are only minor additional packaging changes. [ Other info ] This is a rebuild of the package from sid with only a minimal change: not enabling nvidia-suspend-common. This package is functionally equivalent to src:nvidia-graphics-drivers 525.147.05-1(~deb12u1). Andreas ngd-tesla-525.147.05-3~deb12u1.diff.xz Description: application/xz
Bug#1056744: bookworm-pu: package nvidia-graphics-drivers/525.147.05-1~deb12u1
Package: release.debian.org Severity: normal Tags: bookworm User: release.debian@packages.debian.org Usertags: pu [ Reason ] In oder to fix CVE-2023-31022 we need to upgrade nvidia-graphics-drivers-tesla-470 to a new upstream release. [ Impact ] A proprietary graphics driver with more CVEs open. [ Tests ] Only module building has been tested. Anything else would require certain hardware and driver usage. [ Risks ] Low. Upgrading to a new nvidia driver release in (old-)stable is an established procedure. [ Checklist ] [*] *all* changes are documented in the d/changelog [*] I reviewed all changes and I approve them (excluding the blobs) [*] attach debdiff against the package in (old)stable (excluding the blobs) [*] the issue is verified as fixed in unstable [ Changes ] There is infrastructure prepared for a new binary package (nvidia-suspend-common) that will not yet be enabled in the backport for bookworm (but it is built in sid from the -tesla package). (I expect that to be enabled once we switch to the 535 series in bookworm.) The nvidia-powerd package is not built from this source but from the -tesla package. The changes were synced from there. There are only minor additional packaging changes, most changes originate from keeping the many driver packages in sync. debian/README.source| 9 +- debian/changelog| 175 debian/control | 2 +- debian/control.in | 13 ++- debian/control.md5sum | 8 +- debian/copyright| 3 +- debian/detect/nvidia-tesla.ids | 4 + debian/not-installed.in | 14 ++- debian/nv-readme.ids| 4 + debian/nvidia-options.conf.in | 12 ++- debian/nvidia-powerd.examples | 2 + debian/nvidia-powerd.install| 2 +- debian/nvidia-suspend-common.install| 5 ++ debian/nvidia-suspend-common.lintian-overrides | 18 .../patches/module/0001-bump-minimum-supported-kernel-version-to-3.10.patch | 4 +- .../module/0002-conftest.sh-remove-empty-lines-from-uts_release-outp.patch | 6 +- debian/patches/module/0010-backport-pci-dma-changes-for-ppc64el.patch | 68 -- debian/patches/module/bashisms.patch| 2 +- debian/patches/module/cc_version_check-gcc5.patch | 2 +- debian/patches/module/conftest-verbose.patch| 8 +- debian/patches/module/series.in | 1 - debian/rules| 12 ++- debian/rules.defs | 6 +- debian/xserver-xorg-video-nvidia.examples | 1 - 24 files changed, 259 insertions(+), 122 deletions(-) [ Other info ] This is a rebuild of the package from sid with only a minimal change: not enabling nvidia-suspend-common. Andreas ngd-525.147.05-1~deb12u1.diff.xz Description: application/xz
Bug#1056741: bookworm-pu: package nvidia-open-gpu-kernel-modules/525.147.05-1~deb12u1
|2 +- src/nvidia/src/kernel/gpu/intr/intr.c |6 - src/nvidia/src/kernel/gpu/mem_mgr/arch/ampere/mem_mgr_ga100.c |2 +- src/nvidia/src/kernel/gpu/mem_mgr/mem_mgr_regions.c |2 +- src/nvidia/src/kernel/gpu/mem_sys/arch/hopper/kern_mem_sys_gh100.c | 176 +- src/nvidia/src/kernel/gpu/nvlink/kernel_nvlink.c| 22 +- src/nvidia/src/kernel/gpu/nvlink/kernel_nvlinkcorelibtrain.c|2 +- src/nvidia/src/kernel/mem_mgr/gpu_vaspace.c |4 +- src/nvidia/src/kernel/mem_mgr/mem_fabric.c | 15 +- src/nvidia/src/kernel/rmapi/client_resource.c |7 +- src/nvidia/src/kernel/virtualization/kernel_vgpu_mgr.c |5 +- src/nvidia/src/libraries/mmu/mmu_walk.c |5 +- src/nvidia/srcs.mk |2 + version.mk |2 +- 114 files changed, 7240 insertions(+), 830 deletions(-) [ Other info ] This is a rebuild of the package from sid with no further changes. Andreas diff --git a/debian/changelog b/debian/changelog index 450cd9e8..ae046c07 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,26 @@ +nvidia-open-gpu-kernel-modules (525.147.05-1~deb12u1) bookworm; urgency=medium + + * Rebuild for bookworm. + + -- Andreas Beckmann Sat, 25 Nov 2023 14:13:56 +0100 + +nvidia-open-gpu-kernel-modules (525.147.05-1) unstable; urgency=medium + + * New upstream production branch release 525.147.05 (2023-10-31). +* Fixed CVE-2023-31022. (Closes: #1055144) + https://nvidia.custhelp.com/app/answers/detail/a_id/5491 + * Refresh patches. + * Fix FTBFS with quilt 0.67. + + -- Andreas Beckmann Wed, 22 Nov 2023 01:17:56 +0100 + +nvidia-open-gpu-kernel-modules (525.125.06-2) unstable; urgency=medium + + * Backport get_user_pages changes from 535.86.05 to fix kernel module build +for Linux 6.5. + + -- Andreas Beckmann Tue, 19 Sep 2023 16:28:49 +0200 + nvidia-open-gpu-kernel-modules (525.125.06-1~deb12u1) bookworm; urgency=medium * Rebuild for bookworm. diff --git a/debian/nvidia-options.conf.in b/debian/nvidia-options.conf.in index 5f878850..014bb5d9 100644 --- a/debian/nvidia-options.conf.in +++ b/debian/nvidia-options.conf.in @@ -1,4 +1,10 @@ #options #MODULE# NVreg_DeviceFileUID=0 NVreg_DeviceFileGID=44 NVreg_DeviceFileMode=0660 -# To enable FastWrites and Sidebus addressing, uncomment these lines -# options #MODULE# NVreg_EnableAGPSBA=1 -# options #MODULE# NVreg_EnableAGPFW=1 + +# To grant performance counter access to unprivileged users, uncomment the following line: +#options #MODULE# NVreg_RestrictProfilingToAdminUsers=0 + +# Uncomment to enable this power management feature: +#options #MODULE# NVreg_PreserveVideoMemoryAllocations=1 + +# Uncomment to enable this power management feature: +#options #MODULE# NVreg_EnableS0ixPowerManagement=1 diff --git a/debian/patches/module/0001-bump-minimum-supported-kernel-version-to-3.10.patch b/debian/patches/module/0001-bump-minimum-supported-kernel-version-to-3.10.patch index ec28d6bd..a015484d 100644 --- a/debian/patches/module/0001-bump-minimum-supported-kernel-version-to-3.10.patch +++ b/debian/patches/module/0001-bump-minimum-supported-kernel-version-to-3.10.patch @@ -1,4 +1,4 @@ -From 07730be40239a5ec2c1c3754807e026a1b41fcfe Mon Sep 17 00:00:00 2001 +From fe3344d88a7c56419d42de6efef5161031c77928 Mon Sep 17 00:00:00 2001 From: Andreas Beckmann Date: Mon, 31 Oct 2022 15:10:08 +0100 Subject: [PATCH] bump minimum supported kernel version to 3.10 @@ -9,7 +9,7 @@ conftest.sh has dropped several tests for features predating 3.10 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/common/inc/nv-linux.h b/common/inc/nv-linux.h -index eeba17d..782e42a 100644 +index 792287b..9f32e4e 100644 --- a/common/inc/nv-linux.h +++ b/common/inc/nv-linux.h @@ -57,8 +57,8 @@ diff --git a/debian/patches/module/0002-conftest.sh-remove-empty-lines-from-uts_release-outp.patch b/debian/patches/module/0002-conftest.sh-remove-empty-lines-from-uts_release-outp.patch index 401122ef..a61d4db4 100644 --- a/debian/patches/module/0002-conftest.sh-remove-empty-lines-from-uts_release-outp.patch +++ b/debian/patches/module/0002-conftest.sh-remove-empty-lines-from-uts_release-outp.patch @@ -1,4 +1,4 @@ -From 25d430ed866f0622b602fa42f6d49a0fb4237679 Mon Sep 17 00:00:00 2001 +From 40b15aa3ac67bfefa097f6a28b24e9d5cd9013a2 Mon Sep 17 00:00:00 2001 From: Andreas Beckmann Date: Mon, 31 Oct 2022 14:40:42 +0100 Subject: [PATCH] conftest.sh: remove empty lines from uts_release output @@ -8,10 +8,10 @@ Subject: [PATCH] conftest.sh: remove empty lines from uts_release output 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/conftest.sh b/conftest.sh
Bug#1056715: bullseye-pu: package nvidia-graphics-drivers-tesla-470/470.223.02-1~deb11u1
Package: release.debian.org Severity: normal Tags: bullseye User: release.debian@packages.debian.org Usertags: pu Control: clone -1 -2 Control: usertags -2 pu Control: tags -2 = bookworm Control: retitle -2 bookworm-pu: package nvidia-graphics-drivers-tesla-470/470.223.02-1~deb12u1 [ Reason ] In oder to fix CVE-2023-31022 we need to upgrade nvidia-graphics-drivers-tesla-470 to a new upstream release. [ Impact ] A proprietary graphics driver with more CVEs open. [ Tests ] Only module building has been tested. Anything else would require certain hardware and driver usage. [ Risks ] Low. Upgrading to a new nvidia driver release in (old-)stable is an established procedure. [ Checklist ] [*] *all* changes are documented in the d/changelog [*] I reviewed all changes and I approve them (excluding the blobs) [*] attach debdiff against the package in (old)stable (excluding the blobs) [*] the issue is verified as fixed in unstable [ Changes ] There is a new patch added which is only relevant for using this driver with a backported Linux 6.2+ on a recent Intel CPU. As the blob parts are not built with Indirect Branch Tracking (IBT) support, the module cannot be used on a CPU+kernel combination that enables IBT by default unless it is booted with ibt=off. There are only minor additional packaging changes. debian/README.source| 9 +- debian/changelog| 165 debian/control | 2 +- debian/control.in | 2 +- debian/control.md5sum | 8 +- debian/copyright| 3 +- .../module/debian/patches/0010-backport-pci-dma-changes-for-ppc64el.patch | 68 --- .../patches/0033-refuse-to-load-legacy-module-if-IBT-is-enabled.patch | 63 ++ debian/module/debian/patches/bashisms.patch | 2 +- debian/module/debian/patches/cc_version_check-gcc5.patch| 2 +- debian/module/debian/patches/conftest-verbose.patch | 6 +- debian/module/debian/patches/linux-2.6.34-dev_pm_info-runtime_auto.patch| 2 +- debian/module/debian/patches/series.in | 2 +- debian/nvidia-options.conf.in | 12 ++- debian/rules| 7 +- debian/rules.defs | 4 +- debian/tests/control| 8 +- debian/tests/control.in | 8 +- 18 files changed, 256 insertions(+), 117 deletions(-) [ Other info ] This is a rebuild of the package from sid with no further changes. The bullseye upload will get an additional "rebuild for bullseye" changelog entry. Andreas ngd-470-470.223.02-1~deb12u1.diff.xz Description: application/xz
Bug#1056138: bullseye-pu: package nvidia-graphics-drivers/470.223.02-1
Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
[ Reason ]
In oder to fix CVE-2023-31022 we need to upgrade nvidia-graphics-drivers
to a new upstream release.
[ Impact ]
A proprietary graphics driver with more CVEs open.
[ Tests ]
Only module building has been tested. Anything else would require
certain hardware and driver usage.
[ Risks ]
Low. Upgrading to a new nvidia driver release in (old-)stable is an
established procedure.
[ Checklist ]
[*] *all* changes are documented in the d/changelog
[*] I reviewed all changes and I approve them
(excluding the blobs)
[*] attach debdiff against the package in (old)stable
(excluding the blobs)
[ ] the issue is verified as fixed in unstable
will be fixed by uploads of src:nvidia-graphics-drivers{,-tesla} 525.*
and src:nvidia-graphics-drivers-tesla-470 to sid soon
[ Changes ]
There is a new patch added which is only relevant for using this driver
with a backported Linux 6.2+ on a recent Intel CPU. As the blob parts
are not built with Indirect Branch Tracking (IBT) support, the module
cannot be used on CPU+kernel combination that enables IBT by default
unless it is booted with ibt=off.
There are only minor additional packaging changes.
[ Other info ]
This package is functionally equivalent to
src:nvidia-graphics-drivers-tesla-470 470.223.02-1 which will soon be in
sid and bookworm-pu.
Andreas
diff --git a/debian/README.source b/debian/README.source
index 4c3ae0a0..ad7d55ba 100644
--- a/debian/README.source
+++ b/debian/README.source
@@ -29,7 +29,7 @@ Upstream support timeframes
Tesla 410 EoL
Tesla 418 (LTSB)03/2022 EoL
Tesla 440 11/2020 EoL
-Tesla 450 (LTSB)07/2023
+Tesla 450 (LTSB)07/2023 EoL
Tesla 460 (PB) 01/2022 EoL
Tesla 470 (LTSB)07/2024
Tesla 510 (PB) 01/2023 EoL
@@ -61,9 +61,10 @@ The branch structure in the GIT repository
418-bullseyeEoL (bullseye) 450, 418-tesla
418-tesla EoL (bullseye) 450-tesla, tesla-418/main
tesla-418/main EoL bullseye,sidtesla-450/main
-450 (bullseye) 460, 450-tesla
-450-tesla (bullseye) 460-tesla, tesla-450/main
-tesla-450/mainbullseye,sidtesla-460/main
+450 EoL (bullseye) 460, 450-tesla
+450-tesla EoL (bullseye) 460-tesla, tesla-450/main
+tesla-450/main EoL (bullseye),(sid)tesla-460/main,
tesla-450/transition-470
+tesla-450/transition-470 bullseye,sidtesla-460/transition-470
460 EoL (bullseye) 470, 460-tesla
460-tesla EoL (bullseye) 470-tesla, tesla-460/main
tesla-460/main EoL (bullseye),(sid)tesla-470/main,
tesla-460/transition-470
diff --git a/debian/changelog b/debian/changelog
index 95a17e09..70ab5236 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,6 +1,44 @@
+nvidia-graphics-drivers (470.223.02-1) bullseye; urgency=medium
+
+ * New upstream long term support branch release 470.223.02 (2023-10-31).
+* Fixed CVE-2023-31022. (Closes: #1055136)
+ https://nvidia.custhelp.com/app/answers/detail/a_id/5491
+- Fixed a bug which caused incorrect reporting of presentation
+ times when using the VK_NV_present_barrier Vulkan extension.
+* Improved compatibility with recent Linux kernels.
+
+ [ Andreas Beckmann ]
+ * Refresh patches.
+ * Upload to bullseye.
+
+ -- Andreas Beckmann Fri, 17 Nov 2023 14:40:09 +0100
+
+nvidia-graphics-drivers (470.199.02-4) UNRELEASED; urgency=medium
+
+ * Refuse to load module if IBT is enabled. (Closes: #1052069)
+ * Switch suggestion from obsolete vulkan-utils to vulkan-tools
+(525.125.06-3). (Closes: #1055503)
+
+ -- Andreas Beckmann Wed, 15 Nov 2023 09:41:22 +0100
+
+nvidia-graphics-drivers (470.199.02-3) UNRELEASED; urgency=medium
+
+ * Revert backport of pin_user_pages changes.
+ * Backport drm_gem_prime_handle_to_fd changes from 470.223.02 to fix kernel
+module build for Linux 6.6.
+
+ -- Andreas Beckmann Fri, 03 Nov 2023 12:03:43 +0100
+
+nvidia-graphics-drivers (470.199.02-2) UNRELEASED; urgency=medium
+
+ * Backport get_user_pages and pin_user_pages changes from 520.56.06,
+525.53 and 535.86.05 to fix kernel module build for Linux 6.5.
+
+ -- Andreas Beckmann Wed, 16 Aug 2023 20:12:16 +0200
+
nvidia-graphics-drivers (470.199.02-1) bullseye; urgency=medium
- * New upstream production branch release 470.199.02 (2023-06-26).
+ * New upstream long term support branch release 470.199.02 (2023-06-26).
* Fixed CVE-2023-25515, CVE-2023-25516. (Closes: #1039678)
https://nvidia.custhelp.com/app/answers/detail/a_id/5468
* Improved compatibility with recent Linux kernels.
@@ -13,16 +51,16 @@ nvidia-graphics-drivers
Bug#1056136: bookworm-pu: package intel-graphics-compiler/1.0.12504.6-1+deb12u1
Package: release.debian.org Severity: normal Tags: bookworm User: release.debian@packages.debian.org Usertags: pu Control: block 1055874 with -1 [ Reason ] A recent rebuild of all packages in bookworm discovered an incompatibility of intel-graphics-compiler/bookworm with intel-vc-intrinsics/bookworm, causing the former to FTBFS. #1055874 The intel-graphics-compiler binaries in bookworm were built against an older version of intel-vc-intrinsics (0.8.1) than what was shipped in bookworm (0.11.0). [ Impact ] src:intel-graphics-compiler does FTBFS in bookworm in case someone wants to rebuild it or a security update needs to happen. [ Tests ] Unfortunately there is no testsuite here, but src:intel-compute-runtime (which heavily uses this package) has one. [ Risks ] The upstream commits required for the fix are larger than I would have liked, but they apply cleanly. There seems to have been some major reorganization in intel-vc-intrinsics. intel-graphics-compiler has only one user: intel-compute-runtime (which is a leaf package), so we cannot break much. intel-vc-intrinsics also has only one user (intel-graphics-compiler), therefore no similar bugs could have occurred elsewhere. [ 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 ] * Replace our patches with the corresponding upstream commits (which are larger, but fix all occurrences of the problems and do this more thoroughly), s.t. subsequent patches apply cleanly. (Only two minor adjustments were needed to make 0002-Changed-relative-paths-in-include-directives.patch apply.) * Cherry-pick (without any adjustments needed) two patches which update the codebase for the changes in intel-vc-intrinsics 0.11.0, making it incompatible with older versions (therefore bumping the b-d version). [ Other info ] I'll upload the fixed package right now. b/debian/changelog | 10 b/debian/control |2 b/debian/patches/0001-Preinstalled-SPIRV-Tools-CMakeFile-fix.patch | 51 b/debian/patches/0002-Changed-relative-paths-in-include-directives.patch | 524 b/debian/patches/0003-Add-multi-indirect-byte-regioning-feature.patch| 162 + b/debian/patches/0004-VC-subtarget-refactoring.patch | 1075 ++ b/debian/patches/series |7 debian/patches/fix-relative-includes.patch | 15 debian/patches/fix-spirv-check.diff | 13 9 files changed, 1827 insertions(+), 32 deletions(-) Andreas intel-graphics-compiler_1.0.12504.6-1+deb12u1.diff.xz Description: application/xz
Re: Upcoming changes to Debian Linux kernel packages
On 03/10/2023 19.30, Bastian Blank wrote: thread. Or freak out because meta packages remain uninstallable in backports for days. ... plus gcc or we change how backports works. If uninstallable packages in backports are a problem, perhaps backports needs something like britney to migrate packages from an uploading area to the publishing area (once a package set is installable, no need for delays). That should solve the problem where several source packages need to be updated together. (It would also solve problems with unsatisfiable dependencies where the backporter-uploaded binaries were built by accident in sid instead of stable, requiring a binNMU before migration.) (but this should be discussed elsewhere) Andreas
Bug#1035464: bullseye-pu: package lttng-modules/2.12.5-1+deb11u1
On Sat, 23 Sep 2023 21:53:12 +0100 "Adam D. Barratt" wrote: On Wed, 2023-05-03 at 11:34 -0400, Michael Jeanson wrote: > Fix the dkms build of lttng-modules against the current bullseye > kernel 5.10.0-22. > Please go ahead; sorry for the delay. Hi Michael, I've uploaded your proposed changes to DELAYED/1 to ensure it gets into the next point release (scheduled for Oct 7). Andreas
Re: Upcoming changes to Debian Linux kernel packages
On 25/09/2023 00.50, Bastian Blank wrote: Already built modules remain until someone deletes it. So you can also switch back to the still installed older kernel version and it will have the still working module available. This is what I expect not to work. Assume I have Linux 6.6 and a third-party gpu driver module installed (so there are dkms and the Linux 6.6 headers as well) and everything is working fine. Then I upgrade the system, which brings Linux 6.7 (along linux-image-6.6 which is kept installed) and a new version of the gpu driver (which adds support for 6.7). So the old gpu module for 6.6 gets removed and a new one is built for 6.7 only (since there are only 6.7 headers now). Unfortunately 6.7 breaks some exotic in-tree driver (which I desperately need), so I need to go back to 6.6. Oops, there is no gpu driver module any more. Recovery now needs manual intervention. I'm not sure which class of bugs you are trying to solve with this proposed unversioned linux-headers change. IMO the current scheme of linux-headers-$version-$abi-$flavor matching linux-image-$version-$abi-$flavor works well. But perhaps something could be improved on the metapackage side. Ideally a user should install either meta-linux-image-without-headers-$flavor OR meta-linux-image-with-headers-$flavor (and ideally installing dkms should "automatically switch" to the with-headers variant, not sure how this could be done). The current scheme of having to install linux-image-$flavor AND linux-headers-$flavor is a bit tricky. I'm open to implement improvements on the dkms side. Andreas PS: the proposed "more versioning in the linux-image packages" will solve some rare dkms issues where modules didn't get rebuilt after linux-headers-* was upgraded but $(uname -r) didn't change
Re: Upcoming changes to Debian Linux kernel packages
On 24/09/2023 15.01, Bastian Blank wrote: ## Kernel modules will be signed with an ephemeral key The modules will not longer be signed using the Secure Boot CA like the EFI kernel image itself. Instead a key will be created during the build and thrown away after. Do I correctly assume that change only affects the modules shipped by the linux-image packages and not third-party modules built with dkms? ## Header and tool packages will not longer contain version This means that only headers of one single version can be available on the system at one time. This might be a bit inconvinient for dkms, as it can't longer build modules for multiple versions. That sounds problematic in case of third party modules. If it is possible to have multiple linux-image-* packages installed, but only headers for one of them, the third-party modules will only be available for one of the kernel versions for sure (maybe there are still old module builds available, but no guarantee especially after the third-party module got updated). This will make switching between different kernel versions difficult to impossible, e.g. it may be hard to go back to a working older kernel version in case the new one does not work properly (or the third-party module cannot be built or does not work for the new version). Regarding getting the correct linux-header-* packages installed for the installed linux-image-* packages: Maybe linux-image-* could have Recommends: linux-headers-* | no-linux-headers s.t. the correct linux-headers-* are installed by default (installation of recommends is enabled by default) for all installed linux-image-* packages. no-linux-headers would be an opt-out package that can be installed manually if someone does not want to get linux-headers-* installed at all. It should never be installed automatically. For dkms it is hard recommend the correct linux-header-* package, right now we have Recommends: linux-headers-generic | linux-headers-686-pae | linux-headers-amd64 | linux-headers which does not really work for the non-default kernel flavor, e.g. the -cloud or -i386 kernel. So some improvement on the kernel side would be nice here. Andreas
Bug#1040925: bookworm-pu: package ca-certificates-java/20230103+x
On 18/08/2023 20.49, Paul Gevers wrote: Hi Jonathan, On 18-08-2023 18:48, Jonathan Wiltshire wrote: I'm therefore inclined to make a stable update sooner than the point release. How does this text sound? | ca-certificates-java, a package to update the cacerts JKS keystore used | for many java runtimes, may fail to install alongside OpenJDK because | of a circular dependency. This is a regression in Debian 11 and 12. The regression is that the problem seems to occur more frequently. I'm not convinced it's an actual regression as the circular dependency problem is known from *before* the bullseye release. The actual regression is in openjdk-XX which removed some undocumented undefined behavior. This was not neccessarily on purpose. ca-certificates-java relied on the fact that an unconfigured openjdk-jre-XX-headless could be used for its configuration, which is no longer the case. ca-certificates-java now has to pre-configure java to a usable state if ca-certificates-java gets configured before openjdk-XX-jre-headless was ever configured. That may happen due to the circular dependency. The current fix may actually cause dpkg trigger cycles (due to the circular dependency), but that's a rare event. IIRC in my piuparts tests of this fix I encountered one new trigger cycle, while fixing about 50-250 installation failures due to the ca-certificates-java failure. (exact numbers are hard to estimate since that failure may not propagate transitively: if installing foo which depends on ca-certifictes-java fails, installing bar which depends on foo (and therefore ca-certificates-java, too) may succeed if apt swaps the configuration order of ca-certificates-java and openjdk-XX-jre-headless. In the long run I'd like to bring the changes to bookworm that break the dependency cycle and postpone the ca-certificates-java setup to a trigger that runs after openjdk-xx-jre-headless got configured. (That won't work for bullseye, since there is too much infrastructure missing in the ca-certificates stack, but in bookworm everything should be prepared, it was just not enabled.) backporting ca-certificates-java from sid to bookworm needs careful auditing of the versions in package relationships and my last attempt on that failed since stable-pu didn't have a sufficiently new openjdk, yet. Andreas
Bug#1042809: nmu: mpich_4.1.1.0-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu nmu mpich_4.1.1.0-1 . ANY . experimental . -m "Rebuild against libslurm39" Andreas
Bug#1040930: bullseye-pu: package ca-certificates-java/20190909+deb11u1
On 23/07/2023 15.01, Jonathan Wiltshire wrote: On Wed, Jul 12, 2023 at 04:11:04PM +0200, Andreas Beckmann wrote: The bullseye-security upload of openjdk-17 broke the very fragile assumption in ca-certificates-java that a jre can be used even before it was configured for the first time. As a result new installations of openjdk-17-jre-headless from bullseye-security (or -pu) (and its circular dependency ca-certificates-java from bookworm) will fail, #1039472, (but upgrades seem to work fine, since the jre has been configured at least once in the past). Please go ahead. Should it be published even before the next point release is scheduled? Uploaded. As this only affects new installs (and a specific configuration order of the packages within the dependency loop) but not upgrades, this probably does not need to be pushed to bullseye-updates. AFAIK there haven't been any user bug reports about this issue, yet, since the breakage happened 4 weeks ago. @doko: branch bullseye and signed tag are available in g...@salsa.debian.org:anbe/ca-certificates-java.git Andreas
Bug#1037188: bullseye-pu: package git/2.30.2-1+deb11u3
Control: tag -1 - moreinfo On 08/07/2023 19.25, Adam D. Barratt wrote: It looks like not all of the postinst was removed - was that intentional? It's presumably harmless, but now leads to a lintian warning, which is why I noticed. :-) That git-el.postinst code was already removed by c4b054cf0e debian: drop support for upgrades from pre-1.7.9.5 versions (Mon Dec 28 20:13:48 2020 -0800) and I missed the opportunity to simply delete the whole file when I backported 67b73aadeb debian: remove git-el package (Mon May 31 15:03:12 2021 -0700). The remaining bits should be harmless (it's a postinst script for a package no longer in d/control), but if you prefer, I can reupload with the cruft bits removed, too. Should save a few brain cycles on future updates ;-) Andreas
Bug#1040860: bookworm-pu: package mrtg/2.17.10-5+deb12u1
Followup-For: Bug #1040860 That proposed update causes a regression in the piuparts bullseye->bookworm upgrade test since debsums reports modified conffiles (while piuparts does not customize any conffile). My impression is that the unmodified old conffile from bullseye overwrites the unmodified new conffile from bookworm. #1041332 My suggestion would be to *not* release 2.17.10-5+deb12u1 with 12.1 next Saturday and revisit this for the 12.2 point release. Andreas
Bug#1036676: transition: nvidia-cuda-toolkit 12
On 11/07/2023 09.09, Sebastian Ramacher wrote: Okay, please go ahead whenevery you are ready. Everything should be ready to migrate. Maybe you can hint mumax3 temporarily out of testing, AUTORM would happen in two weeks. Andreas
Bug#1040925: bookworm-pu: package ca-certificates-java/20230103+x
Followup-For: Bug #1040925
Control: retitle -1 bookworm-pu: package ca-certificates-java/20230620~deb12u1
my suggestion: rebuild the 20230620 package from sid
Andreas
diff --git a/debian/ca-certificates-java.postinst
b/debian/ca-certificates-java.postinst
index 94c6c03..963e248 100644
--- a/debian/ca-certificates-java.postinst
+++ b/debian/ca-certificates-java.postinst
@@ -31,6 +31,13 @@ setup_path()
if [ -x /usr/lib/jvm/$jvm/bin/java ]; then
export JAVA_HOME=/usr/lib/jvm/$jvm
PATH=$JAVA_HOME/bin:$PATH
+ # copy java.security to allow import to function
+
security_conf=/etc/java-${version}-openjdk/security
+ if [ -f ${security_conf}/java.security.dpkg-new
] \
+ && [ ! -f
${security_conf}/java.security ]; then
+ cp
${security_conf}/java.security.dpkg-new \
+
${security_conf}/java.security
+ fi
break 2
fi
done
diff --git a/debian/changelog b/debian/changelog
index c316775..4feceba 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,20 @@
+ca-certificates-java (20230620~deb12u1) bookworm; urgency=medium
+
+ * Rebuild for bookworm. (Closes: #1039472)
+
+ -- Andreas Beckmann Sat, 15 Jul 2023 23:23:25 +0200
+
+ca-certificates-java (20230620) unstable; urgency=medium
+
+ [ Matthias Klose ]
+ * Bump standards version.
+ * Build-depend on default-jdk-headless instead of default-jdk.
+
+ [ Vladimir Petko ]
+ * d/ca-certificates-java.postinst: Work-around not yet configured jre.
+
+ -- Matthias Klose Tue, 20 Jun 2023 06:09:44 +0200
+
ca-certificates-java (20230103) unstable; urgency=medium
* Promote again the JRE recommendation to a dependency. Otherwise
diff --git a/debian/control b/debian/control
index 87cfc5f..88c04e9 100644
--- a/debian/control
+++ b/debian/control
@@ -7,10 +7,10 @@ Uploaders: Matthias Klose ,
Build-Depends:
debhelper-compat (= 13),
dh-sequence-javahelper,
- default-jdk,
+ default-jdk-headless,
junit4,
Rules-Requires-Root: no
-Standards-Version: 4.6.1
+Standards-Version: 4.6.2
Vcs-Git: https://salsa.debian.org/java-team/ca-certificates-java.git
Vcs-Browser: https://salsa.debian.org/java-team/ca-certificates-java
Bug#1041039: bookworm-pu: package nvidia-open-gpu-kernel-modules/525.125.06-1~deb12u1
Package: release.debian.org Severity: normal Tags: bookworm User: release.debian@packages.debian.org Usertags: pu [ Reason ] This is the last package in the current nvidia driver update round, fixing some CVEs. [ Impact ] package would become uninstallable due to the firmware package (from src:nvidia-graphics-drivers(-tesla) getting a version bump. [ Tests ] only module compilation was tested [ Risks ] updating the nvidia driver to a new upstream release is a well established procedure, I hope we can handle nvidia-open-gpu-kernel-modules in the same quality. [ Checklist ] [*] *all* changes are documented in the d/changelog [ ] I reviewed all changes and I approve them Honestly, I didn't verify the upstream diff. 141 files changed, 8435 insertions(+), 6089 deletions(-) But most of that code is also part of the blob in src:nvidia-graphics-drivers. [*] attach debdiff against the package in (old)stable [*] the issue is verified as fixed in unstable [ Changes ] A new upstream release. Our patches are in sync with src:nvidia-graphics-drivers (same upstream version branch). [ Other info ] The package is already uploaded. Andreas
Bug#1040951: bookworm-pu: package dhcpcd5/9.4.1-24+deb12u1
Package: release.debian.org Severity: normal Tags: bookworm User: release.debian@packages.debian.org Usertags: pu X-Debbugs-Cc: martin-eric.rac...@iki.fi Control: affects -1 + src:dhcpcd5 [ Reason ] The dhcpcd binary package last existed in wheezy with an epoch of 1: and got reintroduced in bookworm without epoch. Add back the epoch to have only increasing version numbers in the archive. At the same time clean up leftovers from the wheezy package. [ Impact ] incomplete upgrade if dhcpcd/wheezy is still installed [ Tests ] local piuparts upgrade tests [ Risks ] low, there are no versioned dependencies within the package that could be invalidated by adding the epoch [ 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 ] + * Backported Wheezy upgrade mitigation from unstable (see #1037190): ++ Include /usr/share/dpkg/pkg-info.mk needed for target version mingling. ++ Add epoch to bin:dhcpcd via override_dh_gencontrol. + Wheezy had (1:3.2.3-11+deb7u1) so reintroduce the epoch for one target. ++ Add dhcpcd.preinst by Andreas Beckmann to cleanup upgrade leftovers. [ Other info ] Andreas diff -Nru dhcpcd5-9.4.1/debian/changelog dhcpcd5-9.4.1/debian/changelog --- dhcpcd5-9.4.1/debian/changelog 2023-05-29 10:45:31.0 +0300 +++ dhcpcd5-9.4.1/debian/changelog 2023-07-09 22:22:47.0 +0300 @@ -1,6 +1,16 @@ +dhcpcd5 (9.4.1-24+deb12u1) stable-proposed-updates; urgency=medium + + * Backported Wheezy upgrade mitigation from unstable (see #1037190): ++ Include /usr/share/dpkg/pkg-info.mk needed for target version mingling. ++ Add epoch to bin:dhcpcd via override_dh_gencontrol. + Wheezy had (1:3.2.3-11+deb7u1) so reintroduce the epoch for one target. ++ Add dhcpcd.preinst by Andreas Beckmann to cleanup upgrade leftovers. + + -- Martin-Éric Racine Sun, 09 Jul 2023 22:22:47 +0300 + dhcpcd5 (9.4.1-24) unstable; urgency=medium - * Upload to unstable + * Upload to unstable. -- Martin-Éric Racine Mon, 29 May 2023 15:45:31 +0800 diff -Nru dhcpcd5-9.4.1/debian/copyright dhcpcd5-9.4.1/debian/copyright --- dhcpcd5-9.4.1/debian/copyright 2023-05-24 16:29:33.0 +0300 +++ dhcpcd5-9.4.1/debian/copyright 2023-07-09 22:09:15.0 +0300 @@ -4,7 +4,7 @@ Upstream-Contact: Roy Marples Files: * -Copyright: 2006-2018 Roy Marples +Copyright: 2006-2023 Roy Marples 1999, 2016 The NetBSD Foundation, Inc. 2005 Colin Percival 2005 The DragonFly Project. All rights reserved. @@ -68,6 +68,7 @@ 2015 Daniel Echeverry 2018 Scott Leggett 2022-2023 Martin-Éric Racine + 2023 Andreas Beckmann License: BSD-2 Files: debian/hooks/* diff -Nru dhcpcd5-9.4.1/debian/dhcpcd.preinst dhcpcd5-9.4.1/debian/dhcpcd.preinst --- dhcpcd5-9.4.1/debian/dhcpcd.preinst 1970-01-01 02:00:00.0 +0200 +++ dhcpcd5-9.4.1/debian/dhcpcd.preinst 2023-07-09 22:07:22.0 +0300 @@ -0,0 +1,14 @@ +#!/bin/sh +# As per Debian bug #1037190. +# Copyright 2023 Andreas Beckmann +set -e +if dpkg --compare-versions "$2" lt-nl "1:9.4.1-24+deb12u1~" ; then + # Cleanup leftovers from dhcpcd 1:3.* in Wheezy. + # Can be removed after Trixie is released. + update-alternatives --remove dhcpcd /sbin/dhcpcd3 + if [ -d /etc/dhcpc ]; then +test ! -h /etc/dhcpc/resolv.conf || rm -fv /etc/dhcpc/resolv.conf +rmdir --ignore-fail-on-non-empty /etc/dhcpc + fi +fi +#DEBHELPER# diff -Nru dhcpcd5-9.4.1/debian/rules dhcpcd5-9.4.1/debian/rules --- dhcpcd5-9.4.1/debian/rules 2023-05-24 16:29:33.0 +0300 +++ dhcpcd5-9.4.1/debian/rules 2023-07-09 22:14:37.0 +0300 @@ -1,4 +1,5 @@ #!/usr/bin/make -f +include /usr/share/dpkg/pkg-info.mk export DEB_BUILD_MAINT_OPTIONS = hardening=+all @@ -12,8 +13,12 @@ --libexecdir=/usr/lib/dhcpcd \ --rundir=/run/dhcpcd -# avoid starting the unconfigured service as it may break connectivity +# Wheezy had (1:3.2.3-11+deb7u1) so reintroduce the epoch for one target. +override_dh_gencontrol: + dh_gencontrol --package=dhcpcd -- -v1:$(DEB_VERSION_UPSTREAM_REVISION) + dh_gencontrol --remaining-packages +# Avoid starting the unconfigured service as it may break connectivity. override_dh_installinit: dh_installinit --name=dhcpcd --no-start
Bug#1040938: bookworm-pu: package nvidia-graphics-drivers-tesla/525.125.06-1~deb12u1
Package: release.debian.org Severity: normal Tags: bookworm User: release.debian@packages.debian.org Usertags: pu [ Reason ] Let's update nvidia-graphics-drivers-tesla in bookworm to a new upstream release fixing some CVEs. [ Impact ] A proprietary graphics driver with more CVEs open. [ Tests ] Only module building has been tested. Anything else would require certain hardware and driver usage. [ Risks ] Low. Upgrading to a new nvidia driver release in stable is an established procedure. [ Checklist ] [*] *all* changes are documented in the d/changelog [*] I reviewed all changes and I approve them (excluding the blobs) [*] attach debdiff against the package in (old)stable (excluding the blobs) [*] the issue is verified as fixed in unstable [ Changes ] This is a rebuild of src:nvidia-graphics-drivers-tesla/sid with no further changes. It is more or less identical to src:nvidia-graphics-drivers in sid and bookworm(-pu). [ Other info ] The package is already uploaded. Andreas
Bug#1040932: bookworm-pu: package nvidia-graphics-drivers/525.125.06-1~deb12u1
Package: release.debian.org Severity: normal Tags: bookworm User: release.debian@packages.debian.org Usertags: pu [ Reason ] Let's update nvidia-graphics-drivers in bookworm to a new upstream release fixing some CVEs. [ Impact ] A proprietary graphics driver with more CVEs open. [ Tests ] Only module building has been tested. Anything else would require certain hardware and driver usage. [ Risks ] Low. Upgrading to a new nvidia driver release in stable is an established procedure. [ Checklist ] [x] *all* changes are documented in the d/changelog [x] I reviewed all changes and I approve them (excluding the blobs) [x] attach debdiff against the package in (old)stable (excluding the blobs) [x] the issue is verified as fixed in unstable [ Changes ] This is a rebuild of src:nvidia-graphics-drivers/sid with no further changes. [ Other info ] The package is already uploaded. Andreas diff --git a/debian/README.source b/debian/README.source index 05196920..4c3ae0a0 100644 --- a/debian/README.source +++ b/debian/README.source @@ -33,8 +33,9 @@ Upstream support timeframes Tesla 460 (PB) 01/2022 EoL Tesla 470 (LTSB)07/2024 Tesla 510 (PB) 01/2023 EoL -Tesla 515 (PB) 05/2023 +Tesla 515 (PB) 05/2023 EoL Tesla 525 (PB) 12/2023 +Tesla 535 (LTSB)06/2026 The branch structure in the GIT repository @@ -67,20 +68,15 @@ The branch structure in the GIT repository 460-tesla EoL (bullseye) 470-tesla, tesla-460/main tesla-460/main EoL (bullseye),(sid)tesla-470/main, tesla-460/transition-470 tesla-460/transition-470 bullseye,sid -470 bullseye510, 470-tesla -470-tesla (bullseye) 510-tesla, tesla-470/main -tesla-470/mainbullseye,bookworm,sid tesla-510/main -510 EoL (bookworm),sid 515, 510-tesla -510-tesla EoL (bookworm) 515-tesla, tesla-510/main -tesla-510/main EoL (bookworm),(sid)tesla/510, tesla-510/transition -tesla-510/transition sid -tesla/510 EoL (bookworm),sid tesla/515 -515 (bookworm),sid 525, 515-tesla -515-tesla (bookworm) 525-tesla, tesla/515 -tesla/515 (bookworm),sid tesla/525 -525 (bookworm),sid YYY, 525-tesla -525-tesla (bookworm) ZZZ-tesla, tesla/525 -tesla/525 (bookworm),sid tesla/ZZZ +470 bullseye525, 470-tesla +470-tesla (bullseye) 525-tesla, tesla-470/main +tesla-470/mainbullseye,bookworm,sid tesla/525 +525 bookworm,sid535, 525-tesla +525-tesla (bookworm) 535-tesla, tesla/525 +tesla/525 bookworm,sidtesla/535 +535 bookworm,sidYYY, 535-tesla +535-tesla (bookworm) ZZZ-tesla, tesla/535 +tesla/535 bookworm,sidtesla/ZZZ main sid YYY tesla/mainsid YYY experimentalZZZ, (main) diff --git a/debian/changelog b/debian/changelog index dd18087f..edd3661c 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,48 @@ +nvidia-graphics-drivers (525.125.06-1~deb12u1) bookworm; urgency=medium + + * Rebuild for bookworm. + + -- Andreas Beckmann Wed, 12 Jul 2023 16:16:16 +0200 + +nvidia-graphics-drivers (525.125.06-1) unstable; urgency=medium + + * New upstream production branch release 525.125.06 (2023-05-09). +* Fixed CVE-2023-25515, CVE-2023-25516. (Closes: #1039678) + https://nvidia.custhelp.com/app/answers/detail/a_id/5468 +- Fixed a bug which prevented running a Wayland compositor in headless + mode on GPUs without display hardware. + + [ Andreas Beckmann ] + * Update nv-readme.ids. + + -- Andreas Beckmann Wed, 12 Jul 2023 09:52:32 +0200 + +nvidia-graphics-drivers (525.116.04-1) unstable; urgency=medium + + * New upstream production branch release 525.116.04 (2023-05-09). + * New upstream production branch release 525.116.03 (2023-04-25). +- Fixed a regression in Luxmark performance between 525.89.02 and + 525.105.17. +- Fixed a bug that could cause an unexpected + VK_ERROR_NATIVE_WINDOW_IN_USE_KHR error in certain circumstances when + recreating Vulkan surfaces. +- Fixed a regression that caused brightness control to not vary + smoothly across the range of values. +* Improved compatibility with recent Linux kernels. + + [ Andreas Beckmann ] + * Refresh patches. + * Update nv-readme.ids. + + -- Andreas Beckmann Wed, 28 Jun 2023 01:19:51 +0200 + +nvidia-graphics-drivers (525.105.17-2) unstable; urgency
Bug#1040930: bullseye-pu: package ca-certificates-java/20190909+deb11u1
Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: Matthias Klose
[ Reason ]
The bullseye-security upload of openjdk-17 broke the very fragile
assumption in ca-certificates-java that a jre can be used even
before it was configured for the first time.
As a result new installations of openjdk-17-jre-headless from
bullseye-security (or -pu) (and its circular dependency
ca-certificates-java from bookworm) will fail, #1039472, (but
upgrades seem to work fine, since the jre has been configured at
least once in the past).
[ Impact ]
openjdk will fail on new installations after the next point release
[ Tests ]
local piuparts tests of bullseye with the fixed package installed,
buster->bullseye with the fixed package in the upgrade path and
bullseye->bookworm starting from the fixed package.
All installation/upgrades work fine.
[ Risks ]
The hack may break with the next openjdk-17 upload to oldstable, but
there is no alternative solution as trigger support is not yet prepared
in bullseye.
[ 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 ]
In case ca-certificates-java wants to run with a not-yet-configured-once
jre, try to temporarily place a java.security file to make the java
command runnable again.
[ Other info ]
The patch is a backported variant of the HACK that temporarily appeared
in sid (ca-certificates-java 20230620).
Andreas
>From f020db198e9e96dbc9ddaf4b3dbe3d9247b85ae5 Mon Sep 17 00:00:00 2001
From: Matthias Klose
Date: Tue, 20 Jun 2023 06:13:02 +0200
Subject: [PATCH] [ Vladimir Petko ] * d/ca-certificates-java.postinst:
Work-around not yet configured jre.
(cherry picked from commit 561054ed46afe59b5996974e168418362c872d20)
---
debian/changelog | 8
debian/postinst | 7 +++
2 files changed, 15 insertions(+)
diff --git a/debian/changelog b/debian/changelog
index e35274e..a49805a 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+ca-certificates-java (20190909+deb11u1) bullseye; urgency=medium
+
+ [ Vladimir Petko ]
+ * d/ca-certificates-java.postinst: Work-around not yet configured jre.
+(Closes: #1039472)
+
+ -- Andreas Beckmann Tue, 27 Jun 2023 01:12:19 +0200
+
ca-certificates-java (20190909) unstable; urgency=medium
* Team upload.
diff --git a/debian/postinst b/debian/postinst
index 555f87b..7d68036 100644
--- a/debian/postinst
+++ b/debian/postinst
@@ -50,6 +50,13 @@ setup_path()
if [ -x /usr/lib/jvm/$jvm/bin/java ]; then
export JAVA_HOME=/usr/lib/jvm/$jvm
PATH=$JAVA_HOME/bin:$PATH
+ # copy java.security to allow import to function
+ security_conf=/etc/${jvm%-${arch}}/security
+ if [ -f ${security_conf}/java.security.dpkg-new ] \
+ && [ ! -f ${security_conf}/java.security ]; then
+ cp -v ${security_conf}/java.security.dpkg-new \
+ ${security_conf}/java.security
+ fi
break
fi
done
--
2.20.1
Bug#1040925: bookworm-pu: package ca-certificates-java/20230103+x
Package: release.debian.org Severity: normal Tags: bookworm User: release.debian@packages.debian.org Usertags: pu X-Debbugs-Cc: Matthias Klose This request comes without a patch since I don't know how to properly fix it in stable. But it definitively needs to be addressed for the point release because the bookworm-security upload of openjdk-17 broke the very fragile assumption in ca-certificates-java that a jre can be used even before it was configured for the first time. As a result new installations of openjdk-17-jre-headless from bookworm-security (or -pu) (and its circular dependency ca-certificates-java from bookworm) will fail, #1039472, (but upgrades seem to work fine, since the jre has been configured at least once in the past). bookworm had the packages prepared to move the java certificate setup to trigger processing (after the jre got configured) and break the dependency loop, but in the end this was not activated before the bookworm release. It is now enabled in sid. I tried rebuilding the sid package for bookworm, but that is not installable since it has Breaks against jre versions newer than what is in bookworm-security. I'm not sure if the Breaks really need to be that strict (because some new feature is being used) or whether they could be relaxed for bookworm. Andreas
Bug#1040921: bullseye-pu: package dkms/3.0.10-8+deb12u1
Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
[ Reason ]
While earlier dkms versions didn't return an error if dkms failed to
build a kernel module for some kernel (one had to check the log output
to notice this), the version in bookworm does actually indicate that in
the return code. This causes unwanted failures if some cruft *-dkms
packages predating bullseye are still installed and fail to build a
module for the bookworm kernel.
Let's add some Breaks against such *-dkms packages that have no upgrade
path (because there is no newer version in bookworm), to ensure they get
removed early enough during the upgrade.
[ Impact ]
Upgrade from bullseye to bookworm fails if some pre-bullseye cruft
*-dkms in stil installed and needs manual fixup.
[ Tests ]
local piuparts tests starting from ancient releases that exposed these
bugs are now passing again
[ Risks ]
None, the breaks are against package versions neither in bookworm or
bullseye.
[ 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 ]
Add Breaks against some ancient *-dkms packages not in bullseye and
bookworm. Versioned in a way to not be broken in case fixed versions
would appear in bookworm-backports.
[ Other info ]
The package is already uploaded.
Andreas
diff --git a/debian/changelog b/debian/changelog
index 24da0ec..a5d87cd 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+dkms (3.0.10-8+deb12u1) bookworm; urgency=medium
+
+ * Add Breaks against obsolete *-dkms packages that are incompatible with the
+Linux 6.1 kernel in bookworm. (Closes: #1037425)
+
+ -- Andreas Beckmann Wed, 12 Jul 2023 13:43:22 +0200
+
dkms (3.0.10-8) unstable; urgency=medium
* Disable tests broken by fix-builtin-archive-dkms-coinstallation.patch.
diff --git a/debian/control b/debian/control
index 73a13db..69d328c 100644
--- a/debian/control
+++ b/debian/control
@@ -28,6 +28,15 @@ Recommends: fakeroot,
sudo,
linux-headers-generic | linux-headers-686-pae | linux-headers-amd64 |
linux-headers,
Suggests: menu, e2fsprogs
+Breaks:
+# in buster, not in bullseye
+ sl-modem-dkms (<< 2.9.11~20110321-16.0),
+# in stretch, not in buster
+ blktap-dkms (<< 2.0.93-0.10.0),
+# in jessie, not in stretch
+ oss4-dkms (<< 4.2-build2020-1~),
+# in wheezy, not in jessie
+ blcr-dkms (<< 0.8.6~b3-1.0),
Provides:
dkms-autopkgtest (= ${binary:Version}),
Description: Dynamic Kernel Module System (DKMS)
diff --git a/debian/gbp.conf b/debian/gbp.conf
index cec628c..cabf8bc 100644
--- a/debian/gbp.conf
+++ b/debian/gbp.conf
@@ -1,2 +1,3 @@
[DEFAULT]
pristine-tar = True
+debian-branch = bookworm
Bug#1040890: bullseye-pu: package nvidia-settings-tesla/525.125.06-1~deb12u1
Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
[ Reason ]
This is a rebuild of nvidia-settings/525.125.06-1~deb12u1 as
nvidia-settings-tesla/525.125.06-1~deb12u1 fixing a potential crash.
[ Impact ]
minor bugfix
[ Tests ]
none, requires nvidia GPU and driver usage to be tested
[ Risks ]
low, in contrib
[ 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 ]
[ Other info ]
I prefer to keep nvidia-settings and nvidia-settings-tesla in sync.
Andreas
diff --git a/debian/changelog b/debian/changelog
index f3df7e0..bddb60e 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,33 @@
+nvidia-settings-tesla (525.125.06-1~deb12u1) bookworm; urgency=medium
+
+ * Rebuild for bookworm.
+
+ -- Andreas Beckmann Wed, 12 Jul 2023 01:19:40 +0200
+
+nvidia-settings-tesla (525.125.06-1) unstable; urgency=medium
+
+ * Rebuild as nvidia-settings-tesla.
+
+ -- Andreas Beckmann Wed, 12 Jul 2023 00:04:57 +0200
+
+nvidia-settings (525.125.06-1) unstable; urgency=medium
+
+ * New upstream release 525.125.06.
+ * New upstream release 525.105.17.
+- Fixed a bug that could cause the nvidia-settings control panel to
+ crash when resetting the display layout.
+ * Upload to unstable.
+
+ -- Andreas Beckmann Tue, 11 Jul 2023 23:27:45 +0200
+
+nvidia-settings (525.85.05-2) experimental; urgency=medium
+
+ * Move source package back to contrib.
+ * libxnvctrl0, libxnvctrl-dev are now built by src:libxnvctrl.
+ * Upload to experimental.
+
+ -- Andreas Beckmann Tue, 18 Apr 2023 22:28:02 +0200
+
nvidia-settings-tesla (525.85.05-1) unstable; urgency=medium
* Rebuild as nvidia-settings-tesla.
diff --git a/debian/copyright b/debian/copyright
index 1c62a8b..d41447d 100644
--- a/debian/copyright
+++ b/debian/copyright
@@ -10,7 +10,7 @@ Disclaimer:
proprietary NVIDIA drivers in non-free.
Files: *
-Copyright: (C) 2004-2021 NVIDIA Corporation
+Copyright: (C) 2004-2023 NVIDIA Corporation
License: GPL-2
Files: samples/*
diff --git a/doc/version.mk b/doc/version.mk
index 36f5738..33fa123 100644
--- a/doc/version.mk
+++ b/doc/version.mk
@@ -1,4 +1,4 @@
-NVIDIA_VERSION = 525.85.05
+NVIDIA_VERSION = 525.125.06
# This file.
VERSION_MK_FILE := $(lastword $(MAKEFILE_LIST))
diff --git a/samples/version.mk b/samples/version.mk
index 36f5738..33fa123 100644
--- a/samples/version.mk
+++ b/samples/version.mk
@@ -1,4 +1,4 @@
-NVIDIA_VERSION = 525.85.05
+NVIDIA_VERSION = 525.125.06
# This file.
VERSION_MK_FILE := $(lastword $(MAKEFILE_LIST))
diff --git a/src/gtk+-2.x/ctkslimm.c b/src/gtk+-2.x/ctkslimm.c
index ed1ca88..d476f59 100644
--- a/src/gtk+-2.x/ctkslimm.c
+++ b/src/gtk+-2.x/ctkslimm.c
@@ -1292,7 +1292,7 @@ static nvDisplayPtr setup_display(CtkMMDialog
*ctk_mmdialog)
void update_mosaic_dialog_ui(CtkMMDialog *ctk_mmdialog, nvLayoutPtr layout)
{
nvModeLineItemPtr iter;
-char *id;
+char *id = NULL;
if (ctk_mmdialog == NULL) {
return;
@@ -1300,6 +1300,7 @@ void update_mosaic_dialog_ui(CtkMMDialog *ctk_mmdialog,
nvLayoutPtr layout)
if (layout) {
ctk_mmdialog->layout = layout;
+ctk_mmdialog->cur_modeline = NULL;
}
parse_slimm_layout(ctk_mmdialog,
@@ -1307,12 +1308,14 @@ void update_mosaic_dialog_ui(CtkMMDialog *ctk_mmdialog,
nvLayoutPtr layout)
_mmdialog->h_overlap_parsed,
_mmdialog->v_overlap_parsed);
-id = g_strdup(ctk_mmdialog->cur_modeline->data.identifier);
+if (ctk_mmdialog->cur_modeline) {
+id = g_strdup(ctk_mmdialog->cur_modeline->data.identifier);
+}
setup_display(ctk_mmdialog);
iter = ctk_mmdialog->modelines;
-while (iter->next) {
+while (id && iter->next) {
if (strcmp(id, iter->modeline->data.identifier) == 0) {
ctk_mmdialog->cur_modeline = iter->modeline;
break;
diff --git a/src/libXNVCtrl/version.mk b/src/libXNVCtrl/version.mk
index 36f5738..33fa123 100644
--- a/src/libXNVCtrl/version.mk
+++ b/src/libXNVCtrl/version.mk
@@ -1,4 +1,4 @@
-NVIDIA_VERSION = 525.85.05
+NVIDIA_VERSION = 525.125.06
# This file.
VERSION_MK_FILE := $(lastword $(MAKEFILE_LIST))
diff --git a/src/nvml.h b/src/nvml.h
index 0da0f8c..9ac2324 100644
--- a/src/nvml.h
+++ b/src/nvml.h
@@ -1,5 +1,5 @@
/*
- * Copyright 1993-2022 NVIDIA Corporation. All rights reserved.
+ * Copyright 1993-2023 NVIDIA Corporation. All rights reserved.
*
* NOTICE TO USER:
*
@@ -525,6 +525,7 @@ typedef enum nvmlValueType_enum
NVML_VALUE_TYPE_UNSIGNED_LONG = 2,
NVML_VALUE_TYPE_UNSIGNED_LONG_LONG = 3,
NVML_VALUE_TYPE_SIGNED_LONG_LONG = 4,
+NVML_VALUE_TYPE_SIGNED_INT = 5,
// Keep this last
NVML_VALUE_TYPE_C
Bug#1040881: bookworm-pu: package llvm-defaults/0.55.7~deb12u1
Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: Sylvestre Ledru
Control: affects -1 + src:llvm-defaults
[ Reason ]
Since some of the libraries build from the llvm suites are not
co-installable (this is expressed by Conflicts/Replaces/Provides of a
virtual package), this is sometimes tricky for apt to figure out since
it involves removing an installed package in order to install another
one with the same score ...
Adding more Breaks against the default versions from oldstable moves the
scores in favor of installing the new packages and removing the obsolete
ones.
There was also a bad symlink in the liblld-dev package, which as
pointing to lldb headers ...
[ Impact ]
Upgrades may have kept some packages at the version from oldstable even
though there is a newer version in stable.
[ Tests ]
I've performed local piuparts bullseye->bookworm upgrade tests with the
patched packages as upgrade targets and it has resolved all incomplete
upgrade issues.
[ Risks ]
Low. All the new Breaks are against packages not in bookworm, so
should not affect new installations.
[ 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 ]
* Add Breaks against not co-installable packages for smoother upgrades from
bullseye. (Closes: #1036580)
* Fix /usr/include/lld symlink. (Closes: #1036577)
* Silent the breaks-without-version lintian warnings
[ Other info ]
n/a
Andreas
diff --git a/debian/changelog b/debian/changelog
index ac0c76b..9873b51 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,21 @@
+llvm-defaults (0.55.7~deb12u1) bookworm; urgency=medium
+
+ * Rebuild for bookworm.
+
+ -- Andreas Beckmann Tue, 11 Jul 2023 22:52:44 +0200
+
+llvm-defaults (0.55.7) unstable; urgency=medium
+
+ [ Andreas Beckmann ]
+ * Add Breaks against not co-installable packages for smoother upgrades from
+bullseye. (Closes: #1036580)
+ * Fix /usr/include/lld symlink. (Closes: #1036577)
+
+ [ Sylvestre Ledru ]
+ * Silent the breaks-without-version lintian warnings
+
+ -- Sylvestre Ledru Tue, 11 Jul 2023 13:00:54 +0200
+
llvm-defaults (0.55.6) unstable; urgency=medium
* Add s390x in the lld supported archs
diff --git a/debian/control b/debian/control
index 051a071..44e1959 100644
--- a/debian/control
+++ b/debian/control
@@ -254,6 +254,7 @@ Architecture: any
Section: libdevel
Depends: ${shlibs:Depends}, ${misc:Depends},
liblldb-${pv:llvm}-dev ${reqv:llvm}
+Breaks: lldb-11, python3-lldb-11
Multi-Arch: same
Description: Next generation, high-performance debugger, header files
LLDB is a next generation, high-performance debugger. It is built as a set of
@@ -266,6 +267,7 @@ Package: lldb
Architecture: any
Depends: lldb-${pv:llvm} ${reqv:llvm}, ${misc:Depends}
Pre-Depends: ${misc:Pre-Depends}
+Breaks: lldb-11, python3-lldb-11
Multi-Arch: same
Description: Next generation, high-performance debugger
LLDB is a next generation, high-performance debugger. It is built as a set of
@@ -308,7 +310,7 @@ Section: python
Architecture: any
Depends: python3-lldb-${pv:llvm} ${reqv:llvm}, ${misc:Depends}
Replaces: python-lldb (<< 0.49~exp2)
-Breaks: python-lldb (<< 0.49~exp2)
+Breaks: python-lldb (<< 0.49~exp2), python3-lldb-11
Description: Next generation, high-performance debugger, python lib
LLDB is a next generation, high-performance debugger. It is built as a set of
reusable components which highly leverage existing libraries in the larger
LLVM
@@ -348,6 +350,7 @@ Architecture: any
Multi-Arch: same
Pre-Depends: ${misc:Pre-Depends}
Depends: libc++1-${pv:llvm} ${reqv:llvm}, ${shlibs:Depends}, ${misc:Depends}
+Breaks: libc++1-11, libc++abi1-11
Description: LLVM C++ Standard library
libc++ is another implementation of the C++ standard library.
.
@@ -368,6 +371,7 @@ Section: libdevel
Architecture: any
Multi-Arch: same
Depends: libc++-${pv:llvm}-dev ${reqv:llvm}, ${misc:Depends}
+Breaks: libc++1-11, libc++abi1-11
Description: LLVM C++ Standard library (development files)
libc++ is another implementation of the C++ standard library
.
@@ -390,6 +394,7 @@ Architecture: any
Multi-Arch: same
Pre-Depends: ${misc:Pre-Depends}
Depends: libc++abi1-${pv:llvm} ${reqv:llvm}, ${shlibs:Depends}, ${misc:Depends}
+Breaks: libc++abi1-11
Description: LLVM low level support for a standard C++ library
libc++abi is another implementation of low level support for a standard C++
library.
@@ -407,6 +412,7 @@ Section: libdevel
Architecture: any
Multi-Arch: same
Depends: libc++abi-${pv:llvm}-dev ${reqv:llvm}, ${misc:Depends}
+Breaks: libc++abi1-11
Description: LLVM low level support for a standard C++ library (development
files)
libc++abi is another implementation of low level support for a standard C++
library.
dif
Bug#1040770: bookworm-pu: package nvidia-settings/525.125.06-1~deb12u1
Package: release.debian.org Severity: normal Tags: bookworm User: release.debian@packages.debian.org Usertags: pu [ Reason ] In prepararion to upgrading nvidia-graphics-drivers(-tesla) to the 535 series (a new LTSB branch announced last week and supported until June 2026, i.e. sufficient for bookworm) I'd like to split src:nvidia-settings (building binary packages in main and contrib) into src:libxnvctrl (in main) and src:nvidia-settings (in contrib). src:libxnvctrl will most likely see no further updates over the lifetime of bookworm, while src:nvidia-settings will need new upstream releases going into stable as the driver packages get updated. As a side effect of this decoupling, bin:nvidia-settings will no longer be a key package, removing a lot of contrib and non-free packages from the key package set. At the same time I'd like to update nvidia-settings to a new upstream release fixing a crash. [ Impact ] Maintaining the new (split style) in sid/trixie and the old (merged style) in bookworm while updating src:nvidia-settings in bookworm for updated src:nvidia-drivers(-tesla) versions will be much more difficult and less tested than doing the package split in stable, too, and just rebuilding the packages from sid later on. (This does not affect bullseye which cannot be updated beyond the 470 driver series, so no more nvidia-settings updates are expected there.) [ Tests ] diffoscope showed binary identical (excluding metadata) nvidia-settings packages built using old- and new-style packaging (and the same upstream version). [ Risks ] Low, with these changes updating nvidia-settings no longer touches main. [ 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 the NEW package is is ready in experimental, and I'll upload it to both sid and bookworm if this request (and the corresoding one for src:libxnvcrl) is granted. [ Changes ] The packaging changes are mostly for removing the libxnvctrl packages and bringing the src:nvidia-settings packaging in sync with src:nvidia-settings-tesla(-*) (now src:nvidia-settings and src:nvidia-settings-tesla are identical packaging-wise). nvml.h (the biggest part of the upstream diff) is only used internally. (libnvidia-ml-dev from src:nvidia-cuda-toolkit ships nvml.h) [ Other info ] This package may require stable-NEW processing. (src from main to contrib) Andreas nvidia-settings.525.125.06-1~deb12u1.diff.xz Description: application/xz
