Bug#1033811: unblock: mariadb/1:10.11.2-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Control: affects -1 + src:mariadb Please unblock package 'mariadb' so that the bug fixes in the Debian revision 2 can be included in the release of Debian 12 "Bookworm". The package is currently 7/20 days old, but even after 20 days it will not automatically migrate because it is listed as a key package. Also, it has autopkgtest failure for armel/armhf. The failure is safe to ignore because it is from a new test that had a typo[1] on these two platforms. Autopkgtests fully pass on all other platforms. I decided to not do a re-upload just for this typo for now, it would not be frugal use of builders and Debian infra. This Debian revision has been carefully crafted to only include bug fixes, test improvements and translations (following the release policy[2]). There are no risky functional changes, and the package has not had any new bugs reported for several weeks and confidence that this is the best version for Bookworm is high. The changes can be reviewed by reading individual commits (each change is well documented)[3]. Below summary from changelog[4]: mariadb (1:10.11.2-2) unstable; urgency=medium . [ Otto Kekäläinen ] * SUMMARY: This version has a lot of bug fixes, quality fixes, documentation and translation updates and it is tailored for the Debian 12 "Bookworm" release and all potentially functional changes have been left out and are pending review and merge post-Bookworm release at https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests, where contributions both as reviews and new submissions are welcome! * Update NEWS to summarize what is new in MariaDB 10.11 (compared to 10.6) * Update and activate configuration tracing in autopkgtests to ensure that for the Debian 12 "Bookworm" release cycle no upstream server config change would slip in unnoticed * Enable mariadb-plugin-rocksdb for riscv64 (fixes autopkgtests for riscv64) * Sync downstream (where applicable) with upstream 10.11 debian/* contents so that using diff/meld to compare changes are easier * Add important upstream 10.11.2+ fixes as packes: * Stack overflow in pinbox allocator (PR#2541) * Upgrades from MySQL 5.7 to MariaDB 10.11 (MDEV-30483) (Closes: #866751) * Misc compiler warnings in upstream build * Incomplete stack traces if MariaDB crashes * Make mariadbd emit warnings if mariadb-upgrade was not run * Binlog failures due to 'character_set_client' (MDEV-30824) * Prevent mariadb-test-run from using native I/O on ppc64el and s390x due to Linux kernel bug (Related: #1031656) * Add patch to better diagnose potential failures in main.order_by_innodb * Add patch to fix cross-compilation failure on uca-dump (Closes: #1029165) * Update mariadb-test-run skip test lists to not run tests that are known to be broken or unstable, and that have been reported upstream * Limit check of running mysqld/mariadbd to system users (Closes: #1032047) * Make error more helpful in case server restart fails (Related: #1033234) * Update Lintian overrides after rigorous review of all Lintian issues * Remove incorrect Multi-Arch definitions * Fix man pages syntax issues (Closes: #1032861) * Fix spelling in MariaDB and components (Closes: #1032860) * Refresh patches metadata * Update upstream signing key * Fix dependency of obsolete libncurses5-dev . [ Ekaterine Papava ] * Add Georgian translation (error messages) . [ Tuukka Pasanen ] * Update README files to correct versions [1] https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/42 [2] https://release.debian.org/testing/freeze_policy.html [3] https://salsa.debian.org/mariadb-team/mariadb-server/-/commits/debian/1%2510.11.2-2 [4] https://tracker.debian.org/news/1427834/accepted-mariadb-110112-2-source-into-unstable/
Processed: unblock: mariadb/1:10.11.2-2
Processing control commands: > affects -1 + src:mariadb Bug #1033811 [release.debian.org] unblock: mariadb/1:10.11.2-2 Added indication that 1033811 affects src:mariadb -- 1033811: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033811 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033810: unblock: cyrus-imapd/3.6.1-4
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock X-Debbugs-Cc: cyrus-im...@packages.debian.org Control: affects -1 + src:cyrus-imapd Please unblock package cyrus-imapd [ Reason ] debian/copyright was incomplete [ Impact ] Incomplete copyright [ Tests ] No code change [ Risks ] No risk here, no code change. [ 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 testing Cheers, Yadd unblock cyrus-imapd/3.6.1-4 diff --git a/debian/changelog b/debian/changelog index 9d1408cb..a6d3c31a 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +cyrus-imapd (3.6.1-4) unstable; urgency=medium + + * Update copyright + * Declare compliance with policy 4.6.2 + + -- Yadd Fri, 31 Mar 2023 11:12:57 +0400 + cyrus-imapd (3.6.1-2) unstable; urgency=medium [ Remus-Gabriel Chelu ] diff --git a/debian/control b/debian/control index ad383b18..d20e0f52 100644 --- a/debian/control +++ b/debian/control @@ -51,7 +51,7 @@ Build-Depends: bison, unicode-data, xxd, xutils-dev -Standards-Version: 4.6.1 +Standards-Version: 4.6.2 Vcs-Browser: https://salsa.debian.org/debian/cyrus-imapd Vcs-Git: https://salsa.debian.org/debian/cyrus-imapd.git Homepage: https://www.cyrusimap.org/ diff --git a/debian/copyright b/debian/copyright index b6d376e4..1049ba5c 100644 --- a/debian/copyright +++ b/debian/copyright @@ -7,6 +7,43 @@ Files: * Copyright: 1994-2020, Carnegie Mellon University License: CMU +Files: cassandane/* +Copyright: 2011 Opera Software Australia Pty. Ltd. +License: OSAP + +Files: cassandane/Cassandane/* + cassandane/utils/crash.c +Copyright: 2011-2022 Fastmail Pty Ltd +License: FPL + +Files: cmulocal/ax_cxx_compile_stdcxx_11.m4 +Copyright: 2008 Benjamin Kosnik + 2012 Zack Weinberg + 2013 Roy Stogner + 2014, 2015 Google Inc., contributed by Alexey Sokolov + 2015 Paul Norman +License: FSFAPL + +Files: cmulocal/ax_prog_perl_modules.m4 +Copyright: 2009 Dean Povey +License: FSFAPL + +Files: cmulocal/*.m4 + compile + config.* + ylwrap +Copyright: 1992-2022 Free Software Foundation, Inc. +License: GPL-2+ + +Files: cmulocal/ax_python_module.m4 +Copyright: 2008 Andrew Collier +License: FSFAPL + +Files: com_err/et/* +Copyright: 1987, 1988 by the Student Information Processing Board of the + Massachusetts Institute of Technology +License: MIT + Files: debian/* Copyright: 1997, Joey Hess 2001-2010, Henrique de Moraes Holschuh @@ -18,6 +55,11 @@ Copyright: 1997, Joey Hess 2019-2022, Yadd License: GPL-2+ +Files: doc/* +Copyright: 1993–2023 The Cyrus Team +License: CMU +Comment: Built with Sphinx, license BSD-2-Clause + Files: imap/objectstore_caringo.c Copyright: 2015 OpenIO, as a part of Cyrus License: CMU @@ -128,6 +170,41 @@ License: CMU AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +License: FPL + Redistribution and use in source and binary forms, with or without + modification, are permitted provided that the following conditions + are met: + . + 1. Redistributions of source code must retain the above copyright +notice, this list of conditions and the following disclaimer. + . + 2. Redistributions in binary form must reproduce the above copyright +notice, this list of conditions and the following disclaimer in +the documentation and/or other materials provided with the +distribution. + . + 3. The name "Fastmail Pty Ltd" must not be used to +endorse or promote products derived from this software without +prior written permission. For permission or any legal +details, please contact + FastMail Pty Ltd + PO Box 234 + Collins St West 8007 + Victoria + Australia + . + 4. Redistributions of any form whatsoever must retain the following +acknowledgment: +"This product includes software developed by Fastmail Pty. Ltd." + . + FASTMAIL PTY LTD DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, + INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO + EVENT SHALL OPERA SOFTWARE AUSTRALIA BE LIABLE FOR ANY SPECIAL, INDIRECT + OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF + USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER + TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE + OF THIS SOFTWARE. + License: Expat Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to @@ -146,6 +223,12 @@ License: Expat AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNEC- TION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. +License: FSFAPL + Copying and distribution of this file, with or without modification, + are
Processed: unblock: cyrus-imapd/3.6.1-4
Processing control commands: > affects -1 + src:cyrus-imapd Bug #1033810 [release.debian.org] unblock: cyrus-imapd/3.6.1-4 Added indication that 1033810 affects src:cyrus-imapd -- 1033810: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033810 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033766: marked as done (bullseye-pu: package cyrus-imapd/3.6.1-4)
Your message dated Sun, 2 Apr 2023 07:32:25 +0400 with message-id and subject line Re: Bug#1033766: bullseye-pu: package cyrus-imapd/3.6.1-4 has caused the Debian Bug report #1033766, regarding bullseye-pu: package cyrus-imapd/3.6.1-4 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1033766: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033766 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal Tags: bullseye User: release.debian@packages.debian.org Usertags: pu X-Debbugs-Cc: cyrus-im...@packages.debian.org Control: affects -1 + src:cyrus-imapd [ Reason ] debian/copyright was incomplete [ Impact ] Incomplete copyright [ Tests ] No change, test passed. Note that autopkgtest works but has been disabled on Debian machines (too long). [ Risks ] No risk here, no code change. [ 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 ] Update of debian/copyright Cheers, Yadd diff --git a/debian/changelog b/debian/changelog index 9d1408cb..a6d3c31a 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +cyrus-imapd (3.6.1-4) unstable; urgency=medium + + * Update copyright + * Declare compliance with policy 4.6.2 + + -- Yadd Fri, 31 Mar 2023 11:12:57 +0400 + cyrus-imapd (3.6.1-2) unstable; urgency=medium [ Remus-Gabriel Chelu ] diff --git a/debian/control b/debian/control index ad383b18..d20e0f52 100644 --- a/debian/control +++ b/debian/control @@ -51,7 +51,7 @@ Build-Depends: bison, unicode-data, xxd, xutils-dev -Standards-Version: 4.6.1 +Standards-Version: 4.6.2 Vcs-Browser: https://salsa.debian.org/debian/cyrus-imapd Vcs-Git: https://salsa.debian.org/debian/cyrus-imapd.git Homepage: https://www.cyrusimap.org/ diff --git a/debian/copyright b/debian/copyright index b6d376e4..1049ba5c 100644 --- a/debian/copyright +++ b/debian/copyright @@ -7,6 +7,43 @@ Files: * Copyright: 1994-2020, Carnegie Mellon University License: CMU +Files: cassandane/* +Copyright: 2011 Opera Software Australia Pty. Ltd. +License: OSAP + +Files: cassandane/Cassandane/* + cassandane/utils/crash.c +Copyright: 2011-2022 Fastmail Pty Ltd +License: FPL + +Files: cmulocal/ax_cxx_compile_stdcxx_11.m4 +Copyright: 2008 Benjamin Kosnik + 2012 Zack Weinberg + 2013 Roy Stogner + 2014, 2015 Google Inc., contributed by Alexey Sokolov + 2015 Paul Norman +License: FSFAPL + +Files: cmulocal/ax_prog_perl_modules.m4 +Copyright: 2009 Dean Povey +License: FSFAPL + +Files: cmulocal/*.m4 + compile + config.* + ylwrap +Copyright: 1992-2022 Free Software Foundation, Inc. +License: GPL-2+ + +Files: cmulocal/ax_python_module.m4 +Copyright: 2008 Andrew Collier +License: FSFAPL + +Files: com_err/et/* +Copyright: 1987, 1988 by the Student Information Processing Board of the + Massachusetts Institute of Technology +License: MIT + Files: debian/* Copyright: 1997, Joey Hess 2001-2010, Henrique de Moraes Holschuh @@ -18,6 +55,11 @@ Copyright: 1997, Joey Hess 2019-2022, Yadd License: GPL-2+ +Files: doc/* +Copyright: 1993–2023 The Cyrus Team +License: CMU +Comment: Built with Sphinx, license BSD-2-Clause + Files: imap/objectstore_caringo.c Copyright: 2015 OpenIO, as a part of Cyrus License: CMU @@ -128,6 +170,41 @@ License: CMU AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +License: FPL + Redistribution and use in source and binary forms, with or without + modification, are permitted provided that the following conditions + are met: + . + 1. Redistributions of source code must retain the above copyright +notice, this list of conditions and the following disclaimer. + . + 2. Redistributions in binary form must reproduce the above copyright +notice, this list of conditions and the following disclaimer in +the documentation and/or other materials provided with the +distribution. + . + 3. The name "Fastmail Pty Ltd" must not be used to +endorse or promote products derived from this software without +prior written permission. For permission or any legal +details, please contact + FastMail Pty Ltd + PO Box 234 + Collins St West 8007 + Victoria + Australia + . + 4. Redistributions of any form whatsoever must retain the following +acknowledgment: +"This product includes software developed
Bug#1033770: bullseye-pu: package apache2/2.4.56-1~deb11u2
Control: tags -1 - confirmed
On 4/1/23 22:47, Moritz Mühlenhoff wrote:
Am Sat, Apr 01, 2023 at 08:32:55AM +0400 schrieb Yadd:
Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: apac...@packages.debian.org
Control: affects -1 + src:apache2
[ Reason ]
apache2 silently reenable apache2-doc.conf despite having been disabled
(#1018718)
If we update Apache in Bullseye, how about also adding patches for
#1033408 and #1033284?
Cheers,
Moritz
Hi,
here is the new debdiff
Cheers,
Yadddiff --git a/debian/NEWS b/debian/NEWS
new file mode 100644
index ..c048ae45
--- /dev/null
+++ b/debian/NEWS
@@ -0,0 +1,9 @@
+apache2 (2.4.56-1~deb11u2) bullseye; urgency=medium
+
+ This version does not automatically enable the apache2 config snippet for
+ /manual anymore. If you want to have it enabled you will need to do this
+ yourself, e.g. with
+
+/usr/sbin/a2enconf apache2-doc
+
+ -- Yadd Sat, 01 Apr 2023 08:17:08 +0400
diff --git a/debian/apache2-doc.postinst b/debian/apache2-doc.postinst
deleted file mode 100644
index e7e1e5a7..
--- a/debian/apache2-doc.postinst
+++ /dev/null
@@ -1,17 +0,0 @@
-#! /bin/sh
-
-set -e
-
-# conffiles must be moved before invoking rc.d
-#DEBHELPER#
-
-# This code should use dh_apache2 once it is available as build dependency
-
-if [ "$1" = "configure" ] ; then
- if [ -e /usr/share/apache2/apache2-maintscript-helper ] ; then
- . /usr/share/apache2/apache2-maintscript-helper
- apache2_invoke enconf apache2-doc || true
- fi
-fi
-
-exit
diff --git a/debian/changelog b/debian/changelog
index 41c3a7cc..e440c341 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,15 @@
+apache2 (2.4.56-1~deb11u2) bullseye; urgency=medium
+
+ [ Hendrik Jäger ]
+ * Don't automatically enable apache2-doc.conf (Closes: #1018718)
+
+ [ Yadd ]
+ * Fix regression in mod_rewrite introduced in version 2.4.56
+ (Closes: #1033284)
+ * Fix regression in http2 introduced by 2.4.56 (Closes: #1033408)
+
+ -- Yadd Sun, 02 Apr 2023 07:06:01 +0400
+
apache2 (2.4.56-1~deb11u1) bullseye-security; urgency=medium
* New upstream version (Closes: #1032476, CVE-2023-27522, CVE-2023-25690)
diff --git a/debian/patches/fix-2.4.56-regression-2.patch
b/debian/patches/fix-2.4.56-regression-2.patch
new file mode 100644
index ..d19373c0
--- /dev/null
+++ b/debian/patches/fix-2.4.56-regression-2.patch
@@ -0,0 +1,30 @@
+Description: h2 request headers clone instead of copy
+Author: Stefan Eissing
+Origin: upstream,
https://bz.apache.org/bugzilla/attachment.cgi?id=38527=diff
+Bug: https://bz.apache.org/bugzilla/show_bug.cgi?id=66539
+Bug-Debian: https://bugs.debian.org/1033408
+Forwarded: not-needed
+Applied-Upstream: 2.4.57
+Reviewed-By: Yadd
+Last-Update: 2023-04-02
+
+--- a/modules/http2/h2_request.c
b/modules/http2/h2_request.c
+@@ -279,7 +279,7 @@
+ apr_bucket *h2_request_create_bucket(const h2_request *req, request_rec *r)
+ {
+ conn_rec *c = r->connection;
+-apr_table_t *headers = apr_table_copy(r->pool, req->headers);
++apr_table_t *headers = apr_table_clone(r->pool, req->headers);
+ const char *uri = req->path;
+
+ AP_DEBUG_ASSERT(req->authority);
+@@ -303,7 +303,7 @@
+ {
+ const char *cl;
+
+-r->headers_in = apr_table_copy(r->pool, req->headers);
++r->headers_in = apr_table_clone(r->pool, req->headers);
+ if (req->authority) {
+ /* for internal handling, we have to simulate that :authority
+ * came in as Host:, RFC 9113 ch. says that mismatches between
diff --git a/debian/patches/fix-2.4.56-regression.patch
b/debian/patches/fix-2.4.56-regression.patch
new file mode 100644
index ..0203491d
--- /dev/null
+++ b/debian/patches/fix-2.4.56-regression.patch
@@ -0,0 +1,19 @@
+Description: fix 2.4.56 regression
+Author: covener
+Bug-Debian: https://bugs.debian.org/1033284
+Origin: upstream,
http://svn.apache.org/viewvc/httpd/httpd/trunk/modules/mappers/mod_rewrite.c?r1=1908813=1908812=1908813
+Forwarded: not-needed
+Applied-Upstream: 2.4.57
+Reviewed-By: Yadd
+Last-Update: 2023-04-01
+
+--- a/modules/mappers/mod_rewrite.c
b/modules/mappers/mod_rewrite.c
+@@ -3854,6 +3854,7 @@
+ if (*(a2_end-1) == '?') {
+ /* a literal ? at the end of the unsubstituted rewrite rule */
+ newrule->flags |= RULEFLAG_QSNONE;
++ *(a2_end-1) = '\0'; /* trailing ? has done its job */
+ }
+ else if (newrule->flags & RULEFLAG_QSDISCARD) {
+ if (NULL == ap_strchr(newrule->output, '?')) {
diff --git a/debian/patches/series b/debian/patches/series
index aa0aae42..6d738242 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -4,6 +4,8 @@ suexec-CVE-2007-1742.patch
customize_apxs.patch
build_suexec-custom.patch
reproducible_builds.diff
+fix-2.4.56-regression.patch
+fix-2.4.56-regression-2.patch
# This patch is applied manually
#suexec-custom.patch
Processed: Re: bullseye-pu: package apache2/2.4.56-1~deb11u2
Processing control commands: > tags -1 - confirmed Bug #1033770 [release.debian.org] bullseye-pu: package apache2/2.4.56-1~deb11u2 Removed tag(s) confirmed. -- 1033770: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033770 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1032237: bullseye-pu: zfs-linux/2.0.3-9+deb11u1
Processing control commands: > tags -1 - moreinfo Bug #1032237 [release.debian.org] bullseye-pu: package zfs-linux/2.0.3-9+deb11u1 Removed tag(s) moreinfo. -- 1032237: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032237 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1032237: bullseye-pu: zfs-linux/2.0.3-9+deb11u1
Control: tags -1 - moreinfo On Sun, Apr 2, 2023 at 3:10 AM Adam D. Barratt wrote: > > Control: tags -1 + moreinfo > > On Thu, 2023-03-02 at 15:33 +0800, Aron Xu wrote: > > I would like to apply a few patches to address some stability issues > > in the > > zfs-linux package in bullseye. All the patches are cherry-picked from > > upstream > > > > 2.0.x and 2.1.x stable branches. > > > > +This change reworks the zfs_file_[get|put] interface to not rely > +on the file descriptor but instead pass the zfs_file_t pointer around. > > I'm assuming that nothing outside of zfs-linux depends on the signature > of the affected functions? > No, there are no other packages depending on the signature of the affected functions. Regards, Aron
Bug#1027257: bullseye-pu: package golang-github-containers-storage/1.24.8+dfsg1-2~deb11u1
On 4/1/23 3:51 PM, Adam D. Barratt wrote:
Control: tags -1 + moreinfo
Apologies for the delay in getting back to you on this.
On Wed, 2022-12-28 at 22:26 -0500, Reinhard Tartler wrote:
In order to fix CVE-2022-1227, an update to golang-github-containers-
psgo
is needed, more specifically,
https://github.com/containers/psgo/pull/92
That patch introduces a dependency on golang-github-containers-
storage, and uses
the helper functions RawTo{Container,Host} which are introduced with
this patch.
[...]
The code changes adds a helper function that isn't used otherwise
yet.
Looking at the diff, it appears that what it actually does is rename
two existing helper functions, with no functional change to either. Am
I missing something?
You are correct. The patch renames the helper functions to an Uppercase
spelling.
This exposes the function to other packages, which is being used in the patch
to fix CVE-2022-1227.
I would recommend approving this code change.
+golang-github-containers-storage (1.24.8+dfsg1-2~deb11u1) bullseye;
urgency=medium
Given what I can see of the package's upload history, the version
should rather be 1.24.8+dfsg1-1+deb11u1.
Will do!
-rt
Bug#1025654: bullseye-pu: package x4d-icons/1.2-2+deb11u1
El 1/4/23 a las 21:58, Adam D. Barratt escribió:
Have you confirmed via a binary debdiff that there are no changes to
the resulting packages?
The package contents is the expected one:
$ debdiff x4d-icons_1.2-2_all.deb x4d-icons_1.2-2+deb11u1_all.deb
File lists identical (after any substitutions)
Control files: lines which differ (wdiff format)
Installed-Size: [-1188-] {+1187+}
Version: [-1.2-2-] {+1.2-2+deb11u1+}
The icons themselves are not bit-for-bit identical, but I think
they can't really be expected to be, considering that the old package
was built in 2019-03-12 with possibly different libraries.
They look certainly the same to the eye when using a png/gif viewer
or a eps viewer, so I believe everything is ok.
Thanks.
Bug#1033807: unblock: librest/0.9.1-6
Package: release.debian.org Control: affects -1 + src:librest X-Debbugs-Cc: libr...@packages.debian.org User: release.debian@packages.debian.org Usertags: unblock Please unblock package librest [ Reason ] This update fixes missing dependencies in the gir packages and in the -dev package. It also fixes several issues for Multi-Arch. [ Impact ] The impact may be minor. gnome-maps is the only thing that uses the gir package and it has the correct dependencies to work in Bookworm. However, gnome-maps from Experimental needed this fix. But it is still good for gir and dev packages to have correct dependencies, to enable ease of use by things outside of Debian. [ Tests ] Minimal upstream tests are run with dh_auto_test and would fail the build if they failed. No autopkgtest yet, sorry. A manual review of the amd64 build log shows the dependencies look correct. [ Risks ] [ 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 testing [ Other info ] unblock librest/0.9.1-6 Thank you, Jeremy Bicha librest-unblock-20230401.debdiff Description: Binary data
Processed: unblock: librest/0.9.1-6
Processing control commands: > affects -1 + src:librest Bug #1033807 [release.debian.org] unblock: librest/0.9.1-6 Added indication that 1033807 affects src:librest -- 1033807: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033807 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
NEW changes in stable-new
Processing changes file: debian-archive-keyring_2021.1.1+deb11u1_all-buildd.changes ACCEPT Processing changes file: libdatetime-timezone-perl_2.47-1+2023c_all-buildd.changes ACCEPT
Bug#1026845: bullseye-pu: package systemd/247.3-7+deb11u2
Control: tags -1 + confirmed d-i On Thu, 2022-12-22 at 12:13 +, Luca Boccassi wrote: > We'd like to upload several bug fixes, including security fixes, for > systemd to bullseye. > The fixes come from the upstream stable branches which are covered by > CI and confirmed by reporters. > Please go ahead; sorry for the delay. Regards, Adam
Processed: Re: Bug#1026845: bullseye-pu: package systemd/247.3-7+deb11u2
Processing control commands: > tags -1 + confirmed d-i Bug #1026845 [release.debian.org] bullseye-pu: package systemd/247.3-7+deb11u2 Added tag(s) confirmed and d-i. -- 1026845: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026845 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1025703: bullseye-pu: package libexplain/1.4.D001-11+deb11u1
Control: tags -1 + confirmed On Wed, 2022-12-07 at 19:37 +0100, Santiago Vila wrote: > I'd like to make this QA upload to fix FTBFS bug #997222 in > bullseye, > plus allow compilation with kernels slightly newer than the one in > bullseye (for example bullseye-backports). > > The two patches are taken verbatim from bookworm/sid, where this was > fixed one year ago. > Please go ahead; sorry for the delay. Regards, Adam
Processed: Re: Bug#1025703: bullseye-pu: package libexplain/1.4.D001-11+deb11u1
Processing control commands: > tags -1 + confirmed Bug #1025703 [release.debian.org] bullseye-pu: package libexplain/1.4.D001-11+deb11u1 Added tag(s) confirmed. -- 1025703: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025703 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1025654: bullseye-pu: package x4d-icons/1.2-2+deb11u1
Processing control commands: > tags -1 + moreinfo Bug #1025654 [release.debian.org] bullseye-pu: package x4d-icons/1.2-2+deb11u1 Added tag(s) moreinfo. -- 1025654: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025654 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1025654: bullseye-pu: package x4d-icons/1.2-2+deb11u1
Control: tags -1 + moreinfo On Tue, 2022-12-06 at 23:47 +0100, Santiago Vila wrote: > I'd like to fix FTBFS bug #991067 in stable using the attached > debdiff > (not uploaded yet). > Apologies for the delay in getting back to you on this. > The way the FTBFS is fixed is the same I used in upload 1.2-5 which > I > did today for unstable (this upload replaces a previous workaround > which > merely fixed the ftbfs problem by dropping the eps files and thus > losing > functionality). > > You will notice that I have decided to raise debhelper compatibility > level. I am well aware that this should not be done lightly and > without a good reason. > Have you confirmed via a binary debdiff that there are no changes to the resulting packages? Regards, Adam
Processed: Re: Bug#1027257: bullseye-pu: package golang-github-containers-storage/1.24.8+dfsg1-2~deb11u1
Processing control commands: > tags -1 + moreinfo Bug #1027257 [release.debian.org] bullseye-pu: package golang-github-containers-storage/1.24.8+dfsg1-2~deb11u1 Added tag(s) moreinfo. -- 1027257: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027257 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1027257: bullseye-pu: package golang-github-containers-storage/1.24.8+dfsg1-2~deb11u1
Control: tags -1 + moreinfo
Apologies for the delay in getting back to you on this.
On Wed, 2022-12-28 at 22:26 -0500, Reinhard Tartler wrote:
> In order to fix CVE-2022-1227, an update to golang-github-containers-
> psgo
> is needed, more specifically,
> https://github.com/containers/psgo/pull/92
>
> That patch introduces a dependency on golang-github-containers-
> storage, and uses
> the helper functions RawTo{Container,Host} which are introduced with
> this patch.
>
[...]
> The code changes adds a helper function that isn't used otherwise
> yet.
Looking at the diff, it appears that what it actually does is rename
two existing helper functions, with no functional change to either. Am
I missing something?
> +golang-github-containers-storage (1.24.8+dfsg1-2~deb11u1) bullseye;
> urgency=medium
>
Given what I can see of the package's upload history, the version
should rather be 1.24.8+dfsg1-1+deb11u1.
Regards,
Adam
Bug#1027258: bullseye-pu: package golang-github-containers-psgo/1.5.2-2~deb11u1
Control: tags -1 + moreinfo On Wed, 2022-12-28 at 22:40 -0500, Reinhard Tartler wrote: > Backport for CVE-2022-1227, taken from > https://github.com/containers/psgo/pull/92 > > This prevents an exploit when running 'podman top' > Apologies for the delay in getting back to you regarding this. +golang-github-containers-psgo (1.5.2-2~deb11u1) bullseye; urgency=medium Given that there's never been more than one upload of 1.5.2 so far as I can see, that should be 1.5.2-1+deb11u1. + * CVE-2022-1227: do not join the process user namespace [...] Build-Depends-Indep: golang-any, + golang-github-containers-storage-dev (>= 1.24.8+dfsg1-2~deb11u1), Similarly I'd expect this to be 1.24.8+dfsg1-1+deb11u1, as I can only see one upload of 1.24.8+dfsg1 ever having been made to Debian. Regards, Adam
Processed: Re: Bug#1027258: bullseye-pu: package golang-github-containers-psgo/1.5.2-2~deb11u1
Processing control commands: > tags -1 + moreinfo Bug #1027258 [release.debian.org] bullseye-pu: package golang-github-containers-psgo/1.5.2-2~deb11u1 Added tag(s) moreinfo. -- 1027258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027258 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1029142: bullseye-pu: package geeqie/1:1.6-9+deb11u2 (pre-approval)
Processing control commands: > tags -1 + moreinfo Bug #1029142 [release.debian.org] bullseye-pu: package geeqie/1:1.6-9+deb11u2 (pre-approval) Added tag(s) moreinfo. -- 1029142: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029142 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1029142: bullseye-pu: package geeqie/1:1.6-9+deb11u2 (pre-approval)
Control: tags -1 + moreinfo On Wed, 2023-01-18 at 15:13 +0100, Andreas Rönnquist wrote: > The clutter library is buggy, to the extent that geeqie might crash > if > not ran without it. This fix simply removes the libchamplain > dependency > (which in it's turn depends on clutter). This makes it possible and > easier to run geeqie without the need for the cli --disable-clutter > argument. (Fixes #1027753 [1], and please also see #1018123 [2]) > > Apologies for the delay in getting back to you on this. Presumably geeqie doesn't actually use libchamplain? If so, why does it depend on it to begin with? Looking at the diff, I think the change is actually the removal of a /build/ dependency, not a runtime one? If so, it would be good if that were slightly clearly in the changelog. Regards, Adam
Bug#1033694: marked as done (unblock: gortr/0.14.7-2)
Your message dated Sat, 1 Apr 2023 21:35:04 +0200
with message-id
and subject line Re: Bug#1033694: unblock: gortr/0.14.7-2
has caused the Debian Bug report #1033694,
regarding unblock: gortr/0.14.7-2
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1033694: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033694
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: go...@packages.debian.org
Control: affects -1 + src:gortr
Please unblock package gortr
I do not want to ship gortr in bookworm because it is unmaintained, but
other software needs the Go library which comes from this same package.
So I made minimal changes to the package to only build the library.
Full diff attached.
unblock gortr/0.14.7-2
--
ciao,
Marco
diff -Nru gortr-0.14.7/debian/changelog gortr-0.14.7/debian/changelog
--- gortr-0.14.7/debian/changelog 2021-01-03 09:17:16.0 +0100
+++ gortr-0.14.7/debian/changelog 2023-03-27 22:43:29.0 +0200
@@ -1,3 +1,10 @@
+gortr (0.14.7-2) unstable; urgency=medium
+
+ * Stop building gortr because it is unmaintained and has been generally
+replaced by stayrtr.
+
+ -- Marco d'Itri Mon, 27 Mar 2023 22:43:29 +0200
+
gortr (0.14.7-1) unstable; urgency=medium
* New upstream release.
diff -Nru gortr-0.14.7/debian/control gortr-0.14.7/debian/control
--- gortr-0.14.7/debian/control 2021-01-03 09:16:21.0 +0100
+++ gortr-0.14.7/debian/control 2023-03-27 22:42:40.0 +0200
@@ -4,36 +4,27 @@
Section: net
Testsuite: autopkgtest-pkg-go
Priority: optional
-Build-Depends: debhelper-compat (= 12), dh-golang,
+Build-Depends: debhelper-compat (= 13), dh-golang,
golang-any,
golang-github-prometheus-client-golang-dev,
golang-github-stretchr-testify-dev,
golang-golang-x-crypto-dev,
golang-logrus-dev,
-Standards-Version: 4.5.0
+Standards-Version: 4.6.2.0
Vcs-Browser: https://salsa.debian.org/md/gortr
Vcs-Git: https://salsa.debian.org/md/gortr.git
Homepage: https://github.com/cloudflare/gortr
Rules-Requires-Root: no
XS-Go-Import-Path: github.com/cloudflare/gortr
-Package: gortr
-Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends},
- adduser
-Built-Using: ${misc:Built-Using}
-Description: Cloudflare's RPKI to Router server
- GoRTR is an implementation of the RPKI to Router protocol (RFC 6810):
- it can be used to publish Resource Public Key Infrastructure (RFC 6480)
- prefix origin data from a trusted cache to BGP routers.
-
Package: golang-github-cloudflare-gortr-dev
Architecture: all
-Section: devel
+Section: golang
Depends: ${misc:Depends},
golang-github-prometheus-client-golang-dev,
golang-github-stretchr-testify-dev,
golang-golang-x-crypto-dev,
golang-logrus-dev,
+Multi-Arch: foreign
Description: Cloudflare's RPKI to router library
GoRTR is an implementation of the RPKI to router protocol (RFC 6810).
diff -Nru gortr-0.14.7/debian/rules gortr-0.14.7/debian/rules
--- gortr-0.14.7/debian/rules 2021-01-03 09:16:21.0 +0100
+++ gortr-0.14.7/debian/rules 2023-03-27 22:33:18.0 +0200
@@ -1,5 +1,11 @@
#!/usr/bin/make -f
+# only build the library
+export DH_GOLANG_EXCLUDES := cmd/
+
%:
dh $@ --builddirectory=_build --buildsystem=golang --with=golang
+override_dh_auto_install:
+ dh_auto_install --destdir=debian/tmp
+
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Hi,
On 30-03-2023 13:05, Marco d'Itri wrote:
Please unblock package gortr
The excuses have:
not blocked: has successful autopkgtest
Closing the bug as no action is required.
Paul
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
Bug#1033798: unblock: lazarus/2.2.6+dfsg1-1
Control: retitle -1 unblock: lazarus/2.2.6+dfsg1-2
Another bug was fixed in order to allow building Lazarus for armel architecture.
This bug is just disabling a compilation switch in a source file.
The removed compilation switch forces to disable the FPU emulation, which does
not have any sense on armel as it does not have any hardware FPU.
The fix should not alter other architectures as when the switch is not supplied,
FPC will decide automatically whether to use HW FPU of emulation.
Attached the debdiff of this altest modification.
--
Cheers,
Abou Al Montacir
diff -Nru lazarus-2.2.6+dfsg1/debian/changelog lazarus-2.2.6+dfsg1/debian/changelog
--- lazarus-2.2.6+dfsg1/debian/changelog 2023-03-31 19:51:15.0 +0200
+++ lazarus-2.2.6+dfsg1/debian/changelog 2023-04-01 19:28:43.0 +0200
@@ -1,3 +1,9 @@
+lazarus (2.2.6+dfsg1-2) unstable; urgency=medium
+
+ * Fixed compilation of test suite on armel.
+
+ -- Abou Al Montacir Sat, 01 Apr 2023 19:28:43 +0200
+
lazarus (2.2.6+dfsg1-1) unstable; urgency=medium
* New upstream version 2.2.6+dfsg1
diff -Nru lazarus-2.2.6+dfsg1/debian/patches/Fixed-compilation-of-testsuite-on-armel.patch lazarus-2.2.6+dfsg1/debian/patches/Fixed-compilation-of-testsuite-on-armel.patch
--- lazarus-2.2.6+dfsg1/debian/patches/Fixed-compilation-of-testsuite-on-armel.patch 1970-01-01 01:00:00.0 +0100
+++ lazarus-2.2.6+dfsg1/debian/patches/Fixed-compilation-of-testsuite-on-armel.patch 2023-04-01 19:26:12.0 +0200
@@ -0,0 +1,23 @@
+Description: Fixed compilation of test suite on armel.
+ The crash was due to a source file disabling FPU emulation.
+ However, on armel, FPU emulation is needed as no hardware FPU
+ is present.
+ .
+ This patch removed the compiler flag that disabled the FPU emulation.
+ This should not harm, as on other targets, the compiler will by default use
+ the hardware FPU.
+Author: Abou Al Montacir
+
+diff --git a/components/lazreport/source/addons/addfunction/frFuncNum.pas b/components/lazreport/source/addons/addfunction/frFuncNum.pas
+index 769a340d..75e9c037 100644
+--- a/components/lazreport/source/addons/addfunction/frFuncNum.pas
b/components/lazreport/source/addons/addfunction/frFuncNum.pas
+@@ -10,7 +10,7 @@ unit frFuncNum;
+
+ interface
+
+-{$A+,B-,E-,R-}
++{$A+,B-,R-}
+ {.$I FR.inc}
+
+ uses
diff -Nru lazarus-2.2.6+dfsg1/debian/patches/series lazarus-2.2.6+dfsg1/debian/patches/series
--- lazarus-2.2.6+dfsg1/debian/patches/series 2023-03-31 19:51:08.0 +0200
+++ lazarus-2.2.6+dfsg1/debian/patches/series 2023-04-01 19:26:12.0 +0200
@@ -8,3 +8,4 @@
Fixed-end-of-line-for-resource-file.diff
Fixed-allowing-arbitrary-FPPKG-path.patch
Added-missing-source-file.patch
+Fixed-compilation-of-testsuite-on-armel.patch
diff -Nru lazarus-2.2.6+dfsg1/debian/source/timestamps lazarus-2.2.6+dfsg1/debian/source/timestamps
--- lazarus-2.2.6+dfsg1/debian/source/timestamps 2023-03-25 15:09:07.0 +0100
+++ lazarus-2.2.6+dfsg1/debian/source/timestamps 2023-04-01 19:28:07.0 +0200
@@ -1,5 +1,6 @@
components/PascalScript/Source/arm.inc 2020-08-08T09:46+00:00
components/PascalScript/Source/pascalscriptfcl.pas 2022-01-28T09:54+00:00
+components/lazreport/source/addons/addfunction/frFuncNum.pas 2023-04-01T17:28+00:00
ide/codehelp.pas 2020-07-11T19:46+00:00
ide/generatefppkgconfigurationdlg.pas 2022-01-16T13:55+00:00
lcl/include/lcl_defines.inc 2020-07-11T19:46+00:00
signature.asc
Description: This is a digitally signed message part
Processed: Re: Bug#1033653: bullseye-pu: package lemonldap-ng/2.0.11+ds-4+deb11u
Processing control commands: > tags -1 + confirmed Bug #1033653 [release.debian.org] bullseye-pu: package lemonldap-ng/2.0.11+ds-4+deb11u4 Bug #1030598 [release.debian.org] bullseye-pu: package lemonldap-ng/2.0.11+ds-4+deb11u3 Added tag(s) confirmed. Added tag(s) confirmed. -- 1030598: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030598 1033653: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033653 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: unblock: lazarus/2.2.6+dfsg1-1
Processing control commands: > retitle -1 unblock: lazarus/2.2.6+dfsg1-2 Bug #1033798 [release.debian.org] unblock: lazarus/2.2.6+dfsg1-1 Changed Bug title to 'unblock: lazarus/2.2.6+dfsg1-2' from 'unblock: lazarus/2.2.6+dfsg1-1'. -- 1033798: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033798 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033653: bullseye-pu: package lemonldap-ng/2.0.11+ds-4+deb11u
Control: tags -1 + confirmed On Wed, 2023-03-29 at 16:26 +0400, Yadd wrote: > lemonldap-ng is vulnarable to a second factor bypass when used with > an > "AuthBasic handler" (generally used for non-browser apps). > [...] > I didn't pushed yet the already accepted patch for deb11u3 > (#1030598). > Maybe we could join and push directly deb11u4 into Bullseye. > Apparently you also merged the bug reports, thus removing the indication that the previous update had already been approved. In future, please don't do that, it makes the tracking a little more confusing. Please go ahead. Regards, Adam
Bug#1032614: ddcutil: pre-approval request ddcutil-1.4.2-1 fixes bug #1031259
On 2023-03-13 19:00:22 +0100, Sebastian Ramacher wrote: > On 2023-03-13 13:28:47 -0400, Sanford Rockowitz wrote: > > On 3/13/23 07:42, Sebastian Ramacher wrote: > > > On 2023-03-13 07:25:41 -0400, Sanford Rockowitz wrote: > > > > On 3/13/23 05:33, Sebastian Ramacher wrote: > > > > > On 2023-03-11 07:51:16 -0500, Sanford Rockowitz wrote: > > > > > > [Reason ] > > > > > > (Explain what the reason for the unblock request is.) > > > > > > As noted, the unblock request addresses bug #1031259. ddcutil > > > > > > requires > > > > > > driver i2c-dev. If it happens not to be built into the kernel, > > > > > > this entails > > > > > > post-installation system configuration. Despite extensive > > > > > > documentation and > > > > > > application warnings if the driver is not loaded, this can be > > > > > > challenging > > > > > > for inexperienced users. > > > > > > > > > > > > > [ Impact ] > > > > > > > (What is the impact for the user if the unblock isn't granted?) > > > > > > Manual post installation configuration will continue to be required > > > > > > as > > > > > > previously. > > > > > > > [ Tests ] > > > > > > > (What automated or manual tests cover the affected code?) > > > > > > None > > > > > > > [ Risks ] > > > > > > > (Discussion of the risks involved. E.g. code is trivial or > > > > > > > complex, key package vs leaf package, alternatives available.) > > > > > > The changes are trivial, ensuring that driver i2c-dev is loaded if > > > > > > it is not > > > > > > already built into the kernel. Package libddccontrol0, an > > > > > > alternative to > > > > > > ddcutil for monitor control, installs file ddccontrol-i2c-dev.conf, > > > > > > which > > > > > > loads i2c-dev. The contents of that file, a single line containing > > > > > > "i2c-dev", is identical to the contents of the files to be > > > > > > installed by > > > > > > ddcutil. Additional examples of packages that install files in > > > > > > /user/lib/modules-load.d are fwupd, which installs file > > > > > > fwupd-msc.conf, and > > > > > > encryptfs-utils, which installs file ecryptfs.conf. > > > > > The prpoposed changes also introduce a policy violation: > > > > > /usr/lib/modules-load.d/libddcutil.conf installed in libddcutil4 is > > > > > not > > > > > versioned the same way as the shared library. See section 8.2 for more > > > > > details. > > > > > > > > > > Cheers > > > > > > > > > > > If the installed conf file were incorrect, the only effect would be > > > > > > an error > > > > > > in the system log, and manual user configuration would still be > > > > > > required as > > > > > > before. > > > > > > > > > > > > The only (potential) known dependency within Debian is from KDE > > > > > > PowerDevil. However, PowerDevil, as installed by Debian, is built > > > > > > with use > > > > > > of libddcutil if-tested out. (Recommended since its use of > > > > > > libddcutil is > > > > > > "proof of concept" level code.) > > > > > > > > > > > > > [ 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 testing > > > > > > > > > > > > > > [ Other info ] > > > > > > > (Anything else the release team should know.) > > > > As I read section 8.2, there are two possibilities. The first is to > > > > version > > > > the name of the file installed in /usr/lib/modules-load.d, e.g. > > > > libddcutil4.conf for package libddcutil4. The second is to create an > > > > additional package, named e.g. libddcutil-aux, that installs > > > > libddcutil.conf > > > > and on which package libddcutil4 and successor packages libddcutilN > > > > depend. > > > > The former has the advantage that it doesn't introduce an additional > > > > package > > > > simply to install a single file, and the disadvantage that it relies on > > > > a > > > > naming convention for the installed libddcutilN.conf file, which could > > > > easily be overlooked when bumping the SONAME. > > > As we're in hard freeze, option 2 is not an option for bookworm. > > > > > > > A third alternative is to not install a modules-load.d conf file for > > > > libddcutil, and instead rely on packages using the shared library to > > > > install > > > > a conf file. But that would multiply the number of packages installing > > > > files in modules-load.d, and the potential for errors. > > > That doesn't really sound like a solution to the bug. It would leak > > > implementation details of libddcutil to all the reverse dependencies. > > > > > > Cheers > > Setting aside what's possible given the bookworm freeze, do you have a > > strong opinion as to whether the naming convention or separate package is > > preferable/acceptable? I don't feel strongly that the update has to go into > > bookworm. I wanted to address the "bug report" promptly, but the change is > > more of an enhancement. Nothing is really actually broken, it's
Processed: Re: Bug#1031097: bullseye-pu: package conmon/2.0.25+ds1-1.1
Processing control commands: > tags -1 + confirmed Bug #1031097 [release.debian.org] bullseye-pu: package conmon/2.0.25+ds1-1.1 Added tag(s) confirmed. -- 1031097: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031097 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1031097: bullseye-pu: package conmon/2.0.25+ds1-1.1
Control: tags -1 + confirmed On Sat, 2023-02-11 at 19:03 +0100, Reinhard Tartler wrote: > conmon 2.0.25 contains a bug where the container will hang when there > is lots of terminal output. You can easily reproduce like so: > > podman run -it --rm debian:latest > find / > Please go ahead; sorry for the delay. Regards, Adam
Processed: Re: Bug#1031630: bullseye-pu: package containerd/1.4.13~ds1-1~deb11u4
Processing control commands: > tags -1 + confirmed Bug #1031630 [release.debian.org] bullseye-pu: package containerd/1.4.13~ds1-1~deb11u4 Added tag(s) confirmed. -- 1031630: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031630 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1031410: bullseye-pu: package postgis/3.1.1+dfsg-1+deb11u1
Processing control commands: > tags -1 + confirmed Bug #1031410 [release.debian.org] bullseye-pu: package postgis/3.1.1+dfsg-1+deb11u1 Added tag(s) confirmed. -- 1031410: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031410 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1031410: bullseye-pu: package postgis/3.1.1+dfsg-1+deb11u1
Control: tags -1 + confirmed On Thu, 2023-02-16 at 19:38 +0100, Bas Couwenberg wrote: > As reported in #1031392, postgis 3.1.1 has an important issue with > polar > stereographic projections which was resolved in 3.1.2. > > [ Impact ] > Unusable coordinates from transformations. > Please go ahead. Regards, Adam
Bug#1031109: bullseye-pu: package crun/0.17+dfsg-1+deb11u1
Control: tags -1 + confirmed On Sun, 2023-02-12 at 00:06 +0200, Faidon Liambotis wrote: > A no-dsa security vulnerability, CVE-2022-27650: > https://security-tracker.debian.org/tracker/CVE-2022-27650 > > [ Impact ] > Copying from the CVE: > > "A flaw was found in crun where containers were incorrectly started > with > non-empty default permissions. A vulnerability was found in Moby > (Docker > Engine) where containers were started incorrectly with non-empty > inheritable Linux process capabilities. This flaw allows an attacker > with access to programs with inheritable file capabilities to elevate > those capabilities to the permitted set when execve(2) runs." > Please go ahead; sorry for the delay. Regards, Adam
Bug#1031630: bullseye-pu: package containerd/1.4.13~ds1-1~deb11u4
Control: tags -1 + confirmed On Sun, 2023-02-19 at 22:56 +0800, Shengjing Zhu wrote: > Backport patches for 2 CVE: > > * CVE-2023-25153: OCI image importer memory exhaustion > * CVE-2023-25173: Supplementary groups are not set up properly > Please go ahead; sorry for the delay. Regards, Adam
Processed: Re: Bug#1031109: bullseye-pu: package crun/0.17+dfsg-1+deb11u1
Processing control commands: > tags -1 + confirmed Bug #1031109 [release.debian.org] bullseye-pu: package crun/0.17+dfsg-1+deb11u1 Added tag(s) confirmed. -- 1031109: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031109 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1031926: bullseye-pu: package gtk+3.0/3.24.24-4+deb11u3
Processing control commands: > tags -1 + confirmed Bug #1031926 [release.debian.org] bullseye-pu: package gtk+3.0/3.24.24-4+deb11u3 Added tag(s) confirmed. -- 1031926: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031926 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1031926: bullseye-pu: package gtk+3.0/3.24.24-4+deb11u3
Control: tags -1 + confirmed On Sat, 2023-02-25 at 12:05 +, Simon McVittie wrote: > User request via #1020937: make it possible to run GTK 3 apps in > native > Wayland on some proprietary GLES-only graphics drivers (Raspberry Pi > video core, iMX/Vivante). > Please go ahead, sorry for the delay. Regards, Adam
Bug#1031788: bullseye-pu: package publicsuffix/20230209.2326-0+deb11u1
Control: tags -1 + confirmed On Wed, 2023-02-22 at 13:48 -0500, Daniel Kahn Gillmor wrote: > Please consider an update to publicsuffix in debian bullseye. > > This package reflects the state of the network, and keeping it > current > is useful for all the packages that depend on it. > Please go ahead; sorry for the delay. Regards, Adam
Processed: Re: Bug#1031788: bullseye-pu: package publicsuffix/20230209.2326-0+deb11u1
Processing control commands: > tags -1 + confirmed Bug #1031788 [release.debian.org] bullseye-pu: package publicsuffix/20230209.2326-0+deb11u1 Added tag(s) confirmed. -- 1031788: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031788 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1031948: bullseye-pu: package libgit2/1.1.0+dfsg.1-4+deb11u1
Processing control commands: > tags -1 + confirmed Bug #1031948 [release.debian.org] bullseye-pu: package libgit2/1.1.0+dfsg.1-4+deb11u1 Added tag(s) confirmed. -- 1031948: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031948 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1031948: bullseye-pu: package libgit2/1.1.0+dfsg.1-4+deb11u1
Control: tags -1 + confirmed On Sat, 2023-02-25 at 21:16 +0100, Tobias Frost wrote: > After fixing CVE-2023-22742 for LTS and ELTS, I'd like to see > this CVE also fixed in stable, for consistency. > > The CVE is an inproper ssh certificate validation vulnerabilty, > which allows man-in-the-middle attacks. > +libgit2 (1.1.0+dfsg.1-4+deb11u1) bullseye-security; urgency=high That wants to just be "bullseye". + This is a backport of the upstream fix to the Debian stretch version. Presumably that comment could also do with an update. Please go ahead. Regards, Adam
Processed: Re: Bug#1032134: bullseye-pu: package node-cookiejar/2.1.2-1+deb11u1
Processing control commands: > tags -1 + confirmed Bug #1032134 [release.debian.org] bullseye-pu: package node-cookiejar/2.1.2-1+deb11u1 Added tag(s) confirmed. -- 1032134: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032134 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1032134: bullseye-pu: package node-cookiejar/2.1.2-1+deb11u1
Control: tags -1 + confirmed On Tue, 2023-02-28 at 18:00 +0400, Yadd wrote: > node-cookiejar is vulnerable to ReDoS (CVE-2022-25901). > Please go ahead. Regards, Adam
Processed: Re: Bug#1032237: bullseye-pu: zfs-linux/2.0.3-9+deb11u1
Processing control commands: > tags -1 + moreinfo Bug #1032237 [release.debian.org] bullseye-pu: package zfs-linux/2.0.3-9+deb11u1 Added tag(s) moreinfo. -- 1032237: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032237 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1032237: bullseye-pu: zfs-linux/2.0.3-9+deb11u1
Control: tags -1 + moreinfo On Thu, 2023-03-02 at 15:33 +0800, Aron Xu wrote: > I would like to apply a few patches to address some stability issues > in the > zfs-linux package in bullseye. All the patches are cherry-picked from > upstream > > 2.0.x and 2.1.x stable branches. > +This change reworks the zfs_file_[get|put] interface to not rely +on the file descriptor but instead pass the zfs_file_t pointer around. I'm assuming that nothing outside of zfs-linux depends on the signature of the affected functions? Regards, Adam
Processed: Re: Bug#1032299: bullseye-pu: package node-css-what/4.0.0-3
Processing control commands: > tags -1 + confirmed Bug #1032299 [release.debian.org] bullseye-pu: package node-css-what/4.0.0-3 Added tag(s) confirmed. -- 1032299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032299 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1032299: bullseye-pu: package node-css-what/4.0.0-3
Control: tags -1 + confirmed On Fri, 2023-03-03 at 08:57 +, Bastien Roucariès wrote: > CVE-2022-21222/CVE-2021-33587 The package css-what before 2.1.3 are > vulnerable > to Regular Expression Denial of Service (ReDoS) due to the usage of > insecure > regular expression in the re_attr variable of index.js. The > exploitation of > this vulnerability could be triggered via the parse function. > +node-css-what (4.0.0-3+deb11u1) bullseye-security; urgency=medium The distribution needs to simply be "bullseye" for a stable upload. With that change, please go ahead. Regards, Adam
Processed: Re: Bug#1033160: bullseye-pu: package flatpak/1.10.8-0+deb11u1
Processing control commands: > tags -1 + confirmed Bug #1033160 [release.debian.org] bullseye-pu: package flatpak/1.10.8-0+deb11u1 Added tag(s) confirmed. -- 1033160: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033160 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033160: bullseye-pu: package flatpak/1.10.8-0+deb11u1
Control: tags -1 + confirmed On Sat, 2023-03-18 at 16:20 +, Simon McVittie wrote: > CVE-2023-28101: A malicious Flatpak app could prevent the flatpak(1) > CLI > from displaying its permissions as intended, by having crafted > permissions > or other metadata containing terminal escape sequences or other > special > characters. (#1033098) > > CVE-2023-28100: A malicious Flatpak app could execute code outside > the > sandbox if run from a Linux virtual console. (#1033099) > > Additionally, the new upstream stable release has some other bug > fixes > backported from 1.12.x and 1.14.x for: > - temporary directories not being cleaned up if an upgrade is > cancelled, > in particular if it's blocked by parental controls (libmalcontent); > - the `flatpak history` command, which didn't previously work in > bullseye; > Please go ahead. Regards, Adam
Processed: Re: Bug#1032921: bullseye-pu: package node-webpack/4.43.0-6+deb11u1
Processing control commands: > tags -1 + confirmed Bug #1032921 [release.debian.org] bullseye-pu: package node-webpack/4.43.0-6+deb11u1 Added tag(s) confirmed. -- 1032921: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032921 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1032921: bullseye-pu: package node-webpack/4.43.0-6+deb11u1
Control: tags -1 + confirmed On Tue, 2023-03-14 at 08:01 +0400, Yadd wrote: > node-webpack is vulnerable to cross-realm object access > (#1032904, CVE-2023-28154) > Please go ahead. Regards, Adam
Processed: Re: Bug#1033578: bullseye-pu: package joblib/0.17.0-4+deb11u1
Processing control commands: > tags -1 + confirmed Bug #1033578 [release.debian.org] bullseye-pu: package joblib/0.17.0-4+deb11u1 Added tag(s) confirmed. -- 1033578: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033578 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1033759: bullseye-pu: duktape/2.5.0-2+deb11u1
Processing control commands: > tags -1 + confirmed Bug #1033759 [release.debian.org] bullseye-pu: duktape/2.5.0-2+deb11u1 Added tag(s) confirmed. -- 1033759: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033759 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033759: bullseye-pu: duktape/2.5.0-2+deb11u1
Control: tags -1 + confirmed On Fri, 2023-03-31 at 22:28 +, Thorsten Alteholz wrote: > The attached debdiff for duktape fixes CVE-2021-46322 in Bullseye. > Please go ahead. Regards, Adam
Bug#1033578: bullseye-pu: package joblib/0.17.0-4+deb11u1
Control: tags -1 + confirmed On Mon, 2023-03-27 at 19:42 +0200, Helmut Grohne wrote: > Fix no-dsa security vulnerability CVE-2022-21797. > > [ Impact ] > > The n_jobs parameter of the parallel_backend, which used to be a > string > containing a Python expression, becomes restricted to fairly basic > arithmetic expressions. Using it in another way was not intended. > Please go ahead. Regards, Adam
Processed: Re: Bug#1033506: bullseye-pu: package libreoffice/1:7.0.4-4+deb11u6
Processing control commands: > tags -1 + confirmed Bug #1033506 [release.debian.org] bullseye-pu: package libreoffice/1:7.0.4-4+deb11u6 Added tag(s) confirmed. -- 1033506: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033506 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033506: bullseye-pu: package libreoffice/1:7.0.4-4+deb11u6
Control: tags -1 + confirmed On Sun, 2023-03-26 at 14:23 +0200, Rene Engelhard wrote: > This fixes "CVE-2022-38745. Empty entry in Java class path risks > arbitrary code execution" just disclosed by Apache OpenOffice. > Please go ahead. Regards, Adam
Bug#1033770: bullseye-pu: package apache2/2.4.56-1~deb11u2
Am Sat, Apr 01, 2023 at 08:32:55AM +0400 schrieb Yadd: > Package: release.debian.org > Severity: normal > Tags: bullseye > User: release.debian@packages.debian.org > Usertags: pu > X-Debbugs-Cc: apac...@packages.debian.org > Control: affects -1 + src:apache2 > > [ Reason ] > apache2 silently reenable apache2-doc.conf despite having been disabled > (#1018718) If we update Apache in Bullseye, how about also adding patches for #1033408 and #1033284? Cheers, Moritz
Processed: Re: Bug#1033770: bullseye-pu: package apache2/2.4.56-1~deb11u2
Processing control commands: > tags -1 + confirmed Bug #1033770 [release.debian.org] bullseye-pu: package apache2/2.4.56-1~deb11u2 Added tag(s) confirmed. -- 1033770: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033770 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033770: bullseye-pu: package apache2/2.4.56-1~deb11u2
Control: tags -1 + confirmed On Sat, 2023-04-01 at 08:32 +0400, Yadd wrote: > apache2 silently reenable apache2-doc.conf despite having been > disabled > (#1018718) > > [ Impact ] > This behavior overwrites local changes on upgrade, which is a > release-critical bug as it’s a Policy violation > Please go ahead. Regards, Adam
Processed: Re: Bug#1033766: bullseye-pu: package cyrus-imapd/3.6.1-4
Processing control commands: > tags -1 + moreinfo Bug #1033766 [release.debian.org] bullseye-pu: package cyrus-imapd/3.6.1-4 Added tag(s) moreinfo. -- 1033766: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033766 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033766: bullseye-pu: package cyrus-imapd/3.6.1-4
Control: tags -1 + moreinfo On Sat, 2023-04-01 at 07:32 +0400, Yadd wrote: > debian/copyright was incomplete > The debdiff and package version both appear to be for unstable, not bullseye. In general, an update purely to licensing information isn't sufficient to justify a rebuild and update for all users of the package in stable as it's purely a documentation issue. Regards, Adam
NEW changes in stable-new
Processing changes file: debian-archive-keyring_2021.1.1+deb11u1_source.changes ACCEPT Processing changes file: libdatetime-timezone-perl_2.47-1+2023c_source.changes ACCEPT Processing changes file: xorg-server_1.20.11-1+deb11u6_source.changes ACCEPT Processing changes file: xorg-server_1.20.11-1+deb11u6_all-buildd.changes ACCEPT Processing changes file: xorg-server_1.20.11-1+deb11u6_amd64-buildd.changes ACCEPT Processing changes file: xorg-server_1.20.11-1+deb11u6_arm64-buildd.changes ACCEPT Processing changes file: xorg-server_1.20.11-1+deb11u6_armel-buildd.changes ACCEPT Processing changes file: xorg-server_1.20.11-1+deb11u6_armhf-buildd.changes ACCEPT Processing changes file: xorg-server_1.20.11-1+deb11u6_i386-buildd.changes ACCEPT Processing changes file: xorg-server_1.20.11-1+deb11u6_mips64el-buildd.changes ACCEPT Processing changes file: xorg-server_1.20.11-1+deb11u6_mipsel-buildd.changes ACCEPT Processing changes file: xorg-server_1.20.11-1+deb11u6_ppc64el-buildd.changes ACCEPT Processing changes file: xorg-server_1.20.11-1+deb11u6_s390x-buildd.changes ACCEPT
Bug#1033763: marked as done (unblock: fpc/3.2.2+dfsg-20)
Your message dated Sat, 01 Apr 2023 18:45:27 + with message-id and subject line unblock fpc has caused the Debian Bug report #1033763, regarding unblock: fpc/3.2.2+dfsg-20 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1033763: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033763 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package fpc Fixed compiler crash by applying a patch from upstream. [ Reason ] When compiling some packages on mipsel, FPC craches with internal error 2003042401. This issue was solved by upstream. [ Impact ] The fix is in a file specific to the mipsel code generator, so can not impact any other architecutre. It adds code generation for a special combination of opcode and operands. The same code exists already for similar architectures like SPARC. [ Tests ] The code file producing the internal error is now compiled correctly. There is a test produced by upstream to test this fix, but we decided not to include it in order not to increase the size of the patch. [ Risks ] No risks are foreseen. [ 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 testing [ Other info ] This patch was produced by FPC upstream mipsel maintainer and was included for long time in their daily snapshots. --- End Message --- --- Begin Message --- Unblocked.--- End Message ---
Bug#1033790: marked as done (unblock: lnav/0.11.1-3)
Your message dated Sat, 01 Apr 2023 18:43:39 +
with message-id
and subject line unblock lnav
has caused the Debian Bug report #1033790,
regarding unblock: lnav/0.11.1-3
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1033790: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033790
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: l...@packages.debian.org, car...@debian.org
Control: affects -1 + src:lnav
Hi Release team,
Please unblock package lnav
[ Reason ]
This update hotfixes an issue in the testsuite of lnav, which starts
to fail with curl 7.88.1 as now present in bookworm, but did not
7.78.0. Specifically found to be working with 7.87.0-2 but not anymore
once 7.88.1-1 was accepted. The bug is at #1032539. Saying it is a
hotfix, because it only changes the expeced error from curl to be
CURLUE_BAD_IPV6 instead of the initially CURLUE_BAD_PORT_NUMBER. I
think we cannot expect curl here to be at fault, because upstream
commit applied in 7.88.1
https://github.com/curl/curl/commit/8b27799f8c5e51187533edb04c66dd9079e1c478
addresses that the port number function does not need to fully verify
the IPv6 address.
[ Impact ]
If not accepted lnav will be autoremoved from bookworm later on.
[ Tests ]
The previously newly failing test passes now. Manually checking with
SELECT parse_url('https://bad@[fe::') on the query part gives as
expected now as well:
✘ error: invalid URL: “https://bad@[fe::”
│
reason: Bad IPv6 address
[ Risks ]
Low, the patch does really only fixes the error expected on the new
curl version which will be present in bookworm. While it was not nice
to have this that late in release cycle for lnav, it does not uncover
a problem in lnav itself, but in the testsuite.
[ 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 testing
[ Other info ]
Nothing to be added. There might follow a better fix from upstream
which we might have or not have then for bookworm.
unblock lnav/0.11.1-3
Regards,
Salvatore
diff -Nru lnav-0.11.1/debian/changelog lnav-0.11.1/debian/changelog
--- lnav-0.11.1/debian/changelog2023-01-22 20:41:56.0 +0100
+++ lnav-0.11.1/debian/changelog2023-03-31 20:40:20.0 +0200
@@ -1,3 +1,16 @@
+lnav (0.11.1-3) unstable; urgency=medium
+
+ * Upload to unstable
+
+ -- Salvatore Bonaccorso Fri, 31 Mar 2023 20:40:20 +0200
+
+lnav (0.11.1-3~exp1) experimental; urgency=medium
+
+ * test_sql_str_func.sh: Correct expected output on bad IPv6 address
+(Closes: #1032539)
+
+ -- Salvatore Bonaccorso Fri, 31 Mar 2023 17:52:44 +0200
+
lnav (0.11.1-2) unstable; urgency=medium
* Add Build-Depends on tzdata.
diff -Nru lnav-0.11.1/debian/patches/series lnav-0.11.1/debian/patches/series
--- lnav-0.11.1/debian/patches/series 2023-01-22 20:41:56.0 +0100
+++ lnav-0.11.1/debian/patches/series 2023-03-31 20:40:20.0 +0200
@@ -4,3 +4,4 @@
disable-broken-test_logfile-test.patch
disable-test_sql.patch
disable-broken-test_listview.patch
+test_sql_str_func.sh-Correct-expected-output-on-bad-.patch
diff -Nru
lnav-0.11.1/debian/patches/test_sql_str_func.sh-Correct-expected-output-on-bad-.patch
lnav-0.11.1/debian/patches/test_sql_str_func.sh-Correct-expected-output-on-bad-.patch
---
lnav-0.11.1/debian/patches/test_sql_str_func.sh-Correct-expected-output-on-bad-.patch
1970-01-01 01:00:00.0 +0100
+++
lnav-0.11.1/debian/patches/test_sql_str_func.sh-Correct-expected-output-on-bad-.patch
2023-03-31 20:40:20.0 +0200
@@ -0,0 +1,33 @@
+From 8b511514851901cb29ebf3fb96b626bffe37292d Mon Sep 17 00:00:00 2001
+From: Salvatore Bonaccorso
+Date: Fri, 31 Mar 2023 15:51:13 +0200
+Subject: [PATCH] test_sql_str_func.sh: Correct expected output on bad IPv6
+ address
+
+The test checks https://bad@[fe:: which since curl 7.88.1 reports back
+"Bad IPv6 address" (CURLUE_BAD_IPV6). Previously it reported back "Port
+number was not a decimal number between 0 and 65535"
+(CURLUE_BAD_PORT_NUMBER).
+
+Curl upstream changed in
+https://github.com/curl/curl/commit/8b27799f8c5e51187533edb04c66dd9079e1c478
+the port number function extraction, as the port number function does
+not need to fully verify the IPv6 address.
+
+Fixes: #1128
+Link: https://bugs.debian.org/1032539
+Signed-off-by: Salvatore Bonaccorso
+---
+
Processed: debian-archive-keyring 2021.1.1+deb11u1 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 1033157 = bullseye pending Bug #1033157 [release.debian.org] bullseye-pu: package debian-archive-keyring/2021.1.1+deb11u1 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1033157: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033157 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: libdatetime-timezone-perl 2.47-1+2023c 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 1033669 = bullseye pending Bug #1033669 [release.debian.org] bullseye-pu: package libdatetime-timezone-perl/1:2.47-1+2023c Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1033669: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033669 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033669: libdatetime-timezone-perl 2.47-1+2023c flagged for acceptance
package release.debian.org tags 1033669 = bullseye pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bullseye. Thanks for your contribution! Upload details == Package: libdatetime-timezone-perl Version: 2.47-1+2023c Explanation: update included data
Processed: Re: unblock: keyman/16.0.139-4
Processing control commands: > tags -1 moreinfo Bug #1033571 [release.debian.org] unblock: keyman/16.0.139-4 Added tag(s) moreinfo. -- 1033571: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033571 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033571: unblock: keyman/16.0.139-4
Control: tags -1 moreinfo On 27-03-2023 18:15, Eberhard Beilharz wrote: While keyman has autopkgtests and so would qualify for automatic migration, the tests are skipped on s390x. Ack. Included are only small changes: one is a small fix in the postinst script, -set -e +# Don't call `set -e`. Even if some commands should fail, it's still +# worth running the rest of the commands. Can you elaborate? I could imagine you want to run the rest of the commands, but if there is any failure, shouldn't that be recorded and used as the exit code? With the current change, the admin isn't going to be aware of issues at all, which feels weird (why would you run the postinst then in the first place). See also policy 6.1 [1]. > Another reason why I'd like to get this version approved is that it brings the version in Debian on par with the upstream version which simplifies user help requests. Did I miss something but is the *only* change upstream the addition echo? Doesn't feel very appropriate at this stage... Paul [1] https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#introduction-to-package-maintainer-scripts OpenPGP_signature Description: OpenPGP digital signature
Bug#1033157: debian-archive-keyring 2021.1.1+deb11u1 flagged for acceptance
package release.debian.org tags 1033157 = bullseye pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bullseye. Thanks for your contribution! Upload details == Package: debian-archive-keyring Version: 2021.1.1+deb11u1 Explanation: add bookworm keys; move stretch keys to the removed keyring
Bug#1033798: unblock: lazarus/2.2.6+dfsg1-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package lazarus Lazarus is an IDE and a library for rapid application development using Free Pascal Compiler. [ Reason ] New upstream maintenance release. [ Impact ] Several bugs were reported by users to upstream are fixed in this new release. This is a maintenance release only, so no new feature was added, only fixed bugs. [ Tests ] Upstream added tests to the test suite for several fixed bugs. Lazarus have a big test suite that aims to catch most regressions. [ Risks ] Risk is moderated as this is a bug fixes only. It was release by upstream 9th of March and users seems to be happy. The new release was packaged to unstable, and current Debian SW using Lazarus to build seems rebuildign correctly with the new release. [ Checklist ] [ ] all changes are documented in the d/changelog [x] I reviewed all changes and I approve them [x] attach debdiff against the package in testing [ Other info ] Thaking into account the long Debian release cycle, it is probably good to include this maintenance release in order to avoid packaging a version we know already that it has several bugs. Also taking into accoutn the small number of users of Lazarus on Debian, I don't want to loose any of them because we carry an outdated version (most users complain is that Debian always carries outdated versions with bugs that are already fixed in newer upstream versions). unblock lazarus/2.2.6+dfsg1-1 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 3.0 (quilt) Source: lazarus Binary: lazarus-2.2, lazarus-src-2.2, lazarus-ide-2.2, lazarus-ide-gtk2-2.2, lazarus-ide-qt5-2.2, lcl-2.2, lcl-utils-2.2, lcl-units-2.2, lcl-nogui-2.2, lcl-gtk2-2.2, lcl-qt5-2.2, lazarus-doc-2.2, lazarus, lazarus-src, lazarus-ide, lazarus-ide-gtk2, lazarus-ide-qt5, lcl, lcl-utils, lcl-units, lcl-nogui, lcl-gtk2, lcl-qt5, lazarus-doc Architecture: any all Version: 2.2.4+dfsg1-3 Maintainer: Pascal Packaging Team Uploaders: Abou Al Montacir , Paul Gevers Homepage: https://www.lazarus-ide.org/ Standards-Version: 4.4.1 Vcs-Browser: https://salsa.debian.org/pascal-team/lazarus Vcs-Git: https://salsa.debian.org/pascal-team/lazarus.git Testsuite: autopkgtest Testsuite-Triggers: @builddeps@ Build-Depends: debhelper (>= 11~), fp-utils (>= 3.2.0~), fpc (>= 3.2.0~), fpc-source (>= 3.2.0~), libgtk2.0-dev, libqt5pas-dev (>= 2.6~beta-6~), po-debconf, rdfind, symlinks Package-List: lazarus deb devel optional arch=all lazarus-2.2 deb devel optional arch=all lazarus-doc deb doc optional arch=all lazarus-doc-2.2 deb doc optional arch=all lazarus-ide deb devel optional arch=all lazarus-ide-2.2 deb devel optional arch=any lazarus-ide-gtk2 deb devel optional arch=all lazarus-ide-gtk2-2.2 deb devel optional arch=any lazarus-ide-qt5 deb devel optional arch=all lazarus-ide-qt5-2.2 deb devel optional arch=any lazarus-src deb devel optional arch=all lazarus-src-2.2 deb devel optional arch=all lcl deb devel optional arch=all lcl-2.2 deb devel optional arch=any lcl-gtk2 deb devel optional arch=all lcl-gtk2-2.2 deb devel optional arch=any lcl-nogui deb devel optional arch=all lcl-nogui-2.2 deb devel optional arch=any lcl-qt5 deb devel optional arch=all lcl-qt5-2.2 deb devel optional arch=any lcl-units deb devel optional arch=all lcl-units-2.2 deb devel optional arch=any lcl-utils deb devel optional arch=all lcl-utils-2.2 deb devel optional arch=any Checksums-Sha1: 988d4db6652862c358a6222ab603d4a7e629deba 54668272 lazarus_2.2.4+dfsg1.orig.tar.xz 78e6400b5dad246e7d9bc5b44d448e3a79de3b70 68204 lazarus_2.2.4+dfsg1-3.debian.tar.xz Checksums-Sha256: e649e69657d5e3038da5efc0123d08bfd410f30d414e4cc787a92d0453ad2877 54668272 lazarus_2.2.4+dfsg1.orig.tar.xz 27767146278cf967a02be0df004df6aa68151179d60ea49f8c3a8095dbf9655d 68204 lazarus_2.2.4+dfsg1-3.debian.tar.xz Files: b1ac009c2b8ac2fd5cdf10db66ec7f39 54668272 lazarus_2.2.4+dfsg1.orig.tar.xz 979ef81a90b43fcda252b2d0d925bdb5 68204 lazarus_2.2.4+dfsg1-3.debian.tar.xz -BEGIN PGP SIGNATURE- iI0EAREKADUWIQS69sZENhB4UNQicQazJVxtVYeNjAUCZB7cDRccYWJvdS5hbG1v bnRhY2lyQHNmci5mcgAKCRCzJVxtVYeNjA35AP9ois9EsD3ShcZJr2LnwSmEhaV3 AhKCcHutK6WhVQgoKwEAhSlNmjXYYCcjw2upux9IcmlfCqvMgoOAWqNCU5hC9pg= =wp53 -END PGP SIGNATURE- -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 3.0 (quilt) Source: lazarus Binary: lazarus-2.2, lazarus-src-2.2, lazarus-ide-2.2, lazarus-ide-gtk2-2.2, lazarus-ide-qt5-2.2, lcl-2.2, lcl-utils-2.2, lcl-units-2.2, lcl-nogui-2.2, lcl-gtk2-2.2, lcl-qt5-2.2, lazarus-doc-2.2, lazarus, lazarus-src, lazarus-ide, lazarus-ide-gtk2, lazarus-ide-qt5, lcl, lcl-utils, lcl-units, lcl-nogui, lcl-gtk2, lcl-qt5, lazarus-doc Architecture: any all Version: 2.2.6+dfsg1-1 Maintainer: Pascal Packaging Team Uploaders: Abou Al Montacir , Paul Gevers Homepage: https://www.lazarus-ide.org/ Standards-Version: 4.4.1 Vcs-Browser:
Bug#1033789: marked as done (unblock: verilator/5.006-3)
Your message dated Sat, 01 Apr 2023 11:10:02 +
with message-id
and subject line unblock verilator
has caused the Debian Bug report #1033789,
regarding unblock: verilator/5.006-3
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1033789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033789
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: verila...@packages.debian.org
Control: affects -1 + src:verilator
Please unblock package verilator
[ Reason ]
Dimitry Shachnev reported a RC issue (#1033667) against the verilator
package which is fixed by version 5.006-3.
[ Impact ]
Without that fix users are unable to install the verilator package in
bookworm.
[ Tests ]
The verialtor package has currently no autopkgtest so only manual
testing was happen.
[ Risks ]
There are no typical risks, verilator has no reverse dependencies by
or in other packages.
[ 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 testing
As no modification did happen in the upstream related code parts I add
the debian/ related changes directly inline.
diff --git a/debian/changelog b/debian/changelog
index 4c4d83e7..48675e51 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,20 @@
+verilator (5.006-3) unstable; urgency=medium
+
+ * Team upload
+ [ Dmitry Shachnev ]
+ * [38e486b] Move ${sphinxdoc:Built-Using} to the correct field.
+(Closes: #1033667)
+
+ [ Carsten Schoenert ]
+ * [975c120] d/gbp.conf: Adjust to debian/bookworm
+ * [e05438c] Rebuild patch queue from patch-queue branch
+Added patches:
+Fix-build-on-hppa.patch
+Fix-date-on-the-front-page-of-verilator.pdf-3956-3957.patch
+(Closes: #1030913, #1031711)
+
+ -- Carsten Schoenert Thu, 30 Mar 2023 20:05:11
+0200
+
verilator (5.006-2) unstable; urgency=medium
* Team upload
diff --git a/debian/control b/debian/control
index d02cf292..add11de7 100644
--- a/debian/control
+++ b/debian/control
@@ -31,8 +31,9 @@ Depends:
${misc:Depends},
${perl:Depends},
${shlibs:Depends},
- ${sphinxdoc:Built-Using},
${sphinxdoc:Depends},
+Built-Using:
+ ${sphinxdoc:Built-Using},
Recommends:
libsystemc-dev,
Suggests:
diff --git a/debian/gbp.conf b/debian/gbp.conf
index f892216e..f59e67e2 100644
--- a/debian/gbp.conf
+++ b/debian/gbp.conf
@@ -3,7 +3,7 @@
pristine-tar = True
# generate gz compressed orig.tar file
compression = gz
-debian-branch = debian/sid
+debian-branch = debian/bookworm
upstream-branch = upstream
[pq]
diff --git a/debian/patches/Fix-build-on-hppa.patch
b/debian/patches/Fix-build-on-hppa.patch
new file mode 100644
index ..d0a82040
--- /dev/null
+++ b/debian/patches/Fix-build-on-hppa.patch
@@ -0,0 +1,24 @@
+From: Larry Doolittle
+Date: Fri, 10 Feb 2023 21:31:44 -0800
+Subject: Fix build on hppa
+
+As supplied by John David Anglin in Debian bug #1030913
+
+Forwarded: https://github.com/verilator/verilator/pull/3954
+---
+ include/verilatedos.h | 2 ++
+ 1 file changed, 2 insertions(+)
+
+diff --git a/include/verilatedos.h b/include/verilatedos.h
+index 0e30164..7efd61e 100644
+--- a/include/verilatedos.h
b/include/verilatedos.h
+@@ -519,6 +519,8 @@ using ssize_t = uint32_t; ///< signed size_t; returned
from read()
+ # define VL_CPU_RELAX() asm volatile("nop" ::: "memory");
+ #elif defined(__aarch64__) || defined(__arm__)
+ # define VL_CPU_RELAX() asm volatile("yield" ::: "memory")
++#elif defined(__hppa__) // HPPA does not currently have yield/pause
++# define VL_CPU_RELAX() asm volatile("nop" ::: "memory")
+ #elif defined(__loongarch__) // LoongArch does not currently have yield/pause
+ # define VL_CPU_RELAX() asm volatile("nop" ::: "memory")
+ #elif defined(__mips64el__) || defined(__mips__) || defined(__mips64__) ||
defined(__mips64)
diff --git
a/debian/patches/Fix-date-on-the-front-page-of-verilator.pdf-3956-3957.patch
b/debian/patches/Fix-date-on-the-front-page-of-verilator.pdf-3956-3957.patch
new file mode 100644
index ..d4d559a2
--- /dev/null
+++ b/debian/patches/Fix-date-on-the-front-page-of-verilator.pdf-3956-3957.patch
@@ -0,0 +1,69 @@
+From: Larry Doolittle
+Date: Sun, 12 Feb 2023 20:21:03 -0800
+Subject: Fix date on the front page of verilator.pdf (#3956) (#3957)
+
+Forwarded: https://github.com/verilator/verilator/issues/3956
+---
+ docs/guide/conf.py | 27 ---
+ 1 file changed, 12 insertions(+), 15 deletions(-)
Bug#1033790: unblock: lnav/0.11.1-3
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: l...@packages.debian.org, car...@debian.org
Control: affects -1 + src:lnav
Hi Release team,
Please unblock package lnav
[ Reason ]
This update hotfixes an issue in the testsuite of lnav, which starts
to fail with curl 7.88.1 as now present in bookworm, but did not
7.78.0. Specifically found to be working with 7.87.0-2 but not anymore
once 7.88.1-1 was accepted. The bug is at #1032539. Saying it is a
hotfix, because it only changes the expeced error from curl to be
CURLUE_BAD_IPV6 instead of the initially CURLUE_BAD_PORT_NUMBER. I
think we cannot expect curl here to be at fault, because upstream
commit applied in 7.88.1
https://github.com/curl/curl/commit/8b27799f8c5e51187533edb04c66dd9079e1c478
addresses that the port number function does not need to fully verify
the IPv6 address.
[ Impact ]
If not accepted lnav will be autoremoved from bookworm later on.
[ Tests ]
The previously newly failing test passes now. Manually checking with
SELECT parse_url('https://bad@[fe::') on the query part gives as
expected now as well:
✘ error: invalid URL: “https://bad@[fe::”
│
reason: Bad IPv6 address
[ Risks ]
Low, the patch does really only fixes the error expected on the new
curl version which will be present in bookworm. While it was not nice
to have this that late in release cycle for lnav, it does not uncover
a problem in lnav itself, but in the testsuite.
[ 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 testing
[ Other info ]
Nothing to be added. There might follow a better fix from upstream
which we might have or not have then for bookworm.
unblock lnav/0.11.1-3
Regards,
Salvatore
diff -Nru lnav-0.11.1/debian/changelog lnav-0.11.1/debian/changelog
--- lnav-0.11.1/debian/changelog2023-01-22 20:41:56.0 +0100
+++ lnav-0.11.1/debian/changelog2023-03-31 20:40:20.0 +0200
@@ -1,3 +1,16 @@
+lnav (0.11.1-3) unstable; urgency=medium
+
+ * Upload to unstable
+
+ -- Salvatore Bonaccorso Fri, 31 Mar 2023 20:40:20 +0200
+
+lnav (0.11.1-3~exp1) experimental; urgency=medium
+
+ * test_sql_str_func.sh: Correct expected output on bad IPv6 address
+(Closes: #1032539)
+
+ -- Salvatore Bonaccorso Fri, 31 Mar 2023 17:52:44 +0200
+
lnav (0.11.1-2) unstable; urgency=medium
* Add Build-Depends on tzdata.
diff -Nru lnav-0.11.1/debian/patches/series lnav-0.11.1/debian/patches/series
--- lnav-0.11.1/debian/patches/series 2023-01-22 20:41:56.0 +0100
+++ lnav-0.11.1/debian/patches/series 2023-03-31 20:40:20.0 +0200
@@ -4,3 +4,4 @@
disable-broken-test_logfile-test.patch
disable-test_sql.patch
disable-broken-test_listview.patch
+test_sql_str_func.sh-Correct-expected-output-on-bad-.patch
diff -Nru
lnav-0.11.1/debian/patches/test_sql_str_func.sh-Correct-expected-output-on-bad-.patch
lnav-0.11.1/debian/patches/test_sql_str_func.sh-Correct-expected-output-on-bad-.patch
---
lnav-0.11.1/debian/patches/test_sql_str_func.sh-Correct-expected-output-on-bad-.patch
1970-01-01 01:00:00.0 +0100
+++
lnav-0.11.1/debian/patches/test_sql_str_func.sh-Correct-expected-output-on-bad-.patch
2023-03-31 20:40:20.0 +0200
@@ -0,0 +1,33 @@
+From 8b511514851901cb29ebf3fb96b626bffe37292d Mon Sep 17 00:00:00 2001
+From: Salvatore Bonaccorso
+Date: Fri, 31 Mar 2023 15:51:13 +0200
+Subject: [PATCH] test_sql_str_func.sh: Correct expected output on bad IPv6
+ address
+
+The test checks https://bad@[fe:: which since curl 7.88.1 reports back
+"Bad IPv6 address" (CURLUE_BAD_IPV6). Previously it reported back "Port
+number was not a decimal number between 0 and 65535"
+(CURLUE_BAD_PORT_NUMBER).
+
+Curl upstream changed in
+https://github.com/curl/curl/commit/8b27799f8c5e51187533edb04c66dd9079e1c478
+the port number function extraction, as the port number function does
+not need to fully verify the IPv6 address.
+
+Fixes: #1128
+Link: https://bugs.debian.org/1032539
+Signed-off-by: Salvatore Bonaccorso
+---
+ ...sql_str_func.sh_3855d2cc0ab29171cae8e722f130adec25eae36e.err | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git
a/test/expected/test_sql_str_func.sh_3855d2cc0ab29171cae8e722f130adec25eae36e.err
b/test/expected/test_sql_str_func.sh_3855d2cc0ab29171cae8e722f130adec25eae36e.err
+index e3d40abf40a2..a7c2bb2abd74 100644
+---
a/test/expected/test_sql_str_func.sh_3855d2cc0ab29171cae8e722f130adec25eae36e.err
b/test/expected/test_sql_str_func.sh_3855d2cc0ab29171cae8e722f130adec25eae36e.err
+@@ -1 +1 @@
+-error: sqlite3_exec failed --
lnav-error:{"level":"error","message":{"str":"invalid URL:
“https://bad@[fe::”","attrs":[]},"reason":{"str":"Port number was not a decimal
number between 0 and
Processed: unblock: lnav/0.11.1-3
Processing control commands: > affects -1 + src:lnav Bug #1033790 [release.debian.org] unblock: lnav/0.11.1-3 Added indication that 1033790 affects src:lnav -- 1033790: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033790 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033789: unblock: verilator/5.006-3
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: verila...@packages.debian.org
Control: affects -1 + src:verilator
Please unblock package verilator
[ Reason ]
Dimitry Shachnev reported a RC issue (#1033667) against the verilator
package which is fixed by version 5.006-3.
[ Impact ]
Without that fix users are unable to install the verilator package in
bookworm.
[ Tests ]
The verialtor package has currently no autopkgtest so only manual
testing was happen.
[ Risks ]
There are no typical risks, verilator has no reverse dependencies by
or in other packages.
[ 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 testing
As no modification did happen in the upstream related code parts I add
the debian/ related changes directly inline.
diff --git a/debian/changelog b/debian/changelog
index 4c4d83e7..48675e51 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,20 @@
+verilator (5.006-3) unstable; urgency=medium
+
+ * Team upload
+ [ Dmitry Shachnev ]
+ * [38e486b] Move ${sphinxdoc:Built-Using} to the correct field.
+(Closes: #1033667)
+
+ [ Carsten Schoenert ]
+ * [975c120] d/gbp.conf: Adjust to debian/bookworm
+ * [e05438c] Rebuild patch queue from patch-queue branch
+Added patches:
+Fix-build-on-hppa.patch
+Fix-date-on-the-front-page-of-verilator.pdf-3956-3957.patch
+(Closes: #1030913, #1031711)
+
+ -- Carsten Schoenert Thu, 30 Mar 2023 20:05:11
+0200
+
verilator (5.006-2) unstable; urgency=medium
* Team upload
diff --git a/debian/control b/debian/control
index d02cf292..add11de7 100644
--- a/debian/control
+++ b/debian/control
@@ -31,8 +31,9 @@ Depends:
${misc:Depends},
${perl:Depends},
${shlibs:Depends},
- ${sphinxdoc:Built-Using},
${sphinxdoc:Depends},
+Built-Using:
+ ${sphinxdoc:Built-Using},
Recommends:
libsystemc-dev,
Suggests:
diff --git a/debian/gbp.conf b/debian/gbp.conf
index f892216e..f59e67e2 100644
--- a/debian/gbp.conf
+++ b/debian/gbp.conf
@@ -3,7 +3,7 @@
pristine-tar = True
# generate gz compressed orig.tar file
compression = gz
-debian-branch = debian/sid
+debian-branch = debian/bookworm
upstream-branch = upstream
[pq]
diff --git a/debian/patches/Fix-build-on-hppa.patch
b/debian/patches/Fix-build-on-hppa.patch
new file mode 100644
index ..d0a82040
--- /dev/null
+++ b/debian/patches/Fix-build-on-hppa.patch
@@ -0,0 +1,24 @@
+From: Larry Doolittle
+Date: Fri, 10 Feb 2023 21:31:44 -0800
+Subject: Fix build on hppa
+
+As supplied by John David Anglin in Debian bug #1030913
+
+Forwarded: https://github.com/verilator/verilator/pull/3954
+---
+ include/verilatedos.h | 2 ++
+ 1 file changed, 2 insertions(+)
+
+diff --git a/include/verilatedos.h b/include/verilatedos.h
+index 0e30164..7efd61e 100644
+--- a/include/verilatedos.h
b/include/verilatedos.h
+@@ -519,6 +519,8 @@ using ssize_t = uint32_t; ///< signed size_t; returned
from read()
+ # define VL_CPU_RELAX() asm volatile("nop" ::: "memory");
+ #elif defined(__aarch64__) || defined(__arm__)
+ # define VL_CPU_RELAX() asm volatile("yield" ::: "memory")
++#elif defined(__hppa__) // HPPA does not currently have yield/pause
++# define VL_CPU_RELAX() asm volatile("nop" ::: "memory")
+ #elif defined(__loongarch__) // LoongArch does not currently have yield/pause
+ # define VL_CPU_RELAX() asm volatile("nop" ::: "memory")
+ #elif defined(__mips64el__) || defined(__mips__) || defined(__mips64__) ||
defined(__mips64)
diff --git
a/debian/patches/Fix-date-on-the-front-page-of-verilator.pdf-3956-3957.patch
b/debian/patches/Fix-date-on-the-front-page-of-verilator.pdf-3956-3957.patch
new file mode 100644
index ..d4d559a2
--- /dev/null
+++ b/debian/patches/Fix-date-on-the-front-page-of-verilator.pdf-3956-3957.patch
@@ -0,0 +1,69 @@
+From: Larry Doolittle
+Date: Sun, 12 Feb 2023 20:21:03 -0800
+Subject: Fix date on the front page of verilator.pdf (#3956) (#3957)
+
+Forwarded: https://github.com/verilator/verilator/issues/3956
+---
+ docs/guide/conf.py | 27 ---
+ 1 file changed, 12 insertions(+), 15 deletions(-)
+
+diff --git a/docs/guide/conf.py b/docs/guide/conf.py
+index 04759c6..9f69245 100644
+--- a/docs/guide/conf.py
b/docs/guide/conf.py
+@@ -10,7 +10,6 @@
+ # --
+ # -- Path setup
+
+-from datetime import datetime
+ import os
+ import re
+ import sys
+@@ -24,10 +23,17 @@ def get_vlt_version():
+ filename = "../../Makefile"
+ with open(filename, "r", encoding="utf8") as fh:
+ for line in fh:
+-match = re.search(r"PACKAGE_VERSION_NUMBER *= *([a-z0-9.]+)",
line)
++match = re.search(r"PACKAGE_VERSION *= *([a-z0-9.]+) +([-0-9]+)",
line)
+ if match:
+-return match.group(1)
+-return "unknown"
++return
Processed: unblock: verilator/5.006-3
Processing control commands: > affects -1 + src:verilator Bug #1033789 [release.debian.org] unblock: verilator/5.006-3 Added indication that 1033789 affects src:verilator -- 1033789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033789 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033739: unblock: libmath-bigint-perl/1.999838-1
Since this upload triggers a regression in the testsuite of libmath-bigint-gmp-perl (see #1033784), I just uploaded libmath-bigint-gmp-perl 1.6011-3, which fixes the testsuite. signature.asc Description: PGP signature
Bug#1033787: unblock: python-selenium/4.8.3+dfsg-1
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: python-selen...@packages.debian.org
Control: affects -1 + src:python-selenium
Please unblock package python-selenium
[ Reason ]
There was another micro update of python-selenium which includes these
modifications (according to the documented upstream changes). Not all of
these modification are located within the Python specific flavor of
Selenium. There were added a lot more of type safe checking basically
in this update and the -doc package got Sphinx related updates.
Selenium 4.8.3
* Add fine grained control for arguments provided to service
subprocesses by passing a `popen_kw` mapping for all services.
* `Options` classes now allow `timeout` to be set partially and no
longer raise an exception when all values are not provided. (#11623)
* No longer sending `SIGKILL` to subprocesses in instances where
`SIGTERM` was successful within 60 seconds.
* Add CDP files for v111 and remove v108
* Pass default to `pop` when parsing service popen_kw
* Using json output with Selenium Manager
* Sphinx config update to keep invoked methods and shorter aliases in
documentation (#11802)
[ Impact ]
User couldn't use the latest and greatest version of python-selenium in
Debian bookworm.
[ Tests ]
All upstream tests were successfull, a small checking of some local used
Selenium based snippets did also work as expected. Also the DebCI did
not shown any regressions.
[ Risks ]
There are no real risk to me, looking at the upstream changes I don't
see any potential pitfalls.
python-selenium is a key package and needs an manual unblock by the RT.
[ 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 testing
[ Other info ]
There is also a differential view visable in the source repository on
GitHub.
https://github.com/SeleniumHQ/selenium/compare/selenium-4.8.2-python...selenium-4.8.3-python
But this is much bigger as the attached debdiff file as it also contains
parts of upstream code which we do filter out to fullfill the DFSG
requirements.
The Debian related modifications are only this rather small part.
$ git diff debian/4.8.2+dfsg-1 debian/
diff --git a/debian/changelog b/debian/changelog
index e10915a..ef494f9 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+python-selenium (4.8.3+dfsg-1) unstable; urgency=medium
+
+ * [9118276] New upstream version 4.8.3+dfsg
+ * [5bb3ae9] debian/: Move d/docs to d/python-selenium-doc.links
+
+ -- Carsten Schoenert Wed, 29 Mar 2023 12:14:56
+0200
+
python-selenium (4.8.2+dfsg-1) unstable; urgency=medium
* [8e56110] New upstream version 4.8.2+dfsg
diff --git a/debian/docs b/debian/docs
deleted file mode 100644
index a1320b1..000
--- a/debian/docs
+++ /dev/null
@@ -1 +0,0 @@
-README.rst
diff --git a/debian/python-selenium-doc.links b/debian/python-selenium-doc.links
new file mode 100644
index 000..567b3ed
--- /dev/null
+++ b/debian/python-selenium-doc.links
@@ -0,0 +1,4 @@
+# We can't just copy/install the original symlink from the source, it would
+# point to a non existing file after the packaging. So do the correct linking
+# here.
+usr/share/doc/python-selenium-doc/html/_sources/index.rst.txt
usr/share/doc/python-selenium-doc/README.rst
unblock python-selenium/4.8.3+dfsg-1
diff -Nru python-selenium-4.8.2+dfsg/CHANGES python-selenium-4.8.3+dfsg/CHANGES
--- python-selenium-4.8.2+dfsg/CHANGES 2023-02-18 00:17:10.0 +0100
+++ python-selenium-4.8.3+dfsg/CHANGES 2023-03-24 19:05:50.0 +0100
@@ -1,3 +1,12 @@
+Selenium 4.8.3
+* Add fine grained control for arguments provided to service subprocesses by
passing a `popen_kw` mapping for all services.
+* `Options` classes now allow `timeout` to be set partially and no longer
raise an exception when all values are not provided. (#11623)
+* No longer sending `SIGKILL` to subprocesses in instances where `SIGTERM` was
successful within 60 seconds.
+* Add CDP files for v111 and remove v108
+* Pass default to `pop` when parsing service popen_kw
+* Using json output with Selenium Manager
+* Sphinx config update to keep invoked methods and shorter aliases in
documentation (#11802)
+
Selenium 4.8.2
* Update tox.ini for a valid "isort" version (#11667)
* Undo a bug fix that caused a worse bug. (#11666)
diff -Nru python-selenium-4.8.2+dfsg/conftest.py
python-selenium-4.8.3+dfsg/conftest.py
--- python-selenium-4.8.2+dfsg/conftest.py 2023-02-18 00:17:10.0
+0100
+++ python-selenium-4.8.3+dfsg/conftest.py 2023-03-24 19:05:50.0
+0100
@@ -237,7 +237,9 @@
)
except Exception:
print("Starting the Selenium server")
-process = subprocess.Popen(["java", "-jar", _path, "standalone",
"--port", ""])
+process = subprocess.Popen(
+["java", "-jar", _path, "standalone", "--port", "",
Processed: unblock: python-selenium/4.8.3+dfsg-1
Processing control commands: > affects -1 + src:python-selenium Bug #1033787 [release.debian.org] unblock: python-selenium/4.8.3+dfsg-1 Added indication that 1033787 affects src:python-selenium -- 1033787: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033787 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
