Processed: unblock: swe-data/4.0-20221111-2

[Debian Bug Tracking System]

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

> retitle 1033240 unblock: swe-data/4.0-2022-2
Bug #1033240 [release.debian.org] Unblock: swe-data
Changed Bug title to 'unblock: swe-data/4.0-2022-2' from 'Unblock: 
swe-data'.
> affects 1033240 src:swe-data
Bug #1033240 [release.debian.org] unblock: swe-data/4.0-2022-2
Added indication that 1033240 affects src:swe-data
> user release.debian@packages.debian.org
Setting user to release.debian@packages.debian.org (was gin...@debian.org).
> usertag 1033240 + unblock
There were no usertags set.
Usertags are now: unblock.
> thanks
Stopping processing here.

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

Bug#1033067: marked as done (unblock: glide/2002.04.10ds1-21)

[Debian Bug Tracking System]

Your message dated Mon, 10 Apr 2023 10:28:18 +0200
with message-id 

and subject line unblock: glide/2002.04.10ds1-21
has caused the Debian Bug report #1033067,
regarding unblock: glide/2002.04.10ds1-21
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.)


-- 
1033067: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033067
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: gl...@packages.debian.org
Control: affects -1 + src:glide

Please unblock package glide

[ Reason ]

This non-key package does not currently contain autopkgtests.

These two releases include a couple of changes to make the package
finally reproducible, as the generated shared libraries would change
the optimized objects being linked to depending on the build system
(for host=i386 build=amd64).

[ Impact ]

Same generated objects regardless of the build system being used.

[ Tests ]

The tests were performed locally in an amd64 host and an i386 chroot,
before and after the fixes, and the reproducible builds are now green
for i386 for this package.

[ Risks ]

The risks seem minimal, as this is just making sure the build always
behaves in the same way.

[ Checklist ]

  [√] all changes are documented in the d/changelog
(There is the grammar fix in the changelog itself, which I do not
 tend to mention explicitly as it seems unnecessary verbiage.)
  [√] I reviewed all changes and I approve them
  [√] attach debdiff against the package in testing

[ Other info ]

(nothing)


unblock glide/2002.04.10ds1-21

Thanks,
Guillem
diff -Nru glide-2002.04.10ds1/debian/changelog 
glide-2002.04.10ds1/debian/changelog
--- glide-2002.04.10ds1/debian/changelog2023-02-26 23:15:35.0 
+0100
+++ glide-2002.04.10ds1/debian/changelog2023-03-10 02:37:51.0 
+0100
@@ -1,6 +1,20 @@
+glide (2002.04.10ds1-21) unstable; urgency=medium
+
+  * Pass --build and --host to configure via chores.3dfx.
+
+ -- Guillem Jover   Fri, 10 Mar 2023 02:37:51 +0100
+
+glide (2002.04.10ds1-20) unstable; urgency=medium
+
+  * Use autoconf $host_cpu instead of «uname -m» to decide how to optimize
+and what to compile into the resulting objects, which was making the
+build unreproducible on i386 when built on an amd64 build system.
+
+ -- Guillem Jover   Sat, 04 Mar 2023 13:24:56 +0100
+
 glide (2002.04.10ds1-19) unstable; urgency=medium
 
-  * Enable LFS build options. This should ABI safe as the shared library
+  * Enable LFS build options. This should be ABI safe as the shared library
 does not expose any problematic type.
   * Actually show the debconf error when the target is not a symlink.
 
diff -Nru glide-2002.04.10ds1/debian/patches/no-uname.patch 
glide-2002.04.10ds1/debian/patches/no-uname.patch
--- glide-2002.04.10ds1/debian/patches/no-uname.patch   1970-01-01 
01:00:00.0 +0100
+++ glide-2002.04.10ds1/debian/patches/no-uname.patch   2023-03-04 
13:38:57.0 +0100
@@ -0,0 +1,30 @@
+Description: Use autoconf $host_cpu instead of «uname -m»
+ This was making the build unreproducible as the uname will return the build
+ system CPU and not the host one.
+Author: Guillem Jover 
+Origin: vendor
+Forwarded: no
+
+---
+ glide3x/configure.in |3 ++-
+ 1 file changed, 2 insertions(+), 1 deletion(-)
+
+--- a/glide3x/configure.in
 b/glide3x/configure.in
+@@ -142,6 +142,7 @@ AM_CONDITIONAL(FX_GLIDE_CVG, test x$FX_G
+ #
+ # Architecture
+ #
++AC_CANONICAL_HOST
+ AC_ARG_ENABLE([build-architecture],
+   [dnl
+   --enable-build-architecture Enable AMD 3DNow instructions 
[default=current]],
+@@ -152,7 +153,7 @@ AC_ARG_ENABLE([build-architecture],
+*)
+AC_MSG_ERROR([Illegal value (${enableval}) for 
--enable-build-architecture])
+;;
+-   esac],[FX_GLIDE_BUILD_ARCHITECTURE=`uname -m`])
++   esac],[FX_GLIDE_BUILD_ARCHITECTURE=$host_cpu])
+ AC_SUBST(FX_GLIDE_BUILD_ARCHITECTURE)
+ #
+ # Various tests needed at points in the build
diff -Nru glide-2002.04.10ds1/debian/patches/series 
glide-2002.04.10ds1/debian/patches/series
--- glide-2002.04.10ds1/debian/patches/series   2022-07-17 18:28:36.0 
+0200
+++ glide-2002.04.10ds1/debian/patches/series   2023-03-04 13:16:21.0 
+0100
@@ -36,3 +36,4 @@
 z12-local-libtool
 z13-install-perms
 no-x11.patch
+no-uname.patch
diff -Nru glide-2002.04.10ds1/debian/rules glide-2002.04.10ds1/debian/rules
--- glide-2002.04.10ds1/debian/rules2023-02-25 15:42:22.0

Bug#1033240: marked as done (unblock: swe-data/4.0-20221111-2)

[Debian Bug Tracking System]

Your message dated Mon, 10 Apr 2023 10:26:34 +0200
with message-id 

and subject line unblock: swe-data/4.0-2022-2
has caused the Debian Bug report #1033240,
regarding unblock: swe-data/4.0-2022-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.)


-- 
1033240: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033240
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: jald...@debian.org, s...@astrorigin.com

Hello,

I am requesting a review and unblock for a non-key package, 'swe-data'  [1].

The new version fixes the following bug: #1031657  [2].
Missing information in the d/control file did not allow a smooth transition
from bullseye to bookworm.

The fix was tested with first, installation of the packages from bullseye,
then installation of packages from sid. Everything went fine.

You can find the related source debdiff in attachment.

Thanks for attention.


[1] https://tracker.debian.org/pkg/swe-data
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031657
diff -Nru swe-data-4.0-2022/debian/changelog 
swe-data-4.0-2022/debian/changelog
--- swe-data-4.0-2022/debian/changelog  2023-02-08 12:46:57.0 
+0100
+++ swe-data-4.0-2022/debian/changelog  2023-02-27 10:21:27.0 
+0100
@@ -1,9 +1,9 @@
-swe-data (4.0-2022-1.1) unstable; urgency=medium
+swe-data (4.0-2022-2) unstable; urgency=medium

-  * Non-maintainer upload.
-  * Source-only upload.
+  * Add Replaces+Breaks info to swe-standard-data (closes: #1031657).
+  * Add multiarch hints to swe-basic-data, swe-sat-data.

- -- Adrian Bunk   Wed, 08 Feb 2023 13:46:57 +0200
+ -- Stanislas Marquis   Mon, 27 Feb 2023 10:21:27 +0100

 swe-data (4.0-2022-1) unstable; urgency=medium

diff -Nru swe-data-4.0-2022/debian/control 
swe-data-4.0-2022/debian/control
--- swe-data-4.0-2022/debian/control2022-11-11 01:41:55.0 
+0100
+++ swe-data-4.0-2022/debian/control2023-02-27 08:15:11.000
00 +0100
@@ -12,12 +12,17 @@
 Package: swe-basic-data
 Section: libs
 Architecture: all
+Multi-Arch: foreign
 Depends:
  ${misc:Depends},
 Suggests:
  libswe-doc (>= 2.10.03),
  swe-standard-data (= ${binary:Version}),
  swe-extra-data (= ${binary:Version}),
+Replaces:
+ swe-standard-data (<< 4.0-2022),
+Breaks:
+ swe-standard-data (<< 4.0-2022),
 Description: Swiss Ephemeris library (basic set of ephemeris files).
  This set of ephemeris files covers the recent past, contemporary period and
  near future (1800 to 2399 CE). Also included are the static data files for
@@ -56,6 +61,7 @@
 Package: swe-sat-data
 Section: libs
 Architecture: all
+Multi-Arch: foreign
 Depends:
  ${misc:Depends},
 Suggests:


signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Already unblocked by Sebastian.--- End Message ---

Bug#1034100: marked as done (unblock: texlive-base/2022.20230122-3)

[Debian Bug Tracking System]

Your message dated Mon, 10 Apr 2023 10:46:59 +0200
with message-id 

and subject line unblock: texlive-base/2022.20230122-3
has caused the Debian Bug report #1034100,
regarding unblock: texlive-base/2022.20230122-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.)


-- 
1034100: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034100
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: texlive-b...@packages.debian.org
Control: affects -1 + src:texlive-base

Please unblock package src:texlive-base. I did not upload the
package to unstable, I'd like to hear your decision beforehand.
The package contains two changes:
- fix hyphenation for language German.
- Contains Romanian debconf translation of texlive-base.

[ Reason ]
Mainly we'd like to have the hyphenations for language german,
when using luatex, fixed.

[ Impact ]
People writing in German /could/ experience no/wrong hyphenation when
using luatex.

[ Tests ]
There were no automated tests. We only apply the patch for the issue
described here [1]. The submitter confirmed that the patch solved
the specific issue.

[ Risks ]
Code change is rather trivial and should not affect source packages.
The human end users already confirmed that the change is useful.
The code change is meanwhile part of the official TeX Babel package.

[ 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

unblock texlive-base/2022.20230122-3

[1] https://tex.stackexchange.com/questions/680690

-- 
sigmentation fault


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Unblocked, thanks.--- End Message ---

Bug#1034076: marked as done (unblock: spf-engine/3.0.4-1)

[Debian Bug Tracking System]

Your message dated Mon, 10 Apr 2023 10:46:05 +0200
with message-id 

and subject line unblock: spf-engine/3.0.4-1
has caused the Debian Bug report #1034076,
regarding unblock: spf-engine/3.0.4-1
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.)


-- 
1034076: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034076
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 spf-engine

(Please provide enough (but not too much) information to help
the release team to judge the request efficiently. E.g. by
filling in the sections below.)

[ Reason ]
Fixes a bug that will cause mail processing to stop for systems which
send mail to/from local users that doesn't have a fully qualified domain
name.  This a regression from Bullseye.

[ Impact ]
For most users, none, but for users sending to local addresses, mail
will stop flowing after upgrade from Bullseye to Bookworm.

[ Tests ]
The affected code was tested by the original bug reporter and they
verified that the fix worked without unwanted side effects.

[Risks ]
Risk is negligible.  Very small code change that's been tested.  There
is not autopkgtest as the upstream test suite (such as it is, I'm not
proud of it) isn't suitable.  This is a leaf package, so there's no risk
of negative effects on other packages.

[ Checklist ]
  [*] all changes are documented in the d/changelog
  [*] I reviewed all changes and I approve them
  [*] attach debdiff against the package in testing

[ Other info ]
I haven't uploaded this yet, but it's prepared in git locally for upload
if approved.  The only thing I have to do relative to what's in the
debdiff is dch -r to mark it released.

This is something I would ask for a post-release update to fix if I
didn't find out about until after Bookworm's release.

unblock spf-engine/3.0.4-1
diff -Nru spf-engine-3.0.3/CHANGES spf-engine-3.0.4/CHANGES
--- spf-engine-3.0.3/CHANGES2023-02-19 19:30:05.819651600 -0500
+++ spf-engine-3.0.4/CHANGES2023-04-07 20:46:47.963843000 -0400
@@ -4,6 +4,10 @@
 #   ! = Changed something significant, or removed a feature
 #   * = Fixed a bug, or made a minor improvement
 
