Processed: Used correct version for fix to allow migration

[Debian Bug Tracking System]

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

> fixed 1037808 2023.04+ds-1
Bug #1037808 {Done: Markus Blatt } [src:opm-grid] opm-grid: 
ftbfs with GCC-13
Marked as fixed in versions opm-grid/2023.04+ds-1.
> thanks
Stopping processing here.

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

Bug#1043501: marked as done (gst-plugins-ugly1.0: ZDI-CAN-21443 ZDI-CAN-21444)

[Debian Bug Tracking System]

Your message dated Wed, 16 Aug 2023 07:30:30 +0200
with message-id 
and subject line Re: Accepted gst-plugins-ugly1.0 1.22.5-1 (source) into 
unstable
has caused the Debian Bug report #1043501,
regarding gst-plugins-ugly1.0: ZDI-CAN-21443 ZDI-CAN-21444
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.)


-- 
1043501: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043501
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gst-plugins-ugly1.0
Version: 1.22.4-1
Severity: grave
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

There are two gst-streamer-ugly1.0 reports from ZDI (not yet public)
tracked as 

https://gstreamer.freedesktop.org/security/sa-2023-0004.html
https://gitlab.freedesktop.org/gstreamer/gstreamer/-/commit/4266ba0fd2be7702044a5d90a8215abe41709874


https://gstreamer.freedesktop.org/security/sa-2023-0005.html
https://gitlab.freedesktop.org/gstreamer/gstreamer/-/commit/eb89e0a13eeb59fc5bab787ded50faf6a50087e3

AFAICS, no CVEs are yet assigned?

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: gst-plugins-ugly1.0
Source-Version: 1.22.5-1

On Tue, Aug 15, 2023 at 03:06:19PM +, Debian FTP Masters wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> Format: 1.8
> Date: Tue, 15 Aug 2023 10:46:22 -0400
> Source: gst-plugins-ugly1.0
> Built-For-Profiles: noudeb
> Architecture: source
> Version: 1.22.5-1
> Distribution: unstable
> Urgency: medium
> Maintainer: Maintainers of GStreamer packages 
> 
> Changed-By: Jeremy Bícha 
> Changes:
>  gst-plugins-ugly1.0 (1.22.5-1) unstable; urgency=medium
>  .
>* Team upload
>* New upstream release

This fixes as well #1043501, sa-2023-0004 and sa-2023-0005.

Regards,
Salvatore--- End Message ---

Bug#1043501: Accepted gst-plugins-ugly1.0 1.22.5-1 (source) into unstable

[Salvatore Bonaccorso]

Source: gst-plugins-ugly1.0
Source-Version: 1.22.5-1

On Tue, Aug 15, 2023 at 03:06:19PM +, Debian FTP Masters wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> Format: 1.8
> Date: Tue, 15 Aug 2023 10:46:22 -0400
> Source: gst-plugins-ugly1.0
> Built-For-Profiles: noudeb
> Architecture: source
> Version: 1.22.5-1
> Distribution: unstable
> Urgency: medium
> Maintainer: Maintainers of GStreamer packages 
> 
> Changed-By: Jeremy Bícha 
> Changes:
>  gst-plugins-ugly1.0 (1.22.5-1) unstable; urgency=medium
>  .
>* Team upload
>* New upstream release

This fixes as well #1043501, sa-2023-0004 and sa-2023-0005.

Regards,
Salvatore

Bug#965794: RM python-ooolib?

[Bastian Germann]

Hi Rene,

On Sat, 20 May 2023 12:18:16 +0200 Rene Engelhard  wrote:

How is it unclear that noone seriously cares about this package?

Old upstream version, popcon 4, ignored by the maintainer. The fix is 
clear, I just want to get it AUTORMed. How difficult is it to understand 
that?



As I already said to Adrian when he last tagged the bug: stop resetting 
the autorm counter.


(which you did now again, sigh.)

  Besides that: it would miss the hard freeze anyway with medium urgency 
so it's a total waste of time.


Please remove the package then or at least orphan it.

Thanks,
Bastian

Bug#999953: sslh: depends on obsolete pcre3 library

[Don Armstrong]

On Tue, 15 Aug 2023, Bastian Germann wrote:
> I am uploading a NMU to fix this.

That's not the correct fix; the correct fix is to use pcre2 instead of
pcre3. I've already got a patch for it available. but apparently I
haven't pushed it to salsa; sorry about that.

The reason why I haven't uploaded it yet is because the tests for 1.22c 
do not succeed.

-- 
Don Armstrong  https://www.donarmstrong.com

Let the victors, when they come,
When the forts of folly fall
Find thy body by the wall!
 -- Matthew Arnold

Bug#999967: marked as done (samhain: depends on obsolete pcre3 library)

[Debian Bug Tracking System]

Your message dated Tue, 15 Aug 2023 22:09:27 +
with message-id 
and subject line Bug#67: fixed in samhain 4.1.4-2.1
has caused the Debian Bug report #67,
regarding samhain: 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.)


-- 
67: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=67
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: samhain
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: samhain
Source-Version: 4.1.4-2.1
Done: Bastian Germann 

We believe that the bug you reported is fixed in the latest version of
samhain, 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 999...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bastian Germann  (supplier of updated samhain 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: Tue, 15 Aug 2023 22:46:14 +0200
Source: samhain
Architecture: source
Version: 4.1.4-2.1
Distribution: unstable
Urgency: medium
Maintainer: Javier Fernández-Sanguino Peña 
Changed-By: Bastian Germann 
Closes: 67 1007320
Changes:
 samhain (4.1.4-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload
   * Disable logfile monitor and drop pcre (Closes: #67)
   * Convert to source format 3.0 (Closes: #1007320)
   * Drop unused dh_autoreconf
Checksums-Sha1:
 bd0b9923776f64cf034fb944d3a814323375a904 1686 samhain_4.1.4-2.1.dsc
 c7c95c6ebb5e3a4bdaf14ce3416759c896e66085 29428 samhain_4.1.4-2.1.debian.tar.xz
 8513ecc2e6d2dc8e2cec9a3c7b6a5a1e9b274daa 6395 
samhain_4.1.4-2.1_source.buildinfo
Checksums-Sha256:
 7404c06ee9871024921467a3ac5d54db0551e4366863d63db9442854544f74fb 1686 
samhain_4.1.4-2.1.dsc
 5566e51caf9854d79ebe9aa509666b248ba164d5c603ccd9c104f93ee8d992f1 29428 
samhain_4.1.4-2.1.debian.tar.xz
 98af2deeaed79b5dd3247bb37a30a50b586a6743c05a649764bb36f227055806 6395 
samhain_4.1.4-2.1_source.buildinfo
Files:
 9f50f19639cb10b9b30054bce2506658 1686 admin optional samhain_4.1.4-2.1.dsc
 3cbf42f347449246a335a57ee67dc660 29428 admin optional 
samhain_4.1.4-2.1.debian.tar.xz
 243c802dd724c0d7bde2dc416d551fe4 6395 admin optional 
samhain_4.1.4-2.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmTb8XEQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFPdXC/9gkDbxi3Pa7r+i+Ka/EveitIz+n1BcphZG
5fGgVHkuTDR2Fb6VLoOcxFrQq9czJ0E67gCOAy549GnzchD9L/j0uL2NxI3569P7
b8dLNfA16bz0YRB8isXPqj2yZl1W8PKzS/iWmTxW+FeeaBg4wzK6BgOz07OstnFf
KjGgdAYN7PDiKsc4aaNREC5dM759imOdJD2ixM72If0AS8Bg/LgFHVRqlwDXhOws
sMtppnjlnoMoh67QKAy4Qt/xE/PbcIEoNpjO7desWf+p0aApqmac02fx57YaUA6t
vVP91BglrgEEg2SidDOUXoRflLACvpUALYMVckbrhFCAMNf6ro8oMSLlXV3Okgju
wGTFdMU5QpENg+Rol6acZP3vlouVpxGbw/hTg3fJML9tLcCxkFehf6CzuF2q4CEb
1WDnM+i6mh5Lz8AImQM9gC13VsZd6GefGZ+SRQeN+MX0nuDy/3bi82LmReBVtejd
cjzJQFa1+aP4s6wfTnKN83bboP8igyQ=
=UG9C
-END PGP SIGNATURE End Message ---

Processed: fix

[Debian Bug Tracking System]

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

> fixed 845848 gnokii/0.6.30+dfsg-3
Bug #845848 {Done: Bastian Germann } [gnokii] gnokii: switch 
to build depend on the metapackage default-libmysqlclient-dev
The source gnokii and version 0.6.30+dfsg-3 do not appear to match any binary 
packages
Marked as fixed in versions gnokii/0.6.30+dfsg-3.
> fixed 777882 gnokii/0.6.30+dfsg-3
Bug #777882 {Done: gregor herrmann } [src:gnokii] gnokii: 
ftbfs with GCC-5
Bug #832330 {Done: gregor herrmann } [src:gnokii] gnokii: 
FTBFS in experimental: undefined references to GUI_HideAbout, CloseLogosWindow
The source gnokii and version 0.6.30+dfsg-3 do not appear to match any binary 
packages
Marked as fixed in versions gnokii/0.6.30+dfsg-3.
Marked as fixed in versions gnokii/0.6.30+dfsg-3.
>
End of message, stopping processing here.

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

Bug#999967: samhain: depends on obsolete pcre3 library

[Bastian Germann]

I am uploading a NMU to fix this. The debdiff is attached.diff -Nru samhain-4.1.4/configure samhain-4.1.4/configure
--- samhain-4.1.4/configure 2023-08-15 23:48:39.0 +0200
+++ samhain-4.1.4/configure 2016-06-02 22:40:17.0 +0200
@@ -4330,7 +4330,7 @@
 
 case "$host_os" in
 
-   *linux*|*-kfreebsd*-gnu|*-gnu*)
+   *linux*)
sh_use_lcaps="yes"
$as_echo "#define HOST_IS_LINUX 1" >>confdefs.h
 
diff -Nru samhain-4.1.4/configure.ac samhain-4.1.4/configure.ac
--- samhain-4.1.4/configure.ac  2023-08-15 23:48:39.0 +0200
+++ samhain-4.1.4/configure.ac  2016-06-02 13:45:05.0 +0200
@@ -56,7 +56,7 @@
 
 case "$host_os" in
 
-   *linux*|*-kfreebsd*-gnu|*-gnu*)
+   *linux*)
sh_use_lcaps="yes"
AC_DEFINE(HOST_IS_LINUX)
 AC_DEFINE(HAVE_EXT2_IOCTLS)
diff -Nru samhain-4.1.4/debian/changelog samhain-4.1.4/debian/changelog
--- samhain-4.1.4/debian/changelog  2023-08-15 23:48:39.0 +0200
+++ samhain-4.1.4/debian/changelog  2023-08-15 22:46:14.0 +0200
@@ -1,3 +1,12 @@
+samhain (4.1.4-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload
+  * Disable logfile monitor and drop pcre (Closes: #67)
+  * Convert to source format 3.0 (Closes: #1007320)
+  * Drop unused dh_autoreconf
+
+ -- Bastian Germann   Tue, 15 Aug 2023 22:46:14 +0200
+
 samhain (4.1.4-2) unstable; urgency=medium
 
   * Add Build-Dep on libpcre3-dev to fix FTBFS. This library is required
diff -Nru samhain-4.1.4/debian/control samhain-4.1.4/debian/control
--- samhain-4.1.4/debian/control2023-08-15 23:48:39.0 +0200
+++ samhain-4.1.4/debian/control2023-08-15 22:46:14.0 +0200
@@ -2,7 +2,7 @@
 Section: admin
 Priority: optional
 Maintainer: Javier Fernández-Sanguino Peña 
-Build-Depends: debhelper (>> 9), autoconf, procps, libgmp3-dev, e2fslibs-dev, 
libprelude-dev, libauparse-dev [linux-any], autotools-dev, dh-autoreconf, 
libpcre3-dev
+Build-Depends: debhelper (>> 9), autoconf, procps, libgmp3-dev, e2fslibs-dev, 
libprelude-dev, libauparse-dev [linux-any], autotools-dev
 Standards-Version: 3.9.8
 Homepage: http://la-samhna.de/samhain/index.html
 
@@ -27,4 +27,3 @@
   + database and configuration files can be signed
   + logfile entries and e-mail reports are signed
   + support for stealth operation
- .
diff -Nru samhain-4.1.4/debian/patches/configure.patch 
samhain-4.1.4/debian/patches/configure.patch
--- samhain-4.1.4/debian/patches/configure.patch1970-01-01 
01:00:00.0 +0100
+++ samhain-4.1.4/debian/patches/configure.patch2023-08-15 
22:46:14.0 +0200
@@ -0,0 +1,25 @@
+Description: Add OS detection to support Hurd
+Author: Cyril Brulebois
+---
+--- samhain-4.1.4.orig/configure.ac
 samhain-4.1.4/configure.ac
+@@ -56,7 +56,7 @@ enable_asm_ok=yes
+ 
+ case "$host_os" in
+ 
+-  *linux*)
++  *linux*|*-gnu*)
+   sh_use_lcaps="yes"
+   AC_DEFINE(HOST_IS_LINUX)
+ AC_DEFINE(HAVE_EXT2_IOCTLS)
+--- samhain-4.1.4.orig/configure
 samhain-4.1.4/configure
+@@ -4330,7 +4330,7 @@ enable_asm_ok=yes
+ 
+ case "$host_os" in
+ 
+-  *linux*)
++  *linux*|*-gnu*)
+   sh_use_lcaps="yes"
+   $as_echo "#define HOST_IS_LINUX 1" >>confdefs.h
+ 
diff -Nru samhain-4.1.4/debian/patches/debian.patch 
samhain-4.1.4/debian/patches/debian.patch
--- samhain-4.1.4/debian/patches/debian.patch   1970-01-01 01:00:00.0 
+0100
+++ samhain-4.1.4/debian/patches/debian.patch   2023-08-15 22:46:14.0 
+0200
@@ -0,0 +1,448 @@
+--- samhain-4.1.4.orig/Makefile.in
 samhain-4.1.4/Makefile.in
+@@ -54,7 +54,7 @@ selectconfig = @selectconfig@
+ top_builddir = .
+ 
+ INSTALL = @INSTALL@
+-INSTALL_PROGRAM = @INSTALL@ -s -m 700
++INSTALL_PROGRAM = @INSTALL@ -m 700
+ INSTALL_SHELL = @INSTALL@ -m 700
+ INSTALL_DATA = @INSTALL@ -m 600
+ INSTALL_MAN = @INSTALL@ -m 644
+@@ -229,7 +229,7 @@ PROGRAMS = $(SETPWD) $(STEGIN) $(SAMHAIN
+ #
+ #--
+ 
+-all: $(top_srcdir)/depend.sum $(SETPWD) $(STEGIN) $(SAMHAIN) $(YULECTL) sstrip
++all: $(top_srcdir)/depend.sum $(SETPWD) $(STEGIN) $(SAMHAIN) $(YULECTL)
+ 
+ 
+ #--
+@@ -512,7 +512,7 @@ uninstall-boot: samhain-install.sh
+ #
+ 
+ 
+-install-program: $(PROGRAMS) sstrip
++install-program: $(PROGRAMS) 
+   @$(mkinstalldirs) $(DESTDIR)$(sbindir)
+   @if test x$(mytmpdir) != x; then \
+   $(mkinstalldirs) $(DESTDIR)$(mytmpdir); \
+@@ -525,8 +525,6 @@ install-program: $(PROGRAMS) sstrip
+ echo " $(INSTALL_PROGRAM) $$p $$target"; \
+ $(INSTALL_PROGRAM) $$p $$target; \
+ chmod 0700 $$target; \
+-echo " ./sstrip $$target"; \
+-./sstrip $$target; \
+   else \
+ echo " $(INSTALL_SHELL) $$p $$target"; \
+ $(INSTALL_SHELL) $$p $$target; \
+@@ -1256,29 +1254,26 @@ exepack_fill: $(srcsrc)/exepack_fill.c m
+

Bug#999947: marked as done (swish-e: depends on obsolete pcre3 library)

[Debian Bug Tracking System]

Your message dated Tue, 15 Aug 2023 21:40:39 +
with message-id 
and subject line Bug#47: fixed in swish-e 2.4.7-6.2
has caused the Debian Bug report #47,
regarding swish-e: 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.)


-- 
47: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=47
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: swish-e
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: swish-e
Source-Version: 2.4.7-6.2
Done: Bastian Germann 

