Bug#1050207: fcitx5-pinyin-gui/experimental: undeclared file conflict with fcitx5-pinyin/unstable

[Helmut Grohne]

Package: fcitx5-pinyin-gui
Version: 5.1.0-1~exp1
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
Control: affects -1 fcitx5-pinyin

fcitx5-pinyin-gui/experimental and fcitx5-pinyin/unstable both contain
the file /usr/lib/x86_64-linux-gnu/fcitx5/qt5/libpinyindictmanager.so.
As such, dpkg could be unpacking them concurrently and cause an unpack
error. According to debian/changelog, this is a package split. Please
add the necessary Breaks and Replaces declarations.

Helmut

Processed: fcitx5-pinyin-gui/experimental: undeclared file conflict with fcitx5-pinyin/unstable

[Debian Bug Tracking System]

Processing control commands:

> affects -1 fcitx5-pinyin
Bug #1050207 [fcitx5-pinyin-gui] fcitx5-pinyin-gui/experimental: undeclared 
file conflict with fcitx5-pinyin/unstable
Added indication that 1050207 affects fcitx5-pinyin

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

Bug#1040837: rust-log situation update.

[Peter Green]

A bunch of packages just cleared new, and I made a bunch of follow up uploads.
The result is that the situation surrounding the log package has improved
a bit, but it still less than ideal.

The "kv_unstable" and "kv_unstable_sval" features are now enabled, the
"kv_unstable_serde" feature is currently disabled because it requires
the serde feature in the value-bag package, which in turn requires the
serde1 feature in the value-bag-serde1 crate, which in turn requires the
sval_serde crate which is not currently in debian.

I belive the net result of this is that

* kv-log-macro's binary dependencies are  satisfiable but it's 
build-dependencies are not.
* femme's dependencies and build-dependencies are still unsatisfiable.

Looking in the debcargo-conf repository it seems that Fabian Grünbichler
has made a start on packaging sval_serde.

Fabian: is sval-serde ready for sponsorship? if so can you add the RFS
file?

Bug#1025568: gparted: diff for NMU version 1.3.1-1.1

[Hugh McMaster]

On Tue, 22 Aug 2023 at 05:26, Phillip Susi wrote:
>
> I have an upload of 1.5 pending my sorting my gpg key out again.  Could
> you submit any changes as a PR on salsa?  I think I saw someone had done
> that for some minor issues ( was that you? ) but the CI failed.

The only change in the NMU was switching (build-)dependencies from
policykit-1 to pkexec. I can see that you've now committed that change
to the salsa repository, along with some other changes.

I didn't see a need to build-depend on libpolkit-gobject-1-dev, but
I'm not overly familiar with gparted's requirements.

Please let me know if I should submit a PR for the NMU on salsa
(noting you'd have to update the changelog to account for your recent
changes), or whether I should cancel the upload.

Processed: unmerge bugs.

[Debian Bug Tracking System]

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

> #related but not quite the same.
> unmerge 1040835
Bug #1040835 [src:rust-log] librust-async-std-dev: impossible to install: 
missing dependency librust-log-0.4+kv-unstable-dev
Bug #1040837 [src:rust-log] rust-log: breaks API without coordination
Bug #1040995 [src:rust-log] librust-kv-log-macro-dev is no longer installable
Disconnected #1040835 from all other report(s).
> unmerge 1040837
Bug #1040837 [src:rust-log] rust-log: breaks API without coordination
Bug #1040995 [src:rust-log] librust-kv-log-macro-dev is no longer installable
Disconnected #1040837 from all other report(s).
> unmerge 1040995
Bug #1040995 [src:rust-log] librust-kv-log-macro-dev is no longer installable
Ignoring request to unmerge a bug which is not merged with any others.
>
End of message, stopping processing here.

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

Processed: fixed 1042290 in 0.12.3-2

[Debian Bug Tracking System]

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

> fixed 1042290 0.12.3-2
Bug #1042290 [src:jupyter-packaging] jupyter-packaging: FTBFS: dh_auto_test: 
error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit 
code 13
The source 'jupyter-packaging' and version '0.12.3-2' do not appear to match 
any binary packages
Marked as fixed in versions jupyter-packaging/0.12.3-2.
> thanks
Stopping processing here.

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

Processed: Tag patch for DEP8 failure

[Debian Bug Tracking System]

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

> tags 1029283 patch
Bug #1029283 [src:pywebdav] pywebdav: autopkgtest regression with Python 3.11
Added tag(s) patch.
>
End of message, stopping processing here.

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

Bug#1037887: marked as done (vtk9: ftbfs with GCC-13)

[Debian Bug Tracking System]

Your message dated Mon, 21 Aug 2023 22:52:08 +
with message-id 
and subject line Bug#1037887: fixed in vtk9 9.1.0+really9.1.0+dfsg2-7
has caused the Debian Bug report #1037887,
regarding vtk9: ftbfs with GCC-13
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.)


-- 
1037887: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037887
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:vtk9
Version: 9.1.0+really9.1.0+dfsg2-5
Severity: normal
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-13

[This bug is targeted to the upcoming trixie release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The
severity of this report will be raised before the trixie release.

The full build log can be found at:
http://qa-logs.debian.net/2023/05/22/logs/vtk9_9.1.0+really9.1.0+dfsg2-5_unstable_gccexp.log
The last lines of the build log are at the end of this report.

To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-13/porting_to.html

[...]
cd /<>/debian/build/Wrapping/Java && /usr/bin/javac -classpath 
/<>/debian/build/Wrapping/Java -source 1.8 -target 1.8 
/<>/debian/build/Wrapping/Java/vtk/vtkArrayInterpolate.java -d 
CMakeFiles/vtkjava.dir
warning: [options] bootstrap class path not set in conjunction with -source 8
1 warning
[ 45%] Building Java object 
Wrapping/Java/CMakeFiles/vtkjava.dir/vtk/vtkArrayIteratorTemplate.class
cd /<>/debian/build/Wrapping/Java && /usr/bin/javac -classpath 
/<>/debian/build/Wrapping/Java -source 1.8 -target 1.8 
/<>/debian/build/Wrapping/Java/vtk/vtkArrayIteratorTemplate.java 
-d CMakeFiles/vtkjava.dir
warning: [options] bootstrap class path not set in conjunction with -source 8
warning: [options] bootstrap class path not set in conjunction with -source 8
warning: [options] bootstrap class path not set in conjunction with -source 8
warning: [options] bootstrap class path not set in conjunction with -source 8
warning: [options] bootstrap class path not set in conjunction with -source 8
1 warning
1 warning
[ 45%] Building Java object 
Wrapping/Java/CMakeFiles/vtkjava.dir/vtk/vtkArrayPrint.class
cd /<>/debian/build/Wrapping/Java && /usr/bin/javac -classpath 
/<>/debian/build/Wrapping/Java -source 1.8 -target 1.8 
/<>/debian/build/Wrapping/Java/vtk/vtkArrayPrint.java -d 
CMakeFiles/vtkjava.dir
[ 45%] Building Java object 
Wrapping/Java/CMakeFiles/vtkjava.dir/vtk/vtkDenseArray.class
cd /<>/debian/build/Wrapping/Java && /usr/bin/javac -classpath 
/<>/debian/build/Wrapping/Java -source 1.8 -target 1.8 
/<>/debian/build/Wrapping/Java/vtk/vtkDenseArray.java -d 
CMakeFiles/vtkjava.dir
1 warning
[ 45%] Building Java object 
Wrapping/Java/CMakeFiles/vtkjava.dir/vtk/vtkGenericDataArray.class
cd /<>/debian/build/Wrapping/Java && /usr/bin/javac -classpath 
/<>/debian/build/Wrapping/Java -source 1.8 -target 1.8 
/<>/debian/build/Wrapping/Java/vtk/vtkGenericDataArray.java -d 
CMakeFiles/vtkjava.dir
1 warning
warning: [options] bootstrap class path not set in conjunction with -source 8
[ 45%] Building Java object 
Wrapping/Java/CMakeFiles/vtkjava.dir/vtk/vtkMappedDataArray.class
cd /<>/debian/build/Wrapping/Java && /usr/bin/javac -classpath 
/<>/debian/build/Wrapping/Java -source 1.8 -target 1.8 
/<>/debian/build/Wrapping/Java/vtk/vtkMappedDataArray.java -d 
CMakeFiles/vtkjava.dir
1 warning
warning: [options] bootstrap class path not set in conjunction with -source 8
1 warning
1 warning
[ 45%] Building Java object 
Wrapping/Java/CMakeFiles/vtkjava.dir/vtk/vtkSOADataArrayTemplate.class
cd /<>/debian/build/Wrapping/Java && /usr/bin/javac -classpath 
/<>/debian/build/Wrapping/Java -source 1.8 -target 1.8 
/<>/debian/build/Wrapping/Java/vtk/vtkSOADataArrayTemplate.java -d 
CMakeFiles/vtkjava.dir
[ 45%] Building Java object 
Wrapping/Java/CMakeFiles/vtkjava.dir/vtk/vtkSparseArray.class
cd /<>/debian/build/Wrapping/Java && /usr/bin/javac -classpath 

Bug#1041378: marked as done (handbrake: FTBFS with ffmpeg 6.0)

[Debian Bug Tracking System]

Your message dated Mon, 21 Aug 2023 22:06:13 +
with message-id 
and subject line Bug#1041378: fixed in handbrake 1.6.1+ds1-2
has caused the Debian Bug report #1041378,
regarding handbrake: FTBFS with ffmpeg 6.0
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.)


-- 
1041378: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041378
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: handbrake
Version: 1.6.1+ds1-1
Severity: important
Tags: ftbfs sid trixie
X-Debbugs-Cc: sramac...@debian.org

handbrake FTBFS with ffpeg 6.0 (available in experimental):

/usr/lib/ccache/gcc -std=gnu99 -pipe -fmessage-length=0 -Wall 
-Wno-format-truncation -g2 -O3 -mfpmath=sse -msse2 -Wdate-time 
-D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security 
-fstack-protector-strong -D_FORTIFY_SOURCE=2 -D__LIBHB__ -DUSE_PTHREAD 
-DSYS_LINUX -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DHAVE_THREADS=1 
-DHAS_STRERROR_R -DARCH_X86_64 -I./libhb/ -I./contrib/include 
-I./contrib/include/vpl -I/usr/include/libxml2 -c ../libhb/decomb.c -o 
libhb/decomb.o
In file included from ../libhb/decavcodec.c:54:
/usr/include/x86_64-linux-gnu/libavutil/hwcontext_qsv.h:22:10: fatal error: 
mfxvideo.h: No such file or directory
   22 | #include 
  |  ^~~~
compilation terminated.
make[1]: *** [../libhb/module.rules:12: libhb/decavcodec.o] Error 1

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: handbrake
Source-Version: 1.6.1+ds1-2
Done: Sebastian Ramacher 

