Bug#1036904: bookworm-pu: package libreoffice/4:7.4.7-1
Hi, Am 12.07.23 um 23:01 schrieb Jonathan Wiltshire: Control: tag -1 confirmed [...] The version is fine. It may or may not make it into 12.1 depending on build times; we'll do our best. Uploaded, thanks. Regards, Rene
NEW changes in stable-new
Processing changes file: schleuder-cli_0.1.0-4+deb12u1_all-buildd.changes ACCEPT
NEW changes in stable-new
Processing changes file: desktop-base_12.0.6+nmu1~deb12u1_all-buildd.changes ACCEPT Processing changes file: node-webpack_5.75.0+dfsg+~cs17.16.14-1+deb12u1_all-buildd.changes ACCEPT
Processed: bookworm-pu: package sra-sdk/3.0.3+dfsg-6~deb12u1
Processing control commands: > affects -1 + src:sra-sdk Bug #1040953 [release.debian.org] bookworm-pu: package sra-sdk/3.0.3+dfsg-6~deb12u1 Added indication that 1040953 affects src:sra-sdk -- 1040953: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040953 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1040953: bookworm-pu: package sra-sdk/3.0.3+dfsg-6~deb12u1
Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: sra-...@packages.debian.org
Control: affects -1 + src:sra-sdk
[ Reason ]
Per #1039621, the new libngs-jni package accidentally wound up with
bad content (unexpanded variables in the key symlink's source *and*
target) that rendered it useless.
[ Impact ]
This package's reverse dependencies, from libngs-java on up, will be
broken unless libncbi-ngs-dev happens to be installed.
[ Tests ]
Various affected packages have autopkgtests, but they evidently missed
the relevant bug, having presumably wound up running with
libncbi-ngs-dev additionally installed. (The tests did catch the
need for architecture restrictions that made it into bookworm, FWIW.)
[ Risks ]
Minimal -- trivial fix, working in testing and unstable with no
further changes from stable.
[ Checklist ]
[*] *all* changes are documented in the d/changelog
[v] I reviewed all changes and I approve them
[v] attach debdiff against the package in (old)stable
[v] the issue is verified as fixed in unstable
[ Changes ]
Tweak debian/rules to make the necessary substitutions in
libngs-java.links.in.
[ Other info ]
In reviewing the debdiff, I see that one of my teammates pushed a
debian/salsa-ci.yml update without a corresponding changelog note that
consequently slipped into -6 undocumented; what should I do about it
at this point?
I've held off on cleaning up a long-dangling symlink in a different
binary package (sra-toolkit, #1040391) but can readily throw that in
if you'd like.
diff -Nru sra-sdk-3.0.3+dfsg/debian/.gitignore
sra-sdk-3.0.3+dfsg/debian/.gitignore
--- sra-sdk-3.0.3+dfsg/debian/.gitignore2023-02-24 05:52:27.0
-0500
+++ sra-sdk-3.0.3+dfsg/debian/.gitignore1969-12-31 19:00:00.0
-0500
@@ -1,16 +0,0 @@
-*.debhelper
-*.substvars
-.debhelper
-.javahelper_clean
-debhelper-build-stamp
-files
-lib*-dev
-lib*[0-9]
-libngs-java
-libngs-java-doc
-libngs-java-doc.doc-base.javadoc
-libngs-jni
-libngs-jni.links
-python3-ngs
-sra-toolkit
-tmp
diff -Nru sra-sdk-3.0.3+dfsg/debian/changelog
sra-sdk-3.0.3+dfsg/debian/changelog
--- sra-sdk-3.0.3+dfsg/debian/changelog 2023-02-24 05:52:27.0 -0500
+++ sra-sdk-3.0.3+dfsg/debian/changelog 2023-07-12 22:20:14.0 -0400
@@ -1,3 +1,16 @@
+sra-sdk (3.0.3+dfsg-6~deb12u1) bookworm; urgency=medium
+
+ * Reupload to bookworm (stable). (Closes: #10n).
+
+ -- Aaron M. Ucko Wed, 12 Jul 2023 22:20:14 -0400
+
+sra-sdk (3.0.3+dfsg-6) unstable; urgency=high
+
+ * debian/rules: Expand $(DEB_HOST_MULTIARCH) in libngs-java.links.in.
+(Closes: #1039621.)
+
+ -- Aaron M. Ucko Tue, 27 Jun 2023 22:14:41 -0400
+
sra-sdk (3.0.3+dfsg-5) unstable; urgency=medium
* Limit libngs-java to those architectures where libs are available
diff -Nru sra-sdk-3.0.3+dfsg/debian/rules sra-sdk-3.0.3+dfsg/debian/rules
--- sra-sdk-3.0.3+dfsg/debian/rules 2023-02-24 05:52:27.0 -0500
+++ sra-sdk-3.0.3+dfsg/debian/rules 2023-07-12 22:19:10.0 -0400
@@ -152,7 +152,10 @@
execute_before_dh_link:
# Putting the upstream version number (without the dfsg part) at the
end of
# symlink source in the -jni package.
- sed 's/\(#STRIPPED_UPSTREAM_VERSION#\)/\1$(DEB_VERSION_UPSTREAM)/;
s/#STRIPPED_UPSTREAM_VERSION#\(.*\)+dfsg[0-9]*/\1/' debian/libngs-jni.links.in
> debian/libngs-jni.links
+ sed -e 's/\(#STRIPPED_UPSTREAM_VERSION#\)/\1$(DEB_VERSION_UPSTREAM)/' \
+ -e 's/#STRIPPED_UPSTREAM_VERSION#\(.*\)+dfsg[0-9]*/\1/' \
+ -e 's/\$$[({]DEB_HOST_MULTIARCH[)}]/$(DEB_HOST_MULTIARCH)/g' \
+ debian/libngs-jni.links.in > debian/libngs-jni.links
# require network, not automatically run
# use it when the pom file must be re-downloaded from maven repo
diff -Nru sra-sdk-3.0.3+dfsg/debian/salsa-ci.yml
sra-sdk-3.0.3+dfsg/debian/salsa-ci.yml
--- sra-sdk-3.0.3+dfsg/debian/salsa-ci.yml 2023-02-24 05:52:27.0
-0500
+++ sra-sdk-3.0.3+dfsg/debian/salsa-ci.yml 2023-07-12 22:19:10.0
-0400
@@ -2,3 +2,7 @@
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
+
+variables:
+# Does not build on i386
+ SALSA_CI_DISABLE_BUILD_PACKAGE_I386: 1
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
Processed: bookworm-pu: package dhcpcd5/9.4.1-24+deb12u1
Processing control commands: > affects -1 + src:dhcpcd5 Bug #1040951 [release.debian.org] bookworm-pu: package dhcpcd5/9.4.1-24+deb12u1 Added indication that 1040951 affects src:dhcpcd5 -- 1040951: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040951 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
NEW changes in stable-new
Processing changes file: node-tough-cookie_4.0.0-2+deb12u1_all-buildd.changes ACCEPT Processing changes file: nvidia-modprobe_535.54.03-1~deb12u1_amd64-buildd.changes ACCEPT Processing changes file: nvidia-modprobe_535.54.03-1~deb12u1_arm64-buildd.changes ACCEPT Processing changes file: nvidia-modprobe_535.54.03-1~deb12u1_armhf-buildd.changes ACCEPT Processing changes file: nvidia-modprobe_535.54.03-1~deb12u1_i386-buildd.changes ACCEPT Processing changes file: nvidia-modprobe_535.54.03-1~deb12u1_ppc64el-buildd.changes ACCEPT
Bug#1040950: bullseye-pu: package autofs/5.1.7-1+deb11u1
Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: aut...@packages.debian.org
Control: affects -1 + src:autofs
Two issues have recently been addressed in autofs uploads to unstable.
[ Reason ]
Fixed issues:
* Don't let NFSv4-only mounts use rpcbind portmapper service.
* Fix missing unlock in sasl_do_kinit_ext_cc().
[ Impact ]
Fix autofs hanging for LDAP+Kerberos setups. Avoid communication to
rpcbind for NFSv4-only mounts.
[ Tests ]
Manually, on production site, by bug submitters.
[ Risks ]
Regressions in autofs.
[ 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 ]
+ * debian/patches:
++ Add fix-nfs4-only-mounts-should-not-use-rpcbind.patch. Don't let NFSv4-
+ only mounts use rpcbind portmapper service. (Closes: #1034261).
++ Add fix-missing-unlock-in-sasl-do-kinit-ext-cc.patch. Fix missing unlock
+ in sasl_do_kinit_ext_cc(). (Closes: #1039967).
[ Other info ]
Salvatore Bonnacorso (@carnil) will likely follow up this pu with another
pu. Not sure if he gets around to it before the deadline for the next
11.x point release.
diff -Nru autofs-5.1.7/debian/changelog autofs-5.1.7/debian/changelog
--- autofs-5.1.7/debian/changelog 2021-02-04 13:36:20.0 +0100
+++ autofs-5.1.7/debian/changelog 2023-07-10 19:01:17.0 +0200
@@ -1,3 +1,13 @@
+autofs (5.1.7-1+deb11u1) bullseye; urgency=medium
+
+ * debian/patches:
++ Add fix-nfs4-only-mounts-should-not-use-rpcbind.patch. Don't let NFSv4-
+ only mounts use rpcbind portmapper service. (Closes: #1034261).
++ Add fix-missing-unlock-in-sasl-do-kinit-ext-cc.patch. Fix missing unlock
+ in sasl_do_kinit_ext_cc(). (Closes: #1039967).
+
+ -- Mike Gabriel Mon, 10 Jul 2023 19:01:17 +0200
+
autofs (5.1.7-1) unstable; urgency=medium
* New upstream release.
diff -Nru
autofs-5.1.7/debian/patches/fix-missing-unlock-in-sasl-do-kinit-ext-cc.patch
autofs-5.1.7/debian/patches/fix-missing-unlock-in-sasl-do-kinit-ext-cc.patch
---
autofs-5.1.7/debian/patches/fix-missing-unlock-in-sasl-do-kinit-ext-cc.patch
1970-01-01 01:00:00.0 +0100
+++
autofs-5.1.7/debian/patches/fix-missing-unlock-in-sasl-do-kinit-ext-cc.patch
2023-07-05 12:14:29.0 +0200
@@ -0,0 +1,45 @@
+From b2571ed0df973a6dc6a8e661874655fa7cecdc37 Mon Sep 17 00:00:00 2001
+From: James Dingwall
+Date: Wed, 20 Jul 2022 13:22:38 +0800
+Subject: autofs-5.1.8 - fix missing unlock in sasl_do_kinit_ext_cc()
+
+There is a missing mutex unlock in function sasl_do_kinit_ext_cc(),
+fix it.
+
+Signed-off-by: James Dingwall
+Signed-off-by: Ian Kent
+---
+# CHANGELOG| 1 +
+ modules/cyrus-sasl.c | 4
+ 2 files changed, 5 insertions(+)
+
+#diff --git a/CHANGELOG b/CHANGELOG
+#index 1f7c93a..e0b285d 100644
+#--- a/CHANGELOG
+#+++ b/CHANGELOG
+#@@ -27,6 +27,7 @@
+# - add autofs_strerror_r() helper for musl.
+# - update configure.
+# - handle innetgr() not present in musl.
+#+- fix missing unlock in sasl_do_kinit_ext_cc().
+#
+# 19/10/2021 autofs-5.1.8
+# - add xdr_exports().
+diff --git a/modules/cyrus-sasl.c b/modules/cyrus-sasl.c
+index ae046e0..738e363 100644
+--- a/modules/cyrus-sasl.c
b/modules/cyrus-sasl.c
+@@ -721,6 +721,10 @@ sasl_do_kinit_ext_cc(unsigned logopt, struct
lookup_context *ctxt)
+
+ debug(logopt, "Kerberos authentication was successful!");
+
++ status = pthread_mutex_unlock(&krb5cc_mutex);
++ if (status)
++ fatal(status);
++
+ return 0;
+
+ out_cleanup_def_princ:
+--
+cgit
+
diff -Nru
autofs-5.1.7/debian/patches/fix-nfs4-only-mounts-should-not-use-rpcbind.patch
autofs-5.1.7/debian/patches/fix-nfs4-only-mounts-should-not-use-rpcbind.patch
---
autofs-5.1.7/debian/patches/fix-nfs4-only-mounts-should-not-use-rpcbind.patch
1970-01-01 01:00:00.0 +0100
+++
autofs-5.1.7/debian/patches/fix-nfs4-only-mounts-should-not-use-rpcbind.patch
2023-07-05 12:14:29.0 +0200
@@ -0,0 +1,97 @@
+From 80845bbcbc264f19c6c6a81d680e1f2b1ea6d3cc Mon Sep 17 00:00:00 2001
+From: Ian Kent
+Date: Sun, 31 Oct 2021 07:36:16 +0800
+Subject: autofs-5.1.8 - fix nfsv4 only mounts should not use rpcbind
+
+Commit 606795ecfaa1 ("autofs-5.1.7 - also require TCP_REQUESTED when
+setting NFS port" together with commit 26fb6b5408be) caused NFSv4 only
+mounts to also use rpcbind to probe availability which breaks the
+requirememt that this type of mount not use rpcbind at all.
+
+Fix this by treating fstype=nfs4 mounts as a special case which doesn't
+use rpcbind.
+
+Signed-off-by: Ian Kent
+---
+# CHANGELOG| 1 +
+ include/replicated.h | 2 ++
+ modules/mount_nfs.c | 13 +++--
+ modules/replicated.c | 4 ++--
+ 4 files changed, 12 insertions(+), 8 deletions(-)
+
+#diff --git a/CHAN
Processed: bullseye-pu: package autofs/5.1.7-1+deb11u1
Processing control commands: > affects -1 + src:autofs Bug #1040950 [release.debian.org] bullseye-pu: package autofs/5.1.7-1+deb11u1 Added indication that 1040950 affects src:autofs -- 1040950: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040950 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1040949: bookworm-pu: package gosa/2.8~git20230203.10abe45+dfsg-1+deb12u1
Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: g...@packages.debian.org
Control: affects -1 + src:gosa
GOsa²'s PHP 8.2 support was rather poor at the release time of Debian 12.
This update will amend various issues found while testing GOsa² with
Debian Edu.
[ Reason ]
Various issues could be resolved:
* deprecation warnings
* missing smarty template file
* broken debug support
[ Impact ]
Only GOsa² users will be affected by this upload.
[ Tests ]
Manual tests on Debian Edu TJENER system.
[ Risks ]
Introduction of regressions in GOsa² in Debian 12.
[ 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 ]
+ [ Mike Gabriel ]
+ * debian/patches:
++ Add 1003_php-deprecations.patch. Silence various PHP 8.2 deprecation
+ warnings. (Closes: #1038682).
+
+ [ Daniel Teichmann ]
+ * debian/patches:
++ Add 1004_missing_templates.patch. (Closes: #1039697)
++ Update 1002_php82-allow-dynamic-properties.patch: Tolerate dyn. prop. for
+ ALL PHP classes. (Closes: #1039894)
++ Add 1005_preg_replace_deprecation.patch.
++ Add 1006_fix-overflow-debug-print_a-func.patch. (Closes: #1040839)
[ Other info ]
This might not be the last pu of GOsa² to bookworm. But various noises
should be reduced after this update has landed. We also work with
upstream on amending the patched issues there.
diff -Nru gosa-2.8~git20230203.10abe45+dfsg/debian/changelog
gosa-2.8~git20230203.10abe45+dfsg/debian/changelog
--- gosa-2.8~git20230203.10abe45+dfsg/debian/changelog 2023-02-06
20:43:44.0 +0100
+++ gosa-2.8~git20230203.10abe45+dfsg/debian/changelog 2023-07-12
23:12:05.0 +0200
@@ -1,3 +1,20 @@
+gosa (2.8~git20230203.10abe45+dfsg-1+deb12u1) bookworm; urgency=medium
+
+ [ Mike Gabriel ]
+ * debian/patches:
++ Add 1003_php-deprecations.patch. Silence various PHP 8.2 deprecation
+ warnings. (Closes: #1038682).
+
+ [ Daniel Teichmann ]
+ * debian/patches:
++ Add 1004_missing_templates.patch. (Closes: #1039697)
++ Update 1002_php82-allow-dynamic-properties.patch: Tolerate dyn. prop. for
+ ALL PHP classes. (Closes: #1039894)
++ Add 1005_preg_replace_deprecation.patch.
++ Add 1006_fix-overflow-debug-print_a-func.patch. (Closes: #1040839)
+
+ -- Mike Gabriel Wed, 12 Jul 2023 23:12:05 +0200
+
gosa (2.8~git20230203.10abe45+dfsg-1) unstable; urgency=medium
* New upstream Git snapshot.
diff -Nru
gosa-2.8~git20230203.10abe45+dfsg/debian/patches/1002_php82-allow-dynamic-properties.patch
gosa-2.8~git20230203.10abe45+dfsg/debian/patches/1002_php82-allow-dynamic-properties.patch
---
gosa-2.8~git20230203.10abe45+dfsg/debian/patches/1002_php82-allow-dynamic-properties.patch
2023-01-21 20:42:25.0 +0100
+++
gosa-2.8~git20230203.10abe45+dfsg/debian/patches/1002_php82-allow-dynamic-properties.patch
2023-07-12 23:10:08.0 +0200
@@ -1,6 +1,200 @@
-Description: Tolerate dynamic properties in managepws class, deprecated in PHP
8.2
-Author: Mike Gabriel
-
+Description: Tolerate dynamic properties in all classes, deprecated in PHP 8.2
+Author: Daniel Teichmann
+
+--- a/include/class_CopyPasteHandler.inc
b/include/class_CopyPasteHandler.inc
+@@ -22,6 +22,7 @@
+
+ define("LDAP_DUMP_PATH","/var/cache/gosa/tmp");
+
++#[\AllowDynamicProperties]
+ class CopyPasteHandler {
+
+ var $config;
+--- a/include/class_GOsaRegistration.inc
b/include/class_GOsaRegistration.inc
+@@ -1,5 +1,6 @@
+ "
+
+
++#[\AllowDynamicProperties]
+ class writeexcel_formula {
+
+
###
+--- a/include/utils/excel/class.writeexcel_olewriter.inc.php
b/include/utils/excel/class.writeexcel_olewriter.inc.php
+@@ -24,6 +24,7 @@
+ * Spreadsheet::WriteExcel was written by John McNamara, jmcnam...@cpan.org
+ */
+
++#[\AllowDynamicProperties]
+ class writeexcel_olewriter {
+ var $_OLEfilename;
+ var $_OLEtmpfilename; /* ABR */
+--- a/include/utils/excel/class.writeexcel_workbook.inc.php
b/include/utils/excel/class.writeexcel_workbook.inc.php
+@@ -29,6 +29,7 @@
+ require_once "class.writeexcel_formula.inc.php";
+ require_once "class.writeexcel_olewriter.inc.php";
+
++#[\AllowDynamicProperties]
+ class writeexcel_workbook extends writeexcel_biffwriter {
+
+ var $_filename;
+--- a/include/utils/excel/class.writeexcel_worksheet.inc.php
b/include/utils/excel/class.writeexcel_worksheet.inc.php
+@@ -26,6 +26,7 @@
+
+ require_once "class.writeexcel_biffwriter.inc.php";
+
++#[\AllowDynamicProperties]
+ class writeexcel_worksheet extends writeexcel_biffwriter {
+
+ var $_name;
+--- a/plugins/addons/dyngroup/class_DynamicLdapGroup.inc
b/plugins/addons/dyngroup/class_DynamicLdapGroup.inc
+@@ -25,6 +25,7 @
Processed: bookworm-pu: package gosa/2.8~git20230203.10abe45+dfsg-1+deb12u1
Processing control commands: > affects -1 + src:gosa Bug #1040949 [release.debian.org] bookworm-pu: package gosa/2.8~git20230203.10abe45+dfsg-1+deb12u1 Added indication that 1040949 affects src:gosa -- 1040949: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040949 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1036904: bookworm-pu: package libreoffice/4:7.4.7-1
Processing control commands: > tag -1 confirmed Bug #1036904 [release.debian.org] bookworm-pu: package libreoffice/4:7.4.7-1 Added tag(s) confirmed. -- 1036904: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036904 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1036904: bookworm-pu: package libreoffice/4:7.4.7-1
Control: tag -1 confirmed Hi, On Mon, May 29, 2023 at 09:11:14AM +0200, Rene Engelhard wrote: > [ Reason ] > Update to "current" version. (Latest version of stable branch) > > Same reasoning as of #1035056. > > This updates LibreOffice to the last version in the (dead, EOL is June 12) > 7.4.x line[1] > to fix a sh*load of bugs. List of bugs fixed: See [2] Given the comprehensive test suite and upstream's track record of limiting stable branches to bug fixes only, I have reviewed debian/* but not the entire diff. Please go ahead with uploading it. > [ Changes ] > 1. upstream update 7.4.5 -> 7.4.7. The two patches removed are security > fixes which were already in 7.4.6 and 7.4.7 and now of course removed. > No need to mention that in the changelog, it's implied by "New upstream > release" that patches upstream are dropped. Actually it's really helpful to have the dropped patches listed, if feasible. That allows a review to check that the intended patches, and only those, have been dropped. > [ Other info ] > I can back out the fix for 3. The other two are simply not discussable > given #1035056. You can leave 3 in. I'm disappointed by your reluctance to even engage in discussing the other two but also understand that bug has been the source of some frustration for you. > I know this is completely bending the rules, but so is #1035056, too > If you wish I can make this also -0deb12u1, but as there will be no > 7.4.7-1 probably thia is not exactly needed. The version is fine. It may or may not make it into 12.1 depending on build times; we'll do our best. Thanks, -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 ed25519/0x196418AAEB74C8A1: CA619D65A72A7BADFC96D280196418AAEB74C8A1
NEW changes in stable-new
Processing changes file: desktop-base_12.0.6+nmu1~deb12u1_source.changes ACCEPT Processing changes file: libnginx-mod-http-modsecurity_1.0.3-1+b2_amd64-buildd.changes ACCEPT Processing changes file: libnginx-mod-http-modsecurity_1.0.3-1+b2_arm64-buildd.changes ACCEPT Processing changes file: libnginx-mod-http-modsecurity_1.0.3-1+b2_armel-buildd.changes ACCEPT Processing changes file: libnginx-mod-http-modsecurity_1.0.3-1+b2_armhf-buildd.changes ACCEPT Processing changes file: libnginx-mod-http-modsecurity_1.0.3-1+b2_i386-buildd.changes ACCEPT Processing changes file: libnginx-mod-http-modsecurity_1.0.3-1+b2_mips64el-buildd.changes ACCEPT Processing changes file: libnginx-mod-http-modsecurity_1.0.3-1+b2_mipsel-buildd.changes ACCEPT Processing changes file: libnginx-mod-http-modsecurity_1.0.3-1+b2_ppc64el-buildd.changes ACCEPT Processing changes file: libnginx-mod-http-modsecurity_1.0.3-1+b2_s390x-buildd.changes ACCEPT Processing changes file: node-webpack_5.75.0+dfsg+~cs17.16.14-1+deb12u1_sourceonly.changes ACCEPT Processing changes file: schleuder-cli_0.1.0-4+deb12u1_source.changes ACCEPT
Processed: desktop-base 12.0.6+nmu1~deb12u1 flagged for acceptance
Processing commands for cont...@bugs.debian.org: > package release.debian.org Limiting to bugs with field 'package' containing at least one of 'release.debian.org' Limit currently set to 'package':'release.debian.org' > tags 1040739 = bookworm pending Bug #1040739 [release.debian.org] bookworm-pu: package desktop-base/12.0.6+nmu1~deb12u1 Added tag(s) pending; removed tag(s) confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1040739: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040739 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1040739: desktop-base 12.0.6+nmu1~deb12u1 flagged for acceptance
package release.debian.org tags 1040739 = bookworm pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bookworm. Thanks for your contribution! Upload details == Package: desktop-base Version: 12.0.6+nmu1~deb12u1 Explanation: remove emerald alternatives on package uninstallation
Bug#1040678: bookworm-pu: package node-dottie/2.0.2-4+deb12u1
Hi, Given the package is blocked from migration to testing at the moment, and probably won't migrate before we start preparing for 12.1, I've held this upload back. It'll likely be part of 12.2 instead. Thanks, -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 ed25519/0x196418AAEB74C8A1: CA619D65A72A7BADFC96D280196418AAEB74C8A1
NEW changes in stable-new
Processing changes file: node-tough-cookie_4.0.0-2+deb12u1_sourceonly.changes ACCEPT Processing changes file: nvidia-modprobe_535.54.03-1~deb12u1_source.changes ACCEPT
Processed: libnginx-mod-http-modsecurity 1.0.3-1+b2 flagged for acceptance
Processing commands for cont...@bugs.debian.org: > package release.debian.org Limiting to bugs with field 'package' containing at least one of 'release.debian.org' Limit currently set to 'package':'release.debian.org' > tags 1040799 = bookworm pending Bug #1040799 [release.debian.org] nmu: libnginx-mod-http-modsecurity_1.0.3-1+b1 Added tag(s) pending; removed tag(s) moreinfo and confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1040799: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040799 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: node-webpack 5.75.0+dfsg+~cs17.16.14-1+deb12u1 flagged for acceptance
Processing commands for cont...@bugs.debian.org: > package release.debian.org Limiting to bugs with field 'package' containing at least one of 'release.debian.org' Limit currently set to 'package':'release.debian.org' > tags 1040683 = bookworm pending Bug #1040683 [release.debian.org] bookworm-pu: package node-webpack/5.75.0+dfsg+~cs17.16.14-1+deb12u1 Added tag(s) pending; removed tag(s) confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1040683: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040683 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: nvidia-modprobe 535.54.03-1~deb12u1 flagged for acceptance
Processing commands for cont...@bugs.debian.org: > package release.debian.org Limiting to bugs with field 'package' containing at least one of 'release.debian.org' Limit currently set to 'package':'release.debian.org' > tags 1040765 = bookworm pending Bug #1040765 [release.debian.org] bookworm-pu: package nvidia-modprobe/535.54.03-1~deb12u1 Added tag(s) pending; removed tag(s) confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1040765: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040765 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1040799: libnginx-mod-http-modsecurity 1.0.3-1+b2 flagged for acceptance
package release.debian.org tags 1040799 = bookworm pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bookworm. Thanks for your contribution! Upload details == Package: libnginx-mod-http-modsecurity Version: 1.0.3-1+b2 Explanation: binary rebuild with pcre2
Processed: schleuder-cli 0.1.0-4+deb12u1 flagged for acceptance
Processing commands for cont...@bugs.debian.org: > package release.debian.org Limiting to bugs with field 'package' containing at least one of 'release.debian.org' Limit currently set to 'package':'release.debian.org' > tags 1040791 = bookworm pending Bug #1040791 [release.debian.org] bookworm-pu: package schleuder-cli/0.1.0-4+deb12u1 Added tag(s) pending; removed tag(s) confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1040791: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040791 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1040791: schleuder-cli 0.1.0-4+deb12u1 flagged for acceptance
package release.debian.org tags 1040791 = bookworm pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bookworm. Thanks for your contribution! Upload details == Package: schleuder-cli Version: 0.1.0-4+deb12u1 Explanation: security fix (value escaping)
Bug#1040683: node-webpack 5.75.0+dfsg+~cs17.16.14-1+deb12u1 flagged for acceptance
package release.debian.org tags 1040683 = bookworm pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bookworm. Thanks for your contribution! Upload details == Package: node-webpack Version: 5.75.0+dfsg+~cs17.16.14-1+deb12u1 Explanation: security fix (cross-realm objects) [CVE-2023-28154]
Bug#1040765: nvidia-modprobe 535.54.03-1~deb12u1 flagged for acceptance
package release.debian.org tags 1040765 = bookworm pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bookworm. Thanks for your contribution! Upload details == Package: nvidia-modprobe Version: 535.54.03-1~deb12u1 Explanation: new upstream bugfix release
Processed: node-tough-cookie 4.0.0-2+deb12u1 flagged for acceptance
Processing commands for cont...@bugs.debian.org: > package release.debian.org Limiting to bugs with field 'package' containing at least one of 'release.debian.org' Limit currently set to 'package':'release.debian.org' > tags 1040563 = bookworm pending Bug #1040563 [release.debian.org] bookworm-pu: package node-tough-cookie/4.0.0-2+deb12u1 Added tag(s) pending; removed tag(s) confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1040563: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040563 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1040563: node-tough-cookie 4.0.0-2+deb12u1 flagged for acceptance
package release.debian.org tags 1040563 = bookworm pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bookworm. Thanks for your contribution! Upload details == Package: node-tough-cookie Version: 4.0.0-2+deb12u1 Explanation: security fix (prototype pollution) [CVE-2023-26136]
Bug#1040001: Role of tibble? (Was: Bug#1040001: Seeking advise how to proceed with the transition / move R stack to testing)
Hi Paul, On 12 July 2023 at 19:47, Paul Gevers wrote: | On 12-07-2023 16:02, Dirk Eddelbuettel wrote: | > I can add the Breaks as a 'best of the worse alternative'. And, I presume, I | > can remove the existing four-year breaks? [1] | | Yes, you only need to carry the Breaks until in the next release. So | every Breaks that's present in the r-base package in bookworm can be | removed from the r-base package in unstable. Good point and much less ugly then :) Dirk -- dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
Bug#1040001: Role of tibble? (Was: Bug#1040001: Seeking advise how to proceed with the transition / move R stack to testing)
Hi, On 12-07-2023 16:02, Dirk Eddelbuettel wrote: I can add the Breaks as a 'best of the worse alternative'. And, I presume, I can remove the existing four-year breaks? [1] Yes, you only need to carry the Breaks until in the next release. So every Breaks that's present in the r-base package in bookworm can be removed from the r-base package in unstable. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#1040939: bookworm-pu: package rmlint/2.9.0-2.3+deb12u1
Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: rml...@packages.debian.org
Control: affects -1 + src:rmlint
[ Reason ]
This bug has been present for a long time but only just stumbled
upon. rmlint-gui installs a Python package with an invalid version
number, causing other packages to mysteriously break when rmlint-gui
is installed. Only spyder has been reported to be affected so far,
but I expect others to be equally impacted.
[ Impact ]
Some other unrelated packages will continue to break in strange ways.
It may well also cause headaches to maintainers of those packages.
[ Tests ]
No tests cover the affected code, unfortunately, to the best of my
knowledge. However, the package rmlint-gui doesn't work anyway (I
had never used it, but just tried and it crashed immediately with a
SyntaxError). Nevertheless, its mere presence on a Debian system will
cause the above error. Upstream is now showing signs of life again,
though the package does not currently have an active Debian
maintainer, so it may be dropped from testing soon; I'll file an RC
bug against the current version in a moment.
[ Risks ]
I cannot see any risks to fixing one bug in a piece of broken
software.
[ 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 ]
Apply an upstream patch to fix the Python version number.
[ Other info ]
This is an NMU because the maintainer is MIA.
diff -Nru rmlint-2.9.0/debian/changelog rmlint-2.9.0/debian/changelog
--- rmlint-2.9.0/debian/changelog 2021-04-15 22:03:37.0 +0100
+++ rmlint-2.9.0/debian/changelog 2023-07-12 16:18:40.0 +0100
@@ -1,3 +1,11 @@
+rmlint (2.9.0-2.3+deb12u1) bookworm; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix error in other packages caused by invalid python package version
+number (cherry-picking upstream patch; closes: #1040179)
+
+ -- Julian Gilbey Wed, 12 Jul 2023 16:18:40 +0100
+
rmlint (2.9.0-2.3) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru rmlint-2.9.0/debian/patches/python-version-number.patch
rmlint-2.9.0/debian/patches/python-version-number.patch
--- rmlint-2.9.0/debian/patches/python-version-number.patch 1970-01-01
01:00:00.0 +0100
+++ rmlint-2.9.0/debian/patches/python-version-number.patch 2023-07-12
16:18:40.0 +0100
@@ -0,0 +1,17 @@
+From: Cebtenzzre
+Subject: gui: use PEP 440-compliant version number
+Origin: upstream,
https://github.com/sahib/rmlint/commit/b5a6d9b359b1fc1ea75bdb6c1ae6cbdc0a304ecf
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040179
+
+--- a/gui/setup.py
b/gui/setup.py
+@@ -14,7 +14,8 @@
+ with open('../.version', 'r') as handle:
+ version_string = handle.read()
+
+-return version_string.strip()
++version_numbers, _ = version_string.split(' ', 1)
++return version_numbers
+
+
+ def get_prefix():
diff -Nru rmlint-2.9.0/debian/patches/series rmlint-2.9.0/debian/patches/series
--- rmlint-2.9.0/debian/patches/series 2021-04-15 22:03:37.0 +0100
+++ rmlint-2.9.0/debian/patches/series 2023-07-12 16:18:40.0 +0100
@@ -8,3 +8,4 @@
glib-2_62.patch
0001-fix-link-error-on-compilers-with-fno-common-enabled.patch
0010-apply-upstream-fix-for-data-loss-bug.patch
+python-version-number.patch
Processed: bookworm-pu: package rmlint/2.9.0-2.3+deb12u1
Processing control commands: > affects -1 + src:rmlint Bug #1040939 [release.debian.org] bookworm-pu: package rmlint/2.9.0-2.3+deb12u1 Added indication that 1040939 affects src:rmlint -- 1040939: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040939 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
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=medium
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#1040001: Role of tibble? (Was: Bug#1040001: Seeking advise how to proceed with the transition / move R stack to testing)
Hi Paul, On 11 July 2023 at 20:36, Paul Gevers wrote: | On 11-07-2023 02:43, Dirk Eddelbuettel wrote: | I'm totally on board for technical excellence, although I think we have | different things in mind when we say that. | | In Debian, with more QA than we ever had before, we're finding a class | of issues that often went unnoticed years ago. One of these things is Of course I am not against testing auto-upgrades. I imagine nobody is. What I am not happy about is that we fell into a hole we would not need to be in, ideally. Please hear me out on this: - R has an annual release cycle at the end of April - During that cycle the 'next' release (in VCS) is referred to as r-devel. - CRAN checks all packages at all uploads, as well as periodically, against r-devel. - When a change is needed because something would break once r-devel becomes 'r-release' they contact the package author and request the change, this is a hard requirement and non-compliant package are thrown off CRAN. No - breakage allowed! - What I showed with maldiquant was that its upstream made the change in March still well before the R 4.3.0 release requiring it - So we could have (we had the freeze, more below) had the package which would have passed both 'r-release' then and 'r-devel then' (which is 'r-release now') and everything would pass. Even under our tests. That is an ideal I would really like us to move towards with the CRAN packages in Debian. As CRAN makes it so easy for us to 'always build / build @HEAD' we really should take the fullest advantage of it. So I typically roll up my packages the day or week of a CRAN change. (And maintain 2 x 21k binaries off CRAN in r2u, but that is a different story.) As it happens, not everybody does, sometimes we have freezes, and other things happen. Also the number of CRAN packages increases of course and the net-net of that is that we then have to spend precious manual time picking up the pieces. Clearly not ideal, but better than having installation bugs. | that partial upgrades can leave you in a bad state. So more and more we | see that packages "have to" add Breaks to tell apt that when you want to | upgrade package X, you also have to upgrade package Y if you happen to | have that installed. As package Y can not tell that, package X has to | add the Breaks on the broken version of Y. As an example, see the list | of Breaks in libc6 [1]. While partial upgrades aren't officially Thanks for that. An impressively long list! | supported, we rely on them nevertheless (even if only for QA (piuparts, | autopkgtest)), and as a Release Team member I consider that class of | fixes technical excellence: ensuring as best as we can that the user | that upgrades a package keeps a working system. Yes. | While a rebuild of everything combined with bumping the "api" would | achieve that, I'm much more in favor of targeted Breaks, like we have | been discussing here. It's typically more work, but it's more correct. Fully agreed. | For the future, with the recent change in dh-r, r-base will be much less | impacted by this "problem" as the new uploads of reverse dependencies | can migrate *before* r-base, and hence this class of issues will I don't think so. The recent change helps with the (approximately a handful or two CRAN packages) setting the graphics engine check (out of a total of maybe 1300 CRAN/BioC packages at Debian leaving the many others unaffected). | disappear once that happens (autopkgtest failures are retried after a | day). So unless somebody investigates the issues in time, the retry will We will get the same breakage next time will CRAN assumes (and ensures !!) everything is current at HEAD, we usually have slippage for various reasons so in practice I fear ... here we are and remain. | pass after the migration and the issue will no longer block r-base. I | can live with that, but I find it a shame nevertheless. Yep. We should aim to have 'less shame, more technical excellence'. | So, what do you say: technical excellence and you add the Breaks? Or we | let this slip in? I prefer the former, I can live with the latter. I can add the Breaks as a 'best of the worse alternative'. And, I presume, I can remove the existing four-year breaks? [1] Cheers, Dirk [1] edd@rob:~/deb/r-base(master)$ git blame debian/control | grep -A24 Breaks 52de7d776d (Dirk Eddelbuettel 2019-08-08 19:11:55 -0500 55) Breaks: r-bioc-graph (<< 1.62.0-1~), 52de7d776d (Dirk Eddelbuettel 2019-08-08 19:11:55 -0500 56) r-cran-bbmle (<< 1.0.20-5~), 52de7d776d (Dirk Eddelbuettel 2019-08-08 19:11:55 -0500 57) r-cran-biocmanager (<< 1.30.4+dfsg-2~), 52de7d776d (Dirk Eddelbuettel 2019-08-08 19:11:55 -0500 58) r-cran-caret (<< 6.0-84-2~), 52de7d776d (Dirk Eddelbuettel 2019-08-08 19:11:55 -0500 59) r-cran-cmprsk (<< 2.2-8-1~), 52de7d776d (Dirk Eddelbuettel 2019-08-08 19:11:55 -0500 60) r-cran-coin (<< 1.3-0-
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
Processed: retitle 1040921 to bookworm-pu: package dkms/3.0.10-8+deb12u1, tagging 1040921
Processing commands for cont...@bugs.debian.org: > retitle 1040921 bookworm-pu: package dkms/3.0.10-8+deb12u1 Bug #1040921 [release.debian.org] bullseye-pu: package dkms/3.0.10-8+deb12u1 Changed Bug title to 'bookworm-pu: package dkms/3.0.10-8+deb12u1' from 'bullseye-pu: package dkms/3.0.10-8+deb12u1'. > tags 1040921 = bookworm Bug #1040921 [release.debian.org] bookworm-pu: package dkms/3.0.10-8+deb12u1 Added tag(s) bookworm; removed tag(s) bullseye. > thanks Stopping processing here. Please contact me if you need assistance. -- 1040921: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040921 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
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#1040915: bookworm-pu: package dbus/1.14.8-2~deb12u1
On Wed, 12 Jul 2023 at 12:12:47 +0100, Simon McVittie wrote:
> [ Reason ]
> https://bugs.debian.org/1040790
> [ Changes ]
> All changes are part of resolving or testing #1040790.
Debdiff attached.
> [ Tests ]
I should also have mentioned that I'm running the proposed package on
a bookworm desktop system and it works normally.
smcv
diffstat for dbus-1.14.8 dbus-1.14.8
changelog| 16 +
dbus-daemon.postinst |4 +--
tests/control|9 +++
tests/machine-id | 60 +++
4 files changed, 87 insertions(+), 2 deletions(-)
diff -Nru dbus-1.14.8/debian/changelog dbus-1.14.8/debian/changelog
--- dbus-1.14.8/debian/changelog 2023-06-11 12:42:56.0 +0100
+++ dbus-1.14.8/debian/changelog 2023-07-11 20:59:33.0 +0100
@@ -1,3 +1,19 @@
+dbus (1.14.8-2~deb12u1) bookworm; urgency=medium
+
+ * Rebuild for bookworm
+
+ -- Simon McVittie Tue, 11 Jul 2023 20:59:33 +0100
+
+dbus (1.14.8-2) unstable; urgency=high
+
+ * dbus-daemon.postinst: Stop trying to take DPKG_ROOT into account.
+This unintentionally disabled the code path that would copy systemd's
+/etc/machine-id in preference to creating an entirely new machine ID.
+(Closes: #1040790)
+ * d/tests: Add test coverage for #1040790
+
+ -- Simon McVittie Tue, 11 Jul 2023 18:38:22 +0100
+
dbus (1.14.8-1~deb12u1) bookworm; urgency=medium
* Rebuild for bookworm
diff -Nru dbus-1.14.8/debian/dbus-daemon.postinst dbus-1.14.8/debian/dbus-daemon.postinst
--- dbus-1.14.8/debian/dbus-daemon.postinst 2023-06-11 12:42:56.0 +0100
+++ dbus-1.14.8/debian/dbus-daemon.postinst 2023-07-11 20:59:33.0 +0100
@@ -7,8 +7,8 @@
# script does this anyway, but you also have to do this before a session
# bus will work on non-systemd systems, so we do this here for the
# benefit of people starting a temporary session bus in a chroot.
-mkdir -p "${DPKG_ROOT:-/}var/lib/dbus"
-dbus-uuidgen --ensure="${DPKG_ROOT:-/}var/lib/dbus/machine-id"
+mkdir -p /var/lib/dbus
+dbus-uuidgen --ensure
fi
#DEBHELPER#
diff -Nru dbus-1.14.8/debian/tests/control dbus-1.14.8/debian/tests/control
--- dbus-1.14.8/debian/tests/control 2023-06-11 12:42:56.0 +0100
+++ dbus-1.14.8/debian/tests/control 2023-07-11 20:59:33.0 +0100
@@ -25,6 +25,15 @@
Restrictions: allow-stderr, superficial
Depends: dbus-daemon
+Tests: machine-id
+Restrictions: allow-stderr, needs-root, superficial
+Depends: dbus-daemon
+
+Test-Command: debian/tests/machine-id with-systemd
+Features: test-name=machine-id_with_systemd
+Restrictions: allow-stderr, needs-root, superficial
+Depends: dbus-daemon, systemd
+
Tests: dbus-session-bus-common
Restrictions: allow-stderr, superficial
Depends: dbus-session-bus-common
diff -Nru dbus-1.14.8/debian/tests/machine-id dbus-1.14.8/debian/tests/machine-id
--- dbus-1.14.8/debian/tests/machine-id 1970-01-01 01:00:00.0 +0100
+++ dbus-1.14.8/debian/tests/machine-id 2023-07-11 20:59:33.0 +0100
@@ -0,0 +1,60 @@
+#!/bin/sh
+set -eu
+
+# Regression test for https://bugs.debian.org/1040790
+
+mode="${1-}"
+
+export LC_ALL=C.UTF-8
+fail=
+set -x
+
+# dbus-daemon.deb provides a machine ID
+ls -l /etc/machine-id /var/lib/dbus/machine-id || :
+head /etc/machine-id /var/lib/dbus/machine-id || :
+uuid="$(dbus-uuidgen --get)"
+test -n "$uuid" || fail=yes
+# The machine ID consists of 32 lower-case hex digits (and the file
+# also has a newline)
+test "$uuid" = "$(perl -pe 'print "wrong: " unless /\A[a-z0-9]{32}\n\z/' /var/lib/dbus/machine-id)" || fail=yes
+
+# Intentionally not asserting that /etc/machine-id matches
+# /var/lib/dbus/machine-id: if the test container has both dbus and
+# systemd, and it was generated with a version of dbus that has #1040790,
+# then that assertion could fail.
+
+# If there is a systemd machine ID, installing dbus-daemon should
+# make the D-Bus machine ID be the same as it.
+# Unfortunately nothing currently guarantees that a Debian
+# system will have a machine ID, so this has to be conditional. (See
+# also #745876, #783716).
+if [ -e /etc/machine-id ] || [ "$mode" = with-systemd ]; then
+rm -f /var/lib/dbus/machine-id
+# This is for its side-effect of running the postinst, emulating
+# a fresh installation
+dpkg-reconfigure -fnoninteractive -pcritical dbus-daemon
+ls -l /etc/machine-id /var/lib/dbus/machine-id || :
+head /etc/machine-id /var/lib/dbus/machine-id || :
+uuid="$(dbus-uuidgen --get)"
+test -n "$uuid" || fail=yes
+test "$uuid" = "$(perl -pe 'print "wrong: " unless /\A[a-z0-9]{32}\n\z/' /var/lib/dbus/machine-id)" || fail=yes
+test "$uuid" = "$(perl -pe 'print "wrong: " unless /\A[a-z0-9]{32}\n\z/' /etc/machine-id)" || fail=yes
+fi
+
+# Similarly, if there is a D-Bus machine ID but no systemd machine ID
+# (for example if dbus-daemon happened to be installed before systemd),
+# then we expect systemd-machine-id-setup to copy ours.
Bug#1040915: bookworm-pu: package dbus/1.14.8-2~deb12u1
Package: release.debian.org Severity: normal Tags: bookworm User: release.debian@packages.debian.org Usertags: pu X-Debbugs-Cc: d...@packages.debian.org, debian-b...@lists.debian.org Control: affects -1 + src:dbus [ Reason ] https://bugs.debian.org/1040790 [ Impact ] A regression in bookworm's dbus packaging led to /etc/machine-id and /var/lib/dbus/machine-id having different contents in fresh installations of bookworm or later. The machine ID is an opaque hex string analogous to a MAC address, intended to identify the machine in contexts where the hostname would traditionally have been used, but avoiding the risk that a sysadmin setting an aesthetically appealing hostname will result in non-uniqueness (either the same hostname on more than one concurrently used installation, or the same installation having more than one hostname over time). Some packages that rely on this interface try /etc/machine-id first and fall back to /var/lib/dbus/machine-id if it doesn't exist, while others do the opposite, so this bug leads to those packages disagreeing on what the machine ID is, and therefore potentially behaving as though they are running on two different machines with a shared (NFS) home directory. The full user-visible impact of this is unknown: the machine ID is intentionally quite a general feature, so we cannot know all the things that might use it. pulseaudio, ibus, dbus-x11 and maybe others have autostart protocols that involve it, so non-uniqueness could result in unintentionally running two instances of the same service on the same machine. Conversely, GNOME and maybe others store per-machine data in the user's home directory (in particular, GNOME screen settings) keyed by the machine ID, so the apparent machine ID changing could result in apparent configuration data loss. [ Tests ] The majority of the changes are new automated test coverage. I can reproduce the problem with mmdebstrap, and I have confirmed that replacing packages from src:dbus with the proposed version resolves it. I have not attempted to provide the updated dbus to a d-i image and do an install from first principles. [ Risks ] Low-risk change, reverting unnecessary complexity in the postinst and returning to what we did 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 ] All changes are part of resolving or testing #1040790. [ Other info ] dbus technically has a udeb, but it's essentially unused, and in any case dbus-udeb.postinst never had this bug (so it has not changed here). I have not attempted to retroactively fix the machine ID of existing installations: that would be much higher-risk and will require considerably more thought. It's entirely possible that the best approach to existing installations is to ignore the mismatch and hope that it doesn't cause any user-visible symptoms.
Processed: bookworm-pu: package dbus/1.14.8-2~deb12u1
Processing control commands: > affects -1 + src:dbus Bug #1040915 [release.debian.org] bookworm-pu: package dbus/1.14.8-2~deb12u1 Added indication that 1040915 affects src:dbus -- 1040915: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040915 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
NEW changes in stable-new
Processing changes file: pacemaker_2.1.5-1+deb12u1_amd64-buildd.changes ACCEPT Processing changes file: pacemaker_2.1.5-1+deb12u1_i386-buildd.changes ACCEPT Processing changes file: pacemaker_2.1.5-1+deb12u1_s390x-buildd.changes ACCEPT
NEW changes in stable-new
Processing changes file: pacemaker_2.1.5-1+deb12u1_mipsel-buildd.changes ACCEPT
NEW changes in stable-new
Processing changes file: pacemaker_2.1.5-1+deb12u1_arm64-buildd.changes ACCEPT Processing changes file: pacemaker_2.1.5-1+deb12u1_armel-buildd.changes ACCEPT Processing changes file: pacemaker_2.1.5-1+deb12u1_mips64el-buildd.changes ACCEPT
NEW changes in stable-new
Processing changes file: pacemaker_2.1.5-1+deb12u1_armhf-buildd.changes ACCEPT
NEW changes in stable-new
Processing changes file: pacemaker_2.1.5-1+deb12u1_all-buildd.changes ACCEPT Processing changes file: pacemaker_2.1.5-1+deb12u1_ppc64el-buildd.changes ACCEPT
Processed: retitle 1040890 to bookworm-pu: package nvidia-settings-tesla/525.125.06-1~deb12u1, tagging 1040890
Processing commands for cont...@bugs.debian.org: > retitle 1040890 bookworm-pu: package > nvidia-settings-tesla/525.125.06-1~deb12u1 Bug #1040890 [release.debian.org] bullseye-pu: package nvidia-settings-tesla/525.125.06-1~deb12u1 Changed Bug title to 'bookworm-pu: package nvidia-settings-tesla/525.125.06-1~deb12u1' from 'bullseye-pu: package nvidia-settings-tesla/525.125.06-1~deb12u1'. > tags 1040890 = bookworm Bug #1040890 [release.debian.org] bookworm-pu: package nvidia-settings-tesla/525.125.06-1~deb12u1 Added tag(s) bookworm; removed tag(s) bullseye. > thanks Stopping processing here. Please contact me if you need assistance. -- 1040890: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040890 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
NEW changes in stable-new
Processing changes file: pacemaker_2.1.5-1+deb12u1_source.changes ACCEPT
NEW changes in stable-new
Processing changes file: systemd_252.12-1~deb12u1_mipsel-buildd.changes ACCEPT
Processed: pacemaker 2.1.5-1+deb12u1 flagged for acceptance
Processing commands for cont...@bugs.debian.org: > package release.debian.org Limiting to bugs with field 'package' containing at least one of 'release.debian.org' Limit currently set to 'package':'release.debian.org' > tags 1040415 = bookworm pending Bug #1040415 [release.debian.org] bookworm-pu: package pacemaker/2.1.5-1+deb12u1 Added tag(s) pending; removed tag(s) confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1040415: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040415 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1040415: pacemaker 2.1.5-1+deb12u1 flagged for acceptance
package release.debian.org tags 1040415 = bookworm pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bookworm. Thanks for your contribution! Upload details == Package: pacemaker Version: 2.1.5-1+deb12u1 Explanation: fix reression in the resource scheduler