We believe that the bug you reported is fixed in the latest version of
swish-e, 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 999...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bastian Germann  (supplier of updated swish-e 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: Tue, 15 Aug 2023 21:36:06 +0200
Source: swish-e
Architecture: source
Version: 2.4.7-6.2
Distribution: unstable
Urgency: medium
Maintainer: Ludovic Drolez 
Changed-By: Bastian Germann 
Closes: 47 1007314
Changes:
 swish-e (2.4.7-6.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Build without pcre. Closes: #47
   * Convert to source format 3.0 (quilt). Closes: #1007314
Checksums-Sha1:
 134482bab80f9bb62952af6e8b112692d06f967c 1637 swish-e_2.4.7-6.2.dsc
 cbc2ca72331bfc3d9fc29cf2f7db8326da76c140 28916 swish-e_2.4.7-6.2.debian.tar.xz
 1335982ba853c4b0aa54413353631e0fab186615 5561 
swish-e_2.4.7-6.2_source.buildinfo
Checksums-Sha256:
 43e0621b468251c51ac372ab9f85aa4ad838a49158ce11263b4477c339c6f6ef 1637 
swish-e_2.4.7-6.2.dsc
 439bd2524de8b74631a41a12f279007391637dae13a75cbae7335392f6ca8ee8 28916 
swish-e_2.4.7-6.2.debian.tar.xz
 78b8540120baf68ed7594036b831371453c9a6a6ecdd20bf2f40dbd6e4a0db7d 5561 
swish-e_2.4.7-6.2_source.buildinfo
Files:
 f7ae44267effcb711cb6418ad4d21c83 1637 web optional swish-e_2.4.7-6.2.dsc
 0a25c5f3e25d7dc6c44eb765903dcab1 28916 web optional 
swish-e_2.4.7-6.2.debian.tar.xz
 e3365a159f13e8d8a21497cc2ee9c086 5561 web optional 
swish-e_2.4.7-6.2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmTb4F4QHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFKCRC/0ansTDOG9LKeT95PrgZOh5EGHtblXzXSJ/
pO0tFJEQW9M7VZdqTt5/QO8srVaxrc93Sq+Bh8C86G4u8xb4O0ZwcYOn7bA37rg8
k9Nfvu7xZt2LhJH2t9ZgKlOB66RzaNvmvWUyFN5hpYu7Tzp7H4Hbr4WEIVqMUYHu
P9JOjsLoDCWaj9Lxyv0KZKlRg07ZEZCr6z+Z2CSYjUFHN6BL1Riiu4O1l3KhELo6
08aWb36ffSQ/hNIKcLFhMjwJhUTv+Wm/KX70PJ7dQqnDYd4UPYA6DPQpuBHgmVvn
hUQvPfaYnFCyxjBbALq9U+7a8l00wsDwAM5PELLw/CB+C0ZU9t3X9BjNn6WBRsJ0
y+hJ4BTyqyNHjLUi0k/Nno2KWUOEeGQEQsJ7L5FWujxjeUsllHEmf9LymNucATKj
7mtmHvY56UHW1X/uSAJtnn/J3or6Y/MJTVBMUwaNMh73z6qOv6JddGUa+N41wSUQ
ylj19QVALdUqQZoWDld+gn1FpSWGL3I=
=WgXj
-END PGP SIGNATURE End Message ---

Bug#1045688: marked as done (FTBFS: Could NOT find zstd (missing: zstd_LIBRARY zstd_INCLUDE_DIR))

[Debian Bug Tracking System]

Your message dated Tue, 15 Aug 2023 21:39:41 +
with message-id 
and subject line Bug#1045688: fixed in rocm-device-libs 5.2.3-3
has caused the Debian Bug report #1045688,
regarding FTBFS: Could NOT find zstd (missing: zstd_LIBRARY zstd_INCLUDE_DIR)
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.)


-- 
1045688: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1045688
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rocm-device-libs
Version: 5.2.3-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Dear maintainer,

rocm-device-libs fails to build from source. From my build log on amd64:

| -- Found Terminfo: /usr/lib/x86_64-linux-gnu/libtinfo.so  
| -- Found ZLIB: /usr/lib/x86_64-linux-gnu/libz.so (found version "1.2.13")  
| -- Could NOT find zstd (missing: zstd_LIBRARY zstd_INCLUDE_DIR) 
| -- Found LibXml2: /usr/lib/x86_64-linux-gnu/libxml2.so (found version 
"2.9.14") 
| -- Could NOT find zstd (missing: zstd_LIBRARY zstd_INCLUDE_DIR) 
| -- Linker detection: GNU ld
| CMake Deprecation Warning at cmake/OCL.cmake:12 (cmake_policy):
|   The OLD behavior for policy CMP0053 will be removed from a future version
|   of CMake.
| 
|   The cmake-policies(7) manual explains that the OLD behaviors of all
|   policies are deprecated and that a policy should be set to OLD only under
|   specific short-term circumstances.  Projects should be ported to the NEW
|   behavior and not rely on setting a policy to OLD.
| Call Stack (most recent call first):
|   CMakeLists.txt:60 (include)
| 
| 
| -- Running constant fold tests
| device-libs CPACK_RPM_PACKAGE_RELEASE now is local
| -- Configuring done (0.6s)
| CMake Error at /usr/lib/llvm-15/lib/cmake/llvm/LLVMExports.cmake:73 
(set_target_properties):
|   The link interface of target "LLVMSupport" contains:
| 
| zstd::libzstd_shared
| 
|   but the target was not found.  Possible reasons include:
| 
| * There is a typo in the target name.
| * A find_package call is missing for an IMPORTED target.
| * An ALIAS target is missing.
| 
| Call Stack (most recent call first):
|   /usr/lib/llvm-15/cmake/LLVMConfig.cmake:336 (include)
|   CMakeLists.txt:38 (find_package)
| 
| 
| -- Generating done (0.0s)

The full build log on riscv64 is available there:
https://buildd.debian.org/status/fetch.php?pkg=rocm-device-libs&arch=riscv64&ver=5.2.3-2&stamp=1691809795&raw=0

Regards
Aurelien
--- End Message ---
--- Begin Message ---
Source: rocm-device-libs
Source-Version: 5.2.3-3
Done: Christian Kastner 

We believe that the bug you reported is fixed in the latest version of
rocm-device-libs, 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 1045...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Christian Kastner  (supplier of updated rocm-device-libs 
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: Tue, 15 Aug 2023 22:37:41 +0200
Source: rocm-device-libs
Architecture: source
Version: 5.2.3-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Deep Learning Team 
Changed-By: Christian Kastner 
Closes: 1045688
Changes:
 rocm-device-libs (5.2.3-3) unstable; urgency=medium
 .
   * Add libzstd-dev to Build-Depends. (Closes: #1045688)
   * Add myself to Uploaders
   * Bump Standards-Version to 4.6.2 (no changes needed)
Checksums-Sha1:
 99d8dc319cb3f504158b4cf709d9a85f34c8de59 2337 rocm-device-libs_5.2.3-3.dsc
 f0317c3ed6d68f149224d5968f609dc29ce7554d 4192 
rocm-device-libs_5.2.3-3.debian.tar.xz
 0600908fd20766e52204872f10d20a662c70a654 5898 
rocm-device-libs_5.2.3-3_source.buildinfo
Checksums-Sha256:
 1ea4047652ccd0556d24d219153fd3e2a4783dd4af0e0ea1cf792c2ae57998a7 2337 
rocm-device-libs_5.2.3-3.dsc
 e918414dcecb3419d3e219c108141ff98d2861c9f304c1d18de906f4c17f73a1 4192 
rocm-device-libs_5.2.3-3.debian.tar.xz
 776de7d0b2277b4259976cf1f492b732219ea495accbd2e0e9f6fd1d03047ac5 5898 
rocm-device-libs_5.2.3-3_source.buildinfo
Files:
 689a7738e682bfb925a90ac09b0203c8 2337 devel optional 
rocm-device-libs_5.2.3-3.dsc
 884a23b311950be8d4331ee01ccd1f67 4192 devel optional 
rocm-device-libs_5.2.3-3.debian.tar.x

Processed: Bug#1045688 marked as pending in rocm-device-libs

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1045688 [src:rocm-device-libs] FTBFS: Could NOT find zstd (missing: 
zstd_LIBRARY zstd_INCLUDE_DIR)
Added tag(s) pending.

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

Bug#1045688: marked as pending in rocm-device-libs

[Christian Kastner]

Control: tag -1 pending

Hello,

Bug #1045688 in rocm-device-libs 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/rocm-team/rocm-device-libs/-/commit/a5eaa27183773abeba027d5f121407b13b587a63


Add libzstd-dev to Build-Depends

Resolves a FTBFS. The last successful build is 11 months ago and didn't use
this directly according to the build log, so I guess something in the
toolchain changed.

Closes: #1045688


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1045688

Bug#999947: swish-e: depends on obsolete pcre3 library

[Bastian Germann]

I am uploading a NMU to fix this. The debdiff is attached.diff -Nru swish-e-2.4.7/conf/example9.pl swish-e-2.4.7/conf/example9.pl
--- swish-e-2.4.7/conf/example9.pl  2023-08-15 22:31:00.0 +0200
+++ swish-e-2.4.7/conf/example9.pl  2009-04-05 03:58:27.0 +0200
@@ -1,4 +1,4 @@
-#!/usr/bin/perl -w
+#!/usr/local/bin/perl -w
 use strict;
 
 # This is a short example that basically does the same
diff -Nru swish-e-2.4.7/debian/changelog swish-e-2.4.7/debian/changelog
--- swish-e-2.4.7/debian/changelog  2023-08-15 22:31:00.0 +0200
+++ swish-e-2.4.7/debian/changelog  2023-08-15 21:36:06.0 +0200
@@ -1,3 +1,11 @@
+swish-e (2.4.7-6.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Build without pcre. Closes: #47
+  * Convert to source format 3.0 (quilt). Closes: #1007314
+
+ -- Bastian Germann   Tue, 15 Aug 2023 21:36:06 +0200
+
 swish-e (2.4.7-6.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru swish-e-2.4.7/debian/control swish-e-2.4.7/debian/control
--- swish-e-2.4.7/debian/control2023-08-15 22:31:00.0 +0200
+++ swish-e-2.4.7/debian/control2023-08-15 21:36:06.0 +0200
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Ludovic Drolez 
 Standards-Version: 4.1.1
-Build-Depends: debhelper (>= 5), zlib1g-dev, perl, libxml2-dev (>= 2.4.3), 
libpcre3-dev (>= 3.4), sharutils, autotools-dev
+Build-Depends: debhelper (>= 5), zlib1g-dev, perl, libxml2-dev (>= 2.4.3), 
sharutils, autotools-dev
 
 Package: swish-e
 Architecture: any
diff -Nru swish-e-2.4.7/debian/files swish-e-2.4.7/debian/files
--- swish-e-2.4.7/debian/files  2009-04-05 03:58:26.0 +0200
+++ swish-e-2.4.7/debian/files  1970-01-01 01:00:00.0 +0100
@@ -1 +0,0 @@
-swish-e_2.4.0-0_i386.deb web optional
diff -Nru swish-e-2.4.7/debian/patches/debian.patch 
swish-e-2.4.7/debian/patches/debian.patch
--- swish-e-2.4.7/debian/patches/debian.patch   1970-01-01 01:00:00.0 
+0100
+++ swish-e-2.4.7/debian/patches/debian.patch   2023-08-15 21:36:06.0 
+0200
@@ -0,0 +1,718 @@
+--- swish-e-2.4.7.orig/conf/example9.pl
 swish-e-2.4.7/conf/example9.pl
+@@ -1,4 +1,4 @@
+-#!/usr/local/bin/perl -w
++#!/usr/bin/perl -w
+ use strict;
+ 
+ # This is a short example that basically does the same
+--- swish-e-2.4.7.orig/man/SWISH-FAQ.1
 swish-e-2.4.7/man/SWISH-FAQ.1
+@@ -131,7 +131,7 @@
+ .IX Title "SWISH-FAQ 1"
+ .TH SWISH-FAQ 1 "2009-04-04" "2.4.7" "SWISH-E Documentation"
+ .SH "NAME"
+-The Swish\-e FAQ \- Answers to Common Questions
++SWISH-FAQ \- The Swish\-e FAQ. Answers to Common Questions
+ .SH "OVERVIEW"
+ .IX Header "OVERVIEW"
+ List of commonly asked and answered questions.  Please review this
+--- swish-e-2.4.7.orig/perl/API.pm
 swish-e-2.4.7/perl/API.pm
+@@ -214,10 +214,17 @@ The list of possible header names can be
+ 
+ =item $swish-Erank_scheme( 0|1 );
+ 
+-Similar to the -R option with the swish-e command line tool. The default
++Like the -R option with the swish-e command line tool. The default
+ ranking scheme is 0. Set it to 1 to experiment with other ranking features.
+ See the SWISH-CONFIG documentation for more on ranking schemes.
+ 
++=item $swish-Ereturn_raw_rank( 0|1 );
++
++Like the -a option with the swish-e command line tool. The default, 0,
++return ranks normalized to the range 0-1000. When enabled by setting to 1, 
++ranks are returned 'raw' (as computed by Swish-e internally during the search)
++and are only guaranteed to be non-negative.
++
+ =back
+ 
+ =head3 Error Handling
+--- swish-e-2.4.7.orig/perl/API.xs
 swish-e-2.4.7/perl/API.xs
+@@ -221,7 +221,9 @@ decode_header_value( swish_handle, heade
+ break;
+ 
+ default:
+-croak(" Unknown header type '%d'\n", header_type );
++croak(" Unknown header type '%ld'\n", (long int)header_type 
); 
++/* constants used in cases above are enum-ed in headers.h */
++
+ }
+ 
+ 
+--- swish-e-2.4.7.orig/perl/Makefile.PL
 swish-e-2.4.7/perl/Makefile.PL
+@@ -211,7 +211,7 @@ sub read_swish_config {
+ 
+ my %config;
+ $config{VERSION} = backtick("$binary --version");
+-$config{LIBS}= backtick("$binary --libs");
++$config{LIBS}= "-L../src/.libs/ -lxml2 ".backtick("$binary --libs");
+ $config{INC} = backtick("$binary --cflags");
+ $config{BINDIR}  = dirname($binary);
+ 
+--- swish-e-2.4.7.orig/prog-bin/spider.pl.in
 swish-e-2.4.7/prog-bin/spider.pl.in
+@@ -35,7 +35,7 @@ use HTML::LinkExtor;
+ use HTML::Tagset;
+ 
+ use vars '$VERSION';
+-$VERSION = sprintf '%d.%02d', q$Revision: 1900 $ =~ /: (\d+)\.(\d+)/;
++$VERSION = '1.0';
+ 
+ use vars '$bit';
+ use constant DEBUG_ERRORS   => $bit = 1;# program errors
+--- swish-e-2.4.7.orig/src/btree.c
 swish-e-2.4.7/src/btree.c
+@@ -321,7 +321,7 @@ unsigned char *key_k;
+ {
+ k = j + (i - j) / 2;
+ key_k = BTREE_KeyData(pg,k);
+-key_len_k = uncompress2(&key_k);
++key

Bug#1049421: Still testing, but possibly fixed

[Andy Dorman]

I have been researching and noticed the source for dns_linode.py appears 
to default to API version 3 if not specified in the credentials file.


I updated our credentials file to add
dns_linode_version = 4

I tried that and found that apparently the version 3 API security key 
didn't work with the version 4 API.


So I created a new key in the V4 API, updated the credentials and it 
looks like it is going to work. With several domains I have to wait 
several minutes for each domain, but the first one has updated successfully.


I apologize if I have caused unnecessary work.

Thanks for maintaining this very useful package.

--
Andy Dorman
Ironic Design, Inc.

Bug#1043224: r-bioc-decoupler: autopkgtest regression

[Andreas Tille]

Am Tue, Aug 15, 2023 at 09:03:24PM +0200 schrieb Andreas Tille:
> > -extra_depends=r-cran-glmnet (>= 4.1.0), \

Argh, got it, its the usual misspelling of versions and should rather be 4.1-0 
...

I need to think about a fix in dh-r whether I can spot those issues 
automatically.

Kind regards
Andreas.

-- 
http://fam-tille.de

Processed: add missing tags

[Debian Bug Tracking System]

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

> tags 1049445 +trixie
Bug #1049445 [massxpert] massxpert build-dependencies unsatisfiable on many 
architectures due to change in daps.
Added tag(s) trixie.
> tags 1049445 +sid
Bug #1049445 [massxpert] massxpert build-dependencies unsatisfiable on many 
architectures due to change in daps.
Added tag(s) sid.
> thanks
Stopping processing here.

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

Bug#1049447: minexpert2 build-dependencies unsatisfiable on many architectures due to change in daps.

[Peter Green]

Package: minexpert2
Version: 8.6.3-1
Severity: serious
Tags: trixie, sid
Justification: rc-policy - packages must be buildable within the same release.
User: debian...@lists.debian.org
Usertags: edos-uninstallable
x-debbugs-cc: lopi...@debian.org

daps 3.3.2+cleaned1-5 moved calibre from suggests to depends.
This means that daps can no longer be installed on architectures
where calibre is not available.

This in turn means that minexpert2 cannot be built on those
architectures. This applies to both the version of minexpert2 in
testing and the version in unstable.

Processed: src:cpp-httplib: fails to migrate to testing for too long: unresolved RC issue

[Debian Bug Tracking System]

Processing control commands:

> close -1 0.13.1+ds-1
Bug #1049446 [src:cpp-httplib] src:cpp-httplib: fails to migrate to testing for 
too long: unresolved RC issue
Marked as fixed in versions cpp-httplib/0.13.1+ds-1.
Bug #1049446 [src:cpp-httplib] src:cpp-httplib: fails to migrate to testing for 
too long: unresolved RC issue
Marked Bug as done
> block -1 by 1041249
Bug #1049446 {Done: Paul Gevers } [src:cpp-httplib] 
src:cpp-httplib: fails to migrate to testing for too long: unresolved RC issue
1049446 was not blocked by any bugs.
1049446 was not blocking any bugs.
Added blocking bug(s) of 1049446: 1041249

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

Bug#1049446: src:cpp-httplib: fails to migrate to testing for too long: unresolved RC issue

[Paul Gevers]

Source: cpp-httplib
Version: 0.11.4+ds-3
Severity: serious
Control: close -1 0.13.1+ds-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1041249

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:cpp-httplib has been trying to migrate for 
31 days [2]. Hence, I am filing this bug. The version in unstable is 
affected by 1041249.


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and trixie, so 
it doesn't affect (old-)stable.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
[2] https://qa.debian.org/excuses.php?package=cpp-httplib



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1049445: massxpert build-dependencies unsatisfiable on many architectures due to change in daps.

[Peter Green]

Package: massxpert
Version: 7.0.0-2
Severity: serious
Justification: rc-policy - packages must be buildable within the same release.
User: debian...@lists.debian.org
Usertags: edos-uninstallable
x-debbugs-cc: lopi...@debian.org

daps 3.3.2+cleaned1-4 moved calibre from suggests to depends.
This means that daps can no longer be installed on architectures
where calibre is not available.

This in turn means that massxpert cannot be built on those
architectures.

Processed: src:gcc-12-cross-mipsen: fails to migrate to testing for too long: blocked by gcc-13-cross-mipsen

[Debian Bug Tracking System]

Processing control commands:

> close -1 4+c1
Bug #1049444 [src:gcc-12-cross-mipsen] src:gcc-12-cross-mipsen: fails to 
migrate to testing for too long: blocked by gcc-13-cross-mipsen
Marked as fixed in versions gcc-12-cross-mipsen/4+c1.
Bug #1049444 [src:gcc-12-cross-mipsen] src:gcc-12-cross-mipsen: fails to 
migrate to testing for too long: blocked by gcc-13-cross-mipsen
Marked Bug as done

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

Bug#1049444: src:gcc-12-cross-mipsen: fails to migrate to testing for too long: blocked by gcc-13-cross-mipsen

[Paul Gevers]

Source: gcc-12-cross-mipsen
Version: 3+c3
Severity: serious
Control: close -1 4+c1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:gcc-12-cross-mipsen has been trying to 
migrate for 31 days [2]. Hence, I am filing this bug. The version in 
unstable has build dependencies on packages from src:gcc-13-cross-mipsen 
which has build dependencies that are not satisfied. gcc-13-cross-mipsen 
can't migrate.


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and trixie, so 
it doesn't affect (old-)stable.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
[2] https://qa.debian.org/excuses.php?package=gcc-12-cross-mipsen



OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: src:git-annex: fails to migrate to testing for too long: FTBFS on armel

[Debian Bug Tracking System]

Processing control commands:

> close -1 10.20230626-1
Bug #1049443 [src:git-annex] src:git-annex: fails to migrate to testing for too 
long: FTBFS on armel
Marked as fixed in versions git-annex/10.20230626-1.
Bug #1049443 [src:git-annex] src:git-annex: fails to migrate to testing for too 
long: FTBFS on armel
Marked Bug as done

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

Bug#1049443: src:git-annex: fails to migrate to testing for too long: FTBFS on armel

[Paul Gevers]

Source: git-annex
Version: 10.20230407-2
Severity: serious
Control: close -1 10.20230626-1
Tags: sid trixie ftbfs
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:git-annex has been trying to migrate for 
31 days [2]. Hence, I am filing this bug. The version in unstable failed 
to build on armel while it built there in the past.


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and trixie, so 
it doesn't affect (old-)stable.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
[2] https://qa.debian.org/excuses.php?package=git-annex



OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: src:orthanc-dicomweb: fails to migrate to testing for too long: FTBFS on s390x

[Debian Bug Tracking System]

Processing control commands:

> close -1 1.14+dfsg-1
Bug #1049442 [src:orthanc-dicomweb] src:orthanc-dicomweb: fails to migrate to 
testing for too long: FTBFS on s390x
Marked as fixed in versions orthanc-dicomweb/1.14+dfsg-1.
Bug #1049442 [src:orthanc-dicomweb] src:orthanc-dicomweb: fails to migrate to 
testing for too long: FTBFS on s390x
Marked Bug as done

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

Bug#1049442: src:orthanc-dicomweb: fails to migrate to testing for too long: FTBFS on s390x

[Paul Gevers]

Source: orthanc-dicomweb
Version: 1.7+dfsg-6
Severity: serious
Control: close -1 1.14+dfsg-1
Tags: sid trixie ftbfs
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:orthanc-dicomweb has been trying to 
migrate for 31 days [2]. Hence, I am filing this bug. The version in 
unstable failed to build on s390x while it built there in the past.


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and trixie, so 
it doesn't affect (old-)stable.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
[2] https://qa.debian.org/excuses.php?package=orthanc-dicomweb



OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: src:sbcl: fails to migrate to testing for too long: triggers autopkgtest issues

[Debian Bug Tracking System]

Processing control commands:

> close -1 2:2.3.7-2
Bug #1049441 [src:sbcl] src:sbcl: fails to migrate to testing for too long: 
triggers autopkgtest issues
Marked as fixed in versions sbcl/2:2.3.7-2.
Bug #1049441 [src:sbcl] src:sbcl: fails to migrate to testing for too long: 
triggers autopkgtest issues
Marked Bug as done

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

Bug#1049441: src:sbcl: fails to migrate to testing for too long: triggers autopkgtest issues

[Paul Gevers]

Source: sbcl
Version: 2:2.2.9-1
Severity: serious
Control: close -1 2:2.3.7-2
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:sbcl has been trying to migrate for 31 
days [2]. Hence, I am filing this bug. The version in unstable triggers 
autopgktest failures on ppc64el in its own tests as well as src:slime.


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and trixie, so 
it doesn't affect (old-)stable.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
[2] https://qa.debian.org/excuses.php?package=sbcl



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1049440: calculix-cgx - build-depends on dropped transitional package.

[Peter Green]

Package: calculix-cgx
Version: 2.17+dfsg-2
Severity: serious
Tags: trixie, sid

calculix-cgx build-depends on libgl1-mesa-glx which is no longer built by the
mesa source package. It is still present in unstable and on a couple of
architectures in testing as a cruft package, but it is completely gone
from most architectures in testing.

Please update your build-dependencies as appropriate.

Processed: src:ruby-appraiser-rubocop: fails to migrate to testing for too long: not installable

[Debian Bug Tracking System]

Processing control commands:

> close -1 1.0.1-2
Bug #1049439 [src:ruby-appraiser-rubocop] src:ruby-appraiser-rubocop: fails to 
migrate to testing for too long: not installable
Marked as fixed in versions ruby-appraiser-rubocop/1.0.1-2.
Bug #1049439 [src:ruby-appraiser-rubocop] src:ruby-appraiser-rubocop: fails to 
migrate to testing for too long: not installable
Marked Bug as done

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

Bug#1049439: src:ruby-appraiser-rubocop: fails to migrate to testing for too long: not installable

[Paul Gevers]

Source: ruby-appraiser-rubocop
Version: 1.0.1-1.1
Severity: serious
Control: close -1 1.0.1-2
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:ruby-appraiser-rubocop has been trying to 
migrate for 32 days [2]. Hence, I am filing this bug. The migration 
software reports the version in unstable is not installable.


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and trixie, so 
it doesn't affect (old-)stable.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
[2] https://qa.debian.org/excuses.php?package=ruby-appraiser-rubocop



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#999947: swish-e: depends on obsolete pcre3 library

[Bastian Germann]

I suggest to remove swish-e. It is dead upstream.

Bug#1049438: r-cran-rgdal: autopkgtest needs update for new version of r-cran-sp

[Paul Gevers]

Source: r-cran-rgdal
Version: 1.6-7+dfsg-1
Severity: serious
X-Debbugs-CC: r-cran...@packages.debian.org
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:r-cran-sp

Dear maintainer(s),

With a recent upload of r-cran-sp the autopkgtest of r-cran-rgdal fails 
in testing when that autopkgtest is run with the binary packages of 
r-cran-sp from unstable. It passes when run with only packages from 
testing. In tabular form:


   passfail
r-cran-sp  from testing1:2.0-0+dfsg-1
r-cran-rgdal   from testing1.6-7+dfsg-1
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of r-cran-sp to 
testing [1]. Of course, r-cran-sp shouldn't just break your autopkgtest 
(or even worse, your package), but your package needs to update to the 
new situation (or you have to help r-cran-sp maintainers to fix the 
issue in their package).


If this is a real problem in your package (and not only in your 
autopkgtest), the right binary package(s) from r-cran-sp should really 
add a versioned Breaks on the unfixed version of (one of your) 
package(s). Note: the Breaks is nice even if the issue is only in the 
autopkgtest as it helps the migration software to figure out the right 
versions to combine in the tests.


More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=r-cran-sp

https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-rgdal/36836475/log.gz

 44s BEGIN TEST test_enforce_xy.R
 44s  44s R version 4.3.1 (2023-06-16) -- "Beagle Scouts"
 44s Copyright (C) 2023 The R Foundation for Statistical Computing
 44s Platform: x86_64-pc-linux-gnu (64-bit)
 44s  44s R is free software and comes with ABSOLUTELY NO WARRANTY.
 44s You are welcome to redistribute it under certain conditions.
 44s Type 'license()' or 'licence()' for distribution details.
 44s  44s R is a collaborative project with many contributors.
 44s Type 'contributors()' for more information and
 44s 'citation()' on how to cite R or R packages in publications.
 44s  44s Type 'demo()' for some demos, 'help()' for on-line help, or
 44s 'help.start()' for an HTML browser interface to help.
 44s Type 'q()' to quit R.
 44s  44s > suppressPackageStartupMessages(library(rgdal))
 44s > set_thin_PROJ6_warnings(TRUE)
 44s > if (new_proj_and_gdal()) {
 44s + get_enforce_xy()
 44s + x0 <- showSRID("EPSG:4326", multiline=TRUE, EPSG_to_init=FALSE)
 44s + cat(x0, "\n")
 44s + set_enforce_xy(FALSE)
 44s + x1 <- showSRID("EPSG:4326", multiline=TRUE, EPSG_to_init=FALSE)
 44s + cat(x1, "\n")
 44s + set_enforce_xy(TRUE)
 44s + x2 <- showSRID("EPSG:4326", multiline=TRUE, EPSG_to_init=FALSE)
 44s + cat(x2, "\n")
 44s + get_enforce_xy()
 44s + y0 <- showSRID("EPSG:4326", multiline=TRUE, EPSG_to_init=FALSE, 
prefer_proj=TRUE)

 44s + cat(y0, "\n")
 44s + showSRID("EPSG:4326", format="PROJ", EPSG_to_init=FALSE, 
prefer_proj=TRUE)

 44s + set_enforce_xy(FALSE)
 44s + y1 <- showSRID("EPSG:4326", multiline=TRUE, EPSG_to_init=FALSE, 
prefer_proj=TRUE)

 44s + cat(y1, "\n")
 44s + showSRID("EPSG:4326", format="PROJ", EPSG_to_init=FALSE, 
prefer_proj=TRUE)

 44s + set_enforce_xy(TRUE)
 44s + y2 <- showSRID("EPSG:4326", multiline=TRUE, EPSG_to_init=FALSE, 
prefer_proj=TRUE)

 44s + cat(y2, "\n")
 44s + showSRID("EPSG:4326", format="PROJ", EPSG_to_init=FALSE, 
prefer_proj=TRUE)

 44s + }
 44s GEOGCRS["WGS 84 (with axis order normalized for visualization)",
 44s ENSEMBLE["World Geodetic System 1984 ensemble",
 44s MEMBER["World Geodetic System 1984 (Transit)",
 44s ID["EPSG",1166]],
 44s MEMBER["World Geodetic System 1984 (G730)",
 44s ID["EPSG",1152]],
 44s MEMBER["World Geodetic System 1984 (G873)",
 44s ID["EPSG",1153]],
 44s MEMBER["World Geodetic System 1984 (G1150)",
 44s ID["EPSG",1154]],
 44s MEMBER["World Geodetic System 1984 (G1674)",
 44s ID["EPSG",1155]],
 44s MEMBER["World Geodetic System 1984 (G1762)",
 44s ID["EPSG",1156]],
 44s MEMBER["World Geodetic System 1984 (G2139)",
 44s ID["EPSG",1309]],
 44s ELLIPSOID["WGS 84",6378137,298.257223563,
 44s LENGTHUNIT["metre",1],
 44s ID["EPSG",7030]],
 44s ENSEMBLEACCURACY[2.0],
 44s ID["EPSG",6326]],
 44s PRIMEM["Greenwich",0,
 44s ANGLEUNIT["degree",0.0174532925199433],
 44s ID["EPSG",8901]],
 44s CS[ellipsoidal,2],
 44s AXIS["geodetic longitude (Lon)",east,
 44s ORDER[1],
 44s ANGLEUNIT["degree",0.0174532925199433,
 44s ID["EPSG",9122]]],
 44s AXIS["geodetic latitude (Lat)",north,
 44s ORDER[2],
 4

Processed: r-cran-rgdal: autopkgtest needs update for new version of r-cran-sp

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:r-cran-sp
Bug #1049438 [src:r-cran-rgdal] r-cran-rgdal: autopkgtest needs update for new 
version of r-cran-sp
Added indication that 1049438 affects src:r-cran-sp

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

Processed: forw

[Debian Bug Tracking System]

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

> forwarded 37 
> https://github.com/gittup/tup/commit/f26bc1e8c0b87d9d351e062c7d27afbbdc53869d
Bug #37 [src:tup] tup: depends on obsolete pcre3 library
Set Bug forwarded-to-address to 
'https://github.com/gittup/tup/commit/f26bc1e8c0b87d9d351e062c7d27afbbdc53869d'.
>
End of message, stopping processing here.

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

Bug#999953: marked as done (sslh: depends on obsolete pcre3 library)

[Debian Bug Tracking System]

Your message dated Tue, 15 Aug 2023 19:23:09 +
with message-id 
and subject line Bug#53: fixed in sslh 1.20-1.1
has caused the Debian Bug report #53,
regarding sslh: 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.)


-- 
53: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=53
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sslh
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: sslh
Source-Version: 1.20-1.1
Done: Bastian Germann 

We believe that the bug you reported is fixed in the latest version of
sslh, 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 999...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bastian Germann  (supplier of updated sslh 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: Tue, 15 Aug 2023 21:02:01 +0200
Source: sslh
Architecture: source
Version: 1.20-1.1
Distribution: unstable
Urgency: medium
Maintainer: Don Armstrong 
Changed-By: Bastian Germann 
Closes: 53
Changes:
 sslh (1.20-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload
   * Drop pcre3 (Closes: #53)
Checksums-Sha1:
 a61c5f1b2d412035e77625fcbdf38376c47d60a0 1784 sslh_1.20-1.1.dsc
 1f76509575738474ff30a2a34f89f65c57b341ab 18280 sslh_1.20-1.1.debian.tar.xz
 67116125eab2bc9a068c11ab688a53c93fbef0e0 5799 sslh_1.20-1.1_source.buildinfo
Checksums-Sha256:
 01f6902530afeb506ade50cd7361bf1b93c208ff76c1e7ead9ca4716ed3759c1 1784 
sslh_1.20-1.1.dsc
 08a831b2f935f002ce5dc99a02a095b7cc18909e68fb8844742e0a8d4cc4dc6c 18280 
sslh_1.20-1.1.debian.tar.xz
 aecee5022168eaede446ed491da5c9e8c1fdb0f4cc95c64d27035a5db18a98ad 5799 
sslh_1.20-1.1_source.buildinfo
Files:
 c8d1609c86dff9835debc786a977f8ec 1784 net optional sslh_1.20-1.1.dsc
 c22bb52f344485e9460ccd67de300075 18280 net optional sslh_1.20-1.1.debian.tar.xz
 f38a797e090bebd50210e8a73e4e 5799 net optional 
sslh_1.20-1.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmTbzAAQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFNNzC/4wTg7cclO04kdJplv9ruXq+ljfikV0ty1i
Q19ncAf7bzpAoJUHajxWUBBaJQhYb+WC4OoCsJf8deUYKH74HUaCwddQkZfMlMZ7
5Ii8GkWyXIOLfbVmTqCr6UjeMtaRhorGCqTFjEHx4R/rztoq1pATyf7lFB1NOxg2
xO1VdOUN0PhotuLXaBigfRqeFkOQzthgiAE2eg5uXYRbcP1qBRIQq9RbDWq61vN9
Tv6Vmn7rTrT6HkphytiNM7NV97Z6M4RQ4PrdJ1bwKOA3qs4cIgN1js4K3A7IYsK9
Thzb84TTB0YtofgS7r5OHORKGIK/kLOE5dDhq1XrVFyieP8X7CSu7rAQ/e32cRAR
uWnWZTZBNUImxJ2fdDG88YuEKzMUWposI3hj0ScgM9ixy9q0co4OIPfPTGpGoZoQ
z0bmJh9RSl2JTnfCuIn+/YgETJMlyG7iFEb9QmxBPWILeK2VWfM/NN31BP1o+US8
NftB27GMFopvAHMV3MEIqa6fpLKNRYM=
=JN5Q
-END PGP SIGNATURE End Message ---

Bug#999953: sslh: depends on obsolete pcre3 library

[Bastian Germann]

I am uploading a NMU to fix this.diff -Nru sslh-1.20/debian/changelog sslh-1.20/debian/changelog
--- sslh-1.20/debian/changelog  2019-09-05 19:04:54.0 +0200
+++ sslh-1.20/debian/changelog  2023-08-15 21:02:01.0 +0200
@@ -1,3 +1,10 @@
+sslh (1.20-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload
+  * Drop pcre3 (Closes: #53)
+
+ -- Bastian Germann   Tue, 15 Aug 2023 21:02:01 +0200
+
 sslh (1.20-1) unstable; urgency=medium
 
   [ Guillaume Delacour ]
diff -Nru sslh-1.20/debian/control sslh-1.20/debian/control
--- sslh-1.20/debian/control2019-09-05 19:04:54.0 +0200
+++ sslh-1.20/debian/control2023-08-15 20:49:18.0 +0200
@@ -4,7 +4,7 @@
 Maintainer: Don Armstrong 
 Build-Depends: debhelper-compat (= 12), libwrap0-dev, binutils, po-debconf,
libio-socket-inet6-perl, libconfig-dev, libcap-dev [linux-any],
-   psmisc, lcov, libpcre3-dev,
+   psmisc, lcov,
init-system-helpers (>= 1.51)
 Standards-Version: 4.4.0
 Homepage: http://www.rutschle.net/tech/sslh/README.html
diff -Nru sslh-1.20/debian/rules sslh-1.20/debian/rules
--- sslh-1.20/debian/rules  2019-09-05 19:04:54.0 +0200
+++ sslh-1.20/debian/rules  2023-08-15 20:58:16.0 +0200
@@ -12,7 +12,7 @@
 endif
 
 override_dh_auto_build:
-   dh_auto_build -- USELIBWRAP=1 $(EXTRA_OPTIONS)
+   dh_auto_build -- USELIBWRAP=1 USELIBPCRE= $(EXTRA_OPTIONS)
 
 override_dh_auto_install:
# auto install fork version, see debian/install for select version

Bug#1043224: r-bioc-decoupler: autopkgtest regression

[Andreas Tille]

Hi Graham

Am Tue, Aug 15, 2023 at 02:14:06PM + schrieb Graham Inggs:
> Control: tags -1 + patch
> 
> The following patch removes the bogus versioned dependency and allows
> the autopkgtests to succeed:

Would you mind explaining what exactly is bogus on versioned
Test-Depends?  These are created automatically.  Thus I'd like
to learn when a versioned dependency is bogus and when not.

Thanks for the patch anyway
Andreas.

> --- a/debian/tests/autopkgtest-pkg-r.conf
> +++ b/debian/tests/autopkgtest-pkg-r.conf
> @@ -1,4 +1,4 @@
> -extra_depends=r-cran-glmnet (>= 4.1.0), \
> +extra_depends=r-cran-glmnet, \
>r-bioc-gsva, \
>r-bioc-summarizedexperiment, \
>r-cran-rpart, \

-- 
http://fam-tille.de

Bug#1043451: marked as done (libopencsd: binary-any FTBFS)

[Debian Bug Tracking System]

Your message dated Tue, 15 Aug 2023 18:58:28 +
with message-id 
and subject line Bug#1043451: fixed in libopencsd 1.4.0-1
has caused the Debian Bug report #1043451,
regarding libopencsd: binary-any 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.)


-- 
1043451: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043451
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libopencsd
Version: 1.3.3-1
Severity: serious
Tags: ftbfs trixie sid

https://buildd.debian.org/status/fetch.php?pkg=libopencsd&arch=riscv64&ver=1.3.3-1&stamp=1691714850&raw=0

...
   debian/rules override_dh_installdocs
make[1]: Entering directory '/<>'
# kick compat 11+ to put docs where we told it
dh_installdocs -X.md5 -X.map
install -m0755 -d debian/libopencsd-dev/usr/share/doc/libopencsd-dev
install -p -m0644 debian/copyright 
debian/libopencsd-dev/usr/share/doc/libopencsd-dev/copyright
install -m0755 -d debian/libopencsd1/usr/share/doc/libopencsd1
install -p -m0644 debian/copyright 
debian/libopencsd1/usr/share/doc/libopencsd1/copyright
install -m0755 -d debian/libopencsd-bin/usr/share/doc/libopencsd-bin
install -p -m0644 debian/copyright 
debian/libopencsd-bin/usr/share/doc/libopencsd-bin/copyright
jdupes -rl debian/libopencsd-doc/usr/share/doc/

could not stat dir debian/libopencsd-doc/usr/share/doc/
No duplicates found.
make[1]: *** [debian/rules:46: override_dh_installdocs] Error 1



The return value of jdupes changed after bookworm to no longer return success 
when
the given paths do not exist, which causes this failure in binary-and builds
(dpkg-buildpackage -B) where binary-all packages are not being built.
--- End Message ---
--- Begin Message ---
Source: libopencsd
Source-Version: 1.4.0-1
Done: Wookey 

We believe that the bug you reported is fixed in the latest version of
libopencsd, 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.
Wookey  (supplier of updated libopencsd 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: Tue, 15 Aug 2023 14:46:24 +0100
Source: libopencsd
Architecture: source
Version: 1.4.0-1
Distribution: unstable
Urgency: medium
Maintainer: Wookey 
Changed-By: Wookey 
Closes: 1043451
Changes:
 libopencsd (1.4.0-1) unstable; urgency=medium
 .
   * New upstream release.
   * Only run doc rule on -indep build [Thanks Aurelien] (Closes: #1043451)
Checksums-Sha1:
 820eac6ff05db7a075185cf7a5de23ebecada794 2058 libopencsd_1.4.0-1.dsc
 b624ec687ee44aec6eb595c9d313fe462be56791 12590350 libopencsd_1.4.0.orig.tar.gz
 7c90c3c48636236de0bd3501051088210adc9f98 4220 libopencsd_1.4.0-1.debian.tar.xz
 ae6ca873109822ff593b7dbc1edc4a1401818d51 9747 
libopencsd_1.4.0-1_amd64.buildinfo
Checksums-Sha256:
 16a46d65becbba4a0fa2c0c7f47a10146a384fed8a6c1114a661f13780a01183 2058 
libopencsd_1.4.0-1.dsc
 e1bb6d8d09e87974cb5ca6db2a13b0e1ba9e51117ca2ed71879df07ff7af4de2 12590350 
libopencsd_1.4.0.orig.tar.gz
 6c035207b371aab7a3bd2ff3534862c5a9cb02cc8b5524900e93ac26842b78e8 4220 
libopencsd_1.4.0-1.debian.tar.xz
 e6a74be53b931f7f143f1ee5fa2a9322de10b12487ac018c0c264fa105cdd6ba 9747 
libopencsd_1.4.0-1_amd64.buildinfo
Files:
 4a24a0d741a079f5710da482841af26a 2058 libs optional libopencsd_1.4.0-1.dsc
 bd2a32f643c229b5718133685a8e5fe0 12590350 libs optional 
libopencsd_1.4.0.orig.tar.gz
 2b3f5a76b8ffa621b44303c149d20bc5 4220 libs optional 
libopencsd_1.4.0-1.debian.tar.xz
 59b22005dfa1c89b6f22e722ee136ee0 9747 libs optional 
libopencsd_1.4.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEER4nvI8Pe/wVWh5yq+4YyUahvnkcFAmTbxaYACgkQ+4YyUahv
nkfO/xAAnRqfpgvKC4Q4MrZfVEjVarZxJSDosLJN/6bECxd3Q9JmeMEXyrNeIz4m
dRrkezL/RJjfPOskAfWZQZHYnrz6AxXME0XEpr/D2CMFc3WlRIp7yvBqYHtb8t6e
nmeq1vYbPxjw85D8av83oJPJXHev/cwvAuFAnQ9qJpWT+2Ayr0TtWPCSQQ3gdPaI
Hy4KlqcOS3bVdBy0/CdRdMRds5yYyJQu/IKP0miTCoKGKAtDEJug82xLFdXt1Ead
k73ojAI+WROHLeGqy9wLCCkpLhrHwBSOsD5cgorXBe+nFIPvPCvgBWF6XBobp1E9
cbRyaZfTXC/V9sS4TaInoVDhlkAo0LymoFewjC0qGtDYOgymyR3MpZdjQCedpV+s
F9E/JmCzXgWExkT6qf8TVxvaPH4qgmXiJ+5qR9QzXjqMsOw0CsYntfWxnnB6QPLJ
lB8RMNRmTNohvIXAJUHXL

Bug#1041556: src:r-cran-checkmate: fails to migrate to testing for too long: autopkgtest regression on 32 bits

[Andreas Tille]

Control: tags -1 upstream

Processed: Re: Bug#1041556: src:r-cran-checkmate: fails to migrate to testing for too long: autopkgtest regression on 32 bits

[Debian Bug Tracking System]

Processing control commands:

> tags -1 upstream
Bug #1041556 [src:r-cran-checkmate] src:r-cran-checkmate: fails to migrate to 
testing for too long: autopkgtest regression on 32 bits
Added tag(s) upstream.

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

Processed (with 1 error): Re: src:r-cran-checkmate: fails to migrate to testing for too long: autopkgtest regression on 32 bits

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/mllg/checkmate/issues/241
Bug #1041556 {Done: Paul Gevers } [src:r-cran-checkmate] 
src:r-cran-checkmate: fails to migrate to testing for too long: autopkgtest 
regression on 32 bits
Set Bug forwarded-to-address to 'https://github.com/mllg/checkmate/issues/241'.
> tags -1 upsteam
Unknown tag/s: upsteam.
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.

> reopen -1
Bug #1041556 {Done: Paul Gevers } [src:r-cran-checkmate] 
src:r-cran-checkmate: fails to migrate to testing for too long: autopkgtest 
regression on 32 bits
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions r-cran-checkmate/2.2.0-1.

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

Bug#1041556: src:r-cran-checkmate: fails to migrate to testing for too long: autopkgtest regression on 32 bits

[Andreas Tille]

Control: forwarded -1 https://github.com/mllg/checkmate/issues/241
Control: tags -1 upsteam
Control: reopen -1

The issue was reported upstream by someone else in April.  There
is no response up to now.

Processed: tralics: diff for NMU version 2.14.4-2.1

[Debian Bug Tracking System]

Processing control commands:

> tags 965847 + patch
Bug #965847 [src:tralics] tralics: Removal of obsolete debhelper compat 5 and 6 
in bookworm
Added tag(s) patch.
> tags 965847 + pending
Bug #965847 [src:tralics] tralics: Removal of obsolete debhelper compat 5 and 6 
in bookworm
Added tag(s) pending.

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

Bug#965847: tralics: diff for NMU version 2.14.4-2.1

[Thiago Marques Siqueira]

Control: tags 965847 + patch
Control: tags 965847 + pending

Dear maintainer,

I've prepared an NMU for tralics (versioned as 2.14.4-2.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.
Note that modern debhelper's remove debian/.gitignore files in
final tarballs.

Regards,
Thiago Marques Siqueira.

diff -Nru tralics-2.14.4/debian/.gitignore tralics-2.14.4/debian/.gitignore
--- tralics-2.14.4/debian/.gitignore2012-04-04 15:21:57.0 +0100
+++ tralics-2.14.4/debian/.gitignore1970-01-01 01:00:00.0 +0100
@@ -1,4 +0,0 @@
-/tralics/
-/tralics.debhelper.log
-/tralics.substvars
-/files
diff -Nru tralics-2.14.4/debian/changelog tralics-2.14.4/debian/changelog
--- tralics-2.14.4/debian/changelog 2012-04-04 15:29:21.0 +0100
+++ tralics-2.14.4/debian/changelog 2023-08-14 22:32:29.0 +0100
@@ -1,3 +1,14 @@
+tralics (2.14.4-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Using new DH level format. Consequently:
+  - debian/compat: removed.
+  - debian/control: changed from 'debhelper' to 'debhelper-compat' in
+Build-Depends field and bumped level to 13.
+  - Closes: #965847
+
+ -- Thiago Marques Siqueira   Mon, 14 Aug 2023 22:32:29 
+0100
+
 tralics (2.14.4-2) unstable; urgency=low
 
   * Fix FTBFS with gcc-4.7 (Closes: #667397)
diff -Nru tralics-2.14.4/debian/compat tralics-2.14.4/debian/compat
--- tralics-2.14.4/debian/compat2012-01-04 14:52:35.0 +
+++ tralics-2.14.4/debian/compat1970-01-01 01:00:00.0 +0100
@@ -1 +0,0 @@
-5
diff -Nru tralics-2.14.4/debian/control tralics-2.14.4/debian/control
--- tralics-2.14.4/debian/control   2012-04-04 15:21:57.0 +0100
+++ tralics-2.14.4/debian/control   2023-08-14 22:32:29.0 +0100
@@ -3,7 +3,7 @@
 Section: tex
 Priority: optional
 Maintainer: Zbigniew Jędrzejewski-Szmek 
-Build-Depends: debhelper (>= 7)
+Build-Depends: debhelper-compat (= 13)
 Standards-Version: 3.9.3
 
 Package: tralics

Bug#1047864: impressive: Crashes at startup: «module 'PIL.Image' has no attribute 'ANTIALIAS'»

[Gunnar Wolf]

Package: impressive
Version: 0.13.1-1
Followup-For: Bug #1047864

Checking the online documentation of Pillow (the fork of PIL that Debian ships),
the ANTIALIAS method has been renamed as LANCZOS:

https://pillow.readthedocs.io/en/stable/releasenotes/2.7.0.html

Antialias renamed to Lanczos

A new LANCZOS constant was added instead of ANTIALIAS.

When ANTIALIAS was initially added, it was the only high-quality filter
based on convolutions. It’s name was supposed to reflect this. Starting from
Pillow 2.7.0 all resize method are based on convolutions. All of them are
antialias from now on. And the real name of the ANTIALIAS filter is Lanczos
filter.

The ANTIALIAS constant is left for backward compatibility and is an alias
for LANCZOS.

This relates to a very old version (2.7.0 is from 2015)... I don't know the
actual details as to when and why this backward compatibility alias was dropped,
but it just is not provided anymore.

I prepared the patch I'm attaching to this mail and tested it (it works
correctly); I'm rebuilding and uploading a NMU for 7 days.

-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-1-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages impressive depends on:
ii  mupdf-tools 1.22.2+ds1-1
ii  poppler-utils   22.12.0-2+b1
ii  python3 3.11.4-5+b1
ii  python3-pil 10.0.0-1
ii  python3-pygame  2.5.0-2

Versions of packages impressive recommends:
ii  ffmpeg 7:6.0-5
ii  mplayer2:1.5+svn38423-2+b1
ii  perl   5.36.0-7
ii  xdg-utils  1.1.3-4.1

Versions of packages impressive suggests:
ii  ghostscript   10.01.2~dfsg-1
pn  latex-beamer  
pn  pdftk 

-- no debconf information
diff --git a/impressive.py b/impressive.py
index 993dcee..9eb564c 100644
--- a/impressive.py
+++ b/impressive.py
@@ -2076,7 +2076,7 @@ class WipeClouds(Wipe):
 img = ImageOps.equalize(ImageOps.autocontrast(img))
 for i in range(self.blur):
 img = img.filter(ImageFilter.BLUR)
-img = img.crop((border, border, img.size[0] - 2 * border, img.size[1] 
- 2 * border)).resize((self.rx, self.ry), Image.ANTIALIAS)
+img = img.crop((border, border, img.size[0] - 2 * border, img.size[1] 
- 2 * border)).resize((self.rx, self.ry), Image.LANCZOS)
 return img2str(img)
 class WipeBrightness1(Wipe):
 """wipe based on the current slide's brightness"""
@@ -3505,16 +3505,16 @@ def RenderPDF(page, MayAdjustResolution, ZoomMode):
 # downsample a supersampled image
 if Supersample and not(ZoomMode):
 img = img.resize((int(float(out[0]) / Supersample + 0.5),
-  int(float(out[1]) / Supersample + 0.5)), 
Image.ANTIALIAS)
+  int(float(out[1]) / Supersample + 0.5)), 
Image.LANCZOS)
 parscale = False  # don't scale again
 
 # perform PAR scaling (required for pdftoppm which doesn't support 
different
 # dpi for horizontal and vertical)
 if parscale:
 if PAR > 1.0:
-img = img.resize((int(img.size[0] / PAR + 0.5), img.size[1]), 
Image.ANTIALIAS)
+img = img.resize((int(img.size[0] / PAR + 0.5), img.size[1]), 
Image.LANCZOS)
 else:
-img = img.resize((img.size[0], int(img.size[1] * PAR + 0.5)), 
Image.ANTIALIAS)
+img = img.resize((img.size[0], int(img.size[1] * PAR + 0.5)), 
Image.LANCZOS)
 
 # crop the overscan (if present)
 if Overscan:
@@ -3567,7 +3567,7 @@ def LoadImage(page, zoom=False, img=None):
 if newsize > img.size:
 filter = Image.BICUBIC
 else:
-filter = Image.ANTIALIAS
+filter = Image.LANCZOS
 return img.resize(newsize, filter)
 
 
@@ -3703,7 +3703,7 @@ def PageImage(page, ZoomMode=False, RenderMode=False):
 sy = OverviewCellY - 2 * OverviewBorder
 if HighQualityOverview:
 t0 = time.time()
-img.thumbnail((sx, sy), Image.ANTIALIAS)
+img.thumbnail((sx, sy), Image.LANCZOS)
 if (time.time() - t0) > 0.5:
 print("Note: Your system seems to be quite slow; 
falling back to a faster,", file=sys.stderr)
 print("  but slightly lower-quality overview page 
rendering mode", file=sys.stderr)
@@ -6409,7 +6409,7 @@ def main():
 if (dummy.size[0] > maxsize[0]) or (dummy.size[1] > maxsize[1]):
 size = ZoomToFit(dummy.size, maxsize, force_int=True)
 if min(size) > 0:
-dummy.thumbnail(size, Image.ANTIALIAS)
+dummy.thumbnail(size, Image.LANCZOS)
 else:
 dummy = None
 if dummy:

Bug#1043418: rust-rustls-webpki - autopkgtest failure, file not found errors.

[Peter Green]

tags 1043418 +patch
thanks


The autopkgtest for rust-rustls-webpki is failing with a bunch of file not 
found errors.


Investigating a bit more, the issue is that the data files in question are
included in the source package, but not in the binary package. I'm not sure if 
this is
a result of your debcargo fork. In any case, I wrote a patch to allow the 
autpkgtest
to use the test data from the source package.

I also ran into a second issue, there is a patch that removes the 
dev-dependencies
needed for the benches and also removes the bench declaration in Cargo.toml, but
cargo has a feature for auto-detecting tests/benches/examples, so it was still
trying to build the benches. I added autobenches=false to disable this.

With the attatched debdiff, the autopkgtest passes. I'd like to see this fixed
fairly quickly, as fixes blocked by the stalled rustls transition are 
threatening
a bunch of packages with auto-removal. If I get no response I'll likely NMU it
next weekend.

diff -Nru rust-rustls-webpki-0.101.3/debian/changelog 
rust-rustls-webpki-0.101.3/debian/changelog
--- rust-rustls-webpki-0.101.3/debian/changelog 2023-08-13 11:24:24.0 
+
+++ rust-rustls-webpki-0.101.3/debian/changelog 2023-08-15 16:01:55.0 
+
@@ -1,3 +1,14 @@
+rust-rustls-webpki (0.101.3-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Add patch 2004 and alter debian/tests/control to use test data from the 
source
+package during autopkgtest as the test data is not included in the binary
+package (Closes: #1043418)
+  * Extend patch 2001 to add autobenches=false so that the benches
+are really disabled
+
+ -- Peter Michael Green   Tue, 15 Aug 2023 16:01:55 +
+
 rust-rustls-webpki (0.101.3-1) unstable; urgency=medium
 
   [ upstream ]
diff -Nru rust-rustls-webpki-0.101.3/debian/patches/2001_bencher.patch 
rust-rustls-webpki-0.101.3/debian/patches/2001_bencher.patch
--- rust-rustls-webpki-0.101.3/debian/patches/2001_bencher.patch
2023-08-13 11:24:24.0 +
+++ rust-rustls-webpki-0.101.3/debian/patches/2001_bencher.patch
2023-08-15 15:56:54.0 +
@@ -1,11 +1,22 @@
-Description: drop bench-only build-dependencies
+Description: drop bench-only build-dependencies and disable benches
 Author: Jonas Smedegaard 
-Last-Update: 2023-07-29
+Author: Peter Michael Green 
+Last-Update: 2023-08-15
 ---
 This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
 a/Cargo.toml
-+++ b/Cargo.toml
-@@ -72,9 +72,6 @@
+Index: rust-rustls-webpki-0.101.3/Cargo.toml
+===
+--- rust-rustls-webpki-0.101.3.orig/Cargo.toml
 rust-rustls-webpki-0.101.3/Cargo.toml
+@@ -22,6 +22,7 @@ name = "rustls-webpki"
+ readme = "README.md"
+ repository = "https://github.com/rustls/webpki";
+ version = "0.101.3"
++autobenches = false
+ 
+ include = [
+ "Cargo.toml",
+@@ -72,9 +73,6 @@ untrusted = "0.7.1"
  
  [dev-dependencies]
  base64 = "0.21"
@@ -15,7 +26,7 @@
  serde = { version = "1.0", features = ["derive"] }
  serde_json = "1.0"
  
-@@ -94,11 +91,6 @@
+@@ -94,11 +92,6 @@ lto = true
  debug-assertions = false
  codegen-units = 1
  
diff -Nru 
rust-rustls-webpki-0.101.3/debian/patches/2004_use_test_data_from_source_package_during_autopkgtest.patch
 
rust-rustls-webpki-0.101.3/debian/patches/2004_use_test_data_from_source_package_during_autopkgtest.patch
--- 
rust-rustls-webpki-0.101.3/debian/patches/2004_use_test_data_from_source_package_during_autopkgtest.patch
   1970-01-01 00:00:00.0 +
+++ 
rust-rustls-webpki-0.101.3/debian/patches/2004_use_test_data_from_source_package_during_autopkgtest.patch
   2023-08-15 16:01:55.0 +
@@ -0,0 +1,43 @@
+Description: allow using an environment variable to specify where to find 
test-data
+ This allows the test data, which is included in the source package, but not 
in the
+ binary package to be used during the autopkgtest.
+Author: Peter Michael Green 
+Last-Update: 2023-08-15
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+diff -urN rustls-webpki-0.101.3/build.rs rustls-webpki-0.101.3/build.rs
+--- rustls-webpki-0.101.3/build.rs 1970-01-01 00:00:00.0 +
 rustls-webpki-0.101.3/build.rs 2023-08-15 17:04:24.774078929 +
+@@ -0,0 +1,7 @@
++use std::env::VarError::NotPresent;
++fn main() {
++println!("cargo:rerun-if-env-changed=SOURCEPACKAGEDIR");
++if std::env::var("SOURCEPACKAGEDIR") == Err(NotPresent) {
++
println!("cargo:rustc-env=SOURCEPACKAGEDIR={}",std::env::current_dir().unwrap().to_str().unwrap());
++}
++}
+diff -urN rustls-webpki-0.101.3/src/signed_data.rs 
rustls-webpki-0.101.3/src/signed_data.rs
+--- rustls-webpki-0.101.3/src/signed_data.rs   2006-07-24 01:21:28.0 
+
 rustls-webpki-0.101.3/src/signed_data.rs   2023-08-15 16:39:39.669690115 
+
+@@ -441,7 +441,8 @@
+ macro_rules! test_file_bytes {
+ ( $file_name:expr ) => {
+

Processed: re: rust-rustls-webpki - autopkgtest failure, file not found errors.

[Debian Bug Tracking System]

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

> tags 1043418 +patch
Bug #1043418 [rust-rustls-webpki] rust-rustls-webpki - autopkgtest failure, 
file not found errors.
Added tag(s) patch.
> thanks
Stopping processing here.

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

Processed: netplan.io: autopkgtest failures with NetworkManager 1.44.0

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://launchpad.net/bugs/1987001
Bug #1049432 [src:netplan.io] netplan.io: autopkgtest failures with 
NetworkManager 1.44.0
Set Bug forwarded-to-address to 'https://launchpad.net/bugs/1987001'.

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

Bug#1049432: netplan.io: autopkgtest failures with NetworkManager 1.44.0

[Jeremy Bícha]

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

Bug#1042980: marked as done (gnome-shell: FTBFS on mips64el, mipsel: perf-* tests fail)

[Debian Bug Tracking System]

Your message dated Tue, 15 Aug 2023 18:25:00 +0100
with message-id 
and subject line Re: Bug#1042980: gnome-shell: FTBFS on mips64el, mipsel: 
perf-* tests fail
has caused the Debian Bug report #1042980,
regarding gnome-shell: FTBFS on mips64el, mipsel: perf-* tests fail
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.)


-- 
1042980: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042980
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnome-shell
Version: 44.3-1
Severity: serious
Tags: ftbfs experimental help
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: debian-m...@lists.debian.org
User: debian-m...@lists.debian.org
Usertags: mips64el mipsel

gnome-shell 44 builds successfully on all release architectures except
mips*el, but fails to build on mips*el. The three perf-* unit tests fail
with exit status 1 and no obvious error messages:



At the moment this is only in experimental, but we want to upload it to
unstable soon, as part of the libmutter-12-0 transition
.

Is gnome-shell practically useful on mips-based hardware, or does it
have hardware requirements that the mips family do not meet in practice?
If nobody really uses it on mips*el, it might be better to do
architecture-specific removals rather than attempting to debug and fix it.

Or, if the mips porting team can confirm that GNOME 43 works in practice
as a desktop environment on mips*el hardware, then it would be useful
to try GNOME 44 from experimental on the same hardware (after building
gnome-shell locally with DEB_BUILD_OPTIONS=nocheck) to check whether
this is a practical problem.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Version: 44.3-3

gnome-shell/experimental is now building successfully on mips(64)el.
We discovered two related bugs which have not yet been fixed:

There is an apparent bug in llvmpipe, which we would normally use to run
the build-time tests: https://bugs.debian.org/1049404

There is also an apparent timing-, thread- or race-condition-related bug
in gnome-shell or one of its dependencies, seen only when using softpipe:
https://bugs.debian.org/1049407

I think neither of these needs to be RC or block the GNOME 44 transition,
since GNOME is primarily designed to be used on hardware GPUs (and
secondarily on fast x86 VMs with working llvmpipe), so we're now skipping
the affected tests on mips(64)el.

On Fri, 04 Aug 2023 at 15:20:08 +0100, Simon McVittie wrote:
> I notice that the perf-* tests are new in version 44, so if the equivalent
> functionality had been failing on mips*el before, we wouldn't know.
> 
> Can you confirm whether gnome-shell/unstable works on a mips*el desktop
> system?

>From comments on
https://salsa.debian.org/gnome-team/gnome-shell/-/merge_requests/71 the
answer is: yes it does work, as long as the mips*el desktop system has a
hardware GPU (in practice it would be from AMD).

> If that works, please try building
> https://salsa.debian.org/gnome-team/gnome-shell/-/merge_requests/71 with
> DEB_BUILD_OPTIONS=nocheck: does that work or crash on a mips*el desktop?

>From comments on
https://salsa.debian.org/gnome-team/gnome-shell/-/merge_requests/71 the
answer is: yes version 44 also works, again with a hardware GPU.

smcv--- End Message ---

Bug#1043559: marked as done (gnome-calculator: open display blank window)

[Debian Bug Tracking System]

Your message dated Tue, 15 Aug 2023 17:19:16 +
with message-id 
and subject line Bug#1043559: fixed in gnome-calculator 1:45~beta-2
has caused the Debian Bug report #1043559,
regarding gnome-calculator: open display blank window
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.)


-- 
1043559: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043559
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-calculator
Version: 1:45~beta-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

This version only show blank window with Gtk-CRITICAL error:

michiaki@debian$ gnome-calculator   
[~]

(gnome-calculator:14244): Gtk-CRITICAL **: 09:44:14.560: Error building 
template class 'MathWindow' for an instance of type 'MathWindow': .:0:0 Invalid 
object type 'AdwToolbarView'

** (gnome-calculator:14244): CRITICAL **: 09:44:14.568: 
math_converter_set_equation: assertion 'self != NULL' failed

** (gnome-calculator:14244): CRITICAL **: 09:44:14.568: 
math_converter_set_category: assertion 'self != NULL' failed

** (gnome-calculator:14244): CRITICAL **: 09:44:14.568: 
math_converter_set_conversion: assertion 'self != NULL' failed

(gnome-calculator:14244): Gtk-CRITICAL **: 09:44:14.568: gtk_grid_attach: 
assertion 'GTK_IS_GRID (grid)' failed

(gnome-calculator:14244): Gtk-CRITICAL **: 09:44:14.572: 
gtk_grid_attach_next_to: assertion 'GTK_IS_GRID (grid)' failed

(gnome-calculator:14244): Gtk-CRITICAL **: 09:44:14.572: 
gtk_menu_button_set_label: assertion 'GTK_IS_MENU_BUTTON (menu_button)' failed

(gnome-calculator:14244): Gtk-CRITICAL **: 09:44:14.572: gtk_widget_hide: 
assertion 'GTK_IS_WIDGET (widget)' failed

** (gnome-calculator:14244): CRITICAL **: 09:44:14.572: 
history_view_set_serializer: assertion 'self != NULL' failed

(gnome-calculator:14244): Gtk-CRITICAL **: 09:44:14.587: 
gtk_menu_button_set_label: assertion 'GTK_IS_MENU_BUTTON (menu_button)' failed

michiaki@debian$


-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.4.0-2-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.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

Versions of packages gnome-calculator depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.40.0-4
ii  libadwaita-1-0   1.3.4-1
ii  libc62.37-7
ii  libgee-0.8-2 0.20.6-1
ii  libglib2.0-0 2.77.1-2
ii  libgtk-4-1   4.10.5+ds-3
ii  libgtksourceview-5-0 5.8.0-2
ii  libmpc3  1.3.1-1
ii  libmpfr6 4.2.0-1
ii  libsoup-3.0-03.4.2-4
ii  libxml2  2.9.14+dfsg-1.3

Versions of packages gnome-calculator recommends:
ii  gvfs  1.51.90-1
ii  yelp  42.2-1

gnome-calculator suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: gnome-calculator
Source-Version: 1:45~beta-2
Done: Jeremy Bícha 

We believe that the bug you reported is fixed in the latest version of
gnome-calculator, 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.
Jeremy Bícha  (supplier of updated gnome-calculator 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: Tue, 15 Aug 2023 13:03:50 -0400
Source: gnome-calculator
Built-For-Profiles: noudeb
Architecture: source
Version: 1:45~beta-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Jeremy Bícha 
Closes: 1043559
Changes:
 gnome-calculator (1:45~beta-2) unstable; urgency=medium
 .
   * Add patch to revert change that requires libadwaita 1.4 (Closes: #1043559)
Checksums-Sha

Bug#1043559: marked as pending in gnome-calculator

[Jeremy Bicha]

Control: tag -1 pending

Hello,

Bug #1043559 in gnome-calculator 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/gnome-team/gnome-calculator/-/commit/d9a428880cdc740c33b079d5f16a6b5d7604f318


Add patch to revert change that requires libadwaita 1.4

Closes: #1043559


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1043559

Processed: Bug#1043559 marked as pending in gnome-calculator

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1043559 [gnome-calculator] gnome-calculator: open display blank window
Added tag(s) pending.

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

Bug#1042965: marked as done (py7zr: Remove unneeded build-depends on deprecate pep517)

[Debian Bug Tracking System]

Your message dated Tue, 15 Aug 2023 17:07:58 +
with message-id 
and subject line Bug#1042965: fixed in py7zr 0.11.3+dfsg-6
has caused the Debian Bug report #1042965,
regarding py7zr: Remove unneeded build-depends on deprecate pep517
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.)


-- 
1042965: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042965
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: py7zr
Version: 0.11.3+dfsg-5
Severity: important
Tags: patch

The pep517 package has been superceded by python-pyproject-hooks.  It
looks like this package added a build-depends on python3-pep517
relatively early in our fielding of the ability to build Debian packages
based on pyproject.toml.  This build dependency is no longer needed and
can be simply removed.

I did test that the package built without it.  See the attached patch.
I am happy to address this as a team upload if you would prefer.  I will
soon be requesting removal of the pep517 package and I intend to bump
the severity of this when I do if it's not resolved by then.

Scott K
diff -Nru py7zr-0.11.3+dfsg/debian/changelog py7zr-0.11.3+dfsg/debian/changelog
--- py7zr-0.11.3+dfsg/debian/changelog  2023-03-25 18:50:07.0 -0400
+++ py7zr-0.11.3+dfsg/debian/changelog  2023-08-02 10:11:34.0 -0400
@@ -1,3 +1,10 @@
+py7zr (0.11.3+dfsg-6) unstable; urgency=medium
+
+  * Team upload.
+  * Drop build-depends on python3-pep517, deprecated, no longer needed
+
+ -- Scott Kitterman   Wed, 02 Aug 2023 10:11:34 -0400
+
 py7zr (0.11.3+dfsg-5) unstable; urgency=medium
 
   [ YOKOTA Hiroshi ]
diff -Nru py7zr-0.11.3+dfsg/debian/control py7zr-0.11.3+dfsg/debian/control
--- py7zr-0.11.3+dfsg/debian/control2023-03-25 18:50:07.0 -0400
+++ py7zr-0.11.3+dfsg/debian/control2023-08-02 10:06:35.0 -0400
@@ -6,7 +6,6 @@
 Build-Depends: debhelper-compat (= 13),
pybuild-plugin-pyproject,
python3-all-dev,
-   python3-pep517,
python3-pyannotate ,
python3-pycryptodome ,
python3-pytest ,
--- End Message ---
--- Begin Message ---
Source: py7zr
Source-Version: 0.11.3+dfsg-6
Done: Sandro Tosi 

We believe that the bug you reported is fixed in the latest version of
py7zr, 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.
Sandro Tosi  (supplier of updated py7zr 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: Tue, 15 Aug 2023 12:44:42 -0400
Source: py7zr
Architecture: source
Version: 0.11.3+dfsg-6
Distribution: unstable
Urgency: medium
Maintainer: Sandro Tosi 
Changed-By: Sandro Tosi 
Closes: 1042965
Changes:
 py7zr (0.11.3+dfsg-6) unstable; urgency=medium
 .
   [ Scott Kitterman ]
   * Drop build-depends on python3-pep517, deprecated, no longer needed;
 Closes: #1042965
Checksums-Sha1:
 04d2006e4d4e868751c160adec04f02398e241e0 2351 py7zr_0.11.3+dfsg-6.dsc
 8b2b9cc2754acc3affcb2830c8ae7ea40a3c510a 9680 py7zr_0.11.3+dfsg-6.debian.tar.xz
 b5f0966d1c8c8285cfd7b308585ce53b70a7760b 9622 
py7zr_0.11.3+dfsg-6_source.buildinfo
Checksums-Sha256:
 24af121b2f3797d18fe9055dc8fa9b0dc32a05517265edaf1126f567f8a21979 2351 
py7zr_0.11.3+dfsg-6.dsc
 6b8ea2c63bfc15d9e055c2785a0fe2b6476ff79df3ddcabead5cdcee6f320a7c 9680 
py7zr_0.11.3+dfsg-6.debian.tar.xz
 6acce00fbc922516e175d687024fd97fa72491208b3e7f420bb3f22789834b7b 9622 
py7zr_0.11.3+dfsg-6_source.buildinfo
Files:
 7cdac53c2f02a8e998312439b53393ec 2351 python optional py7zr_0.11.3+dfsg-6.dsc
 1746e240f811e24d40ffa0d41edfd7df 9680 python optional 
py7zr_0.11.3+dfsg-6.debian.tar.xz
 375d257685b576cce15da4700cdf649f 9622 python optional 
py7zr_0.11.3+dfsg-6_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEufrTGSrz5KUwnZ05h588mTgBqU8FAmTbq4kACgkQh588mTgB
qU+jxA/+Jg156ppvd2SRKblC8ysg/vPnKzft7WrXBNXIfO/KMRAhv8GSFMyNl6qK
dzz6REbpve7SVgA6Ps8NW5MKClDKasfO/Mes/2OuA9W3D5a626ECeibpUtF98H3K
v6AIPhDCSlCi/5AATDxSkQELsM698cX6SY/ldPhCsRvRZAbVyJ6BAMU8qHfeRa4s
l3N4vG8zHo3DqARdEKX+OGqPzMDt49n1ZWdXgdq7oXSQlcC3iVCDMZj5m6ctoVJ1
LyzmsSH3xImibKbu+EyWV7icOWSXP7f3

Bug#1043002: pdm: Please replace python3-pep517 with python3-pyproject-hooks in Depends/Build-Depends

[Scott Kitterman]

pdm is the last remaining blocker for pep517 removal.

Scott K

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

Bug#1037803: marked as done (openfoam: ftbfs with GCC-13)

[Debian Bug Tracking System]

Your message dated Tue, 15 Aug 2023 16:56:05 +
with message-id 
and subject line Bug#1037803: fixed in openfoam 1912.200626-2
has caused the Debian Bug report #1037803,
regarding openfoam: 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.)


-- 
1037803: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037803
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:openfoam
Version: 1912.200626-1
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/openfoam_1912.200626-1_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

[...]
  |  ^~~~
g++ -std=c++11 -pthread -DOPENFOAM=1912 -DWM_DP -DWM_LABEL_SIZE=32 -Wall 
-Wextra -Wold-style-cast -Wnon-virtual-dtor -Wno-unused-parameter 
-Wno-invalid-offsetof -Wno-attributes -Wno-unknown-pragmas -g -O2 
-ffile-prefix-map=/<>/src/OpenFOAM=. -fstack-protector-strong 
-Wformat -Werror=format-security  -O3  -DNoRepository -ftemplate-depth-100 
-I/<>/build/linux64Gcc/src/OpenFOAM -IlnInclude -I. 
-I/<>/src/OpenFOAM/lnInclude 
-I/<>/src/OSspecific/POSIX/lnInclude   -fPIC -c 
primitives/ints/lists/labelList.C -o 
/<>/build/linux64Gcc/src/OpenFOAM/primitives/ints/lists/labelList.o
g++ -std=c++11 -pthread -DOPENFOAM=1912 -DWM_DP -DWM_LABEL_SIZE=32 -Wall 
-Wextra -Wold-style-cast -Wnon-virtual-dtor -Wno-unused-parameter 
-Wno-invalid-offsetof -Wno-attributes -Wno-unknown-pragmas -g -O2 
-ffile-prefix-map=/<>/src/OpenFOAM=. -fstack-protector-strong 
-Wformat -Werror=format-security  -O3  -DNoRepository -ftemplate-depth-100 
-I/<>/build/linux64Gcc/src/OpenFOAM -IlnInclude -I. 
-I/<>/src/OpenFOAM/lnInclude 
-I/<>/src/OSspecific/POSIX/lnInclude   -fPIC -c 
primitives/ints/lists/labelIOList.C -o 
/<>/build/linux64Gcc/src/OpenFOAM/primitives/ints/lists/labelIOList.o
g++ -std=c++11 -pthread -DOPENFOAM=1912 -DWM_DP -DWM_LABEL_SIZE=32 -Wall 
-Wextra -Wold-style-cast -Wnon-virtual-dtor -Wno-unused-parameter 
-Wno-invalid-offsetof -Wno-attributes -Wno-unknown-pragmas -g -O2 
-ffile-prefix-map=/<>/src/OpenFOAM=. -fstack-protector-strong 
-Wformat -Werror=format-security  -O3  -DNoRepository -ftemplate-depth-100 
-I/<>/build/linux64Gcc/src/OpenFOAM -IlnInclude -I. 
-I/<>/src/OpenFOAM/lnInclude 
-I/<>/src/OSspecific/POSIX/lnInclude   -fPIC -c 
primitives/ints/lists/labelListIOList.C -o 
/<>/build/linux64Gcc/src/OpenFOAM/primitives/ints/lists/labelListIOList.o
g++ -std=c++11 -pthread -DOPENFOAM=1912 -DWM_DP -DWM_LABEL_SIZE=32 -Wall 
-Wextra -Wold-style-cast -Wnon-virtual-dtor -Wno-unused-parameter 
-Wno-invalid-offsetof -Wno-attributes -Wno-unknown-pragmas -g -O2 
-ffile-prefix-map=/<>/src/OpenFOAM=. -fstack-protector-strong 
-Wformat -Werror=format-security  -O3  -DNoRepository -ftemplate-depth-100 
-I/<>/build/linux64Gcc/src/OpenFOAM -IlnInclude -I. 
-I/<>/src/OpenFOAM/lnInclude 
-I/<>/src/OSspecific/POSIX/lnInclude   -fPIC -c 
primitives/Scalar/doubleScalar/doubleScalar.C -o 
/<>/build/linux64Gcc/src/OpenFOAM/primitives/Scalar/doubleScalar/doubleScalar.o
g++ -std=c++11 -pthread -DOPENFOAM=1912 -DWM_DP -DWM_LABEL_SIZE=32 -Wall 
-Wextra -Wold-style-cast -Wnon-virtual-dtor -Wno-unused-parameter 
-Wno-invalid-offsetof -Wno-attributes -Wno-unknown-pragmas -g -O2 
-ffile-prefix-map=/<>/src/OpenFOAM=. -fstack-protector-strong 
-Wformat -Werror=format-security  -O3  -DNoRepository -ftemplate-depth-100 
-I/<>/build/linux64Gcc/src/OpenFOAM -IlnInclude -I. 
-I/<>/src/OpenFOAM/lnInclude 
-I/<>/src/OSspecific/POSIX/lnInclude   -fPIC -c 

Bug#1042965: marked as pending in py7zr

[Sandro Tosi]

Control: tag -1 pending

Hello,

Bug #1042965 in py7zr 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/py7zr/-/commit/0706a0a12307c8335a13e94510d271fb529846cd


Drop build-depends on python3-pep517, deprecated, no longer needed; Closes: 
#1042965


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1042965

Processed: Bug#1042965 marked as pending in py7zr

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1042965 [src:py7zr] py7zr: Remove unneeded build-depends on deprecate 
pep517
Added tag(s) pending.

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

Bug#1043122: marked as done (rust-cargo-outdated FTBFS on i386)

[Debian Bug Tracking System]

Your message dated Tue, 15 Aug 2023 16:27:03 +
with message-id 
and subject line Bug#1043122: fixed in rust-cargo-outdated 0.11.1-3
has caused the Debian Bug report #1043122,
regarding rust-cargo-outdated FTBFS 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.)


-- 
1043122: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043122
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-cargo-outdated
Version: 0.11.1-2
Severity: serious
Tags: ftbfs patch

https://buildd.debian.org/status/fetch.php?pkg=rust-cargo-outdated&arch=i386&ver=0.11.1-2%2Bb2&stamp=1691281459&raw=0

...
   Compiling cargo-outdated v0.11.1 (/<>)
 Running `CARGO=/usr/bin/cargo CARGO_BIN_NAME=cargo-outdated 
CARGO_CRATE_NAME=cargo_outdated CARGO_MANIFEST_DIR=/<> 
CARGO_PKG_AUTHORS='Kevin K. :Frederick Z. 
:Ricky H. ' 
CARGO_PKG_DESCRIPTION='Cargo subcommand for displaying when dependencies are 
out of date' CARGO_PKG_HOMEPAGE='' CARGO_PKG_LICENSE=MIT 
CARGO_PKG_LICENSE_FILE='' CARGO_PKG_NAME=cargo-outdated 
CARGO_PKG_REPOSITORY='https://github.com/kbknapp/cargo-outdated.git' 
CARGO_PKG_RUST_VERSION='' CARGO_PKG_VERSION=0.11.1 CARGO_PKG_VERSION_MAJOR=0 
CARGO_PKG_VERSION_MINOR=11 CARGO_PKG_VERSION_PATCH=1 CARGO_PKG_VERSION_PRE='' 
CARGO_PRIMARY_PACKAGE=1 
LD_LIBRARY_PATH='/<>/target/release/deps:/usr/lib' rustc 
--crate-name cargo_outdated --edition=2021 src/main.rs --error-format=json 
--json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type bin 
--emit=dep-info,link -C opt-level=3 -C lto --cfg 'feature="default"' -C 
metadata=10150f9b45772b13 -C extra-filename=-10150f9b45772b13 --out-dir 
/<>/target/i686-unknown-linux-gnu/release/deps --target 
i686-unknown-linux-gnu -L 
dependency=/<>/target/i686-unknown-linux-gnu/release/deps -L 
dependency=/<>/target/release/deps --extern 
anyhow=/<>/target/i686-unknown-linux-gnu/release/deps/libanyhow-c48d3102a0bce80d.rlib
 --extern 
cargo=/<>/target/i686-unknown-linux-gnu/release/deps/libcargo-23903a11b32352ed.rlib
 --extern 
clap=/<>/target/i686-unknown-linux-gnu/release/deps/libclap-73d705ff12e8319b.rlib
 --extern 
env_logger=/<>/target/i686-unknown-linux-gnu/release/deps/libenv_logger-33bade16531972fd.rlib
 --extern 
git2_curl=/<>/target/i686-unknown-linux-gnu/release/deps/libgit2_curl-f2102546b1f137d0.rlib
 --extern 
semver=/<>/target/i686-unknown-linux-gnu/release/deps/libsemver-45b6e27d18e6caff.rlib
 --extern 
serde=/<>/target/i686-unknown-linux-gnu/release/deps/libserde-5f8a4b63cb9ba203.rlib
 --extern 
serde_derive=/<>/target/release/deps/libserde_derive-ec44495953d5a4b9.so
 --extern 
serde_json=/<>/target/i686-unknown-linux-gnu/release/deps/libserde_json-dd1c2fa9619d6755.rlib
 --extern 
tabwriter=/<>/target/i686-unknown-linux-gnu/release/deps/libtabwriter-80d09d35ad315607.rlib
 --extern 
tempfile=/<>/target/i686-unknown-linux-gnu/release/deps/libtempfile-0b2fb83cb6c10a6c.rlib
 --extern 
toml=/<>/target/i686-unknown-linux-gnu/release/deps/libtoml-9784df5cff5c540f.rlib
 -C debuginfo=2 --cap-lints warn -C linker=i686-linux-gnu-gcc -C 
link-arg=-Wl,-z,relro --remap-path-prefix 
/<>=/usr/share/cargo/registry/cargo-outdated-0.11.1 
--remap-path-prefix 
/<>/debian/cargo_registry=/usr/share/cargo/registry -L 
native=/<>/target/i686-unknown-linux-gnu/release/build/rustix-cdf51c8d04ee3483/out
 -L native=/usr/lib/i386-linux-gnu -L native=/usr/lib/i386-linux-gnu -L 
native=/usr/lib/i386-linux-gnu -L native=/usr/lib/i386-linux-gnu`
LLVM ERROR: out of memory
Allocation failed
error: could not compile `cargo-outdated`



Fix:

--- debian/rules.old2023-08-06 09:22:33.248596042 +
+++ debian/rules2023-08-06 09:23:00.012581438 +
@@ -3,8 +3,8 @@
 %:
dh $@ --buildsystem cargo
 
-#lto disabled on these architectures due to address space exhaustion.
-ifneq (,$(filter $(DEB_HOST_ARCH),armhf armel mipsel))
+#lto disabled on 32bit architectures due to address space exhaustion.
+ifeq ($(DEB_HOST_ARCH_BITS), 32)
   LTO=false
 else
   LTO=true
--- End Message ---
--- Begin Message ---
Source: rust-cargo-outdated
Source-Version: 0.11.1-3
Done: Peter Michael Green 

We believe that the bug you reported is fixed in the latest version of
rust-cargo-outdated, 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.
Peter Michael

Bug#1043117: marked as done (rust-zram-generator: FTBFS)

[Debian Bug Tracking System]

Your message dated Tue, 15 Aug 2023 16:05:26 +
with message-id 
and subject line Bug#1043117: fixed in rust-zram-generator 1.1.2-3
has caused the Debian Bug report #1043117,
regarding rust-zram-generator: 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.)


-- 
1043117: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043117
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-zram-generator
Version: 1.1.2-2
Severity: serious
Tags: ftbfs sid trixie
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=rust-zram-generator&arch=amd64&ver=1.1.2-2%2Bb3&stamp=1691270844&raw=0

 dh_dwz -a -O--buildsystem=cargo
dwz: 
debian/systemd-zram-generator/lib/systemd/system-generators/zram-generator: 
Couldn't find DIE at [103d] referenced by DW_AT_abstract_origin from DIE at 
[2853b]
dh_dwz: error: dwz -- 
debian/systemd-zram-generator/lib/systemd/system-generators/zram-generator 
returned exit code 1
dh_dwz: error: Aborting due to earlier error
make: *** [debian/rules:6: binary-arch] Error 25

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: rust-zram-generator
Source-Version: 1.1.2-3
Done: Peter Michael Green 

We believe that the bug you reported is fixed in the latest version of
rust-zram-generator, 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.
Peter Michael Green  (supplier of updated 
rust-zram-generator 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: Tue, 15 Aug 2023 15:11:31 +
Source: rust-zram-generator
Architecture: source
Version: 1.1.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: Peter Michael Green 
Closes: 1043117
Changes:
 rust-zram-generator (1.1.2-3) unstable; urgency=medium
 .
   * Team upload.
   * Package zram-generator 1.1.2 from crates.io using debcargo 2.6.0
   * Apply workaround for dh_dwz crash (Closes: #1043117)
   * Fix autopkgtest (it was previously skipped)
 + Bump dev-dependency on nix to allow version 0.26
 + Don't fail the tests if mount returns "invalid argument", this likely
   indicates a lack of kernel support.
 + Set SYSTEMD_UTIL_DIR=/lib/systemd when running autopkgtest.
Checksums-Sha1:
 5c413938129bc52ec5a93ccaec6dad273af6fd0b 2856 rust-zram-generator_1.1.2-3.dsc
 236b55fde352416579921aa608143c6d19e5c14b 4740 
rust-zram-generator_1.1.2-3.debian.tar.xz
 9a17a7ec82240451c5e501b203cc25443af7e216 13656 
rust-zram-generator_1.1.2-3_source.buildinfo
Checksums-Sha256:
 9e47a238cfa442c75640ffa0024c1d18c57b3c3365efb8feba8ef9c8854df246 2856 
rust-zram-generator_1.1.2-3.dsc
 83d596b2cdb0bf63347d8fc876033a052d8a0657bf56056cad7b81f6203dda33 4740 
rust-zram-generator_1.1.2-3.debian.tar.xz
 440f0c51417c723d65c78793e978ef4df98985a6e56cff70e1906dfe3d55cd75 13656 
rust-zram-generator_1.1.2-3_source.buildinfo
Files:
 c8ed23106c5104de1ec60f2737582c0c 2856 rust optional 
rust-zram-generator_1.1.2-3.dsc
 6a482560c60ac0e387090e450eda54e9 4740 rust optional 
rust-zram-generator_1.1.2-3.debian.tar.xz
 f3c7ed1e813f99a4fddf948ec9033d1e 13656 rust optional 
rust-zram-generator_1.1.2-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAmTblbwUHHBsdWd3YXNo
QGRlYmlhbi5vcmcACgkQDEjqKnqP/XswCw//X3O4eZdU+ubJCgLAbhO1KM9BZ9tp
CDEaL6T+nLhmQiJ87Z2Aqow6xzlYcyrVKLhpieoaOmNBf9p+JW/7XbneR26kQdUQ
0IMsn3+cGUHXO2rcQ2wOI1K0DjETgb3JhYpm/AMIeYhEr4Hv9qYVScVJjoZujvTt
mXioCdgYkggv45JDEriTzxv0dH8x7PxSxl9o8YJZQ0Svp2TqU+bCW3mC8C47lBRS
EO24A21d1w0vDE8yF3va0A++zSEE3a43Wy5mgeLL48359auZMTE1PglHqwUDSNH3
bpTOPwV08XQKCCn/o/+EarG0pn5MIhPGja2NY70ti4K9eI9BVcMcP6JHSX36prss
ibSeO0ZYv31KzFCkdYSPMeExFKHYqBe7SpWTIZLB70ueEgBLVYT8mb3mKJ1N41TF
8/DEKZ6ZpXYGo8fi51F4KoYCnxVS8XB8BeCqqIq0tOOXeX90fctJ2G7KBVuSLR1S
VSLuRcY3GHBCR/q104k1JbgRNF1ddHB0eZ1BF7ZrxM6cLt7ulHrQAGIi/f6YvTa1
5OPMKp5ConE90Grg3RCpWJbUQ1JuOsa7cVloYShHX4+G7sp8JjvJCejhpBgeRaMG
LBOOT552ai5YxOHHnTk9Dz5NcMN34SIUQU7LiDkyGIzCljnEM/zV3ZYmhe7lGf0c
Yos3f+HYX7lDVr4=
=jcZ+
-EN

Bug#1042227: marked as done (rust-erbium-net: FTBFS: unsatisfiable build-dependencies: sbuild-build-depends-main-dummy : Depends: librust-netlink-packet-core-0.4+default-dev but it is not installable)

[Debian Bug Tracking System]

Your message dated Tue, 15 Aug 2023 16:42:40 +0100
with message-id 
and subject line re: rust-erbium-net: FTBFS: unsatisfiable build-dependencies: 
sbuild-build-depends-main-dummy : Depends: 
librust-netlink-packet-core-0.4+default-dev but it is not installable
has caused the Debian Bug report #1042227,
regarding rust-erbium-net: FTBFS: unsatisfiable build-dependencies: 
sbuild-build-depends-main-dummy : Depends: 
librust-netlink-packet-core-0.4+default-dev but it is not installable
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.)


-- 
1042227: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042227
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-erbium-net
Version: 1.0.5-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):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 12), dh-cargo (>= 25), cargo, rustc, 
> libstd-rust-dev, librust-bytes+default-dev (>= 1.2-~~), 
> librust-futures-0.3+default-dev (>= 0.3.8-~~), librust-log-0.4+default-dev, 
> librust-mio-0.8+default-dev, librust-mio-0.8+net-dev, 
> librust-mio-0.8+os-poll-dev, librust-netlink-packet-core-0.4+default-dev, 
> librust-netlink-packet-route-0.12+default-dev, 
> librust-netlink-sys-0.8+default-dev, 
> librust-netlink-sys-0.8+tokio-socket-dev, librust-nix-0.26+default-dev, 
> librust-nix-0.26+net-dev, librust-tokio-1+default-dev (>= 1.8.4-~~), 
> librust-tokio-1+full-dev (>= 1.8.4-~~), build-essential, fakeroot
> Filtered Build-Depends: debhelper (>= 12), dh-cargo (>= 25), cargo, rustc, 
> libstd-rust-dev, librust-bytes+default-dev (>= 1.2-~~), 
> librust-futures-0.3+default-dev (>= 0.3.8-~~), librust-log-0.4+default-dev, 
> librust-mio-0.8+default-dev, librust-mio-0.8+net-dev, 
> librust-mio-0.8+os-poll-dev, librust-netlink-packet-core-0.4+default-dev, 
> librust-netlink-packet-route-0.12+default-dev, 
> librust-netlink-sys-0.8+default-dev, 
> librust-netlink-sys-0.8+tokio-socket-dev, librust-nix-0.26+default-dev, 
> librust-nix-0.26+net-dev, librust-tokio-1+default-dev (>= 1.8.4-~~), 
> librust-tokio-1+full-dev (>= 1.8.4-~~), build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [543 B]
> Get:5 copy:/<>/apt_archive ./ Packages [616 B]
> Fetched 2122 B in 0s (138 kB/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-main-dummy : Depends: 
> librust-netlink-packet-core-0.4+default-dev but it is not installable
>Depends: 
> librust-netlink-packet-route-0.12+default-dev
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build log is available from:
http://qa-logs.debian.net/2023/07/26/rust-erbium-net_1.0.5-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&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230726&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=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/B

Bug#1031834: Updates?

[jayf]

Does anyone have an update on this?  It's been outstanding for a while.
Any ETA on a fix?

Jay Fluharty
Network Analyst
Wheeling-Nippon Steel Inc.
PO Box 635
Follansbee, WV 26037
j...@wheeling-nipponsteel.com
1-304-527-4819

Processed: Re: gstreamer-editing-services1.0: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=8 meson test returned exit code 1

[Debian Bug Tracking System]

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

> forwarded 1042341 
> https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/2481
Bug #1042341 [src:gstreamer-editing-services1.0] gstreamer-editing-services1.0: 
FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 
MESON_TESTTHREADS=8 meson test returned exit code 1
Set Bug forwarded-to-address to 
'https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/2481'.
>
End of message, stopping processing here.

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

Bug#1049384: marked as done (zlib: trying to overwrite '/usr/include/minizip/crypt.h', which is also in package libminizip-dev:amd64 1:1.2.13.dfsg-2)

[Debian Bug Tracking System]

Your message dated Tue, 15 Aug 2023 14:41:01 +
with message-id 
and subject line Bug#1049384: fixed in zlib 1:1.2.13.dfsg-3
has caused the Debian Bug report #1049384,
regarding zlib: trying to overwrite '/usr/include/minizip/crypt.h', which is 
also in package libminizip-dev:amd64 1:1.2.13.dfsg-2
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1049384: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1049384
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: zlib
Version: 1:1.2.13.dfsg-2
Severity: serious
Justification: makes the package in question unusable or mostly so

Dear Maintainer,

zlib1g-dev fails to upgrade due to a file confict with libminizip-dev:

 Preparing to unpack .../zlib1g-dev_1%3a1.2.13.dfsg-2_amd64.deb ...
 Unpacking zlib1g-dev:amd64 (1:1.2.13.dfsg-2) over (1:1.2.13.dfsg-1) ...
 dpkg: error processing archive 
/var/cache/apt/archives/zlib1g-dev_1%3a1.2.13.dfsg-2_amd64.deb (--unpack):
  trying to overwrite '/usr/include/minizip/crypt.h', which is also in package 
libminizip-dev:amd64 1:1.2.13.dfsg-2
 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
 Errors were encountered while processing:
  /var/cache/apt/archives/zlib1g-dev_1%3a1.2.13.dfsg-2_amd64.deb
 E: Sub-process /usr/bin/dpkg returned an error code (1)

Breaks/Replaces or Conflicts seem to be missing.

Kind Regards,

Bas
--- End Message ---
--- Begin Message ---
Source: zlib
Source-Version: 1:1.2.13.dfsg-3
Done: Mark Brown 

We believe that the bug you reported is fixed in the latest version of
zlib, 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.
Mark Brown  (supplier of updated zlib 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: Tue, 15 Aug 2023 14:35:28 +0100
Source: zlib
Architecture: source
Version: 1:1.2.13.dfsg-3
Distribution: unstable
Urgency: low
Maintainer: Mark Brown 
Changed-By: Mark Brown 
Closes: 1049384
Changes:
 zlib (1:1.2.13.dfsg-3) unstable; urgency=low
 .
   * Further fixes to the minizip integration, don't install the minizip
 headers in both -dev packages (closes: #1049384).
Checksums-Sha1:
 33bc9b44b21e001bf711567c56dc73dd7e52e56d 2571 zlib_1.2.13.dfsg-3.dsc
 35440a649a6ab78d7aa03a808d798cfa554eddb5 16688 zlib_1.2.13.dfsg-3.debian.tar.xz
 28c9a03a9b9b1e0b5db34e6a617d285cd4f0367b 6591 
zlib_1.2.13.dfsg-3_source.buildinfo
Checksums-Sha256:
 c8727df9e01126381fb0f2f9aa5f21f09c2e562ec0a0e7b23c0729328b5dfb83 2571 
zlib_1.2.13.dfsg-3.dsc
 ee3d6f346c3efc09ea92a42e1937db602ea5895c383e524ba9048df80069a8b4 16688 
zlib_1.2.13.dfsg-3.debian.tar.xz
 b2045dfdee864dcda4983ddcbcbcaed547a27f884b13df0ee0a4d2bf16ddff25 6591 
zlib_1.2.13.dfsg-3_source.buildinfo
Files:
 8d26bfe2c2647b001687a3ef3a4a869f 2571 libs optional zlib_1.2.13.dfsg-3.dsc
 5e983c94a5c6b2ed4697510f183876d2 16688 libs optional 
zlib_1.2.13.dfsg-3.debian.tar.xz
 fe7a335a39449efdbd90b5d696824242 6591 libs optional 
zlib_1.2.13.dfsg-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQFHBAEBCgAxFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAmTbgJYTHGJyb29uaWVA
ZGViaWFuLm9yZwAKCRAk1otyXVSH0KRsB/oDHmxwPjgGlZIZKPjF8ERGu4xO4HA+
Y8wx2/mpynsGLtyoAx+M+oH68zas7r0r1/mD+aJw4Y5fkS2yGS2qYO+0n5V4aqSq
cnbHv+oR1kXVXm1S9i3RyPQWytulPPXv4eEu9QM4xBwAgJIkZuR6dHTh42CdyxHo
0TZIrs9gkqY6TYjVpJtAyTxR2IvZLl51iaLyk002rR33gRBM3Jy4tT/7wH43xuYR
jA+pttVaLrsl2CChr6+YZWCQWC1N9bjY909zqqgM4iKj3AyNBQJS3v+ZCpTU82Vy
tW5DHl/Tt/6PXrSqK9NdaMKptCmfwke3NKnwzd0riRl5SFkcREbNxHgC
=4RzZ
-END PGP SIGNATURE End Message ---

Bug#1043246: marked as done (libdbus-c++-glib-1-0/experimental: undeclared file conflict with libdbus-c++-1-0v5/unsable)

[Debian Bug Tracking System]

Your message dated Tue, 15 Aug 2023 14:35:03 +
with message-id 
and subject line Bug#1043246: fixed in dbus-c++ 0.9.0-14
has caused the Debian Bug report #1043246,
regarding libdbus-c++-glib-1-0/experimental: undeclared file conflict with 
libdbus-c++-1-0v5/unsable
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.)


-- 
1043246: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043246
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libdbus-c++-glib-1-0
Version: 0.9.0-13
Severity: serious
Control: affects -1 + libdbus-c++-1-0v5
User: debian...@lists.debian.org
Usertags: fileconflict

Both libdbus-c++-glib-1-0/experimental and libdbus-c++-1-0v5/unstable
contain the files /usr/lib/x86_64-linux-gnu/libdbus-c++-glib-1.so.0 and
/usr/lib/x86_64-linux-gnu/libdbus-c++-glib-1.so.0.0.0 without resolving
this conflict via Conflicts, Replaces or diversions. This may result in
an unpack error from dpkg and is a serious issue.

I guess that you meant to restructure the library and that these files
are supposed to be moved between packages. In this case, please add
Breaks and Replaces declarations for libdbus-c++-1-0v5 to
libdbus-c++-glib-1-0.

Helmut
--- End Message ---
--- Begin Message ---
Source: dbus-c++
Source-Version: 0.9.0-14
Done: Bastian Germann 

We believe that the bug you reported is fixed in the latest version of
dbus-c++, 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.
Bastian Germann  (supplier of updated dbus-c++ 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: Tue, 15 Aug 2023 16:03:25 +0200
Source: dbus-c++
Architecture: source
Version: 0.9.0-14
Distribution: experimental
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Bastian Germann 
Closes: 1043245 1043246
Changes:
 dbus-c++ (0.9.0-14) experimental; urgency=medium
 .
   * QA upload.
   * Correct Breaks/Replaces versions. (Closes: #1043245, #1043246)
Checksums-Sha1:
 e8dfeaea186ff860044afc1a014e1d93e0615e28 2173 dbus-c++_0.9.0-14.dsc
 ff0369b22519f82977b57a7b8040e1b7561a2fb9 11916 dbus-c++_0.9.0-14.debian.tar.xz
 cb47a0b3d82e19035dcfb6176094d3ec3b0f6fce 6818 
dbus-c++_0.9.0-14_source.buildinfo
Checksums-Sha256:
 8a56d9c3e793fbbb969cb519d21ae9452fe7b8b59ba25a210d05683adc773814 2173 
dbus-c++_0.9.0-14.dsc
 5d96be659a8ff56a075f7460c92b4280c8a0c994f3632fa39a0be603c058130b 11916 
dbus-c++_0.9.0-14.debian.tar.xz
 3119c0844c1fccb89f1dc76a01d752b5169ccc1fcbf853dede40414a35298312 6818 
dbus-c++_0.9.0-14_source.buildinfo
Files:
 ba582c8fd114dc49cad625148e6cd865 2173 libs optional dbus-c++_0.9.0-14.dsc
 5ae9e19de939b22f650cc874eb01ae90 11916 libs optional 
dbus-c++_0.9.0-14.debian.tar.xz
 a8d464fcc7dcede1f09ad36350358d49 6818 libs optional 
dbus-c++_0.9.0-14_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmTbhnsQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFOiHDACL2+mw/547GKT1gE0BuLM3zeLAU00Ngt51
upR2OZftggvxXkfRw/0r87JbwiJbastsXasmFXkvQWhDwlAYX7EGd37dYUTKTvFS
8+JgSHZ9oBYp1CXcWLcVkVv2HkyiDvQygB8Le52X+KQBWX5BsdhjD6nrvcJ3QYvn
WLQcxbAngdOLq7UXvFDPvjnAjlA929REo2BtE6OvmqmZAS2prkl9eeaIyt9JBpK0
ilppwjMDSGl9Fw3pumf5V5R6idjqb8nrei+8SZg8WI6kOCkJlM1h/Z3xZYC7ZvHj
DecdomsZ5y9CaRGrK+o+RlWL8TGV8XiLjvqScamkwVbBqPXRTDsehXs3RbAomq1G
MPL6De/sZEiy9AwWYJLfOYzCIWsDTos6loX6OGJJPhrEk4xhsMMx9z9wv2bUWjXL
6LyZDSRAmYjUAlIgQpEEmc/AxsPUMBYHoJEn3I2cFXqg6WktWd0lvSHa/Ys94QSH
tjRKUDDc4t6WlXatGU6BkhreNBBkcyY=
=/pvI
-END PGP SIGNATURE End Message ---

Bug#1043245: marked as done (libdbus-c++-ecore-1-0/experimental: undeclared file conflict with libdbus-c++-1-0v5/unsable)

[Debian Bug Tracking System]

Your message dated Tue, 15 Aug 2023 14:35:03 +
with message-id 
and subject line Bug#1043245: fixed in dbus-c++ 0.9.0-14
has caused the Debian Bug report #1043245,
regarding libdbus-c++-ecore-1-0/experimental: undeclared file conflict with 
libdbus-c++-1-0v5/unsable
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.)


-- 
1043245: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043245
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libdbus-c++-ecore-1-0
Version: 0.9.0-13
Severity: serious
Control: affects -1 + libdbus-c++-1-0v5
User: debian...@lists.debian.org
Usertags: fileconflict

Both libdbus-c++-ecore-1-0/experimental and libdbus-c++-1-0v5/unstable
contain the files /usr/lib/x86_64-linux-gnu/libdbus-c++-ecore-1.so.0 and
/usr/lib/x86_64-linux-gnu/libdbus-c++-ecore-1.so.0.0.0 without resolving
this conflict via Conflicts, Replaces or diversions. This may result in
an unpack error from dpkg and is a serious issue.

I guess that you meant to restructure the library and that these files
are supposed to be moved between packages. In this case, please add
Breaks and Replaces declarations for libdbus-c++-1-0v5 to
libdbus-c++-ecore-1-0.

Helmut
--- End Message ---
--- Begin Message ---
Source: dbus-c++
Source-Version: 0.9.0-14
Done: Bastian Germann 

We believe that the bug you reported is fixed in the latest version of
dbus-c++, 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.
Bastian Germann  (supplier of updated dbus-c++ 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: Tue, 15 Aug 2023 16:03:25 +0200
Source: dbus-c++
Architecture: source
Version: 0.9.0-14
Distribution: experimental
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Bastian Germann 
Closes: 1043245 1043246
Changes:
 dbus-c++ (0.9.0-14) experimental; urgency=medium
 .
   * QA upload.
   * Correct Breaks/Replaces versions. (Closes: #1043245, #1043246)
Checksums-Sha1:
 e8dfeaea186ff860044afc1a014e1d93e0615e28 2173 dbus-c++_0.9.0-14.dsc
 ff0369b22519f82977b57a7b8040e1b7561a2fb9 11916 dbus-c++_0.9.0-14.debian.tar.xz
 cb47a0b3d82e19035dcfb6176094d3ec3b0f6fce 6818 
dbus-c++_0.9.0-14_source.buildinfo
Checksums-Sha256:
 8a56d9c3e793fbbb969cb519d21ae9452fe7b8b59ba25a210d05683adc773814 2173 
dbus-c++_0.9.0-14.dsc
 5d96be659a8ff56a075f7460c92b4280c8a0c994f3632fa39a0be603c058130b 11916 
dbus-c++_0.9.0-14.debian.tar.xz
 3119c0844c1fccb89f1dc76a01d752b5169ccc1fcbf853dede40414a35298312 6818 
dbus-c++_0.9.0-14_source.buildinfo
Files:
 ba582c8fd114dc49cad625148e6cd865 2173 libs optional dbus-c++_0.9.0-14.dsc
 5ae9e19de939b22f650cc874eb01ae90 11916 libs optional 
dbus-c++_0.9.0-14.debian.tar.xz
 a8d464fcc7dcede1f09ad36350358d49 6818 libs optional 
dbus-c++_0.9.0-14_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmTbhnsQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFOiHDACL2+mw/547GKT1gE0BuLM3zeLAU00Ngt51
upR2OZftggvxXkfRw/0r87JbwiJbastsXasmFXkvQWhDwlAYX7EGd37dYUTKTvFS
8+JgSHZ9oBYp1CXcWLcVkVv2HkyiDvQygB8Le52X+KQBWX5BsdhjD6nrvcJ3QYvn
WLQcxbAngdOLq7UXvFDPvjnAjlA929REo2BtE6OvmqmZAS2prkl9eeaIyt9JBpK0
ilppwjMDSGl9Fw3pumf5V5R6idjqb8nrei+8SZg8WI6kOCkJlM1h/Z3xZYC7ZvHj
DecdomsZ5y9CaRGrK+o+RlWL8TGV8XiLjvqScamkwVbBqPXRTDsehXs3RbAomq1G
MPL6De/sZEiy9AwWYJLfOYzCIWsDTos6loX6OGJJPhrEk4xhsMMx9z9wv2bUWjXL
6LyZDSRAmYjUAlIgQpEEmc/AxsPUMBYHoJEn3I2cFXqg6WktWd0lvSHa/Ys94QSH
tjRKUDDc4t6WlXatGU6BkhreNBBkcyY=
=/pvI
-END PGP SIGNATURE End Message ---

Processed (with 2 errors): Re: gstreamer-editing-services1.0: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=8 meson test returned exit code 1

[Debian Bug Tracking System]

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

> forwarded 1042341
Unknown command or malformed arguments to command.
> https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/2481
Unknown command or malformed arguments to command.
> tags 1042341 upstream
Bug #1042341 [src:gstreamer-editing-services1.0] gstreamer-editing-services1.0: 
FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 
MESON_TESTTHREADS=8 meson test returned exit code 1
Added tag(s) upstream.
>
End of message, stopping processing here.

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

Bug#1043002: pdm: Please replace python3-pep517 with python3-pyproject-hooks in Depends/Build-Depends

[Scott Kitterman]

On August 15, 2023 1:51:54 PM UTC, Jeroen Dekkers  wrote:
>On Tue, 15 Aug 2023 15:08:11 +0200,
>Scott Kitterman wrote:
>>
>> On Tuesday, August 15, 2023 3:53:07 AM EDT Andreas Tille wrote:
>> > Hi Scott,
>> >
>> > Am Mon, Aug 14, 2023 at 02:06:42PM + schrieb Scott Kitterman:
>> >
>> > > those are all binary without source.  That's a problem.
>> >
>> > Given your role as ftpmaster you definitely have more experience than I
>> > in this field.  I personally was thinking more in the line of binary
>> > data we can not avoid in some cases.  This is a bit in the line with
>> > Rdata decision[1] where those binary data files are documented in
>> > debian/README.source.
>> >
>> > My point is just: If we remove those data files (which are IMHO harmless
>> > since these are not executd but used as input in tests - please correct
>> > me if I'm wrong) we can not test the package.  Removing the files
>> > prevents testing and thus we can not know whether the package we deliver
>> > will work.  I've actually shown that not all tests are working but
>> > stopped investigating this further.
>>
>> Even if they are used as data (I didn't check), they are, in fact, binary
>> blobs of code by our definition and that requires the corresponding source.
>
>They are zip files containing python source code. It is possible to include
>compiled C extensions in wheels, but I checked and these wheels are all pure
>python, so no binary blobs are included.

In Debian terms, it's not the preferred form for modification, so it's not 
source.  In this regard DFSG goes farther than some software licenses.

Scott K

Bug#1049421: python3-certbot-dns-linode: Severe - Unable to renew certs. Linode API v3 no longer active. Use API v4

[Michael Alan Dorman]

Package: python3-certbot-dns-linode
Version: 2.1.0-1
Severity: grave
Tags: upstream
Justification: renders package unusable

Dear Maintainer,

Trying to renew multiple domains on several servers results in the following:

Exception: Linode api error: [{'ERRORMESSAGE': 'Linode API v3 is no longer 
active. Please use Linode API v4: https://www.linode.com/docs/api', 
'ERRORCODE': 16}]

This began about a week ago but I just noticed it this morning.

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 4.16.0-1-686-pae (SMP w/2 CPU threads)
Kernel taint flags: TAINT_WARN
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: sysvinit (via /sbin/init)

Versions of packages python3-certbot-dns-linode depends on:
ii  certbot  2.1.0-4
ii  python3  3.11.4-5
ii  python3-acme 2.1.0-1
ii  python3-certbot [python3-certbot-abi-2]  2.1.0-4
ii  python3-lexicon  3.11.7-1
ii  python3-pkg-resources68.0.0-1

python3-certbot-dns-linode recommends no packages.

python3-certbot-dns-linode suggests no packages.

-- no debconf information

Bug#1043223: marked as done (r-cran-biocmanager: autopkgtest needs update for r-bioc-biocversion)

[Debian Bug Tracking System]

Your message dated Tue, 15 Aug 2023 16:14:06 +0200
with message-id 
and subject line Re: Bug#1043223: r-cran-biocmanager: autopkgtest needs update 
for r-bioc-biocversion
has caused the Debian Bug report #1043223,
regarding r-cran-biocmanager: autopkgtest needs update for r-bioc-biocversion
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.)


-- 
1043223: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043223
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-biocmanager
Version: 1.30.21.1+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: needs-update

Hi Maintainer

Since the upload of r-bioc-biocversion 3.17.1-1, the autopkgtests of
r-cran-biocmanager are failing [1].  I've copied what I hope is the
relevant part of the log below.

Regards
Graham


[1] https://ci.debian.net/packages/r/r-cran-biocmanager/testing/amd64/


 38s > test_check("BiocManager")
 58s [ FAIL 1 | WARN 1 | SKIP 24 | PASS 84 ]
 58s
 58s == Skipped tests (24)
==
 59s * On CRAN (23): 'test_install.R:27:5', 'test_install.R:45:5',
 59s   'test_install.R:204:5', 'test_repositories.R:5:5',
 59s   'test_repositories.R:14:5', 'test_repositories.R:20:5',
 59s   'test_repositories.R:26:5', 'test_repositories.R:33:5',
 59s   'test_repositories.R:43:5', 'test_repositories.R:118:5',
 59s   'test_repositories.R:127:5', 'test_repositories.R:165:5',
 59s   'test_version.R:17:5', 'test_version.R:39:5', 'test_version.R:92:5',
 59s   'test_version.R:107:5', 'test_version.R:147:5', 'test_version.R:194:5',
 59s   'test_version.R:235:5', 'test_version.R:246:5', 'test_version.R:277:5',
 59s   'test_version.R:328:5', 'test_version.R:387:5'
 59s * too idiosyncratic for standardized testing (1): 'test_install.R:164:5'
 59s
 59s == Failed tests

 59s -- Failure ('test_install.R:355:5'): install() without package
names passes ... to install.packages --
 59s `object` is not TRUE
 59s
 59s `actual`:   FALSE
 59s `expected`: TRUE
 59s
 59s [ FAIL 1 | WARN 1 | SKIP 24 | PASS 84 ]
--- End Message ---
--- Begin Message ---
Hi Graham,

thanks for the patch.  There was a race condition between you filing
the bug and me realising the issue on Salsa-CI.  Since the bug is
closed in 1.30.22+dfsg-2 I'm just closing this bug.

Thanks a lot for beeing that fast to spot an issue and providing a patch
   Andreas.

-- 
http://fam-tille.de--- End Message ---

Bug#1043224: r-bioc-decoupler: autopkgtest regression

[Graham Inggs]

Control: tags -1 + patch

The following patch removes the bogus versioned dependency and allows
the autopkgtests to succeed:

--- a/debian/tests/autopkgtest-pkg-r.conf
+++ b/debian/tests/autopkgtest-pkg-r.conf
@@ -1,4 +1,4 @@
-extra_depends=r-cran-glmnet (>= 4.1.0), \
+extra_depends=r-cran-glmnet, \
   r-bioc-gsva, \
   r-bioc-summarizedexperiment, \
   r-cran-rpart, \

Regards
Graham

Processed: r-bioc-decoupler: autopkgtest regression

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #1043224 [src:r-bioc-decoupler] r-bioc-decoupler: autopkgtest regression
Added tag(s) patch.

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

Bug#1043002: pdm: Please replace python3-pep517 with python3-pyproject-hooks in Depends/Build-Depends

[Jeroen Dekkers]

On Tue, 15 Aug 2023 15:08:11 +0200,
Scott Kitterman wrote:
>
> On Tuesday, August 15, 2023 3:53:07 AM EDT Andreas Tille wrote:
> > Hi Scott,
> >
> > Am Mon, Aug 14, 2023 at 02:06:42PM + schrieb Scott Kitterman:
> >
> > > those are all binary without source.  That's a problem.
> >
> > Given your role as ftpmaster you definitely have more experience than I
> > in this field.  I personally was thinking more in the line of binary
> > data we can not avoid in some cases.  This is a bit in the line with
> > Rdata decision[1] where those binary data files are documented in
> > debian/README.source.
> >
> > My point is just: If we remove those data files (which are IMHO harmless
> > since these are not executd but used as input in tests - please correct
> > me if I'm wrong) we can not test the package.  Removing the files
> > prevents testing and thus we can not know whether the package we deliver
> > will work.  I've actually shown that not all tests are working but
> > stopped investigating this further.
>
> Even if they are used as data (I didn't check), they are, in fact, binary
> blobs of code by our definition and that requires the corresponding source.

They are zip files containing python source code. It is possible to include
compiled C extensions in wheels, but I checked and these wheels are all pure
python, so no binary blobs are included.

Kind regards,

Jeroen Dekkers

Bug#1043223: r-cran-biocmanager: autopkgtest needs update for r-bioc-biocversion

[Graham Inggs]

Control: tags -1 + patch

The failing test "install() without package names" was previously
skipped, but enabled again [1] in a recent upload.

The reason the autopkgtests pass in testing [2] is that testing
Bioconductor version 3.16 with R version 4.3 is considered a
misconfiguration, and several tests are skipped.  See test output
below.

The following patch will skip the failing test unconditionally:

--- a/tests/testthat/test_install.R
+++ b/tests/testthat/test_install.R
@@ -329,7 +329,7 @@
 })

 test_that("install() without package names passes ... to install.packages", {
-.skip_if_misconfigured()
+skip()
 object <- FALSE
 with_mock(
 available.packages = function(...) {

Regards
Graham


[1] 
https://salsa.debian.org/r-pkg-team/r-cran-biocmanager/-/commit/9f65e83f51ad6b1b9e8edc05fa92c7bf86e587e7
[2] 
https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-biocmanager/36777045/log.gz


 37s > library(testthat)
 37s > library(BiocManager)
 37s Bioconductor version '3.16' requires R version '4.2'; use
`version = '3.17'`
 37s   with R version 4.3; see https://bioconductor.org/install
 37s Bioconductor version '3.16' is out-of-date; the current release
version '3.17'
 37s   is available with R version '4.3'; see https://bioconductor.org/install
 37s >
 37s > test_check("BiocManager")
 84s [ FAIL 0 | WARN 0 | SKIP 27 | PASS 72 ]
 84s
 84s == Skipped tests (27)
==
 85s * On CRAN (8): 'test_repositories.R:33:5', 'test_repositories.R:127:5',
 85s   'test_repositories.R:165:5', 'test_version.R:17:5',
'test_version.R:39:5',
 85s   'test_version.R:235:5', 'test_version.R:246:5', 'test_version.R:277:5'
 85s * mis-configuration, R 4.3.1, Bioconductor 3.16 (18):
'test_install.R:26:5',
 85s   'test_install.R:44:5', 'test_install.R:203:5', 'test_install.R:332:5',
 85s   'test_repositories.R:4:5', 'test_repositories.R:13:5',
 85s   'test_repositories.R:19:5', 'test_repositories.R:25:5',
 85s   'test_repositories.R:42:5', 'test_repositories.R:53:5',
 85s   'test_repositories.R:117:5', 'test_valid.R:4:5', 'test_version.R:91:5',
 85s   'test_version.R:106:5', 'test_version.R:146:5', 'test_version.R:193:5',
 85s   'test_version.R:327:5', 'test_version.R:386:5'
 85s * too idiosyncratic for standardized testing (1): 'test_install.R:164:5'
 85s
 85s [ FAIL 0 | WARN 0 | SKIP 27 | PASS 72 ]

Processed: r-cran-biocmanager: autopkgtest needs update for r-bioc-biocversion

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #1043223 [src:r-cran-biocmanager] r-cran-biocmanager: autopkgtest needs 
update for r-bioc-biocversion
Added tag(s) patch.

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

Bug#1043002: pdm: Please replace python3-pep517 with python3-pyproject-hooks in Depends/Build-Depends

[Scott Kitterman]

On Tuesday, August 15, 2023 3:53:07 AM EDT Andreas Tille wrote:
> Hi Scott,
> 
> Am Mon, Aug 14, 2023 at 02:06:42PM + schrieb Scott Kitterman:
> > >Before I upload I'd like to ask for reviewing this patch and opinions
> > >about the test suite errors.  While these possibly occure in previous
> > >versions (which I did not tested) we might consider ignoring just the
> > >failing tests.  I need to admit that I did not went through the list of
> > >single failures - may be there is a chance of easy fixes for some of
> > >them.  I simply wanted to discuss the reintroduction of the artifacts
> > >and my patch first.
> > 
> > With the exception of future_fstrings
> 
> I think there is also the souce for demo included.
> 
> > those are all binary without source.  That's a problem.
> 
> Given your role as ftpmaster you definitely have more experience than I
> in this field.  I personally was thinking more in the line of binary
> data we can not avoid in some cases.  This is a bit in the line with
> Rdata decision[1] where those binary data files are documented in
> debian/README.source.
> 
> My point is just: If we remove those data files (which are IMHO harmless
> since these are not executd but used as input in tests - please correct
> me if I'm wrong) we can not test the package.  Removing the files
> prevents testing and thus we can not know whether the package we deliver
> will work.  I've actually shown that not all tests are working but
> stopped investigating this further.

Even if they are used as data (I didn't check), they are, in fact, binary 
blobs of code by our definition and that requires the corresponding source.

> > It's probably okay if you add the corresponding source somewhere in the
> > package.
> We probably have some source packages inside Debian - may be in
> different versions.  I need to admit that I intended to do a "quick fix
> of a simple bug that affects some Debian Med packages" but realised that
> I'm possibly opening a can of worms.  The simplest solution to fulfill
> my needs would be probably to revert my change to run the tests and be
> done.  However, I'm not sure whetherr this is in the interest of the
> users of this package.  I'm absolutely not able time-wise to povide
> sources and reconstruct all those *.whl files *and* in addition track
> down the test suite errors.  This is a team package and if the team
> decides we should go without testing I can do an according upload.
> However, my prefered path would to document the issue of some binary
> data properly an test what upstream expects to be tested.

i think this is definitely more complicated than you want to take on casually.  
I don't think it's required to actually rebuild the wheels.  If you provide 
the source, the DFSG is happy.  You have to be able to rebuild it, but you 
aren't required to do it.

It might, however, be simpler in the long run to just depend on those packages 
and build wheels from those (a Debian binary package has enough in it 
generally to build a wheel from it).

I agree it'd be better in the long run to run the tests, but that may be more 
than you want to take on right now.

Scott K



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

Bug#1049384: zlib: trying to overwrite '/usr/include/minizip/crypt.h', which is also in package libminizip-dev:amd64 1:1.2.13.dfsg-2

[Sebastiaan Couwenberg]

On 8/15/23 14:07, Adrian Bunk wrote:

On Tue, Aug 15, 2023 at 05:28:25AM +0200, Bas Couwenberg wrote:

zlib1g-dev fails to upgrade due to a file confict with libminizip-dev:

  Preparing to unpack .../zlib1g-dev_1%3a1.2.13.dfsg-2_amd64.deb ...
  Unpacking zlib1g-dev:amd64 (1:1.2.13.dfsg-2) over (1:1.2.13.dfsg-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/zlib1g-dev_1%3a1.2.13.dfsg-2_amd64.deb (--unpack):
   trying to overwrite '/usr/include/minizip/crypt.h', which is also in package 
libminizip-dev:amd64 1:1.2.13.dfsg-2
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/zlib1g-dev_1%3a1.2.13.dfsg-2_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

Breaks/Replaces or Conflicts seem to be missing.


No, the bug is that the /usr/include/minizip headers are shipped in both
zlib1g-dev and libminizip-dev, and that they should never have been in 
zlib1g-dev.


Yes, usr/include/* in zlib1g-dev.install is problematic because that 
also matches usr/include/minizip.


This may suffice to resolve that:

--- debian/rules.orig   2023-08-15 14:23:13.505744473 +0200
+++ debian/rules2023-08-15 14:22:00.029708908 +0200
@@ -207,6 +207,7 @@
dh_installdocs -a
dh_installexamples -a
dh_install -a --sourcedir=debian/tmp
+   $(RM) -r debian/zlib1g-dev/usr/include/minizip
dh_installman -a
dh_lintian -a
dh_link -a

Kind Regards,

Bas

--
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Bug#1039591: logcheck: prompting due to modified conffiles which were not modified by the user: /etc/logcheck/header.txt

[Santiago Vila]

El 29/6/23 a las 22:20, Richard Lewis escribió:


for reasons unknown, when debian introduced header.txt in 2014 it shipped 
header.txt in /usr/share/logcheck and copied it to /etc/logcheck in postinst on 
initial install. Only the file in /etc is ever used.


Hello. There was indeed a good reason for that: The conffile mechanism should 
only be used
when there is a default which satisfies everybody (or almost everybody).

In this case there will be people who will be happy with the default header.txt,
but there will also be people (like me) who prefer not to have any header.txt 
at all.

In my opinion header.txt is one of those files where it is much better
not to be handled via the conffile mechanism. I've just filed a separate bug
for that (#1049412), since deletion is currently unsupported and it should be.

Note: I see there is a "md5sum framework" in place to update the file in
case it's necessary. I have a similar md5sum framework in base-files.postinst
and it works very well. With this framework already in place, I would hope
that switching to the old way of handling header.txt should be easy enough.

Thanks.

Bug#1049384: zlib: trying to overwrite '/usr/include/minizip/crypt.h', which is also in package libminizip-dev:amd64 1:1.2.13.dfsg-2

[Sebastiaan Couwenberg]

On 8/15/23 14:24, Sebastiaan Couwenberg wrote:

On 8/15/23 14:07, Adrian Bunk wrote:

On Tue, Aug 15, 2023 at 05:28:25AM +0200, Bas Couwenberg wrote:

zlib1g-dev fails to upgrade due to a file confict with libminizip-dev:

  Preparing to unpack .../zlib1g-dev_1%3a1.2.13.dfsg-2_amd64.deb ...
  Unpacking zlib1g-dev:amd64 (1:1.2.13.dfsg-2) over (1:1.2.13.dfsg-1) 
...
  dpkg: error processing archive 
/var/cache/apt/archives/zlib1g-dev_1%3a1.2.13.dfsg-2_amd64.deb 
(--unpack):
   trying to overwrite '/usr/include/minizip/crypt.h', which is also 
in package libminizip-dev:amd64 1:1.2.13.dfsg-2

  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/zlib1g-dev_1%3a1.2.13.dfsg-2_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

Breaks/Replaces or Conflicts seem to be missing.


No, the bug is that the /usr/include/minizip headers are shipped in both
zlib1g-dev and libminizip-dev, and that they should never have been in 
zlib1g-dev.


Yes, usr/include/* in zlib1g-dev.install is problematic because that 
also matches usr/include/minizip.


This may suffice to resolve that:

--- debian/rules.orig   2023-08-15 14:23:13.505744473 +0200
+++ debian/rules    2023-08-15 14:22:00.029708908 +0200
@@ -207,6 +207,7 @@
     dh_installdocs -a
     dh_installexamples -a
     dh_install -a --sourcedir=debian/tmp
+   $(RM) -r debian/zlib1g-dev/usr/include/minizip
     dh_installman -a
     dh_lintian -a
     dh_link -a


This might be better:

--- debian/zlib1g-dev.install.orig  2023-08-15 14:27:22.181864870 +0200
+++ debian/zlib1g-dev.install   2023-08-15 14:27:01.693854494 +0200
@@ -1,4 +1,4 @@
-usr/include/*
+usr/include/*.h
 usr/lib/*/libz.a
 usr/lib/*/libz.so
 usr/share/man/man3/*

Kind Regards,

Bas

--
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Bug#1049399: marked as done (zlib1g-dev: Broken dependency to zlib1g)

[Debian Bug Tracking System]

Your message dated Tue, 15 Aug 2023 13:11:41 +0100
with message-id <668542e1-8ea9-4b90-9fab-9953ea6c4...@sirena.org.uk>
and subject line Re: Bug#1049399: zlib1g-dev: Broken dependency to zlib1g
has caused the Debian Bug report #1049399,
regarding zlib1g-dev: Broken dependency to zlib1g
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.)


-- 
1049399: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1049399
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: zlib1g-dev
Version: 1:1.2.13.dfsg-1
Severity: grave
Justification: renders package unusable

$ sudo apt-get dist-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies:
 zlib1g-dev : Depends: zlib1g (= 1:1.2.13.dfsg-1) but 1:1.2.13.dfsg-2 is 
installed
 zlib1g-dev:i386 : Depends: zlib1g:i386 (= 1:1.2.13.dfsg-1) but 1:1.2.13.dfsg-2 
is installed
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or 
specify a solution).



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

Kernel: Linux 6.1.45-1321ab40 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages zlib1g-dev depends on:
ii  libc6-dev [libc-dev]  2.37-7
iu  zlib1g1:1.2.13.dfsg-2

zlib1g-dev recommends no packages.

zlib1g-dev suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
On Tue, Aug 15, 2023 at 11:17:45AM +0200, Jonas Lundqvist wrote:

> Severity: grave
> Justification: renders package unusable

Please don't inflate bug severities.

> You might want to run 'apt --fix-broken install' to correct these.
> The following packages have unmet dependencies:
>  zlib1g-dev : Depends: zlib1g (= 1:1.2.13.dfsg-1) but 1:1.2.13.dfsg-2 is 
> installed
>  zlib1g-dev:i386 : Depends: zlib1g:i386 (= 1:1.2.13.dfsg-1) but 
> 1:1.2.13.dfsg-2 is installed

You are installing a mixed x86_64 i386 system and i386 has not yet built
the package.  This is a normal effect of multi-arch systems on unstable,
it's not a bug.


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

Processed: tagging 1049384

[Debian Bug Tracking System]

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

> tags 1049384 + ftbfs
Bug #1049384 [src:zlib] zlib: trying to overwrite 
'/usr/include/minizip/crypt.h', which is also in package libminizip-dev:amd64 
1:1.2.13.dfsg-2
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#1049384: zlib: trying to overwrite '/usr/include/minizip/crypt.h', which is also in package libminizip-dev:amd64 1:1.2.13.dfsg-2

[Adrian Bunk]

On Tue, Aug 15, 2023 at 05:28:25AM +0200, Bas Couwenberg wrote:
> Source: zlib
> Version: 1:1.2.13.dfsg-2
> Severity: serious
> Justification: makes the package in question unusable or mostly so
> 
> Dear Maintainer,
> 
> zlib1g-dev fails to upgrade due to a file confict with libminizip-dev:
> 
>  Preparing to unpack .../zlib1g-dev_1%3a1.2.13.dfsg-2_amd64.deb ...
>  Unpacking zlib1g-dev:amd64 (1:1.2.13.dfsg-2) over (1:1.2.13.dfsg-1) ...
>  dpkg: error processing archive 
> /var/cache/apt/archives/zlib1g-dev_1%3a1.2.13.dfsg-2_amd64.deb (--unpack):
>   trying to overwrite '/usr/include/minizip/crypt.h', which is also in 
> package libminizip-dev:amd64 1:1.2.13.dfsg-2
>  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
>  Errors were encountered while processing:
>   /var/cache/apt/archives/zlib1g-dev_1%3a1.2.13.dfsg-2_amd64.deb
>  E: Sub-process /usr/bin/dpkg returned an error code (1)
> 
> Breaks/Replaces or Conflicts seem to be missing.

No, the bug is that the /usr/include/minizip headers are shipped in both 
zlib1g-dev and libminizip-dev, and that they should never have been in 
zlib1g-dev.

> Kind Regards,
> 
> Bas

cu
Adrian

Bug#1041451: gmap: FTBFS on all !amd64 archs

[Étienne Mollier]

Hi,

The relevant part of the error message shows that the generic
fully scalar gmap.nosimd executable is never built for any cpu
architecture:

Note: /<>/build/src/gmap.avx2 does not exist.  For faster 
speed, may want to compile package on an AVX2 machine
Note: /<>/build/src/gmap.sse42 does not exist.  For faster 
speed, may want to compile package on an SSE4.2 machine
Note: /<>/build/src/gmap.sse41 does not exist.  For faster 
speed, may want to compile package on an SSE4.1 machine
Note: /<>/build/src/gmap.ssse3 does not exist.  For faster 
speed, may want to compile package on an SSSE3 machine
Note: /<>/build/src/gmap.sse2 does not exist.  For faster 
speed, may want to compile package on an SSE2 machine
Note: /<>/build/src/gmap.nosimd does not exist.  For 
faster speed, may want to compile package on an non-SIMD machine
Error: appropriate GMAP version not found

Looking into src/Makefile.am, indeed they seem disabled upstream
for the current gmap versions:

# intersect-uint2.c requires SIMD
#bin_PROGRAMS += gmap.nosimd
#bin_PROGRAMS += gmapl.nosimd
#bin_PROGRAMS += gsnap.nosimd
#bin_PROGRAMS += gsnapl.nosimd

My quick attempts to bring the necessary support in the
aforementioned intersect-uint2.c file were not very fruitful so
far.  Something in there looks to prevent use of simde.

Anyways, in hope this helps further investigations,
-- 
  .''`.  Étienne Mollier 
 : :' :  gpg: 8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
 `. `'   sent from /dev/pts/4, please excuse my verbosity
   `-


signature.asc
Description: PGP signature

Bug#1049328: marked as done (Adding users fails due to broken class_groups.inc)

[Debian Bug Tracking System]

Your message dated Tue, 15 Aug 2023 10:04:54 +
with message-id 
and subject line Bug#1049328: fixed in gosa 2.8~git20230203.10abe45+dfsg-6
has caused the Debian Bug report #1049328,
regarding Adding users fails due to broken class_groups.inc
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.)


-- 
1049328: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1049328
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debian-edu-config
Version: 2.12.32

Adding a student or teacher in gosa fails with the following LDAP errors (e.g. 
adding a student "mam" here):

LDAP-Operation fehlgeschlagen

Objekt: cn=mam,ou=group,ou=Students,dc=skole,dc=skolelinux,dc=no

Fehler: Object class violation (no structural object class provided, während
der Arbeit mit cn=mam,ou=group,ou=Students,dc=skole,dc=skolelinux,dc=no auf
dem LDAP-Server ldaps://ldap.intern)



LDAP-Operation fehlgeschlagen

Objekt: cn=students,ou=group,ou=Students,dc=skole,dc=skolelinux,dc=no

Fehler: Object class violation (attribute 'member' not allowed, während der
Arbeit mit cn=students,ou=group,ou=Students,dc=skole,dc=skolelinux,dc=no auf
dem LDAP-Server ldaps://ldap.intern)·



Furthermore, the postcreate command fails:

Kann POSTCREATE Kommando (/usr/share/debian-edu-config/tools/gosa-create
'mam') für Modul posixAccount nicht ausführen!

-- 
Guido Berhoerster
--- End Message ---
--- Begin Message ---
Source: gosa
Source-Version: 2.8~git20230203.10abe45+dfsg-6
Done: Mike Gabriel 

We believe that the bug you reported is fixed in the latest version of
gosa, 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.
Mike Gabriel  (supplier of updated gosa 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: Tue, 15 Aug 2023 11:41:16 +0200
Source: gosa
Architecture: source
Version: 2.8~git20230203.10abe45+dfsg-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Edu Packaging Team 

Changed-By: Mike Gabriel 
Closes: 1043575 1049328 1049338 1049394 1049400
Changes:
 gosa (2.8~git20230203.10abe45+dfsg-6) unstable; urgency=medium
 .
   * debian/patches:
 + Add patches 1011 to 1020. Revert nested group feature for GOsa² groups.
   This feature is completely broken in GOsa² upstream when posixGroups
   are in use. (Closes: #1049328). Also trivially rebase patches 1009 and
   2009.
 + Add 1021_fix-config-parser-being-null.patch. Since PHP 8.x an XML parser
   must not be null when accessed. It needs to be an instance of 
XMLParser().
   (Closes: #1049338).
 + Re-add 1035_acl_override_to_allow_delete_of_group_members.patch. Allow
   users with memberUid write access to remove users from posixGroup 
objects.
   Related to closing #1049328.
 + Add 1099_remove-debug-code.patch. Drop unwanted var_dump() call and
   other print statements.
 + Add 1022_fix-implicit-conversions-of-float-to-int.patch. Avoid PHP
   deprecation warning "Deprecated: Implicit conversion from float 

   to int loses precision in ". (Closes: #1043575).
 + Add 11?? patches. Derived from Debian's gosa 2.7.5 patchset (and ignored
   first when bringing in gosa 2.8.x, but now re-reviewed and re-applied).
 + Add 1023_fix-icon-labelling-with-default-theme.patch. Properly render
   labelled icons if default materialize CSS theme is used. (Closes:
   #1049400).
 + Improve 1003_php-deprecations.patch. Silence another 'Deprecated:
   preg_match(): Passing null to parameter #2 () of type string is
   deprecated' warning. (Closes: #1049394).
   * debian/rules:
 + Symlink the smarty4 version of the smarty-gettext plugin to
   DATADIR/gosa/include/smartyAddons/ (not the smarty3 version).
   * lintian:
 + Adjust line numbers in some overrides.
Checksums-Sha1:
 f4f146963a39b5a3d01b84483a2a0b27637b6204 2492 
gosa_2.8~git20230203.10abe45+dfsg-6.dsc
 ed1aefa68222db828c5047e5f629dc20ca81 72348 
gosa_2.8~git20230203.10abe45+dfsg-6.debian.tar.xz
 c4bdaa4e761f02874b9870fa1426bd65e94c4ae3 6773 
gosa_2.8~git20230203.10abe45+dfsg-6_source.bui

Bug#1049399: zlib1g-dev: Broken dependency to zlib1g

[Jonas Lundqvist]

Package: zlib1g-dev
Version: 1:1.2.13.dfsg-1
Severity: grave
Justification: renders package unusable

$ sudo apt-get dist-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies:
 zlib1g-dev : Depends: zlib1g (= 1:1.2.13.dfsg-1) but 1:1.2.13.dfsg-2 is 
installed
 zlib1g-dev:i386 : Depends: zlib1g:i386 (= 1:1.2.13.dfsg-1) but 1:1.2.13.dfsg-2 
is installed
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or 
specify a solution).



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

Kernel: Linux 6.1.45-1321ab40 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages zlib1g-dev depends on:
ii  libc6-dev [libc-dev]  2.37-7
iu  zlib1g1:1.2.13.dfsg-2

zlib1g-dev recommends no packages.

zlib1g-dev suggests no packages.

-- no debconf information

Bug#1042132: marked as done (ruby-gnome: FTBFS: rbglib_bookmarkfile.c:39:1: error: static declaration of ‘g_bookmark_file_get_type’ follows non-static declaration)

[Debian Bug Tracking System]

Your message dated Tue, 15 Aug 2023 09:05:25 +
with message-id 
and subject line Bug#1042132: fixed in ruby-gnome 3.4.3-2.1
has caused the Debian Bug report #1042132,
regarding ruby-gnome: FTBFS: rbglib_bookmarkfile.c:39:1: error: static 
declaration of ‘g_bookmark_file_get_type’ follows non-static declaration
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.)


-- 
1042132: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042132
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-gnome
Version: 3.4.3-2
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):
> x86_64-linux-gnu-gcc -I. -I/usr/include/x86_64-linux-gnu/ruby-3.1.0 
> -I/usr/include/ruby-3.1.0/ruby/backward -I/usr/include/ruby-3.1.0 -I. 
> -I/<>/debian/tmp/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/3.1.0 
>  -I/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/3.1.0  -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -DHAVE_UNISTD_H 
> -DHAVE_G_SPAWN_CLOSE_PID -DHAVE_G_THREAD_INIT -DHAVE_G_MAIN_DEPTH 
> -DHAVE_G_LISTENV -DHAVE_RB_CHECK_ARRAY_TYPE -DHAVE_RB_CHECK_HASH_TYPE 
> -DHAVE_RB_EXEC_RECURSIVE -DHAVE_RB_ERRINFO -DHAVE_RB_THREAD_CALL_WITHOUT_GVL 
> -DHAVE_RUBY_NATIVE_THREAD_P -DHAVE_RB_THREAD_CALL_WITH_GVL 
> -DHAVE_RB_GC_REGISTER_MARK_OBJECT -DHAVE_RB_EXC_NEW_STR 
> -DHAVE_RB_ENC_STR_NEW_STATIC -DRUBY_GLIB2_COMPILATION -Wdate-time 
> -D_FORTIFY_SOURCE=2   -fPIC -g -O2 -ffile-prefix-map=BUILDDIR=. 
> -fstack-protector-strong -Wformat -Werror=format-security -fPIC -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wall -Waggregate-return -Wcast-align -Wformat=2 
> -Winit-self -Wlarger-than-65500 -Wmissing-declarations 
> -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn 
> -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wpacked 
> -Wp,-D_FORTIFY_SOURCE=2 -Wpointer-arith -Wundef -Wunsafe-loop-optimizations 
> -Wwrite-strings  -pthread  -o rbglib_bookmarkfile.o -c rbglib_bookmarkfile.c
> rbglib_bookmarkfile.c:39:1: error: static declaration of 
> ‘g_bookmark_file_get_type’ follows non-static declaration
>39 | g_bookmark_file_get_type(void)
>   | ^~~~
> In file included from /usr/include/glib-2.0/gobject/gboxed.h:29,
>  from /usr/include/glib-2.0/gobject/gobject.h:31,
>  from /usr/include/glib-2.0/gobject/gbinding.h:31,
>  from /usr/include/glib-2.0/glib-object.h:24,
>  from rbgobject.h:25,
>  from rbgprivate.h:31,
>  from rbglib_bookmarkfile.c:22:
> /usr/include/glib-2.0/gobject/glib-types.h:402:9: note: previous declaration 
> of ‘g_bookmark_file_get_type’ with type ‘GType(void)’ {aka ‘long unsigned 
> int(void)’}
>   402 | GType   g_bookmark_file_get_type   (void) G_GNUC_CONST;
>   | ^~~~
> rbglib_bookmarkfile.c:50: warning: "G_TYPE_BOOKMARK_FILE" redefined
>50 | #define G_TYPE_BOOKMARK_FILE (g_bookmark_file_get_type())
>   | 
> /usr/include/glib-2.0/gobject/glib-types.h:337: note: this is the location of 
> the previous definition
>   337 | #define G_TYPE_BOOKMARK_FILE (g_bookmark_file_get_type ())
>   | 
> rbglib_bookmarkfile.c: In function ‘rg_set_groups’:
> rbglib_bookmarkfile.c:388:47: warning: passing argument 3 of 
> ‘g_bookmark_file_set_groups’ from incompatible pointer type 
> [-Wincompatible-pointer-types]
>   388 | g_bookmark_file_set_groups(bookmark, uri, groups, n);
>   |   ^~
>   |   |
>   |   gchar ** {aka char **}
> In file included from /usr/include/glib-2.0/glib.h:39,
>  from /usr/include/glib-2.0/gobject/gbinding.h:30:
> /usr/include/glib-2.0/glib/gbookmarkfile.h:140:69: note: expected ‘const 
> gchar **’ {aka ‘const char **’} but argument is of type ‘gchar **’ {aka ‘char 
> **’}
>   140 | const gchar   
> **groups,
>   | 
> ^~
> make[1]: *** [Makefile:246: rbglib_bookmarkfile.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2023/07/26/ruby-gnome_3.4.3-2_unstable.log

All bug

Bug#1042132: ruby-gnome: FTBFS: rbglib_bookmarkfile.c:39:1: error: static declaration of ‘g_bookmark_file_get_type’ follows non-static declaration

[Bastian Germann]

I am uploading a NMU to fix this. The debdiff is attached.diff -Nru ruby-gnome-3.4.3/debian/changelog ruby-gnome-3.4.3/debian/changelog
--- ruby-gnome-3.4.3/debian/changelog   2022-06-26 14:29:08.0 +0200
+++ ruby-gnome-3.4.3/debian/changelog   2023-08-14 19:15:42.0 +0200
@@ -1,3 +1,11 @@
+ruby-gnome (3.4.3-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop unused ruby-gtk2 (Closes: #967733).
+  * Include upstream patch for GLib >= 2.75 (Closes: #1042132).
+
+ -- Bastian Germann   Mon, 14 Aug 2023 17:15:42 +
+
 ruby-gnome (3.4.3-2) unstable; urgency=medium
 
   * Team upload.
diff -Nru ruby-gnome-3.4.3/debian/control ruby-gnome-3.4.3/debian/control
--- ruby-gnome-3.4.3/debian/control 2022-06-25 09:49:19.0 +0200
+++ ruby-gnome-3.4.3/debian/control 2023-08-14 19:15:42.0 +0200
@@ -14,7 +14,6 @@
libgstreamer-plugins-base1.0-dev,
libgstreamer1.0-dev,
libgtksourceview-3.0-dev,
-   libgtk2.0-dev,
libjpeg-dev,
libpng-dev,
librsvg2-dev (>= 2.8.0),
@@ -287,25 +286,6 @@
  This package contains libraries for using GStreamer with the Ruby programming
  language.
 
-Package: ruby-gtk2
-Architecture: any
-XB-Ruby-Versions: ${ruby:Versions}
-X-DhRuby-Root: gtk2
-Depends: ruby | ruby-interpreter,
- ruby-atk (>= ${source:Version}),
- ruby-gdk-pixbuf2 (>= ${source:Version}),
- ruby-pango (= ${binary:Version}),
- ${misc:Depends},
- ${shlibs:Depends}
-Multi-Arch: same
-Description: GTK+ 2 bindings for the Ruby language
- GTK+ is a multi-platform toolkit for creating graphical user interfaces.
- Offering a complete set of widgets, GTK+ is suitable for projects ranging
- from small one-off tools to complete application suites.
- .
- This package contains libraries for using GTK+ 2 with the Ruby programming
- language.
-
 Package: ruby-gtk3
 Architecture: any
 XB-Ruby-Versions: ${ruby:Versions}
diff -Nru 
ruby-gnome-3.4.3/debian/patches/dont-define-G_TYPE_BOOKMARK_FILE.patch 
ruby-gnome-3.4.3/debian/patches/dont-define-G_TYPE_BOOKMARK_FILE.patch
--- ruby-gnome-3.4.3/debian/patches/dont-define-G_TYPE_BOOKMARK_FILE.patch  
1970-01-01 01:00:00.0 +0100
+++ ruby-gnome-3.4.3/debian/patches/dont-define-G_TYPE_BOOKMARK_FILE.patch  
2023-08-14 19:15:42.0 +0200
@@ -0,0 +1,34 @@
+Origin: upstream, 396d2d377bd85d9bdd73b26210e323129deea1f4
+From: Sutou Kouhei 
+Date: Thu, 16 Feb 2023 17:03:57 +0900
+Subject: glib2: don't define G_TYPE_BOOKMARK_FILE() for GLib >= 2.75
+
+GitHub: fix GH-1547
+
+GLib >= 2.75 defines it.
+
+Reported by Mamoru TASAKA. Thanks!!!
+---
+ glib2/ext/glib2/rbglib_bookmarkfile.c | 2 ++
+ 1 file changed, 2 insertions(+)
+
+diff --git a/glib2/ext/glib2/rbglib_bookmarkfile.c 
b/glib2/ext/glib2/rbglib_bookmarkfile.c
+index 036f783961..a7ac83eff9 100644
+--- a/glib2/ext/glib2/rbglib_bookmarkfile.c
 b/glib2/ext/glib2/rbglib_bookmarkfile.c
+@@ -21,6 +21,7 @@
+ 
+ #include "rbgprivate.h"
+ 
++#ifndef G_TYPE_BOOKMARK_FILE
+ //
+ static GBookmarkFile*
+ bookmarkfile_copy(const GBookmarkFile* file)
+@@ -48,6 +49,7 @@ g_bookmark_file_get_type(void)
+ //
+ 
+ #define G_TYPE_BOOKMARK_FILE (g_bookmark_file_get_type())
++#endif
+ 
+ #define RG_TARGET_NAMESPACE cBookmarkFile
+ #define _SELF(self) ((GBookmarkFile*)(RVAL2BOXED(self, G_TYPE_BOOKMARK_FILE)))
diff -Nru ruby-gnome-3.4.3/debian/patches/series 
ruby-gnome-3.4.3/debian/patches/series
--- ruby-gnome-3.4.3/debian/patches/series  2021-09-12 07:45:24.0 
+0200
+++ ruby-gnome-3.4.3/debian/patches/series  2023-08-14 19:15:42.0 
+0200
@@ -7,3 +7,4 @@
 do-not-run-dependency-check.patch
 ruby-gnome2-gemspecs.patch
 do-not-depend-dependency-check.patch
+dont-define-G_TYPE_BOOKMARK_FILE.patch
diff -Nru ruby-gnome-3.4.3/debian/ruby-gtk2.examples 
ruby-gnome-3.4.3/debian/ruby-gtk2.examples
--- ruby-gnome-3.4.3/debian/ruby-gtk2.examples  2021-09-12 07:45:20.0 
+0200
+++ ruby-gnome-3.4.3/debian/ruby-gtk2.examples  1970-01-01 01:00:00.0 
+0100
@@ -1 +0,0 @@
-gtk2/sample/*
diff -Nru ruby-gnome-3.4.3/debian/ruby-gtk2.install 
ruby-gnome-3.4.3/debian/ruby-gtk2.install
--- ruby-gnome-3.4.3/debian/ruby-gtk2.install   2021-09-12 07:45:20.0 
+0200
+++ ruby-gnome-3.4.3/debian/ruby-gtk2.install   1970-01-01 01:00:00.0 
+0100
@@ -1,4 +0,0 @@
-usr/lib/*/ruby/vendor_ruby/*/gtk2.so
-usr/lib/ruby/vendor_ruby/gtk2.rb
-usr/lib/ruby/vendor_ruby/gtk2/base.rb
-usr/share/rubygems-integration/*/specifications/gtk2-*.gemspec
diff -Nru ruby-gnome-3.4.3/debian/rules ruby-gnome-3.4.3/debian/rules
--- ruby-gnome-3.4.3/debian/rules   2021-09-12 07:45:24.0 +0200
+++ ruby-gnome-3.4.3/debian/rules   2023-08-14 19:15:42.0 +0200
@@ -19,7 +19,6 @@
dh_fixperms
# Remove executable flag from some examples tha

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

[Markus Blatt]

On Fri, 4 Aug 2023 08:47:23 +0200 Gianfranco Costamagna 
 wrote:

Hello, if you request with a signed message you can as maintainer get access to 
porterboxes.
See e.g. https://lists.debian.org/debian-mentors/2019/04/msg00125.html


Also I find useful with qemu-user-static and ubuntu-dev-tools installed to 
debug with

pbuilder-dist sid armel create
pbuilder-dist sid armel login
and then copy-paste do whatever I want in the qemu-created chroot.
It's slow, but works for most of the tasks I need to solve

HTH


Dear Gianfranco,

Thank a lot. I ended up using a chroot using qemu and also found an armhf 
machine where I could see the same problems.


It turns out that at least some of tests (e.g. test_AggregateActionxData) fail
due to an std::time_t overflow on 32bit architectures. Chances are that the
rest of the failures is similar.

At upstream we never cared about those because they would seriously limit 
the simulation time. A few years ago I started to add 32bit patches to the Debian 
packages, but then I realized that this would become a very big effort with 
very little gain for the user. It is of course very unfortunate that we did 
not fail when testing before, but that was probably because of missing tests 
and luck.


My proposal is to make our packages and upstream already check for 64bit when 
configuring the packages and remove the binaries of the archictures where this 
happens.


Note that opm-common is more or less a helper package for the other OPM modules. 
For the user the architectures supported by opm-simulators and opm-upscaling 
are what matters. Removing other architectures from helper modules will not 
limit the usability in any major way.


Best,

Markus

Bug#1043002: pdm: Please replace python3-pep517 with python3-pyproject-hooks in Depends/Build-Depends

[Andreas Tille]

Hi Scott,

Am Mon, Aug 14, 2023 at 02:06:42PM + schrieb Scott Kitterman:
> >Before I upload I'd like to ask for reviewing this patch and opinions
> >about the test suite errors.  While these possibly occure in previous
> >versions (which I did not tested) we might consider ignoring just the
> >failing tests.  I need to admit that I did not went through the list of
> >single failures - may be there is a chance of easy fixes for some of
> >them.  I simply wanted to discuss the reintroduction of the artifacts
> >and my patch first.
> >
> With the exception of future_fstrings

I think there is also the souce for demo included.

> those are all binary without source.  That's a problem.

Given your role as ftpmaster you definitely have more experience than I
in this field.  I personally was thinking more in the line of binary
data we can not avoid in some cases.  This is a bit in the line with
Rdata decision[1] where those binary data files are documented in
debian/README.source.

My point is just: If we remove those data files (which are IMHO harmless
since these are not executd but used as input in tests - please correct
me if I'm wrong) we can not test the package.  Removing the files
prevents testing and thus we can not know whether the package we deliver
will work.  I've actually shown that not all tests are working but
stopped investigating this further.

> It's probably okay if you add the corresponding source somewhere in the 
> package.

We probably have some source packages inside Debian - may be in
different versions.  I need to admit that I intended to do a "quick fix
of a simple bug that affects some Debian Med packages" but realised that
I'm possibly opening a can of worms.  The simplest solution to fulfill
my needs would be probably to revert my change to run the tests and be
done.  However, I'm not sure whetherr this is in the interest of the
users of this package.  I'm absolutely not able time-wise to povide
sources and reconstruct all those *.whl files *and* in addition track
down the test suite errors.  This is a team package and if the team
decides we should go without testing I can do an according upload.
However, my prefered path would to document the issue of some binary
data properly an test what upstream expects to be tested.

> I do think it's odd that pdm would need poetry-core in its test suit.

At least there is poetry_core-1.3.2-py3-none-any.whl which might mean
that poetry-core is used for testing. 

Kind regards
   Andreas.
 

[1] https://lists.debian.org/debian-devel/2013/09/msg00332.html 

-- 
http://fam-tille.de