+--- 3.0.4 (2023-04-07)
+  * Fix recipient logging to not cause an error for local (not fully
+qualified) email addresses (LP: #2015609)
+
 --- 3.0.3 (2023-02-19)
   * Fix reference to QueueID in policydspfsupp.py (LP: #2007123), thanks to
 Wolfgang Karall-Ahlborn for the bug and the fix
diff -Nru spf-engine-3.0.3/debian/changelog spf-engine-3.0.4/debian/changelog
--- spf-engine-3.0.3/debian/changelog   2023-02-19 20:13:27.0 -0500
+++ spf-engine-3.0.4/debian/changelog   2023-04-08 00:06:57.0 -0400
@@ -1,3 +1,9 @@
+spf-engine (3.0.4-1) UNRELEASED; urgency=medium
+
+  * New upstream release
+
+ -- Scott Kitterman   Sat, 08 Apr 2023 00:06:57 -0400
+
 spf-engine (3.0.3-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru spf-engine-3.0.3/PKG-INFO spf-engine-3.0.4/PKG-INFO
--- spf-engine-3.0.3/PKG-INFO   1969-12-31 19:00:00.0 -0500
+++ spf-engine-3.0.4/PKG-INFO   1969-12-31 19:00:00.0 -0500
@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: spf-engine
-Version: 3.0.3
+Version: 3.0.4
 Summary: SPF (Sender Policy Framework) processing engine for Postfix policy 
server and Milter implemented in Python.
 Keywords: Postfix,Sendmail,milter,spf,email
 Author-email: Scott Kitterman 
diff -Nru spf-engine-3.0.3/spf_engine/__init__.py 
spf-engine-3.0.4/spf_engine/__init__.py
--- spf-engine-3.0.3/spf_engine/__init__.py 2023-02-19 19:30:53.016298500 
-0500
+++ spf-engine-3.0.4/spf_engine/__init__.py 2023-04-07 22:36:19.567618000 
-0400
@@ -40,7 +40,7 @@
51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
 '''
 
-__version__ = "3.0.3"
+__version__ = "3.0.4"
 
 import syslog
 import os
diff -Nru spf-engine-3.0.3/spf_engine/policyd_spf.py 
spf-engine-3.0.4/spf_engine/policyd_spf.py
--- spf-engine-3.0.3/spf_engine/policyd_spf.py  2022-12-01 21:07:37.670749200 
-0500
+++ spf-engine-3.0.4/spf_engine/policyd_spf.py  2023-04-07 20:44:54.125643300 
-0400
@@ -94,7 +94,10 @@
 elif configData.get('Hide_Receiver') != 'No':
 data['recipient'] = ''
 elif data.get('recipient') != 'none':
-data['recipient'] = data.get('recipient').split('@')[1]
+try:
+data['recipient'] = data.get('recipient').split('@')[1]
+except IndexError:
+pass # local 

Processed: unblock: devscripts [pre-approval]

[Debian Bug Tracking System]

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

> retitle 1033838 unblock: devscripts [pre-approval]
Bug #1033838 [release.debian.org] release.debian.org: Pre-merge review for 
devscripts
Changed Bug title to 'unblock: devscripts [pre-approval]' from 
'release.debian.org: Pre-merge review for devscripts'.
> affects 1033838 src:devscripts
Bug #1033838 [release.debian.org] unblock: devscripts [pre-approval]
Added indication that 1033838 affects src:devscripts
> user release.debian@packages.debian.org
Setting user to release.debian@packages.debian.org (was gin...@debian.org).
> usertag 1033838 + unblock
There were no usertags set.
Usertags are now: unblock.
> thanks
Stopping processing here.

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

Processed: [pre-approval] unblock: glibc/2.36-9

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + src:glibc
Bug #1034134 [release.debian.org] [pre-approval] unblock: glibc/2.36-9
Added indication that 1034134 affects src:glibc

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

Bug#1034134: [pre-approval] unblock: glibc/2.36-9

[Aurelien Jarno]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: gl...@packages.debian.org, debian-gl...@lists.debian.org
Control: affects -1 + src:glibc

[ Reason ]
An RC bug reported by a user (#1033931) triggered a routing update of
the glibc package from the upstream stable tree, which contains the fix.

The upstream stable tree also includes a fix to the daylight computation
affecting at least the Africa/Tripoli timezone, as well as a fix to the
testsuite on POWER when compiling with -mcpu=power10 (which is not the
case of Debian).

This is also the occasion to update the debconf translation that has
been received since the toolchain freeze.

[ Impact ]
The FIS-GT.M database randomly crash on x86 processors using the SSE2
version of memcmp, due to a bug in that specific implementation.

[ Tests ]
The changes to the SSE2 version of memcmp is covered by the existing
testsuite. The changes to the daylight computation comes with a new
test, which unfortunately can't be run, as it requires a binary test
file which can't be included easily in the diff, so it is disabled in
the debian package, but I verified manually it passes correctly.

[ Risks ]
The changes in the resulting binary packages are quite small if we
except the translation updates, and have been shipped in some other
distributions for a couple of months.

Let me anyway detail the changelog that might look scarying at a first
glance:

|  [ Aurelien Jarno ]
|  * debian/po/it.po: Update Italian debconf translation, by Luca Monducci.
|Closes: #1028133.
|  * debian/po/tr.po: Update Turkish debconf translation, by Atila KOÇ.
|Closes: #1028306.
|  * debian/po/cs.po: Update Czech debconf translation, by Miroslav Kure.
|Closes: #1028326.
|  * debian/po/zh_CN.po: Update Chinese debconf translation, by Tianyu Chen.
|  * debian/po/pt.po: Update Portugues debconf translation, by Pedro Ribeiro.
|Closes: #1028353.
|  * debian/po/sk.po: Fix invalid control sequence in Slovak translation.
|  * debian/po/pt_BR.po: Update Brazilian Portuguese debconf translation, by
|Adriano Rafael Gomes. Closes: #1029005.
|  * debian/po/nl.po: Update Dutch debconf translation, by Frans Spiesschaert.
|Closes: #1029018, #1033905.
|  * debian/po/ro.po: Update Romanian debconf translation, by Remus-Gabriel
|Chelu. Closes: #1031163.

All of the above are just debconf translation updates received
recently, it would be good to have them for Bookworm. They represent the
majority of the diff.

|  * debian/patches/git-updates.diff: update from upstream stable branch:
|- Prevent SIGSEGV in the SSE2 version of memcmp when data is concurrently
|  modified. Closes: #1033931.
|- Fix a corner case in daylight computation affecting the Africa/Tripoli
|  zone since tzdata 2022g.
|- Fix elf/tst-tlsopt-powerpc failure when compiled with -mcpu=power10.

Those are the changes pulled from the upstream stable branch. Note that
the changes to elf/tst-tlsopt-powerpc is not relevant for Debian as the
ppc64el toolchain does not default to -mcpu=power10 (and neither the
ppc64 nor powerpc one do), and anyway the change is in the testsuite so
does not affect the resulting binary packages.

|  * patches/any/local-disable-tst-bz29951.diff: disable new test included in
|the latest update from upstream stable branch, as git-updates.diff can't
|include the corresponding binary test file.

As explained above we can't easily run the new test for the daylight
computation fix, so this patch disables it until we can find a better
solution.

|  [ Samuel Thibault ]
|  * debian/sysdeps/hurd.mk: Add -fno-omit-frame-pointer to extra_cflags.
|  * debian/testsuite-xfail-debian.mk: Update hurd results.
|  * debian/patches/hurd-i386/git-intr-msg-cfa.diff: Fix stack unwinding over
|_hurd_intr_rpc_mach_msg, for go runtime.
|  * debian/libc0.3.symbols.hurd-i386: Update symbols with new RPCs.

Those are changes that have been accumulated in git since the toolchain
freeze, and only affect hurd specific code, so with no impact on the
binaries of the release architectures.

[ 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
diff --git a/debian/changelog b/debian/changelog
index d1a16865..d67a3e5d 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,41 @@
+glibc (2.36-9) unstable; urgency=medium
+
+  [ Aurelien Jarno ]
+  * debian/po/it.po: Update Italian debconf translation, by Luca Monducci.
+Closes: #1028133.
+  * debian/po/tr.po: Update Turkish debconf translation, by Atila KOÇ.
+Closes: #1028306.
+  * debian/po/cs.po: Update Czech debconf translation, by Miroslav Kure.
+Closes: #1028326.
+  * debian/po/zh_CN.po: Update Chinese debconf translation, by Tianyu Chen.
+  * debian/po/pt.po: Update Portugues debconf translation, by Pedro Ribeiro.
+Closes: #1028353.
+  * debian/po/sk.

Bug#1034142: unblock: live-installer/58

[Roland Clobus]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package live-installer, see also the discussion on
https://lists.debian.org/debian-cd/2023/04/msg9.html which leads to this
unblock request.

[ Reason ]
The Debian installer, when started from a live image, needs about 2 additional
minutes after
the 'Installation is complete, so it is time to boot into your new system'
prompt is shown. This additional delay can be removed by performing the step to
remove the live-specific packages earlier, ensuring that only one long non-
interactive phase is present in the installer. The regular installation takes
about 20-30 minutes.

[ Impact ]
The user will have to wait an additional 2 minutes after pressing the button to
reboot the computer (because that's the time required to remove all live-
related packages on a non Qt-based system).
An inconvenience, which is not necessary, and will be avoided by this change.

[ Tests ]
The new version of live-installer is working correctly, as can be seen by a sid
build of the live image on openQA:
https://openqa.debian.net/tests/138478/video?filename=video.ogv
See the movie at 0:50-0:56

[ Risks ]
The patch is a trivial rename of the hook file from 60remove-live-packages to
14remove-live-packages

The other changes in the diff are the usual Janitor and modernisation changes.

[ 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 ]
* kibi asked me to file the unblock. I'm not a DD (yet?) and would need a
sponsor if additional changes need to be made/reverted.
* This bug report might be non-standard, because reportbug crashed while
generating this unblock report (to be filed later)

With kind regards,
Roland Clobus
Working on the Debian live images

unblock live-installer/58
diff -Nru live-installer-57/AUTHORS live-installer-58/AUTHORS
--- live-installer-57/AUTHORS   2018-08-10 21:22:33.0 +0200
+++ live-installer-58/AUTHORS   2019-04-15 19:43:07.0 +0200
@@ -1,4 +1,4 @@
-Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
+Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
 Upstream-Name: live-installer
 Upstream-Contact: debian-b...@lists.debian.org
 Source: http://snapshot.debian.org/package/live-installer/
diff -Nru live-installer-57/ChangeLog live-installer-58/ChangeLog
--- live-installer-57/ChangeLog 2019-01-17 13:03:40.0 +0100
+++ live-installer-58/ChangeLog 2019-04-15 19:43:07.0 +0200
@@ -1,6 +1,32 @@
+live-installer (58) unstable; urgency=medium
+
+  [ Jonathan Carter ]
+  * Fix typo in previous changelog entry
+  * Update standards version to 4.6.1
+  * Upload MR!3 from Roland Clobus
+- Remove the live packages before the cdrom is unmounted
+  * Remove myself from uploaders
+
+  [ Cyril Brulebois ]
+  * Remove Christian Perrier from Uploaders, with many thanks for all
+his contributions over the years! (Closes: #927548)
+
+  [ Holger Wansing ]
+  * Remove trailing whitespace from changelog file, to fix lintian tag.
+  * Change Format URI in copyright file to https, to fix lintian tag.
+
+  [ Debian Janitor ]
+  * Add missing ${misc:Depends} to Depends for live-installer.
+  * Drop custom source compression, custom source compression level.
+  * Bump debhelper from old 10 to 13.
+  * Set debhelper-compat version in Build-Depends.
+  * Update standards version to 4.6.0, no changes needed.
+
+ -- Jonathan Carter   Mon, 15 Apr 2019 17:43:07 +
+
 live-installer (57) unstable; urgency=medium
 
-  * Add calamares-settings-debian as packaged to be removed at
+  * Add calamares-settings-debian as package to be removed at
 the end of installation
   * Add self to uploaders
   * Update standards-version to 4.3.0
@@ -78,7 +104,7 @@
 live-installer (48) unstable; urgency=low
 
   * Drop cruft files from my unclean git copy. Sigh:
-- live-installer.d/remove-packages 
+- live-installer.d/remove-packages
 - live-installer.d/xserver-xorg
 
  -- Christian Perrier   Mon, 09 Mar 2015 16:56:58 +0100
@@ -465,7 +491,7 @@
   * Lithuanian (lt.po) by Kęstutis Biliūnas
   * Slovenian (sl.po) by Vanja Cvelbar
 
- -- Daniel Baumann   Thu, 18 May 2010 18:53:34 +0200
+ -- Daniel Baumann   Tue, 18 May 2010 18:53:34 +0200
 
 live-installer (17) unstable; urgency=low
 
diff -Nru live-installer-57/COPYING live-installer-58/COPYING
--- live-installer-57/COPYING   2018-08-10 21:22:33.0 +0200
+++ live-installer-58/COPYING   2019-04-15 19:43:07.0 +0200
@@ -1,4 +1,4 @@
-Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
+Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
 Upstream-Name: live-installer
 Upstream-Contact: debian-b...@lists.debian.org
 Source: http://snapshot.debian.org/package/live-installer/
diff -Nru live-installer-57/debian/chang

Bug#1034146: unblock: ledger/3.3.0-3

[David Bremner]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: led...@packages.debian.org
Control: affects -1 + src:ledger

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Please unblock package ledger


[ Reason ]

This version fixes two bugs with severity important: #1032292 and #1033552.

[ Impact ]

The first is a regression from the version in bullseye, while the
second is an old crash.

[ Tests ]

Ledger has an extensive build time test suite. I have also manually
sanity checked the new binary packages.

[ Risks ]

Ledger is a leaf package. The two patches are cherry-picked from
upstream, and the total diff is small (6 insertions , 4 deletions)

[ 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 ]

Trimmed diff of only upstream changes also attached.


unblock ledger/3.3.0-3


-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkiyHYXwaY0SiY6fqA0U5G1WqFSEFAmQz8r8ACgkQA0U5G1Wq
FSEE3Q//cNItCQC0KvUyWw0kY4v0aa05Y3K+F+F3u8IOBjnhGkBA5+gR4Rq110dE
4N0K7l7JLemR7eJBHtOh+LfGI6AmLGurD0hmAwVrjYC+ti5xcnDMN7tpfXLKaqIS
jmCATrWtKN9+IZKl6G4V0R7o+HtKfHb4qG8Gzk3qwvjCtTvEGJGiwA1ErwCjUidn
+uBlIzn3MRiAjxrNWUQqq8RkPtyvP95JSgvpAXtQuo0qI2YQ0/613wlS2Fq4S1+J
mlC1rr/gpLl2wpxpUGVB8ph6rsgcKs5TY8GQ5nCk8h8EfH8eAvNwrs6AKEdVna+z
TC31HQ5Jw4s7jyoQRu2L2K3lM0F97FO8P5DXA2nn+AjfQqNvBXyXZMFtLfdnWKIc
g2mws+mD0/zVUwUJtTAdeei46SJilGDJXZ9To7I0LxYcFRPvP8CGfJP0wTSNdvAU
ylEmIppHnJ/Byz5N/JgPg/oi/ehwgixmt6j9Z/2r0CwSTdBqXiEe9Qu9XjEuqT2I
O6okdg8t07zGyf2+wSyeh6cJ7x87od2OtRZi48N2yrD+t8/sPuo6TvdxZmp+LIgg
AqDvkCiQ2uCnEFg3B6shARL51Jp2UScPLnXdVH6sjSQ0QwwaHzopZ2G+nCVYG7mc
uRFlbIq9yWHGQY5oYLXDvUs+kuB98BPZOR17CYh6h3ZKvywGNmc=
=dJ3v
-END PGP SIGNATURE-
diff -Nru ledger-3.3.0/debian/changelog ledger-3.3.0/debian/changelog
--- ledger-3.3.0/debian/changelog   2023-02-17 09:58:07.0 -0400
+++ ledger-3.3.0/debian/changelog   2023-03-28 08:05:17.0 -0300
@@ -1,3 +1,18 @@
+ledger (3.3.0-3) unstable; urgency=medium
+
+  * Bug fix: "Valid transaction: Error: Divide by zero", thanks to Martin
+Michlmayr (Closes: #1033552). Cherry-pick upstream commit 49cf332.
+
+ -- David Bremner   Tue, 28 Mar 2023 08:05:17 -0300
+
+ledger (3.3.0-2) unstable; urgency=medium
+
+  * Bug fix: "Ledger 3.3.0 regression: specifying format for commodity",
+thanks to Martin Michlmayr (Closes: #1032292). Cherry-pick upstream
+commit 87b6a1e.
+
+ -- David Bremner   Sat, 04 Mar 2023 15:32:33 -0800
+
 ledger (3.3.0-1) unstable; urgency=medium
 
   * Bug fix: "New upstream release: 3.3.0", thanks to Martin Michlmayr
diff -Nru 
ledger-3.3.0/debian/patches/0001-Do-not-perform-commodity-reduction-when-parsing-a-fo.patch
 
ledger-3.3.0/debian/patches/0001-Do-not-perform-commodity-reduction-when-parsing-a-fo.patch
--- 
ledger-3.3.0/debian/patches/0001-Do-not-perform-commodity-reduction-when-parsing-a-fo.patch
 1969-12-31 20:00:00.0 -0400
+++ 
ledger-3.3.0/debian/patches/0001-Do-not-perform-commodity-reduction-when-parsing-a-fo.patch
 2023-03-28 08:05:17.0 -0300
@@ -0,0 +1,28 @@
+From: John Wiegley 
+Date: Thu, 2 Mar 2023 15:04:29 -0800
+Subject: Do not perform commodity reduction when parsing a format directive
+
+---
+ src/textual.cc | 8 +---
+ 1 file changed, 5 insertions(+), 3 deletions(-)
+
+diff --git a/src/textual.cc b/src/textual.cc
+index 62007ab..5276c92 100644
+--- a/src/textual.cc
 b/src/textual.cc
+@@ -1132,10 +1132,12 @@ void 
instance_t::commodity_format_directive(commodity_t& comm, string format)
+   // observational formatting.
+   trim(format);
+   amount_t amt;
+-  amt.parse(format);
++  amt.parse(format, PARSE_NO_REDUCE);
+   if (amt.commodity() != comm)
+-throw_(parse_error, _f("commodity directive symbol %1% and format 
directive symbol %2% should be the same") %
+-  comm.symbol() % amt.commodity().symbol());
++throw_(parse_error,
++   _f("commodity directive symbol %1% and format directive symbol %2% 
should be the same")
++ % comm.symbol()
++ % amt.commodity().symbol());
+   amt.commodity().add_flags(COMMODITY_STYLE_NO_MIGRATE);
+   VERIFY(amt.valid());
+ }
diff -Nru 
ledger-3.3.0/debian/patches/0002-Change-a-use-of-is_realzero-to-just-is_zero.patch
 
ledger-3.3.0/debian/patches/0002-Change-a-use-of-is_realzero-to-just-is_zero.patch
--- 
ledger-3.3.0/debian/patches/0002-Change-a-use-of-is_realzero-to-just-is_zero.patch
  1969-12-31 20:00:00.0 -0400
+++ 
ledger-3.3.0/debian/patches/0002-Change-a-use-of-is_realzero-to-just-is_zero.patch
  2023-03-28 08:05:17.0 -0300
@@ -0,0 +1,22 @@
+From: John Wiegley 
+Date: Thu, 23 Mar 2023 11:23:39 -0700
+Subject: Change a use of is_realzero to just is_zero
+
+This is needed to avoid a possible divide by zero.
+---
+ src/pool.cc | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/src/pool.cc b/src/pool.cc
+index 2c055d6..73e7

Processed: unblock: ledger/3.3.0-3

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + src:ledger
Bug #1034146 [release.debian.org] unblock: ledger/3.3.0-3
Added indication that 1034146 affects src:ledger

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

Processed: unblock: (pre-approval): glib2.0/2.74.6-2

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + src:glib2.0
Bug #1034149 [release.debian.org] unblock: (pre-approval): glib2.0/2.74.6-2
Added indication that 1034149 affects src:glib2.0

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

Bug#1034149: unblock: (pre-approval): glib2.0/2.74.6-2

[Simon McVittie]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: glib...@packages.debian.org
Control: affects -1 + src:glib2.0

I've been using this proposed glib2.0 update for a few days and I'd like
to upload it to unstable. There's nothing RC here, but it seems safer and
easier to do several small bugfix updates rather than one large one.

[ Reason ]
Pick up stable-branch changes from upstream, which are expected to be
released in 2.74.7 at some point.

[ Impact ]
If not accepted:
- Peer-to-peer D-Bus servers implemented with GLib, such as the ones in
  gvfs and ibus, won't interoperate properly with sd-bus clients
  (GNOME/glib#2916)
- Some multi-threaded uses of GDBus will have a use-after-free
  (GNOME/glib#2924)
- glib2.0 will FTBFS in non-minimal Docker containers (GNOME/glib#3307)

[ Tests ]
Automated tests continue to pass, and I've been using this version on my
laptop for several days. There is no specific test coverage for the changes.

[ Risks ]
High-visibility key package, but the changes are narrowly targeted.

[ 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

unblock glib2.0/2.74.6-2
diffstat for glib2.0-2.74.6 glib2.0-2.74.6

 debian/changelog   |   13 
 debian/patches/gdbus-Fix-an-accidental-string-freeze-break.patch   |   31 ++
 debian/patches/gdbus-Never-buffer-reads-during-server-authentication.patch |  141 ++
 debian/patches/gdbusconnection-Make-GDBusMethodInvocation-transfer-a-bit.patch |   28 +
 debian/patches/gdbusinterfaceskeleton-Fix-a-use-after-free-of-a-GDBusMet.patch |   58 
 debian/patches/gdbusinterfaceskeleton-Remove-an-unnecessary-helper-struc.patch |   83 +
 debian/patches/series  |6 
 debian/patches/tests-Skip-assert-msg-test.py-if-gdb-fails.patch|   34 ++
 gio/gdbusauth.c|   50 ++-
 gio/gdbusconnection.c  |2 
 gio/gdbusinterfaceskeleton.c   |   24 -
 glib/tests/assert-msg-test.py  |6 
 12 files changed, 442 insertions(+), 34 deletions(-)

diff -Nru glib2.0-2.74.6/debian/changelog glib2.0-2.74.6/debian/changelog
--- glib2.0-2.74.6/debian/changelog	2023-03-02 20:53:53.0 +
+++ glib2.0-2.74.6/debian/changelog	2023-04-04 09:55:32.0 +0100
@@ -1,3 +1,16 @@
+glib2.0 (2.74.6-2) unstable; urgency=medium
+
+  * d/patches: Update to upstream 2.74.x branch commit
+2.74.6-12-ga1e169129, omitting Windows-specific changes
+- Fix GDBus server interop with sd-bus clients (GNOME/glib#2916)
+- Fix use-after-free of a GDBusMethodInvocation in some threaded
+  use patterns (GNOME/glib#2924)
+- Fix a test failure resulting in FTBFS in some container environments
+  if gdb happens to be installed, but access to ptrace and
+  /proc/PID/mem is disallowed (GNOME/glib#3307)
+
+ -- Simon McVittie   Tue, 04 Apr 2023 09:55:32 +0100
+
 glib2.0 (2.74.6-1) unstable; urgency=medium
 
   * New upstream stable release
diff -Nru glib2.0-2.74.6/debian/patches/gdbusconnection-Make-GDBusMethodInvocation-transfer-a-bit.patch glib2.0-2.74.6/debian/patches/gdbusconnection-Make-GDBusMethodInvocation-transfer-a-bit.patch
--- glib2.0-2.74.6/debian/patches/gdbusconnection-Make-GDBusMethodInvocation-transfer-a-bit.patch	1970-01-01 01:00:00.0 +0100
+++ glib2.0-2.74.6/debian/patches/gdbusconnection-Make-GDBusMethodInvocation-transfer-a-bit.patch	2023-04-04 09:55:32.0 +0100
@@ -0,0 +1,28 @@
+From: Philip Withnall 
+Date: Wed, 22 Feb 2023 12:50:10 +
+Subject: gdbusconnection: Make GDBusMethodInvocation transfer a bit clearer
+
+Add a missing steal call in `schedule_method_call()`. This introduces no
+functional changes, but documents the ownership transfer more clearly.
+
+Signed-off-by: Philip Withnall 
+Bug: https://gitlab.gnome.org/GNOME/glib/-/issues/2924
+Origin: https://gitlab.gnome.org/GNOME/glib/-/merge_requests/3298
+Applied-upstream: 2.74.7, commit:2da9ca2727a559a5e6b517582d14ba05d963f603
+---
+ gio/gdbusconnection.c | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/gio/gdbusconnection.c b/gio/gdbusconnection.c
+index 663cd95..368898d 100644
+--- a/gio/gdbusconnection.c
 b/gio/gdbusconnection.c
+@@ -5048,7 +5048,7 @@ schedule_method_call (GDBusConnection*connection,
+   g_source_set_priority (idle_source, G_PRIORITY_DEFAULT);
+   g_source_set_callback (idle_source,
+  call_in_idle_cb,
+- invocation,
++ g_steal_pointer (&invocation),
+  g_object_unref);
+   g_s

Bug#1034153: unblock: scikit-rf/0.15.4-2.1

[Josef Schneider]

Package: release.debian.org
Severity: normal
X-Debbugs-Cc: josef81...@gmail.com, t...@debian.org, ruben.undh...@gmail.com
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package scikit-rf.

[ Reason ]
This update allows the python package to import without error by 
importing the collections.abc python package in replacement of the 
collections python package because collections.abc contains the Sequence 
and MutableMapping attributes (see #1032392).


[ Impact ]
With this fix, the package does not throw an AttributeError when being 
imported in a python console. scikit-rf has no reverse-dependencies, so 
there is no impact on other packages.


[ Tests ]
dh_auto_test runs during the build and would fail the build if tests 
failed. I installed the new .deb and ran `import skrf` and `from skrf 
import Network` in a python console. No error was thrown and running 
`skrf` produces '/usr/lib/python3/dist-packages/skrf/__init__.py'> as expected. The 
updates were also reviewed by the DD who signed and uploaded the package.


[ Risks ]
scikit-rf has no reverse-dependencies so there are no 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

unblock: scikit-rf/0.15.4-2.1

--
Josef Schneider

GPG Fingerprint 3267 0331 DB61 A817 7D25 4D05 5A44 BC12 F2A8 E58F
diff -Nru scikit-rf-0.15.4/debian/changelog scikit-rf-0.15.4/debian/changelog
--- scikit-rf-0.15.4/debian/changelog   2020-12-02 09:46:23.0 +0100
+++ scikit-rf-0.15.4/debian/changelog   2023-04-04 19:53:06.0 +0200
@@ -1,3 +1,11 @@
+scikit-rf (0.15.4-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add patch to import python package collections.abc instead of collections.
++ Fixes AttributeError when importing the package (Closes: #1032392).
+
+ -- Josef Schneider   Tue, 04 Apr 2023 19:53:06 +0200
+
 scikit-rf (0.15.4-2) unstable; urgency=medium
 
   * First source-only upload
diff -Nru scikit-rf-0.15.4/debian/patches/0002-import-collections-abc.patch 
scikit-rf-0.15.4/debian/patches/0002-import-collections-abc.patch
--- scikit-rf-0.15.4/debian/patches/0002-import-collections-abc.patch   
1970-01-01 01:00:00.0 +0100
+++ scikit-rf-0.15.4/debian/patches/0002-import-collections-abc.patch   
2023-04-04 19:53:06.0 +0200
@@ -0,0 +1,43 @@
+From eb86566f22b80cf782585dc04d872fc11b437946 Mon Sep 17 00:00:00 2001
+From: Josef Schneider 
+Date: Tue, 4 Apr 2023 20:04:21 +0200
+Subject: [PATCH] import collections abc
+
+---
+ skrf/util.py | 6 +++---
+ 1 file changed, 3 insertions(+), 3 deletions(-)
+
+diff --git a/skrf/util.py b/skrf/util.py
+index b9566f3..355ec0e 100644
+--- a/skrf/util.py
 b/skrf/util.py
+@@ -32,7 +32,7 @@ import six.moves.cPickle as pickle
+ 
+ import numpy as npy
+ from datetime import datetime
+-import collections
++import collections.abc
+ import pprint
+ import re
+ from subprocess import Popen, PIPE
+@@ -286,7 +286,7 @@ def findReplace(directory, find, replace, filePattern):
+ 
+ # general purpose objects
+ 
+-class HomoList(collections.Sequence):
++class HomoList(collections.abc.Sequence):
+ '''
+ 
+ A Homogeneous Sequence
+@@ -384,7 +384,7 @@ class HomoList(collections.Sequence):
+ return pprint.pformat(self.store)
+ 
+ 
+-class HomoDict(collections.MutableMapping):
++class HomoDict(collections.abc.MutableMapping):
+ '''
+ A Homogeneous Mutable Mapping
+ 
+-- 
+2.38.1
+
diff -Nru scikit-rf-0.15.4/debian/patches/series 
scikit-rf-0.15.4/debian/patches/series
--- scikit-rf-0.15.4/debian/patches/series  2020-12-02 09:45:36.0 
+0100
+++ scikit-rf-0.15.4/debian/patches/series  2023-04-04 19:53:06.0 
+0200
@@ -1 +1,2 @@
 0001-Included-script-should-run-with-Python-3.patch
+0002-import-collections-abc.patch


OpenPGP_0x5A44BC12F2A8E58F.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Processed: unblock: pci.ids/0.0~2023.03.17-1

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + src:pci.ids
Bug #1034157 [release.debian.org] unblock: pci.ids/0.0~2023.03.17-1
Added indication that 1034157 affects src:pci.ids

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

Bug#1034157: unblock: pci.ids/0.0~2023.03.17-1

[Guillem Jover]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: pci@packages.debian.org
Control: affects -1 + src:pci.ids

Please unblock package pci.ids

[ Reason ]

This is a data-only package that provides know PCI IDs and their
descriptions, which helps with hardware enablement. (I've been meaning
to send similar requests for stable, but as I've not don that before I
was a bit hesitant, but depending on the outcome of this one, I might
start proposing those too.)

[ Impact ]

Hardware that was previously unknown would now be known to the system
and packages using this database.

[ Tests ]

The package provides an autopkgtest that verifies the format of the
database.

[ Risks ]

I'd say very minimal.

[ Checklist ]

  [√] all changes are documented in the d/changelog
  [√] I reviewed all changes and I approve them
  [√] attach debdiff against the package in testing

[ Other info ]

None.

unblock pci.ids/0.0~2023.03.17-1

Thanks,
Guillem
diff -Nru pci.ids-0.0~2023.02.23/debian/changelog 
pci.ids-0.0~2023.03.17/debian/changelog
--- pci.ids-0.0~2023.02.23/debian/changelog 2023-02-26 23:31:06.0 
+0100
+++ pci.ids-0.0~2023.03.17/debian/changelog 2023-03-22 23:56:31.0 
+0100
@@ -1,3 +1,10 @@
+pci.ids (0.0~2023.03.17-1) unstable; urgency=medium
+
+  * New upstream release.
+- Refresh patch.
+
+ -- Guillem Jover   Wed, 22 Mar 2023 23:56:31 +0100
+
 pci.ids (0.0~2023.02.23-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru pci.ids-0.0~2023.02.23/debian/patches/0001-Fix-encoding-issues.patch 
pci.ids-0.0~2023.03.17/debian/patches/0001-Fix-encoding-issues.patch
--- pci.ids-0.0~2023.02.23/debian/patches/0001-Fix-encoding-issues.patch
2023-02-26 23:30:31.0 +0100
+++ pci.ids-0.0~2023.03.17/debian/patches/0001-Fix-encoding-issues.patch
2023-03-22 23:51:29.0 +0100
@@ -12,7 +12,7 @@
 
 --- a/pci.ids
 +++ b/pci.ids
-@@ -2749,7 +2749,7 @@
+@@ -2752,7 +2752,7 @@
  # FX-797A-TNBC
1682 3213  HD 7970 Black Edition
1682 3214  Double D HD 7970
@@ -21,7 +21,7 @@
  # Radeon HD 7970 X2
1787 2317  Radeon HD 7990
1787 3000  Tahiti XT2 [Radeon HD 7970 GHz Edition]
-@@ -2812,7 +2812,7 @@
+@@ -2815,7 +2815,7 @@
174b e282  Vapor-X R9 290X Tri-X OC
174b e285  R9 290X Tri-X OC
174b e324  Grenada XT2 [Radeon R9 390X]
@@ -30,7 +30,7 @@
1787 2357  Grenada XT [Radeon R9 390X]
67b1  Hawaii PRO [Radeon R9 290/390]
1043 04dd  STRIX R9 390
-@@ -3703,7 +3703,7 @@
+@@ -3707,7 +3707,7 @@
1002 0322  All-in-Wonder X1800XL
1002 0d02  Radeon X1800 CrossFire Edition
710a  R520 [Radeon X1800 GTO]
@@ -39,7 +39,7 @@
710b  R520 [Radeon X1800 GTO]
710e  R520 GL [FireGL V7300]
13cc 3d0c  MXRT-5150
-@@ -7495,7 +7495,7 @@
+@@ -7499,7 +7499,7 @@
1077 02f2  QLogic 1x32Gb QLE2770 FC HBA
1077 02f3  QLogic 2x32Gb QLE2772 FC HBA
1590 02d3  SN1610Q - 1P Enhanced 32GFC Single Port Fibre 
Channel Host Bus Adapter
@@ -48,7 +48,7 @@
2289  ISP2852-based 64/32G Fibre Channel to PCIe Controller with 
StorCryption
1077 02e9  QLE2882 Dual Port 64GFC PCIe Gen4 x8 Adapter with 
StorCryption
1077 02eb  QLE2782 Dual Port 32GFC PCIe Gen4 x8 Adapter with 
StorCryption
-@@ -13227,7 +13227,7 @@
+@@ -13233,7 +13233,7 @@
10ec 8739  Dell Wireless 1801
17aa b736  Z50-75
b822  RTL8822BE 802.11a/b/g/n/ac WiFi adapter
@@ -57,7 +57,7 @@
17aa 5124  ThinkPad E595
17aa b023  ThinkPad E595
c821  RTL8821CE 802.11ac PCIe Wireless Network Adapter
-@@ -21323,10 +21323,10 @@
+@@ -21338,10 +21338,10 @@
193d 1084  NIC-ETH540F-3S-2P
1016  MT27710 Family [ConnectX-4 Lx Virtual Function]
1017  MT27800 Family [ConnectX-5]
@@ -72,7 +72,7 @@
193d 1051  NIC-IB1040i-Mb-2P
1018  MT27800 Family [ConnectX-5 Virtual Function]
1019  MT28800 Family [ConnectX-5 Ex]
-@@ -21522,7 +21522,7 @@
+@@ -21540,7 +21540,7 @@
  15cd  Dreamtech Co Ltd
  15ce  Genrad Inc
  # https://www.hilscher.com/imprint/
@@ -81,7 +81,7 @@
  CIFX PCI/PCIe
  15d1  Infineon Technologies AG
  15d2  FIC (First International Computer Inc)
-@@ -21993,14 +21993,14 @@
+@@ -22013,14 +22013,14 @@
002e  AR9287 Wireless Network Adapter (PCI-Express)
105b e034  T77H167.00
0030  AR93xx Wireless Network Adapter
@@ -98,7 +98,7 @@
105b e044  Unex DHXA-225
144d 410e  AR9485WB-EG 802.11b/g/n mini-PCIe card on a series 3 
laptop
1a3b 1186  AW-NE186H
-@@ -25410,13 +25410,13 @@
+@@ -25434,13 +25434,13 @@
1203  NVMe SSD Controller UHXXXa series
1e81 a121  NVMe SSD UHXXXa 

Bug#1034161: unblock: muffin/5.6.4-1

[Fabio Fantoni]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: muf...@packages.debian.org, fantonifa...@tiscali.it
Control: affects -1 + src:muffin

Please unblock package muffin

5.6.4-1 include a new bugfix release with some fixes:
- meta-gpu-xrandr: Account for the current user text scale factor when 
calculating the crtc scale based on Xft.dpi.

- window.c: Allow meta_window_get_xwindow() to be used with introspection.
- window.c: Restore property notify for the tile mode property.
- place.c: Add missing import.
- display.c: Make meta_display_get_pointer_window() available to 
cinnamon again.

- clutter-text.c: Remove redundant clutter_text_set_buffer call in finalize.

The symbol added is not a new function but only export of existant function,
making it available again to cinnamon.

I also added replace of libgdk-pixbuf2.0-dev build-dep. with 
libgdk-pixbuf-2.0-dev,
libgdk-pixbuf2.0-dev is a transition metapackage from bullseye so should 
don't

be a risk FWIK.

No regression found or reported, I think is good to have in bookworm.

[ Risks ]
I consider the risk of regression small

[ 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 muffin/5.6.4-1
diff --git a/clutter/clutter/clutter-text.c b/clutter/clutter/clutter-text.c
index 3da410f..e18ed4c 100644
--- a/clutter/clutter/clutter-text.c
+++ b/clutter/clutter/clutter-text.c
@@ -1807,7 +1807,6 @@ clutter_text_finalize (GObject *gobject)
 
   clutter_text_dirty_paint_volume (self);
 
-  clutter_text_set_buffer (self, NULL);
   g_free (priv->font_name);
 
   g_clear_object (&priv->input_focus);
diff --git a/debian/changelog b/debian/changelog
index 88556cf..e435e28 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+muffin (5.6.4-1) unstable; urgency=medium
+
+  * New upstream bugfix version 5.6.4
+  * Replace libgdk-pixbuf2.0-dev build-dep. with libgdk-pixbuf-2.0-dev
+  * Update symbols
+
+ -- Fabio Fantoni   Sun, 19 Mar 2023 22:33:27 +0100
+
 muffin (5.6.3-1) unstable; urgency=medium
 
   * New upstream version 5.6.3
diff --git a/debian/control b/debian/control
index 130f0e7..0626f50 100644
--- a/debian/control
+++ b/debian/control
@@ -149,7 +149,7 @@ Depends: gir1.2-meta-muffin-0.0 (= ${binary:Version}),
  libcinnamon-desktop-dev (>= 5.6),
  libdrm-dev,
  libegl1-mesa-dev,
- libgdk-pixbuf2.0-dev,
+ libgdk-pixbuf-2.0-dev,
  libgles2-mesa-dev | libgles2-dev,
  libglib2.0-dev,
  libgraphene-1.0-dev (>= 1.9.3),
diff --git a/debian/libmuffin0.symbols b/debian/libmuffin0.symbols
index 2a1f2eb..279e3ed 100644
--- a/debian/libmuffin0.symbols
+++ b/debian/libmuffin0.symbols
@@ -2136,6 +2136,7 @@ libmuffin.so.0 libmuffin0 #MINVER#
  meta_display_get_monitor_scale@Base 5.4.1
  meta_display_get_n_monitors@Base 5.4.1
  meta_display_get_pad_action_label@Base 5.4.1
+ meta_display_get_pointer_window@Base 5.6.4
  meta_display_get_primary_monitor@Base 5.4.1
  meta_display_get_selection@Base 5.4.1
  meta_display_get_size@Base 5.4.1
diff --git a/meson.build b/meson.build
index 63b5fad..d4b4590 100644
--- a/meson.build
+++ b/meson.build
@@ -1,5 +1,5 @@
 project('muffin', 'c',
-  version: '5.6.3',
+  version: '5.6.4',
   meson_version: '>= 0.50.0',
   license: 'GPLv2+'
 )
diff --git a/src/backends/meta-settings-private.h 
b/src/backends/meta-settings-private.h
index a7241ce..8965e1c 100644
--- a/src/backends/meta-settings-private.h
+++ b/src/backends/meta-settings-private.h
@@ -58,6 +58,8 @@ void meta_settings_update_ui_scaling_factor (MetaSettings 
*settings);
 gboolean meta_settings_get_global_scaling_factor (MetaSettings *settings,
   int  *scaing_factor);
 
+double meta_settings_get_font_scaling_factor (MetaSettings *settings);
+
 META_EXPORT_TEST
 gboolean meta_settings_is_experimental_feature_enabled (MetaSettings   
*settings,
 
MetaExperimentalFeature feature);
diff --git a/src/backends/meta-settings.c b/src/backends/meta-settings.c
index e544d65..f4a692f 100644
--- a/src/backends/meta-settings.c
+++ b/src/backends/meta-settings.c
@@ -223,6 +223,12 @@ meta_settings_update_font_dpi (MetaSettings *settings)
 g_signal_emit (settings, signals[FONT_DPI_CHANGED], 0);
 }
 
+double
+meta_settings_get_font_scaling_factor(MetaSettings *settings)
+{
+return g_settings_get_double (settings->interface_settings, 
"text-scaling-factor");
+}
+
 int
 meta_settings_get_font_dpi (MetaSettings *settings)
 {
diff --git a/src/backends/x11/meta-gpu-xrandr.c 
b/src/backends/x11/meta-gpu-xrandr.c
index 65a3c30..f2563e6 100644
--- a/src/backends/x11/meta-gpu-xrandr.c
+++ b/src/backends/x11/meta-gpu-xrandr.c
@@ -98,6 +98,10 @@ static int
 get_current_dpi_scale (MetaMonitorManagerXrandr *

Processed: unblock: muffin/5.6.4-1

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + src:muffin
Bug #1034161 [release.debian.org] unblock: muffin/5.6.4-1
Added indication that 1034161 affects src:muffin

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

Processed: unblock: cinnamon/5.6.8-1

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + src:cinnamon
Bug #1034162 [release.debian.org] unblock: cinnamon/5.6.8-1
Added indication that 1034162 affects src:cinnamon

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

Bug#1034162: unblock: cinnamon/5.6.8-1

[Fabio Fantoni]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: cinna...@packages.debian.org, fantonifa...@tiscali.it
Control: affects -1 + src:cinnamon

Please unblock package cinnamon

5.6.8-1 include a new bugfix release with some fixes:
- grouped-window-list: Make appGroup's flashButton sane, fix invalid 
source id.

- cinnamon-screenshot.c: Disable unredirection when taking a screenshot.
- remove unused import cairo
- cs_themes: load theme thumbnail from XDG_DATA_DIRS
- gwl: Fix typo.
- sound applet: Clear the source ID in Seeker._timerCallback().
- window-list: Fix signal name for tile notifications.
- overrides.js: Silently fail to install polyfills.

One fix seems a "big patch" 
(https://github.com/linuxmint/cinnamon/commit/fcffd73eace934c817db394d347705f81e564f3c)
but solves cinnamon crash in some cases doing screenshot 
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032912)


No regression found or reported, I think is good to have in bookworm.

[ Risks ]
I consider the risk of regression small

[ 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 cinnamon/5.6.8-1
diff --git a/debian/changelog b/debian/changelog
index 6ca12b51a..8bd8d7d27 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+cinnamon (5.6.8-1) unstable; urgency=medium
+
+  * New upstream bugfix version 5.6.8 (Closes: #1032912)
+
+ -- Fabio Fantoni   Sun, 19 Mar 2023 22:38:37 +0100
+
 cinnamon (5.6.7-1) unstable; urgency=medium
 
   * New upstream version 5.6.7
diff --git 
a/files/usr/share/cinnamon/applets/grouped-window-l...@cinnamon.org/appGroup.js 
b/files/usr/share/cinnamon/applets/grouped-window-l...@cinnamon.org/appGroup.js
index ef0a7e5b8..9ca6b37d5 100644
--- 
a/files/usr/share/cinnamon/applets/grouped-window-l...@cinnamon.org/appGroup.js
+++ 
b/files/usr/share/cinnamon/applets/grouped-window-l...@cinnamon.org/appGroup.js
@@ -1,6 +1,7 @@
 const Cinnamon = imports.gi.Cinnamon;
 const Meta = imports.gi.Meta;
 const Clutter = imports.gi.Clutter;
+const GLib = imports.gi.GLib;
 const St = imports.gi.St;
 const Main = imports.ui.main;
 const Tweener = imports.ui.tweener;
@@ -304,35 +305,40 @@ class AppGroup {
 if (this._needsAttention) return;
 
 this._needsAttention = true;
-let counter = 0;
-this.flashButton(counter);
+this.flashButton();
 }
 
-flashButton(counter) {
-if (!this._needsAttention || !this.actor) return;
+flashButton() {
+if (!this._needsAttention || !this.actor || this.flashTimer)
+return;
 
-// If the app was closed during a flash sequence, stop looping.
-if (!this.groupState.groupReady && this.groupState.isFavoriteApp) {
-
this.actor.remove_style_class_name('grouped-window-list-item-demands-attention');
+if (!this.groupState.groupReady && this.groupState.isFavoriteApp)
 return;
-}
 
-this.actor.remove_style_pseudo_class('active');
-
this.actor.add_style_class_name('grouped-window-list-item-demands-attention');
-if (counter < FLASH_MAX_COUNT) {
-this.flashTimer = Mainloop.timeout_add(FLASH_INTERVAL, () => {
-if (this.actor && 
this.actor.has_style_class_name('grouped-window-list-item-demands-attention')) {
-
this.actor.remove_style_class_name('grouped-window-list-item-demands-attention');
-this.actor.add_style_pseudo_class('active');
-}
+let counter = 0;
+const sc = "grouped-window-list-item-demands-attention";
 
-this.flashTimer = Mainloop.timeout_add(FLASH_INTERVAL, () => {
-this.flashButton(++counter);
-});
-});
-} else {
-this.flashTimer = 0;
-}
+this.flashTimer = Mainloop.timeout_add(FLASH_INTERVAL, () => {
+if (!this._needsAttention) {
+this.flashTimer = 0;
+return GLib.SOURCE_REMOVE;
+}
+
+if (this.actor.has_style_class_name(sc)) {
+this.actor.add_style_class_name("active");
+this.actor.remove_style_class_name(sc);
+}
+else {
+this.actor.remove_style_class_name("active")
+this.actor.add_style_class_name(sc);
+}
+
+const continueFlashing = (counter++ < FLASH_MAX_COUNT);
+if (!continueFlashing) {
+this.flashTimer = 0;
+}
+return continueFlashing;
+});
 }
 
 getPreferredWidth(actor, forHeight, alloc) {
@@ -597,9 +603,7 @@ class AppGroup {
 if (hasFocus) {
 this.listState.trigger('updateFocusState', appId);
 this.actor.add_style_pseudo_class('focus');
-i

Processed: unblock: teeworlds/0.7.5-2

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + src:teeworlds
Bug #1034164 [release.debian.org] unblock: teeworlds/0.7.5-2
Added indication that 1034164 affects src:teeworlds

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

Bug#1034164: unblock: teeworlds/0.7.5-2

[Salvatore Bonaccorso]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: teewor...@packages.debian.org, Moritz Muehlenhoff 
, car...@debian.org
Control: affects -1 + src:teeworlds

Dear release team,

Please unblock package teeworlds

Moritz Muehlenhoff addressed with a targetted fix CVE-2021-43518,
#1009070 for teeworlds. It has been in unstable for 24 days, but needs
an explicit unblock. The issue would be classified no-dsa for bookworm
similar to bullseye, but as the fix is quite isolated might be worth
having it fixed in bookworm.

Attached is the full debdiff for the changes. I cannot say about
specific done tests on the package.

unblock teeworlds/0.7.5-2

Regards,
Salvatore
diff -Nru teeworlds-0.7.5/debian/changelog teeworlds-0.7.5/debian/changelog
--- teeworlds-0.7.5/debian/changelog2020-08-30 15:38:14.0 +0200
+++ teeworlds-0.7.5/debian/changelog2023-03-17 11:46:31.0 +0100
@@ -1,3 +1,10 @@
+teeworlds (0.7.5-2) unstable; urgency=medium
+
+  * Backport 91e5492d4c210f82f1ca6b43a73417fef5463368 as the hotfix
+for CVE-2021-43518 (Closes: #1009070)
+
+ -- Moritz Muehlenhoff   Fri, 17 Mar 2023 11:46:31 +0100
+
 teeworlds (0.7.5-1) unstable; urgency=medium
 
   * Team upload.
diff -Nru teeworlds-0.7.5/debian/patches/CVE-2021-43518.patch 
teeworlds-0.7.5/debian/patches/CVE-2021-43518.patch
--- teeworlds-0.7.5/debian/patches/CVE-2021-43518.patch 1970-01-01 
01:00:00.0 +0100
+++ teeworlds-0.7.5/debian/patches/CVE-2021-43518.patch 2023-03-17 
11:46:31.0 +0100
@@ -0,0 +1,34 @@
+Backport 91e5492d4c210f82f1ca6b43a73417fef5463368 as the hotfix for 
CVE-2021-43518
+
+--- teeworlds-0.7.5.orig/src/game/client/components/maplayers.cpp
 teeworlds-0.7.5/src/game/client/components/maplayers.cpp
+@@ -254,7 +254,7 @@ void CMapLayers::LoadEnvPoints(const CLa
+   p.m_Time = pEnvPoint_v1->m_Time;
+   p.m_Curvetype = pEnvPoint_v1->m_Curvetype;
+ 
+-  for(int c = 0; c < pItem->m_Channels; c++)
++  for(int c = 0; c < min(pItem->m_Channels, 4); 
c++)
+   {
+   p.m_aValues[c] = 
pEnvPoint_v1->m_aValues[c];
+   p.m_aInTangentdx[c] = 0;
+--- teeworlds-0.7.5.orig/src/game/editor/io.cpp
 teeworlds-0.7.5/src/game/editor/io.cpp
+@@ -478,7 +478,8 @@ int CEditorMap::Load(class IStorage *pSt
+   for(int e = 0; e < Num; e++)
+   {
+   CMapItemEnvelope *pItem = (CMapItemEnvelope 
*)DataFile.GetItem(Start+e, 0, 0);
+-  CEnvelope *pEnv = new 
CEnvelope(pItem->m_Channels);
++  const int Channels = min(pItem->m_Channels, 4);
++  CEnvelope *pEnv = new CEnvelope(Channels);
+   pEnv->m_lPoints.set_size(pItem->m_NumPoints);
+   for(int n = 0; n < pItem->m_NumPoints; n++)
+   {
+@@ -495,7 +496,7 @@ int CEditorMap::Load(class IStorage *pSt
+   pEnv->m_lPoints[n].m_Time = 
pEnvPoint_v1->m_Time;
+   pEnv->m_lPoints[n].m_Curvetype 
= pEnvPoint_v1->m_Curvetype;
+ 
+-  for(int c = 0; c < 
pItem->m_Channels; c++)
++  for(int c = 0; c < Channels; 
c++)
+   {
+   
pEnv->m_lPoints[n].m_aValues[c] = pEnvPoint_v1->m_aValues[c];
+   }
diff -Nru teeworlds-0.7.5/debian/patches/series 
teeworlds-0.7.5/debian/patches/series
--- teeworlds-0.7.5/debian/patches/series   2020-08-30 15:38:14.0 
+0200
+++ teeworlds-0.7.5/debian/patches/series   2023-03-17 11:46:31.0 
+0100
@@ -5,3 +5,4 @@
 no-cmake.patch
 python3.patch
 new-wavpack.patch
+CVE-2021-43518.patch

Processed: unblock: waypipe/0.8.4-3

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + src:waypipe
Bug #1034165 [release.debian.org] unblock: waypipe/0.8.4-3
Added indication that 1034165 affects src:waypipe

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

Bug#1034165: unblock: waypipe/0.8.4-3

[Gard Spreemann]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: wayp...@packages.debian.org, g...@nonempty.org
Control: affects -1 + src:waypipe

Please unblock package waypipe.


[ Reason ]
Waypipe versions prior to 0.8.6 contain a memory leak that is documented
as bug #1034163 [1]. I have cherry-picked a one-line fix from upstream
[2], and have verified that it fixes the problem. I have uploaded
0.8.4-3 to unstable with that patch as the only change. A debdiff
against 0.8.4-2 (in testing) is attached.

[ Impact ]
If the unblock isn't granted, Bookworm will ship with a version of
waypipe that leaks memory, making long-running sessions
problematic. Since waypipe's job is to provide SSH forwarding (à la "ssh
-X") to software running under Wayland, such long-running sessions are
expected.

[ Tests ]
By running waypipe in debug mode, e.g.

 waypipe -d ssh localhost weston-simple-shm  2>&1 | grep "in flight"

one can watch the "number of bytes in flight" messages report an
ever-increasing number of bytes in the version of waypipe in Bookworm
(0.8.4-2). With the fixed version from unstable (0.8.4-3), the number
of bytes in flight remains bounded.

This test was recommended to me by waypipe's upstream author.

[ Risks ]
The fix is a one-line patch, authored by upstream and already released
as part of upstream's version 0.8.6.

[ 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


[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034163

[2] 
https://gitlab.freedesktop.org/mstoeckl/waypipe/-/commit/9070c4c527c906cb186588ca410d92d2f7f3c7ba


unblock waypipe/0.8.4-3
diff -Nru waypipe-0.8.4/debian/changelog waypipe-0.8.4/debian/changelog
--- waypipe-0.8.4/debian/changelog	2022-11-23 17:11:16.0 +0100
+++ waypipe-0.8.4/debian/changelog	2023-04-10 15:51:36.0 +0200
@@ -1,3 +1,9 @@
+waypipe (0.8.4-3) unstable; urgency=medium
+
+  * Add upstream patch to fix memory leak. (Closes: #1034163)
+
+ -- Gard Spreemann   Mon, 10 Apr 2023 15:51:36 +0200
+
 waypipe (0.8.4-2) unstable; urgency=medium
 
   * Increase timeout limit for build-time tests. (Closes: #1011322)
diff -Nru waypipe-0.8.4/debian/patches/0001-Fix-a-memory-leak.patch waypipe-0.8.4/debian/patches/0001-Fix-a-memory-leak.patch
--- waypipe-0.8.4/debian/patches/0001-Fix-a-memory-leak.patch	1970-01-01 01:00:00.0 +0100
+++ waypipe-0.8.4/debian/patches/0001-Fix-a-memory-leak.patch	2023-04-10 15:51:36.0 +0200
@@ -0,0 +1,29 @@
+From: Gard Spreemann 
+Date: Mon, 10 Apr 2023 12:21:18 +0200
+Subject: Fix a memory leak
+
+This cherry-picks upstream commit
+9070c4c527c906cb186588ca410d92d2f7f3c7ba. The original commit message
+follows.
+
+This was introduced by a0f6bfa191f55b99e4ff68dd0063aa0c0e12dcbd
+incorrectly checking when to increase the value of
+cxs->last_confirmed_msgno. As a result, one of the two Waypipe
+processes would leak all the messages sent to the other process.
+---
+ src/mainloop.c | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/src/mainloop.c b/src/mainloop.c
+index 181319c..38a084d 100644
+--- a/src/mainloop.c
 b/src/mainloop.c
+@@ -280,7 +280,7 @@ static int interpret_chanmsg(struct chan_msg_state *cmsg,
+ 	} else if (type == WMSG_ACK_NBLOCKS) {
+ 		struct wmsg_ack *ackm = (struct wmsg_ack *)packet;
+ 		if (msgno_gt(ackm->messages_received,
+-cxs->last_received_msgno)) {
++cxs->last_confirmed_msgno)) {
+ 			cxs->last_confirmed_msgno = ackm->messages_received;
+ 		}
+ 		return 0;
diff -Nru waypipe-0.8.4/debian/patches/series waypipe-0.8.4/debian/patches/series
--- waypipe-0.8.4/debian/patches/series	1970-01-01 01:00:00.0 +0100
+++ waypipe-0.8.4/debian/patches/series	2023-04-10 15:51:36.0 +0200
@@ -0,0 +1 @@
+0001-Fix-a-memory-leak.patch


signature.asc
Description: PGP signature

Processed: unblock (pre-approval): gnome-shell/43.4-1

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + src:gnome-shell
Bug #1034166 [release.debian.org] unblock (pre-approval): gnome-shell/43.4-1
Added indication that 1034166 affects src:gnome-shell

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

Bug#1034166: unblock (pre-approval): gnome-shell/43.4-1

[Simon McVittie]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: gnome-sh...@packages.debian.org
Control: affects -1 + src:gnome-shell

I'd like to upload a new upstream bug fix release of gnome-shell.

[ Reason ]
Catch up with upstream 43.4 bug fix release, and cherry-pick patches
that were already accepted for 43.5.

[ Impact ]
One small bug fix, one translation update, and convert several earlier
translation updates and bug fixes from being applied as patches to being
part of the updated upstream source.

[ Tests ]
I used a previous release-candidate on my Intel laptop for several days
without noticing any regressions. The only change since that version is
the Abkhazian translation update.

[ Risks ]
Key package with high visibility in our default desktop environment, but
the changes are narrowly targeted.

[ 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
  (filtered to exclude patch contents and translations)

[ Other info ]
This has only been tested together with the corresponding mutter update.

unblock gnome-shell/43.4-1
debdiff *.dsc | filterdiff -p1 -x'debian/patches/*.patch' -x'po/*.po'

diffstat for gnome-shell-43.3 gnome-shell-43.4

 NEWS   |   14 
 debian/changelog   |   16 
 debian/patches/Update-Abkhazian-translation.patch  | 4910 ++
 debian/patches/Update-Finnish-translation.patch|  873 -
 debian/patches/Update-Georgian-translation.patch   |  577 -
 debian/patches/Update-German-translation.patch |  896 -
 debian/patches/Update-Hungarian-translation.patch  |  848 -
 debian/patches/Update-Indonesian-translation.patch |  544 -
 debian/patches/Update-Lithuanian-translation.patch |  554 -
 debian/patches/Update-Polish-translation.patch |  806 -
 debian/patches/Update-Portuguese-translation.patch |  574 -
 debian/patches/Update-Serbian-translation.patch|  591 -
 debian/patches/Update-Slovenian-translation.patch  | 1990 
 debian/patches/Update-Swedish-translation.patch|  537 -
 debian/patches/Update-Turkish-translation.patch|  869 -
 debian/patches/Update-Ukrainian-translation.patch  |  577 -
 debian/patches/debian/Revert-build-Port-to-gcr4.patch  |2 
 debian/patches/overview-Don-t-claim-to-be-SHOWN-when-HIDDEN-during-start.patch |   38 
 debian/patches/overview-Hide-when-failing-to-take-grab-at-end-of-startup.patch |   27 
 debian/patches/series  |   16 
 js/ui/dnd.js   |9 
 js/ui/status/network.js|6 
 meson.build|2 
 po/ab.po   | 4383 
 po/fr.po   |  377 
 subprojects/extensions-app/data/metainfo/org.gnome.Extensions.metainfo.xml.in  |1 
 subprojects/extensions-app/meson.build |2 
 subprojects/extensions-app/subprojects/shew/meson.build|2 
 subprojects/extensions-tool/meson.build|2 
 subprojects/shew/meson.build   |2 
 30 files changed, 9414 insertions(+), 10631 deletions(-)

diff -Nru gnome-shell-43.3/debian/changelog gnome-shell-43.4/debian/changelog
--- gnome-shell-43.3/debian/changelog	2023-03-08 11:09:54.0 +
+++ gnome-shell-43.4/debian/changelog	2023-04-10 14:07:38.0 +0100
@@ -1,3 +1,19 @@
+gnome-shell (43.4-1) unstable; urgency=medium
+
+  * Team upload
+  * New upstream release
+- Fix memory leaks when the list of wireless networks is refreshed
+  (GNOME/gnome-shell!2652)
+- Stop tracking drag-and-drop source object when destroyed
+  (part of GNOME/gnome-shell!2318)
+- Translation update: fr
+- All other changes were included in 43.3-2 and 43.3-3
+  * Drop patches added by 43.3-2 and 43.3-3, included in upstream 43.4
+  * d/patches: Update to gnome-43 branch commit 43.4-1-g3499d2e87
+- Translation update: ab
+
+ -- Simon McVittie   Mon, 10 Apr 2023 14:07:38 +0100
+
 gnome-shell (43.3-3) unstable; urgency=medium
 
   * Team upload

Processed: unblock (pre-approval): mutter/43.4-1

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + src:mutter
Bug #1034167 [release.debian.org] unblock (pre-approval): mutter/43.4-1
Added indication that 1034167 affects src:mutter

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

Bug#1034167: unblock (pre-approval): mutter/43.4-1

[Simon McVittie]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: mut...@packages.debian.org
Control: affects -1 + src:mutter

I'd like to upload a new upstream bug fix release of mutter.

[ Reason ]
Catch up with upstream 43.4 bug fix release, and cherry-pick patches
that were already accepted for 43.5.

[ Impact ]
Multiple bug fixes and one translation update. Also transfer various
earlier bug fixes from Debian patches into part of the upstream source.

[ Tests ]
I used a previous release-candidate on my Intel laptop for several days
without noticing any regressions. The only change since that version is
the Abkhazian translation update.

Upstream's automated tests (at build-time and during autopkgtest) have the
same coverage and results as the version currently in bookworm.

[ Risks ]
Key package with high visibility in our default desktop environment, but
the changes are narrowly targeted.

[ 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
  (filtered to exclude patch contents and translations)

[ Other info ]
This has only been tested together with the corresponding gnome-shell
update.

There is a remaining X11 focus issue that I'd like to be able to fix in
bookworm (#1032388) but upstream does not have a solution for it yet,
and the version already in testing has the same bug.

unblock mutter/43.4-1
debdiff *.dsc | filterdiff -p1 -x'po/*.po' -x'debian/patches/*.patch'

diffstat for mutter-43.3 mutter-43.4

 NEWS   |   13 
 clutter/clutter/clutter-text.c |1 
 cogl/cogl/cogl-framebuffer.c   |2 
 cogl/cogl/cogl-onscreen.c  |   18 
 cogl/cogl/cogl-onscreen.h  |3 
 debian/changelog   |   23 
 debian/patches/Revert-x11-Do-not-move-X11-input-focus-during-grabs.patch   |   87 
 debian/patches/Revert-x11-events-Do-not-update-focus-XWindow-during-grab.patch |   36 
 debian/patches/Update-Abkhazian-translation.patch  | 4262 ++
 debian/patches/color-device-Don-t-close-lcms-profile-on-error-from-cd_ic.patch |   52 
 debian/patches/color-device-Make-sure-lcms_context-is-not-NULL.patch   |   47 
 debian/patches/core-Avoid-focusing-windows-on-map-during-grabs.patch   |   35 
 debian/patches/debian/Support-Dynamic-triple-double-buffering.patch|8 
 debian/patches/debian/meson-Do-not-mark-CI-test-tools-as-required.patch|2 
 debian/patches/meson-add-back-default_driver-option.patch  |2 
 debian/patches/series  |   10 
 debian/patches/wayland-Don-t-overwrite-surface-offsets.patch   |   57 
 debian/patches/wayland-Skip-subsurface-desync-if-parent-is-NULL.patch  |   35 
 debian/patches/x11-Avoid-updating-focus-on-wayland-compositor.patch|   47 
 debian/patches/x11-Ignore-_NET_ACTIVE_WINDOW-client-messages-while-grabb.patch |   45 
 meson.build|2 
 po/ab.po   | 4159 +
 src/backends/meta-stage-impl.c |   14 
 src/wayland/meta-wayland-subsurface.c  |6 
 24 files changed, 8509 insertions(+), 457 deletions(-)

diff -Nru mutter-43.3/clutter/clutter/clutter-text.c mutter-43.4/clutter/clutter/clutter-text.c
--- mutter-43.3/clutter/clutter/clutter-text.c	2023-02-13 18:12:26.0 +
+++ mutter-43.4/clutter/clutter/clutter-text.c	2023-03-19 22:26:48.0 +
@@ -1826,7 +1826,6 @@
 
   clutter_text_free_paint_volume (self);
 
-  clutter_text_set_buffer (self, NULL);
   g_free (priv->font_name);
 
   g_clear_object (&priv->input_focus);
diff -Nru mutter-43.3/cogl/cogl/cogl-framebuffer.c mutter-43.4/cogl/cogl/cogl-framebuffer.c
--- mutter-43.3/cogl/cogl/cogl-framebuffer.c	2023-02-13 18:12:26.0 +
+++ mutter-43.4/cogl/cogl/cogl-framebuffer.c	2023-03-19 22:26:48.0 +
@@ -1695,8 +1695,6 @@
   CoglFramebufferPrivate *priv =
 cogl_framebuffer_get_instance_private (framebuffer);
 
-  g_return_if_fail (buffers & COGL_BUFFER_BIT_COLOR);
-
   cogl_framebuffer_driver_discard_buffers (priv->driver, buffers);
 }
 
diff -Nru mutter-43.3/cogl/cogl/cogl-onscreen.c mutter-43.4/cogl/cogl/cogl-onscreen.c
--- mutter-43.3/cogl/cogl/cogl-onscreen.c	2023-04-10 14:26:00.0 +0100
+++ mutter-43.4/cogl/cogl/cogl-onscreen.c	2023-04-10 14:26:01.0 +0100
@@ -334,17 +334

Bug#1034146: marked as done (unblock: ledger/3.3.0-3)

[Debian Bug Tracking System]

Your message dated Mon, 10 Apr 2023 16:09:54 +
with message-id 
and subject line unblock ledger
has caused the Debian Bug report #1034146,
regarding unblock: ledger/3.3.0-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.)


-- 
1034146: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034146
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: led...@packages.debian.org
Control: affects -1 + src:ledger

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Please unblock package ledger


[ Reason ]

This version fixes two bugs with severity important: #1032292 and #1033552.

[ Impact ]

The first is a regression from the version in bullseye, while the
second is an old crash.

[ Tests ]

Ledger has an extensive build time test suite. I have also manually
sanity checked the new binary packages.

[ Risks ]

Ledger is a leaf package. The two patches are cherry-picked from
upstream, and the total diff is small (6 insertions , 4 deletions)

[ 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 ]

Trimmed diff of only upstream changes also attached.


unblock ledger/3.3.0-3


-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkiyHYXwaY0SiY6fqA0U5G1WqFSEFAmQz8r8ACgkQA0U5G1Wq
FSEE3Q//cNItCQC0KvUyWw0kY4v0aa05Y3K+F+F3u8IOBjnhGkBA5+gR4Rq110dE
4N0K7l7JLemR7eJBHtOh+LfGI6AmLGurD0hmAwVrjYC+ti5xcnDMN7tpfXLKaqIS
jmCATrWtKN9+IZKl6G4V0R7o+HtKfHb4qG8Gzk3qwvjCtTvEGJGiwA1ErwCjUidn
+uBlIzn3MRiAjxrNWUQqq8RkPtyvP95JSgvpAXtQuo0qI2YQ0/613wlS2Fq4S1+J
mlC1rr/gpLl2wpxpUGVB8ph6rsgcKs5TY8GQ5nCk8h8EfH8eAvNwrs6AKEdVna+z
TC31HQ5Jw4s7jyoQRu2L2K3lM0F97FO8P5DXA2nn+AjfQqNvBXyXZMFtLfdnWKIc
g2mws+mD0/zVUwUJtTAdeei46SJilGDJXZ9To7I0LxYcFRPvP8CGfJP0wTSNdvAU
ylEmIppHnJ/Byz5N/JgPg/oi/ehwgixmt6j9Z/2r0CwSTdBqXiEe9Qu9XjEuqT2I
O6okdg8t07zGyf2+wSyeh6cJ7x87od2OtRZi48N2yrD+t8/sPuo6TvdxZmp+LIgg
AqDvkCiQ2uCnEFg3B6shARL51Jp2UScPLnXdVH6sjSQ0QwwaHzopZ2G+nCVYG7mc
uRFlbIq9yWHGQY5oYLXDvUs+kuB98BPZOR17CYh6h3ZKvywGNmc=
=dJ3v
-END PGP SIGNATURE-
diff -Nru ledger-3.3.0/debian/changelog ledger-3.3.0/debian/changelog
--- ledger-3.3.0/debian/changelog   2023-02-17 09:58:07.0 -0400
+++ ledger-3.3.0/debian/changelog   2023-03-28 08:05:17.0 -0300
@@ -1,3 +1,18 @@
+ledger (3.3.0-3) unstable; urgency=medium
+
+  * Bug fix: "Valid transaction: Error: Divide by zero", thanks to Martin
+Michlmayr (Closes: #1033552). Cherry-pick upstream commit 49cf332.
+
+ -- David Bremner   Tue, 28 Mar 2023 08:05:17 -0300
+
+ledger (3.3.0-2) unstable; urgency=medium
+
+  * Bug fix: "Ledger 3.3.0 regression: specifying format for commodity",
+thanks to Martin Michlmayr (Closes: #1032292). Cherry-pick upstream
+commit 87b6a1e.
+
+ -- David Bremner   Sat, 04 Mar 2023 15:32:33 -0800
+
 ledger (3.3.0-1) unstable; urgency=medium
 
   * Bug fix: "New upstream release: 3.3.0", thanks to Martin Michlmayr
diff -Nru 
ledger-3.3.0/debian/patches/0001-Do-not-perform-commodity-reduction-when-parsing-a-fo.patch
 
ledger-3.3.0/debian/patches/0001-Do-not-perform-commodity-reduction-when-parsing-a-fo.patch
--- 
ledger-3.3.0/debian/patches/0001-Do-not-perform-commodity-reduction-when-parsing-a-fo.patch
 1969-12-31 20:00:00.0 -0400
+++ 
ledger-3.3.0/debian/patches/0001-Do-not-perform-commodity-reduction-when-parsing-a-fo.patch
 2023-03-28 08:05:17.0 -0300
@@ -0,0 +1,28 @@
+From: John Wiegley 
+Date: Thu, 2 Mar 2023 15:04:29 -0800
+Subject: Do not perform commodity reduction when parsing a format directive
+
+---
+ src/textual.cc | 8 +---
+ 1 file changed, 5 insertions(+), 3 deletions(-)
+
+diff --git a/src/textual.cc b/src/textual.cc
+index 62007ab..5276c92 100644
+--- a/src/textual.cc
 b/src/textual.cc
+@@ -1132,10 +1132,12 @@ void 
instance_t::commodity_format_directive(commodity_t& comm, string format)
+   // observational formatting.
+   trim(format);
+   amount_t amt;
+-  amt.parse(format);
++  amt.parse(format, PARSE_NO_REDUCE);
+   if (amt.commodity() != comm)
+-throw_(parse_error, _f("commodity directive symbol %1% and format 
directive symbol %2% should be the same") %
+-  comm.symbol() % amt.commodity().symbol());
++throw_(parse_error,
++   _f("commodity directive symbol %1% and format directive symbol %2% 
should be the same")
++ % comm.symbol()
++ % amt.commodity().symbol());
+   amt.commodity().add_flags(COMMODITY_STYLE_NO_MIGRATE);
+   VERIFY(a

Bug#1034153: marked as done (unblock: scikit-rf/0.15.4-2.1)

[Debian Bug Tracking System]

Your message dated Mon, 10 Apr 2023 16:11:50 +
with message-id 
and subject line unblock scikit-rf
has caused the Debian Bug report #1034153,
regarding unblock: scikit-rf/0.15.4-2.1
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.)


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

Package: release.debian.org
Severity: normal
X-Debbugs-Cc: josef81...@gmail.com, t...@debian.org, ruben.undh...@gmail.com
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package scikit-rf.

[ Reason ]
This update allows the python package to import without error by 
importing the collections.abc python package in replacement of the 
collections python package because collections.abc contains the Sequence 
and MutableMapping attributes (see #1032392).


[ Impact ]
With this fix, the package does not throw an AttributeError when being 
imported in a python console. scikit-rf has no reverse-dependencies, so 
there is no impact on other packages.


[ Tests ]
dh_auto_test runs during the build and would fail the build if tests 
failed. I installed the new .deb and ran `import skrf` and `from skrf 
import Network` in a python console. No error was thrown and running 
`skrf` produces '/usr/lib/python3/dist-packages/skrf/__init__.py'> as expected. The 
updates were also reviewed by the DD who signed and uploaded the package.


[ Risks ]
scikit-rf has no reverse-dependencies so there are no 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

unblock: scikit-rf/0.15.4-2.1

--
Josef Schneider

GPG Fingerprint 3267 0331 DB61 A817 7D25 4D05 5A44 BC12 F2A8 E58F
diff -Nru scikit-rf-0.15.4/debian/changelog scikit-rf-0.15.4/debian/changelog
--- scikit-rf-0.15.4/debian/changelog   2020-12-02 09:46:23.0 +0100
+++ scikit-rf-0.15.4/debian/changelog   2023-04-04 19:53:06.0 +0200
@@ -1,3 +1,11 @@
+scikit-rf (0.15.4-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add patch to import python package collections.abc instead of collections.
++ Fixes AttributeError when importing the package (Closes: #1032392).
+
+ -- Josef Schneider   Tue, 04 Apr 2023 19:53:06 +0200
+
 scikit-rf (0.15.4-2) unstable; urgency=medium
 
   * First source-only upload
diff -Nru scikit-rf-0.15.4/debian/patches/0002-import-collections-abc.patch 
scikit-rf-0.15.4/debian/patches/0002-import-collections-abc.patch
--- scikit-rf-0.15.4/debian/patches/0002-import-collections-abc.patch   
1970-01-01 01:00:00.0 +0100
+++ scikit-rf-0.15.4/debian/patches/0002-import-collections-abc.patch   
2023-04-04 19:53:06.0 +0200
@@ -0,0 +1,43 @@
+From eb86566f22b80cf782585dc04d872fc11b437946 Mon Sep 17 00:00:00 2001
+From: Josef Schneider 
+Date: Tue, 4 Apr 2023 20:04:21 +0200
+Subject: [PATCH] import collections abc
+
+---
+ skrf/util.py | 6 +++---
+ 1 file changed, 3 insertions(+), 3 deletions(-)
+
+diff --git a/skrf/util.py b/skrf/util.py
+index b9566f3..355ec0e 100644
+--- a/skrf/util.py
 b/skrf/util.py
+@@ -32,7 +32,7 @@ import six.moves.cPickle as pickle
+ 
+ import numpy as npy
+ from datetime import datetime
+-import collections
++import collections.abc
+ import pprint
+ import re
+ from subprocess import Popen, PIPE
+@@ -286,7 +286,7 @@ def findReplace(directory, find, replace, filePattern):
+ 
+ # general purpose objects
+ 
+-class HomoList(collections.Sequence):
++class HomoList(collections.abc.Sequence):
+ '''
+ 
+ A Homogeneous Sequence
+@@ -384,7 +384,7 @@ class HomoList(collections.Sequence):
+ return pprint.pformat(self.store)
+ 
+ 
+-class HomoDict(collections.MutableMapping):
++class HomoDict(collections.abc.MutableMapping):
+ '''
+ A Homogeneous Mutable Mapping
+ 
+-- 
+2.38.1
+
diff -Nru scikit-rf-0.15.4/debian/patches/series 
scikit-rf-0.15.4/debian/patches/series
--- scikit-rf-0.15.4/debian/patches/series  2020-12-02 09:45:36.0 
+0100
+++ scikit-rf-0.15.4/debian/patches/series  2023-04-04 19:53:06.0 
+0200
@@ -1 +1,2 @@
 0001-Included-script-should-run-with-Python-3.patch
+0002-import-collections-abc.patch


OpenPGP_0x5A44BC12F2A8E58F.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Unblocked.--- End Message ---

Bug#1034164: marked as done (unblock: teeworlds/0.7.5-2)

[Debian Bug Tracking System]

Your message dated Mon, 10 Apr 2023 16:13:42 +
with message-id 
and subject line unblock teeworlds
has caused the Debian Bug report #1034164,
regarding unblock: teeworlds/0.7.5-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.)


-- 
1034164: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034164
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: teewor...@packages.debian.org, Moritz Muehlenhoff 
, car...@debian.org
Control: affects -1 + src:teeworlds

Dear release team,

Please unblock package teeworlds

Moritz Muehlenhoff addressed with a targetted fix CVE-2021-43518,
#1009070 for teeworlds. It has been in unstable for 24 days, but needs
an explicit unblock. The issue would be classified no-dsa for bookworm
similar to bullseye, but as the fix is quite isolated might be worth
having it fixed in bookworm.

Attached is the full debdiff for the changes. I cannot say about
specific done tests on the package.

unblock teeworlds/0.7.5-2

Regards,
Salvatore
diff -Nru teeworlds-0.7.5/debian/changelog teeworlds-0.7.5/debian/changelog
--- teeworlds-0.7.5/debian/changelog2020-08-30 15:38:14.0 +0200
+++ teeworlds-0.7.5/debian/changelog2023-03-17 11:46:31.0 +0100
@@ -1,3 +1,10 @@
+teeworlds (0.7.5-2) unstable; urgency=medium
+
+  * Backport 91e5492d4c210f82f1ca6b43a73417fef5463368 as the hotfix
+for CVE-2021-43518 (Closes: #1009070)
+
+ -- Moritz Muehlenhoff   Fri, 17 Mar 2023 11:46:31 +0100
+
 teeworlds (0.7.5-1) unstable; urgency=medium
 
   * Team upload.
diff -Nru teeworlds-0.7.5/debian/patches/CVE-2021-43518.patch 
teeworlds-0.7.5/debian/patches/CVE-2021-43518.patch
--- teeworlds-0.7.5/debian/patches/CVE-2021-43518.patch 1970-01-01 
01:00:00.0 +0100
+++ teeworlds-0.7.5/debian/patches/CVE-2021-43518.patch 2023-03-17 
11:46:31.0 +0100
@@ -0,0 +1,34 @@
+Backport 91e5492d4c210f82f1ca6b43a73417fef5463368 as the hotfix for 
CVE-2021-43518
+
+--- teeworlds-0.7.5.orig/src/game/client/components/maplayers.cpp
 teeworlds-0.7.5/src/game/client/components/maplayers.cpp
+@@ -254,7 +254,7 @@ void CMapLayers::LoadEnvPoints(const CLa
+   p.m_Time = pEnvPoint_v1->m_Time;
+   p.m_Curvetype = pEnvPoint_v1->m_Curvetype;
+ 
+-  for(int c = 0; c < pItem->m_Channels; c++)
++  for(int c = 0; c < min(pItem->m_Channels, 4); 
c++)
+   {
+   p.m_aValues[c] = 
pEnvPoint_v1->m_aValues[c];
+   p.m_aInTangentdx[c] = 0;
+--- teeworlds-0.7.5.orig/src/game/editor/io.cpp
 teeworlds-0.7.5/src/game/editor/io.cpp
+@@ -478,7 +478,8 @@ int CEditorMap::Load(class IStorage *pSt
+   for(int e = 0; e < Num; e++)
+   {
+   CMapItemEnvelope *pItem = (CMapItemEnvelope 
*)DataFile.GetItem(Start+e, 0, 0);
+-  CEnvelope *pEnv = new 
CEnvelope(pItem->m_Channels);
++  const int Channels = min(pItem->m_Channels, 4);
++  CEnvelope *pEnv = new CEnvelope(Channels);
+   pEnv->m_lPoints.set_size(pItem->m_NumPoints);
+   for(int n = 0; n < pItem->m_NumPoints; n++)
+   {
+@@ -495,7 +496,7 @@ int CEditorMap::Load(class IStorage *pSt
+   pEnv->m_lPoints[n].m_Time = 
pEnvPoint_v1->m_Time;
+   pEnv->m_lPoints[n].m_Curvetype 
= pEnvPoint_v1->m_Curvetype;
+ 
+-  for(int c = 0; c < 
pItem->m_Channels; c++)
++  for(int c = 0; c < Channels; 
c++)
+   {
+   
pEnv->m_lPoints[n].m_aValues[c] = pEnvPoint_v1->m_aValues[c];
+   }
diff -Nru teeworlds-0.7.5/debian/patches/series 
teeworlds-0.7.5/debian/patches/series
--- teeworlds-0.7.5/debian/patches/series   2020-08-30 15:38:14.0 
+0200
+++ teeworlds-0.7.5/debian/patches/series   2023-03-17 11:46:31.0 
+0100
@@ -5,3 +5,4 @@
 no-cmake.patch
 python3.patch
 new-wavpack.patch
+CVE-2021-43518.patch
--- End Message ---
--- Begin Message ---
Unblocked.--- End Message ---

Bug#1034157: marked as done (unblock: pci.ids/0.0~2023.03.17-1)

[Debian Bug Tracking System]

Your message dated Mon, 10 Apr 2023 16:14:03 +
with message-id 
and subject line unblock pci.ids
has caused the Debian Bug report #1034157,
regarding unblock: pci.ids/0.0~2023.03.17-1
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.)


-- 
1034157: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034157
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: pci@packages.debian.org
Control: affects -1 + src:pci.ids

Please unblock package pci.ids

[ Reason ]

This is a data-only package that provides know PCI IDs and their
descriptions, which helps with hardware enablement. (I've been meaning
to send similar requests for stable, but as I've not don that before I
was a bit hesitant, but depending on the outcome of this one, I might
start proposing those too.)

[ Impact ]

Hardware that was previously unknown would now be known to the system
and packages using this database.

[ Tests ]

The package provides an autopkgtest that verifies the format of the
database.

[ Risks ]

I'd say very minimal.

[ Checklist ]

  [√] all changes are documented in the d/changelog
  [√] I reviewed all changes and I approve them
  [√] attach debdiff against the package in testing

[ Other info ]

None.

unblock pci.ids/0.0~2023.03.17-1

Thanks,
Guillem
diff -Nru pci.ids-0.0~2023.02.23/debian/changelog 
pci.ids-0.0~2023.03.17/debian/changelog
--- pci.ids-0.0~2023.02.23/debian/changelog 2023-02-26 23:31:06.0 
+0100
+++ pci.ids-0.0~2023.03.17/debian/changelog 2023-03-22 23:56:31.0 
+0100
@@ -1,3 +1,10 @@
+pci.ids (0.0~2023.03.17-1) unstable; urgency=medium
+
+  * New upstream release.
+- Refresh patch.
+
+ -- Guillem Jover   Wed, 22 Mar 2023 23:56:31 +0100
+
 pci.ids (0.0~2023.02.23-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru pci.ids-0.0~2023.02.23/debian/patches/0001-Fix-encoding-issues.patch 
pci.ids-0.0~2023.03.17/debian/patches/0001-Fix-encoding-issues.patch
--- pci.ids-0.0~2023.02.23/debian/patches/0001-Fix-encoding-issues.patch
2023-02-26 23:30:31.0 +0100
+++ pci.ids-0.0~2023.03.17/debian/patches/0001-Fix-encoding-issues.patch
2023-03-22 23:51:29.0 +0100
@@ -12,7 +12,7 @@
 
 --- a/pci.ids
 +++ b/pci.ids
-@@ -2749,7 +2749,7 @@
+@@ -2752,7 +2752,7 @@
  # FX-797A-TNBC
1682 3213  HD 7970 Black Edition
1682 3214  Double D HD 7970
@@ -21,7 +21,7 @@
  # Radeon HD 7970 X2
1787 2317  Radeon HD 7990
1787 3000  Tahiti XT2 [Radeon HD 7970 GHz Edition]
-@@ -2812,7 +2812,7 @@
+@@ -2815,7 +2815,7 @@
174b e282  Vapor-X R9 290X Tri-X OC
174b e285  R9 290X Tri-X OC
174b e324  Grenada XT2 [Radeon R9 390X]
@@ -30,7 +30,7 @@
1787 2357  Grenada XT [Radeon R9 390X]
67b1  Hawaii PRO [Radeon R9 290/390]
1043 04dd  STRIX R9 390
-@@ -3703,7 +3703,7 @@
+@@ -3707,7 +3707,7 @@
1002 0322  All-in-Wonder X1800XL
1002 0d02  Radeon X1800 CrossFire Edition
710a  R520 [Radeon X1800 GTO]
@@ -39,7 +39,7 @@
710b  R520 [Radeon X1800 GTO]
710e  R520 GL [FireGL V7300]
13cc 3d0c  MXRT-5150
-@@ -7495,7 +7495,7 @@
+@@ -7499,7 +7499,7 @@
1077 02f2  QLogic 1x32Gb QLE2770 FC HBA
1077 02f3  QLogic 2x32Gb QLE2772 FC HBA
1590 02d3  SN1610Q - 1P Enhanced 32GFC Single Port Fibre 
Channel Host Bus Adapter
@@ -48,7 +48,7 @@
2289  ISP2852-based 64/32G Fibre Channel to PCIe Controller with 
StorCryption
1077 02e9  QLE2882 Dual Port 64GFC PCIe Gen4 x8 Adapter with 
StorCryption
1077 02eb  QLE2782 Dual Port 32GFC PCIe Gen4 x8 Adapter with 
StorCryption
-@@ -13227,7 +13227,7 @@
+@@ -13233,7 +13233,7 @@
10ec 8739  Dell Wireless 1801
17aa b736  Z50-75
b822  RTL8822BE 802.11a/b/g/n/ac WiFi adapter
@@ -57,7 +57,7 @@
17aa 5124  ThinkPad E595
17aa b023  ThinkPad E595
c821  RTL8821CE 802.11ac PCIe Wireless Network Adapter
-@@ -21323,10 +21323,10 @@
+@@ -21338,10 +21338,10 @@
193d 1084  NIC-ETH540F-3S-2P
1016  MT27710 Family [ConnectX-4 Lx Virtual Function]
1017  MT27800 Family [ConnectX-5]
@@ -72,7 +72,7 @@
193d 1051  NIC-IB1040i-Mb-2P
1018  MT27800 Family [ConnectX-5 Virtual Function]
1019  MT28800 Family [ConnectX-5 Ex]
-@@ -

Bug#1034165: marked as done (unblock: waypipe/0.8.4-3)

[Debian Bug Tracking System]

Your message dated Mon, 10 Apr 2023 16:14:33 +
with message-id 
and subject line unblock waypipe
has caused the Debian Bug report #1034165,
regarding unblock: waypipe/0.8.4-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.)


-- 
1034165: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034165
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: wayp...@packages.debian.org, g...@nonempty.org
Control: affects -1 + src:waypipe

Please unblock package waypipe.


[ Reason ]
Waypipe versions prior to 0.8.6 contain a memory leak that is documented
as bug #1034163 [1]. I have cherry-picked a one-line fix from upstream
[2], and have verified that it fixes the problem. I have uploaded
0.8.4-3 to unstable with that patch as the only change. A debdiff
against 0.8.4-2 (in testing) is attached.

[ Impact ]
If the unblock isn't granted, Bookworm will ship with a version of
waypipe that leaks memory, making long-running sessions
problematic. Since waypipe's job is to provide SSH forwarding (à la "ssh
-X") to software running under Wayland, such long-running sessions are
expected.

[ Tests ]
By running waypipe in debug mode, e.g.

 waypipe -d ssh localhost weston-simple-shm  2>&1 | grep "in flight"

one can watch the "number of bytes in flight" messages report an
ever-increasing number of bytes in the version of waypipe in Bookworm
(0.8.4-2). With the fixed version from unstable (0.8.4-3), the number
of bytes in flight remains bounded.

This test was recommended to me by waypipe's upstream author.

[ Risks ]
The fix is a one-line patch, authored by upstream and already released
as part of upstream's version 0.8.6.

[ 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


[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034163

[2] 
https://gitlab.freedesktop.org/mstoeckl/waypipe/-/commit/9070c4c527c906cb186588ca410d92d2f7f3c7ba


unblock waypipe/0.8.4-3
diff -Nru waypipe-0.8.4/debian/changelog waypipe-0.8.4/debian/changelog
--- waypipe-0.8.4/debian/changelog	2022-11-23 17:11:16.0 +0100
+++ waypipe-0.8.4/debian/changelog	2023-04-10 15:51:36.0 +0200
@@ -1,3 +1,9 @@
+waypipe (0.8.4-3) unstable; urgency=medium
+
+  * Add upstream patch to fix memory leak. (Closes: #1034163)
+
+ -- Gard Spreemann   Mon, 10 Apr 2023 15:51:36 +0200
+
 waypipe (0.8.4-2) unstable; urgency=medium
 
   * Increase timeout limit for build-time tests. (Closes: #1011322)
diff -Nru waypipe-0.8.4/debian/patches/0001-Fix-a-memory-leak.patch waypipe-0.8.4/debian/patches/0001-Fix-a-memory-leak.patch
--- waypipe-0.8.4/debian/patches/0001-Fix-a-memory-leak.patch	1970-01-01 01:00:00.0 +0100
+++ waypipe-0.8.4/debian/patches/0001-Fix-a-memory-leak.patch	2023-04-10 15:51:36.0 +0200
@@ -0,0 +1,29 @@
+From: Gard Spreemann 
+Date: Mon, 10 Apr 2023 12:21:18 +0200
+Subject: Fix a memory leak
+
+This cherry-picks upstream commit
+9070c4c527c906cb186588ca410d92d2f7f3c7ba. The original commit message
+follows.
+
+This was introduced by a0f6bfa191f55b99e4ff68dd0063aa0c0e12dcbd
+incorrectly checking when to increase the value of
+cxs->last_confirmed_msgno. As a result, one of the two Waypipe
+processes would leak all the messages sent to the other process.
+---
+ src/mainloop.c | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/src/mainloop.c b/src/mainloop.c
+index 181319c..38a084d 100644
+--- a/src/mainloop.c
 b/src/mainloop.c
+@@ -280,7 +280,7 @@ static int interpret_chanmsg(struct chan_msg_state *cmsg,
+ 	} else if (type == WMSG_ACK_NBLOCKS) {
+ 		struct wmsg_ack *ackm = (struct wmsg_ack *)packet;
+ 		if (msgno_gt(ackm->messages_received,
+-cxs->last_received_msgno)) {
++cxs->last_confirmed_msgno)) {
+ 			cxs->last_confirmed_msgno = ackm->messages_received;
+ 		}
+ 		return 0;
diff -Nru waypipe-0.8.4/debian/patches/series waypipe-0.8.4/debian/patches/series
--- waypipe-0.8.4/debian/patches/series	1970-01-01 01:00:00.0 +0100
+++ waypipe-0.8.4/debian/patches/series	2023-04-10 15:51:36.0 +0200
@@ -0,0 +1 @@
+0001-Fix-a-memory-leak.patch


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Unblocked.--- End Message ---

Bug#1034118: marked as done (unblock: lowdown/1.0.0-2)

[Debian Bug Tracking System]

Your message dated Mon, 10 Apr 2023 16:15:24 +
with message-id 
and subject line unblock lowdown
has caused the Debian Bug report #1034118,
regarding unblock: lowdown/1.0.0-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.)


-- 
1034118: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034118
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 lowdown, a key package, through:
  bind9 -> libmaxminddb -> lowdown

[ Reason ]
lowdown is a Markdown to HTML/roff/LaTeX/etc. translator. A regression
was introduced at some point where the -Tman (manpage) output used a
roff macro that is not present in the "man" package but in the "ms"
package. I reported this upstream[1], and it was subsequently fixed[2].

This is a bookworm-targeted backport of that specific upstream commit,
that applies cleanly as-is.

1: https://github.com/kristapsdz/lowdown/issues/111
2: 
https://github.com/kristapsdz/lowdown/commit/02491bf4ae2a39df2dfed10382512449a5b3262f

[ Impact ]
The output difference is minor from a visual standpoint, e.g.
   OPTIONS
  -batch_size __
  -  Maximum  number  of  entries to request per call to 
get-entries.
  -  You should not generally need to change this. Defaults to 1000.
  +Maximum number of entries to request per call to get-entries.  
You
  +should not generally need to change this. Defaults to 1000.

However, the roff output is technically invalid.

In Debian, this manifests in reverse build-dependencies that are using
lowdown to generate their manpage to emit lintian warnings, e.g.:
W: certspotter: groff-message 29: warning: macro 'PI' not defined 
[usr/share/man/man8/certspotter-script.8.gz:1]
W: certspotter: groff-message 56: warning: macro 'PI' not defined 
[usr/share/man/man8/certspotter.8.gz:1]

There are three reverse build-dependencies in testing:
  1) src:libmaxminddb
  2) src:certspotter
  3) src:nix

Only the first two are using -Tman. I am the maintainer for both.
src:libmaxminddb was built with an pre-regression version of lowdown and
is not affected. It can be binNMUed, although not strictly necessary.

src:certspotter is affected and should probably be binNMUed, although as
explained, the visual impact is relatively minor.

[ Tests ]
Upstream has a comprehensive test suite that runs as part of the build.
The package also has autopkgtests that pass.

[ Risks ]
The code for the fix is trivial. The package is technically a key
package, but only as a reverse build-dep of another package, and is only
a B-D for three packages in total.

[ 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 ]
debdiff attached; you can also find the git diff at:
https://salsa.debian.org/debian/lowdown/-/commit/0e2160bb23e194edc5c15c7772042857fd18f2f7

unblock lowdown/1.0.0-2

Also probably:

nmu certspotter_0.16.0-1 . ANY . unstable . -m "Rebuild with lowdown 1.0.0-2"

(but no idea how to ensure the ordering of those two, not fluent in
wanna-build)
diff -Nru lowdown-1.0.0/debian/changelog lowdown-1.0.0/debian/changelog
--- lowdown-1.0.0/debian/changelog  2023-01-07 06:52:41.0 +0200
+++ lowdown-1.0.0/debian/changelog  2023-04-09 03:39:15.0 +0300
@@ -1,3 +1,13 @@
+lowdown (1.0.0-2) unstable; urgency=medium
+
+  * Backport upstream patch to avoid the use of an -ms macro, PI, in the -Tman
+output. This addresses a man warning ("macro 'PI' not defined") which in
+turn is a lintian warning for packages using lowdown to generate their
+manpage(s).
+  * Bump Standards-Version to 4.6.2, no changes needed.
+
+ -- Faidon Liambotis   Sun, 09 Apr 2023 03:39:15 +0300
+
 lowdown (1.0.0-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru lowdown-1.0.0/debian/control lowdown-1.0.0/debian/control
--- lowdown-1.0.0/debian/control2023-01-07 04:49:43.0 +0200
+++ lowdown-1.0.0/debian/control2023-04-09 03:39:15.0 +0300
@@ -6,7 +6,7 @@
  libbsd-dev,
  libmd-dev,
  pkgconf | pkg-config,
-Standards-Version: 4.6.1
+Standards-Version: 4.6.2
 Section: text
 Homepage: https://kristaps.bsd.lv/lowdown/
 Vcs-Browser: https://salsa.debian.org/debian/lowdown
diff -Nru lowdown-1.0.0/debian/patches/dont-use-PI-for-tman.patch 
lowdown-1.0.0/debian/patches/dont-use-PI-for-tman.patch
--- lowdown-1.0.0/debian/patches/dont-use-PI-for-t

Bug#1034130: marked as done (unblock: wxpython4.0/4.2.0+dfsg-3)

[Debian Bug Tracking System]

Your message dated Mon, 10 Apr 2023 16:18:29 +
with message-id 
and subject line unblock wxpython4.0
has caused the Debian Bug report #1034130,
regarding unblock: wxpython4.0/4.2.0+dfsg-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.)


-- 
1034130: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034130
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: wxpython...@packages.debian.org
Control: affects -1 + src:wxpython4.0

Please unblock package wxpython4.0

[ Reason ]
Remove reference to non-existent package (wx3.0-doc).

[ Impact ]
wxpython4.0 will get shipped with a Suggests for a non-existent package.

[ Tests ]
None.

[ Risks ]
Changes are trivial.

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in testing

[ Other info ]
None

unblock wxpython4.0/4.2.0+dfsg-3
diff -Nru wxpython4.0-4.2.0+dfsg/debian/changelog 
wxpython4.0-4.2.0+dfsg/debian/changelog
--- wxpython4.0-4.2.0+dfsg/debian/changelog 2023-02-23 19:34:57.0 
-0500
+++ wxpython4.0-4.2.0+dfsg/debian/changelog 2023-03-15 20:27:44.0 
-0400
@@ -1,3 +1,9 @@
+wxpython4.0 (4.2.0+dfsg-3) unstable; urgency=medium
+
+  * d/control: update wx3.0-doc Suggests to wx3.2-doc (Closes: #1032867)
+
+ -- Scott Talbert   Wed, 15 Mar 2023 20:27:44 -0400
+
 wxpython4.0 (4.2.0+dfsg-2) unstable; urgency=medium
 
   * d/control: make sip-tools requirements match python3-sipbuild
diff -Nru wxpython4.0-4.2.0+dfsg/debian/control 
wxpython4.0-4.2.0+dfsg/debian/control
--- wxpython4.0-4.2.0+dfsg/debian/control   2023-02-23 19:26:38.0 
-0500
+++ wxpython4.0-4.2.0+dfsg/debian/control   2023-03-15 20:26:03.0 
-0400
@@ -33,7 +33,7 @@
 Package: python3-wxgtk4.0
 Architecture: any
 Depends: python3-pil, python3-six, ${python3:Depends}, ${shlibs:Depends}, 
${misc:Depends}
-Suggests: wx3.0-doc
+Suggests: wx3.2-doc
 Provides: ${python3:Provides}
 Description: Python 3 interface to the wxWidgets Cross-platform C++ GUI toolkit
  wxWidgets (formerly known as wxWindows) is a class library for C++ providing
--- End Message ---
--- Begin Message ---
Unblocked.--- End Message ---

Bug#1034132: marked as done (unblock: dpmb/0~2023.03.11)

[Debian Bug Tracking System]

Your message dated Mon, 10 Apr 2023 16:19:40 +
with message-id 
and subject line unblock dpmb
has caused the Debian Bug report #1034132,
regarding unblock: dpmb/0~2023.03.11
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.)


-- 
1034132: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034132
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: d...@packages.debian.org
Control: affects -1 + src:dpmb

Please unblock package dpmb/0~2023.03.11

DPMB = Debian Packaging Management (E-)Book

[ Reason ]

Content of the e-book has been updated for the Bookworm release,
describing changes like non-free-firmware, Stretch being now ELTS,
vrms has been renamed to check-dfsg-status, etc.

Sections about package management related packages which are no more
in any supported Debian release have been removed from the book.

[ Impact ]

Without the update, changes in Bookworm won't be covered in Bookworm.

[ Tests ]

The e-book (and package) built fine on Sid in three different types of
environment: locally, local minimal pbuilder chroot as well as on the
buildd.

Buildd-built HTML, EPUB and PDF variants have been skimmed through for
proper formatting. (HTML with Chromium, EPUB and PDF with mupdf.)

The Mobi version for Kindle devices hasn't been checked as I don't
have a Kindle device. But is converted from the EPUB version using
Calibre's ebook-convert.

[ Risks ]

Other book content has been updated or expanded, too. Changed or added
content might have introduced typos or other content issues.

[ Checklist ]
  [x] all (non-content) changes are documented in the d/changelog
  [x] I made all (non-content) changes and I approve them
  [x] attach debdiff against the package in testing

[ Other info ]

debdiff of the non-content changes:

diff -Nru dpmb-0~2021.03.01/debian/changelog dpmb-0~2023.03.11/debian/changelog
--- dpmb-0~2021.03.01/debian/changelog  2021-03-01 00:56:34.0 +0100
+++ dpmb-0~2023.03.11/debian/changelog  2023-03-12 00:34:38.0 +0100
@@ -1,3 +1,16 @@
+dpmb (0~2023.03.11) unstable; urgency=medium
+
+  * The Debian 12 Bookworm Edition.
++ Covers non-free-firmware archive section.
++ Debian 9 Stretch is now ELTS.
+  * Bracketize sole lintian override so far.
+  * Add lintian override for very-long-line-length-in-source-file on
+binary file and handwritten Markdown files with a few long semantic
+HTML oneliners.
+  * Declare compliance with Debian Policy 4.6.2. (No changes needed.)
+
+ -- Axel Beckert   Sat, 11 Mar 2023 23:34:38 +
+
 dpmb (0~2021.03.01) unstable; urgency=medium
 
   * New snapshot
diff -Nru dpmb-0~2021.03.01/debian/control dpmb-0~2023.03.11/debian/control
--- dpmb-0~2021.03.01/debian/control2021-02-03 04:27:56.0 +0100
+++ dpmb-0~2023.03.11/debian/control2023-03-12 00:32:59.0 +0100
@@ -10,7 +10,7 @@
  dblatex,
  texlive-lang-german,
  xmlto
-Standards-Version: 4.5.1
+Standards-Version: 4.6.2
 Homepage: https://www.dpmb.org/
 Vcs-Git: https://github.com/dpmb/dpmb.git
 Vcs-Browser: https://github.com/dpmb/dpmb
diff -Nru dpmb-0~2021.03.01/debian/lintian-overrides 
dpmb-0~2023.03.11/debian/lintian-overrides
--- dpmb-0~2021.03.01/debian/lintian-overrides  2016-06-29 23:15:14.0 
+0200
+++ dpmb-0~2023.03.11/debian/lintian-overrides  2023-03-12 00:20:22.0 
+0100
@@ -1,2 +1,2 @@
 # Feature request against doc-base, see https://bugs.debian.org/730240
-debian-paketmanagement-buch: doc-base-file-unknown-format 
debian-paketmanagement-buch:14 epub
+debian-paketmanagement-buch: doc-base-file-unknown-format epub 
[usr/share/doc-base/debian-paketmanagement-buch.debian-paketmanagement-buch:14]
diff -Nru dpmb-0~2021.03.01/debian/source/lintian-overrides 
dpmb-0~2023.03.11/debian/source/lintian-overrides
--- dpmb-0~2021.03.01/debian/source/lintian-overrides   1970-01-01 
01:00:00.0 +0100
+++ dpmb-0~2023.03.11/debian/source/lintian-overrides   2023-03-12 
00:28:25.0 +0100
@@ -0,0 +1,6 @@
+# Binary file
+dpmb source: very-long-line-length-in-source-file 1296 > 512 
[praxis/apt-cache/apt-cache.dia:2]
+
+# Handwritten Markdown with a few long semantic HTML oneliners
+dpmb source: very-long-line-length-in-source-file * > 512 [README.mdwn:64]
+very-long-line-length-in-source-file * > 512 [LICENSE.md:3]

Full debdiff attached.

So please

unblock dpmb/0~2023.03.11

Thanks in advance!


dpmb_0~2021.03.01_0~2023.03.11.dsc.debdiff.xz
Descrip

Bug#1034125: marked as done (unblock: mbedtls/2.28.2-1)

[Debian Bug Tracking System]

Your message dated Mon, 10 Apr 2023 16:17:33 +
with message-id 
and subject line unblock mbedtls
has caused the Debian Bug report #1034125,
regarding unblock: mbedtls/2.28.2-1
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.)


-- 
1034125: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034125
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: mbed...@packages.debian.org
Control: affects -1 + src:mbedtls

Please unblock package mbedtls

[ Reason ]
Upstream released a new LTS bugfix version, and I'd like to have it in
bookworm. Since mbedtls is a crypto library and backporting single commits can
be dangerous, importing new versions is the safest and most appropriate thing
to do, especially since the upstream developers do a pretty good job in
maintaining LTS versions for a long time.

[ Impact ]
If not granted, Debian will release with a somewhat vulnerable/buggy version of
a widely used crypto library.

[ Tests ]
I've manually reviewed the changelog and diffs of the new release, tested it
locally with the upstream test suite and autopkgtest, and it has passed all the
CI checks on Salsa (repo available at
).

[ Risks ]
Risks should be low, as upstream usually does a good job with backporting. The
"only" issue is that between 2.28.2 and 2.28.3 they have adopted a new code
style, and reformatted the whole codebase accordingly; this means that the
debdiff is huge, even though the changes are only a few. To make reviewing
easier for me and you too, I've prepared three git diffs that exclude the
upstream commits that reformatted the code, and another one that adds the
string "\emptydescription" to many documentation strings in the source files.
As upstream also always backports test code along with fixes, these diffs only
include changes from the include/ and library/ directories, since that's where
the code that gets into the binary packages resides.
.
The diffs were generated with these commands:
.
$ git clone https://github.com/Mbed-TLS/mbedtls.git
$ cd mbedtls
$ git diff v2.28.2..160df1d13621ca3ee70e1fa19d0da88398da9683~1 include/
library/
$ git diff
b37f6c1b95815d39fea26b2a17e318602eefe709..b361e04207831f753a29d6036361d44473bc~1
include/ library/
$ git diff 7a5168e90db359e17e72591cb5ddb06ef5f0388f..v2.28.3 include/
library/

[ 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 ]
I mistakenly uploaded the new mbedtls version to unstable because I didn't
realize it was a key package, and thought that a regular 20 days of waiting
would suffice. This is also my first unblock request, so please be clement with
me, thanks! :D

Also, the debdiff is not directly attached to this email to avoid hitting the
size limit of the mailing list. You can find it here:


unblock mbedtls/2.28.2-1
diff --git a/include/mbedtls/bn_mul.h b/include/mbedtls/bn_mul.h
index a3fc36381..bce9ce38c 100644
--- a/include/mbedtls/bn_mul.h
+++ b/include/mbedtls/bn_mul.h
@@ -84,6 +84,7 @@
 
 #endif /* bits in mbedtls_mpi_uint */
 
+/* *INDENT-OFF* */
 #if defined(MBEDTLS_HAVE_ASM)
 
 #ifndef asm
@@ -1001,4 +1002,5 @@
 #endif /* C (generic)  */
 #endif /* C (longlong) */
 
+/* *INDENT-ON* */
 #endif /* bn_mul.h */
diff --git a/include/mbedtls/check_config.h b/include/mbedtls/check_config.h
index 7ae1ff94d..2ab99823e 100644
--- a/include/mbedtls/check_config.h
+++ b/include/mbedtls/check_config.h
@@ -28,6 +28,7 @@
 #ifndef MBEDTLS_CHECK_CONFIG_H
 #define MBEDTLS_CHECK_CONFIG_H
 
+/* *INDENT-OFF* */
 /*
  * We assume CHAR_BIT is 8 in many places. In practice, this is true on our
  * target platforms, so not an issue, but let's just be extra sure.
@@ -143,6 +144,11 @@
 #error "MBEDTLS_ECDH_VARIANT_EVEREST_ENABLED defined, but 
MBEDTLS_ECDH_LEGACY_CONTEXT not disabled"
 #endif
 
+#if defined(MBEDTLS_ECP_RESTARTABLE)   && \
+!defined(MBEDTLS_ECP_C)
+#error "MBEDTLS_ECP_RESTARTABLE defined, but not all prerequisites"
+#endif
+
 #if defined(MBEDTLS_ECDSA_DETERMINISTIC) && !defined(MBEDTLS_HMAC_DRBG_C)
 #error "MBEDTLS_ECDSA_DETERMINISTIC defined, but not all prerequisites"
 #endif
@@ -955,4 +961,5 @@
  */
 typedef int mbedtls_iso_c_forbids_empty_translation_units;
 
+/* *INDENT-ON* */
 #endif /* MBEDTLS_CHECK_CONFIG_H */
diff -

Processed: Re: Bug#1034149: unblock: (pre-approval): glib2.0/2.74.6-2

[Debian Bug Tracking System]

Processing control commands:

> tags -1 confirmed moreinfo
Bug #1034149 [release.debian.org] unblock: (pre-approval): glib2.0/2.74.6-2
Added tag(s) confirmed and moreinfo.

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

Bug#1034149: unblock: (pre-approval): glib2.0/2.74.6-2

[Sebastian Ramacher]

Control: tags -1 confirmed moreinfo

On 2023-04-10 13:17:32 +0100, Simon McVittie wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> X-Debbugs-Cc: glib...@packages.debian.org
> Control: affects -1 + src:glib2.0
> 
> I've been using this proposed glib2.0 update for a few days and I'd like
> to upload it to unstable. There's nothing RC here, but it seems safer and
> easier to do several small bugfix updates rather than one large one.

Please go ahead and remove the moreinfo tag once the package is
available in unstable.

Cheers

> 
> [ Reason ]
> Pick up stable-branch changes from upstream, which are expected to be
> released in 2.74.7 at some point.
> 
> [ Impact ]
> If not accepted:
> - Peer-to-peer D-Bus servers implemented with GLib, such as the ones in
>   gvfs and ibus, won't interoperate properly with sd-bus clients
>   (GNOME/glib#2916)
> - Some multi-threaded uses of GDBus will have a use-after-free
>   (GNOME/glib#2924)
> - glib2.0 will FTBFS in non-minimal Docker containers (GNOME/glib#3307)
> 
> [ Tests ]
> Automated tests continue to pass, and I've been using this version on my
> laptop for several days. There is no specific test coverage for the changes.
> 
> [ Risks ]
> High-visibility key package, but the changes are narrowly targeted.
> 
> [ 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
> 
> unblock glib2.0/2.74.6-2

> diffstat for glib2.0-2.74.6 glib2.0-2.74.6
> 
>  debian/changelog 
>   |   13 
>  debian/patches/gdbus-Fix-an-accidental-string-freeze-break.patch 
>   |   31 ++
>  debian/patches/gdbus-Never-buffer-reads-during-server-authentication.patch   
>   |  141 ++
>  
> debian/patches/gdbusconnection-Make-GDBusMethodInvocation-transfer-a-bit.patch
>  |   28 +
>  
> debian/patches/gdbusinterfaceskeleton-Fix-a-use-after-free-of-a-GDBusMet.patch
>  |   58 
>  
> debian/patches/gdbusinterfaceskeleton-Remove-an-unnecessary-helper-struc.patch
>  |   83 +
>  debian/patches/series
>   |6 
>  debian/patches/tests-Skip-assert-msg-test.py-if-gdb-fails.patch  
>   |   34 ++
>  gio/gdbusauth.c  
>   |   50 ++-
>  gio/gdbusconnection.c
>   |2 
>  gio/gdbusinterfaceskeleton.c 
>   |   24 -
>  glib/tests/assert-msg-test.py
>   |6 
>  12 files changed, 442 insertions(+), 34 deletions(-)
> 
> diff -Nru glib2.0-2.74.6/debian/changelog glib2.0-2.74.6/debian/changelog
> --- glib2.0-2.74.6/debian/changelog   2023-03-02 20:53:53.0 +
> +++ glib2.0-2.74.6/debian/changelog   2023-04-04 09:55:32.0 +0100
> @@ -1,3 +1,16 @@
> +glib2.0 (2.74.6-2) unstable; urgency=medium
> +
> +  * d/patches: Update to upstream 2.74.x branch commit
> +2.74.6-12-ga1e169129, omitting Windows-specific changes
> +- Fix GDBus server interop with sd-bus clients (GNOME/glib#2916)
> +- Fix use-after-free of a GDBusMethodInvocation in some threaded
> +  use patterns (GNOME/glib#2924)
> +- Fix a test failure resulting in FTBFS in some container environments
> +  if gdb happens to be installed, but access to ptrace and
> +  /proc/PID/mem is disallowed (GNOME/glib#3307)
> +
> + -- Simon McVittie   Tue, 04 Apr 2023 09:55:32 +0100
> +
>  glib2.0 (2.74.6-1) unstable; urgency=medium
>  
>* New upstream stable release
> diff -Nru 
> glib2.0-2.74.6/debian/patches/gdbusconnection-Make-GDBusMethodInvocation-transfer-a-bit.patch
>  
> glib2.0-2.74.6/debian/patches/gdbusconnection-Make-GDBusMethodInvocation-transfer-a-bit.patch
> --- 
> glib2.0-2.74.6/debian/patches/gdbusconnection-Make-GDBusMethodInvocation-transfer-a-bit.patch
>  1970-01-01 01:00:00.0 +0100
> +++ 
> glib2.0-2.74.6/debian/patches/gdbusconnection-Make-GDBusMethodInvocation-transfer-a-bit.patch
>  2023-04-04 09:55:32.0 +0100
> @@ -0,0 +1,28 @@
> +From: Philip Withnall 
> +Date: Wed, 22 Feb 2023 12:50:10 +
> +Subject: gdbusconnection: Make GDBusMethodInvocation transfer a bit clearer
> +
> +Add a missing steal call in `schedule_method_call()`. This introduces no
> +functional changes, but documents the ownership transfer more clearly.
> +
> +Signed-off-by: Philip Withnall 
> +Bug: https://gitlab.gnome.org/GNOME/glib/-/issues/2924
> +Origin: https://gitlab.gnome.org/GNOME/glib/-/merge_requests/3298
> +Applied-upstream: 2.74.7, commit:2da9ca2727a559a5e6b517582d14ba05d963f603
> +---
> + gio/gdbusconnection.c | 2 +-
> + 1 file changed, 1 insertion(+), 1 deletion(-)
> +
> +diff --git a/gio/gdbusconnection.c b/gio/gdbusconnection.c
> +index 663cd95

Processed: Re: Bug#1034134: [pre-approval] unblock: glibc/2.36-9

[Debian Bug Tracking System]

Processing control commands:

> tags -1 moreinfo confirmed
Bug #1034134 [release.debian.org] [pre-approval] unblock: glibc/2.36-9
Added tag(s) confirmed and moreinfo.

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

Bug#1034134: [pre-approval] unblock: glibc/2.36-9

[Sebastian Ramacher]

Control: tags -1 moreinfo confirmed

On 2023-04-10 11:02:23 +0200, Aurelien Jarno wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> X-Debbugs-Cc: gl...@packages.debian.org, debian-gl...@lists.debian.org
> Control: affects -1 + src:glibc
> 
> [ Reason ]
> An RC bug reported by a user (#1033931) triggered a routing update of
> the glibc package from the upstream stable tree, which contains the fix.
> 
> The upstream stable tree also includes a fix to the daylight computation
> affecting at least the Africa/Tripoli timezone, as well as a fix to the
> testsuite on POWER when compiling with -mcpu=power10 (which is not the
> case of Debian).
> 
> This is also the occasion to update the debconf translation that has
> been received since the toolchain freeze.

Please go ahead and remove the moreinfo tag once the version is
available in unstable.

Cheers

> 
> [ Impact ]
> The FIS-GT.M database randomly crash on x86 processors using the SSE2
> version of memcmp, due to a bug in that specific implementation.
> 
> [ Tests ]
> The changes to the SSE2 version of memcmp is covered by the existing
> testsuite. The changes to the daylight computation comes with a new
> test, which unfortunately can't be run, as it requires a binary test
> file which can't be included easily in the diff, so it is disabled in
> the debian package, but I verified manually it passes correctly.
> 
> [ Risks ]
> The changes in the resulting binary packages are quite small if we
> except the translation updates, and have been shipped in some other
> distributions for a couple of months.
> 
> Let me anyway detail the changelog that might look scarying at a first
> glance:
> 
> |  [ Aurelien Jarno ]
> |  * debian/po/it.po: Update Italian debconf translation, by Luca Monducci.
> |Closes: #1028133.
> |  * debian/po/tr.po: Update Turkish debconf translation, by Atila KOÇ.
> |Closes: #1028306.
> |  * debian/po/cs.po: Update Czech debconf translation, by Miroslav Kure.
> |Closes: #1028326.
> |  * debian/po/zh_CN.po: Update Chinese debconf translation, by Tianyu Chen.
> |  * debian/po/pt.po: Update Portugues debconf translation, by Pedro Ribeiro.
> |Closes: #1028353.
> |  * debian/po/sk.po: Fix invalid control sequence in Slovak translation.
> |  * debian/po/pt_BR.po: Update Brazilian Portuguese debconf translation, by
> |Adriano Rafael Gomes. Closes: #1029005.
> |  * debian/po/nl.po: Update Dutch debconf translation, by Frans Spiesschaert.
> |Closes: #1029018, #1033905.
> |  * debian/po/ro.po: Update Romanian debconf translation, by Remus-Gabriel
> |Chelu. Closes: #1031163.
> 
> All of the above are just debconf translation updates received
> recently, it would be good to have them for Bookworm. They represent the
> majority of the diff.
> 
> |  * debian/patches/git-updates.diff: update from upstream stable branch:
> |- Prevent SIGSEGV in the SSE2 version of memcmp when data is concurrently
> |  modified. Closes: #1033931.
> |- Fix a corner case in daylight computation affecting the Africa/Tripoli
> |  zone since tzdata 2022g.
> |- Fix elf/tst-tlsopt-powerpc failure when compiled with -mcpu=power10.
> 
> Those are the changes pulled from the upstream stable branch. Note that
> the changes to elf/tst-tlsopt-powerpc is not relevant for Debian as the
> ppc64el toolchain does not default to -mcpu=power10 (and neither the
> ppc64 nor powerpc one do), and anyway the change is in the testsuite so
> does not affect the resulting binary packages.
> 
> |  * patches/any/local-disable-tst-bz29951.diff: disable new test included in
> |the latest update from upstream stable branch, as git-updates.diff can't
> |include the corresponding binary test file.
> 
> As explained above we can't easily run the new test for the daylight
> computation fix, so this patch disables it until we can find a better
> solution.
> 
> |  [ Samuel Thibault ]
> |  * debian/sysdeps/hurd.mk: Add -fno-omit-frame-pointer to extra_cflags.
> |  * debian/testsuite-xfail-debian.mk: Update hurd results.
> |  * debian/patches/hurd-i386/git-intr-msg-cfa.diff: Fix stack unwinding over
> |_hurd_intr_rpc_mach_msg, for go runtime.
> |  * debian/libc0.3.symbols.hurd-i386: Update symbols with new RPCs.
> 
> Those are changes that have been accumulated in git since the toolchain
> freeze, and only affect hurd specific code, so with no impact on the
> binaries of the release architectures.
> 
> [ 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

> diff --git a/debian/changelog b/debian/changelog
> index d1a16865..d67a3e5d 100644
> --- a/debian/changelog
> +++ b/debian/changelog
> @@ -1,3 +1,41 @@
> +glibc (2.36-9) unstable; urgency=medium
> +
> +  [ Aurelien Jarno ]
> +  * debian/po/it.po: Update Italian debconf translation, by Luca Monducci.
> +Closes:

Bug#1033996: marked as done (unblock: brltty/6.5-7)

[Debian Bug Tracking System]

Your message dated Mon, 10 Apr 2023 16:37:18 +
with message-id 
and subject line unblock brltty
has caused the Debian Bug report #1033996,
regarding unblock: brltty/6.5-7
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.)


-- 
1033996: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033996
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: brl...@packages.debian.org
Control: affects -1 + src:brltty

Hello,

I have uploaded brltty/6.5-7 to unstable, to make it hopefully included
in bookworm.

[ Reason ]
It was reported on
http://brltty.app/pipermail/brltty/2023-March/019836.html
that cursor routing is not working at all any more in X, because of a
crash in the routing process that 6.5-7 fixes.

[ Impact ]
Cursor routing is the way for blind users to be very efficient. Just
like we can click with the mouse wherever we want in some text to bring
the cursor there, when a blind user is reading some text they can press
a little button above the letter to bring the cursor there. Currently
the cursor doesn't move at all, and thus blind users have lost their way
to be very efficient at editing text.

The problem only affects X, not the Linux console, but more and more
blind users have to migrate to X environments since java-script-enabled
websites can nowaday only be browsed with e.g. firefox.

[ Tests ]
This was tested manually.

[ Risks ]
The code is very trivial: just check for the pointer before freeing the
underlying resource.

[ 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 ]
I also included a small pending d-i translation.

unblock brltty/6.5-7
diff -Nru brltty-6.5/debian/changelog brltty-6.5/debian/changelog
--- brltty-6.5/debian/changelog 2022-12-06 22:25:48.0 +0100
+++ brltty-6.5/debian/changelog 2023-04-06 01:27:28.0 +0200
@@ -1,3 +1,13 @@
+brltty (6.5-7) unstable; urgency=medium
+
+  [ Remus-Gabriel Chelu ]
+  * po/ro.po: Add Romanian debconf translation (Closes: Bug#1031150).
+
+  [ Samuel Thibault ]
+  * patches/atspi2-routing-crash.patch: Fix crash on cursor routing call.
+
+ -- Samuel Thibault   Thu, 06 Apr 2023 01:27:28 +0200
+
 brltty (6.5-6) unstable; urgency=medium
 
   * initramfs/hooks/brltty.in: Copy over brltty preferences into initramfs.
diff -Nru brltty-6.5/debian/patches/atspi2-routing-crash.patch 
brltty-6.5/debian/patches/atspi2-routing-crash.patch
--- brltty-6.5/debian/patches/atspi2-routing-crash.patch1970-01-01 
01:00:00.0 +0100
+++ brltty-6.5/debian/patches/atspi2-routing-crash.patch2023-04-06 
01:26:36.0 +0200
@@ -0,0 +1,40 @@
+commit 1d7515229f4283b2b6c1a74135be3eae2d9892cd
+Author: Samuel Thibault 
+Date:   Thu Apr 6 01:23:37 2023 +0200
+
+AtSpi2: Fix crash on routing request
+
+We would otherwise get, here with ubsan:
+
+brltty: report listener already registered: 5: a2CoreSelUpdated
+UndefinedBehaviorSanitizer:DEADLYSIGNAL
+==2087615==ERROR: UndefinedBehaviorSanitizer: SEGV on unknown address 
0x (pc 0x56356b124850 bp 0x sp 0x7fcc4d9fdbd8 T2087615)
+==2087615==The signal is caused by a READ memory access.
+==2087615==Hint: address points to the zero page.
+#0 0x56356b124850 in unregisterReportListener 
/home/samy/brl/mielke-svn/brltty/Programs/./report.c:208:22
+#1 0x7fcc5233f0ab in destruct_AtSpi2Screen 
/home/samy/brl/mielke-svn/brltty/Drivers/Screen/AtSpi2/./a2_screen.c:1574:5
+#2 0x56356b15304d in destructRoutingScreen 
/home/samy/brl/mielke-svn/brltty/Programs/./scr.c:255:3
+#3 0x56356b1542e9 in startRoutingProcess 
/home/samy/brl/mielke-svn/brltty/Programs/./routing.c:498:9
+#4 0x56356b1542e9 in runRoutingThread 
/home/samy/brl/mielke-svn/brltty/Programs/./routing.c:543:17
+#5 0x56356b11f574 in runThreadFunction 
/home/samy/brl/mielke-svn/brltty/Programs/./thread.c:151:33
+#6 0x56356b11f857 in runThread 
/home/samy/brl/mielke-svn/brltty/Programs/./thread.c:46:18
+#7 0x7fcc4f9c8fd3 in start_thread nptl/./nptl/pthread_create.c:442:8
+#8 0x7fcc4fa4966b in clone3 
misc/../sysdeps/unix/sysv/linux/x86_64/clone3.S:81
+
+diff --git a/Drivers/Screen/AtSpi2/a2_screen.c 
b/Drivers/Screen/AtSpi2/a2_screen.c
+index d60a91c68..9d5ca1d23 100644
+--- a/Drivers/Screen/AtSpi2/a2_screen.c
 b/Drivers/Screen/AtSpi2/a2_screen.c
+@@ -1571,8 +1571,1

Bug#1034131: marked as done (unblock: chromium/112.0.5615.49-2)

[Debian Bug Tracking System]

Your message dated Mon, 10 Apr 2023 16:36:41 +
with message-id 
and subject line unblock chromium
has caused the Debian Bug report #1034131,
regarding unblock: chromium/112.0.5615.49-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.)


-- 
1034131: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034131
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: chrom...@packages.debian.org
Control: affects -1 + src:chromium

Please unblock package chromium so that it migrates to bookworm after 5 
days. The upload to unstable fixes another set of 14 CVEs.


Thanks,
Andres
--- End Message ---
--- Begin Message ---
Unblocked.--- End Message ---

Processed: Re: Bug#1034166: unblock (pre-approval): gnome-shell/43.4-1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 moreinfo confirmed
Bug #1034166 [release.debian.org] unblock (pre-approval): gnome-shell/43.4-1
Added tag(s) confirmed and moreinfo.

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

Bug#1034166: unblock (pre-approval): gnome-shell/43.4-1

[Sebastian Ramacher]

Control: tags -1 moreinfo confirmed

On 2023-04-10 15:27:52 +0100, Simon McVittie wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> X-Debbugs-Cc: gnome-sh...@packages.debian.org
> Control: affects -1 + src:gnome-shell
> 
> I'd like to upload a new upstream bug fix release of gnome-shell.

Please go ahead and remove the moreinfo tag once the version is
available in unstable.

Cheers

> 
> [ Reason ]
> Catch up with upstream 43.4 bug fix release, and cherry-pick patches
> that were already accepted for 43.5.
> 
> [ Impact ]
> One small bug fix, one translation update, and convert several earlier
> translation updates and bug fixes from being applied as patches to being
> part of the updated upstream source.
> 
> [ Tests ]
> I used a previous release-candidate on my Intel laptop for several days
> without noticing any regressions. The only change since that version is
> the Abkhazian translation update.
> 
> [ Risks ]
> Key package with high visibility in our default desktop environment, but
> the changes are narrowly targeted.
> 
> [ 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
>   (filtered to exclude patch contents and translations)
> 
> [ Other info ]
> This has only been tested together with the corresponding mutter update.
> 
> unblock gnome-shell/43.4-1

> debdiff *.dsc | filterdiff -p1 -x'debian/patches/*.patch' -x'po/*.po'
> 
> diffstat for gnome-shell-43.3 gnome-shell-43.4
> 
>  NEWS 
>   |   14 
>  debian/changelog 
>   |   16 
>  debian/patches/Update-Abkhazian-translation.patch
>   | 4910 ++
>  debian/patches/Update-Finnish-translation.patch  
>   |  873 -
>  debian/patches/Update-Georgian-translation.patch 
>   |  577 -
>  debian/patches/Update-German-translation.patch   
>   |  896 -
>  debian/patches/Update-Hungarian-translation.patch
>   |  848 -
>  debian/patches/Update-Indonesian-translation.patch   
>   |  544 -
>  debian/patches/Update-Lithuanian-translation.patch   
>   |  554 -
>  debian/patches/Update-Polish-translation.patch   
>   |  806 -
>  debian/patches/Update-Portuguese-translation.patch   
>   |  574 -
>  debian/patches/Update-Serbian-translation.patch  
>   |  591 -
>  debian/patches/Update-Slovenian-translation.patch
>   | 1990 
>  debian/patches/Update-Swedish-translation.patch  
>   |  537 -
>  debian/patches/Update-Turkish-translation.patch  
>   |  869 -
>  debian/patches/Update-Ukrainian-translation.patch
>   |  577 -
>  debian/patches/debian/Revert-build-Port-to-gcr4.patch
>   |2 
>  
> debian/patches/overview-Don-t-claim-to-be-SHOWN-when-HIDDEN-during-start.patch
>  |   38 
>  
> debian/patches/overview-Hide-when-failing-to-take-grab-at-end-of-startup.patch
>  |   27 
>  debian/patches/series
>   |   16 
>  js/ui/dnd.js 
>   |9 
>  js/ui/status/network.js  
>   |6 
>  meson.build  
>   |2 
>  po/ab.po 
>   | 4383 
>  po/fr.po 
>   |  377 
>  
> subprojects/extensions-app/data/metainfo/org.gnome.Extensions.metainfo.xml.in 
>  |1 
>  subprojects/extensions-app/meson.build   
>   |2 
>  subprojects/extensions-app/subprojects/shew/meson.build  
>   |2 
>  subprojects/extensions-tool/meson.build  
>   |2 
>  subprojects/shew/meson.build 
>   |2 
>  30 files changed, 9414 insertions(+), 10631 deletions(-)
> 
> diff -Nru gnome-shell-43.3/debian/changelog gnome-shell-43.4/debian/changelog
> --- gnome-shell-43.3/debian/changelog 2023-03-08 11:09:54.0 +
> +++ gnome-shell-43.4/debian/changelog 2023-04-10 14:07:38.0 +0100
> @@ -1,3 +1,19 @@
> +gnome-shell (43.4-1) unstable; urgency=medium
> +
> +  * Team upload
> +  * New upstream release
> +- Fix memory leaks when the list of wireless networks is refreshed
> +  (GNOME/gnome-shell!2652)
> +- Stop tracking drag-and-dr

Processed: Re: Bug#1034167: unblock (pre-approval): mutter/43.4-1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 moreinfo confirmed
Bug #1034167 [release.debian.org] unblock (pre-approval): mutter/43.4-1
Added tag(s) confirmed and moreinfo.

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

Bug#1034167: unblock (pre-approval): mutter/43.4-1

[Sebastian Ramacher]

Control: tags -1 moreinfo confirmed

On 2023-04-10 15:29:08 +0100, Simon McVittie wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> X-Debbugs-Cc: mut...@packages.debian.org
> Control: affects -1 + src:mutter
> 
> I'd like to upload a new upstream bug fix release of mutter.

Please go ahead and remove the moreinfo tag once the version is
available in unstable.

Cheers

> 
> [ Reason ]
> Catch up with upstream 43.4 bug fix release, and cherry-pick patches
> that were already accepted for 43.5.
> 
> [ Impact ]
> Multiple bug fixes and one translation update. Also transfer various
> earlier bug fixes from Debian patches into part of the upstream source.
> 
> [ Tests ]
> I used a previous release-candidate on my Intel laptop for several days
> without noticing any regressions. The only change since that version is
> the Abkhazian translation update.
> 
> Upstream's automated tests (at build-time and during autopkgtest) have the
> same coverage and results as the version currently in bookworm.
> 
> [ Risks ]
> Key package with high visibility in our default desktop environment, but
> the changes are narrowly targeted.
> 
> [ 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
>   (filtered to exclude patch contents and translations)
> 
> [ Other info ]
> This has only been tested together with the corresponding gnome-shell
> update.
> 
> There is a remaining X11 focus issue that I'd like to be able to fix in
> bookworm (#1032388) but upstream does not have a solution for it yet,
> and the version already in testing has the same bug.
> 
> unblock mutter/43.4-1

> debdiff *.dsc | filterdiff -p1 -x'po/*.po' -x'debian/patches/*.patch'
> 
> diffstat for mutter-43.3 mutter-43.4
> 
>  NEWS 
>   |   13 
>  clutter/clutter/clutter-text.c   
>   |1 
>  cogl/cogl/cogl-framebuffer.c 
>   |2 
>  cogl/cogl/cogl-onscreen.c
>   |   18 
>  cogl/cogl/cogl-onscreen.h
>   |3 
>  debian/changelog 
>   |   23 
>  debian/patches/Revert-x11-Do-not-move-X11-input-focus-during-grabs.patch 
>   |   87 
>  
> debian/patches/Revert-x11-events-Do-not-update-focus-XWindow-during-grab.patch
>  |   36 
>  debian/patches/Update-Abkhazian-translation.patch
>   | 4262 ++
>  
> debian/patches/color-device-Don-t-close-lcms-profile-on-error-from-cd_ic.patch
>  |   52 
>  debian/patches/color-device-Make-sure-lcms_context-is-not-NULL.patch 
>   |   47 
>  debian/patches/core-Avoid-focusing-windows-on-map-during-grabs.patch 
>   |   35 
>  debian/patches/debian/Support-Dynamic-triple-double-buffering.patch  
>   |8 
>  debian/patches/debian/meson-Do-not-mark-CI-test-tools-as-required.patch  
>   |2 
>  debian/patches/meson-add-back-default_driver-option.patch
>   |2 
>  debian/patches/series
>   |   10 
>  debian/patches/wayland-Don-t-overwrite-surface-offsets.patch 
>   |   57 
>  debian/patches/wayland-Skip-subsurface-desync-if-parent-is-NULL.patch
>   |   35 
>  debian/patches/x11-Avoid-updating-focus-on-wayland-compositor.patch  
>   |   47 
>  
> debian/patches/x11-Ignore-_NET_ACTIVE_WINDOW-client-messages-while-grabb.patch
>  |   45 
>  meson.build  
>   |2 
>  po/ab.po 
>   | 4159 +
>  src/backends/meta-stage-impl.c   
>   |   14 
>  src/wayland/meta-wayland-subsurface.c
>   |6 
>  24 files changed, 8509 insertions(+), 457 deletions(-)
> 
> diff -Nru mutter-43.3/clutter/clutter/clutter-text.c 
> mutter-43.4/clutter/clutter/clutter-text.c
> --- mutter-43.3/clutter/clutter/clutter-text.c2023-02-13 
> 18:12:26.0 +
> +++ mutter-43.4/clutter/clutter/clutter-text.c2023-03-19 
> 22:26:48.0 +
> @@ -1826,7 +1826,6 @@
>  
>clutter_text_free_paint_volume (self);
>  
> -  clutter_text_set_buffer (self, NULL);
>g_free (priv->font_name);
>  
>g_clear_object (&priv->input_focus);
> diff -Nru mutter-43.3/cogl/cogl/cogl-framebuffer.c 
> mutter-43.4/cogl/cogl/cogl-framebuffer.c
> --- mutter-43.3/cogl/cogl/cogl-framebuffer.c  2023-02-13 18:12:26.0 
> +
> +++ mutter-43.4/cogl/cogl/cogl-framebuffer.c  2023-03-19 22:26:48.0 
> +
> @@ -1695,8 +1695,6 @@
>

Bug#1034046: marked as done (unblock: markdown-exec/1.4.0-1)

[Debian Bug Tracking System]

Your message dated Mon, 10 Apr 2023 16:56:06 +
with message-id 
and subject line unblock markdown-exec
has caused the Debian Bug report #1034046,
regarding unblock: markdown-exec/1.4.0-1
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.)


-- 
1034046: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034046
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: markdown-e...@packages.debian.org
Control: affects -1 + src:markdown-exec

Please unblock package markdown-exec

[ Reason ]
The package got rather small upstream modifications since 1.3.0 I'd like
to see in the bookworm release. Another reason is the mark as a core
package which requires a manually unblock by the RT.

An diff about the differences between 1.3.0 and 1.4.0 can be viewed on
the project GitHub website.

https://github.com/pawamoy/markdown-exec/compare/1.3.0...1.4.0

[ Impact ]
The user can use a improved Session handling which was added to 1.4.0.

[ Tests ]
All the tests while package build and within the autopkgtest run
succeeded. Using the newer Debian package in local projects working just
fine.

[ Risks ]
The risks are quite low as only extra functionality was added and no
changes did happen to the existing code.
No issues got reported since the upload of 1.4.0-1 almost 3 weeks ago.

[ 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


diff -Nru markdown-exec-1.3.0/CHANGELOG.md markdown-exec-1.4.0/CHANGELOG.md
--- markdown-exec-1.3.0/CHANGELOG.md2023-02-18 13:54:04.0 +0100
+++ markdown-exec-1.4.0/CHANGELOG.md2023-03-15 21:43:25.0 +0100
@@ -5,6 +5,14 @@
 and this project adheres to [Semantic 
Versioning](http://semver.org/spec/v2.0.0.html).
 
 

+## [1.4.0](https://github.com/pawamoy/markdown-exec/releases/tag/1.4.0) - 
2023-03-15
+
+[Compare with 
1.3.0](https://github.com/pawamoy/markdown-exec/compare/1.3.0...1.4.0)
+
+### Features
+
+- Sessions: persist and reuse state for Python and Pycon code blocks 
([a8fef5e](https://github.com/pawamoy/markdown-exec/commit/a8fef5e90b1d7165e16ff5afe4b84e8441503098)
 by Timothée Mazzucotelli). [Issue 
#16](https://github.com/pawamoy/markdown-exec/issues/16)
+
 ## [1.3.0](https://github.com/pawamoy/markdown-exec/releases/tag/1.3.0) - 
2023-02-18
 
 [Compare with 1.2.0](https://github.com/pawamoy/markdown-exec/compare/1.2.0...1.3.0)

diff -Nru markdown-exec-1.3.0/debian/changelog 
markdown-exec-1.4.0/debian/changelog
--- markdown-exec-1.3.0/debian/changelog2023-02-27 12:21:30.0 
+0100
+++ markdown-exec-1.4.0/debian/changelog2023-03-19 07:26:01.0 
+0100
@@ -1,3 +1,9 @@
+markdown-exec (1.4.0-1) unstable; urgency=medium
+
+  * [2aede3c] New upstream version 1.4.0
+
+ -- Carsten Schoenert   Sun, 19 Mar 2023 07:26:01 
+0100
+
 markdown-exec (1.3.0-1) unstable; urgency=medium
 
   * [8a80096] New upstream version 1.3.0

diff -Nru markdown-exec-1.3.0/docs/usage/index.md 
markdown-exec-1.4.0/docs/usage/index.md
--- markdown-exec-1.3.0/docs/usage/index.md 2023-02-18 13:54:04.0 
+0100
+++ markdown-exec-1.4.0/docs/usage/index.md 2023-03-15 21:43:25.0 
+0100
@@ -258,6 +258,27 @@
 > WARNING  -  markdown_exec: Execution of python code block 'print world' 
exited with errors
 > ```
 
+## Sessions

+
+Markdown Exec makes it possible to persist state between executed code blocks.
+To persist state and reuse it in other code blocks, give a session name to 
your blocks:
+
+md exec="1" source="material-block" title="Sessions"
+```python exec="1" session="greet"
+def greet(name):
+print(f"Hello {name}!")
+```
+
+Hello Mushu!
+
+```python exec="1" session="greet"
+greet("Ping")
+```
+
+
+WARNING: **Limitation**  
+Sessions only work with Python and Pycon syntax for now.

+
 ## Literate Markdown
 
 With this extension, it is also possible to write "literate programming" Markdown.

diff -Nru markdown-exec-1.3.0/README.md markdown-exec-1.4.0/README.md
--- markdown-exec-1.3.0/README.md   2023-02-18 13:54:04.0 +0100
+++ markdown-exec-1.4.0/README.md   2023-03-15 21:43:25.0 +0100
@@ -91,5 +91,14 @@
 
 The `exec` option will be true for every possible value except `0`, `no`, `off` and `false` (case insensitive).
 
+Below you can see an example of running a bash script that is expected to

+return a non-zero exit code:
+
+md
+```bash exec="1" source="tabbed-left" r

Bug#1034127: unblock: rhino/1.7.14-2.1

[Markus Koschany]

Am Sonntag, dem 09.04.2023 um 22:28 +0200 schrieb Paul Gevers:
> 
> [ Risks ]
> This is a new upstream release. This is not a small change. And while
> typing this unblock request, I'm getting uncomfortable and wonder if
> we want this. But as it's all prepared, let's discuss and pull Markus
> in to elaborate a bit too.

I am in favor of shipping rhino 1.7.14 in Bookworm for all the reasons Paul has
mentioned. I believe at this point in the release cycle we don't want to make
arbitrary changes but we also want to deliver the best possible software
package to our users. I'm not confident to find a different fix to address
#1026639 and the broken web application in openrefine. It clearly works with
1.7.14 but not with the current version in testing. Since I only had to patch
one reverse-dependency, the orphaned package closure-compiler, and everything
else appears to work as expected, I believe the risks are very manageable.
Worst case would be to rebuild another package. We also get the latest upstream
version and don't have to ship a six year old version again. 

Markus


signature.asc
Description: This is a digitally signed message part

Re: Streamlining d-i releases

[Joerg Jaspert]

On 16829 March 1977, Cyril Brulebois wrote:

I put SSH trigger into the room, instead of sudo. You supply the 
version
on the ssh cmdline, and if that exists in unstable, a copy-installer 
is

run with that version.

That looks very good to me, thanks!
Could even be extended to have source and target suite selectable 
too.

I think we only released the installer via tpu once, at least that I
could confirm by checking my sent box:


I prepared a little script. Now need a SSH key to allow.
Usage is simple, you MUST supply a version, you CAN supply a source and
a dest suite. Space seperated.
It checks amd64s installer in that suite, and if the version directory
exists, it calls dak copy-installer on it.

--
bye, Joerg

Bug#1034194: unblock: closure-compiler/20130227+dfsg1-13

[Markus Koschany]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: a...@debian.org

Please unblock package closure-compiler

[ Reason ]

This is related to #1034127 and the unblock request of rhino 1.7.14.
If we ship rhino 1.7.14 in Bookworm, then closure-compiler should be
unblocked too to fix a FTBFS.


[ Impact ]

If rhino is unblocked but closure-compiler is not, then the package in
testing will FTBFS.

[ Tests ]

closure-compiler builds fine now and works as expected.

[ Risks ]

closure-compiler is used to minify/optimize Javascript files and this
still seems to work.

[ 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


unblock closure-compiler/20130227+dfsg1-13
diff -Nru closure-compiler-20130227+dfsg1/debian/changelog 
closure-compiler-20130227+dfsg1/debian/changelog
--- closure-compiler-20130227+dfsg1/debian/changelog2022-11-19 
09:00:34.0 +0100
+++ closure-compiler-20130227+dfsg1/debian/changelog2023-02-14 
00:18:02.0 +0100
@@ -1,3 +1,12 @@
+closure-compiler (20130227+dfsg1-13) unstable; urgency=medium
+
+  * QA upload.
+  * Tighten dependency on librhino-java to >= 1.7.14.
+  * Fix FTBFS with rhino 1.7.14.
+  * Use canonical VCS URI.
+
+ -- Markus Koschany   Tue, 14 Feb 2023 00:18:02 +0100
+
 closure-compiler (20130227+dfsg1-12) unstable; urgency=medium
 
   * QA upload.
diff -Nru closure-compiler-20130227+dfsg1/debian/control 
closure-compiler-20130227+dfsg1/debian/control
--- closure-compiler-20130227+dfsg1/debian/control  2022-11-19 
09:00:34.0 +0100
+++ closure-compiler-20130227+dfsg1/debian/control  2023-02-14 
00:18:02.0 +0100
@@ -12,7 +12,7 @@
 libargs4j-java,
 libguava-java (>= 15.0),
 libjsr305-java,
-librhino-java (>= 1.7R4),
+librhino-java (>= 1.7.14),
 ant,
 libjarjar-java,
 protobuf-compiler,
@@ -20,8 +20,8 @@
 javahelper (>= 0.25)
 Build-Depends-Indep: default-jdk-doc, libmaven-javadoc-plugin-java
 Standards-Version: 4.1.0
-Vcs-Git: https://anonscm.debian.org/git/pkg-java/closure-compiler.git
-Vcs-Browser: https://anonscm.debian.org/cgit/pkg-java/closure-compiler.git
+Vcs-Git: https://salsa.debian.org/java-team/closure-compiler.git
+Vcs-Browser: https://salsa.debian.org/java-team/closure-compiler
 Homepage: https://developers.google.com/closure/compiler/
 
 Package: closure-compiler
diff -Nru 
closure-compiler-20130227+dfsg1/debian/patches/fix-librhino-java-FTBFS.patch 
closure-compiler-20130227+dfsg1/debian/patches/fix-librhino-java-FTBFS.patch
--- 
closure-compiler-20130227+dfsg1/debian/patches/fix-librhino-java-FTBFS.patch
1970-01-01 01:00:00.0 +0100
+++ 
closure-compiler-20130227+dfsg1/debian/patches/fix-librhino-java-FTBFS.patch
2023-02-14 00:18:02.0 +0100
@@ -0,0 +1,65 @@
+From: Markus Koschany 
+Date: Tue, 14 Feb 2023 00:06:12 +0100
+Subject: fix librhino-java FTBFS
+
+Fix FTBFS with rhino 1.7.14.
+
+Forwarded: not-needed
+---
+ src/com/google/javascript/jscomp/parsing/IRFactory.java  | 4 ++--
+ src/com/google/javascript/jscomp/parsing/TypeSafeDispatcher.java | 6 +++---
+ 2 files changed, 5 insertions(+), 5 deletions(-)
+
+diff --git a/src/com/google/javascript/jscomp/parsing/IRFactory.java 
b/src/com/google/javascript/jscomp/parsing/IRFactory.java
+index 361f31d..0e34a4d 100644
+--- a/src/com/google/javascript/jscomp/parsing/IRFactory.java
 b/src/com/google/javascript/jscomp/parsing/IRFactory.java
+@@ -65,7 +65,7 @@ import com.google.javascript.rhino.head.ast.SwitchCase;
+ import com.google.javascript.rhino.head.ast.SwitchStatement;
+ import com.google.javascript.rhino.head.ast.ThrowStatement;
+ import com.google.javascript.rhino.head.ast.TryStatement;
+-import com.google.javascript.rhino.head.ast.UnaryExpression;
++import com.google.javascript.rhino.head.ast.UpdateExpression;
+ import com.google.javascript.rhino.head.ast.VariableDeclaration;
+ import com.google.javascript.rhino.head.ast.VariableInitializer;
+ import com.google.javascript.rhino.head.ast.WhileLoop;
+@@ -1145,7 +1145,7 @@ class IRFactory {
+ }
+ 
+ @Override
+-Node processUnaryExpression(UnaryExpression exprNode) {
++Node processUpdateExpression(UpdateExpression exprNode) {
+   int type = transformTokenType(exprNode.getType());
+   Node operand = transform(exprNode.getOperand());
+   if (type == Token.NEG && operand.isNumber()) {
+diff --git a/src/com/google/javascript/jscomp/parsing/TypeSafeDispatcher.java 
b/src/com/google/javascript/jscomp/parsing/TypeSafeDispatcher.java
+index 95aaacd..fc6ace3 100644
+--- a/src/com/google/javascript/jscomp/parsing/TypeSafeDispatcher.java
 b/src/com/google/javascript/jscomp/parsing/TypeSafeDispatcher.java
+@@ -55,7 +55,7 @@ import com.google.javascript.rhino.head.ast.SwitchCase;
+ import com.google.javascript.rhino.head.ast.SwitchStatement;
+ impor

Processed: bullseye-pu: package golang-github-containers-common/0.33.4+ds1-1+deb11u1

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + src:golang-github-containers-common
Bug #1034198 [release.debian.org] bullseye-pu: package 
golang-github-containers-common/0.33.4+ds1-1+deb11u1
Added indication that 1034198 affects src:golang-github-containers-common

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

Bug#1034198: bullseye-pu: package golang-github-containers-common/0.33.4+ds1-1+deb11u1

[Reinhard Tartler]

Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: golang-github-containers-com...@packages.debian.org, 
siret...@tauware.de
Control: affects -1 + src:golang-github-containers-common

[ Reason ]

Podman relies on DBUS for correct functioning and reads the
DBUS_SESSION_BUS_ADDRESS environent variables. As it turns out, some session
managers use multiple values, separated by comma, to add additional
information, such as a "guid". Unfortunately, an oversight in the parsing code
in podman 3 fails to take multi-value items into account and leads to podman
failing to connect to the session bus.

[ Impact ]
This is highly inconvenient to the users as they would have to either use a
session manager that sets the DBUS_SESSION_BUS_ADDRESS without commas, or the
user would have to sanitize the environment manually. Only very highly skilled
users that happened to find https://github.com/containers/podman/issues/15546 or
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018816 would be able to 
figure
this out.

[ Tests ]
This was manually tested.

[ Risks ]
the risk of regression is minimal, the patch was taken from upstream, and is 
included
in later releases.

[ 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 ]
diff --git a/debian/changelog b/debian/changelog
index c23b4b9b..97d97794 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+golang-github-containers-common (0.33.4+ds1-1+deb11u2) bullseye; urgency=medium
+
+  * Fix parsing of DBUS_SESSION_BUS_ADDRESS, Closes: #1018816
+
+ -- Reinhard Tartler   Mon, 10 Apr 2023 18:19:51 -0400
+
 golang-github-containers-common (0.33.4+ds1-1+deb11u1) bullseye; urgency=medium
 
   * Backport seccomp patches from upstream to allow execution of newer
diff --git a/debian/patches/DBUS_SESSION_BUS_ADDRESS_parsing.patch 
b/debian/patches/DBUS_SESSION_BUS_ADDRESS_parsing.patch
new file mode 100644
index ..d1408a43
--- /dev/null
+++ b/debian/patches/DBUS_SESSION_BUS_ADDRESS_parsing.patch
@@ -0,0 +1,37 @@
+commit 47ea9a8cbcc35d1e758b01ae40f37fec8a2e310b
+Author: Giuseppe Scrivano 
+Date:   Mon Jul 26 15:00:25 2021 +0200
+
+config: split arguments in DBUS_SESSION_BUS_ADDRESS
+
+split the DBUS_SESSION_BUS_ADDRESS value so that something like:
+
+unix:path=/run/user/1000/bus,guid=817e9ffcfb383869ad17ea8360e7428a
+
+will ignore ",guid=817e9ffcfb383869ad17ea8360e7428a" when checking
+that the path exists.
+
+Closes: https://bugzilla.redhat.com/show_bug.cgi?id=1984531
+
+Signed-off-by: Giuseppe Scrivano 
+
+--- a/pkg/config/config.go
 b/pkg/config/config.go
+@@ -538,9 +538,14 @@
+ 
+   session := os.Getenv("DBUS_SESSION_BUS_ADDRESS")
+   hasSession := session != ""
+-  if hasSession && strings.HasPrefix(session, "unix:path=") {
+-  _, err := os.Stat(strings.TrimPrefix(session, "unix:path="))
+-  hasSession = err == nil
++  if hasSession {
++  for _, part := range strings.Split(session, ",") {
++  if strings.HasPrefix(part, "unix:path=") {
++  _, err := os.Stat(strings.TrimPrefix(part, 
"unix:path="))
++  hasSession = err == nil
++  break
++  }
++  }
+   }
+ 
+   if !hasSession {
diff --git a/debian/patches/series b/debian/patches/series
index c2a2b119..201ff0d9 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -6,3 +6,4 @@ seccomp-fixup.patch
 08bbb0dfae71da36afd3be1ca104701e6cfa4406.patch
 0f242ca74bd16175bc55013ed457c88137bec0cf.patch
 689e5b074454da5228bb05604f89b7a876baa8fe.patch
+DBUS_SESSION_BUS_ADDRESS_parsing.patch

Processed: unblock: owslib/0.27.2-3

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + src:owslib
Bug #1034206 [release.debian.org] unblock: owslib/0.27.2-3
Added indication that 1034206 affects src:owslib

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

Bug#1034206: unblock: owslib/0.27.2-3

[Bas Couwenberg]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: ows...@packages.debian.org
Control: affects -1 + src:owslib

Please unblock package owslib

It is affected by CVE-2023-27476 reported in #1034182.

[ Reason ]
Fixes security issue and missing recommended dependencies.

[ Impact ]
Unfixed security issue.

[ Tests ]
Upstream test suite.

[ Risks ]
Low, the changes are pretty straight forward.

[ 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 ]
Testing autoremoval of rdeps would remove qgis which is one of, if not the, 
most important GIS packages for users.

The package has not been unloaded to unstable yet.

unblock owslib/0.27.2-3
diff -Nru owslib-0.27.2/debian/changelog owslib-0.27.2/debian/changelog
--- owslib-0.27.2/debian/changelog  2022-11-07 19:38:12.0 +0100
+++ owslib-0.27.2/debian/changelog  2023-04-11 06:30:11.0 +0200
@@ -1,3 +1,16 @@
+owslib (0.27.2-3) unstable; urgency=medium
+
+  * Team upload.
+  * Add Rules-Requires-Root to control file.
+  * Add py3dist overrides for dataclasses.
+  * Fix 'Recommends' typo.
+  * Bump Standards-Version to 4.6.2, no changes.
+  * Add upstream patch to fix CVE-2023-27476.
+(closes: #1034182)
+  * Add python3-lxml to build dependencies.
+
+ -- Bas Couwenberg   Tue, 11 Apr 2023 06:30:11 +0200
+
 owslib (0.27.2-2) unstable; urgency=medium
 
   * Team upload.
diff -Nru owslib-0.27.2/debian/control owslib-0.27.2/debian/control
--- owslib-0.27.2/debian/control2022-10-19 11:58:01.0 +0200
+++ owslib-0.27.2/debian/control2023-04-11 06:29:20.0 +0200
@@ -8,22 +8,23 @@
dh-python,
python3-all,
python3-dateutil,
+   python3-lxml,
python3-pytest,
python3-requests,
python3-setuptools,
python3-tz,
python3-yaml
-Standards-Version: 4.6.1
+Standards-Version: 4.6.2
 Vcs-Browser: https://salsa.debian.org/debian-gis-team/owslib
 Vcs-Git: https://salsa.debian.org/debian-gis-team/owslib.git
 Homepage: https://geopython.github.com/OWSLib/
+Rules-Requires-Root: no
 
 Package: python3-owslib
 Architecture: all
-Depends: python3-lxml,
- ${python3:Depends},
+Depends: ${python3:Depends},
  ${misc:Depends}
-Recommeds: python3-pyproj
+Recommends: python3-pyproj
 Description: Client library for Open Geospatial (OGC) web services (Python 3)
  OWSLib is a Python package for client programming with Open Geospatial
  Consortium (OGC) web service (hence OWS) interface standards, and their
diff -Nru owslib-0.27.2/debian/patches/series 
owslib-0.27.2/debian/patches/series
--- owslib-0.27.2/debian/patches/series 2022-10-19 11:58:01.0 +0200
+++ owslib-0.27.2/debian/patches/series 2023-04-11 06:25:37.0 +0200
@@ -1 +1,2 @@
 yaml-safe_load.patch
+use-only-lxml-for-XML-handling.patch
diff -Nru owslib-0.27.2/debian/patches/use-only-lxml-for-XML-handling.patch 
owslib-0.27.2/debian/patches/use-only-lxml-for-XML-handling.patch
--- owslib-0.27.2/debian/patches/use-only-lxml-for-XML-handling.patch   
1970-01-01 01:00:00.0 +0100
+++ owslib-0.27.2/debian/patches/use-only-lxml-for-XML-handling.patch   
2023-04-11 06:28:15.0 +0200
@@ -0,0 +1,318 @@
+Description: use only lxml for XML handling
+ Fixes CVE-2023-27476
+Author: Tom Kralidis 
+Origin: 
https://github.com/geopython/OWSLib/commit/d91267303a695d69e73fa71efa100a035852a063
+Bug: https://github.com/geopython/OWSLib/pull/863
+Bug-Debian: https://bugs.debian.org/1034182
+
+--- a/.github/workflows/main.yml
 b/.github/workflows/main.yml
+@@ -8,9 +8,7 @@ jobs:
+ strategy:
+   matrix:
+ python-version: [3.6, 3.7, 3.8, 3.9]
+-lxml: [true, false]
+ env:
+-LXML: ${{ matrix.lxml }}
+ GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+ COVERALLS_SERVICE_NAME: github
+ steps:
+@@ -28,8 +26,6 @@ jobs:
+ pip3 install -e .
+ pip3 install -r requirements.txt
+ pip3 install -r requirements-dev.txt
+-echo "LXML => $LXML"
+-if [ "$LXML" == "true" ]; then pip install lxml; fi
+ - name: run tests ⚙️
+   run: python3 -m pytest
+ - name: run coveralls ⚙️
+--- a/docs/en/installation.rst
 b/docs/en/installation.rst
+@@ -4,7 +4,7 @@ Installation
+ Requirements
+ 
+ 
+-OWSLib requires a Python interpreter, as well as `ElementTree 
`_ or `lxml 
`_ for XML parsing.
++OWSLib requires a Python interpreter, as well as `lxml `_ 
for XML parsing.
+ 
+ Install
+ ---
+--- a/etc/debian/control
 b/etc/debian/control
+@@ -9,5 +9,5 @@ Homepage: http://geopython.github.com/OW
+ 
+ Package: python-owslib
+ Architecture: all
+-Depends: ${misc