We believe that the bug you reported is fixed in the latest version of
handbrake, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1041...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated handbrake 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 21 Aug 2023 23:44:46 +0200
Source: handbrake
Architecture: source
Version: 1.6.1+ds1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Sebastian Ramacher 
Closes: 1041378
Changes:
 handbrake (1.6.1+ds1-2) unstable; urgency=medium
 .
   * debian/patches: Fix build with ffmpeg 6.0 (Closes: #1041378)
 Thanks to Daniel Vacek.
Checksums-Sha1:
 40f378f7dcf3d1de4ad38aec148b27caa671c760 2132 handbrake_1.6.1+ds1-2.dsc
 f52961f35da8f4245a412e1a889162f04d983dfc 23760 
handbrake_1.6.1+ds1-2.debian.tar.xz
Checksums-Sha256:
 06fd20fc4a483c1d9e810e2173ea1c1586decef80a1b4a91230f980a7dab8e66 2132 
handbrake_1.6.1+ds1-2.dsc
 15f2f7cf30ebde16ec45e3472e6fc66365a52c6cd337467ba84e9b10eb3232ae 23760 
handbrake_1.6.1+ds1-2.debian.tar.xz
Files:
 2844e39f7d1222b91d7def95722c4960 2132 graphics optional 
handbrake_1.6.1+ds1-2.dsc
 cee99c29c3250b034b0e2211603f0567 23760 graphics optional 
handbrake_1.6.1+ds1-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iHUEARYKAB0WIQRCYn6EHZln2oPh+pAhk2s2YA/NiQUCZOPcfgAKCRAhk2s2YA/N
iZbZAQDSSRb26vUi6QGDcTj/Rr7zpZq3wWwzneP/N6iZuL80YgEAuEWA5AmSAgMm
SUTDkyS+TMJlZpnLhbw3Wga6KzlMSAw=
=1U6J
-END PGP SIGNATURE End Message ---

Bug#1037887: bug#1037887: vtk9: ftbfs with GCC-13

[Aurelien Jarno]

control: tag -1 + pending

Dear maintainer,

On 2023-08-21 14:33, Aurelien Jarno wrote:
> On 2023-06-14 09:32, Matthias Klose wrote:
> > Package: src:vtk9
> > Version: 9.1.0+really9.1.0+dfsg2-5
> > Severity: normal
> > Tags: sid trixie
> > User: debian-...@lists.debian.org
> > Usertags: ftbfs-gcc-13
> > 
> > [This bug is targeted to the upcoming trixie release]
> > 
> > Please keep this issue open in the bug tracker for the package it
> > was filed for.  If a fix in another package is required, please
> > file a bug for the other package (or clone), and add a block in this
> > package. Please keep the issue open until the package can be built in
> > a follow-up test rebuild.
> > 
> > The package fails to build in a test rebuild on at least amd64 with
> > gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The
> > severity of this report will be raised before the trixie release.
> 
> The following upstream patch fixes the issue:
> https://gitlab.kitware.com/vtk/vtk/-/commit/1233ceec268d5366c66f5e79786ec784042b591b
> 

I've prepared an NMU for vtk9 (versioned as 9.1.0+really9.1.0+dfsg2-6.1)
to fix this FTBFS, you will find the corresponding diff attached. I have
uploaded it to DELAYED/2. Please feel free to tell me if I should delay
it further or cancel it.

Regards,
Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://aurel32.net
diff -Nru vtk9-9.1.0+really9.1.0+dfsg2/debian/changelog vtk9-9.1.0+really9.1.0+dfsg2/debian/changelog
--- vtk9-9.1.0+really9.1.0+dfsg2/debian/changelog	2023-06-22 05:14:50.0 +
+++ vtk9-9.1.0+really9.1.0+dfsg2/debian/changelog	2023-08-21 21:27:16.0 +
@@ -1,3 +1,12 @@
+vtk9 (9.1.0+really9.1.0+dfsg2-6.1) unstable; urgency=medium
+
+  [ Aurelien Jarno ]
+  * Non-maintainer upload.
+  * Backport patch from upstream to fix GCC 13 compatibility. (Closes:
+#1037887).
+
+ -- Aurelien Jarno   Mon, 21 Aug 2023 23:27:16 +0200
+
 vtk9 (9.1.0+really9.1.0+dfsg2-6) unstable; urgency=medium
 
   * Team upload.
diff -Nru vtk9-9.1.0+really9.1.0+dfsg2/debian/patches/130_gcc13.patch vtk9-9.1.0+really9.1.0+dfsg2/debian/patches/130_gcc13.patch
--- vtk9-9.1.0+really9.1.0+dfsg2/debian/patches/130_gcc13.patch	1970-01-01 00:00:00.0 +
+++ vtk9-9.1.0+really9.1.0+dfsg2/debian/patches/130_gcc13.patch	2023-08-21 21:12:28.0 +
@@ -0,0 +1,34 @@
+From 1233ceec268d5366c66f5e79786ec784042b591b Mon Sep 17 00:00:00 2001
+From: Laurent Rineau 
+Date: Tue, 17 Jan 2023 16:18:53 +0100
+Subject: [PATCH] Add #include  to compile with gcc13
+
+The `vtkSEPReader` was introduced by MRs !4909 (from my former
+collaborator Maxime) and !4938. Then it was highly modified by
+!7516. The later MR is the one that introduced the uses of
+`std::uint8_t` and `std::uint32_t`.
+
+Those types needs the inclusion of ``.
+---
+ IO/Image/vtkSEPReader.h | 5 +++--
+ 1 file changed, 3 insertions(+), 2 deletions(-)
+
+diff --git a/IO/Image/vtkSEPReader.h b/IO/Image/vtkSEPReader.h
+index a7d8aad1510..37d0c44d18c 100644
+--- a/IO/Image/vtkSEPReader.h
 b/IO/Image/vtkSEPReader.h
+@@ -25,8 +25,9 @@
+ #include "vtkImageAlgorithm.h"
+ #include "vtkNew.h" // for ivars
+ 
+-#include   // for std::array
+-#include  // for std::string
++#include// for std::array
++#include  // for std::uint8_t and std::uint32_t
++#include   // for std::string
+ 
+ namespace details
+ {
+-- 
+GitLab
+
diff -Nru vtk9-9.1.0+really9.1.0+dfsg2/debian/patches/series vtk9-9.1.0+really9.1.0+dfsg2/debian/patches/series
--- vtk9-9.1.0+really9.1.0+dfsg2/debian/patches/series	2023-06-22 05:12:22.0 +
+++ vtk9-9.1.0+really9.1.0+dfsg2/debian/patches/series	2023-08-21 21:25:56.0 +
@@ -12,3 +12,4 @@
 99_fix_ftbfs.patch
 110_vtk9_netcdf.patch
 120_fix_shader_crash.patch
+130_gcc13.patch


signature.asc
Description: PGP signature

Processed: bug#1037887: vtk9: ftbfs with GCC-13

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + pending
Bug #1037887 [src:vtk9] vtk9: ftbfs with GCC-13
Added tag(s) pending.

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

Bug#1032584: marked as done (xdg-desktop-portal-gnome: 44 causes long delay in portal apps for non-GNOME desktops)

[Debian Bug Tracking System]

Your message dated Mon, 21 Aug 2023 21:05:18 +
with message-id 
and subject line Bug#1032584: fixed in xdg-desktop-portal 1.17.0-1
has caused the Debian Bug report #1032584,
regarding xdg-desktop-portal-gnome: 44 causes long delay in portal apps for 
non-GNOME desktops
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.)


-- 
1032584: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032584
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xdg-desktop-portal-gnome
Version: 44~beta-1
Severity: serious
Control: forwarded -1
https://gitlab.gnome.org/GNOME/xdg-desktop-portal-gnome/-/issues/74

If xdg-desktop-portal-gnome 44~beta-1 is installed and a non-GNOME
desktop is used (like MATE), the first time trying to use something
like the file chooser in a portal-confined app will do nothing until
the systemd user service times out (90 seconds??). Afterwards, the
file chooser works normally.

In Debian (and Ubuntu), it's not expected that
xdg-desktop-portal-gnome would be installed on a system that does not
have GNOME installed (it is not a dependency of other things).
However, it is easily possible for someone to have multiple desktops
installed on their system and they would experience this bug then.

Thank you,
Jeremy Bícha
--- End Message ---
--- Begin Message ---
Source: xdg-desktop-portal
Source-Version: 1.17.0-1
Done: Jeremy Bícha 

We believe that the bug you reported is fixed in the latest version of
xdg-desktop-portal, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1032...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jeremy Bícha  (supplier of updated xdg-desktop-portal 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 21 Aug 2023 16:33:43 -0400
Source: xdg-desktop-portal
Built-For-Profiles: noudeb
Architecture: source
Version: 1.17.0-1
Distribution: experimental
Urgency: medium
Maintainer: Utopia Maintenance Team 

Changed-By: Jeremy Bícha 
Closes: 1032584
Launchpad-Bugs-Fixed: 2013116
Changes:
 xdg-desktop-portal (1.17.0-1) experimental; urgency=medium
 .
   * Team upload
   * New upstream release
 - Fixes portal delay with x-d-p-gnome 44 and non-GNOME desktops
   (LP: #2013116) (Closes: #1032584)
   * debian/control: Build-Depend on python3-dbusmock & python3-pytest
 for build tests
   * Drop all patches: applied in new release
   * Cherry-pick 3 bug fixes from upstream repo
Checksums-Sha1:
 00dda4097413f7d1a12148a7eab6848d0e5862f8 2667 xdg-desktop-portal_1.17.0-1.dsc
 d41e9054910d65127c39f6622ffce17bfa71b5b0 258252 
xdg-desktop-portal_1.17.0.orig.tar.xz
 3de84a9e9a42fe5e5fd5ad578d10ad3a51f33e62 12036 
xdg-desktop-portal_1.17.0-1.debian.tar.xz
 1ae3973295f644103ee264eeb27d3975c3e900c2 12378 
xdg-desktop-portal_1.17.0-1_source.buildinfo
Checksums-Sha256:
 df828c2479eb7d4442b4e05a1ea0689271d558b0767699c9a00196398d7ad982 2667 
xdg-desktop-portal_1.17.0-1.dsc
 cafa7c4289decf203d21829abbbefc3e968c9975664685e151db2c701b532a8b 258252 
xdg-desktop-portal_1.17.0.orig.tar.xz
 698e320df686a91343c9886719a637f642462375957288ff5804fbb07e25e062 12036 
xdg-desktop-portal_1.17.0-1.debian.tar.xz
 5631451f5c30a4ea70416b3076c4dd4de2ca8c085557ba0d66c9df19f905e21f 12378 
xdg-desktop-portal_1.17.0-1_source.buildinfo
Files:
 72738f8b405e14ad2affa2b5698c8d2c 2667 admin optional 
xdg-desktop-portal_1.17.0-1.dsc
 d71b13d62a0c709f64cd001c962c8da8 258252 admin optional 
xdg-desktop-portal_1.17.0.orig.tar.xz
 b1387c6fc19df01bdb2d577a91aae862 12036 admin optional 
xdg-desktop-portal_1.17.0-1.debian.tar.xz
 d7517e0a8b06bcefe2cac98dad1cc082 12378 admin optional 
xdg-desktop-portal_1.17.0-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmTjypIACgkQ5mx3Wuv+
bH3guxAAlctIyMaRTS/ZUvviPuHeHrpmIK+fMK3bzJjPW/NRXbEtuyxJbYk23Jdg
y+1OKxBzWZjCdQh4cLc8bCLl6RLnR7FJGbCGQg0YRIsWtL7zC2pVbPOmh9vb/4tY
9YjmeIB831SCm0jNblqHzXgdnBnNnfgmJmECINnEHv/odJi3ZG5uQzQ/Z4PGfsYI
VWv1tZRroAjAlfKrxO+OgPP8l4d995KW5b+jwwp0Z0Q/LjQVKzeB2Z4I6eCDPMb1
SVK4JkPru3vq8KElj6/oONPfbLm0MNibRo3SwYZvTRwoXfi7Ep/PfV5SL4U3PIKY
0zxlSsrKe98D/To0cBA/DLKXAhM2u8YXyGH5srLApOREHgUlebkxJmdOVpIPtZA4

Processed: fixed 1041491 in 0-1335+ds-1.1

[Debian Bug Tracking System]

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

> fixed 1041491 0-1335+ds-1.1
Bug #1041491 {Done: Bastian Germann } [src:yuzu] yuzu: FTBFS: 
Unmet build dependencies: glslang-tools:native
The source 'yuzu' and version '0-1335+ds-1.1' do not appear to match any binary 
packages
Marked as fixed in versions yuzu/0-1335+ds-1.1.
> thanks
Stopping processing here.

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

Bug#1025568: gparted: diff for NMU version 1.3.1-1.1

[Phillip Susi]

Hugh McMaster  writes:

> Control: tags 1025568 + patch
> Control: tags 1025568 + pending
>
> Dear maintainer,
>
> I've prepared an NMU for gparted (versioned as 1.3.1-1.1) and
> uploaded it to DELAYED/2. Please feel free to tell me if I
> should delay it longer.

I have an upload of 1.5 pending my sorting my gpg key out again.  Could
you submit any changes as a PR on salsa?  I think I saw someone had done
that for some minor issues ( was that you? ) but the CI failed.

Bug#1023565: dleyna adoption

[Barak A. Pearlmutter]

I've done a bit more packaging of dleyna, pushed to
https://salsa.debian.org/debian/dleyna.git branch debian/main, mainly
moving to the latest upstream 0.8.2. My plan is to adopt it by
uploading, which hopefully will result in mopidy-dleyna becoming
usable and then I'll be able to listen to DLNA music on my home
network using Debian boxes, yippee.

Any objections to my just doing an upload? Should I close 1023565 in
the changelog?

(I am, BTW, always thrilled to have co-maintainers, and even happy if
people just do 0-day NMUs or just uploading fixes or whatever.)

Cheers,

--Barak.

Bug#1041078: marked as done (mongo-cxx-driver-legacy FTBFS with googletest 1.13.0)

[Debian Bug Tracking System]

Your message dated Mon, 21 Aug 2023 19:06:23 +
with message-id 
and subject line Bug#1041078: fixed in mongo-cxx-driver-legacy 1.1.3-3.2
has caused the Debian Bug report #1041078,
regarding mongo-cxx-driver-legacy FTBFS with googletest 1.13.0
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.)


-- 
1041078: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041078
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mongo-cxx-driver-legacy
Version: 1.1.3-3.1
Severity: serious
Tags: ftbfs trixie sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/mongo-cxx-driver-legacy.html

...
In file included from /usr/include/gtest/gtest-message.h:57,
 from /usr/include/gtest/gtest-assertion-result.h:46,
 from /usr/include/gtest/gtest.h:64,
 from src/mongo/unittest/unit_test_main.cpp:16:
/usr/include/gtest/internal/gtest-port.h:270:2: error: #error C++ versions less 
than C++14 are not supported.
  270 | #error C++ versions less than C++14 are not supported.
  |  ^
...


This can be fixed by changing -std=c++11 to -std=c++14
in SConstruct
--- End Message ---
--- Begin Message ---
Source: mongo-cxx-driver-legacy
Source-Version: 1.1.3-3.2
Done: Michael R. Crusoe 

We believe that the bug you reported is fixed in the latest version of
mongo-cxx-driver-legacy, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1041...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael R. Crusoe  (supplier of updated 
mongo-cxx-driver-legacy package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 21 Aug 2023 20:39:59 +0200
Source: mongo-cxx-driver-legacy
Architecture: source
Version: 1.1.3-3.2
Distribution: unstable
Urgency: medium
Maintainer: Debian MongoDB Maintainers 
Changed-By: Michael R. Crusoe 
Closes: 1041078
Changes:
 mongo-cxx-driver-legacy (1.1.3-3.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * d/rules: specify "-std=c++14" to fix FTBFS with googletest 1.13.0.
 Closes: #1041078
Checksums-Sha1:
 ab82a25a76321298f7e2b64af8cc941c0fb080b6 2443 
mongo-cxx-driver-legacy_1.1.3-3.2.dsc
 031aed045ca11e74f9158a3f6e348c889082a627 21948 
mongo-cxx-driver-legacy_1.1.3-3.2.debian.tar.xz
 a76e9cd6783ba8cb24314b633b471c41791b7318 14808 
mongo-cxx-driver-legacy_1.1.3-3.2_source.buildinfo
Checksums-Sha256:
 6baf6e3284f95af9576af07dee321f67a0ebe20cdaf3e751f55eab4062ee3712 2443 
mongo-cxx-driver-legacy_1.1.3-3.2.dsc
 3afbc68220db594315718e87c0523084b63d49c36a70b6b2eea702d49be6a988 21948 
mongo-cxx-driver-legacy_1.1.3-3.2.debian.tar.xz
 104f9762a74f7d7c267d47c77e5a4a6830a66f99bea3da27c23db53e0905bf23 14808 
mongo-cxx-driver-legacy_1.1.3-3.2_source.buildinfo
Files:
 fed0cdf8a1636f0ccef1ba510beb9f16 2443 devel optional 
mongo-cxx-driver-legacy_1.1.3-3.2.dsc
 b46f8e0761cb662cacc8c264b7e4cab9 21948 devel optional 
mongo-cxx-driver-legacy_1.1.3-3.2.debian.tar.xz
 7948a3dfffd8e18fae9a4ecee40508ef 14808 devel optional 
mongo-cxx-driver-legacy_1.1.3-3.2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEck1gkzcRPHEFUNdHPCZ2P2xn5uIFAmTjr8sSHGNydXNvZUBk
ZWJpYW4ub3JnAAoJEDwmdj9sZ+biszkQAM32U5WJFRhUc/enMisbWWK2TrsRmTun
JL5O+/vDxA2duHGIr1/PhNkAkPstpYJkrkbbgGnfxocbGBJsXoLW5MqKnJEeWdnx
CgosZjy7zztW99qtP4fOILTxDpcvmYb74irg2qqDmNN9xwx1u6ufdXHvxt+agBcN
+H6Czvg9knzKBchKNbXrpllpidxO1IOlfGSx+7eNJ0bvL33A63oHUpztzUNAwaSA
77Sp9f7YEk1/ACie6Hnx6TNJUQpB9IANZtQ23BWLBsfp2PVwJ/pyJ7324sJyYsKx
e0Rb6FCeTkSh+6HKQBLyfYjSeniFtaa9BvDcl/2BFwdY/slCEsj0dTMWMkIOa/nI
4HdnPH/o0yxCQnJf6KJXgYvRBKIHPdmxT3N2sXf9IIQ8G+QRIAp11MkJAcFSETll
dSmh4+drxCDfIKgHpN/qnhwWdYNPKn5UvDtnBA5XkP3sBHE+eNE3bNsZ9EaRLAjO
yCU1XTEzZyGSQ6GDF4EI0vkQaRmGXezsB64hzvtxFhw07KJoMZN+DP+BqTY81Ne+
XaUQEimJAkUNyrEGEDnoU8zO55jRjvZo4JIBAsmOme7+8XYutilMaL41RPklDcVz
TYU3gtfMqBrhWqaao8rWJPAneZIECd1NN2KN4qeXU6gLckThCpouEu/JZneBCkee
OdYtljs3KZJB
=AKR6
-END PGP SIGNATURE End Message ---

Bug#1049438: closed by Debian FTP Masters (reply to Andreas Tille ) (Bug#1049438: fixed in r-cran-sp 1:2.0-0+dfsg-2)

[Paul Gevers]

Hi Andreas,

On 19-08-2023 19:39, Debian Bug Tracking System wrote:
Changes: r-cran-sp (1:2.0-0+dfsg-2) unstable; urgency=medium . * Drop 
rgdal from Test-Depends Closes: #1042426, #1049438


I fail to see how this is going to fix the r-cran-rgdal regression. 
Unless you mean to remove r-cran-rgdal from testing without causing 
regression in r-cran-sp. But than I still think that r-cran-sp doesn't 
"close" this particular bug.


Paul


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1049884: birdtray: FTBFS on armhf, armel, mipsel due to thunderbird build-dep

[Emanuele Rocca]

Hi!

On 2023-08-21 07:36, Adam Borowski wrote:
> On Mon, Aug 21, 2023 at 10:38:52AM +0200, Emanuele Rocca wrote:
> > Well FTBFS is a bug isn't it? :-)
> 
> A FTBFS on an architecture that has built before (and hasn't been RMed)
> is a bug, and one that's policied as high severity.

As far as I understand that is the case for birdtray on all 3
architectures? It used to build fine in the past, now it does not:
https://buildd.debian.org/status/fetch.php?pkg=birdtray=mipsel=1.4-2=1547097073=0

> Obviously we'd prefer thunderbird:armhf to be a thing, but unless/until it
> can be fixed, talk about thunderbird addons on armhf is quite moot.

Agreed.

> > Why does birdtray build-depend on thunderbird? It seems to build
> > perfectly fine in a clean armhf chroot without it.

> Build yes, work no. The result would be a pointless package you can't
> use; adding this (otherwise superfluous) build-dependency avoids
> having a non-installable package in the archive.

Given that we know that birdtray does not work on armhf, armel, and
mipsel, the Architecture field should reflect this fact I think. And yes
I understand that in a hypothetical scenario in which thunderbird works
on those arches, birdtray works too. That's not the present reality
though and it seems more accurate to state this fact explicitly instead
of implying it with a superfluous uninstallable build-dep.

>From 
>https://www.debian.org/doc/debian-policy/ch-controlfields.html#architecture:

| Specifying a list of architectures or architecture wildcards indicates
| that the source will build an architecture-dependent package, and will
| only work correctly on the listed or matching architectures.

Cheers,
  Emanuele

Bug#1041078: mongo-cxx-driver-legacy: diff for NMU version 1.1.3-3.2

[Michael R . Crusoe]

Control: tags 1041078 + patch


Dear maintainer,

I've prepared an NMU for mongo-cxx-driver-legacy (versioned as 1.1.3-3.2). The 
diff
is attached to this message.

Regards.

diff -Nru mongo-cxx-driver-legacy-1.1.3/debian/changelog 
mongo-cxx-driver-legacy-1.1.3/debian/changelog
--- mongo-cxx-driver-legacy-1.1.3/debian/changelog  2021-01-03 
09:48:28.0 +0100
+++ mongo-cxx-driver-legacy-1.1.3/debian/changelog  2023-08-21 
20:39:59.0 +0200
@@ -1,3 +1,11 @@
+mongo-cxx-driver-legacy (1.1.3-3.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * d/rules: specify "-std=c++14" to fix FTBFS with googletest 1.13.0.
+Closes: #1041078
+
+ -- Michael R. Crusoe   Mon, 21 Aug 2023 20:39:59 +0200
+
 mongo-cxx-driver-legacy (1.1.3-3.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru mongo-cxx-driver-legacy-1.1.3/debian/rules 
mongo-cxx-driver-legacy-1.1.3/debian/rules
--- mongo-cxx-driver-legacy-1.1.3/debian/rules  2021-01-03 09:48:28.0 
+0100
+++ mongo-cxx-driver-legacy-1.1.3/debian/rules  2023-08-21 16:49:58.0 
+0200
@@ -13,8 +13,7 @@
 --use-sasl-client\
 --sharedclient   \
 --disable-warnings-as-errors \
---c++11=on  \
-CXXFLAGS="$(CXXFLAGS) $(CPPFLAGS)"   \
+CXXFLAGS="$(CXXFLAGS) $(CPPFLAGS) -std=c++14"   \
 CFLAGS="$(CFLAGS) $(CPPFLAGS)"   \
 LINKFLAGS="$(LDFLAGS)"
 

Processed: mongo-cxx-driver-legacy: diff for NMU version 1.1.3-3.2

[Debian Bug Tracking System]

Processing control commands:

> tags 1041078 + patch
Bug #1041078 [src:mongo-cxx-driver-legacy] mongo-cxx-driver-legacy FTBFS with 
googletest 1.13.0
Added tag(s) patch.

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

Bug#1050149: marked as done (budgie-desktop: Please upload a version compatible with mutter 44 to unstable)

[Debian Bug Tracking System]

Your message dated Mon, 21 Aug 2023 18:34:02 +
with message-id 
and subject line Bug#1050149: fixed in budgie-desktop 10.8-2
has caused the Debian Bug report #1050149,
regarding budgie-desktop: Please upload a version compatible with mutter 44 to 
unstable
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.)


-- 
1050149: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050149
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: budgie-desktop
Version: 10.7.1-1
Severity: serious
Tags: trixie sid
Justification: transition #1043144

I've just uploaded mutter version 44 to experimental, starting transition
#1043144. Please upload a compatible version of budgie-desktop to
unstable, and close this bug with that upload. The newer upstream version
currently in experimental seems suitable.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Source: budgie-desktop
Source-Version: 10.8-2
Done: David Mohammed 

We believe that the bug you reported is fixed in the latest version of
budgie-desktop, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1050...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
David Mohammed  (supplier of updated budgie-desktop 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 21 Aug 2023 19:05:07 +0100
Source: budgie-desktop
Built-For-Profiles: noudeb
Architecture: source
Version: 10.8-2
Distribution: unstable
Urgency: medium
Maintainer: David Mohammed 
Changed-By: David Mohammed 
Closes: 1050149
Changes:
 budgie-desktop (10.8-2) unstable; urgency=medium
 .
   * Upload to unstable to support the GNOME 44/mutter-12 transition
 (Closes: #1050149)
   * Add missing changelog-announcement.txt entry for v10.8
Checksums-Sha1:
 4b0e74f3fb669ae79fb21e1f915d43b6319f0101 3485 budgie-desktop_10.8-2.dsc
 8954e5a7a81e0460f8f93fe0289ca9df0b6f0d8f 53312 
budgie-desktop_10.8-2.debian.tar.xz
 a2e1f4673fdc0def84c121ad12f406dc674b4f0d 24116 
budgie-desktop_10.8-2_source.buildinfo
Checksums-Sha256:
 a77d50e7e11919338c31bf686bfe946a9ed09658876b44010b306e4ba3ba3f66 3485 
budgie-desktop_10.8-2.dsc
 2201d8b268aa9d0977abebb049c5e88098b2dda1a84bfe03a32f012a06ce9b38 53312 
budgie-desktop_10.8-2.debian.tar.xz
 af655b4b6291267055495bff7c358c27375cc0acc860fddce08ded9abb205816 24116 
budgie-desktop_10.8-2_source.buildinfo
Files:
 63e7df976e4c3c901bde4966fbe54724 3485 x11 optional budgie-desktop_10.8-2.dsc
 534c6d31d5fdb0dd5f4b2fecb873a407 53312 x11 optional 
budgie-desktop_10.8-2.debian.tar.xz
 525648975aadd49d1373f51bc8008c89 24116 x11 optional 
budgie-desktop_10.8-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEHh+wAXyZiorixJimwuqoomrcWe4FAmTjqkUACgkQwuqoomrc
We6iGRAAg+pivfCyRpTA9+kbaWGUQVEB7kYc5gxVozXIHF7i0O11HQMW0l4I0HwX
aGP3EdrwXeFjGZoAAHTVaiLy/A8IOrbiEEDuC8CFGMBpI7jI3ojt2HCR6+Z+1psS
3EWwOUnF0qmneQl0q4pEtfe5iBEO+2qkO+Xyt1VOfjWlFPZehGCc54gOvSIrXzcb
TWSeu7punCeu+RwpWRCW33jZTe+PojQw1c64X4eIE3EbJ0THbwLKmnIifkAI4LfJ
/ZEaLVDaOVWlFYtjRSS64m5lFRolJ0N4TbKr4JULyil3uCIrG1jT+qpIn2k/I+jn
d0a0JV96UoGpg+z6sZ1cCCAE0dUrCJEvnqD0BXjuLrNf0dRNDnSizeFXf1kp6Jxd
V1a3pIdXJ0IFaOTrGSeEesrYn3Gz2Z+L+540AtVKH5ex3dQvpKyIImXjx5DYQsrq
gV8kNCb/jeK3M5S3FVcXi/+ArBK2CFj2g0eDzrS/8VbBbGE9QjKShNECFBJXk+r/
sfpiCZTKUNn7qZwkpSx2At8DT+otuXy/TTGRWoooBXlu5PrrdVnKfWi4o+urpL+U
YWPsgiivJ85i1E2nRC+LGOcz4p/XLrgeFob5lLsV0w7of9XnhrL0upwe8KS/z1C5
ZVTjHY4OPdCx3bXxLeSjRLXviXXy/1Nb/5/sONe8i9/bca5oPhs=
=kLkM
-END PGP SIGNATURE End Message ---

Bug#1000026: marked as done (cegui-mk2: depends on obsolete pcre3 library)

[Debian Bug Tracking System]

Your message dated Mon, 21 Aug 2023 18:19:06 +
with message-id 
and subject line Bug#126: fixed in cegui-mk2 0.8.7+git20220615-4
has caused the Debian Bug report #126,
regarding cegui-mk2: depends on obsolete pcre3 library
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.)


-- 
126: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=126
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cegui-mk2
Severity: important
User: matthew-pcre...@debian.org
Usertags: obsolete-pcre3

Dear maintainer,

Your package still depends on the old, obsolete PCRE3[0] libraries
(i.e. libpcre3-dev). This has been end of life for a while now, and
upstream do not intend to fix any further bugs in it. Accordingly, I
would like to remove the pcre3 libraries from Debian, preferably in
time for the release of Bookworm.

The newer PCRE2 library was first released in 2015, and has been in
Debian since stretch. Upstream's documentation for PCRE2 is available
here: https://pcre.org/current/doc/html/

Many large projects that use PCRE have made the switch now (e.g. git,
php); it does involve some work, but we are now at the stage where
PCRE3 should not be used, particularly if it might ever be exposed to
untrusted input.

This mass bug filing was discussed on debian-devel@ in
https://lists.debian.org/debian-devel/2021/11/msg00176.html

Regards,

Matthew [0] Historical reasons mean that old PCRE is packaged as
pcre3 in Debian 
--- End Message ---
--- Begin Message ---
Source: cegui-mk2
Source-Version: 0.8.7+git20220615-4
Done: Olek Wojnar 

We believe that the bug you reported is fixed in the latest version of
cegui-mk2, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1000...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Olek Wojnar  (supplier of updated cegui-mk2 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 21 Aug 2023 11:21:05 -0400
Source: cegui-mk2
Architecture: source
Version: 0.8.7+git20220615-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Olek Wojnar 
Closes: 126
Changes:
 cegui-mk2 (0.8.7+git20220615-4) unstable; urgency=medium
 .
   * Remove additional legacy pcre reference (Closes: #126)
Checksums-Sha1:
 11bd81225c484c08da7503c5ba11a7f62539007d 3201 cegui-mk2_0.8.7+git20220615-4.dsc
 93b196a5527b18b062a8a3add8b1f417de5dfa8d 21016 
cegui-mk2_0.8.7+git20220615-4.debian.tar.xz
 c5903fae316152d748cffa020da6c142327ce461 21357 
cegui-mk2_0.8.7+git20220615-4_amd64.buildinfo
Checksums-Sha256:
 2f763910839ebff772f248db4177c4d815a963f16b6b5c16576824972bf33ffe 3201 
cegui-mk2_0.8.7+git20220615-4.dsc
 129ea91d3aa1954303a3b6a2d07f1e266a4db340b4efd1e87aef13929656678b 21016 
cegui-mk2_0.8.7+git20220615-4.debian.tar.xz
 d3b0cd219f160131c05c3f58febd933055e86d52a0c13c74fc28006b759802ab 21357 
cegui-mk2_0.8.7+git20220615-4_amd64.buildinfo
Files:
 7202ba46f8a0c6f7aaf674451d5ba6f0 3201 libs optional 
cegui-mk2_0.8.7+git20220615-4.dsc
 ac55ef9ec1bb5998265a97282a59e133 21016 libs optional 
cegui-mk2_0.8.7+git20220615-4.debian.tar.xz
 e54ff407fdb41125a94c1aabf3eba586 21357 libs optional 
cegui-mk2_0.8.7+git20220615-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEELejiDiSiH9jtG0ynfYPUBqCdweQFAmTjppQACgkQfYPUBqCd
weSKXA//eVLompyUh4cfJUbrAmj1/6yCG5IhiCkU6ii2ItBrk3jgytCVrvd9PQM/
FwnoZh9wDy31LPiuIjITNZdtobQRDYDycEfq/tptk5VwhyH9LgPM6t3k+ocCF8oZ
HHFCno2rEculyHgd8PcJ07AsAiMVYUlMjyA5ySirj81X9nEH0yKbxYFtHPA5pRdl
WuBxn42gtXenuJdCTaVkgOV1aqhOmUfbOeaM3+CjyCd142vqkz8b4ioGdSRuDtsM
yZEHOjphtOjdEyGAguhh4zah6MG0MCln9MEYtbYxn/YsIchscUxKe/SDwFNZnzzB
92ZZCbVzPU6k+IHIBbEeQ6364Zki2x83joNksBSTiLYkEfpv9rRwAGfbeqyMsdJp
XDvX9vREDUk4tg9787LFVHUE4XNcWHrc3kSlCM4JNFWeXoGXyBhPGAblk1Mdtf3O
fLb7v5iAQ5nx1+PtfqAs5zmIm2dLgTulEcjBTtIrlGOlUxRKshIJekozGnE0MlvY
tiCTdgn5wZeedF5fiqkNwdcZD/hf2eegshTJoagcQjUg0foxsaVLNfT39F3zHiFT
BlvFyUsBh79cAM9oFXEBuF8K++mfZGEqeLXlju57FcmlYLW9aSE3dxdjbb5TS4ub
gCPJ8Vg4q5bOVjagWsHIdGvjq22Ou/3+0YwFZ5DfkoDABTuA5PE=
=mWsY
-END PGP SIGNATURE End Message ---

Bug#1049884: birdtray: FTBFS on armhf, armel, mipsel due to thunderbird build-dep

[Adam Borowski]

On Mon, Aug 21, 2023 at 10:38:52AM +0200, Emanuele Rocca wrote:
> Hi Adam,
Hi Em!

> On 2023-08-16 05:14, Adam Borowski wrote:
> > This is not a regression, thus why would it be a bug?
> 
> Well FTBFS is a bug isn't it? :-)

A FTBFS on an architecture that has built before (and hasn't been RMed)
is a bug, and one that's policied as high severity.

A FTBFS that's not a regression is a wishlist, a porting opportunity.
And here it's not even a build failure but a failure to install b-deps.

Obviously we'd prefer thunderbird:armhf to be a thing, but unless/until it
can be fixed, talk about thunderbird addons on armhf is quite moot.
And the way b-deps are written, the moment thunderbird:armhf hits incoming
its addons get enabled in wanna-build, with no human action needed.

> > There's nothing in birdtray itself that would prevent it from being built on
> > these architectures the moment problems in thunderbird are resolved
> 
> Why does birdtray build-depend on thunderbird? It seems to build
> perfectly fine in a clean armhf chroot without it.

Build yes, work no.  The result would be a pointless package you can't use;
adding this (otherwise superfluous) build-dependency avoids having a
non-installable package in the archive.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁
⢿⡄⠘⠷⠚⠋⠀ An imaginary friend squared is a real enemy.
⠈⠳⣄

Bug#1050186: [Pkg-nginx-maintainers] Bug#1050186: libnginx-mod-http-lua: depends on obsolete pcre3 library

[Thomas Ward]

Bastian:

As I understand the module, for over a year now the latest Lua module 
from OpenResty requires LuaJIT to actually compile.  See 
https://salsa.debian.org/nginx-team/libnginx-mod-http-lua/-/blob/main/debian/control#L8 
where this is in the build deps.


I have not tested removing the PCRE3 build dependency here, but because 
OpenResty has refused to change the Lua library to be any Lua support 
other than 5.1, it requires LuaJIT in order to provide 'continued 
support' for Lua 5.1 bytecode.


It is my understanding that the pcre2/pcre3 dependency may not be 
needed, but I have not deep dived into the Lua packaging recently.  I'm 
running a test build from the tagged data in Salsa locally to see if it 
builds without the pcre2/pcre3 devel libraries in build-deps.



Thomas


On 8/21/23 12:58, Bastian Germann wrote:
Thomas, can you please explain why this package still builds when 
nginx has moved to pcre2? I do not get it.

Bug#1050186: [Pkg-nginx-maintainers] Bug#1050186: libnginx-mod-http-lua: depends on obsolete pcre3 library

[Bastian Germann]

Thomas, can you please explain why this package still builds when nginx 
has moved to pcre2? I do not get it.

Bug#908295: marked as done (rhc depreated)

[Debian Bug Tracking System]

Your message dated Mon, 21 Aug 2023 16:54:41 +
with message-id 
and subject line Bug#1043568: Removed package(s) from unstable
has caused the Debian Bug report #908295,
regarding rhc depreated
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.)


-- 
908295: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908295
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: rhc
Version: 1.38.7-2
Severity: important

Hi,

It seems that rhc is deprecated for a year or two (last commit is from
Nov 2016).

Shouldn't this package be removed from the archive (or at least
buster/testing)?

Kind regards,

Laurent Bigonville

-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.18.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy
--- End Message ---
--- Begin Message ---
Version: 1.38.7-3+rm

Dear submitter,

as the package rhc has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1043568

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1026432: marked as done (libbase58: Leaf library: keep out of bookworm?)

[Debian Bug Tracking System]

Your message dated Mon, 21 Aug 2023 16:56:06 +
with message-id 
and subject line Bug#1049415: Removed package(s) from unstable
has caused the Debian Bug report #1026432,
regarding libbase58: Leaf library: keep out of bookworm?
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.)


-- 
1026432: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026432
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libbase58
Version: 0.1.4-5
Severity: serious

libbase58 appears to be a leaf library package - nothing else in Debian
debends on it. Apparently it was introduced for some other
bitcoin-related libraries, which are gone again.

I would suggest we waste no resources on this for bookworm. Interested
parties can still pick it up and maintain it properly, if they desire.

Chris
--- End Message ---
--- Begin Message ---
Version: 0.1.4-5+rm

Dear submitter,

as the package libbase58 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1049415

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1019683: marked as done (test-kitchen: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: "#".)

[Debian Bug Tracking System]

Your message dated Mon, 21 Aug 2023 16:54:09 +
with message-id 
and subject line Bug#1043565: Removed package(s) from unstable
has caused the Debian Bug report #1019683,
regarding test-kitchen: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: 
"#".
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.)


-- 
1019683: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019683
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: test-kitchen
Version: 1.23.2-6
Severity: important
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.1

Hi,

We are about to start the ruby3.1 transition in unstable. While trying to
rebuild test-kitchen with ruby3.1 enabled, the build failed.

Relevant part of the build log (hopefully):
> "#".
> 
>  58) Failure:
> Kitchen::Loader::YAML::#diagnose::for yaml files::for combined on 
> error#test_0003_uses an error hash with the exception message 
> [/<>/spec/kitchen/loader/yaml_spec.rb:761]:
> Expected /Error parsing/ to match # encoding: ASCII-8BIT
> #valid: true
> "wrong number of arguments (given 4, expected 1)".
> 
>  59) Failure:
> Kitchen::Loader::YAML::#diagnose::for yaml files#test_0004_project config 
> contains raw data [/<>/spec/kitchen/loader/yaml_spec.rb:621]:
> No visible difference in the Hash#inspect output.
> You should look at the implementation of #== on Hash or its members.
> {"from_project"=>"project", "common"=>{"p"=>"pretty"}}
> 
>  60) Failure:
> Kitchen::Loader::YAML::#diagnose::for yaml files#test_0006_local config 
> contains raw data [/<>/spec/kitchen/loader/yaml_spec.rb:633]:
> No visible difference in the Hash#inspect output.
> You should look at the implementation of #== on Hash or its members.
> {"from_local"=>"local", "common"=>{"l"=>"looky"}}
> 
>  61) Failure:
> Kitchen::Loader::YAML::#diagnose::for yaml files#test_0008_combined config 
> contains raw data [/<>/spec/kitchen/loader/yaml_spec.rb:645]:
> No visible difference in the Hash#inspect output.
> You should look at the implementation of #== on Hash or its members.
> {"from_global"=>"global", "from_project"=>"project", "from_local"=>"local", 
> "common"=>{"g"=>"goody", "p"=>"pretty", "l"=>"looky"}}
> 
>  62) Failure:
> Kitchen::Loader::YAML::#diagnose::for yaml files#test_0002_global config 
> contains raw data [/<>/spec/kitchen/loader/yaml_spec.rb:609]:
> No visible difference in the Hash#inspect output.
> You should look at the implementation of #== on Hash or its members.
> {"from_global"=>"global", "common"=>{"g"=>"goody"}}
> 
> 2210 runs, 3375 assertions, 18 failures, 44 errors, 0 skips
> rake aborted!
> Command failed with status (1): [ruby -w 
> /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/rake_test_loader.rb 
> "spec/kitchen/base64_stream_spec.rb" "spec/kitchen/cli_spec.rb" 
> "spec/kitchen/collection_spec.rb" "spec/kitchen/color_spec.rb" 
> "spec/kitchen/config_spec.rb" "spec/kitchen/configurable_spec.rb" 
> "spec/kitchen/data_munger_spec.rb" "spec/kitchen/diagnostic_spec.rb" 
> "spec/kitchen/driver/base_spec.rb" "spec/kitchen/driver/dummy_spec.rb" 
> "spec/kitchen/driver/exec_spec.rb" "spec/kitchen/driver/proxy_spec.rb" 
> "spec/kitchen/driver/ssh_base_spec.rb" "spec/kitchen/driver_spec.rb" 
> "spec/kitchen/errors_spec.rb" "spec/kitchen/instance_spec.rb" 
> "spec/kitchen/lazy_hash_spec.rb" "spec/kitchen/lifecycle_hooks_spec.rb" 
> "spec/kitchen/loader/yaml_spec.rb" "spec/kitchen/logger_spec.rb" 
> "spec/kitchen/logging_spec.rb" "spec/kitchen/login_command_spec.rb" 
> "spec/kitchen/metadata_chopper_spec.rb" "spec/kitchen/platform_spec.rb" 
> "spec/kitchen/provisioner/base_spec.rb" 
> "spec/kitchen/provisioner/chef/policyfile_spec.rb" 
> "spec/kitchen/provisioner/chef_apply_spec.rb" 
> "spec/kitchen/provisioner/chef_base_spec.rb" 
> "spec/kitchen/provisioner/chef_solo_spec.rb" 
> "spec/kitchen/provisioner/chef_zero_spec.rb" 
> "spec/kitchen/provisioner/dummy_spec.rb" 
> "spec/kitchen/provisioner/shell_spec.rb" "spec/kitchen/provisioner_spec.rb" 
> "spec/kitchen/shell_out_spec.rb" "spec/kitchen/ssh_spec.rb" 
> "spec/kitchen/state_file_spec.rb" "spec/kitchen/suite_spec.rb" 
> "spec/kitchen/transport/base_spec.rb" "spec/kitchen/transport/exec_spec.rb" 
> "spec/kitchen/transport/ssh_spec.rb" "spec/kitchen/transport/winrm_spec.rb" 
> "spec/kitchen/transport_spec.rb" "spec/kitchen/util_spec.rb" 
> "spec/kitchen/verifier/base_spec.rb" "spec/kitchen/verifier/busser_spec.rb" 
> "spec/kitchen/verifier/dummy_spec.rb" "spec/kitchen/verifier/shell_spec.rb" 
> "spec/kitchen/verifier_spec.rb" "spec/kitchen_spec.rb" 
> 

Bug#1050186: [Pkg-nginx-maintainers] Bug#1050186: libnginx-mod-http-lua: depends on obsolete pcre3 library

[Thomas Ward]

All:

See the Lua NGINX module issue here in upstream: 
https://github.com/openresty/lua-nginx-module/issues/1984


This has been an open issue since December 2021, and there has *NOT* 
been massive movement yet upstream towards PCRE2 support.


The last info on that bug from July 13th indicates that there are no 
major updates and that a MAJOR update would be needed in Open Resty 
(1.21.4 has been Open Resty's version for eons) in order for PCRE2 
support to really make it, despite nginx core moving to PCRE2.


Given this situation, and the fact this is still not being moved on 
Upstream, this may be a case where we have to decide whether to actually 
*keep* Lua module around at all, especially if we consider PCRE3 
obsolete and a security flaw.  (In which case, this should be also 
tagged as a Security bug).



Thomas



On 8/21/23 11:24, Bastian Germann wrote:

Source: libnginx-mod-http-lua
Severity: serious
Version: 1:0.10.25-1
User: matthew-pcre...@debian.org
Usertags: obsolete-pcre3

Dear maintainer,

When the pcre3 -> pcre2 mass bug was filed, this package was left out.
I am filing this (edited copy) after the fact:

Your package still depends on the old, obsolete PCRE3 libraries
(i.e. libpcre3-dev). This has been end of life for a while now, and
upstream do not intend to fix any further bugs in it. Accordingly, we
would like to remove the pcre3 libraries from Debian.

The newer PCRE2 library was first released in 2015, and has been in
Debian since stretch. Upstream's documentation for PCRE2 is available
here: https://pcre.org/current/doc/html/

Many large projects that use PCRE have made the switch now (e.g. git,
php); it does involve some work, but we are now at the stage where
PCRE3 should not be used, particularly if it might ever be exposed to
untrusted input.

This mass bug filing was discussed on debian-devel@ in
https://lists.debian.org/debian-devel/2021/11/msg00176.html

Thanks,
Bastian

___
Pkg-nginx-maintainers mailing list
pkg-nginx-maintain...@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-nginx-maintainers 

Bug#996227: marked as done (ruby-ferret: FTBFS with ruby3.0: index.h:595:25: error: width of ‘is_compressed’ exceeds its type)

[Debian Bug Tracking System]

Your message dated Mon, 21 Aug 2023 16:48:28 +
with message-id 
and subject line Bug#1043537: Removed package(s) from unstable
has caused the Debian Bug report #996227,
regarding ruby-ferret: FTBFS with ruby3.0: index.h:595:25: error: width of 
‘is_compressed’ exceeds its type
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.)


-- 
996227: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996227
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-ferret
Version: 0.11.8.7-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.0

Hi,

We are about to enable building against ruby3.0 on unstable. During a test
rebuild, ruby-ferret was found to fail to build in that situation.

To reproduce this locally, you need to install ruby-all-dev from experimental
on an unstable system or build chroot.

Relevant part (hopefully):
> gcc -fdebug-prefix-map=/<>=. -I. 
> -I/usr/include/x86_64-linux-gnu/ruby-3.0.0 
> -I/usr/include/ruby-3.0.0/ruby/backward -I/usr/include/ruby-3.0.0 -I. 
> -Wdate-time -D_FORTIFY_SOURCE=2   -fPIC -g -O2 
> -ffile-prefix-map=/build/ruby3.0-2KsnwC/ruby3.0-3.0.2=. 
> -fstack-protector-strong -Wformat -Werror=format-security -fPIC -Wall 
> -D_FILE_OFFSET_BITS=64 -D_XOPEN_SOURCE=500  -o compound_io.o -c compound_io.c
> In file included from compound_io.c:1:
> index.h:595:25: error: width of ‘is_compressed’ exceeds its type
>   595 | boolis_compressed : 2; /* set to 2 after all data 
> is loaded */
>   | ^
> make[1]: *** [Makefile:245: compound_io.o] Error 1


The full build log is available at
https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-ferret/ruby-ferret_0.11.8.7-2+rebuild1633379746_amd64.build.txt


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 0.11.8.7-2+rm

Dear submitter,

as the package ruby-ferret has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1043537

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1027345: marked as done (ruby-terrapin: FTBFS: ERROR: Test "ruby3.1" failed: ArgumentError:)

[Debian Bug Tracking System]

Your message dated Mon, 21 Aug 2023 16:30:53 +
with message-id 
and subject line Bug#1043491: Removed package(s) from unstable
has caused the Debian Bug report #1027345,
regarding ruby-terrapin: FTBFS: ERROR: Test "ruby3.1" failed: ArgumentError:
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.)


-- 
1027345: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027345
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-terrapin
Version: 0.6.0-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221230 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
>   ArgumentError:
> wrong number of arguments (given 4, expected 3)
>   # 
> /usr/share/rubygems-integration/all/gems/mocha-1.16.1/lib/mocha/mock.rb:319:in
>  `new'
>   # 
> /usr/share/rubygems-integration/all/gems/mocha-1.16.1/lib/mocha/mock.rb:319:in
>  `handle_method_call'
>   # 
> /usr/share/rubygems-integration/all/gems/mocha-1.16.1/lib/mocha/stubbed_method.rb:60:in
>  `block in define_new_method'
>   # ./lib/terrapin/command_line.rb:42:in `block in best_runner'
>   # ./lib/terrapin/command_line.rb:41:in `each'
>   # ./lib/terrapin/command_line.rb:41:in `detect'
>   # ./lib/terrapin/command_line.rb:41:in `best_runner'
>   # ./lib/terrapin/command_line.rb:23:in `runner'
>   # ./lib/terrapin/command_line.rb:55:in `initialize'
>   # ./spec/terrapin/runners_spec.rb:24:in `new'
>   # ./spec/terrapin/runners_spec.rb:24:in `block (2 levels) in  (required)>'
> 
> Deprecation Warnings:
> 
> Using `should` from rspec-expectations' old `:should` syntax without 
> explicitly enabling the syntax is deprecated. Use the new `:expect` syntax or 
> explicitly enable `:should` with `config.expect_with(:rspec) { |c| c.syntax = 
> :should }` instead. Called from 
> /<>/spec/terrapin/command_line/runners/backticks_runner_spec.rb:19:in
>  `block (2 levels) in '.
> 
> 
> If you need more of the backtrace for any of these deprecations to
> identify where to make the necessary changes, you can configure
> `config.raise_errors_for_deprecations!`, and it will turn the
> deprecation warnings into errors, giving you the full backtrace.
> 
> 1 deprecation warning total
> 
> Finished in 1.42 seconds (files took 0.40114 seconds to load)
> 67 examples, 30 failures
> 
> Failed examples:
> 
> rspec ./spec/terrapin/command_line_spec.rb:14 # Terrapin::CommandLine 
> specifies the $PATH where the command can be found on unix
> rspec ./spec/terrapin/command_line_spec.rb:20 # Terrapin::CommandLine 
> specifies the %PATH% where the command can be found on windows
> rspec ./spec/terrapin/command_line_spec.rb:27 # Terrapin::CommandLine 
> specifies more than one path where the command can be found
> rspec ./spec/terrapin/command_line_spec.rb:57 # Terrapin::CommandLine can 
> interpolate quoted variables into the command line's parameters
> rspec ./spec/terrapin/command_line_spec.rb:66 # Terrapin::CommandLine does 
> not over-interpolate in a command line
> rspec ./spec/terrapin/command_line_spec.rb:75 # Terrapin::CommandLine 
> interpolates when running a command
> rspec ./spec/terrapin/command_line_spec.rb:80 # Terrapin::CommandLine 
> interpolates any Array arguments when running a command
> rspec ./spec/terrapin/command_line_spec.rb:85 # Terrapin::CommandLine quotes 
> command line options differently if we're on windows
> rspec ./spec/terrapin/command_line_spec.rb:94 # Terrapin::CommandLine can 
> quote and interpolate dangerous variables
> rspec ./spec/terrapin/command_line_spec.rb:102 # Terrapin::CommandLine cannot 
> recursively introduce a place where user-supplied commands can run
> rspec ./spec/terrapin/command_line_spec.rb:107 # Terrapin::CommandLine can 
> quote and interpolate dangerous variables even on windows
> rspec ./spec/terrapin/command_line_spec.rb:116 # Terrapin::CommandLine quotes 
> blank values into the command line's parameters
> rspec ./spec/terrapin/command_line_spec.rb:129 # Terrapin::CommandLine 
> handles symbols in user supplied values
> rspec ./spec/terrapin/command_line_spec.rb:135 # Terrapin::CommandLine can 
> redirect stderr to the bit bucket if requested
> rspec ./spec/terrapin/command_line_spec.rb:143 # Terrapin::CommandLine can 
> redirect stderr to the bit bucket on windows
> rspec ./spec/terrapin/command_line_spec.rb:163 # Terrapin::CommandLine 
> colorizes the output to a tty
> rspec ./spec/terrapin/command_line_spec.rb:169 # 

Bug#1027341: marked as done (ruby-bourne: FTBFS: ERROR: Test "ruby3.1" failed: Error: test_should_stub_two_different_class_methods_again(StubbaExampleTest): ArgumentError: wrong number of arguments (g

[Debian Bug Tracking System]

Your message dated Mon, 21 Aug 2023 16:31:55 +
with message-id 
and subject line Bug#1043492: Removed package(s) from unstable
has caused the Debian Bug report #1027341,
regarding ruby-bourne: FTBFS: ERROR: Test "ruby3.1" failed: Error: 
test_should_stub_two_different_class_methods_again(StubbaExampleTest): 
ArgumentError: wrong number of arguments (given 4, expected 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.)


-- 
1027341: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027341
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-bourne
Version: 1.6.0-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221230 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> Error: test_should_stub_two_different_class_methods_again(StubbaExampleTest): 
> ArgumentError: wrong number of arguments (given 4, expected 3)
> /<>/lib/bourne/invocation.rb:8:in `initialize'
> /usr/share/rubygems-integration/all/gems/mocha-1.16.1/lib/mocha/mock.rb:319:in
>  `new'
> /usr/share/rubygems-integration/all/gems/mocha-1.16.1/lib/mocha/mock.rb:319:in
>  `handle_method_call'
> /usr/share/rubygems-integration/all/gems/mocha-1.16.1/lib/mocha/stubbed_method.rb:60:in
>  `block in define_new_method'
> /<>/test/acceptance/stubba_example_test.rb:90:in 
> `should_stub_two_different_class_methods'
> /<>/test/acceptance/stubba_example_test.rb:69:in 
> `test_should_stub_two_different_class_methods_again'
>  66:   end
>  67: 
>  68:   def test_should_stub_two_different_class_methods_again
>   => 69: should_stub_two_different_class_methods
>  70:   end
>  71: 
>  72:   private
> ===
> : (0.001355)
> 
> Finished in 0.452356416 seconds.
> ---
> 137 tests, 79 assertions, 3 failures, 81 errors, 0 pendings, 0 omissions, 0 
> notifications
> 38.6861% passed
> ---
> 302.86 tests/s, 174.64 assertions/s
> rake aborted!
> Command failed with status (1): [ruby -w -I"test" 
> /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/rake_test_loader.rb 
> "test/acceptance/mocha_example_test.rb" "test/acceptance/spy_test.rb" 
> "test/acceptance/stubba_example_test.rb" "test/unit/assert_received_test.rb" 
> "test/unit/have_received_test.rb" "test/unit/invocation_test.rb" 
> "test/unit/mock_test.rb" "test/unit/mockery_test.rb" "test/test_helper.rb" 
> "test/test_runner.rb"  -v]
> 
> Tasks: TOP => default
> (See full trace by running task with --trace)
> ERROR: Test "ruby3.1" failed: 


The full build log is available from:
http://qa-logs.debian.net/2022/12/30/ruby-bourne_1.6.0-3_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221230;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221230=lu...@debian.org=1=1=1=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Version: 1.6.0-3+rm

Dear submitter,

as the package ruby-bourne has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1043492

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1030765: marked as done (pipewire-media-session is dead upstream)

[Debian Bug Tracking System]

Your message dated Mon, 21 Aug 2023 16:21:37 +
with message-id 
and subject line Bug#1043405: Removed package(s) from unstable
has caused the Debian Bug report #1030765,
regarding pipewire-media-session is dead upstream
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.)


-- 
1030765: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030765
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pipewire-media-session
Severity: important
Tags: trixie

pipewire-media-session is dead upstream and must not be shipped with Trixie.
Wireplumber must be used instead.

https://gitlab.freedesktop.org/pipewire/media-session/-/commit/80dae7e2
--- End Message ---
--- Begin Message ---
Version: 0.4.2-3+rm

Dear submitter,

as the package pipewire-media-session has just been removed from the Debian 
archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1043405

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#997148: marked as done (f-irc: FTBFS: loop.c:1031:25: error: format not a string literal and no format arguments [-Werror=format-security])

[Debian Bug Tracking System]

Your message dated Mon, 21 Aug 2023 16:19:03 +
with message-id 
and subject line Bug#1043380: Removed package(s) from unstable
has caused the Debian Bug report #997148,
regarding f-irc: FTBFS: loop.c:1031:25: error: format not a string literal and 
no format arguments [-Werror=format-security]
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.)


-- 
997148: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997148
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: f-irc
Version: 1.36-1.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> cc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -Wformat -Werror=format-security -DVERSION=\"1.36\" 
> -DSYSCONFDIR=\"/usr/local/etc\" -O3 -g -Wall -pedantic -Wdate-time 
> -D_FORTIFY_SOURCE=2  -c -o loop.o loop.c
> loop.c: In function ‘update_channel_border’:
> loop.c:1031:25: error: format not a string literal and no format arguments 
> [-Werror=format-security]
>  1031 | mvwprintw(chat_window_border -> win, kr_y, 
> kr_x, tooltip);
>   | ^
> loop.c: In function ‘log_channel’:
> loop.c:424:9: warning: ignoring return value of ‘asprintf’ declared with 
> attribute ‘warn_unused_result’ [-Wunused-result]
>   424 | asprintf(, "%s(%s) %s: %s\n", pc -> channel_name, ps 
> -> description, str_or_nothing(user), string);
>   | 
> ^~~
> loop.c:471:17: warning: ignoring return value of ‘asprintf’ declared with 
> attribute ‘warn_unused_result’ [-Wunused-result]
>   471 | asprintf(, "%02d:%02d:%02d]", ptm -> tm_hour, ptm 
> -> tm_min, ptm -> tm_sec);
>   | 
> ^~
> loop.c:479:25: warning: ignoring return value of ‘asprintf’ declared with 
> attribute ‘warn_unused_result’ [-Wunused-result]
>   479 | asprintf(_buffer, "%s %s", ts, temp);
>   | ^~~~
> loop.c:481:25: warning: ignoring return value of ‘asprintf’ declared with 
> attribute ‘warn_unused_result’ [-Wunused-result]
>   481 | asprintf(_buffer, "%s %s: %s", ts, user, 
> temp);
>   | 
> ^~
> loop.c:487:25: warning: ignoring return value of ‘asprintf’ declared with 
> attribute ‘warn_unused_result’ [-Wunused-result]
>   487 | asprintf(_buffer, "%s %s: %s", ts, 
> nick_only, temp);
>   | 
> ^~~
> loop.c:496:17: warning: ignoring return value of ‘asprintf’ declared with 
> attribute ‘warn_unused_result’ [-Wunused-result]
>   496 | asprintf(_buffer, "%s > %s", ts, string);
>   | ^~~~
> loop.c:528:25: warning: ignoring return value of ‘asprintf’ declared with 
> attribute ‘warn_unused_result’ [-Wunused-result]
>   528 | asprintf(_str_buffer, "last message: %s 
> (%ld), current time: %s (%ld)", time_str1, last_entry, time_str2, rnow);
>   | 
> ^~~~
> loop.c: In function ‘update_statusline’:
> loop.c:590:15: warning: ignoring return value of ‘vasprintf’ declared with 
> attribute ‘warn_unused_result’ [-Wunused-result]
>   590 | (void)vasprintf(_buffer, fmt, ap);
>   |   ^~~
> loop.c: In function ‘log_to_file’:
> loop.c:1054:17: warning: ignoring return value of ‘asprintf’ declared with 
> attribute ‘warn_unused_result’ [-Wunused-result]
>  1054 | asprintf(, "%s/%s/", log_dir, ps -> server_host);
>   | ^
> loop.c:1055:17: warning: ignoring return value of ‘asprintf’ declared with 
> attribute ‘warn_unused_result’ [-Wunused-result]
>  1055 | asprintf(, "%s/%s/%s.log", log_dir, ps -> 
> server_host, pc -> channel_name);
>   | 
> ^~~
> cc1: some warnings being treated as errors
> make[1]: *** [: loop.o] Error 1


The 

Bug#1000132: marked as done (doscan: depends on obsolete pcre3 library)

[Debian Bug Tracking System]

Your message dated Mon, 21 Aug 2023 16:19:41 +
with message-id 
and subject line Bug#1043382: Removed package(s) from unstable
has caused the Debian Bug report #1000132,
regarding doscan: depends on obsolete pcre3 library
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.)


-- 
1000132: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000132
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: doscan
Severity: important
User: matthew-pcre...@debian.org
Usertags: obsolete-pcre3

Dear maintainer,

Your package still depends on the old, obsolete PCRE3[0] libraries
(i.e. libpcre3-dev). This has been end of life for a while now, and
upstream do not intend to fix any further bugs in it. Accordingly, I
would like to remove the pcre3 libraries from Debian, preferably in
time for the release of Bookworm.

The newer PCRE2 library was first released in 2015, and has been in
Debian since stretch. Upstream's documentation for PCRE2 is available
here: https://pcre.org/current/doc/html/

Many large projects that use PCRE have made the switch now (e.g. git,
php); it does involve some work, but we are now at the stage where
PCRE3 should not be used, particularly if it might ever be exposed to
untrusted input.

This mass bug filing was discussed on debian-devel@ in
https://lists.debian.org/debian-devel/2021/11/msg00176.html

Regards,

Matthew [0] Historical reasons mean that old PCRE is packaged as
pcre3 in Debian 
--- End Message ---
--- Begin Message ---
Version: 0.3.3-1.2+rm

Dear submitter,

as the package doscan has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1043382

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1039022: marked as done (obsoleted fork, can be replaced by golang-github-creack-pty-dev)

[Debian Bug Tracking System]

Your message dated Mon, 21 Aug 2023 16:14:27 +
with message-id 
and subject line Bug#1043371: Removed package(s) from unstable
has caused the Debian Bug report #1039022,
regarding obsoleted fork, can be replaced by golang-github-creack-pty-dev
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.)


-- 
1039022: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039022
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-elisescu-pty
Version: 1.1.9-1
Severity: serious
X-Debbugs-Cc: z...@debian.org

This fork only contains one change:

https://github.com/elisescu/pty/commit/b36ef7cd (Add a Setsize function to set
the size of the terminal)

This is already merged in https://github.com/creack/pty/commit/f4f01f59

Reverse dependencies should migrate to golang-github-creack-pty-dev.


-- System Information:
Debian Release: 12.0
  APT prefers testing
  APT policy: (500, 'testing'), (100, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-9-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Version: 1.1.9-1+rm

Dear submitter,

as the package golang-github-elisescu-pty has just been removed from the Debian 
archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1043371

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1014169: marked as done (rinutils FTBFS)

[Debian Bug Tracking System]

Your message dated Mon, 21 Aug 2023 16:13:49 +
with message-id 
and subject line Bug#1043359: Removed package(s) from unstable
has caused the Debian Bug report #1014169,
regarding rinutils FTBFS
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.)


-- 
1014169: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014169
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: rinutils
Version: 0.10.0-1
Severity: high

Dear Maintainer,

rinutils is currently FTBFS due to some missing cmake modules:

```
CMake Warning at cmake/shlomif_common_bootstrap.cmake:7 (MESSAGE):
  Could not find Shlomif_Common.cmake - you can find it here:
  https://github.com/shlomif/shlomif-cmake-modules ; trying to download it
  for you.
Call Stack (most recent call first):
  CMakeLists.txt:4 (INCLUDE)

CMake Error at CMakeLists.txt:5 (SHLOMIF_COMMON_SETUP):
  Unknown CMake command "SHLOMIF_COMMON_SETUP"
```
These cmake modules do not appear to be packaged anywhere in Debian. Since
the builds are done without internet access, the build will continue to
fail until these modules are packaged and added as a dependency to rinutils.

Thank you,

William
--- End Message ---
--- Begin Message ---
Version: 0.10.0-1+rm

Dear submitter,

as the package rinutils has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1043359

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1049432: marked as done (netplan.io: autopkgtest failures with NetworkManager 1.44.0)

[Debian Bug Tracking System]

Your message dated Mon, 21 Aug 2023 15:50:12 +
with message-id 
and subject line Bug#1049432: fixed in netplan.io 0.107-2
has caused the Debian Bug report #1049432,
regarding netplan.io: autopkgtest failures with NetworkManager 1.44.0
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.)


-- 
1049432: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1049432
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: netplan.io
Version: 0.106.1-8
Severity: serious
Tags: upstream
Affects: src:network-manager
Control: forwarded -1 https://launchpad.net/bugs/1987001

netplan.io's autopkgtests fail with NetworkManager 1.44.0. This is
blocking NetworkManager 1.44.0 from migrating from Unstable to
Testing.

This happens in both Debian and Ubuntu 23.10

https://autopkgtest.ubuntu.com/packages/netplan.io/mantic/amd64
https://ci.debian.net/packages/n/netplan.io/testing/amd64

autopkgtest log excerpt


3624s ==
3624s FAIL: test_vrf_basic (__main__.TestNetworkManager.test_vrf_basic)
3624s --
3624s Traceback (most recent call last):
3624s File 
"/tmp/autopkgtest-lxc.tzad0mtq/downtmp/build.vhF/src/tests/integration/routing.py",
line 316, in test_vrf_basic
3624s self.assertIn('10.10.0.0/16 via 10.10.10.1 dev vrf0', out)
3624s AssertionError: '10.10.0.0/16 via 10.10.10.1 dev vrf0' not found
in '10.10.10.0/24 dev eth42 proto kernel scope link src 10.10.10.22
metric 100 \nlocal 10.10.10.22 dev eth42 proto kernel scope host src
10.10.10.22 \nbroadcast 10.10.10.255 dev eth42 proto kernel scope link
src 10.10.10.22 \n11.11.11.0/24 via 10.10.10.2 dev eth42 proto static
metric 100 \n'
3624s
3624s --
3624s Ran 28 tests in 757.513s
3624s
3624s FAILED (failures=1, skipped=3)
3624s autopkgtest [15:11:48]: test routing: ---]
3624s autopkgtest [15:11:48]: test routing: - - - - - - - - - -
results - - - - - - - - - -
3624s routing FAIL non-zero exit status 1


Thank you,
Jeremy Bícha
--- End Message ---
--- Begin Message ---
Source: netplan.io
Source-Version: 0.107-2
Done: Lukas Märdian 

We believe that the bug you reported is fixed in the latest version of
netplan.io, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1049...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Lukas Märdian  (supplier of updated netplan.io package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 21 Aug 2023 17:25:33 +0200
Source: netplan.io
Built-For-Profiles: noudeb
Architecture: source
Version: 0.107-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Netplan Maintainers 
Changed-By: Lukas Märdian 
Closes: 1046524 1049432
Launchpad-Bugs-Fixed: 2031421 2031962
Changes:
 netplan.io (0.107-2) unstable; urgency=medium
 .
   * d/control: Add runtime dependency on python3-cffi-backend (LP: #2031962)
   * d/t/control: Enable dummy & veth integration tests
   * Fix NetworkManager 1.44 VRF compatibility (LP: #2031421, Closes: #1049432)
 d/p/0001-parse-allow-COMMON_LINK_HANDLERS-for-VRFs-LP-2031421.patch
   * d/rules: Fix dh_clean to cleanup after tests (Closes: #1046524)
   * Fix OVS tests by avoiding NetworkManager taking control
 d/p/0002-test-ovs-Avoid-NetworkManager-taking-contol-breaking.patch
   * d/t/control: Don't hide real OVS test failures as skippable
Checksums-Sha1:
 ed2c24472edd48575d5198acf877e53eed6b4924 2837 netplan.io_0.107-2.dsc
 b05bba40d726ec8c8eff72dd1168962b9acc00bc 14312 netplan.io_0.107-2.debian.tar.xz
 65359a313c9153d0641fa108da982d2979c9212a 12647 
netplan.io_0.107-2_source.buildinfo
Checksums-Sha256:
 e54d4ea1a37c8958f238d97d97cc091b4033be49d44ea1996b1524d144e859ed 2837 
netplan.io_0.107-2.dsc
 802555969296932dbd97530fc12dac6dbc35ecaf0a0974bf868aeb6fbbd497c6 14312 
netplan.io_0.107-2.debian.tar.xz
 6c9bca47cd98bfabd4e84d62ac8496c16d08d9d62a5f7b396fda6cd88655edb8 12647 
netplan.io_0.107-2_source.buildinfo
Files:
 b839aaa99cbfdfb256f7c0e25979e4b2 2837 net optional netplan.io_0.107-2.dsc
 

Processed (with 1 error): raise severity as in the other pcre3 bugs

[Debian Bug Tracking System]

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

> severity 891197 serious
Bug #891197 [ncbi-blast+] Please switch to pcre2
Severity set to 'serious' from 'normal'
> user 891197 matthew-pcre...@debian.org
Unknown command or malformed arguments to command.
> usertags 891197 obsolete-pcre3
User is b...@debian.org
There were no usertags set.
Usertags are now: obsolete-pcre3.
>
End of message, stopping processing here.

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

Bug#1050187: mvdsv: depends on obsolete pcre3 library

[Bastian Germann]

Source: mvdsv
Severity: serious
Version: 0.35-6
User: matthew-pcre...@debian.org
Usertags: obsolete-pcre3

Dear maintainer,

When the pcre3 -> pcre2 mass bug was filed, this package was left out.
I am filing this (edited copy) after the fact:

Your package still depends on the old, obsolete PCRE3 libraries
(i.e. libpcre3-dev). This has been end of life for a while now, and
upstream do not intend to fix any further bugs in it. Accordingly, we
would like to remove the pcre3 libraries from Debian.

The newer PCRE2 library was first released in 2015, and has been in
Debian since stretch. Upstream's documentation for PCRE2 is available
here: https://pcre.org/current/doc/html/

Many large projects that use PCRE have made the switch now (e.g. git,
php); it does involve some work, but we are now at the stage where
PCRE3 should not be used, particularly if it might ever be exposed to
untrusted input.

This mass bug filing was discussed on debian-devel@ in
https://lists.debian.org/debian-devel/2021/11/msg00176.html

Thanks,
Bastian

Bug#1050186: libnginx-mod-http-lua: depends on obsolete pcre3 library

[Bastian Germann]

Source: libnginx-mod-http-lua
Severity: serious
Version: 1:0.10.25-1
User: matthew-pcre...@debian.org
Usertags: obsolete-pcre3

Dear maintainer,

When the pcre3 -> pcre2 mass bug was filed, this package was left out.
I am filing this (edited copy) after the fact:

Your package still depends on the old, obsolete PCRE3 libraries
(i.e. libpcre3-dev). This has been end of life for a while now, and
upstream do not intend to fix any further bugs in it. Accordingly, we
would like to remove the pcre3 libraries from Debian.

The newer PCRE2 library was first released in 2015, and has been in
Debian since stretch. Upstream's documentation for PCRE2 is available
here: https://pcre.org/current/doc/html/

Many large projects that use PCRE have made the switch now (e.g. git,
php); it does involve some work, but we are now at the stage where
PCRE3 should not be used, particularly if it might ever be exposed to
untrusted input.

This mass bug filing was discussed on debian-devel@ in
https://lists.debian.org/debian-devel/2021/11/msg00176.html

Thanks,
Bastian

Bug#1050185: rust-derive-builder-core - depends on old version of darling.

[Peter Green]

Package: rust-derive-builder-core
Version: 0.12.0-1
Severity: serious

Recently a new version of the darling crates was uploaded,
(Alexander Kajil prepared the uploads, Sylvestre uploaded
darling-core and I uploaded the rest of the darling crates).

Most of the reverse dependencies either already had uploads
prepared, or I was able to prepare uploads. Unfortunately
things were not so fortunate with derive-builder-core.

Bumping darling generally also implies bumping syn,
otherwise one runs into issues. We currently have both
versions 1.x and 2.x of syn in Debian, so this is not
an issue in itself but it means more API changes.

I tried to patch derive-builder-core for the new syn,
but I failed. Looking upstream it seems they are also
currently stuck.

https://github.com/colin-kiegel/rust-derive-builder/issues/292

Bug#1050184: libgetdata: depends on obsolete pcre3 library

[Bastian Germann]

Source: libgetdata
Severity: serious
Version: 0.11.0-6
User: matthew-pcre...@debian.org
Usertags: obsolete-pcre3

Dear maintainer,

When the pcre3 -> pcre2 mass bug was filed, this package was left out.
I am filing this (edited copy) after the fact:

Your package still depends on the old, obsolete PCRE3 libraries
(i.e. libpcre3-dev). This has been end of life for a while now, and
upstream do not intend to fix any further bugs in it. Accordingly, we
would like to remove the pcre3 libraries from Debian.

The newer PCRE2 library was first released in 2015, and has been in
Debian since stretch. Upstream's documentation for PCRE2 is available
here: https://pcre.org/current/doc/html/

Many large projects that use PCRE have made the switch now (e.g. git,
php); it does involve some work, but we are now at the stage where
PCRE3 should not be used, particularly if it might ever be exposed to
untrusted input.

This mass bug filing was discussed on debian-devel@ in
https://lists.debian.org/debian-devel/2021/11/msg00176.html

Thanks,
Bastian

Bug#1050183: httest: depends on obsolete pcre3 library

[Bastian Germann]

Source: httest
Severity: serious
Version: 2.4.23-1.4
User: matthew-pcre...@debian.org
Usertags: obsolete-pcre3

Dear maintainer,

When the pcre3 -> pcre2 mass bug was filed, this package was left out.
I am filing this (edited copy) after the fact:

Your package still depends on the old, obsolete PCRE3 libraries
(i.e. libpcre3-dev). This has been end of life for a while now, and
upstream do not intend to fix any further bugs in it. Accordingly, we
would like to remove the pcre3 libraries from Debian.

The newer PCRE2 library was first released in 2015, and has been in
Debian since stretch. Upstream's documentation for PCRE2 is available
here: https://pcre.org/current/doc/html/

Many large projects that use PCRE have made the switch now (e.g. git,
php); it does involve some work, but we are now at the stage where
PCRE3 should not be used, particularly if it might ever be exposed to
untrusted input.

This mass bug filing was discussed on debian-devel@ in
https://lists.debian.org/debian-devel/2021/11/msg00176.html

Thanks,
Bastian

Processed: unarchive

[Debian Bug Tracking System]

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

> unarchive 126
Bug #126 {Done: Olek Wojnar } [src:cegui-mk2] cegui-mk2: 
depends on obsolete pcre3 library
Unarchived Bug 126
> severity 126 serious
Bug #126 {Done: Olek Wojnar } [src:cegui-mk2] cegui-mk2: 
depends on obsolete pcre3 library
Severity set to 'serious' from 'important'
> reassign 126 libcegui-mk2-dev
Bug #126 {Done: Olek Wojnar } [src:cegui-mk2] cegui-mk2: 
depends on obsolete pcre3 library
Bug reassigned from package 'src:cegui-mk2' to 'libcegui-mk2-dev'.
Ignoring request to alter found versions of bug #126 to the same values 
previously set
No longer marked as fixed in versions cegui-mk2/0.8.7+git20220615-2.
> notfixed 126 cegui-mk2/0.8.7+git20220615-2
Bug #126 {Done: Olek Wojnar } [libcegui-mk2-dev] 
cegui-mk2: depends on obsolete pcre3 library
Ignoring request to alter fixed versions of bug #126 to the same values 
previously set
> found 126 0.8.7+git20220615-2
Bug #126 {Done: Olek Wojnar } [libcegui-mk2-dev] 
cegui-mk2: depends on obsolete pcre3 library
Marked as found in versions cegui-mk2/0.8.7+git20220615-2 and reopened.
> thanks
Stopping processing here.

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

Bug#1050182: python3-sage: depends on obsolete pcre3 library

[Bastian Germann]

Package: python3-sage
Severity: serious
Version: 9.5-6
User: matthew-pcre...@debian.org
Usertags: obsolete-pcre3

Dear maintainer,

When the pcre3 -> pcre2 mass bug was filed, python-pcre had not yet been
in the archive. I am filing this (edited copy) after the fact:

Your package still depends on the old, obsolete PCRE3 libraries
(i.e. libpcre3-dev). This has been end of life for a while now, and
upstream do not intend to fix any further bugs in it. Accordingly, we
would like to remove the pcre3 libraries from Debian.

The newer PCRE2 library was first released in 2015, and has been in
Debian since stretch. Upstream's documentation for PCRE2 is available
here: https://pcre.org/current/doc/html/

Many large projects that use PCRE have made the switch now (e.g. git,
php); it does involve some work, but we are now at the stage where
PCRE3 should not be used, particularly if it might ever be exposed to
untrusted input.

This mass bug filing was discussed on debian-devel@ in
https://lists.debian.org/debian-devel/2021/11/msg00176.html

Thanks,
Bastian

Bug#1050181: rtpengine: depends on obsolete pcre3 library

[Bastian Germann]

Source: rtpengine
Severity: serious
Version: 10.5.5.2-1
User: matthew-pcre...@debian.org
Usertags: obsolete-pcre3

Dear maintainer,

When the pcre3 -> pcre2 mass bug was filed, python-pcre had not yet been
in the archive. I am filing this (edited copy) after the fact:

Your package still depends on the old, obsolete PCRE3 libraries
(i.e. libpcre3-dev). This has been end of life for a while now, and
upstream do not intend to fix any further bugs in it. Accordingly, we
would like to remove the pcre3 libraries from Debian.

The newer PCRE2 library was first released in 2015, and has been in
Debian since stretch. Upstream's documentation for PCRE2 is available
here: https://pcre.org/current/doc/html/

Many large projects that use PCRE have made the switch now (e.g. git,
php); it does involve some work, but we are now at the stage where
PCRE3 should not be used, particularly if it might ever be exposed to
untrusted input.

This mass bug filing was discussed on debian-devel@ in
https://lists.debian.org/debian-devel/2021/11/msg00176.html

Thanks,
Bastian

Processed: Bug#1025568 marked as pending in gparted

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1025568 [src:gparted] gparted: dependency on transitional policykit-1 
package
Ignoring request to alter tags of bug #1025568 to the same tags previously set

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

Bug#1025568: marked as pending in gparted

[Phillip Susi]

Control: tag -1 pending

Hello,

Bug #1025568 in gparted reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/debian/gparted/-/commit/f64c86a0329ee2a0f8834058c32405832243bfdd


Switch dependency from transitional polkit-1 to pkexec package (Closes: 
#1025568)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1025568

Bug#1050175: Missing symbol when importing torch

[M. Zhou]

Sorry for the inconvenience. This is a temporary break due to the
undergoing pytorch 2.0.1 upgrade work.

On Mon, 2023-08-21 at 14:52 +0200, Mattias Ellert wrote:
> Package: python3-torch
> Version: 1.13.1+dfsg-4
> Severity: serious
> 
> Importing torch results in failure due to missing symbols:
> 
> $ python3
> Python 3.11.4 (main, Jun  7 2023, 10:13:09) [GCC 12.2.0] on linux
> Type "help", "copyright", "credits" or "license" for more
> information.
> > > > import torch
> Traceback (most recent call last):
>   File "", line 1, in 
>   File "/usr/lib/python3/dist-packages/torch/__init__.py", line 218,
> in
> 
>     from torch._C import *  # noqa: F403
>     ^^
> ImportError: /lib/x86_64-linux-gnu/libtorch_cpu.so.1.13: undefined
> symbol: _ZN4onnx7checker11check_modelERKNS_10ModelProtoE
> > > > 
> 
> pytorch requires rebuild due to updated libonnx1:
> 
> $ c++filt _ZN4onnx7checker11check_modelERKNS_10ModelProtoE
> onnx::checker::check_model(onnx::ModelProto const&)
> 
> $ dpkg-query --show python3-torch libonnx1
> libonnx1:amd641.13.1-1
> python3-torch 1.13.1+dfsg-4
> 
>   Mattias
> 

Bug#1050175: Missing symbol when importing torch

[Mattias Ellert]

Package: python3-torch
Version: 1.13.1+dfsg-4
Severity: serious

Importing torch results in failure due to missing symbols:

$ python3
Python 3.11.4 (main, Jun  7 2023, 10:13:09) [GCC 12.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import torch
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/torch/__init__.py", line 218, in

from torch._C import *  # noqa: F403
^^
ImportError: /lib/x86_64-linux-gnu/libtorch_cpu.so.1.13: undefined
symbol: _ZN4onnx7checker11check_modelERKNS_10ModelProtoE
>>> 

pytorch requires rebuild due to updated libonnx1:

$ c++filt _ZN4onnx7checker11check_modelERKNS_10ModelProtoE
onnx::checker::check_model(onnx::ModelProto const&)

$ dpkg-query --show python3-torch libonnx1
libonnx1:amd64  1.13.1-1
python3-torch   1.13.1+dfsg-4

Mattias



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

Bug#1026558: marked as done (python-cookies: FTBFS: make[1]: *** [debian/rules:12: override_dh_auto_clean] Error 25)

[Debian Bug Tracking System]

Your message dated Mon, 21 Aug 2023 12:49:18 +
with message-id 
and subject line Bug#1026558: fixed in python-cookies 2.2.1-5
has caused the Debian Bug report #1026558,
regarding python-cookies: FTBFS: make[1]: *** [debian/rules:12: 
override_dh_auto_clean] Error 25
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.)


-- 
1026558: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026558
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-cookies
Version: 2.2.1-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> rm -rf cookies.egg-info __pycache__ .cache
> dh_auto_clean
>   pybuild --clean -i python{version} -p "3.11 3.10"
> I: pybuild base:240: python3.11 setup.py clean 
> Traceback (most recent call last):
>   File "/<>/setup.py", line 2, in 
> from cookies import __version__
>   File "/<>/cookies.py", line 110, in 
> class Definitions(object):
>   File "/<>/cookies.py", line 312, in Definitions
> ATTR_RE = re.compile(ATTR)
>   
>   File "/usr/lib/python3.11/re/__init__.py", line 227, in compile
> return _compile(pattern, flags)
>
>   File "/usr/lib/python3.11/re/__init__.py", line 294, in _compile
> p = _compiler.compile(pattern, flags)
> ^
>   File "/usr/lib/python3.11/re/_compiler.py", line 743, in compile
> p = _parser.parse(p, flags)
> ^^^
>   File "/usr/lib/python3.11/re/_parser.py", line 980, in parse
> p = _parse_sub(source, state, flags & SRE_FLAG_VERBOSE, 0)
> ^^
>   File "/usr/lib/python3.11/re/_parser.py", line 455, in _parse_sub
> itemsappend(_parse(source, state, verbose, nested + 1,
> ^^
>   File "/usr/lib/python3.11/re/_parser.py", line 863, in _parse
> p = _parse_sub(source, state, sub_verbose, nested + 1)
> ^^
>   File "/usr/lib/python3.11/re/_parser.py", line 455, in _parse_sub
> itemsappend(_parse(source, state, verbose, nested + 1,
> ^^
>   File "/usr/lib/python3.11/re/_parser.py", line 863, in _parse
> p = _parse_sub(source, state, sub_verbose, nested + 1)
> ^^
>   File "/usr/lib/python3.11/re/_parser.py", line 455, in _parse_sub
> itemsappend(_parse(source, state, verbose, nested + 1,
> ^^
>   File "/usr/lib/python3.11/re/_parser.py", line 841, in _parse
> raise source.error('global flags not at the start '
> re.error: global flags not at the start of the expression at position 399 
> (line 7, column 33)
> E: pybuild pybuild:386: clean: plugin distutils failed with: exit code=1: 
> python3.11 setup.py clean 
> dh_auto_clean: error: pybuild --clean -i python{version} -p "3.11 3.10" 
> returned exit code 13
> make[1]: *** [debian/rules:12: override_dh_auto_clean] Error 25


The full build log is available from:
http://qa-logs.debian.net/2022/12/20/python-cookies_2.2.1-4_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221220;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221220=lu...@debian.org=1=1=1=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: python-cookies
Source-Version: 2.2.1-5
Done: Bastian Germann 

We believe that the bug you reported is fixed in the latest version of
python-cookies, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 

Bug#1041249: cpp-httplib: FTBFS on s390x: ../test/test.cc:5462: Failure

[Andrea Pappacoda]

Hi Emanuele, thank you for the info. I'm aware of that, and even reported the 
issue upstream[1], but the maintainer isn't interested in fixing it.

I would debug and maybe fix the issue myself, but as a DM I don't have easy 
access to porter boxes and honestly the long wait and inability to get access 
to all of them is quite demotivating. I have asked for an s390x porter box a 
couple of days ago and still didn't get access to it, and I'd now have to 
re-ask for and armhf one, and wait again... I'll eventually fix this, but I 
cannot now for factors outside of my control.

If you could please help debug the issue on the architectures you have access 
to I'd be very grateful. If you don't have time, no worries, I fully understand 
it, but please be patient :)

Thanks!

[1]: https://github.com/yhirose/cpp-httplib/issues/1199

Il 21 agosto 2023 10:53:23 CEST, Emanuele Rocca  ha scritto:
>I've bumped into a very similar failure on armhf too, so the problem is
>probably not s390x-specific.
>
>Note that the build succeeded on a second try.

Processed: bug 1037887 is forwarded to https://gitlab.kitware.com/vtk/vtk/-/commit/1233ceec268d5366c66f5e79786ec784042b591b

[Debian Bug Tracking System]

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

> forwarded 1037887 
> https://gitlab.kitware.com/vtk/vtk/-/commit/1233ceec268d5366c66f5e79786ec784042b591b
Bug #1037887 [src:vtk9] vtk9: ftbfs with GCC-13
Set Bug forwarded-to-address to 
'https://gitlab.kitware.com/vtk/vtk/-/commit/1233ceec268d5366c66f5e79786ec784042b591b'.
> thanks
Stopping processing here.

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

Bug#1041580: marked as done (gnome-shell-extension-tiling-assistant: needs update for GNOME Shell 44)

[Debian Bug Tracking System]

Your message dated Mon, 21 Aug 2023 12:34:06 +
with message-id 
and subject line Bug#1041580: fixed in gnome-shell-extension-tiling-assistant 
41-2
has caused the Debian Bug report #1041580,
regarding gnome-shell-extension-tiling-assistant: needs update for GNOME Shell 
44
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.)


-- 
1041580: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041580
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-shell-extension-tiling-assistant
Version: 39-1
Severity: important
Tags: trixie sid
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-44
Control: fixed -1 39-3

The version of gnome-shell-extension-tiling-assistant in unstable is
not marked as compatible with GNOME Shell 44, but the version in
experimental is.

If the version in experimental is suitable to be uploaded to unstable
even while the GNOME Shell in unstable is still version 43, please do
so, and close this bug in that upload. If not, the version currently
in testing/unstable can stay until we are ready to go ahead with GNOME
Shell 44.

If not updated, it will have to be removed from testing for the GNOME
Shell 44 transition (I don't know when that will be). This bug will be
raised to serious severity when the transition is ready.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Source: gnome-shell-extension-tiling-assistant
Source-Version: 41-2
Done: Fabio Augusto De Muzio Tobich 

We believe that the bug you reported is fixed in the latest version of
gnome-shell-extension-tiling-assistant, which is due to be installed in the 
Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1041...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Fabio Augusto De Muzio Tobich  (supplier of updated 
gnome-shell-extension-tiling-assistant package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 21 Aug 2023 09:07:26 -0300
Source: gnome-shell-extension-tiling-assistant
Architecture: source
Version: 41-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Fabio Augusto De Muzio Tobich 
Closes: 1041580
Changes:
 gnome-shell-extension-tiling-assistant (41-2) unstable; urgency=medium
 .
   * Upload to unstable. (Closes: #1041580)
   * debian/control.in:
   - Bumped Standards-Version to 4.6.2.
   - Adjusted gnome-shell versions in Depends field in package stanza to
 support GNOME 43 to 45.
   * debian/copyright: updated packaging data.
   * debian/patches/series: commented out GNOME 45 support patches for now.
Checksums-Sha1:
 e77f7b070a827bae0cddb97d53022fb9bb745220 2378 
gnome-shell-extension-tiling-assistant_41-2.dsc
 471f5a51664aefa09630606825d3bc44b5631299 25652 
gnome-shell-extension-tiling-assistant_41-2.debian.tar.xz
 eb9604706fabc1aca5632cc69c9657b72b2d89bb 6297 
gnome-shell-extension-tiling-assistant_41-2_source.buildinfo
Checksums-Sha256:
 b50acf5b775df9bc88a1d50b711f14497b699f20c9fed0025dbb309cfb0552c1 2378 
gnome-shell-extension-tiling-assistant_41-2.dsc
 0debed23968d35aeecd8927c467fb0e3dc50a45200c1ae587cd05d8f20bff26c 25652 
gnome-shell-extension-tiling-assistant_41-2.debian.tar.xz
 19a6329ab3554e4ac4a98df3987939f7e0cc7b0330ce217b261208403c512137 6297 
gnome-shell-extension-tiling-assistant_41-2_source.buildinfo
Files:
 86e12bd96355d5a70b37a88fd4118aa3 2378 gnome optional 
gnome-shell-extension-tiling-assistant_41-2.dsc
 3b40b3597f2c34865269a53f5b693d80 25652 gnome optional 
gnome-shell-extension-tiling-assistant_41-2.debian.tar.xz
 de3aac372e014e961aa27e1e4969d1aa 6297 gnome optional 
gnome-shell-extension-tiling-assistant_41-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEElzBAZuWu+sImg9A9T7O00372Oy4FAmTjVNcACgkQT7O00372
Oy7jug/9GcTP1B49WcvunZ+Gprh7sDFaYrDT7L2OXNH8tJBN1aKhYrGjVa7NKIPU
7laZS8bWGo0NynDyqME0xB67oR8XZa0WGOKCh3kzQcnCl+Ds9kcbfwdBGJKqSIx3
V9EJ2jKv/5fqPfGHNzCes5MGfHGgN5LtzeYkTRd0Vpg6QS6BKD1+7Ma72AqpNXCp
Px+xydDrSedz6O8sYfuhwMwBzZrHCdIvLVa/7c26RWUbFTqPqBAS5p+fvSmVZldg
ybND4ODKf1SLP/3R1e6SoaPZsTkA5EFGAzszwQPp3sx4n4tO4jmz//HtfJe80i3u
zEpwU6mp3yvkUMsu8iCxyEqIhsopCrOQ0kPRH2TU5MBphd4B26d3ZSMhflW53RY5

Processed: Re: vtk9: ftbfs with GCC-13

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + upstream
Bug #1037887 [src:vtk9] vtk9: ftbfs with GCC-13
Added tag(s) upstream.
> tag -1 + fixed-upstream
Bug #1037887 [src:vtk9] vtk9: ftbfs with GCC-13
Added tag(s) fixed-upstream.
> tag -1 + patch
Bug #1037887 [src:vtk9] vtk9: ftbfs with GCC-13
Added tag(s) patch.

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

Bug#1037887: vtk9: ftbfs with GCC-13

[Aurelien Jarno]

control: tag -1 + upstream
control: tag -1 + fixed-upstream
control: tag -1 + patch

Hi,

On 2023-06-14 09:32, Matthias Klose wrote:
> Package: src:vtk9
> Version: 9.1.0+really9.1.0+dfsg2-5
> Severity: normal
> Tags: sid trixie
> User: debian-...@lists.debian.org
> Usertags: ftbfs-gcc-13
> 
> [This bug is targeted to the upcoming trixie release]
> 
> Please keep this issue open in the bug tracker for the package it
> was filed for.  If a fix in another package is required, please
> file a bug for the other package (or clone), and add a block in this
> package. Please keep the issue open until the package can be built in
> a follow-up test rebuild.
> 
> The package fails to build in a test rebuild on at least amd64 with
> gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The
> severity of this report will be raised before the trixie release.

The following upstream patch fixes the issue:
https://gitlab.kitware.com/vtk/vtk/-/commit/1233ceec268d5366c66f5e79786ec784042b591b

Regards
Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://aurel32.net

Bug#1041580: marked as done (gnome-shell-extension-tiling-assistant: needs update for GNOME Shell 44)

[Debian Bug Tracking System]

Your message dated Mon, 21 Aug 2023 14:28:28 +0200
with message-id 
and subject line Bug #1041580
has caused the Debian Bug report #1041580,
regarding gnome-shell-extension-tiling-assistant: needs update for GNOME Shell 
44
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.)


-- 
1041580: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041580
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-shell-extension-tiling-assistant
Version: 39-1
Severity: important
Tags: trixie sid
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-44
Control: fixed -1 39-3

The version of gnome-shell-extension-tiling-assistant in unstable is
not marked as compatible with GNOME Shell 44, but the version in
experimental is.

If the version in experimental is suitable to be uploaded to unstable
even while the GNOME Shell in unstable is still version 43, please do
so, and close this bug in that upload. If not, the version currently
in testing/unstable can stay until we are ready to go ahead with GNOME
Shell 44.

If not updated, it will have to be removed from testing for the GNOME
Shell 44 transition (I don't know when that will be). This bug will be
raised to serious severity when the transition is ready.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
41 has been uploaded

--- End Message ---

Bug#877122: marked as done (libengine-pkcs11-openssl1.1: Engine is installed into wrong directory on i386)

[Debian Bug Tracking System]

Your message dated Mon, 21 Aug 2023 14:19:12 +0200
with message-id 
and subject line Re: libengine-pkcs11-openssl1.1: Engine is installed into 
wrong directory on i386
has caused the Debian Bug report #877122,
regarding libengine-pkcs11-openssl1.1: Engine is installed into wrong directory 
on i386
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.)


-- 
877122: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877122
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libengine-pkcs11-openssl1.1
Version: 0.4.4-4
Severity: normal

Dear Maintainer,

pkcs11.so is installed to /usr/lib/i686-linux-gnu/engines-1.1/, which is
wrong for i386 architecture and openssl fails to load the engine:

# openssl engine pkcs11 -t
3073050944:error:25066067:DSO support routines:dlfcn_load:could not load the 
shared 
library:../crypto/dso/dso_dlfcn.c:113:filename(/usr/lib/i386-linux-gnu/engines-1.1/pkcs11.so):
 /usr/lib/i386-linux-gnu/engines-1.1/pkcs11.so: cannot open shared object file: 
No such file or directory
3073050944:error:25070067:DSO support routines:DSO_load:could not load the 
shared library:../crypto/dso/dso_lib.c:161:
3073050944:error:260B6084:engine routines:dynamic_load:dso not 
found:../crypto/engine/eng_dyn.c:414:
3073050944:error:2606A074:engine routines:ENGINE_by_id:no such 
engine:../crypto/engine/eng_list.c:339:id=pkcs11


Manually symlinking the file works, though:

root:/usr/lib/i386-linux-gnu/engines-1.1# LC_ALL=C ls -l
total 32
-rw-r--r-- 1 root root  5384 Jun  5 12:40 capi.so
-rw-r--r-- 1 root root 22056 Jun  5 12:40 padlock.so
root:/usr/lib/i386-linux-gnu/engines-1.1# ln -sf 
/usr/lib/i686-linux-gnu/engines-1.1/pkcs11.so 
root:/usr/lib/i386-linux-gnu/engines-1.1# LC_ALL=C ls -l
total 32
-rw-r--r-- 1 root root  5384 Jun  5 12:40 capi.so
-rw-r--r-- 1 root root 22056 Jun  5 12:40 padlock.so
lrwxrwxrwx 1 root root45 Sep 29 00:28 pkcs11.so -> 
/usr/lib/i686-linux-gnu/engines-1.1/pkcs11.so
root:/usr/lib/i386-linux-gnu/engines-1.1# openssl engine pkcs11 -t
(pkcs11) pkcs11 engine
 [ available ]


I guess his happens because DEB_HOST_GNU_TYPE is used in debian/rules
instead of DEB_HOST_MULTIARCH.


-- System Information:
Debian Release: 9.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 4.9.0-3-686-pae (SMP w/2 CPU cores)
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to ru_RU.UTF-8), LANGUAGE=ru_RU.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to ru_RU.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libengine-pkcs11-openssl1.1 depends on:
ii  libc6  2.24-11+deb9u1
ii  libssl1.1  1.1.0f-3
ii  p11-kit0.23.3-2

libengine-pkcs11-openssl1.1 recommends no packages.

libengine-pkcs11-openssl1.1 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---

Closing old bug.--- End Message ---

Processed: Re: cloud-initramfs-growroot: missing dependencies in initramfs

[Debian Bug Tracking System]

Processing control commands:

> severity -1 grave
Bug #1037914 [cloud-initramfs-growroot] cloud-initramfs-growroot: missing 
dependencies in initramfs
Severity set to 'grave' from 'important'

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

Bug#1025568: gparted: diff for NMU version 1.3.1-1.1

[Hugh McMaster]

Control: tags 1025568 + patch
Control: tags 1025568 + pending

Dear maintainer,

I've prepared an NMU for gparted (versioned as 1.3.1-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards,

Hugh
diff -Nru gparted-1.3.1/debian/changelog gparted-1.3.1/debian/changelog
--- gparted-1.3.1/debian/changelog	2022-01-13 03:23:19.0 +1100
+++ gparted-1.3.1/debian/changelog	2023-08-21 21:32:58.0 +1000
@@ -1,3 +1,10 @@
+gparted (1.3.1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/control: Replace policykit-1 with pkexec (Closes: #1025568).
+
+ -- Hugh McMaster   Mon, 21 Aug 2023 21:32:58 +1000
+
 gparted (1.3.1-1) unstable; urgency=medium
 
   * New upstream version 1.3.1
diff -Nru gparted-1.3.1/debian/control gparted-1.3.1/debian/control
--- gparted-1.3.1/debian/control	2022-01-13 02:52:18.0 +1100
+++ gparted-1.3.1/debian/control	2023-08-21 21:31:52.0 +1000
@@ -7,8 +7,8 @@
  libgtkmm-3.0-dev,
  libparted-dev (>= 2.22),
  parted,
+ pkexec,
  pkg-config,
- policykit-1,
  uuid-dev,
  yelp-tools
 Standards-Version: 4.5.0
@@ -19,7 +19,7 @@
 Package: gparted
 Architecture: any
 Depends: ${misc:Depends}, ${shlibs:Depends},
- gparted-common (= ${source:Version}), policykit-1
+ gparted-common (= ${source:Version}), pkexec
 Breaks: udisks2 (<< 2.1.5), gparted-common (= 1.0.0-0.1)
 Replaces: gparted-common (= 1.0.0-0.1)
 Suggests:

Processed: gparted: diff for NMU version 1.3.1-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 1025568 + patch
Bug #1025568 [src:gparted] gparted: dependency on transitional policykit-1 
package
Added tag(s) patch.
> tags 1025568 + pending
Bug #1025568 [src:gparted] gparted: dependency on transitional policykit-1 
package
Added tag(s) pending.

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

Bug#999936: uwsgi: depends on obsolete pcre3 library

[Mathias Behrle]

Hi all,

friendly ping ;)

> Seems like uwsgi-plugin-{luajit,mongo,php} need a binNMU or an upload
> due to uwsgi ABI change.

Any news on this? Quite a number of packages depending on uwsgi will fall out
of testing shortly, because uwsgi doesn't migrate to testing (which is a major
annoyance).

Thanks for looking into this!

Cheers,
Mathias

-- 

Mathias Behrle
PGP/GnuPG key availabable from any keyserver, ID: 0xD6D09BE48405BBF6
AC29 7E5C 46B9 D0B6 1C71  7681 D6D0 9BE4 8405 BBF6

Bug#1043058: marked as done (libesmtp6: missing Breaks: libesmtp5)

[Debian Bug Tracking System]

Your message dated Mon, 21 Aug 2023 10:49:51 +
with message-id 
and subject line Bug#1043058: fixed in libesmtp 1.1.0-3.1
has caused the Debian Bug report #1043058,
regarding libesmtp6: missing Breaks: libesmtp5
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.)


-- 
1043058: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043058
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libesmtp6
Version: 1.1.0-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts replaces-without-breaks

Hi,

during a test with piuparts and DOSE tools I noticed your package causes
removal of files that also belong to another package.
This is caused by using Replaces without corresponding Breaks.

This leaves a crippled libesmtp5 package installed on certain upgrade
paths.

This is a serious bug violating policy 7.6, see
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces
and also see the footnote that describes this incorrect behavior:
https://www.debian.org/doc/debian-policy/ch-relationships.html#id13

The libesmtp6 package has the following relationships with libesmtp5:

  Conflicts: n/a
  Breaks:n/a
  Replaces:  libesmtp5

>From the attached log (scroll to the bottom...):

3m29.5s ERROR: FAIL: debsums reports modifications inside the chroot:
  debsums: missing file /usr/lib/esmtp/sasl-cram-md5.so (from libesmtp5 package)
  debsums: missing file /usr/lib/esmtp/sasl-login.so (from libesmtp5 package)
  debsums: missing file /usr/lib/esmtp/sasl-plain.so (from libesmtp5 package)

This wasn't noticed as long as libesmtp6 still provided the files, but
that no longer seems to be the case.


cheers,

Andreas


libesmtp-dev_1.1.0-3+b1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: libesmtp
Source-Version: 1.1.0-3.1
Done: Salvatore Bonaccorso 

We believe that the bug you reported is fixed in the latest version of
libesmtp, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1043...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated libesmtp package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 19 Aug 2023 12:04:32 +0200
Source: libesmtp
Architecture: source
Version: 1.1.0-3.1
Distribution: unstable
Urgency: medium
Maintainer: Jeremy T. Bouse 
Changed-By: Salvatore Bonaccorso 
Closes: 1043058
Changes:
 libesmtp (1.1.0-3.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * libesmtp6: Add versioned Replaces and Breaks against
 libesmtp5 (<< 1.0.6-1~) (Closes: #1043058)
Checksums-Sha1: 
 9c2c76c6032698e88aec7ee72fee4e6755f3e876 2100 libesmtp_1.1.0-3.1.dsc
 35ce434cd7bf269143118ead4d70e18213312d4f 4920 libesmtp_1.1.0-3.1.debian.tar.xz
Checksums-Sha256: 
 1a54dded96b3cf809d075ab0869bb349adfa59db11f03a70915c8d26f69e1b76 2100 
libesmtp_1.1.0-3.1.dsc
 2aa53e59271970f0ad97dee72dd51fab28b2a49e4b3ceb58513c297c0109dbc9 4920 
libesmtp_1.1.0-3.1.debian.tar.xz
Files: 
 0d5c23728c2185b34de5ecb51934c98f 2100 libs optional libesmtp_1.1.0-3.1.dsc
 e134e04406f8fa73cb60fa7d3eaf9eeb 4920 libs optional 
libesmtp_1.1.0-3.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmTglHNfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89EPgYP/0XQtyrPvJ5a2gy0QMO0RqDpEC9tkMwG
pzwpDIp1hycXxBX7BAym/tE9rhOIBVoFKj4wrL+dqkzhoQvgQWnPZMPqort+jz14
ndAvaCV8aGmYPzSNuu/04onVTFunpEz5erIhe9moVX7+IkDCB6yKzmnETpNKJKDr
QEa+zpt8CkvxbN9VyvAe9ZW7EwL+b3I/xV5a9jVs2BNWjJX9zgF/scz6vpWZ6xH6
yBI8MN+DcdWTc3OhRycGcPFAn0v88vu9eBvFCkVqn9oVA2BtbYr8tasNwDaXHyCV
W9QyXrGfUl9qaFBlggDG8ZJMJG5yju+177mxNBe9GBQ1DUccyVGb/XefrfO6Qa5y
OwZ+blFS67GwD+IvYT2VJmdFKuTror5tueJF+2ZWoI6srweVMtZ6OGKeUn95/OX0
y+kzFBd/0iuS8mJaCiU4u0TXgFh+T1mdTsVAa5jMoVtdE+Pn7wlBwoY7CWh9Fpvs
djowaAXq1jWuHTRbWbGwDK3ovGmzMPprGmZvX0TDoyjb3sB6gO2KsxGm3LYaFzj4
tFfZYfNTXlEjEWEg7vG/joEmgMKv1mZvCWZpKpVsvXsYoaHcH9W32fiK/tepFtgA
IlEL+uSqkFm0lFKVHcccRVzQ5QXaLX9q3F8UBrxWogjefqFgQgxJYC6Tul9HjwZB

Processed: Bug#1026558 marked as pending in python-cookies

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1026558 [src:python-cookies] python-cookies: FTBFS: make[1]: *** 
[debian/rules:12: override_dh_auto_clean] Error 25
Added tag(s) pending.

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

Bug#1026558: marked as pending in python-cookies

[Bastian Germann]

Control: tag -1 pending

Hello,

Bug #1026558 in python-cookies reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/python-team/packages/python-cookies/-/commit/2193311aec42027c6ac614899f190e6734827a39


Patch: Fix all DeprecationWarnings as of Python 3.7.0 (Closes: #1026558)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1026558

Processed (with 2 errors): Block 1042023 by 1049463

[Debian Bug Tracking System]

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

> # block by bug on ftpmaster where we request removal of binaries for armel 
> and mipsel sid
> block 1042023 by 1049463
Bug #1042023 [src:opm-common] opm-common: FTBFS on armel and mipsel
1042023 was not blocked by any bugs.
1042023 was not blocking any bugs.
Added blocking bug(s) of 1042023: 1049463
> # won't fix as opm-common never supported 32bit architectures and Cmake in 
> opm-common will now fail there
> tag 1042023 wontfix # lower severity to allow transition of
Unknown tag/s: #, lower, severity, to, allow, transition, of.
Recognized are: patch wontfix moreinfo unreproducible help security upstream 
pending confirmed ipv6 lfs d-i l10n newcomer a11y ftbfs fixed-upstream fixed 
fixed-in-experimental sid experimental potato woody sarge sarge-ignore etch 
etch-ignore lenny lenny-ignore squeeze squeeze-ignore wheezy wheezy-ignore 
jessie jessie-ignore stretch stretch-ignore buster buster-ignore bullseye 
bullseye-ignore bookworm bookworm-ignore trixie trixie-ignore forky 
forky-ignore.

Bug #1042023 [src:opm-common] opm-common: FTBFS on armel and mipsel
Added tag(s) wontfix.
> opm-common-2023.04+ds-5 once ftpmaster removed binaries for armel.
Unknown command or malformed arguments to command.
> # Even though it built there previously armel, being 32bit, was never 
> supported.
> severity 1042023 normal
Bug #1042023 [src:opm-common] opm-common: FTBFS on armel and mipsel
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Bug#1050168: FTBFS: test_no_local_cert: tlsv13 alert certificate required

[Shengjing Zhu]

Source: kxd
Version: 0.15-4
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: albert...@blitiri.com.ar, z...@debian.org

I'm not sure if it's related to golang-defaults -> golang-1.21 recently.

tests/run_tests -b
...F
Stderr:
/usr/lib/python3.11/unittest/case.py:622: ResourceWarning: unclosed 

  with outcome.testPartExecutor(self):
..
==
FAIL: test_no_local_cert (__main__.TrickyRequests.test_no_local_cert)
No local certificate.
--
Traceback (most recent call last):
  File "/<>/tests/run_tests", line 357, in test_no_local_cert
conn.getresponse()
  File "/usr/lib/python3.11/http/client.py", line 1378, in getresponse
response.begin()
  File "/usr/lib/python3.11/http/client.py", line 318, in begin
version, status, reason = self._read_status()
  ^^^
  File "/usr/lib/python3.11/http/client.py", line 279, in _read_status
line = str(self.fp.readline(_MAXLINE + 1), "iso-8859-1")
   ^^
  File "/usr/lib/python3.11/socket.py", line 706, in readinto
return self._sock.recv_into(b)
   ^^^
  File "/usr/lib/python3.11/ssl.py", line 1278, in recv_into
return self.read(nbytes, buffer)
   ^
  File "/usr/lib/python3.11/ssl.py", line 1134, in read
return self._sslobj.read(len, buffer)
   ^^
ssl.SSLError: [SSL: TLSV13_ALERT_CERTIFICATE_REQUIRED] tlsv13 alert certificate 
required (_ssl.c:2576)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/<>/tests/run_tests", line 360, in test_no_local_cert
self.assertEqual(err.reason, "SSLV3_ALERT_BAD_CERTIFICATE")
AssertionError: 'TLSV13_ALERT_CERTIFICATE_REQUIRED' != 
'SSLV3_ALERT_BAD_CERTIFICATE'
- TLSV13_ALERT_CERTIFICATE_REQUIRED
+ SSLV3_ALERT_BAD_CERTIFICATE


Stdout:
Launching server:  /<>/out/kxd 
--data_dir=/tmp/kxdtest-y_lm39pn/config-server-u2ol6sph/data 
--key=/tmp/kxdtest-y_lm39pn/config-server-u2ol6sph/key.pem 
--cert=/tmp/kxdtest-y_lm39pn/config-server-u2ol6sph/cert.pem 
--logfile=/tmp/kxdtest-y_lm39pn/config-server-u2ol6sph/log 
--hook=/tmp/kxdtest-y_lm39pn/config-server-u2ol6sph/hook

--
Ran 10 tests in 3.009s

FAILED (failures=1)

Processed: Re: Bug#1050163: dh-python is confused about the name for wheels on armel and armhf

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/tox-dev/tox/issues/3100
Bug #1050163 [src:dh-python] dh-python is confused about the name for wheels on 
armel and armhf
Set Bug forwarded-to-address to 'https://github.com/tox-dev/tox/issues/3100'.
> reassign -1 tox
Bug #1050163 [src:dh-python] dh-python is confused about the name for wheels on 
armel and armhf
Bug reassigned from package 'src:dh-python' to 'tox'.
No longer marked as found in versions dh-python/6.20230813.
Ignoring request to alter fixed versions of bug #1050163 to the same values 
previously set
> found -1 tox/4.9.0-1
Bug #1050163 [tox] dh-python is confused about the name for wheels on armel and 
armhf
Marked as found in versions tox/4.9.0-1.
> close -1 4.9.0-2
Bug #1050163 [tox] dh-python is confused about the name for wheels on armel and 
armhf
Marked as fixed in versions tox/4.9.0-2.
Bug #1050163 [tox] dh-python is confused about the name for wheels on armel and 
armhf
Marked Bug as done
> affects -1 dh-python
Bug #1050163 {Done: Stefano Rivera } [tox] dh-python is 
confused about the name for wheels on armel and armhf
Added indication that 1050163 affects dh-python

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

Bug#1050163: dh-python is confused about the name for wheels on armel and armhf

[Stefano Rivera]

Control: forwarded -1 https://github.com/tox-dev/tox/issues/3100
Control: reassign -1 tox
Control: found -1 tox/4.9.0-1
Control: close -1 4.9.0-2
Control: affects -1 dh-python

This should already be fixed in tox.

This should be fixed by tox 4.9.0-2.

Stefano

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Processed: Re: Bug#1041249: cpp-httplib: FTBFS on s390x: ../test/test.cc:5462: Failure

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 cpp-httplib: FTBFS on s390x, armhf due to flaky tests
Bug #1041249 [src:cpp-httplib] cpp-httplib: FTBFS on s390x: 
../test/test.cc:5462: Failure
Changed Bug title to 'cpp-httplib: FTBFS on s390x, armhf due to flaky tests' 
from 'cpp-httplib: FTBFS on s390x: ../test/test.cc:5462: Failure'.

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

Bug#1041249: cpp-httplib: FTBFS on s390x: ../test/test.cc:5462: Failure

[Emanuele Rocca]

Control: retitle -1 cpp-httplib: FTBFS on s390x, armhf due to flaky tests

Hi,

On 2023-07-24 04:26, Andrea Pappacoda wrote:
> I've looked into this, but I couldn't find any change which would
> cause test failures on s390x specifically.  cpp-httplib's test suite
> is a bit flaky though, so it may have been just an unlucky run (this
> is an issue in itself, but I have already reported it upstream and it
> didn't get much attention). Is it possible to re-try the build?

I've bumped into a very similar failure on armhf too, so the problem is
probably not s390x-specific.

Note that the build succeeded on a second try.

[--] 3 tests from HostAndPortPropertiesTest
[ RUN  ] HostAndPortPropertiesTest.NoSSL
[   OK ] HostAndPortPropertiesTest.NoSSL (0 ms)
[ RUN  ] HostAndPortPropertiesTest.NoSSLWithSimpleAPI
[   OK ] HostAndPortPropertiesTest.NoSSLWithSimpleAPI (0 ms)
[ RUN  ] HostAndPortPropertiesTest.SSL
[   OK ] HostAndPortPropertiesTest.SSL (0 ms)
[--] 3 tests from HostAndPortPropertiesTest (0 ms total)

[--] 2 tests from SSLClientTest
[ RUN  ] SSLClientTest.UpdateCAStore
[   OK ] SSLClientTest.UpdateCAStore (0 ms)
[ RUN  ] SSLClientTest.ServerCertificateVerification4
../test/test.cc:4808: Failure
Value of: res
  Actual: false
Expected: true
==


Summary of Failures:

1/1 main TIMEOUT900.20s   killed by signal 15 SIGTERM

Ok: 0   
Expected Fail:  0   
Fail:   0   
Unexpected Pass:0   
Skipped:0   
Timeout:1   
dh_auto_test: error: cd obj-arm-linux-gnueabihf && LC_ALL=C.UTF-8 
MESON_TESTTHREADS=8 meson test --timeout-multiplier=3 
--test-args=--gtest_filter=-\*_Online:\*ClientProblemDetectionTest\* returned 
exit code 1
make[1]: *** [debian/rules:42: override_dh_auto_test] Error 25
make[1]: Leaving directory '/<>'

Processed: Re: Bug#1041569: gnome-shell-extension-easyscreencast: needs update for GNOME Shell 44

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/EasyScreenCast/EasyScreenCast/pull/345
Bug #1041569 [gnome-shell-extension-easyscreencast] 
gnome-shell-extension-easyscreencast: needs update for GNOME Shell 44
Set Bug forwarded-to-address to 
'https://github.com/EasyScreenCast/EasyScreenCast/pull/345'.
> tags -1 + patch fixed-upstream
Bug #1041569 [gnome-shell-extension-easyscreencast] 
gnome-shell-extension-easyscreencast: needs update for GNOME Shell 44
Added tag(s) fixed-upstream and patch.

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

Bug#1041569: gnome-shell-extension-easyscreencast: needs update for GNOME Shell 44

[Simon McVittie]

Control: forwarded -1 https://github.com/EasyScreenCast/EasyScreenCast/pull/345
Control: tags -1 + patch fixed-upstream

On Thu, 20 Jul 2023 at 23:27:25 +0100, Simon McVittie wrote:
> This extension has not been checked for compatibility with GNOME Shell
> 44. Depending how compatible it is, it will either need an update to
> its metadata.json and debian/control to declare compatibility with the
> new version, or code changes to adapt it to the new Shell version.

According to upstream it seems that only metadata changes were needed.

smcv

Bug#1000089: clisp: depends on obsolete pcre3 library

[Bastian Germann]

I am uploading this as NMU to DELAYED/2.

Processed: Re: Bug#1041571: gnome-shell-extension-flypie: needs update for GNOME Shell 44

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + fixed-upstream patch
Bug #1041571 [gnome-shell-extension-flypie] gnome-shell-extension-flypie: needs 
update for GNOME Shell 44
Added tag(s) patch and fixed-upstream.

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

Bug#1041571: gnome-shell-extension-flypie: needs update for GNOME Shell 44

[Simon McVittie]

Control: tags -1 + fixed-upstream patch

On Thu, 20 Jul 2023 at 23:28:09 +0100, Simon McVittie wrote:
> This extension has not been checked for compatibility with GNOME Shell
> 44. Depending how compatible it is, it will either need an update to
> its metadata.json and debian/control to declare compatibility with the
> new version, or code changes to adapt it to the new Shell version.

Upstream version 21 already declares compatibility with GNOME Shell 44 in
metadata.json, so unless you know otherwise, the required change should
be as simple as this edit to debian/control:

-Depends: gnome-shell (<< 44~), gnome-shell (>= 3.36~), ${misc:Depends}
+Depends: gnome-shell (<< 45~), gnome-shell (>= 3.36~), ${misc:Depends}

Please remember to check metadata.json when importing new upstream releases.

Thanks,
smcv

Processed: Re: Bug#1041572: gnome-shell-extension-freon: needs update for GNOME Shell 44

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 
> https://github.com/UshakovVasilii/gnome-shell-extension-freon/pull/257
Bug #1041572 [gnome-shell-extension-freon] gnome-shell-extension-freon: needs 
update for GNOME Shell 44
Set Bug forwarded-to-address to 
'https://github.com/UshakovVasilii/gnome-shell-extension-freon/pull/257'.
> tags -1 + patch fixed-upstream
Bug #1041572 [gnome-shell-extension-freon] gnome-shell-extension-freon: needs 
update for GNOME Shell 44
Added tag(s) fixed-upstream and patch.

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

Bug#1041572: gnome-shell-extension-freon: needs update for GNOME Shell 44

[Simon McVittie]

Control: forwarded -1 
https://github.com/UshakovVasilii/gnome-shell-extension-freon/pull/257
Control: tags -1 + patch fixed-upstream

On Thu, 20 Jul 2023 at 23:28:26 +0100, Simon McVittie wrote:
> This extension has not been checked for compatibility with GNOME Shell
> 44. Depending how compatible it is, it will either need an update to
> its metadata.json and debian/control to declare compatibility with the
> new version, or code changes to adapt it to the new Shell version.

According to the upstream issue tracker, only metadata changes are needed.

smcv

Processed: Re: Bug#1041573: gnome-shell-extension-gamemode: needs update for GNOME Shell 44

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/gicmo/gamemode-extension/pull/65
Bug #1041573 [gnome-shell-extension-gamemode] gnome-shell-extension-gamemode: 
needs update for GNOME Shell 44
Set Bug forwarded-to-address to 
'https://github.com/gicmo/gamemode-extension/pull/65'.
> tags -1 + patch fixed-upstream
Bug #1041573 [gnome-shell-extension-gamemode] gnome-shell-extension-gamemode: 
needs update for GNOME Shell 44
Added tag(s) patch and fixed-upstream.

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

Bug#1049884: birdtray: FTBFS on armhf, armel, mipsel due to thunderbird build-dep

[Emanuele Rocca]

Hi Adam,

On 2023-08-16 05:14, Adam Borowski wrote:
> This is not a regression, thus why would it be a bug?

Well FTBFS is a bug isn't it? :-)

> There's nothing in birdtray itself that would prevent it from being built on
> these architectures the moment problems in thunderbird are resolved

Why does birdtray build-depend on thunderbird? It seems to build
perfectly fine in a clean armhf chroot without it.

Cheers,
  Emanuele

Bug#1041573: gnome-shell-extension-gamemode: needs update for GNOME Shell 44

[Simon McVittie]

Control: forwarded -1 https://github.com/gicmo/gamemode-extension/pull/65
Control: tags -1 + patch fixed-upstream

On Thu, 20 Jul 2023 at 23:28:48 +0100, Simon McVittie wrote:
> This extension has not been checked for compatibility with GNOME Shell
> 44. Depending how compatible it is, it will either need an update to
> its metadata.json and debian/control to declare compatibility with the
> new version, or code changes to adapt it to the new Shell version.

>From upstream it appears that only metadata changes are needed for GNOME
Shell 44.

Please set the dependency version to gnome-shell (<< 45~) to make sure this
extension is not falsely advertised as compatible with Shell 45, even if
metadata.json says it's compatible: according to comments on the
upstream PR, 45 was added to metadata.json wrongly, and according to
https://github.com/gicmo/gamemode-extension/issues/70 code changes will
be required for Shell 45.

smcv

Bug#1050163: dh-python is confused about the name for wheels on armel and armhf

[Matthias Klose]

Package: src:dh-python
Version: 6.20230813
Severity: serious
Tags: sid trixie

dh-python's autopkg tests fail on armel and armhf,

https://ci.debian.net/data/autopkgtest/testing/armhf/d/dh-python/36979742/log.gz

the reference tests have:

'build/bdist.linux-armhf' does not exist -- can't clean it
creating build/temp.linux-armhf-cpython-311

while the new one has:

'build/bdist.linux-armv7l' does not exist -- can't clean it
creating build/temp.linux-armv7l-cpython-311

and later fails with

ERROR: foo-0.0.0-cp311-cp311-linux_armv7l.whl is not a supported wheel on this 
platform.

Bug#1041574: gnome-shell-extension-hamster: needs update for GNOME Shell 44

[Simon McVittie]

Control: forwarded -1 
https://github.com/projecthamster/hamster-shell-extension/pull/357
Control: tags -1 + patch fixed-upstream

On Thu, 20 Jul 2023 at 23:29:30 +0100, Simon McVittie wrote:
> This extension has not been checked for compatibility with GNOME Shell
> 44. Depending how compatible it is, it will either need an update to
> its metadata.json and debian/control to declare compatibility with the
> new version, or code changes to adapt it to the new Shell version.

>From upstream it appears that only metadata changes are needed.

smcv

Processed: Re: Bug#1041574: gnome-shell-extension-hamster: needs update for GNOME Shell 44

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 
> https://github.com/projecthamster/hamster-shell-extension/pull/357
Bug #1041574 [gnome-shell-extension-hamster] gnome-shell-extension-hamster: 
needs update for GNOME Shell 44
Set Bug forwarded-to-address to 
'https://github.com/projecthamster/hamster-shell-extension/pull/357'.
> tags -1 + patch fixed-upstream
Bug #1041574 [gnome-shell-extension-hamster] gnome-shell-extension-hamster: 
needs update for GNOME Shell 44
Added tag(s) fixed-upstream and patch.

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

Processed: Re: Bug#1041575: gnome-shell-extension-impatience: needs update for GNOME Shell 44

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/timbertson/gnome-shell-impatience/pull/31
Bug #1041575 [gnome-shell-extension-impatience] 
gnome-shell-extension-impatience: needs update for GNOME Shell 44
Set Bug forwarded-to-address to 
'https://github.com/timbertson/gnome-shell-impatience/pull/31'.
> tags -1 + patch fixed-upstream
Bug #1041575 [gnome-shell-extension-impatience] 
gnome-shell-extension-impatience: needs update for GNOME Shell 44
Added tag(s) patch and fixed-upstream.

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

Bug#1041575: gnome-shell-extension-impatience: needs update for GNOME Shell 44

[Simon McVittie]

Control: forwarded -1 
https://github.com/timbertson/gnome-shell-impatience/pull/31
Control: tags -1 + patch fixed-upstream

On Sun, 20 Aug 2023 at 23:54:13 +0100, Simon McVittie wrote:
> On Thu, 20 Jul 2023 at 23:29:56 +0100, Simon McVittie wrote:
> > This extension has not been checked for compatibility with GNOME Shell
> > 44. Depending how compatible it is, it will either need an update to
> > its metadata.json and debian/control to declare compatibility with the
> > new version, or code changes to adapt it to the new Shell version.

>From upstream it appears that only metadata changes are needed.

smcv

Bug#1041580: gnome-shell-extension-tiling-assistant: needs update for GNOME Shell 44

[Simon McVittie]

On Mon, 21 Aug 2023 at 00:24:01 +0100, Simon McVittie wrote:
> On Thu, 20 Jul 2023 at 23:38:49 +0100, Simon McVittie wrote:
> > The version of gnome-shell-extension-tiling-assistant in unstable is
> > not marked as compatible with GNOME Shell 44, but the version in
> > experimental is.
> 
> I've just uploaded gnome-shell 44 to unstable. Please upload the
> experimental version of this extension to unstable whenever is convenient,
> and close this bug in that upload.

Alternatively, upstream version 41 seems to be "officially" compatible
with Shell 44 without needing downstream patches.

smcv

Bug#1041582: gnome-shell-extension-vertical-overview: needs update for GNOME Shell 44

[Simon McVittie]

Control: forwarded -1 
https://github.com/RensAlthuis/vertical-overview/issues/122
Control: tags -1 + upstream patch

On Thu, 20 Jul 2023 at 23:39:33 +0100, Simon McVittie wrote:
> This extension has not been checked for compatibility with GNOME Shell
> 44. Depending how compatible it is, it will either need an update to
> its metadata.json and debian/control to declare compatibility with the
> new version, or code changes to adapt it to the new Shell version.

It appears that code changes are required. A merge request has been proposed
upstream  but has
not yet been reviewed or merged.

(I have not checked that change for correctness: I don't use this
extension myself.)

smcv

Processed: Re: Bug#1041582: gnome-shell-extension-vertical-overview: needs update for GNOME Shell 44

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/RensAlthuis/vertical-overview/issues/122
Bug #1041582 [gnome-shell-extension-vertical-overview] 
gnome-shell-extension-vertical-overview: needs update for GNOME Shell 44
Set Bug forwarded-to-address to 
'https://github.com/RensAlthuis/vertical-overview/issues/122'.
> tags -1 + upstream patch
Bug #1041582 [gnome-shell-extension-vertical-overview] 
gnome-shell-extension-vertical-overview: needs update for GNOME Shell 44
Added tag(s) upstream and patch.

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

Bug#1042023: opm-common: FTBFS on armel and mipsel

[Markus Blatt]

Hi,

I have changed opm-common to not build on 32bit architectures anymore
in version 2023.04+ds-3 and requested removal of the binary packages
in #1049463 [1].

Once the binaries are removed we should decrease the severity of this bug
to allow migation of new versions to testing again.

Best,

Markus

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

Bug#1042303: marked as done (ukui-screensaver: FTBFS: make[3]: *** [i18n_ts/CMakeFiles/i18n.dir/build.make:115: i18n_ts/.lupdate/es.ts.stamp] Error 1)

[Debian Bug Tracking System]

Your message dated Mon, 21 Aug 2023 07:50:49 +
with message-id 
and subject line Bug#1042303: fixed in ukui-screensaver 3.0.3.2-1
has caused the Debian Bug report #1042303,
regarding ukui-screensaver: FTBFS: make[3]: *** 
[i18n_ts/CMakeFiles/i18n.dir/build.make:115: i18n_ts/.lupdate/es.ts.stamp] 
Error 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.)


-- 
1042303: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042303
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ukui-screensaver
Version: 3.0.3.1-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230726 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
> /<>/BiometricAuth/giodbus.h:0: Note: No relevant classes found. 
> No output generated.
> [  1%] Generating .lupdate/bo.ts.stamp
> [  1%] Generating moc_autoresize.cpp
> [  1%] Generating .lupdate/es.ts.stamp
> [  1%] Generating moc_biometricdeviceswidget.cpp
> cd /<>/obj-x86_64-linux-gnu/Common && /usr/lib/qt5/bin/moc 
> @/<>/obj-x86_64-linux-gnu/Common/moc_autoresize.cpp_parameters
> cd /<>/obj-x86_64-linux-gnu/BiometricAuth && 
> /usr/lib/qt5/bin/moc 
> @/<>/obj-x86_64-linux-gnu/BiometricAuth/moc_biometricdeviceswidget.cpp_parameters
> cd /<>/obj-x86_64-linux-gnu/i18n_ts && /usr/lib/qt5/bin/lupdate 
> @ -ts /<>/i18n_ts/es.ts
> cd /<>/obj-x86_64-linux-gnu/i18n_ts && /usr/lib/qt5/bin/lupdate 
> @ -ts /<>/i18n_ts/bo.ts
> [  2%] Automatic MOC and UIC for target VirtualKeyboard
> [  2%] Automatic MOC and UIC for target Kylin-nm
> cd /<>/obj-x86_64-linux-gnu/KylinNM && /usr/bin/cmake -E 
> cmake_autogen 
> /<>/obj-x86_64-linux-gnu/KylinNM/CMakeFiles/Kylin-nm_autogen.dir/AutogenInfo.json
>  Debug
> cd /<>/obj-x86_64-linux-gnu/VirtualKeyboard && /usr/bin/cmake -E 
> cmake_autogen 
> /<>/obj-x86_64-linux-gnu/VirtualKeyboard/CMakeFiles/VirtualKeyboard_autogen.dir/AutogenInfo.json
>  Debug
> /<>/Common/autoresize.h:0: Note: No relevant classes found. No 
> output generated.
> [  2%] Generating moc_biometricproxy.cpp
> cd /<>/obj-x86_64-linux-gnu/BiometricAuth && 
> /usr/lib/qt5/bin/moc 
> @/<>/obj-x86_64-linux-gnu/BiometricAuth/moc_biometricproxy.cpp_parameters
> [  3%] Generating moc_interface.cpp
> QFSFileEngine::open: No file name specified
> QFSFileEngine::open: No file name specified
> lupdate error: List file '' is not readable.
> lupdate error: List file '' is not readable.
> make[3]: *** [i18n_ts/CMakeFiles/i18n.dir/build.make:115: 
> i18n_ts/.lupdate/es.ts.stamp] Error 1


The full build log is available from:
http://qa-logs.debian.net/2023/07/26/ukui-screensaver_3.0.3.1-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230726;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230726=lu...@debian.org=1=1=1=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: ukui-screensaver
Source-Version: 3.0.3.2-1
Done: handsome_feng 

We believe that the bug you reported is fixed in the latest version of
ukui-screensaver, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1042...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
handsome_feng  (supplier of updated 
ukui-screensaver package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 21 Aug 2023 15:32:43 +0800
Source: ukui-screensaver
Architecture: source
Version: 3.0.3.2-1
Distribution: unstable
Urgency: medium
Maintainer: Kylin Team 
Changed-By: handsome_feng 
Closes: 1042303
Changes:
 

Bug#1025633: marked as done (ukui-biometric-auth: dependency on transitional policykit-1 package)

[Debian Bug Tracking System]

Your message dated Mon, 21 Aug 2023 07:04:02 +
with message-id 
and subject line Bug#1025633: fixed in ukui-biometric-auth 1.2.2.1-2
has caused the Debian Bug report #1025633,
regarding ukui-biometric-auth: dependency on transitional policykit-1 package
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.)


-- 
1025633: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025633
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ukui-biometric-auth
Version: 1.2.2.1-1
Severity: normal
User: pkg-utopia-maintain...@lists.alioth.debian.org
Usertags: policykit-1
Control: block 1025540 by -1

This package has a Depends and/or Build-Depends on the transitional
package policykit-1, which has been separated into polkitd, pkexec and
(deprecated) polkitd-pkla packages.

If this package communicates with polkitd via D-Bus, please represent that
as a Depends, Recommends or Suggests on polkitd, whichever is appropriate
for the strength of the requirement.

If this package runs /usr/bin/pkexec, please represent that as a Depends,
Recommends or Suggests on pkexec, whichever is appropriate for the strength
of the requirement.

If this package requires polkit at build-time (usually for the gettext
extensions polkit.its and polkit.loc), please build-depend on both
libpolkit-gobject-1-dev and polkitd, even if the package does not
actually depend on libpolkit-gobject-1 at runtime. This is because
the gettext extensions are currently in polkitd, but might be moved to
libpolkit-gobject-1-dev in future (see #955204). pkexec is usually not
required at build-time.

For packages that are expected to be backported to bullseye, it's OK to
use an alternative dependency: polkitd | policykit-1 and/or
pkexec | policykit-1.

This is part of a mass bug filing, see
.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Source: ukui-biometric-auth
Source-Version: 1.2.2.1-2
Done: handsome_feng 

We believe that the bug you reported is fixed in the latest version of
ukui-biometric-auth, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1025...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
handsome_feng  (supplier of updated 
ukui-biometric-auth package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 21 Aug 2023 13:47:48 +0800
Source: ukui-biometric-auth
Architecture: source
Version: 1.2.2.1-2
Distribution: unstable
Urgency: medium
Maintainer: Kylin Team 
Changed-By: handsome_feng 
Closes: 1025633
Changes:
 ukui-biometric-auth (1.2.2.1-2) unstable; urgency=medium
 .
   * d/control: drop policykit-1, add pkexec. (Closes: #1025633)
Checksums-Sha1:
 e085f7a90f7dacfd0ee29e24ac94d925d0785932 2232 ukui-biometric-auth_1.2.2.1-2.dsc
 8e1e8adffbc4f69eeb8762f74699b0616f28dd67 451176 
ukui-biometric-auth_1.2.2.1.orig.tar.gz
 6e19f7cc428c4452b84a92c3d2204ea85a8990b2 2668 
ukui-biometric-auth_1.2.2.1-2.debian.tar.xz
 94ef4879eb68405736f0743f0d6a870faeb20070 21734 
ukui-biometric-auth_1.2.2.1-2_source.buildinfo
Checksums-Sha256:
 6442624c6e4cb1c65fb62025364ab17805c246d6e466f087bf4bd3b4b2300ccb 2232 
ukui-biometric-auth_1.2.2.1-2.dsc
 d0b4650a2b7478664a208feb3395b93c4818bc1d8a17e80a0e19f99fdb9a10af 451176 
ukui-biometric-auth_1.2.2.1.orig.tar.gz
 33f246cf847109ad8c6d1ced0c857fb43f1f386fe6395a0d0ea4588f27bf5cac 2668 
ukui-biometric-auth_1.2.2.1-2.debian.tar.xz
 40f15033a057ae4ec01ab23f3eab161e77130e07384d1ec39f0789100a16628c 21734 
ukui-biometric-auth_1.2.2.1-2_source.buildinfo
Files:
 4b0180307b4ca29231cd8fa102c4b498 2232 admin optional 
ukui-biometric-auth_1.2.2.1-2.dsc
 464953629fa3030f7264bb39cd0363c0 451176 admin optional 
ukui-biometric-auth_1.2.2.1.orig.tar.gz
 e16b1a7f66b0e986220e93cdd806775d 2668 admin optional 
ukui-biometric-auth_1.2.2.1-2.debian.tar.xz
 bee606217082f19f4a032b7255eb022c 21734 admin optional 
ukui-biometric-auth_1.2.2.1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJPBAEBCAA5FiEEhsgAHpUwnacZWWSCm7hQwBMRHwwFAmTjCWcbHGppYW5mZW5n
bGlAdWJ1bnR1a3lsaW4uY29tAAoJEJu4UMATER8M6LIP/3Gh+UAe+a2wu5LsAioa

Processed: not fixed Re: libgpuarray: i386 test fail with new pocl

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1031414 [src:pocl,src:libgpuarray] libgpuarray: i386 test fail with new 
pocl
Severity set to 'serious' from 'normal'

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