Processed: closing 1037571

[Debian Bug Tracking System]

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

> close 1037571 1.1.2-4
Bug #1037571 [src:aghermann] aghermann: ftbfs with GCC-13
The source 'aghermann' and version '1.1.2-4' do not appear to match any binary 
packages
Marked as fixed in versions aghermann/1.1.2-4.
Bug #1037571 [src:aghermann] aghermann: ftbfs with GCC-13
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1037736: [Pkg-sass-devel] Bug#1037736: Bug#1037736: libsass: ftbfs with GCC-13

[Bo YU]

Hi!

On Sun, Aug 6, 2023 at 10:10 PM Jonas Smedegaard  wrote:
>
> Quoting Jonas Smedegaard (2023-08-06 14:07:09)
> > Quoting Bo YU (2023-08-06 13:48:43)
> > > On Mon, Jul 31, 2023 at 1:09 AM Jonas Smedegaard  wrote:
> > > > If you are generally interested in SASS tools and want to help maintain
> > > > them in Debian, then you are very welcome to join the team (which is
> > > > effectively only me at the moment).
> > > Thanks for the invitation. I am happy to maintain SASS tools packages.
> >
> > Great!  Please request membership of the salsa group at
> > https://salsa.debian.org/groups/sass-team/-/group_members
>
Request has been sent.

> Please also subscribe to our mailinglist - it is listed at our team page
> at https://wiki.debian.org/Teams/Sass (which I created just now,
> reminded by my earlier mention of lousy documentation).
>
Done. Thanks again for your work here, I will look at them.

BR,
Bo
>
>  - Jonas
>
> --
>  * Jonas Smedegaard - idealist & Internet-arkitekt
>  * Tlf.: +45 40843136  Website: http://dr.jones.dk/
>  * Sponsorship: https://ko-fi.com/drjones
>
>  [x] quote me freely  [ ] ask before reusing  [ ] keep private

Bug#1041258: marked as done (rust-fs-extra: FTBFS: test failures)

[Debian Bug Tracking System]

Your message dated Mon, 7 Aug 2023 04:10:01 +0100
with message-id <201032f8-a114-aabf-80b4-83440c46c...@debian.org>
and subject line Re: Bug#1041258 closed by Debian FTP Masters 
 (reply to Peter Michael Green 
) (Bug#1041258: fixed in rust-fs-extra 1.3.0-2)
has caused the Debian Bug report #1041258,
regarding rust-fs-extra: FTBFS: test failures
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.)


-- 
1041258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041258
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-fs-extra
Version: 1.3.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

https://buildd.debian.org/status/fetch.php?pkg=rust-fs-extra&arch=amd64&ver=1.3.0-1&stamp=1688994742&raw=0


failures:
it_copy_progress_work

it_copy_with_progress_inside_no_overwrite_work_target_dir_exist_with_source_dir_exist

it_copy_with_progress_inside_overwrite_work_target_dir_exist_with_source_dir_exist

it_copy_with_progress_inside_work_target_dir_exist_with_no_source_dir_named_sub_dir
it_copy_with_progress_inside_work_target_dir_not_exist
it_copy_with_progress_work_dif_buf_size
it_get_dir_content
it_get_dir_content_many_levels

it_move_dir_with_progress_inside_no_overwrite_work_target_dir_exist_with_source_dir_exist

it_move_dir_with_progress_inside_overwrite_work_target_dir_exist_with_source_dir_exist

it_move_dir_with_progress_inside_work_target_dir_exist_with_no_source_dir_named_sub_dir
it_move_dir_with_progress_inside_work_target_dir_not_exist
it_move_progress_work
it_move_with_progress_work_dif_buf_size

test result: FAILED. 68 passed; 14 failed; 0 ignored; 0 measured; 0 filtered 
out; finished in 0.05s

error: test failed, to rerun pass `--test dir`
dh_auto_test: error: /usr/share/cargo/bin/cargo test --all returned exit code 
101
make[1]: *** [debian/rules:7: override_dh_auto_test] Error 25


Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---

It still fails to build:


1.3.0-3 really fixed it.--- End Message ---

Bug#957230: freebsd-buildutils: ftbfs with GCC-10

[Bastian Germann]

Am 07.08.23 um 02:40 schrieb Bastian Germann:

I am uploading a NMU to fix this. The debdiff is attached.


Now with the correct debdiff. I mixed up the BTS addresses.diff -Nru freebsd-buildutils-10.3~svn296373/debian/changelog 
freebsd-buildutils-10.3~svn296373/debian/changelog
--- freebsd-buildutils-10.3~svn296373/debian/changelog  2017-02-13 
22:45:25.0 +0100
+++ freebsd-buildutils-10.3~svn296373/debian/changelog  2023-08-07 
00:36:34.0 +0200
@@ -1,3 +1,14 @@
+freebsd-buildutils (10.3~svn296373-7.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Don't build against flex-old. (Closes: #932512)
+  * Build with gcc-9. (Closes: #957230)
+  * Depend on bsd{extra}utils instead of bsdmainutils. (Closes: #964527)
+  * Require newer freebsd-glue.
+  * Do not require lorder.
+
+ -- Bastian Germann   Mon, 07 Aug 2023 00:36:34 +0200
+
 freebsd-buildutils (10.3~svn296373-7) unstable; urgency=medium
 
   * Build fmtree with support for MD5, SHA1, RMD160, SHA256 checksums
diff -Nru freebsd-buildutils-10.3~svn296373/debian/control 
freebsd-buildutils-10.3~svn296373/debian/control
--- freebsd-buildutils-10.3~svn296373/debian/control2017-02-13 
22:25:13.0 +0100
+++ freebsd-buildutils-10.3~svn296373/debian/control2023-08-07 
00:36:34.0 +0200
@@ -7,13 +7,14 @@
  Robert Millan ,
  Steven Chamberlain ,
 Build-Depends: debhelper (>= 9),
- flex | flex-old,
- libfl-dev | flex-old,
+ gcc-9,
+ flex,
+ libfl-dev,
  bison,
  dpkg-dev (>= 1.16.1.1),
  libbsd-dev (>= 0.3.0),
  libmd-dev,
- freebsd-glue (>= 0.2.20),
+ freebsd-glue (>> 0.2.22),
  bmake,
  byacc (>= 20120115~),
 # for freebsd-config
@@ -24,8 +25,8 @@
 
 Package: freebsd-buildutils
 Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}, bsdmainutils, unzip, patchutils,
- freebsd-glue (>= 0.2.8~),
+Depends: ${shlibs:Depends}, ${misc:Depends}, bsdutils, bsdextrautils, unzip,
+ patchutils, freebsd-glue (>= 0.2.8~),
 # Required by lex
  m4,
 # Not strictly required anymore. But let's drag it in for now, to avoid 
breaking
diff -Nru freebsd-buildutils-10.3~svn296373/debian/patches/01_make_fixes.diff 
freebsd-buildutils-10.3~svn296373/debian/patches/01_make_fixes.diff
--- freebsd-buildutils-10.3~svn296373/debian/patches/01_make_fixes.diff 
2016-03-05 16:28:15.0 +0100
+++ freebsd-buildutils-10.3~svn296373/debian/patches/01_make_fixes.diff 
2023-08-07 00:36:34.0 +0200
@@ -76,7 +76,7 @@
@${ECHO} building static ${LIB} library
@rm -f ${.TARGET}
 -  @${AR} ${ARFLAGS} ${.TARGET} `NM='${NM}' lorder ${OBJS} ${STATICOBJS} | 
tsort -q` ${ARADD}
-+  @${AR} ${ARFLAGS} ${.TARGET} `NM='${NM}' lorder ${OBJS} ${STATICOBJS} | 
tsort` ${ARADD}
++  ${AR} ${ARFLAGS} ${.TARGET} ${OBJS} ${STATICOBJS} ${ARADD}
${RANLIB} ${RANLIBFLAGS} ${.TARGET}
  .endif
  
@@ -85,7 +85,7 @@
@${ECHO} building profiled ${LIB} library
@rm -f ${.TARGET}
 -  @${AR} ${ARFLAGS} ${.TARGET} `NM='${NM}' lorder ${POBJS} | tsort -q` 
${ARADD}
-+  @${AR} ${ARFLAGS} ${.TARGET} `NM='${NM}' lorder ${POBJS} | tsort` 
${ARADD}
++  ${AR} ${ARFLAGS} ${.TARGET} ${POBJS} ${ARADD}
${RANLIB} ${RANLIBFLAGS} ${.TARGET}
  .endif
  
@@ -94,7 +94,7 @@
${_LD} ${LDFLAGS} ${SSP_CFLAGS} ${SOLINKOPTS} \
-o ${.TARGET} -Wl,-soname,${SONAME} \
 -  `NM='${NM}' lorder ${SOBJS} | tsort -q` ${LDADD}
-+  `NM='${NM}' lorder ${SOBJS} | tsort` ${LDADD}
++  ${SOBJS} ${LDADD}
  .if ${MK_CTF} != "no"
${CTFMERGE} ${CTFFLAGS} -o ${.TARGET} ${SOBJS}
  .endif
diff -Nru 
freebsd-buildutils-10.3~svn296373/debian/patches/ar_command_lines.diff 
freebsd-buildutils-10.3~svn296373/debian/patches/ar_command_lines.diff
--- freebsd-buildutils-10.3~svn296373/debian/patches/ar_command_lines.diff  
2016-07-19 10:30:55.0 +0200
+++ freebsd-buildutils-10.3~svn296373/debian/patches/ar_command_lines.diff  
2023-08-07 00:36:34.0 +0200
@@ -1,27 +1,9 @@
 Date: Tue, 19 Jul 2016 09:06:50 +0100
 From: Steven Chamberlain 
-Subject: make ar command lines visible in build log
+Subject: make ar command line visible in build log
 
 --- a/src/share/mk/bsd.lib.mk
 +++ b/src/share/mk/bsd.lib.mk
-@@ -175,7 +175,7 @@
- lib${LIB}.a: ${OBJS} ${STATICOBJS}
-   @${ECHO} building static ${LIB} library
-   @rm -f ${.TARGET}
--  @${AR} ${ARFLAGS} ${.TARGET} `NM='${NM}' lorder ${OBJS} ${STATICOBJS} | 
tsort` ${ARADD}
-+  ${AR} ${ARFLAGS} ${.TARGET} `NM='${NM}' lorder ${OBJS} ${STATICOBJS} | 
tsort` ${ARADD}
-   ${RANLIB} ${RANLIBFLAGS} ${.TARGET}
- .endif
- 
-@@ -188,7 +188,7 @@
- lib${LIB}_p.a: ${POBJS}
-   @${ECHO} building profiled ${LIB} library
-   @rm -f ${.TARGET}
--  @${AR} ${ARFLAGS} ${.TARGET} `NM='${NM}' lorder ${POBJS} | tsort` 
${ARADD}
-+  ${AR} ${ARFLAGS} ${.TARGET} `NM='${NM}' lorder ${POBJS} | tsort` 
${ARADD}
-   ${RANLIB} ${RANLIBFLAGS} ${.TARGET}
- .endif
- 
 @@ -239,7 +239,7 @@
  lib${LIB}_pic.a: ${SOBJS}
@${ECHO} bu

Bug#964661: freebsd-buildutils: ftbfs with GCC-10

[Bastian Germann]

I am uploading a NMU to fix this. The debdiff is attached.diff -Nru freebsd-glue-0.2.22/debian/changelog 
freebsd-glue-0.2.22+nmu1/debian/changelog
--- freebsd-glue-0.2.22/debian/changelog2016-03-05 16:44:54.0 
+0100
+++ freebsd-glue-0.2.22+nmu1/debian/changelog   2023-08-07 01:20:16.0 
+0200
@@ -1,3 +1,12 @@
+freebsd-glue (0.2.22+nmu1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Build with gcc-9. (Closes: #964661)
+  * Include #pragma once in md5.h for freebsd-buildutils.
+  * Temporarily include lorder/tsort workaround. (Closes: #964661)
+
+ -- Bastian Germann   Mon, 07 Aug 2023 01:20:16 +0200
+
 freebsd-glue (0.2.22) unstable; urgency=medium
 
   * Actually use the proper build architecture compiler
diff -Nru freebsd-glue-0.2.22/debian/control 
freebsd-glue-0.2.22+nmu1/debian/control
--- freebsd-glue-0.2.22/debian/control  2016-03-05 02:08:01.0 +0100
+++ freebsd-glue-0.2.22+nmu1/debian/control 2023-08-07 01:18:20.0 
+0200
@@ -7,6 +7,7 @@
  Steven Chamberlain ,
 Build-Depends:
  debhelper (>= 8.0),
+ gcc-9,
  kfreebsd-kernel-headers (>= 10.0~3) [kfreebsd-any],
  freebsd-mk,
  bmake,
diff -Nru freebsd-glue-0.2.22/debian/lorder 
freebsd-glue-0.2.22+nmu1/debian/lorder
--- freebsd-glue-0.2.22/debian/lorder   1970-01-01 01:00:00.0 +0100
+++ freebsd-glue-0.2.22+nmu1/debian/lorder  2023-08-07 01:20:16.0 
+0200
@@ -0,0 +1,2 @@
+#!/bin/sh
+echo $@
diff -Nru freebsd-glue-0.2.22/debian/rules freebsd-glue-0.2.22+nmu1/debian/rules
--- freebsd-glue-0.2.22/debian/rules2016-03-05 01:54:10.0 +0100
+++ freebsd-glue-0.2.22+nmu1/debian/rules   2023-08-07 01:20:16.0 
+0200
@@ -6,7 +6,7 @@
 # Determine host architecture compiler
 DEB_HOST_GNU_TYPE  ?= $(shell dpkg-architecture -qDEB_HOST_GNU_TYPE)
 ifeq ($(origin CC),default)
-CC := $(DEB_HOST_GNU_TYPE)-gcc
+CC := $(DEB_HOST_GNU_TYPE)-gcc-9
 endif
 
 # Determine build architecture compiler
@@ -23,7 +23,7 @@
 endif
 
 DESTDIR = $(CURDIR)/debian/tmp
-PATH := /usr/lib/freebsd:$(PATH)
+PATH := $(CURDIR)/debian:/usr/lib/freebsd:$(PATH)
 PMAKE := \
MAKEFLAGS=$(BSD_MAKEFLAGS) \
MAKEOBJDIRPREFIX=$(CURDIR)/obj-deb \
diff -Nru freebsd-glue-0.2.22/debian/tsort freebsd-glue-0.2.22+nmu1/debian/tsort
--- freebsd-glue-0.2.22/debian/tsort1970-01-01 01:00:00.0 +0100
+++ freebsd-glue-0.2.22+nmu1/debian/tsort   2023-08-07 01:20:16.0 
+0200
@@ -0,0 +1,2 @@
+#!/bin/sh
+sort $@
diff -Nru freebsd-glue-0.2.22/include/md5.h 
freebsd-glue-0.2.22+nmu1/include/md5.h
--- freebsd-glue-0.2.22/include/md5.h   2014-08-25 21:40:17.0 +0200
+++ freebsd-glue-0.2.22+nmu1/include/md5.h  2023-08-07 01:20:16.0 
+0200
@@ -1 +1,2 @@
+#pragma once
 #include 

Bug#1043174: marked as done (precious - update for new serial-test)

[Debian Bug Tracking System]

Your message dated Mon, 07 Aug 2023 01:11:20 +
with message-id 
and subject line Bug#1043174: fixed in precious 0.5.1+20230704-2
has caused the Debian Bug report #1043174,
regarding precious - update for new serial-test
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.)


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

Package: precious
Severity: serious
Tags: trixie, sid

I just updated the serial-test crate to version 2.0. Precious
needs a small update to the Debian dependency to match. (the Cargo
dependency already allows both versions).

Debdiff attatched.diff -Nru precious-0.5.1+20230704/debian/changelog 
precious-0.5.1+20230704/debian/changelog
--- precious-0.5.1+20230704/debian/changelog2023-07-11 21:20:29.0 
+
+++ precious-0.5.1+20230704/debian/changelog2023-08-06 12:48:08.0 
+
@@ -1,3 +1,11 @@
+precious (0.5.1+20230704-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Update Debian dependency on serial-test to 2.0.
+(cargo dependency already allows the new version)
+
+ -- Peter Michael Green   Sun, 06 Aug 2023 12:48:08 +
+
 precious (0.5.1+20230704-1) unstable; urgency=medium
 
   [ upstream ]
diff -Nru precious-0.5.1+20230704/debian/control 
precious-0.5.1+20230704/debian/control
--- precious-0.5.1+20230704/debian/control  2023-07-11 21:20:29.0 
+
+++ precious-0.5.1+20230704/debian/control  2023-08-06 12:47:55.0 
+
@@ -33,7 +33,7 @@
  librust-regex-1+default-dev (>= 1.7),
  librust-serde-1+default-dev (>= 1.0.147),
  librust-serde-1+derive-dev (>= 1.0.147),
- librust-serial-test-0.9+default-dev ,
+ librust-serial-test-2.0+default-dev ,
  librust-tempfile-3+default-dev (>= 3.3) ,
  librust-test-case-2+default-dev ,
  librust-thiserror-1+default-dev (>= 1.0.37),
--- End Message ---
--- Begin Message ---
Source: precious
Source-Version: 0.5.1+20230704-2
Done: Jonas Smedegaard 

We believe that the bug you reported is fixed in the latest version of
precious, 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.
Jonas Smedegaard  (supplier of updated precious package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 07 Aug 2023 02:35:20 +0200
Source: precious
Architecture: source
Version: 0.5.1+20230704-2
Distribution: unstable
Urgency: medium
Maintainer: Jonas Smedegaard 
Changed-By: Jonas Smedegaard 
Closes: 1043174
Changes:
 precious (0.5.1+20230704-2) unstable; urgency=medium
 .
   * update dh-cargo fork
   * update copyright info: update file paths
   * reduce patch 1001 to not affect crate serial-test;
 update build-dependency for crate serial-test;
 closes: bug#1043174, thanks to Peter Green
Checksums-Sha1:
 94f38555c33d4e2d7a05892f7cbcb97cd9ede60b 3133 precious_0.5.1+20230704-2.dsc
 0d231bb382f7b887f7c836da276589ddd4620449 23644 
precious_0.5.1+20230704-2.debian.tar.xz
 687d21209bca1219e09910c7ea2287320a4da75c 17224 
precious_0.5.1+20230704-2_amd64.buildinfo
Checksums-Sha256:
 17834eeac93958b8420f13afb9030150a9dd6b981381622660e791a66ea0e116 3133 
precious_0.5.1+20230704-2.dsc
 c3fb14b3984904c743e4fd85af47cf08457434e060e1927148c7b92c9ec3934f 23644 
precious_0.5.1+20230704-2.debian.tar.xz
 533a768e11748a6b430c91160c950318b8a2dc1c66fedc4ce01090dde4e256c8 17224 
precious_0.5.1+20230704-2_amd64.buildinfo
Files:
 b401ab1c7940a4648c4f5d1ed6fc1862 3133 devel optional 
precious_0.5.1+20230704-2.dsc
 3ee6bc6cbd1c2d165661cfc390203968 23644 devel optional 
precious_0.5.1+20230704-2.debian.tar.xz
 01b7557997132e797ec19149408f6705 17224 devel optional 
precious_0.5.1+20230704-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmTQPcEACgkQLHwxRsGg
ASHksg/+KB8+B2FOJhstyTzYBebtSyI6tnTZKz5ySzQuNz7ocbFg+xA1AU5BK/sm
tFpFx31Iw/6bah4+zWneZPIvbJnw+CzFcViOg5X4HdBm5h+l1nwTZLS6jgjgwiin
Xbn+7MMoJbzGed2Q0IgYkq74738gCWehvb886nLF690fYTFJ0hSf5f8d7P0dn2p9
0vdU511pjbEbjNLFJLMU8QN20ET1XIEOdjFNnikC8Z6cI5Fdv8XTGaNRz7Di5PyD
OB8rbRI4xQs4Sj40yHVJIc7aS/pNbeAppfDRxl4VAmqr+

Bug#1043176: marked as done (sccache - update for new serial-test)

[Debian Bug Tracking System]

Your message dated Mon, 07 Aug 2023 00:51:02 +
with message-id 
and subject line Bug#1043176: fixed in sccache 0.5.4-8
has caused the Debian Bug report #1043176,
regarding sccache - update for new serial-test
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.)


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

Package: sccache
Severity: serious
Tags: trixie, sid

I just updated the serial-test crate to version 2.0. sccache
needs a small update to the Debian dependency to match. (the Cargo
dependency already allows both versions).

Debdiff attatched.
diff -Nru sccache-0.5.4/debian/changelog sccache-0.5.4/debian/changelog
--- sccache-0.5.4/debian/changelog  2023-07-30 16:13:02.0 +
+++ sccache-0.5.4/debian/changelog  2023-08-06 13:14:32.0 +
@@ -1,3 +1,11 @@
+sccache (0.5.4-7.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Update Debian dependency on serial-test to version 2
+(Cargo dependencies already allow it).
+
+ -- root   Sun, 06 Aug 2023 13:14:32 +
+
 sccache (0.5.4-7) unstable; urgency=medium
 
   * fix yet again: reduce lto further on mipsel
diff -Nru sccache-0.5.4/debian/control sccache-0.5.4/debian/control
--- sccache-0.5.4/debian/control2023-07-27 16:54:09.0 +
+++ sccache-0.5.4/debian/control2023-08-06 13:13:12.0 +
@@ -58,7 +58,7 @@
  librust-serde-1+default-dev,
  librust-serde-1+derive-dev,
  librust-serde-json-1+default-dev,
- librust-serial-test-0.9+default-dev ,
+ librust-serial-test-2+default-dev ,
  librust-sha2-0.10+default-dev,
  librust-strip-ansi-escapes-0.1+default-dev,
  librust-tar-0.4+default-dev,
--- End Message ---
--- Begin Message ---
Source: sccache
Source-Version: 0.5.4-8
Done: Jonas Smedegaard 

We believe that the bug you reported is fixed in the latest version of
sccache, 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.
Jonas Smedegaard  (supplier of updated sccache package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 07 Aug 2023 02:08:33 +0200
Source: sccache
Architecture: source
Version: 0.5.4-8
Distribution: unstable
Urgency: medium
Maintainer: Jonas Smedegaard 
Changed-By: Jonas Smedegaard 
Closes: 1043176
Changes:
 sccache (0.5.4-8) unstable; urgency=medium
 .
   * drop patch 2011, obsoleted by Debian package update;
 update build-dependency for crate serial-test;
 closes: bug#1043176, thanks to Peter Green
Checksums-Sha1:
 7bfcbb0a8d8ced4e73b94ba4062dd3147359a02d 4377 sccache_0.5.4-8.dsc
 6e78c3e6dae34ddf96c3b2aa44d3e6db183c8f3b 18780 sccache_0.5.4-8.debian.tar.xz
 ab9d3a5e7130242933188ea92e7675cee1836ffe 22718 sccache_0.5.4-8_amd64.buildinfo
Checksums-Sha256:
 df3edfa4812c4b01878e52d857f5bfe4137416d8c8bb23e59a5ac05e7e5ee486 4377 
sccache_0.5.4-8.dsc
 335623c042efd8c4e079c6437193364b94a05d3df9517794696d98293f4a02e7 18780 
sccache_0.5.4-8.debian.tar.xz
 4a1e04ca3b4446fa24c0928adb6dccbe7df8f396bec1de167a667a51e5b1ea9e 22718 
sccache_0.5.4-8_amd64.buildinfo
Files:
 71ae42bf89602843b62b4e9fd69f7592 4377 devel optional sccache_0.5.4-8.dsc
 d0997ef6a9e0e1d149c8b382ed7bee2f 18780 devel optional 
sccache_0.5.4-8.debian.tar.xz
 29635f00bfebf9870ba9af34b156bfd2 22718 devel optional 
sccache_0.5.4-8_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmTQOZsACgkQLHwxRsGg
ASGjcQ/+IWwije2e1ygSWuRD/A1sPGH21jh12urS6s7X/I9RhGhf59sJilp7Ycju
4CtJ+u8DnaDiR0I26Yhz1KnNxsjXcLRzcEEdmDI55/p0hO1ZDVnHt1QHZKcqByqP
19P/56RYZOfO/SQuf6nrYHlXFK9D7JrCi1CZPuMCtYwt98wjJQl83ahT2HkII5UT
oc/tl0aUDbrcJHPok2hJqtuFSlGB+s2XjLSCwmu/O5GIigzXb37WhJIFU2n87coK
ge5lT3pqCU1aiBl4dee8OfoLUqpI87/eQkqqn11e9Tpa5UWihIU4D5HZHPIdYe+d
s1OjK8u99y8eD06K97VTparezrc9XdSmlq8d4Cc5e/3bNAJGXVIPs02Fl08KqYpQ
fYNn9EiK7CDe0YeDXPJTNDNNq96EHS0rsvXc2AKixFA1ivKwlPD2gAW0JFuufUw6
RWAPTDF5y2POZrsed3SN5fS5inFzjkBO6nfjrDcuJZPZVpanuFlG9PwYHCNKtTno
LanHYJXwB1Kdyg9g8bUCimQW9I94xpCLoik2GdZDicYAd+Uy/4w/Ru1ESSQK7FL7
Q4Y/hZPgNGC7YWjN0pOGH8NeixYrUZMhouaszSWM8RASppF15UsDWuvhCNxu50

Bug#1043175: marked as done (rust-rustls-native-certs - update for new serial-test)

[Debian Bug Tracking System]

Your message dated Mon, 07 Aug 2023 00:50:53 +
with message-id 
and subject line Bug#1043175: fixed in rust-rustls-native-certs 0.6.3-2
has caused the Debian Bug report #1043175,
regarding rust-rustls-native-certs - update for new serial-test
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.)


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

Package: rust-rustls-native-certs
Severity: serious
Tags: trixie, sid

I just updated the serial-test crate to version 2.0. rust-rustls-native-certs
needs a small update to the Debian dependency to match. (the Cargo
dependency already allows both versions).

Debdiff attatched.
diff -Nru rust-rustls-native-certs-0.6.3/debian/changelog 
rust-rustls-native-certs-0.6.3/debian/changelog
--- rust-rustls-native-certs-0.6.3/debian/changelog 2023-07-29 
21:03:41.0 +
+++ rust-rustls-native-certs-0.6.3/debian/changelog 2023-08-06 
13:08:55.0 +
@@ -1,3 +1,11 @@
+rust-rustls-native-certs (0.6.3-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Update debian dependencies for rust-serial-test 2
+(Cargo dependencies already allow that version).
+
+ -- Peter Michael Green   Sun, 06 Aug 2023 13:08:55 +
+
 rust-rustls-native-certs (0.6.3-1) unstable; urgency=medium
 
   [ upstream ]
diff -Nru rust-rustls-native-certs-0.6.3/debian/control 
rust-rustls-native-certs-0.6.3/debian/control
--- rust-rustls-native-certs-0.6.3/debian/control   2023-07-29 
21:03:41.0 +
+++ rust-rustls-native-certs-0.6.3/debian/control   2023-08-06 
13:07:44.0 +
@@ -9,7 +9,7 @@
  librust-rustls-0.21+default-dev ,
  librust-rustls-pemfile-1+default-dev ,
  librust-rustls-webpki-0.101+default-dev ,
- librust-serial-test-0.9+default-dev ,
+ librust-serial-test-2+default-dev ,
  librust-untrusted-0.7+default-dev ,
  libstring-shellquote-perl,
 Maintainer: Jonas Smedegaard 
diff -Nru rust-rustls-native-certs-0.6.3/debian/tests/control 
rust-rustls-native-certs-0.6.3/debian/tests/control
--- rust-rustls-native-certs-0.6.3/debian/tests/control 2023-07-29 
21:03:41.0 +
+++ rust-rustls-native-certs-0.6.3/debian/tests/control 2023-08-06 
13:08:50.0 +
@@ -8,7 +8,7 @@
  librust-rustls-0.21+default-dev,
  librust-rustls-native-certs-0.6-dev,
  librust-rustls-webpki-0.101+default-dev,
- librust-serial-test-0.9+default-dev,
+ librust-serial-test-2+default-dev,
  librust-untrusted-0.7+default-dev,
 Restrictions: allow-stderr, flaky
 
@@ -22,7 +22,7 @@
  librust-rustls-0.21+default-dev,
  librust-rustls-native-certs-0.6+default-dev,
  librust-rustls-webpki-0.101+default-dev,
- librust-serial-test-0.9+default-dev,
+ librust-serial-test-2+default-dev,
  librust-untrusted-0.7+default-dev,
 Restrictions: allow-stderr, flaky
 
@@ -36,6 +36,6 @@
  librust-rustls-0.21+default-dev,
  librust-rustls-native-certs-0.6-dev,
  librust-rustls-webpki-0.101+default-dev,
- librust-serial-test-0.9+default-dev,
+ librust-serial-test-2+default-dev,
  librust-untrusted-0.7+default-dev,
 Restrictions: allow-stderr, flaky
--- End Message ---
--- Begin Message ---
Source: rust-rustls-native-certs
Source-Version: 0.6.3-2
Done: Jonas Smedegaard 

We believe that the bug you reported is fixed in the latest version of
rust-rustls-native-certs, 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.
Jonas Smedegaard  (supplier of updated rust-rustls-native-certs 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 07 Aug 2023 02:26:46 +0200
Source: rust-rustls-native-certs
Architecture: source
Version: 0.6.3-2
Distribution: unstable
Urgency: medium
Maintainer: Jonas Smedegaard 
Changed-By: Jonas Smedegaard 
Closes: 1043175
Changes:
 rust-rustls-native-certs (0.6.3-2) unstable; urgency=medium
 .
   * drop patch 2003, obsoleted by Debian package update;
 update build- and autopkgtest-dependency for crate serial-test;
 closes: bug#1043175, thanks to Peter Green
Checksums-Sha1:
 a122e73918dfc3bf249fad3eacf65f4bf6498b

Bug#964661: marked as done (freebsd-glue: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)

[Debian Bug Tracking System]

Your message dated Mon, 07 Aug 2023 00:48:56 +
with message-id 
and subject line Bug#964661: fixed in freebsd-glue 0.2.22+nmu1
has caused the Debian Bug report #964661,
regarding freebsd-glue: FTBFS: dpkg-gensymbols: error: some symbols or patterns 
disappeared in the symbols file: see diff output below
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.)


-- 
964661: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964661
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: freebsd-glue
Version: 0.2.22
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200709 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
>  fakeroot debian/rules binary
> MAKEFLAGS=-j4 MAKEOBJDIRPREFIX=/<>/obj-deb CFLAGS=" -O2" 
> DESTDIR="/<>/debian/tmp" bmake -m /usr/share/mk-freebsd 
> CC=x86_64-linux-gnu-gcc  obj
> --- _sub.obj ---
> ===> src (obj)
> --- _sub.obj ---
> ===> src/freebsd-glue (obj)
> --- obj ---
> ===> src/crypt (obj)
> --- obj ---
> ===> src/z (obj)
> --- obj ---
> MAKEFLAGS=-j4 MAKEOBJDIRPREFIX=/<>/obj-deb CFLAGS=" -O2" 
> DESTDIR="/<>/debian/tmp" bmake -m /usr/share/mk-freebsd 
> CC=x86_64-linux-gnu-gcc 
> --- _sub.all ---
> ===> src (all)
> --- _sub.all ---
> ===> src/freebsd-glue (all)
> ===> src/crypt (all)
> ===> src/z (all)
> MAKEFLAGS=-j4 MAKEOBJDIRPREFIX=/<>/obj-udeb CFLAGS=" -Os" 
> DESTDIR="/<>/debian/tmp-udeb" bmake -m /usr/share/mk-freebsd 
> CC=x86_64-linux-gnu-gcc RESCUE=yes  obj
> --- _sub.obj ---
> ===> src (obj)
> --- _sub.obj ---
> ===> src/freebsd-glue (obj)
> --- obj ---
> ===> src/crypt (obj)
> --- obj ---
> ===> src/z (obj)
> --- obj ---
> MAKEFLAGS=-j4 MAKEOBJDIRPREFIX=/<>/obj-udeb CFLAGS=" -Os" 
> DESTDIR="/<>/debian/tmp-udeb" bmake -m /usr/share/mk-freebsd 
> CC=x86_64-linux-gnu-gcc RESCUE=yes 
> --- _sub.all ---
> ===> src (all)
> --- _sub.all ---
> ===> src/freebsd-glue (all)
> ===> src/crypt (all)
> ===> src/z (all)
> dh_testdir
> dh_testroot
> dh_prep -a
> dh_installdirs -a
> dh_installdirs: warning: Compatibility levels before 10 are deprecated (level 
> 7 in use)
> mkdir -p /<>/debian/tmp{,-udeb}/{usr/,}lib
> MAKEFLAGS=-j4 MAKEOBJDIRPREFIX=/<>/obj-deb CFLAGS=" -O2" 
> DESTDIR="/<>/debian/tmp" bmake -m /usr/share/mk-freebsd 
> CC=x86_64-linux-gnu-gcc  install
> --- _sub.realinstall ---
> ===> src (install)
> --- _sub.realinstall ---
> ===> src/freebsd-glue (install)
> --- _libinstall ---
> install -o root -g root -m 444   libfreebsd-glue.a 
> /<>/debian/tmp/usr/lib
> install -o root -g root -m 444   libfreebsd-glue_p.a 
> /<>/debian/tmp/usr/lib
> install  -o root -g root -m 444 libfreebsd-glue.so.0 
> /<>/debian/tmp/lib
> ln -s /lib/libfreebsd-glue.so.0  
> /<>/debian/tmp/usr/lib/libfreebsd-glue.so
> ===> src/crypt (install)
> --- _libinstall ---
> install -o root -g root -m 444   libcrypt-freebsd.a 
> /<>/debian/tmp/usr/lib
> install -o root -g root -m 444   libcrypt-freebsd_p.a 
> /<>/debian/tmp/usr/lib
> install  -o root -g root -m 444 libcrypt-freebsd.so.0 
> /<>/debian/tmp/lib
> ln -s /lib/libcrypt-freebsd.so.0  
> /<>/debian/tmp/usr/lib/libcrypt-freebsd.so
> ===> src/z (install)
> --- _libinstall ---
> install -o root -g root -m 444   libz-freebsd.a 
> /<>/debian/tmp/usr/lib
> install -o root -g root -m 444   libz-freebsd_p.a 
> /<>/debian/tmp/usr/lib
> install  -o root -g root -m 444 libz-freebsd.so.0 
> /<>/debian/tmp/lib
> ln -s /lib/libz-freebsd.so.0  
> /<>/debian/tmp/usr/lib/libz-freebsd.so
> MAKEFLAGS=-j4 MAKEOBJDIRPREFIX=/<>/obj-udeb CFLAGS=" -Os" 
> DESTDIR="/<>/debian/tmp-udeb" bmake -m /usr/share/mk-freebsd 
> CC=x86_64-linux-gnu-gcc RESCUE=yes  install
> --- _sub.realinstall ---
> ===> src (install)
> --- _sub.realinstall ---
> ===> src/freebsd-glue (install)
> --- _libinstall ---
> install -o root -g root -m 444   libfreebsd-glue.a 
> /<>/debian/tmp-udeb/usr/lib
> install -o root -g root -m 444   libfreebsd-glue_p.a 
> /<>/debian/tmp-udeb/usr/lib
> install  -o root -g root -m 444 libfreebsd-glue.so.0 
> /<>/debian/tmp-udeb/lib
> ln -s /lib/libfreebsd-glue.so.0  
> /<>/debian/tmp-udeb/usr/lib/libfreebsd-glue.so
> ===> src/crypt (install)
> --- _libinstall ---
> install -o root -g root -m 444   libcrypt-freebsd.a 
> /<>/debian/tmp-udeb/usr/lib
> install -o root -g root -m 444   libcrypt-freebsd_p.a 
> /<>/debian/tmp-udeb/usr/lib
> install  -o root -g root -m 444 libcrypt-freebsd.so.0 
> /<>/debian/tmp-udeb/lib
> ln -s /lib/libcrypt-freebsd.so.0  
> /<>/debian/tmp-udeb/usr/lib/libcrypt-freebsd.so
> ===> src/z (inst

Bug#957230: freebsd-buildutils: ftbfs with GCC-10

[Bastian Germann]

I am uploading a NMU to fix this. The debdiff is attached.diff -Nru freebsd-glue-0.2.22/debian/changelog 
freebsd-glue-0.2.22+nmu1/debian/changelog
--- freebsd-glue-0.2.22/debian/changelog2016-03-05 16:44:54.0 
+0100
+++ freebsd-glue-0.2.22+nmu1/debian/changelog   2023-08-07 01:20:16.0 
+0200
@@ -1,3 +1,12 @@
+freebsd-glue (0.2.22+nmu1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Build with gcc-9. (Closes: #964661)
+  * Include #pragma once in md5.h for freebsd-buildutils.
+  * Temporarily include lorder/tsort workaround. (Closes: #964661)
+
+ -- Bastian Germann   Mon, 07 Aug 2023 01:20:16 +0200
+
 freebsd-glue (0.2.22) unstable; urgency=medium
 
   * Actually use the proper build architecture compiler
diff -Nru freebsd-glue-0.2.22/debian/control 
freebsd-glue-0.2.22+nmu1/debian/control
--- freebsd-glue-0.2.22/debian/control  2016-03-05 02:08:01.0 +0100
+++ freebsd-glue-0.2.22+nmu1/debian/control 2023-08-07 01:18:20.0 
+0200
@@ -7,6 +7,7 @@
  Steven Chamberlain ,
 Build-Depends:
  debhelper (>= 8.0),
+ gcc-9,
  kfreebsd-kernel-headers (>= 10.0~3) [kfreebsd-any],
  freebsd-mk,
  bmake,
diff -Nru freebsd-glue-0.2.22/debian/lorder 
freebsd-glue-0.2.22+nmu1/debian/lorder
--- freebsd-glue-0.2.22/debian/lorder   1970-01-01 01:00:00.0 +0100
+++ freebsd-glue-0.2.22+nmu1/debian/lorder  2023-08-07 01:20:16.0 
+0200
@@ -0,0 +1,2 @@
+#!/bin/sh
+echo $@
diff -Nru freebsd-glue-0.2.22/debian/rules freebsd-glue-0.2.22+nmu1/debian/rules
--- freebsd-glue-0.2.22/debian/rules2016-03-05 01:54:10.0 +0100
+++ freebsd-glue-0.2.22+nmu1/debian/rules   2023-08-07 01:20:16.0 
+0200
@@ -6,7 +6,7 @@
 # Determine host architecture compiler
 DEB_HOST_GNU_TYPE  ?= $(shell dpkg-architecture -qDEB_HOST_GNU_TYPE)
 ifeq ($(origin CC),default)
-CC := $(DEB_HOST_GNU_TYPE)-gcc
+CC := $(DEB_HOST_GNU_TYPE)-gcc-9
 endif
 
 # Determine build architecture compiler
@@ -23,7 +23,7 @@
 endif
 
 DESTDIR = $(CURDIR)/debian/tmp
-PATH := /usr/lib/freebsd:$(PATH)
+PATH := $(CURDIR)/debian:/usr/lib/freebsd:$(PATH)
 PMAKE := \
MAKEFLAGS=$(BSD_MAKEFLAGS) \
MAKEOBJDIRPREFIX=$(CURDIR)/obj-deb \
diff -Nru freebsd-glue-0.2.22/debian/tsort freebsd-glue-0.2.22+nmu1/debian/tsort
--- freebsd-glue-0.2.22/debian/tsort1970-01-01 01:00:00.0 +0100
+++ freebsd-glue-0.2.22+nmu1/debian/tsort   2023-08-07 01:20:16.0 
+0200
@@ -0,0 +1,2 @@
+#!/bin/sh
+sort $@
diff -Nru freebsd-glue-0.2.22/include/md5.h 
freebsd-glue-0.2.22+nmu1/include/md5.h
--- freebsd-glue-0.2.22/include/md5.h   2014-08-25 21:40:17.0 +0200
+++ freebsd-glue-0.2.22+nmu1/include/md5.h  2023-08-07 01:20:16.0 
+0200
@@ -1 +1,2 @@
+#pragma once
 #include 

Processed (with 1 error): your mail

[Debian Bug Tracking System]

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

> severity 1028229 serious
Bug #1028229 [libwmf-0.2-7-gtk] libwmf-0.2-7-gtk: tries to overwrite file in 
libwmf0.2-7-gtk
Severity set to 'serious' from 'normal'
> close 1028229
Bug #1028229 [libwmf-0.2-7-gtk] libwmf-0.2-7-gtk: tries to overwrite file in 
libwmf0.2-7-gtk
Marked Bug as done
> forcemerge 1034959 1028229
Failed to forcibly merge 1034959: Not altering archived bugs; see unarchive.

>
End of message, stopping processing here.

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

Bug#1043176: sccache - update for new serial-test

[Peter Green]

Package: sccache
Severity: serious
Tags: trixie, sid

I just updated the serial-test crate to version 2.0. sccache
needs a small update to the Debian dependency to match. (the Cargo
dependency already allows both versions).

Debdiff attatched.
diff -Nru sccache-0.5.4/debian/changelog sccache-0.5.4/debian/changelog
--- sccache-0.5.4/debian/changelog  2023-07-30 16:13:02.0 +
+++ sccache-0.5.4/debian/changelog  2023-08-06 13:14:32.0 +
@@ -1,3 +1,11 @@
+sccache (0.5.4-7.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Update Debian dependency on serial-test to version 2
+(Cargo dependencies already allow it).
+
+ -- root   Sun, 06 Aug 2023 13:14:32 +
+
 sccache (0.5.4-7) unstable; urgency=medium
 
   * fix yet again: reduce lto further on mipsel
diff -Nru sccache-0.5.4/debian/control sccache-0.5.4/debian/control
--- sccache-0.5.4/debian/control2023-07-27 16:54:09.0 +
+++ sccache-0.5.4/debian/control2023-08-06 13:13:12.0 +
@@ -58,7 +58,7 @@
  librust-serde-1+default-dev,
  librust-serde-1+derive-dev,
  librust-serde-json-1+default-dev,
- librust-serial-test-0.9+default-dev ,
+ librust-serial-test-2+default-dev ,
  librust-sha2-0.10+default-dev,
  librust-strip-ansi-escapes-0.1+default-dev,
  librust-tar-0.4+default-dev,

Bug#1043175: rust-rustls-native-certs - update for new serial-test

[Peter Green]

Package: rust-rustls-native-certs
Severity: serious
Tags: trixie, sid

I just updated the serial-test crate to version 2.0. rust-rustls-native-certs
needs a small update to the Debian dependency to match. (the Cargo
dependency already allows both versions).

Debdiff attatched.
diff -Nru rust-rustls-native-certs-0.6.3/debian/changelog 
rust-rustls-native-certs-0.6.3/debian/changelog
--- rust-rustls-native-certs-0.6.3/debian/changelog 2023-07-29 
21:03:41.0 +
+++ rust-rustls-native-certs-0.6.3/debian/changelog 2023-08-06 
13:08:55.0 +
@@ -1,3 +1,11 @@
+rust-rustls-native-certs (0.6.3-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Update debian dependencies for rust-serial-test 2
+(Cargo dependencies already allow that version).
+
+ -- Peter Michael Green   Sun, 06 Aug 2023 13:08:55 +
+
 rust-rustls-native-certs (0.6.3-1) unstable; urgency=medium
 
   [ upstream ]
diff -Nru rust-rustls-native-certs-0.6.3/debian/control 
rust-rustls-native-certs-0.6.3/debian/control
--- rust-rustls-native-certs-0.6.3/debian/control   2023-07-29 
21:03:41.0 +
+++ rust-rustls-native-certs-0.6.3/debian/control   2023-08-06 
13:07:44.0 +
@@ -9,7 +9,7 @@
  librust-rustls-0.21+default-dev ,
  librust-rustls-pemfile-1+default-dev ,
  librust-rustls-webpki-0.101+default-dev ,
- librust-serial-test-0.9+default-dev ,
+ librust-serial-test-2+default-dev ,
  librust-untrusted-0.7+default-dev ,
  libstring-shellquote-perl,
 Maintainer: Jonas Smedegaard 
diff -Nru rust-rustls-native-certs-0.6.3/debian/tests/control 
rust-rustls-native-certs-0.6.3/debian/tests/control
--- rust-rustls-native-certs-0.6.3/debian/tests/control 2023-07-29 
21:03:41.0 +
+++ rust-rustls-native-certs-0.6.3/debian/tests/control 2023-08-06 
13:08:50.0 +
@@ -8,7 +8,7 @@
  librust-rustls-0.21+default-dev,
  librust-rustls-native-certs-0.6-dev,
  librust-rustls-webpki-0.101+default-dev,
- librust-serial-test-0.9+default-dev,
+ librust-serial-test-2+default-dev,
  librust-untrusted-0.7+default-dev,
 Restrictions: allow-stderr, flaky
 
@@ -22,7 +22,7 @@
  librust-rustls-0.21+default-dev,
  librust-rustls-native-certs-0.6+default-dev,
  librust-rustls-webpki-0.101+default-dev,
- librust-serial-test-0.9+default-dev,
+ librust-serial-test-2+default-dev,
  librust-untrusted-0.7+default-dev,
 Restrictions: allow-stderr, flaky
 
@@ -36,6 +36,6 @@
  librust-rustls-0.21+default-dev,
  librust-rustls-native-certs-0.6-dev,
  librust-rustls-webpki-0.101+default-dev,
- librust-serial-test-0.9+default-dev,
+ librust-serial-test-2+default-dev,
  librust-untrusted-0.7+default-dev,
 Restrictions: allow-stderr, flaky

Bug#1043174: precious - update for new serial-test

[Peter Green]

Package: precious
Severity: serious
Tags: trixie, sid

I just updated the serial-test crate to version 2.0. Precious
needs a small update to the Debian dependency to match. (the Cargo
dependency already allows both versions).

Debdiff attatched.diff -Nru precious-0.5.1+20230704/debian/changelog 
precious-0.5.1+20230704/debian/changelog
--- precious-0.5.1+20230704/debian/changelog2023-07-11 21:20:29.0 
+
+++ precious-0.5.1+20230704/debian/changelog2023-08-06 12:48:08.0 
+
@@ -1,3 +1,11 @@
+precious (0.5.1+20230704-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Update Debian dependency on serial-test to 2.0.
+(cargo dependency already allows the new version)
+
+ -- Peter Michael Green   Sun, 06 Aug 2023 12:48:08 +
+
 precious (0.5.1+20230704-1) unstable; urgency=medium
 
   [ upstream ]
diff -Nru precious-0.5.1+20230704/debian/control 
precious-0.5.1+20230704/debian/control
--- precious-0.5.1+20230704/debian/control  2023-07-11 21:20:29.0 
+
+++ precious-0.5.1+20230704/debian/control  2023-08-06 12:47:55.0 
+
@@ -33,7 +33,7 @@
  librust-regex-1+default-dev (>= 1.7),
  librust-serde-1+default-dev (>= 1.0.147),
  librust-serde-1+derive-dev (>= 1.0.147),
- librust-serial-test-0.9+default-dev ,
+ librust-serial-test-2.0+default-dev ,
  librust-tempfile-3+default-dev (>= 3.3) ,
  librust-test-case-2+default-dev ,
  librust-thiserror-1+default-dev (>= 1.0.37),

Bug#1043173: wlgreet: Fails to start sway due to incorrect configuration

[Diederik de Haas]

On 07 Aug 2023 00:18:15 +0200 Diederik de Haas  wrote:
> Package: wlgreet
> Version: 0.4.1-1
> Severity: grave
> Tags: patch
> Justification: renders package unusable
> 
> I'm preparing a MR on Salsa and once I have a bug number for this bug,
> I'll submit it.

https://salsa.debian.org/debian/wlgreet/-/merge_requests/2

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

Bug#1043173: wlgreet: Fails to start sway due to incorrect configuration

[Diederik de Haas]

Package: wlgreet
Version: 0.4.1-1
Severity: grave
Tags: patch
Justification: renders package unusable

If you switch greetd's config to start wlgreet, you get presented a
screen to input your username and the next screen is for the password.
When you then press enter sway is supposed to start and it appears that
'something' is happening, but then you get thrown back to wlgreet's
login screen. It appears that the configuration is incorrect. After I
fixed that, I did login and a sway session (?) was started.

I'm preparing a MR on Salsa and once I have a bug number for this bug,
I'll submit it.

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (101, 'experimental')
Architecture: arm64 (aarch64)

Kernel: Linux 6.4.0-1-arm64 (SMP w/4 CPU threads)
Locale: LANG=C.UTF-8, LC_CTYPE=C.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 wlgreet depends on:
ii  libc6  2.37-6
ii  libgcc-s1  13.2.0-1
ii  sway   1.8.1-2

wlgreet recommends no packages.

wlgreet suggests no packages.

-- Configuration Files:
/etc/greetd/sway-config changed:
exec "/usr/sbin/wlgreet --command sway; swaymsg exit"
bindsym Mod4+shift+e exec swaynag \
-t warning \
-m 'What do you want to do?' \
-b 'Poweroff' 'systemctl poweroff -i' \
-b 'Reboot' 'systemctl reboot -i'
output * bg 
/usr/share/desktop-base/active-theme/lockscreen/contents/images/3840x2160.svg 
fill
include /etc/sway/config.d/*
include /etc/greetd/sway-config.d/*

/etc/greetd/wlgreet.tom [Errno 2] No such file or directory: 
'/etc/greetd/wlgreet.tom'

-- no debconf information

Bug#1042218: marked as done (ruby-moneta: FTBFS: ERROR: Test "ruby3.1" failed: cannot load such file -- ox/ox)

[Debian Bug Tracking System]

Your message dated Sun, 06 Aug 2023 21:05:26 +
with message-id 
and subject line Bug#1042218: fixed in ruby-ox 2.14.17-1
has caused the Debian Bug report #1042218,
regarding ruby-moneta: FTBFS: ERROR: Test "ruby3.1" failed: cannot load 
such file -- ox/ox
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.)


-- 
1042218: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042218
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-moneta
Version: 1.5.2-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):
> cannot load such file -- ox/ox
>   Shared Example Group: :transform_value called from ./spec/helper.rb:298
>   # ./lib/moneta/transformer.rb:350:in `require'
>   # ./lib/moneta/transformer.rb:350:in `block in compile_transformer'
>   # ./lib/moneta/transformer.rb:348:in `each'
>   # ./lib/moneta/transformer.rb:348:in `compile_transformer'
>   # ./lib/moneta/transformer.rb:63:in `compile'
>   # ./lib/moneta/transformer.rb:38:in `new'
>   # ./lib/moneta/builder.rb:65:in `new_proxy'
>   # ./lib/moneta/builder.rb:25:in `block in build'
>   # ./lib/moneta/builder.rb:23:in `each'
>   # ./lib/moneta/builder.rb:23:in `inject'
>   # ./lib/moneta/builder.rb:23:in `build'
>   # ./lib/moneta.rb:167:in `build'
>   # ./spec/moneta/proxies/transformer/transformer_ox_spec.rb:3:in `block 
> (2 levels) in '
>   # ./spec/helper.rb:315:in `instance_eval'
>   # ./spec/helper.rb:315:in `new_store'
>   # ./spec/helper.rb:291:in `block in moneta_specs'
>   # 
> /usr/share/rubygems-integration/all/gems/rspec-retry-0.6.2/lib/rspec/retry.rb:124:in
>  `block in run'
>   # 
> /usr/share/rubygems-integration/all/gems/rspec-retry-0.6.2/lib/rspec/retry.rb:110:in
>  `loop'
>   # 
> /usr/share/rubygems-integration/all/gems/rspec-retry-0.6.2/lib/rspec/retry.rb:110:in
>  `run'
>   # 
> /usr/share/rubygems-integration/all/gems/rspec-retry-0.6.2/lib/rspec_ext/rspec_ext.rb:12:in
>  `run_with_retry'
>   # 
> /usr/share/rubygems-integration/all/gems/rspec-retry-0.6.2/lib/rspec/retry.rb:37:in
>  `block (2 levels) in setup'
>   # --
>   # --- Caused by: ---
>   # LoadError:
>   #   cannot load such file -- /usr/lib/ruby/vendor_ruby/ox.so
>   #   ./lib/moneta/transformer.rb:350:in `require'
> 
> Finished in 2 minutes 13.5 seconds (files took 0.67973 seconds to load)
> 1272 examples, 94 failures
> 
> Failed examples:
> 
> rspec ./spec/moneta/proxies/transformer/transformer_ox_spec.rb:15 # 
> transformer_ox compile transformer class
> rspec './spec/moneta/proxies/transformer/transformer_ox_spec.rb[1:1:1]' # 
> transformer_ox create feature creates the given key
> rspec './spec/moneta/proxies/transformer/transformer_ox_spec.rb[1:1:2]' # 
> transformer_ox create feature creates raw value with the given key
> rspec './spec/moneta/proxies/transformer/transformer_ox_spec.rb[1:1:3]' # 
> transformer_ox create feature does not create a key if it exists
> rspec './spec/moneta/proxies/transformer/transformer_ox_spec.rb[1:1:4]' # 
> transformer_ox create feature supports Mutex
> rspec './spec/moneta/proxies/transformer/transformer_ox_spec.rb[1:2:1:1]' # 
> transformer_ox each_key feature when a block is not given returns an empty 
> enum when there are no keys
> rspec './spec/moneta/proxies/transformer/transformer_ox_spec.rb[1:2:1:2]' # 
> transformer_ox each_key feature when a block is not given returns collection 
> with the stored key/s
> rspec './spec/moneta/proxies/transformer/transformer_ox_spec.rb[1:2:1:3]' # 
> transformer_ox each_key feature when a block is not given when a lazy size 
> implementation exist it returns the size of the collection or nil
> rspec './spec/moneta/proxies/transformer/transformer_ox_spec.rb[1:2:1:4]' # 
> transformer_ox each_key feature when a block is not given doesn't duplicate 
> keys
> rspec './spec/moneta/proxies/transformer/transformer_ox_spec.rb[1:2:1:5]' # 
> transformer_ox each_key feature when a block is not given doesn't return 
> deleted keys
> rspec './spec/moneta/proxies/transformer/transformer_ox_spec.rb[1:2:1:6]' # 
> transformer_ox each_key feature when a block is not given allows checking and 
> retrieving entries while enumerating
> rspec './spec/moneta/proxies/transformer/transformer_ox_spec.rb[1:2:1:7]' # 
> transformer_ox each_key feature when a block is not gi

Bug#1043048: marked as done (openblas: gives wrong results on mips64el, ignores test failures)

[Debian Bug Tracking System]

Your message dated Sun, 06 Aug 2023 20:43:44 +
with message-id 
and subject line Bug#1043048: fixed in openblas 0.3.23+ds-3
has caused the Debian Bug report #1043048,
regarding openblas: gives wrong results on mips64el, ignores test failures
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.)


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

Package: libopenblas0-pthread
Version: 0.3.23+ds-2
Control: affects -1 src:statsmodels
Severity: serious
Justification: the default BLAS should NOT silently give wrong answers
(i.e. if there's no easy way to actually fix this, please switch the 
default on mips64el back to atlas, and consider removing this package 
from mips64el)


statsmodels recently (between 0.14.0+dfsg-1 and -2) started to FTBFS on 
mips64el with multiple wrong test results.  The most obviously relevant 
change between those is that the installed BLAS changed from atlas to 
openblas.


openblas' own tests on mips64el ( 
https://buildd.debian.org/status/fetch.php?pkg=openblas&arch=mips64el&ver=0.3.23%2Bds-2&stamp=1686760279&raw=0 
) have 64 instances of "FATAL ERROR - COMPUTED RESULT IS LESS THAN HALF 
ACCURATE".  (I don't know why this isn't failing the build, which is 
possibly a bug in itself.)


openblas upstream are not _obviously_ aware of this.  Given the 
existence of .github/workflows/mips64.yml, this suggests it _may_ be 
nontrivial to reproduce in qemu.
--- End Message ---
--- Begin Message ---
Source: openblas
Source-Version: 0.3.23+ds-3
Done: Sébastien Villemot 

We believe that the bug you reported is fixed in the latest version of
openblas, 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.
Sébastien Villemot  (supplier of updated openblas 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: Sun, 06 Aug 2023 20:45:18 +0200
Source: openblas
Architecture: source
Version: 0.3.23+ds-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Sébastien Villemot 
Closes: 1039904 1043048
Changes:
 openblas (0.3.23+ds-3) unstable; urgency=medium
 .
   * mips64-generic.patch: new patch from upstream.
 Fixes incorrect numerical results on mips64el. (Closes: #1043048)
   * shared-blas-lapack.patch: restore missing symbols in liblapack64.so.3.
 Many symbols were inadvertently dropped in version 0.3.22+ds-1,
 because of the overhaul of no-embedded-lapack.patch that removed the
 lapack64-netlib directory. (Closes: #1039904)
   * shared-blas-lapack.patch: add missing clean rule for 
lib{blas,lapack}64.so.3
   * Remove all references to kfreebsd-{amd64,i386} ports
   * README.Debian: update binary packages names for custom installation
 procedure
Checksums-Sha1:
 5f24c0b74d1bac0ac5e3f4ac65751b5b2217eeba 4419 openblas_0.3.23+ds-3.dsc
 0e3e1ef117ca63005839f3f6965289899b5ea9dd 24372 
openblas_0.3.23+ds-3.debian.tar.xz
 6ffc49bf930925fa459d178cff986e04f8fda240 13139 
openblas_0.3.23+ds-3_amd64.buildinfo
Checksums-Sha256:
 70bfdbe0cdf6452c218145b81c92512e60dd6b36de8b4a22096e41dfc1a3a005 4419 
openblas_0.3.23+ds-3.dsc
 386c2ef24b62da25ecae28fe3842aaea02d288bc8795156a6bbee20b12808086 24372 
openblas_0.3.23+ds-3.debian.tar.xz
 c76368f777c5c9c053f00408979d36a23eb654a2374850b7a3718faeef7fc1fd 13139 
openblas_0.3.23+ds-3_amd64.buildinfo
Files:
 730c2018ebda924f635d73d218dd1cbd 4419 devel optional openblas_0.3.23+ds-3.dsc
 93a786c9546d05bcb42dda9383e5fdbe 24372 devel optional 
openblas_0.3.23+ds-3.debian.tar.xz
 97365728fea344553bf59f798b14db98 13139 devel optional 
openblas_0.3.23+ds-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEU5UdlScuDFuCvoxKLOzpNQ7OvkoFAmTP/7MACgkQLOzpNQ7O
vkrHuw/+Pyr8DHAutUOq5QocyLOSyDKE/Je1AKgnOKOOq2ZedVSkYROToMMypDLq
jmXncuIK335L9BgONz/qYUUp5lN7DNiDgCKIRUIuo1YbS0rugXR1pruj3p9dNJ76
xx633KAJWINNe+e/bxzThkcE+8g5CL+aRHVndBeBGfN7Yf8IcL7e1KrI6ULhPZvT
RNXWQqixH+DYqX6jbWvPLn0wvJ3uzhj6YCPskdrDzMAqsYyFWrFwlTOP65Yu7alI
HFJIldiFQTlAgs5WuBcWA6dot7VC3yyKnZaF110loHsvhGPr8c5aMKRlrtPoLU60
v4CqsOsig4Ys/3tU6gJzHnKd

Bug#1043167: RM: graphmonkey -- RoQA; low popcon; depends on gtk2

[Bastian Germann]

Source: graphmonkey
Version: 1.7-4.2
Severity: serious

Please consider removing graphmonkey. It build depends on 
libgtk2.0-cil-dev which should be removed in oder to get rid of gtk2 
eventually.


I am filing this as serious so that people recognize this bug.
If nobody complains about the possible removal when the package is 
autoremoved, I am going to file the RM bug.

Processed: severity of 1043161 is grave

[Debian Bug Tracking System]

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

> severity 1043161 grave
Bug #1043161 [src:i2p] i2p: CVE-2023-36325
Severity set to 'grave' from 'normal'
> thanks
Stopping processing here.

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

Bug#1037567: abseil: ftbfs with GCC-13

[Benjamin Barenblat]

Thank you for the patch, Aurelien! I’ve applied it to the 20220623.1
release and uploaded it to unstable as 20220623.1-2.

Bug#1040801: mcomix: pillow 10.0.0 not recognized as higher than 6.0.0

[Olivier Allard-Jacquin]

Hi,

On Mon, 10 Jul 2023 22:08:46 +0200 Sebastien KALT  wrote:

Package: mcomix
Version: 2.1.0-2
Severity: grave
Justification: renders package unusable


Same issue here (Debian testing up to date).

The issue is here :
/usr/lib/python3/dist-packages/mcomix/run.py:

 if PIL.__version__ < '6.0.0':


	I guess that issue root cause is due to "<", who is probably not the 
good way to compare strings under python. Python look like understand 
that "6.0" is after "10.0", due to comparison-only between 6 and 1...


I'm not a python developer, so here a quick and dirty patch:

# diff /usr/lib/python3/dist-packages/mcomix/run.py.bak 
/usr/lib/python3/dist-packages/mcomix/run.py

143c143
< if PIL.__version__ < '6.0.0':
---
> if PIL.__version__ < '10.0.0':

With this modification, mcomix work fine.

	Real python developers, or packagers should provide a better and more 
python-style than me ! :)


Best regards,
Olivier

Bug#1025638: marked as done (ayatana-indicator-session: autopkgtest depends on transitional policykit-1 package)

[Debian Bug Tracking System]

Your message dated Sun, 06 Aug 2023 18:49:03 +
with message-id 
and subject line Bug#1025638: fixed in ayatana-indicator-session 22.9.2-3
has caused the Debian Bug report #1025638,
regarding ayatana-indicator-session: autopkgtest depends on transitional 
policykit-1 package
to be marked as done.

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

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


-- 
1025638: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025638
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ayatana-indicator-session
Version: 22.9.0-2
Severity: normal
User: pkg-utopia-maintain...@lists.alioth.debian.org
Usertags: policykit-1
Control: block 1025540 by -1

This package's autopkgtest-based test suite depends on the transitional
package policykit-1, which has been separated into polkitd, pkexec and
(deprecated) polkitd-pkla packages.

If the tests communicate with polkitd via D-Bus, please represent that
as a Depends on polkitd.

If the tests run /usr/bin/pkexec, please represent that as a Depends
on pkexec.

If the tests require legacy .pkla files to be processed, please represent
that as a Depends on polkitd-pkla (but note that this package will probably
be removed from testing/unstable after Debian 12 is released).

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

This is part of a mass bug filing, see
.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Source: ayatana-indicator-session
Source-Version: 22.9.2-3
Done: Marius Gripsgard 

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

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

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

Debian distribution maintenance software
pp.
Marius Gripsgard  (supplier of updated 
ayatana-indicator-session 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: Sun, 06 Aug 2023 20:32:12 +0200
Source: ayatana-indicator-session
Architecture: source
Version: 22.9.2-3
Distribution: unstable
Urgency: medium
Maintainer: Ayatana Packagers 
Changed-By: Marius Gripsgard 
Closes: 1025638
Changes:
 ayatana-indicator-session (22.9.2-3) unstable; urgency=medium
 .
   * debian/tests: Drop policykit as depends, dropped upstream
 (closes: #1025638)
Checksums-Sha1:
 64c320e999c352b41c5090dfa2d15e1fa3b8eab4 2123 
ayatana-indicator-session_22.9.2-3.dsc
 d9fa9bc83b84043a6a194cdb755b966f289f0cee 327351 
ayatana-indicator-session_22.9.2.orig.tar.gz
 f875a278038a3c1cfad08db9b25ff76a5844fbd6 833 
ayatana-indicator-session_22.9.2.orig.tar.gz.asc
 6ecbbf29185a6166bd0078c152f93daf8877022a 15152 
ayatana-indicator-session_22.9.2-3.debian.tar.xz
 aaeb74079e890c4e6c36e7430f65e98b964c1e08 9381 
ayatana-indicator-session_22.9.2-3_source.buildinfo
Checksums-Sha256:
 adcbe2a6ede3f99153689e76b779d3be574e8cdbe1a48f4916da311e43c5d480 2123 
ayatana-indicator-session_22.9.2-3.dsc
 6d28125d6856653f20392b4a66bbceb06cb4ee4272036f798241114ad9ec7412 327351 
ayatana-indicator-session_22.9.2.orig.tar.gz
 c2cb8616e73e8ef52f0cc886c96e06106eef3a04bcc27d30ae14cefb08376d89 833 
ayatana-indicator-session_22.9.2.orig.tar.gz.asc
 2cf00c075aa98e4b43230da5af5acc4424cc1cc8aa4f61ca9bcdc503a90cd37f 15152 
ayatana-indicator-session_22.9.2-3.debian.tar.xz
 7037b253b6de66d4ebd2d602926a2555da0f6b0c00e9379ed3a25768011c496a 9381 
ayatana-indicator-session_22.9.2-3_source.buildinfo
Files:
 0e977db0df05c84bcacff908e21de4d5 2123 misc optional 
ayatana-indicator-session_22.9.2-3.dsc
 0e15ec6f02c18718870dd3ce0f1c36fb 327351 misc optional 
ayatana-indicator-session_22.9.2.orig.tar.gz
 9806f51be9c3f909699e7fad2834fef6 833 misc optional 
ayatana-indicator-session_22.9.2.orig.tar.gz.asc
 2e08b0e41f973b88fd0f11f613119359 15152 misc optional 
ayatana-indicator-session_22.9.2-3.debian.tar.xz
 fd9057b7cdf34b3ebf1f337447ee3be6 9381 misc optional 
ayatana-indicator-session_22.9.2-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iIsEARYIADMWIQT0KegCiCm6mh1JH2jwqyDIdgBMKgUCZM/nbxUcbWFyaW9ncmlw
QGRlYmlhbi5vcmcACgkQ8KsgyHYATCpeSgD+OOd0SgZ7YjT+vcMEJcXvvMUHnh

Processed: forcibly merging 1043121 1043135

[Debian Bug Tracking System]

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

> forcemerge 1043121 1043135
Bug #1043121 {Done: Guido Günther } [phoc] Needs breaks phosh 
<< 0.30.0~
Bug #1043135 [phoc] phosh 0.29.0-1 crashes with phoc 0.30 in trixie
Severity set to 'critical' from 'normal'
Marked Bug as done
Marked as fixed in versions phoc/0.30.0+ds-2.
Marked as found in versions phoc/0.30.0+ds-1.
Merged 1043121 1043135
> thanks
Stopping processing here.

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

Bug#1005717: marked as done (nzbget: FTBFS with OpenSSL 3.0)

[Debian Bug Tracking System]

Your message dated Sun, 06 Aug 2023 18:21:56 +
with message-id 
and subject line Bug#1005717: fixed in nzbget 21.2~r2333+dfsg-1
has caused the Debian Bug report #1005717,
regarding nzbget: FTBFS with OpenSSL 3.0
to be marked as done.

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

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


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

Source: nzbget
Version: 21.0+dfsg-2
Severity: important
Tags: bookworm sid
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: ftbfs-3.0

Your package is failing to build using OpenSSL 3.0 with the
following error:

| daemon/connect/TlsSocket.cpp: In static member function ‘static void 
TlsSocket::Final()’:
| daemon/connect/TlsSocket.cpp:192:9: error: ‘FIPS_mode_set’ was not declared 
in this scope
|   192 | FIPS_mode_set(0);
|   | ^
| daemon/connect/TlsSocket.cpp: In member function ‘bool TlsSocket::Start()’:
| daemon/connect/TlsSocket.cpp:392:56: warning: ‘EC_KEY* 
EC_KEY_new_by_curve_name(int)’ is deprecated: Since OpenSSL 3.0 
[-Wdeprecated-declara tions]
|   392 | EC_KEY* ecdh = 
EC_KEY_new_by_curve_name(NID_X9_62_prime256v1);
|   |
^~
| In file included from /usr/include/openssl/x509.h:33,
|  from /usr/include/openssl/ssl.h:31,
|  from ./daemon/main/nzbget.h:257,
|  from daemon/connect/TlsSocket.cpp:21:
| /usr/include/openssl/ec.h:996:31: note: declared here
|   996 | OSSL_DEPRECATEDIN_3_0 EC_KEY *EC_KEY_new_by_curve_name(int nid);
|   |   ^~~~
| daemon/connect/TlsSocket.cpp:402:36: warning: ‘void EC_KEY_free(EC_KEY*)’ is 
deprecated: Since OpenSSL 3.0 [-Wdeprecated-declarations]
|   402 | EC_KEY_free(ecdh);
|   | ~~~^~
| In file included from /usr/include/openssl/x509.h:33,
|  from /usr/include/openssl/ssl.h:31,
|  from ./daemon/main/nzbget.h:257,
|  from daemon/connect/TlsSocket.cpp:21:
| /usr/include/openssl/ec.h:1001:28: note: declared here
|  1001 | OSSL_DEPRECATEDIN_3_0 void EC_KEY_free(EC_KEY *key);
|   |^~~
| daemon/connect/TlsSocket.cpp:406:28: warning: ‘void EC_KEY_free(EC_KEY*)’ is 
deprecated: Since OpenSSL 3.0 [-Wdeprecated-declarations]
|   406 | EC_KEY_free(ecdh);
|   | ~~~^~
| In file included from /usr/include/openssl/x509.h:33,
|  from /usr/include/openssl/ssl.h:31,
|  from ./daemon/main/nzbget.h:257,
|  from daemon/connect/TlsSocket.cpp:21:
| /usr/include/openssl/ec.h:1001:28: note: declared here
|  1001 | OSSL_DEPRECATEDIN_3_0 void EC_KEY_free(EC_KEY *key);
|   |^~~
| daemon/connect/Connection.cpp: In function ‘hostent* 
android_read_hostent(FILE*, hostent*, char*, size_t)’:
| daemon/connect/Connection.cpp:1196:22: warning: ignoring return value of 
‘size_t fread(void*, size_t, size_t, FILE*)’ declared with attribut e 
‘warn_unused_result’ [-Wunused-result]
|  1196 | fread(&size, 1, sizeof(size), proxy);
|   | ~^~~
| make[2]: *** [Makefile:1774: daemon/connect/TlsSocket.o] Error 1

For more information see:
https://www.openssl.org/docs/man3.0/man7/migration_guide.html

Sebastian
--- End Message ---
--- Begin Message ---
Source: nzbget
Source-Version: 21.2~r2333+dfsg-1
Done: Andreas Moog 

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

Debian distribution maintenance software
pp.
Andreas Moog  (supplier of updated nzbget 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: Sun, 06 Aug 2023 19:07:23 +0200
Source: nzbget
Architecture: source
Version: 21.2~r2333+dfsg-1
Distribution: experimental
Urgency: medium
Maintainer: Andreas Moog

Bug#1007134: marked as done (nzbget: wrong architecture target for source files on armhf)

[Debian Bug Tracking System]

Your message dated Sun, 06 Aug 2023 18:21:56 +
with message-id 
and subject line Bug#1007134: fixed in nzbget 21.2~r2333+dfsg-1
has caused the Debian Bug report #1007134,
regarding nzbget: wrong architecture target for source files on armhf
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.)


-- 
1007134: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007134
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nzbget
Version: 21.0+dfsg-2
Severity: important
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu jammy ubuntu-patch

Hi Andreas,

The nzbget package is failing to build from source in Ubuntu on armhf,
because Ubuntu's compiler is currently stricter with compiler options than
Debian's:

[...]
g++ -DHAVE_CONFIG_H -I.  -I./daemon/connect -I./daemon/extension 
-I./daemon/feed -I./daemon/frontend -I./daemon/main -I./daemon/nntp 
-I./daemon/postprocess -I./daemon/queue -I./daemon/remote -I./daemon/util 
-I./daemon/nserv -I./lib/par2 -I./lib/yencode  -Wdate-time -D_FORTIFY_SOURCE=2 
-I/usr/include/libxml2 -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600-g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -fpermissive -march=armv8-a+crc -fpermissive -c -o 
lib/yencode/AcleCrc.o lib/yencode/AcleCrc.cpp
cc1plus: error: ‘-mfloat-abi=hard’: selected architecture lacks an FPU
make[2]: *** [Makefile:1774: lib/yencode/AcleCrc.o] Error 1
[...]

  
(https://launchpad.net/ubuntu/+source/nzbget/21.0+dfsg-2ubuntu1/+build/22597345)

The compiler doesn't like the use of -march=armv8-a+crc as a target because
this override of a default target doesn't specify the presence of an FPU,
which is required for hard-float (the 'hf' in armhf).

However, the correct fix here is NOT to pass -march=armv8-a+crc+fp, because
armv8 code is not guaranteed to run on the armhf architecture!  The baseline
for armhf in Debian is armv6 and in Ubuntu is armv7, so having code that
doesn't do CPU detection but is built for armv8 (or neon/simd, as appears
elsewhere in the build scripts) will generate SIGILL on various hardware
that is supposed to be supported.

I therefore think the simplest correct fix is to disable these optimizations
for armhf - if someone wants better performance on the hardware in question
they can use the arm64 build instead.

Attached is the patch I've uploaded to Ubuntu to solve this there.  Please
consider applying it in Debian as well.

Thanks,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru nzbget-21.0+dfsg/debian/patches/armv7-only.patch 
nzbget-21.0+dfsg/debian/patches/armv7-only.patch
--- nzbget-21.0+dfsg/debian/patches/armv7-only.patch1969-12-31 
16:00:00.0 -0800
+++ nzbget-21.0+dfsg/debian/patches/armv7-only.patch2022-03-11 
10:19:23.0 -0800
@@ -0,0 +1,24 @@
+Description: don't use NEON, armv8 instructions on armhf
+ The guaranteed ISA for armhf is armv7+fpu and does not include SIMD or
+ armv8.  Do not try to optimize the armhf binary with these extensions;
+ users who want this should run the arm64 port.
+Author: Steve Langasek 
+Last-Update: 2022-03-11
+Forwarded: no
+
+Index: nzbget-21.0+dfsg/configure.ac
+===
+--- nzbget-21.0+dfsg.orig/configure.ac
 nzbget-21.0+dfsg/configure.ac
+@@ -572,11 +572,6 @@
+   PCLMUL_CXXFLAGS="-msse4.1 -mpclmul"
+   USE_SIMD=yes
+   ;;
+-  arm*)
+-  NEON_CXXFLAGS="-mfpu=neon"
+-  ACLECRC_CXXFLAGS="-march=armv8-a+crc -fpermissive"
+-  USE_SIMD=yes
+-  ;;
+   aarch64)
+   ACLECRC_CXXFLAGS="-march=armv8-a+crc -fpermissive"
+   USE_SIMD=yes
diff -Nru nzbget-21.0+dfsg/debian/patches/series 
nzbget-21.0+dfsg/debian/patches/series
--- nzbget-21.0+dfsg/debian/patches/series  2021-12-07 04:28:18.0 
-0800
+++ nzbget-21.0+dfsg/debian/patches/series  2022-03-11 10:17:49.0 
-0800
@@ -1,2 +1,3 @@
 0001-dont-embed-libraries.patch
 fips_mode.patch
+armv7-only.patch
--- End Message ---
--- Begin Message ---
Source: nzbget
Source-Version: 21.2~r2333+dfsg-1
Done: Andreas Moog 

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

A summary of the changes b

Bug#1041499: meson: glib2.0 FTBFS on mips64el: "native build" but then "Can not run test applications in this cross environment"

[Eli Schwartz]

On Wed, 19 Jul 2023 20:12:08 +0100 Simon McVittie  wrote:

> glib2.0's meson.build has several calls to 'cc.run(...)' guarded by
> a check for 'cc_can_run = meson.can_run_host_binaries()'.
> 
> On mips64el, Meson seems confused about whether this is a native or
> cross build. At first, it correctly reports that this is a native build:
> 
> 
> > The Meson build system
> > Version: 1.2.0
> > Source dir: /<>
> > Build dir: /<>/debian/build/deb
> > Build type: native build
> > Project name: glib
> > Project version: 2.76.4
> 
> but then later, cc.run() fails:
> 
> > ../../../meson.build:1127:14: ERROR: Can not run test applications in this 
> > cross environment.


Update: Simon wrote a fix for this and it is merged upstream and tagged
for the .1 maintenance release.

https://github.com/mesonbuild/meson/pull/12080


-- 
Eli Schwartz

Processed: Re: naev: FTBFS on mips64el

[Debian Bug Tracking System]

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

> affects 1041454 src:gnome-builder
Bug #1041454 [meson] naev: FTBFS on mips64el
Bug #1041499 [meson] meson: glib2.0 FTBFS on mips64el: "native build" but then 
"Can not run test applications in this cross environment"
Ignoring request to set affects of bug 1041454 to the same value previously set
Ignoring request to set affects of bug 1041499 to the same value previously set
>
End of message, stopping processing here.

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

Bug#1043059: abseil/experimental FTBFS on mipsel

[Adrian Bunk]

On Sat, Aug 05, 2023 at 03:34:07PM +0300, Adrian Bunk wrote:
>...
> The patch below works around the address space issue, but later there is a 
> test failure:
> 
> ...
> 86: ./absl/log/scoped_mock_log.cc:39: Failure
> 86: Mock function called more times than expected - returning directly.
> 86: Function call: Log(INFO, @0x7f9b9b2c "./absl/log/log_format_test.cc", 
> @0x7f9b9b14 "nan")
> 86:  Expected: to be never called
> 86:Actual: called once - over-saturated and active
> 86: ./absl/log/log_format_test.cc:611: Failure
> 86: Actual function call count doesn't match EXPECT_CALL(test_sink, 
> Send(AllOf( TextMessage(MatchesOstream(comparison_stream)), 
> TextMessage(AnyOf(Eq("-nan"), Eq("nan"), Eq("NaN"), Eq("-nan(ind)"))), 
> ::testing::_)))...
> 86:  Expected: to be called once
> 86:Actual: never called - unsatisfied and active
> 86: [  FAILED  ] FloatingPointLogFormatTest/0.NegativeNaN, where TypeParam = 
> float (0 ms)
>...

FTR, this failure might be related to 
https://en.wikipedia.org/wiki/NaN#Encoding

cu
Adrian

Processed: transition: mutter/gnome-shell 44

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + src:mutter src:gnome-shell
Bug #1043144 [release.debian.org] transition: mutter/gnome-shell 44
Added indication that 1043144 affects src:mutter and src:gnome-shell
> block -1 by 1042980
Bug #1043144 [release.debian.org] transition: mutter/gnome-shell 44
1043144 was not blocked by any bugs.
1043144 was not blocking any bugs.
Added blocking bug(s) of 1043144: 1042980

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

Bug#965479: marked as done (cvsutils: Removal of obsolete debhelper compat 5 and 6 in bookworm)

[Debian Bug Tracking System]

Your message dated Sun, 06 Aug 2023 17:19:41 +
with message-id 
and subject line Bug#965479: fixed in cvsutils 0.2.5-2
has caused the Debian Bug report #965479,
regarding cvsutils: Removal of obsolete debhelper compat 5 and 6 in bookworm
to be marked as done.

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

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


-- 
965479: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965479
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cvsutils
Version: 0.2.5-1
Severity: normal
Usertags: compat-5-6-removal

Hi,

The package cvsutils uses debhelper with a compat level of 5 or 6,
which is deprecated and scheduled for removal[1].

Please bump the debhelper compat at your earliest convenience
/outside the freeze/!

  * Compat 13 is recommended (supported in stable-backports)

  * Compat 7 is the bare minimum


PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads
with compat bumps during the freeze.

If there is any risk that the fix for this bug might not migrate to
testing before 2021-01-01[3] then please postpone the fix until after
the freeze.


At the time of filing this bug, compat 5 and 6 are expected to be
removed "some time during the development cycle of bookworm".


Thanks,
~Niels


[1] https://lists.debian.org/debian-devel/2020/07/msg00065.html

[2] https://release.debian.org/bullseye/FAQ.html

[3] The choice of 2021-01-01 as a "deadline" is set before the actual
freeze deadline to provide a safe cut off point for most people.

Mind you, it is still your responsibility to ensure that the upload
makes it into testing even if you upload before that date.
--- End Message ---
--- Begin Message ---
Source: cvsutils
Source-Version: 0.2.5-2
Done: Bastian Germann 

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

Debian distribution maintenance software
pp.
Bastian Germann  (supplier of updated cvsutils 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: Sun, 06 Aug 2023 18:36:16 +0200
Source: cvsutils
Architecture: source
Version: 0.2.5-2
Distribution: unstable
Urgency: medium
Maintainer: Uwe Hermann 
Changed-By: Bastian Germann 
Closes: 965479
Changes:
 cvsutils (0.2.5-2) unstable; urgency=medium
 .
   * QA upload.
   * Convert to source format 3.0.
   * Update debhelper to compat 10. (Closes: #965479)
   * d/copyright: Convert to machine-readable format.
Checksums-Sha1:
 638c9603ad700c4a0bf94a2b61a1e4180951d4de 1590 cvsutils_0.2.5-2.dsc
 a427ff80befdae4933f3f5dd1c5ab4a935c5afef 3244 cvsutils_0.2.5-2.debian.tar.xz
 e975b169b41ab6f3860c6188977aa4763ced009c 5952 cvsutils_0.2.5-2_source.buildinfo
Checksums-Sha256:
 4d80cc5b84e80b47df84b055aced05c8b5aa716e3911389a627e69214ed5c540 1590 
cvsutils_0.2.5-2.dsc
 8e239e954d52d1a1fc527d69e880f3ec10ca6b4bcd366a046023538f92d7268a 3244 
cvsutils_0.2.5-2.debian.tar.xz
 cda1fac79728931f5a80ae55a00b9fd7ded28951d97c7bd53dd7d5e084a9ef1d 5952 
cvsutils_0.2.5-2_source.buildinfo
Files:
 c0e3a49324b736fdfca8707e5b5ab3c9 1590 devel optional cvsutils_0.2.5-2.dsc
 61d714384c0abf634e2a66e7eaf4549f 3244 devel optional 
cvsutils_0.2.5-2.debian.tar.xz
 256484426098a0b5f19efe076bb8 5952 devel optional 
cvsutils_0.2.5-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmTP1DoQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFCGSC/9mE3snZmVznkwdrAjq/hNAfI/kM2MJF3JT
Ad2xVNfKz6u9UpPvPSGO9Dowp4Gq7oZuRd8cw8QUn2JmATQY6s6C90ejU63DmsTj
ODG8VVgqWWU4nbkSv+gJP6jYfpBcSwavAFqnwAuXPeGE+6bhUYgb5W8UvVtTZByS
ZzDmP7qYgupaPoxp+x6T2AotsF/wMMMBj7L04rnn145krw373Fne3eKZzkhYLBfU
Zn7wpGlexUoRypwCaFp8S4Z0Fs5xlC8TERUkmcMVaGJaUus0tywnEMRYdvgN5vNB
JO5YItQLFNQnEXNb5obEVFN6TVqN1Eba+Xjm35OJpTItX4v8iCbCOlc9JjE0UpS/
GkrPDJ4KZfrV2yJJfFtZ7XrP/HK1Lw8JM9YsJr1fv/nirjot1rks8GouVzqOAQ3Z
BbSKCu4lHEpjusGUyGH2qD/GUhuWNDkMX0tyjdWtow2p/psO4oam/IJHrefOYu84
GM7DgpnPZXWREwQbRcj0K/3nvTYgYjU=
=SPs/
-END PGP SIGNATURE End Message ---

Bug#1042810: [Debian-pan-maintainers] Bug#1042810: bornagain: FTBFS/BD-Uninstallable on !amd64

[Roland Mas]

Le 01/08/2023 à 10:14, Sebastian Ramacher a écrit :

Source: bornagain
Version: 20.2+ds3-1
Severity: serious
Tags: ftbfs sid trixie
Justification: fails to build from source (but built successfully in the past)


A partial patch fixing several testsuite failures has already been 
committed upstream and cherry-picked in the package, but other failures 
remain. Discussion is ongoing with upstream.


Roland.

Processed: severity of 1030290 is serious

[Debian Bug Tracking System]

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

> severity 1030290 serious
Bug #1030290 {Done: Scott Kitterman } [python3-gtts] 
python3-gtts: Outdated, no longer works
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#1001225: marked as done (tmate-ssh-server: CVE-2021-44512 CVE-2021-44513)

[Debian Bug Tracking System]

Your message dated Sun, 06 Aug 2023 15:36:11 +
with message-id 
and subject line Bug#1001225: fixed in tmate-ssh-server 2.3.0-68-gd7334ee4-1
has caused the Debian Bug report #1001225,
regarding tmate-ssh-server: CVE-2021-44512 CVE-2021-44513
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.)


-- 
1001225: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001225
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tmate-ssh-server
Version: 2.3.0-49-g97d20249-1
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerabilities were published for tmate-ssh-server.

CVE-2021-44512[0], CVE-2021-44513[1].

Note that there are as well other issues which do not have a CVE which
are mentioned in the oss-security[2] post.

If you fix the vulnerabilities please also make sure to include the
CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2021-44512
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44512
[1] https://security-tracker.debian.org/tracker/CVE-2021-44513
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44513
[2] https://www.openwall.com/lists/oss-security/2021/12/06/2

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: tmate-ssh-server
Source-Version: 2.3.0-68-gd7334ee4-1
Done: Christoph Berg 

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

Debian distribution maintenance software
pp.
Christoph Berg  (supplier of updated tmate-ssh-server 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: Sun, 06 Aug 2023 16:16:16 +0200
Source: tmate-ssh-server
Architecture: source
Version: 2.3.0-68-gd7334ee4-1
Distribution: unstable
Urgency: medium
Maintainer: Adrian Vondendriesch 
Changed-By: Christoph Berg 
Closes: 989176 1001225
Changes:
 tmate-ssh-server (2.3.0-68-gd7334ee4-1) unstable; urgency=medium
 .
   [ Debian Janitor ]
   * Use secure copyright file specification URI.
   * Bump debhelper from old 12 to 13.
   * Set upstream metadata fields: Bug-Database, Bug-Submit.
   * Update standards version to 4.5.1, no changes needed.
   * Avoid explicitly specifying -Wl,--as-needed linker flag.
 .
   [ Christoph Berg ]
   * New upstream version 2.3.0-68-gd7334ee4.
   * Stricter /tmp handling. (Closes: #1001225, CVE-2021-44512, CVE-2021-44513)
   * README.Debian: Use SHA256 in example. (Closes: #989176)
Checksums-Sha1:
 0f2e9d1b6abad2cada813000ccc674788a096df6 2174 
tmate-ssh-server_2.3.0-68-gd7334ee4-1.dsc
 f944630477df34ad73cb39c18297ce4c1a9dadfa 623391 
tmate-ssh-server_2.3.0-68-gd7334ee4.orig.tar.gz
 06fda43ae5b2660cd87b019a1cba7033fddd478d 5468 
tmate-ssh-server_2.3.0-68-gd7334ee4-1.debian.tar.xz
Checksums-Sha256:
 e46a3369467f0ec97643a5d32ea183c864bc29445a40c54b89cfeed0baa0bce5 2174 
tmate-ssh-server_2.3.0-68-gd7334ee4-1.dsc
 b21c1e1c4cd629d934a48c1e72215f5393a9f0b43308bf0a0a99812331c5f9ee 623391 
tmate-ssh-server_2.3.0-68-gd7334ee4.orig.tar.gz
 47e556f6797a52ca959dae67ac549132c6abc5b7c0ed049f3976aecb0797f9fd 5468 
tmate-ssh-server_2.3.0-68-gd7334ee4-1.debian.tar.xz
Files:
 d4178787ffd20c049d29416326f6356c 2174 admin optional 
tmate-ssh-server_2.3.0-68-gd7334ee4-1.dsc
 3b156656cc791d6c7078bcf7db143b1d 623391 admin optional 
tmate-ssh-server_2.3.0-68-gd7334ee4.orig.tar.gz
 4f258f6db37c9ca16e1af2e9f4db624a 5468 admin optional 
tmate-ssh-server_2.3.0-68-gd7334ee4-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEXEj+YVf0kXlZcIfGTFprqxLSp64FAmTPuZgACgkQTFprqxLS
p65v/g/+NOPsyH1kabtgL0suGn+ggTCZ5ngqlT2AHxTfO0g4uazNkhoQIN9G2/0b
oRLpH46nAikyQUM8k+86NVTXQflV245RgGIrFHwGr4VdSANZsW4AFrZCn+61X8YF
H7VFMYkTw9p1pMyqRCIIKpamp1l214qfKvMaLKvFmnXiOFAtsxGWH2TlzM3muI/w
g2BEjkwYPubNqi4QDS+sIxxH69+Du4zAnCEmWK5iY54BBljC7CgQYyGzGs/nZqix
skdvnVq58fzpTENkktusnJr7DitdJVn/wNkj4iXY/PTsyFPFC02O54fwFcHhWqEb
Pmrw/WSLuuz/Xe6Hkdau7zZRiSfuclfKM4yd1SM6pmT8YE1l3/aYA+Q3++Jl3wsp
ns5niJzaolskpFl/

Bug#1042907: marked as done (Breaks Emacs 29.1 upgrade: haskell.el:30:2: Error: Eager macro-expansion failure: (error "Misplaced t or ‘otherwise’ clause"))

[Debian Bug Tracking System]

Your message dated Sun, 06 Aug 2023 14:48:08 +
with message-id 
and subject line Bug#1042890: fixed in haskell-mode 17.4-1
has caused the Debian Bug report #1042890,
regarding Breaks Emacs 29.1 upgrade: haskell.el:30:2: Error: Eager 
macro-expansion failure: (error "Misplaced t or ‘otherwise’ clause")
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.)


-- 
1042890: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042890
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: elpa-haskell-mode
Version: 17.2-5
Severity: serious
X-Debbugs-Cc: a...@debian.org
Control: affects -1 emacs emacs-gtk emacs-lucid emacs-nox emacs-pgtk

After upgrading Emacs to 29.1, byte-(re-)compiling fails as follows:

[…]
Install elpa-haskell-mode for emacs
install/haskell-mode-17.2snapshot: Handling install of emacsen flavor emacs
install/haskell-mode-17.2snapshot: byte-compiling for emacs
../../elpa-src/haskell-mode-17.2snapshot/haskell-cabal.el: Warning: Case 
'before will match ‘quote’.  If that’s intended, write (before quote) instead.  
Otherwise, don’t quote ‘before’.
../../elpa-src/haskell-mode-17.2snapshot/haskell-cabal.el: Warning: Case 'after 
will match ‘quote’.  If that’s intended, write (after quote) instead.  
Otherwise, don’t quote ‘after’.
../../elpa-src/haskell-mode-17.2snapshot/haskell-cabal.el: Warning: Case 
'single will match ‘quote’.  If that’s intended, write (single quote) instead.  
Otherwise, don’t quote ‘single’.
../../elpa-src/haskell-mode-17.2snapshot/haskell-process.el: Warning: Case 
'ghci will match ‘quote’.  If that’s intended, write (ghci quote) instead.  
Otherwise, don’t quote ‘ghci’.
../../elpa-src/haskell-mode-17.2snapshot/haskell-process.el: Warning: Case 
'cabal-repl will match ‘quote’.  If that’s intended, write (cabal-repl quote) 
instead.  Otherwise, don’t quote ‘cabal-repl’.
../../elpa-src/haskell-mode-17.2snapshot/haskell-process.el: Warning: Case 
'stack-ghci will match ‘quote’.  If that’s intended, write (stack-ghci quote) 
instead.  Otherwise, don’t quote ‘stack-ghci’.
../../elpa-src/haskell-mode-17.2snapshot/haskell-commands.el: Warning: Case 
'unknown-command will match ‘quote’.  If that’s intended, write 
(unknown-command quote) instead.  Otherwise, don’t quote ‘unknown-command’.
../../elpa-src/haskell-mode-17.2snapshot/haskell-commands.el: Warning: Case 
'option-missing will match ‘quote’.  If that’s intended, write (option-missing 
quote) instead.  Otherwise, don’t quote ‘option-missing’.
../../elpa-src/haskell-mode-17.2snapshot/haskell-commands.el: Warning: Case 
'interactive-error will match ‘quote’.  If that’s intended, write 
(interactive-error quote) instead.  Otherwise, don’t quote ‘interactive-error’.

In toplevel form:
ghci-script-mode.el:20:2: Error: Eager macro-expansion failure: (error 
"Misplaced t or ‘otherwise’ clause")

In haskell-cabal-classify-line:
haskell-cabal.el:363:2: Warning: docstring wider than 80 characters
haskell-cabal.el:363:2: Warning: docstring has wrong usage of unescaped single 
quotes (use \= or different quoting)

In haskell-cabal-enum-targets:
haskell-cabal.el:496:2: Warning: docstring wider than 80 characters

In haskell-cabal-listify:
haskell-cabal.el:701:12: Warning: Case 'before will match ‘quote’.  If that’s 
intended, write (before quote) instead.  Otherwise, don’t quote ‘before’.
haskell-cabal.el:701:12: Warning: Case 'after will match ‘quote’.  If that’s 
intended, write (after quote) instead.  Otherwise, don’t quote ‘after’.
haskell-cabal.el:701:12: Warning: Case 'single will match ‘quote’.  If that’s 
intended, write (single quote) instead.  Otherwise, don’t quote ‘single’.

In haskell-cabal-line-filename:
haskell-cabal.el:926:2: Warning: docstring wider than 80 characters

In haskell-blank-line-p:
haskell-collapse.el:46:9: Warning: ‘point-at-eol’ is an obsolete function (as 
of 29.1); use ‘line-end-position’ or ‘pos-eol’ instead.

In haskell-hide-toggle-all:
haskell-collapse.el:95:19: Warning: ‘point-at-bol’ is an obsolete function (as 
of 29.1); use ‘line-beginning-position’ or ‘pos-bol’ instead.

In toplevel form:
haskell-commands.el:652:12: Error: Misplaced t or ‘otherwise’ clause

In toplevel form:
haskell-compile.el:42:2: Warning: custom-declare-variable 
`haskell-compile-cabal-build-command' docstring wider than 80 characters
haskell-compile.el:49:2: Warning: custom-declare-variable 
`haskell-compile-cabal-build-alt-command' docstring wider than 80 characters
haskell-compile.el:56:2: Warning: custom-declare-variable 
`haskell-compile-stack-build-command' docstring wider than 80 characters
haskell-compile.el

Bug#1042890: marked as done (haskell-mode: bytecompilation fails against Emacs 29.1)

[Debian Bug Tracking System]

Your message dated Sun, 06 Aug 2023 14:48:08 +
with message-id 
and subject line Bug#1042890: fixed in haskell-mode 17.4-1
has caused the Debian Bug report #1042890,
regarding haskell-mode: bytecompilation fails against Emacs 29.1
to be marked as done.

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

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


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

Dear maintainer,

haskell-mode fails to bytecompile against Emacs 29.1, which latter is
now in sid.

In toplevel form:
haskell.el:30:2: Error: Eager macro-expansion failure: (error "Misplaced t 
or ‘otherwise’ clause")

-- 
Sean Whitton


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: haskell-mode
Source-Version: 17.4-1
Done: Barak A. Pearlmutter 

We believe that the bug you reported is fixed in the latest version of
haskell-mode, 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.
Barak A. Pearlmutter  (supplier of updated haskell-mode 
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: Sun, 06 Aug 2023 15:07:58 +0100
Source: haskell-mode
Architecture: source
Version: 17.4-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Emacsen Team 
Changed-By: Barak A. Pearlmutter 
Closes: 1042890
Changes:
 haskell-mode (17.4-1) unstable; urgency=medium
 .
   * Track upstream, who is also working on the Emacs 29.1 test failure issue
   * Remove patches appropriately
   * Patch typo
   * New upstream release
   * Patch to remove bad redefinition of string-trim-left in test suite 
(closes: #1042890)
Checksums-Sha1:
 b72d56a607602dbc559b7eb72572c12c29fdd9b5 2085 haskell-mode_17.4-1.dsc
 e5f014227c39212a75caf2f29921bbf26c4491e9 1041024 haskell-mode_17.4.orig.tar.xz
 5c77d4436fbc6dd2cb7af56edde6d8c6f3a6 8136 haskell-mode_17.4-1.debian.tar.xz
 155ae5e68f5147a4e76d7797a6defb5f3c3e14a1 13428 
haskell-mode_17.4-1_source.buildinfo
Checksums-Sha256:
 9321bb8fee7a8db513254abc203e459caeab5d028c149f98838e40963fbdf200 2085 
haskell-mode_17.4-1.dsc
 db0042d66f2c6f4333126a4b11b7c0099ad5055bebdff37568fb0e35c7c9e85c 1041024 
haskell-mode_17.4.orig.tar.xz
 325300783c77e8f5255bdf12ba40de4d67d9e68be24b4e03b6977752efc99c67 8136 
haskell-mode_17.4-1.debian.tar.xz
 0cc869225a8acfffaf178109ef694c4ac0c73f7f3cf5bcc0882441d4a98c8d12 13428 
haskell-mode_17.4-1_source.buildinfo
Files:
 f6d3d896d9dee3f1d3d994d2d1097f79 2085 editors optional haskell-mode_17.4-1.dsc
 b81ea0fa44af549e18600b8e2609393e 1041024 editors optional 
haskell-mode_17.4.orig.tar.xz
 9b4e35e5e0b00f622afae604bd8f9155 8136 editors optional 
haskell-mode_17.4-1.debian.tar.xz
 d43d0efb607279e053fe93d0b46a28b4 13428 editors optional 
haskell-mode_17.4-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJDBAEBCgAtFiEE+nZaz+JE7Dn2AefCmesepNIze4gFAmTPqzYPHGJhcEBkZWJp
YW4ub3JnAAoJEJnrHqTSM3uIcgcQALFaH593ZA/dTJiyorU5utITLGMchGTPWrhW
50l7Fa29Xsq9/VNlo3k73JnqvWD07dPf+8oR8UgBIkoQBK/gxkc1g745D4V8pUjH
HFnL9LmAildgQ8P7+lWOKMUdHc84Y5yTJM/3ev7xCiRubMxfjOIU46Tiyi44pwsb
S2L1cGDRZVknceJe5Ewtbm5A5XD92tbYXLz8VlvUn6/DVyjUsdmLGsQ0Xab8tG+M
3xpXFCo0q6IB51kp3A6Bm/ZUGwkkD7553N2GNgZL9aNzrRMB5+23roVWNqOM3zB2
clhr+kFhEdrw7YRSvA55Q92jitaERx74hyzKsP9OAYHlrh9oHPY3xq/FpPvErNOc
nRtxoNKYB9heJnyKm1j5bPYbEM9+UfzIhvKOmw0njHowJkpjqukaTkPOZUK2YKLV
73HYfQYJKWINLJ4U6QdMdhobQYn9/Ad7rIfneD10A+xpSrwFqYx1K/YVSFVMSVvK
n2+16PxLdypPu0Naplwp8VwMZaS+fzGi/lsgDyzOkaFp0kAd1gYg7MJ/HUk+D6jW
m/bnNxPOA+qxcH/VT8lkSXWal0VKBMpjAwSxQNt6nWciFEXRzybIwpjZUGPhddFY
RrLGiusschD/xUk4Tezf905a55tAeRfbGvJmFXVc2TFLsgXWfO1A/Fs3KFvZww4m
PlHqSpeq
=C7YE
-END PGP SIGNATURE End Message ---

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

[Richard Lewis]

On Wed, 12 Jul 2023 at 12:20, Mathias Gibbens  wrote:
>
>   Andreas, thanks for the report, and Richard, thanks for your work as
> well. I think the changes look good, and if there's no other concerns
> I'll merge the salsa MR, and upload a new version to unstable. Once
> that's done, I'll also file a bug for uploading the updated version to
> stable-proposed-updates;

A gentle reminder on the last bit of this - getting it into bookworm
point release. (i think i read somewhere
 that 12.2 would be at the end of august)

 -- let me know if there's anything i can do to help with this (i
couldn't find anything listing what it involves!)

im about to set up a merge request to add a systemd timer, and have
some other changes in mind,
but think we should get this bit done first

Bug#1037736: [Pkg-sass-devel] Bug#1037736: Bug#1037736: libsass: ftbfs with GCC-13

[Jonas Smedegaard]

Quoting Jonas Smedegaard (2023-08-06 14:07:09)
> Quoting Bo YU (2023-08-06 13:48:43)
> > On Mon, Jul 31, 2023 at 1:09 AM Jonas Smedegaard  wrote:
> > > If you are generally interested in SASS tools and want to help maintain
> > > them in Debian, then you are very welcome to join the team (which is
> > > effectively only me at the moment).
> > Thanks for the invitation. I am happy to maintain SASS tools packages.
> 
> Great!  Please request membership of the salsa group at
> https://salsa.debian.org/groups/sass-team/-/group_members

Please also subscribe to our mailinglist - it is listed at our team page
at https://wiki.debian.org/Teams/Sass (which I created just now,
reminded by my earlier mention of lousy documentation).


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/
 * Sponsorship: https://ko-fi.com/drjones

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Bug#1041096: raspi-firmware: kernel removal can render raspi unbootable

[Daniel Moran]

Hi, it looks like this bug was introduced in the suggested patch for 
#1032186 [1].


I've attached a simple patch which rearranges the conditionals to make 
sure the variables containing the Kernel and Initrd names are populated 
even if the command is "remove".


Daniel

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

On Fri, 14 Jul 2023 15:52:24 -0500 Andreas Kloeckner  
wrote:

Package: raspi-firmware
Version: 1.20230405+ds-1
Severity: important

Dear Maintainer,

When removing a no-longer-in-use kernel recently, the raspi-firmware
postrm script, presumably the fact that this line [1] is not executed
on kernel removals, left me with a /boot/firmware/config.txt containing
the line

kernel=auto

which in turn left the Raspi (Model 4B in case it matters) firmware
very confused, and the machine unbootable.

Andreas

[1] 
https://salsa.debian.org/debian/raspi-firmware/-/blob/9cafcd85f8aed1ec0c0f609b98af591fae367ba2/debian/kernel/postinst.d/z50-raspi-firmware#L128


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

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

Versions of packages raspi-firmware depends on:
ii  dosfstools  4.2-1
ii  dpkg1.21.22

raspi-firmware recommends no packages.

Versions of packages raspi-firmware suggests:
pn  bluez-firmware 
pn  firmware-brcm80211 
ii  firmware-misc-nonfree  20230515-3

From bdf757722770155e9e885b2fff7f229100ca898c Mon Sep 17 00:00:00 2001
From: Daniel Moran 
Date: Sun, 6 Aug 2023 14:49:31 +0100
Subject: [PATCH 1/1] Ensure kernel and initrd names are set, even on remove

---
 debian/kernel/postinst.d/z50-raspi-firmware | 14 +++---
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/debian/kernel/postinst.d/z50-raspi-firmware b/debian/kernel/postinst.d/z50-raspi-firmware
index 9b3bfa502744..86d5d95fa683 100755
--- a/debian/kernel/postinst.d/z50-raspi-firmware
+++ b/debian/kernel/postinst.d/z50-raspi-firmware
@@ -115,18 +115,18 @@ else
   dtb_path="/usr/lib/linux-image-${latest_kernel#/boot/vmlinuz-}"
 fi
 
-# Do not copy DTBs or kernel/initramfs when removing packages (#1032186)
-if [ "$1" != "remove" ]; then
-  if [ "$KERNEL" = "auto" ] ; then
+if [ "$KERNEL" = "auto" ] ; then
+  latest_kernel_basename=$(basename "$latest_kernel")
+  latest_initrd_basename=$(basename "$latest_initrd")
+  KERNEL=${latest_kernel_basename}
+
+  # Do not copy DTBs or kernel/initramfs when removing packages (#1032186)
+  if [ "$1" != "remove" ]; then
 for dtb in "${dtb_path}"/bcm*.dtb; do
   [ -e "${dtb}" ] || continue
   cp "${dtb}" /boot/firmware/
 done
 
-latest_kernel_basename=$(basename "$latest_kernel")
-latest_initrd_basename=$(basename "$latest_initrd")
-KERNEL=${latest_kernel_basename}
-
 cp "$latest_kernel" /boot/firmware/
 cp "$latest_initrd" /boot/firmware/
   fi
-- 
2.40.1

Bug#1043128: marked as done (kodi: FTBFS on s390x)

[Debian Bug Tracking System]

Your message dated Sun, 06 Aug 2023 13:52:11 +
with message-id 
and subject line Bug#1043128: fixed in kodi 2:20.2+dfsg-4
has caused the Debian Bug report #1043128,
regarding kodi: FTBFS on s390x
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.)


-- 
1043128: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043128
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kodi
Version: 2:20.2+dfsg-3
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=kodi&arch=s390x&ver=2%3A20.2%2Bdfsg-3&stamp=1691212083&raw=0

make[3]: *** Waiting for unfinished jobs
[  7%] Building CXX object 
build/windowing/X11/CMakeFiles/windowing_X11.dir/WinSystemX11.cpp.o
cd /<>/obj-s390x-linux-gnu/build/windowing/X11 && /usr/bin/c++  
-I/<>/obj-s390x-linux-gnu -I/<> 
-I/<>/lib -I/<>/xbmc 
-I/<>/xbmc/platform/linux 
-I/<>/xbmc/cores/VideoPlayer 
-I/<>/obj-s390x-linux-gnu/build 
-I/<>/xbmc/platform/posix -isystem 
/<>/obj-s390x-linux-gnu/build/include -isystem 
/usr/include/dbus-1.0 -isystem /usr/lib/s390x-linux-gnu/dbus-1.0/include 
-isystem /usr/include/pipewire-0.3 -isystem /usr/include/spa-0.2 -isystem 
/usr/include/python3.11 -isystem /usr/include/samba-4.0 -isystem 
/usr/include/libxml2 -isystem 
/<>/obj-s390x-linux-gnu/build/cores/RetroPlayer/messages -isystem 
/usr/include/freetype2 -isystem /usr/include/fribidi -isystem /usr/include/lzo 
-isystem /usr/include/libdrm -g -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -O3 -Wdate-time 
-D_FORTIFY_SOURCE=2 -D_XBMC -DDEB_VERSION=\"2:20.2+dfsg-3\" -Wall 
-Wdouble-promotion -Wmissing-field-initializers -Wsign-compare -Wextra 
-Wno-unused-parameter -Wno-cast-function-type -Wnon-virtual-dtor -O2 -g 
-DNDEBUG -std=c++17 -DTARGET_POSIX -DTARGET_LINUX -D_GNU_SOURCE 
-DHAVE_LINUX_UDMABUF=1 -DHAVE_LINUX_DMA_HEAP=1 -DHAVE_LINUX_DMA_BUF=1 
-DHAVE_MKOSTEMP=1 -DHAVE_LINUX_MEMFD=1 -DWORDS_BIGENDIAN=1 -DHAVE_STATX=1 
-D__STDC_CONSTANT_MACROS -D_FILE_OFFSET_BITS=64 -DHAS_POSIX_NETWORK 
-DHAS_LINUX_NETWORK -DHAS_BUILTIN_SYNC_ADD_AND_FETCH=1 
-DHAS_BUILTIN_SYNC_SUB_AND_FETCH=1 -DHAS_BUILTIN_SYNC_VAL_COMPARE_AND_SWAP=1 
-DHAVE_INOTIFY=1 -DHAVE_POSIX_FADVISE=1 -DHAVE_LOCALTIME_R=1 -DHAVE_GMTIME_R=1 
-DHAVE_INTTYPES_H=1 -DHAS_ALSA=1 -DHAS_AVAHI=1 -DHAS_ZEROCONF=1 
-DHAVE_LIBBLURAY=1 -DHAVE_LIBBLURAY_BDJ=1 -DHAVE_LIBCEC=1 -DHAS_DBUS=1 
-DHAS_ISO9660PP=1 -DHAVE_LCMS2=1 -DCMS_NO_REGISTER_KEYWORD=1 -DHAS_LIRC=1 
-DHAS_WEB_SERVER=1 -DHAS_WEB_INTERFACE=1 -DHAS_FILESYSTEM_NFS=1 
-DHAS_NFS_SET_TIMEOUT -DHAS_PIPEWIRE=1 -DHAS_AIRPLAY=1 -DHAS_PULSEAUDIO=1 
-DHAS_PYTHON=1 -DHAS_FILESYSTEM_SMB=1 -DHAS_SNDIO=1 -DHAVE_LIBUDEV=1 
-DHAS_UDFREAD=1 -DHAVE_LIBXSLT=1 -DHAVE_LIBVA=1 -DHAS_GLX=1 -DHAVE_LIBVDPAU=1 
-DDATE_HAS_STRINGVIEW -DFFMPEG_VER_SHA=\"4.4.1\" -DHAVE_GCRYPT=1 
-DSPDLOG_FMT_EXTERNAL -DSPDLOG_DEBUG_ON -DSPDLOG_NO_ATOMIC_LEVELS 
-DSPDLOG_ENABLE_PATTERN_PADDING -DSPDLOG_COMPILED_LIB -DSPDLOG_SHARED_LIB 
-DHAS_EGL=1 -DHAVE_EGLEXTANGLE=1 -DHAVE_X11=1 -DHAVE_LIBXRANDR=1 
-DHAVE_HDR_OUTPUT_METADATA=1 -DHAVE_DRM_MODIFIER_NAME=1 -DHAS_GL=1 
-DHAVE_WAYLAND=1 -DHAVE_GBM=1 -DHAS_GBM_BO_MAP=1 -DHAS_GBM_MODIFIERS=1 
-DHAS_MYSQL=1 -DHAS_UPNP=1 -DHAS_DVD_DRIVE -DHAS_CDDA_RIPPER -DHAS_AIRTUNES=1 
-DBIN_INSTALL_PATH=\"/usr/lib/s390x-linux-gnu/kodi\" 
-DINSTALL_PATH=\"/usr/share/kodi\" -Werror=double-promotion 
-Werror=missing-field-initializers -Werror=sign-compare -MD -MT 
build/windowing/X11/CMakeFiles/windowing_X11.dir/WinSystemX11.cpp.o -MF 
CMakeFiles/windowing_X11.dir/WinSystemX11.cpp.o.d -o 
CMakeFiles/windowing_X11.dir/WinSystemX11.cpp.o -c 
/<>/xbmc/windowing/X11/WinSystemX11.cpp
In file included from /<>/xbmc/guilib/VisibleEffect.h:23,
 from /<>/xbmc/guilib/GUIControl.h:17,
 from /<>/xbmc/guilib/GUIControlLookup.h:11,
 from /<>/xbmc/guilib/GUIControlGroup.h:16,
 from /<>/xbmc/guilib/GUIWindow.h:17,
 from /<>/xbmc/guilib/GUIWindowManager.h:12,
 from /<>/xbmc/windowing/X11/WinEventsX11.cpp:16:
/<>/xbmc/utils/TransformMatrix.h: In member function ‘void 
TransformMatrix::SetFader(float)’:
/<>/xbmc/utils/TransformMatrix.h:129:19: error: implicit 
conversion from ‘float’ to ‘double’ to match other operand of binary expression 
[-Werror=double-promotion]
  129 | identity = (a == 1.0f);
  | ~~^~~
/<>/xbmc/utils/TransformMatrix.h: In member function ‘void 
TransformMatrix::SetFader(float, float, f

Bug#1041401: marked as done (kodi-inputstream-ffmpegdirect: FTBFS with ffmpeg 6.0)

[Debian Bug Tracking System]

Your message dated Sun, 06 Aug 2023 13:52:45 +
with message-id 
and subject line Bug#1041401: fixed in kodi-inputstream-ffmpegdirect 
20.5.0+ds1-2
has caused the Debian Bug report #1041401,
regarding kodi-inputstream-ffmpegdirect: FTBFS with ffmpeg 6.0
to be marked as done.

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

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


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

kodi-inputstream-ffmpegdirect FTBFS with ffmpeg 6.0 (available in
experimental):

/<>/src/stream/FFmpegStream.cpp: In member function ‘bool 
ffmpegdirect::FFmpegStream::OpenWithFFmpeg(const AVInputFormat*, const 
AVIOInterruptCB&)’:
/<>/src/stream/FFmpegStream.cpp:954:34: error: 
‘AVFMT_FLAG_PRIV_OPT’ was not declared in this scope; did you mean 
‘AVFMT_FLAG_IGNIDX’?
  954 |   m_pFormatContext->flags |= AVFMT_FLAG_PRIV_OPT;
  |  ^~~
  |  AVFMT_FLAG_IGNIDX
/<>/src/stream/FFmpegStream.cpp:969:33: error: 
‘AVFMT_FLAG_PRIV_OPT’ was not declared in this scope; did you mean 
‘AVFMT_FLAG_IGNIDX’?
  969 | m_pFormatContext->flags &= ~AVFMT_FLAG_PRIV_OPT;
  | ^~~
  | AVFMT_FLAG_IGNIDX
make[3]: *** [CMakeFiles/inputstream.ffmpegdirect.dir/build.make:135: 
CMakeFiles/inputstream.ffmpegdirect.dir/src/stream/FFmpegStream.cpp.o] Error 1

The full build log is attached.

Cheers
-- 
Sebastian Ramacher
sbuild (Debian sbuild) 0.85.2 (11 March 2023) on jupiter.ramacher.at

+==+
| kodi-inputstream-ffmpegdirect (amd64)Tue, 18 Jul 2023 08:58:06 + |
+==+

Package: kodi-inputstream-ffmpegdirect
Distribution: experimental
Machine Architecture: amd64
Host Architecture: amd64
Build Architecture: amd64
Build Type: full

I: NOTICE: Log filtering will replace 
'var/run/schroot/mount/experimental-amd64-sbuild-02c302c6-c64c-40d1-b868-486adc1511c1'
 with '<>'
Copying 
/home/sebastian/Debian/multimedia-team/libswscale7-dbgsym_6.0-3_amd64.deb to 
Sbuild::ChrootSchroot=HASH(0x55f7f22fcca0)->get('Location')...
Copying 
/home/sebastian/Debian/multimedia-team/libavfilter-extra_6.0-3_amd64.deb to 
Sbuild::ChrootSchroot=HASH(0x55f7f22fcca0)->get('Location')...
Copying /home/sebastian/Debian/multimedia-team/libpostproc-dev_6.0-3_amd64.deb 
to Sbuild::ChrootSchroot=HASH(0x55f7f22fcca0)->get('Location')...
Copying /home/sebastian/Debian/multimedia-team/libavformat-dev_6.0-3_amd64.deb 
to Sbuild::ChrootSchroot=HASH(0x55f7f22fcca0)->get('Location')...
Copying 
/home/sebastian/Debian/multimedia-team/libswresample-dev_6.0-3_amd64.deb to 
Sbuild::ChrootSchroot=HASH(0x55f7f22fcca0)->get('Location')...
Copying 
/home/sebastian/Debian/multimedia-team/libavfilter-extra9-dbgsym_6.0-3_amd64.deb
 to Sbuild::ChrootSchroot=HASH(0x55f7f22fcca0)->get('Location')...
Copying 
/home/sebastian/Debian/multimedia-team/libavformat60-dbgsym_6.0-3_amd64.deb to 
Sbuild::ChrootSchroot=HASH(0x55f7f22fcca0)->get('Location')...
Copying /home/sebastian/Debian/multimedia-team/libswresample4_6.0-3_amd64.deb 
to Sbuild::ChrootSchroot=HASH(0x55f7f22fcca0)->get('Location')...
Copying 
/home/sebastian/Debian/multimedia-team/libavcodec-extra60-dbgsym_6.0-3_amd64.deb
 to Sbuild::ChrootSchroot=HASH(0x55f7f22fcca0)->get('Location')...
Copying /home/sebastian/Debian/multimedia-team/libavcodec-extra_6.0-3_amd64.deb 
to Sbuild::ChrootSchroot=HASH(0x55f7f22fcca0)->get('Location')...
Copying /home/sebastian/Debian/multimedia-team/libavdevice-dev_6.0-3_amd64.deb 
to Sbuild::ChrootSchroot=HASH(0x55f7f22fcca0)->get('Location')...
Copying /home/sebastian/Debian/multimedia-team/libavfilter-dev_6.0-3_amd64.deb 
to Sbuild::ChrootSchroot=HASH(0x55f7f22fcca0)->get('Location')...
Copying 
/home/sebastian/Debian/multimedia-team/libavfilter9-dbgsym_6.0-3_amd64.deb to 
Sbuild::ChrootSchroot=HASH(0x55f7f22fcca0)->get('Location')...
Copying 
/home/sebastian/Debian/multimedia-team/libpostproc57-dbgsym_6.0-3_amd64.deb to 
Sbuild::ChrootSchroot=HASH(0x55f7f22fcca0)->get('Location')...
Copying 
/home/sebastian/Debian/multimedia-team/libavformat-extra60-dbgsym_6.0-3_amd64.deb
 to Sbuild::ChrootSchroot=HASH(0x55f7f22fcca0)->get('Location')...
Copying /home/sebastian/Debian/multimedia-team/libswscale-dev_6.

Bug#1037714: marked as done (kodi-inputstream-ffmpegdirect: ftbfs with GCC-13)

[Debian Bug Tracking System]

Your message dated Sun, 06 Aug 2023 13:52:45 +
with message-id 
and subject line Bug#1037714: fixed in kodi-inputstream-ffmpegdirect 
20.5.0+ds1-2
has caused the Debian Bug report #1037714,
regarding kodi-inputstream-ffmpegdirect: 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.)


-- 
1037714: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037714
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:kodi-inputstream-ffmpegdirect
Version: 20.5.0+ds1-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/kodi-inputstream-ffmpegdirect_20.5.0+ds1-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

[...]
[ 56%] Building CXX object 
CMakeFiles/inputstream.ffmpegdirect.dir/src/stream/TimeshiftSegment.cpp.o
/usr/bin/c++ -DADDON_GLOBAL_VERSION_FILESYSTEM_USED 
-DADDON_GLOBAL_VERSION_GENERAL_USED -DADDON_GLOBAL_VERSION_MAIN_USED 
-DADDON_GLOBAL_VERSION_NETWORK_USED -DADDON_GLOBAL_VERSION_TOOLS_USED 
-DADDON_INSTANCE_VERSION_INPUTSTREAM_USED -DBUILD_KODI_ADDON 
-DFFMPEGDIRECT_VERSION=20.5.0 -Dinputstream_ffmpegdirect_EXPORTS  -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC   -DTARGET_POSIX 
-DTARGET_LINUX -D_GNU_SOURCE -DHAVE_LINUX_UDMABUF=1 -DHAVE_LINUX_DMA_HEAP=1 
-DHAVE_LINUX_DMA_BUF=1 -DHAVE_MKOSTEMP=1 -DHAVE_LINUX_MEMFD=1 -DHAVE_STATX=1 
-DHAVE_SSE=1 -DHAVE_SSE2=1 -DHAVE_SSE3=1 -DHAVE_SSSE3=1 -DHAVE_SSE4_1=1 
-std=c++17 -MD -MT 
CMakeFiles/inputstream.ffmpegdirect.dir/src/stream/TimeshiftSegment.cpp.o -MF 
CMakeFiles/inputstream.ffmpegdirect.dir/src/stream/TimeshiftSegment.cpp.o.d -o 
CMakeFiles/inputstream.ffmpegdirect.dir/src/stream/TimeshiftSegment.cpp.o -c 
/<>/src/stream/TimeshiftSegment.
 cpp
[ 62%] Building CXX object 
CMakeFiles/inputstream.ffmpegdirect.dir/src/stream/TimeshiftStream.cpp.o
/usr/bin/c++ -DADDON_GLOBAL_VERSION_FILESYSTEM_USED 
-DADDON_GLOBAL_VERSION_GENERAL_USED -DADDON_GLOBAL_VERSION_MAIN_USED 
-DADDON_GLOBAL_VERSION_NETWORK_USED -DADDON_GLOBAL_VERSION_TOOLS_USED 
-DADDON_INSTANCE_VERSION_INPUTSTREAM_USED -DBUILD_KODI_ADDON 
-DFFMPEGDIRECT_VERSION=20.5.0 -Dinputstream_ffmpegdirect_EXPORTS  -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC   -DTARGET_POSIX 
-DTARGET_LINUX -D_GNU_SOURCE -DHAVE_LINUX_UDMABUF=1 -DHAVE_LINUX_DMA_HEAP=1 
-DHAVE_LINUX_DMA_BUF=1 -DHAVE_MKOSTEMP=1 -DHAVE_LINUX_MEMFD=1 -DHAVE_STATX=1 
-DHAVE_SSE=1 -DHAVE_SSE2=1 -DHAVE_SSE3=1 -DHAVE_SSSE3=1 -DHAVE_SSE4_1=1 
-std=c++17 -MD -MT 
CMakeFiles/inputstream.ffmpegdirect.dir/src/stream/TimeshiftStream.cpp.o -MF 
CMakeFiles/inputstream.ffmpegdirect.dir/src/stream/TimeshiftStream.cpp.o.d -o 
CMakeFiles/inputstream.ffmpegdirect.dir/src/stream/TimeshiftStream.cpp.o -c 
/<>/src/stream/TimeshiftStream.cpp
[ 68%] Building CXX object 
CMakeFiles/inputstream.ffmpegdirect.dir/src/stream/url/URL.cpp.o
/usr/bin/c++ -DADDON_GLOBAL_VERSION_FILESYSTEM_USED 
-DADDON_GLOBAL_VERSION_GENERAL_USED -DADDON_GLOBAL_VERSION_MAIN_USED 
-DADDON_GLOBAL_VERSION_NETWORK_USED -DADDON_GLOBAL_VERSION_TOOLS_USED 
-DADDON_INSTANCE_VERSION_INPUTSTREAM_USED -DBUILD_KODI_ADDON 
-DFFMPEGDIRECT_VERSION=20.5.0 -Dinputstream_ffmpegdirect_EXPORTS  -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC   -DTARGET_POSIX 
-DTARGET_LINUX -D_GNU_SOURCE -DHAVE_LINUX_UDMABUF=1 -DHAVE_LINUX_DMA_HEAP=1 

Bug#1037712: marked as done (kodi-inputstream-adaptive: ftbfs with GCC-13)

[Debian Bug Tracking System]

Your message dated Sun, 06 Aug 2023 13:52:35 +
with message-id 
and subject line Bug#1037712: fixed in kodi-inputstream-adaptive 20.3.11+ds-1
has caused the Debian Bug report #1037712,
regarding kodi-inputstream-adaptive: 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.)


-- 
1037712: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037712
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:kodi-inputstream-adaptive
Version: 20.3.2+ds-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/kodi-inputstream-adaptive_20.3.2+ds-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

[...]
cd /<>/obj-x86_64-linux-gnu/lib/mpegts && /usr/bin/c++ 
-DBUILD_KODI_ADDON -DUNICODE -D_UNICODE -D__STDC_FORMAT_MACROS 
-I/<>/lib/mpegts/. -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -fPIC   -DTARGET_POSIX -DTARGET_LINUX -D_GNU_SOURCE 
-DHAVE_LINUX_UDMABUF=1 -DHAVE_LINUX_DMA_HEAP=1 -DHAVE_LINUX_DMA_BUF=1 
-DHAVE_MKOSTEMP=1 -DHAVE_LINUX_MEMFD=1 -DHAVE_STATX=1 -DHAVE_SSE=1 
-DHAVE_SSE2=1 -DHAVE_SSE3=1 -DHAVE_SSSE3=1 -DHAVE_SSE4_1=1 -std=c++17 -MD -MT 
lib/mpegts/CMakeFiles/mpegts.dir/ES_MPEGAudio.cpp.o -MF 
CMakeFiles/mpegts.dir/ES_MPEGAudio.cpp.o.d -o 
CMakeFiles/mpegts.dir/ES_MPEGAudio.cpp.o -c 
/<>/lib/mpegts/ES_MPEGAudio.cpp
[ 19%] Building CXX object lib/mpegts/CMakeFiles/mpegts.dir/ES_Subtitle.cpp.o
cd /<>/obj-x86_64-linux-gnu/lib/mpegts && /usr/bin/c++ 
-DBUILD_KODI_ADDON -DUNICODE -D_UNICODE -D__STDC_FORMAT_MACROS 
-I/<>/lib/mpegts/. -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -fPIC   -DTARGET_POSIX -DTARGET_LINUX -D_GNU_SOURCE 
-DHAVE_LINUX_UDMABUF=1 -DHAVE_LINUX_DMA_HEAP=1 -DHAVE_LINUX_DMA_BUF=1 
-DHAVE_MKOSTEMP=1 -DHAVE_LINUX_MEMFD=1 -DHAVE_STATX=1 -DHAVE_SSE=1 
-DHAVE_SSE2=1 -DHAVE_SSE3=1 -DHAVE_SSSE3=1 -DHAVE_SSE4_1=1 -std=c++17 -MD -MT 
lib/mpegts/CMakeFiles/mpegts.dir/ES_Subtitle.cpp.o -MF 
CMakeFiles/mpegts.dir/ES_Subtitle.cpp.o.d -o 
CMakeFiles/mpegts.dir/ES_Subtitle.cpp.o -c 
/<>/lib/mpegts/ES_Subtitle.cpp
[ 20%] Building CXX object lib/mpegts/CMakeFiles/mpegts.dir/ES_AAC.cpp.o
cd /<>/obj-x86_64-linux-gnu/lib/mpegts && /usr/bin/c++ 
-DBUILD_KODI_ADDON -DUNICODE -D_UNICODE -D__STDC_FORMAT_MACROS 
-I/<>/lib/mpegts/. -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -fPIC   -DTARGET_POSIX -DTARGET_LINUX -D_GNU_SOURCE 
-DHAVE_LINUX_UDMABUF=1 -DHAVE_LINUX_DMA_HEAP=1 -DHAVE_LINUX_DMA_BUF=1 
-DHAVE_MKOSTEMP=1 -DHAVE_LINUX_MEMFD=1 -DHAVE_STATX=1 -DHAVE_SSE=1 
-DHAVE_SSE2=1 -DHAVE_SSE3=1 -DHAVE_SSSE3=1 -DHAVE_SSE4_1=1 -std=c++17 -MD -MT 
lib/mpegts/CMakeFiles/mpegts.dir/ES_AAC.cpp.o -MF 
CMakeFiles/mpegts.dir/ES_AAC.cpp.o.d -o CMakeFiles/mpegts.dir/ES_AAC.cpp.o -c 
/<>/lib/mpegts/ES_AAC.cpp
/<>/src/test/TestHelper.cpp: In constructor 
‘HLSTestTree::HLSTestTree(UTILS::PROPERTIES::KodiProperties, 
CHOOSER::IRepresentationChooser*)’:
/<>/src/test/TestHelper.cpp:142:74: error: invalid cast to 
abstract class type ‘AESDecrypter’
  142 |   m_decrypter = 
std::make_unique(AESDecrypter(std::string()));
  | 
 ^
/<>/src/test/TestHelper.h:69:7: note:   because the following 
virtual functions are pure within ‘AESDecrypter’:
   69 | class AESDecrypter : public IAESDecrypter

Bug#1037711: marked as done (kodi-imagedecoder-heif: ftbfs with GCC-13)

[Debian Bug Tracking System]

Your message dated Sun, 06 Aug 2023 13:52:21 +
with message-id 
and subject line Bug#1037711: fixed in kodi-imagedecoder-heif 20.1.0+ds1-3
has caused the Debian Bug report #1037711,
regarding kodi-imagedecoder-heif: 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.)


-- 
1037711: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037711
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:kodi-imagedecoder-heif
Version: 20.1.0+ds1-2
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/kodi-imagedecoder-heif_20.1.0+ds1-2_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

[...]
/<>/lib/TinyEXIF/TinyEXIF.cpp:1238:9: error: ‘RelatedImageWidth’ 
was not declared in this scope
 1238 | RelatedImageWidth = 0;
  | ^
/<>/lib/TinyEXIF/TinyEXIF.cpp:1239:9: error: ‘RelatedImageHeight’ 
was not declared in this scope
 1239 | RelatedImageHeight= 0;
  | ^~
/<>/lib/TinyEXIF/TinyEXIF.cpp:1240:9: error: ‘Orientation’ was not 
declared in this scope
 1240 | Orientation   = 0;
  | ^~~
/<>/lib/TinyEXIF/TinyEXIF.cpp:1243:9: error: ‘ResolutionUnit’ was 
not declared in this scope; did you mean ‘XResolution’?
 1243 | ResolutionUnit= 0;
  | ^~
  | XResolution
/<>/lib/TinyEXIF/TinyEXIF.cpp:1244:9: error: ‘BitsPerSample’ was 
not declared in this scope
 1244 | BitsPerSample = 0;
  | ^
/<>/lib/TinyEXIF/TinyEXIF.cpp:1247:9: error: ‘ExposureProgram’ was 
not declared in this scope
 1247 | ExposureProgram   = 0;
  | ^~~
/<>/lib/TinyEXIF/TinyEXIF.cpp:1248:9: error: ‘ISOSpeedRatings’ was 
not declared in this scope
 1248 | ISOSpeedRatings   = 0;
  | ^~~
/<>/lib/TinyEXIF/TinyEXIF.cpp:1255:9: error: ‘Flash’ was not 
declared in this scope
 1255 | Flash = 0;
  | ^
/<>/lib/TinyEXIF/TinyEXIF.cpp:1256:9: error: ‘MeteringMode’ was 
not declared in this scope
 1256 | MeteringMode  = 0;
  | ^~~~
/<>/lib/TinyEXIF/TinyEXIF.cpp:1257:9: error: ‘LightSource’ was not 
declared in this scope
 1257 | LightSource   = 0;
  | ^~~
/<>/lib/TinyEXIF/TinyEXIF.cpp:1258:9: error: ‘ProjectionType’ was 
not declared in this scope
 1258 | ProjectionType= 0;
  | ^~
/<>/lib/TinyEXIF/TinyEXIF.cpp:1259:21: error: request for member 
‘clear’ in ‘((TinyEXIF::EXIFInfo*)this)->TinyEXIF::EXIFInfo::SubjectArea’, 
which is of non-class type ‘int’
 1259 | SubjectArea.clear();
  | ^
/<>/lib/TinyEXIF/TinyEXIF.cpp:1275:18: error: ‘struct 
TinyEXIF::EXIFInfo::LensInfo_t’ has no member named ‘FocalPlaneResolutionUnit’; 
did you mean ‘FocalPlaneXResolution’?
 1275 | LensInfo.FocalPlaneResolutionUnit = 0;
  |  ^~~~
  |  FocalPlaneXResolution
/<>/lib/TinyEXIF/TinyEXIF.cpp:1294:21: error: ‘struct 
TinyEXIF::EXIFInfo::Geolocation_t’ has no member named ‘GPSDifferential’
 1294 | GeoLocation.GPSDifferential = 0;
  | ^~~
/<>/lib/TinyEXIF/TinyEXIF.cpp:1301:35: error: ‘struct 
TinyEXIF::EXIFInfo::Geolocation_t::Coord_t’ has no member named ‘direction’
 1301 | GeoLocation.LatComponents.direction = 0;
  | 

Bug#1043102: marked as done (libflatbuffers-dev: Try to overwrite flatbuffers.pc already in package libflatbuffers2)

[Debian Bug Tracking System]

Your message dated Sun, 06 Aug 2023 13:19:32 +
with message-id 
and subject line Bug#1043102: fixed in flatbuffers 2.0.8+dfsg1-6
has caused the Debian Bug report #1043102,
regarding libflatbuffers-dev: Try to overwrite flatbuffers.pc already in 
package libflatbuffers2
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.)


-- 
1043102: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043102
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libflatbuffers-dev
Version: 2.0.8+dfsg1-5
Severity: serious

Dear Maintainer,

Error message in French.

,
| Dépaquetage de libflatbuffers-dev:amd64 (2.0.8+dfsg1-5) sur (2.0.8+dfsg1-4) 
...
| dpkg: erreur de traitement de l'archive 
/tmp/apt-dpkg-install-Qf2whY/01-libflatbuffers-dev_2.0.8+dfsg1-5_amd64.deb 
(--unpack) :
|  tentative de remplacement de « 
/usr/lib/x86_64-linux-gnu/pkgconfig/flatbuffers.pc », qui appartient aussi au 
paquet libflatbuffers2:amd64 2.0.8+dfsg1-4
`

Christian

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

Kernel: Linux 6.4.8-1-custom (SMP w/24 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libflatbuffers-dev depends on:
ii  flatbuffers-compiler-dev  2.0.8+dfsg1-5
ii  libflatbuffers2   2.0.8+dfsg1-5

libflatbuffers-dev recommends no packages.

libflatbuffers-dev suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: flatbuffers
Source-Version: 2.0.8+dfsg1-6
Done: Nobuhiro Iwamatsu 

We believe that the bug you reported is fixed in the latest version of
flatbuffers, 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.
Nobuhiro Iwamatsu  (supplier of updated flatbuffers 
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: Sun, 06 Aug 2023 17:28:38 +0900
Source: flatbuffers
Architecture: source
Version: 2.0.8+dfsg1-6
Distribution: unstable
Urgency: medium
Maintainer: Maximiliano Curia 
Changed-By: Nobuhiro Iwamatsu 
Closes: 1043102
Changes:
 flatbuffers (2.0.8+dfsg1-6) unstable; urgency=medium
 .
   * d/control: Fix Breaks and Replaces. (Closes: #1043102)
Checksums-Sha1:
 6eeec392620df25da421381778fc18da75539f5d 2343 flatbuffers_2.0.8+dfsg1-6.dsc
 84aa7b46e9cbbb7dea4d343502f6fe195c7a9402 10188 
flatbuffers_2.0.8+dfsg1-6.debian.tar.xz
 8a8def39b5fad4521335d85567bd844682325650 9042 
flatbuffers_2.0.8+dfsg1-6_amd64.buildinfo
Checksums-Sha256:
 cdcaca67b7dbcb3745ad12acf9ce2e51fb47c3b986e478067d8cb848299e2967 2343 
flatbuffers_2.0.8+dfsg1-6.dsc
 8fa977699bf86861359c5a80d2b49aebb2f9f29efefeb7410b805fff5aa7b371 10188 
flatbuffers_2.0.8+dfsg1-6.debian.tar.xz
 f1f512fcff4a465b59490fde95102d54bbc1126c1373ce6ea294dbfc3da90182 9042 
flatbuffers_2.0.8+dfsg1-6_amd64.buildinfo
Files:
 af732c6ef0426f9cba93313edb9d698d 2343 devel optional 
flatbuffers_2.0.8+dfsg1-6.dsc
 8e4d274591bda9d25b7b046e47c8aa0a 10188 devel optional 
flatbuffers_2.0.8+dfsg1-6.debian.tar.xz
 cbe9b6155c991207571d57bd152da374 9042 devel optional 
flatbuffers_2.0.8+dfsg1-6_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEXmKe5SMhlzV7hM9DMiR/u0CtH6YFAmTPmiAACgkQMiR/u0Ct
H6bhmw/9HiGf5rE2a8YN7qm5LEagTpiauDNNLm6Mtba/Co5sV7pMOcgra/cceJ/g
ZObAc4aRKacg56jwiHiQ/S7hqfSyo+35xmbXHJ1h/6lV9tkf1o888Z4kdVaUAP4x
kqze4Hp2eLanoMjppjyrYdM+SlRPpKDHPUl3xTdE5k/U5uNc3PpziU7jhmjgQ6tV
ZQ9DCsMy3lkRkkjSXnH9ebS95nxBNAYdgYUSkAbPb8nq7W9V+mtzxCc7BV75zQar
Gro1WzbNd7FmXkmwGISCCWA4PRyv7JuB/qs0MuQX2juHnrxPEgyyHCBjJNBbi1SN
JCVfOnZRw6160GsFPKEm4GI+67HqflaKB25aabpGSESmMaIB2dsWBim/kEyPjaFj
HW3RwWviT3Gb3oI8Nrh31GJD3Z7inlPFf2aG4/OnzmlpA5Q7DY32R/E64w6gfRKi
ihYneIhsGlnKHTS3OyKJM9LGPq0JMxWQ5Nc3qrZLnZgsSROrlpKKqcTayqQTQTeC
KrLhZjlNqz+fQ1drBBVenYHSdWVpvfYVc+aaqrNbo1uUM3IHw0LPBQu0BQPd/69b
CO3K5gfk0DnwILtGkA0WMznTnIH8OD0QMpebGIDDfECY3gB50e7sy4

Bug#1042301: marked as done (pycairo: FTBFS: dh_missing: error: missing files, aborting)

[Debian Bug Tracking System]

Your message dated Sun, 06 Aug 2023 13:05:05 +
with message-id 
and subject line Bug#1040748: fixed in pycairo 1.24.0-1.1
has caused the Debian Bug report #1040748,
regarding pycairo: FTBFS: dh_missing: error: missing files, aborting
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.)


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

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_installchangelogs -Xchangelog
> make[1]: Leaving directory '/<>'
>dh_installexamples -O--buildsystem=meson
>dh_python3 -O--buildsystem=meson
>dh_installsystemduser -O--buildsystem=meson
>dh_lintian -O--buildsystem=meson
>dh_perl -O--buildsystem=meson
>dh_link -O--buildsystem=meson
>dh_strip_nondeterminism -O--buildsystem=meson
>dh_compress -O--buildsystem=meson
>dh_fixperms -O--buildsystem=meson
>dh_missing -O--buildsystem=meson
> dh_missing: warning: 
> usr/lib/python3/dist-packages/cairo/__pycache__/__init__.cpython-311.pyc 
> exists in debian/tmp but is not installed to anywhere 
> dh_missing: error: missing files, aborting
>   The following debhelper tools have reported what they installed (with 
> files per package)
>* dh_install: python3-cairo (5), python3-cairo-dev (3), 
> python3-cairo-doc (0)
>* dh_installdocs: python3-cairo (1), python3-cairo-dev (0), 
> python3-cairo-doc (1)
>* dh_installexamples: python3-cairo (0), python3-cairo-dev (0), 
> python3-cairo-doc (4)
>   If the missing files are installed by another tool, please file a bug 
> against it.
>   When filing the report, if the tool is not part of debhelper itself, 
> please reference the
>   "Logging helpers and dh_missing" section from the "PROGRAMMING" guide 
> for debhelper (10.6.3+).
> (in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.gz)
>   Be sure to test with dpkg-buildpackage -A/-B as the results may vary 
> when only a subset is built
>   If the omission is intentional or no other helper can take care of this 
> consider adding the
>   paths to debian/not-installed.
> make: *** [debian/rules:6: binary] Error 25


The full build log is available from:
http://qa-logs.debian.net/2023/07/26/pycairo_1.24.0-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/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: pycairo
Source-Version: 1.24.0-1.1
Done: Chris Hofstaedtler 

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

Debian distribution maintenance software
pp.
Chris Hofstaedtler  (supplier of updated pycairo 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: Sun, 06 Aug 2023 14:42:07 +0200
Source: pycairo
Architecture: source
Version: 1.24.0-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Chris Hofstaedtler 
Closes: 1040748
Changes:
 pycairo (1.24.0-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Workaround automatic Pyth

Bug#1040748: marked as done (ftbfs in pycairo with meson 1.2.0 rc2)

[Debian Bug Tracking System]

Your message dated Sun, 06 Aug 2023 13:05:05 +
with message-id 
and subject line Bug#1040748: fixed in pycairo 1.24.0-1.1
has caused the Debian Bug report #1040748,
regarding ftbfs in pycairo with meson 1.2.0 rc2
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.)


-- 
1040748: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040748
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pycairo
Version: 1.24.0-1
Severity: important
Tags: ftbfs
X-Debbugs-CC: hel...@subdivi.de


During an archive rebuild against the release candidate for meson in
experimental, pycairo failed to build from source with the following log
excerpt:


```
   dh_auto_install -O--buildsystem=meson
cd obj-x86_64-linux-gnu && DESTDIR=/<>/debian/tmp
LC_ALL=C.UTF-8 ninja install
[0/1] Installing files.
Compiling
'/<>/debian/tmp/usr/lib/python3/dist-packages/cairo/__init__.py'...
[...]
Running custom install script '/usr/bin/python3
/<>/obj-x86_64-linux-gnu/meson-private/pycompile.py
python-3.11-installed.json 0'
[...]
   dh_missing -O--buildsystem=meson
dh_missing: warning:
usr/lib/python3/dist-packages/cairo/__pycache__/__init__.cpython-311.pyc
exists in debian/tmp but is not installed to anywhere
dh_missing: error: missing files, aborting
[...]
make: *** [debian/rules:6: binary] Error 25
```


This fails with the release candidate, but does not fail against the
stable release of meson. The underlying cause is an additional feature
of meson:

https://mesonbuild.com/Release-notes-for-1-2-0.html#python-module-can-now-compile-bytecode

If this file is not desired in the debian package, please specify your
preferred value for this meson setting. For example, to avoid compiling
bytecode as part of `meson install`, you could setup the build system
with the `-Dpython.bytecompile=-1` option.


-- 
Eli Schwartz
--- End Message ---
--- Begin Message ---
Source: pycairo
Source-Version: 1.24.0-1.1
Done: Chris Hofstaedtler 

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

Debian distribution maintenance software
pp.
Chris Hofstaedtler  (supplier of updated pycairo 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: Sun, 06 Aug 2023 14:42:07 +0200
Source: pycairo
Architecture: source
Version: 1.24.0-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Chris Hofstaedtler 
Closes: 1040748
Changes:
 pycairo (1.24.0-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Workaround automatic Python bytecode compilation leading to
 FTBFS. (Closes: #1040748)
 Fixing this in debhelper for all packages would obviously be preferred,
 but for now this has to do.
Checksums-Sha1:
 e9f68412bb811721c1295ab914953dbb0ad9c545 2270 pycairo_1.24.0-1.1.dsc
 6bf74bb6c68f972edc4fb7ffa161fd00dc3680ed 15132 pycairo_1.24.0-1.1.debian.tar.xz
 b04069a561dbd713d298a524f27c18fd1ed4d1f3 10688 
pycairo_1.24.0-1.1_arm64.buildinfo
Checksums-Sha256:
 668075ae02d4401ee7493e07eefe1cd0f59d8d25cf96975bae25499eb99a5d54 2270 
pycairo_1.24.0-1.1.dsc
 b4c825032441dc80ccbb418829032505cbaa9476bb5c20abeefe90d7dc0978e6 15132 
pycairo_1.24.0-1.1.debian.tar.xz
 a2b7aba204ff86a5e59e3a3f547915f9761b93a455e0a792f1ca581513df58f5 10688 
pycairo_1.24.0-1.1_arm64.buildinfo
Files:
 74706db093e5f60c952a4f2bd71c1b1e 2270 python optional pycairo_1.24.0-1.1.dsc
 261004d284b33c5ddb15056ecfe7e55e 15132 python optional 
pycairo_1.24.0-1.1.debian.tar.xz
 68b81cca2d4b0deb70a9ed5cd8b75d73 10688 python optional 
pycairo_1.24.0-1.1_arm64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEfRrP+tnggGycTNOSXBPW25MFLgMFAmTPmB0ACgkQXBPW25MF
LgM/yA/9EcEdcUyvSUoSWg/jng2EPdQ1z4Pviqga7MYPhRVHSbiYH96x7Gj/ftyu
jR+EnUIu+bblVBdTeFKAH8CHvS1MdEE5JlsvKEhxNLEF3fZ3/jJbk0MuQ20xhTRS
jxYrXo7aZwMZdpDmT1yJVbrP+AsgFeUa21+nvaUlQh1ZfRj7rXhWjUd4T4Z8YUVD
Duyt9lM9leDMQqHzoKarzoDVE5Z5ddHEj25UWqEkCRTlwjOqjFABtSLYC1Yrnllj
F33yhvcMht9QJvf0cFgdCQFsusGmmmcB7s+AjtNkomFoQC7Tb1J+R7lmf5muL7dK
RTpiv/qYedaebBdlQLRkHiSIKYEvp4PfX5Afym2WfMtbtwlwhTthOiJQeVZjg+LU
R3qLcba5pjN6jZ+KOYr6GPbeOnD+xSP

Bug#1040748: pycairo: diff for NMU version 1.24.0-1.1

[Chris Hofstaedtler]

Source: pycairo
Followup-For: Bug #1040748

Control: tags 1040748 + patch
Control: tags 1040748 + pending

Dear maintainer,

I've prepared an NMU for pycairo (versioned as 1.24.0-1.1) and
uploaded it directly. 

Chris


diff -Nru pycairo-1.24.0/debian/changelog pycairo-1.24.0/debian/changelog
--- pycairo-1.24.0/debian/changelog 2023-07-03 19:31:14.0 +0200
+++ pycairo-1.24.0/debian/changelog 2023-08-06 14:42:07.0 +0200
@@ -1,3 +1,13 @@
+pycairo (1.24.0-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Workaround automatic Python bytecode compilation leading to
+FTBFS. (Closes: #1040748)
+Fixing this in debhelper for all packages would obviously be preferred,
+but for now this has to do.
+
+ -- Chris Hofstaedtler   Sun, 06 Aug 2023 14:42:07 +0200
+
 pycairo (1.24.0-1) unstable; urgency=medium
 
   * Team upload
diff -Nru pycairo-1.24.0/debian/rules pycairo-1.24.0/debian/rules
--- pycairo-1.24.0/debian/rules 2023-07-03 19:31:14.0 +0200
+++ pycairo-1.24.0/debian/rules 2023-08-06 14:41:01.0 +0200
@@ -5,6 +5,9 @@
 %:
dh $@ --with python3,sphinxdoc --buildsystem=meson
 
+override_dh_auto_configure:
+   dh_auto_configure -- -Dpython.bytecompile=-1
+
 execute_after_dh_auto_build:
python3 -m sphinx -bhtml docs debian/tmp-doc/html
# to fix lintian: privacy-breach-generic

Processed: notfound 1043134 in 0.9.94-1, notfound 1043134 in gnutls28/3.7.9-1, notfound 1043134 in 3.7.1-5 ...

[Debian Bug Tracking System]

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

> notfound 1043134 0.9.94-1
Bug #1043134 [guile-gnutls] guile-gnutls: FTBFS against gnutls28 3.8.1
There is no source info for the package 'guile-gnutls' at version '0.9.94-1' 
with architecture ''
Unable to make a source version for version '0.9.94-1'
Ignoring request to alter found versions of bug #1043134 to the same values 
previously set
> notfound 1043134 gnutls28/3.7.9-1
Bug #1043134 [guile-gnutls] guile-gnutls: FTBFS against gnutls28 3.8.1
Ignoring request to alter found versions of bug #1043134 to the same values 
previously set
> notfound 1043134 3.7.1-5
Bug #1043134 [guile-gnutls] guile-gnutls: FTBFS against gnutls28 3.8.1
Ignoring request to alter found versions of bug #1043134 to the same values 
previously set
> notfound 1043134 3.7.8-1
Bug #1043134 [guile-gnutls] guile-gnutls: FTBFS against gnutls28 3.8.1
Ignoring request to alter found versions of bug #1043134 to the same values 
previously set
> found 1043134 guile-gnutls/3.7.9-1
Bug #1043134 [guile-gnutls] guile-gnutls: FTBFS against gnutls28 3.8.1
Marked as found in versions guile-gnutls/3.7.9-1.
> thanks
Stopping processing here.

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

Processed: bug 1043134 is forwarded to https://gitlab.com/gnutls/guile/-/issues/15

[Debian Bug Tracking System]

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

> forwarded 1043134 https://gitlab.com/gnutls/guile/-/issues/15
Bug #1043134 [guile-gnutls] guile-gnutls: FTBFS against gnutls28 3.8.1
Set Bug forwarded-to-address to 'https://gitlab.com/gnutls/guile/-/issues/15'.
> thanks
Stopping processing here.

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

Bug#1043134: guile-gnutls: FTBFS against gnutls28 3.8.1

[Andreas Metzler]

Package: guile-gnutls
Version: 3.7.12
Severity: serious
Tags: upstream ftbfs
Justification: fails to build from source (but built successfully in the past)

I have already forwarded this upstream
https://gitlab.com/gnutls/guile/-/issues/15

Bug#1043128: kodi: FTBFS on s390x

[Vasyl Gello]

Hi Sebastian,

Thanks for the report! I did a preliminary investigation yesterday and filed the
bug against gcc-13 [1]. In the meantime I will include the workaround for it
and upload the -4 (as there is another ffmpeg6-related crash fix to upload).

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

-- 
Vasyl Gello
==
Certified SolidWorks Expert

Mob.:+380 (98) 465 66 77

E-Mail: vasek.ge...@gmail.com
==
호랑이는 죽어서 가죽을 남기고 사람은 죽어서 이름을 남긴다

Bug#1043121: marked as done (Needs breaks phosh << 0.30.0~)

[Debian Bug Tracking System]

Your message dated Sun, 06 Aug 2023 12:05:45 +
with message-id 
and subject line Bug#1043121: fixed in phoc 0.30.0+ds-2
has caused the Debian Bug report #1043121,
regarding Needs breaks phosh << 0.30.0~
to be marked as done.

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

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


-- 
1043121: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043121
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: phoc
Version: 0.30.0
Severity: critical

We can't run with phosh << 0.30.0 session due to XWayland changes that
crash g-s-d settings. Hence we need the breaks.
Cheers,
 -- Guido


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

Kernel: Linux 6.3.0-1-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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 phoc depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.40.0-4
ii  gsettings-desktop-schemas44.0-2
ii  libc62.37-5
ii  libcairo21.16.0-7
ii  libdrm2  2.4.115-1
ii  libegl1  1.6.0-1
ii  libgbm1  22.3.6-1+deb12u1
ii  libgles2 1.6.0-1
ii  libglib2.0-0 2.76.4-4
ii  libgnome-desktop-3-2044.0-1
ii  libinput10   1.23.0-2
ii  libjson-glib-1.0-0   1.6.6-1
ii  libpixman-1-00.42.2-1
ii  libseat1 0.7.0-6
ii  libudev1 252.11-1
ii  libwayland-client0   1.22.0-0.1
ii  libwayland-server0   1.22.0-0.1
ii  libxcb-composite01.15-1
ii  libxcb-dri3-01.15-1
ii  libxcb-icccm40.4.1-1.1
ii  libxcb-present0  1.15-1
ii  libxcb-render-util0  0.3.9-1+b1
ii  libxcb-render0   1.15-1
ii  libxcb-res0  1.15-1
ii  libxcb-shm0  1.15-1
ii  libxcb-xfixes0   1.15-1
ii  libxcb-xinput0   1.15-1
ii  libxcb1  1.15-1
ii  libxkbcommon01.5.0-1
ii  mutter-common44.0-2

Versions of packages phoc recommends:
ii  phosh  0.29.0+next20230727.1753.1

phoc suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: phoc
Source-Version: 0.30.0+ds-2
Done: Guido Günther 

We believe that the bug you reported is fixed in the latest version of
phoc, 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.
Guido Günther  (supplier of updated phoc 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: Sun, 06 Aug 2023 11:32:08 +0200
Source: phoc
Architecture: source
Version: 0.30.0+ds-2
Distribution: unstable
Urgency: medium
Maintainer: DebianOnMobile Maintainers 

Changed-By: Guido Günther 
Closes: 1043121
Changes:
 phoc (0.30.0+ds-2) unstable; urgency=medium
 .
   * d/control: Add breaks on phosh older than 0.30.0.
 Phosh itself works but want a session without g-s-d settings.
 (Closes: #1043121)
Checksums-Sha1:
 d872089fe6b5dc1a7fbf52bae596911602a2fe7e 2527 phoc_0.30.0+ds-2.dsc
 ad80b1c346adb303afcba369c84e4a66850f78d9 13144 phoc_0.30.0+ds-2.debian.tar.xz
 6be043e430903452613df42fe6a80b0a9fc5727c 16967 phoc_0.30.0+ds-2_amd64.build

Bug#1037736: [Pkg-sass-devel] Bug#1037736: libsass: ftbfs with GCC-13

[Jonas Smedegaard]

Quoting Bo YU (2023-08-06 13:48:43)
> Sorry for the later reply, I was travelling some days and now I can
> own my time.

No problem - there is no rush, so just take your time :-)


> On Mon, Jul 31, 2023 at 1:09 AM Jonas Smedegaard  wrote:
> > If you are generally interested in SASS tools and want to help maintain
> > them in Debian, then you are very welcome to join the team (which is
> > effectively only me at the moment).
> Thanks for the invitation. I am happy to maintain SASS tools packages.

Great!  Please request membership of the salsa group at
https://salsa.debian.org/groups/sass-team/-/group_members

> At the moment I need to take some time to understand their technical
> details but maintaining them should be okay given the packages were in
> a good sharp.

Don't hesitate to ask!  This is a very small team, and I am bad at
writing documentation so some things are only in my head and maybe not
easy to guess, to please just ask!

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/
 * Sponsorship: https://ko-fi.com/drjones

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Bug#1040630: marked as done (gavodachs autopkg tests fail with pillow 10.0.0)

[Debian Bug Tracking System]

Your message dated Sun, 6 Aug 2023 13:47:25 +0200
with message-id <2bd92f46-398b-e5ac-5864-db37bbfb4...@debian.org>
and subject line Closing bub
has caused the Debian Bug report #1040630,
regarding gavodachs autopkg tests fail with pillow 10.0.0
to be marked as done.

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

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


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

Package: src:gavodachs
Version: 2.8+dfsg-1
Severity: serious
Tags: sid trixie

see
https://ci.debian.net/data/autopkgtest/testing/amd64/g/gavodachs/35498774/log.gz

107s autopkgtest [17:24:20]: test integration-test: [---
108s Making data it/q#import_t5
108s Shipped 5/5
108s Create index t5_spoint_t5
108s Rows affected: 5
108s Making data it/q#import_t25
108s Shipped 25/30
108s Create index t25_spoint_t25
108s Rows affected: 25
110s EE
110s 2 of 2 bad.  avg 0.01, min 0.01, max 0.01. 178.7/s, par 1.3
110s From it/q:
110sERROR SCS has a valid response
110sERROR TAP query with pgsphere yields plausible result
110s
110s
111s autopkgtest [17:24:24]: test integration-test: ---]
111s integration-test FAIL non-zero exit status 1
111s autopkgtest [17:24:24]: test integration-test:  - - - - - - - - - - results 
- - - - - - - - - -

111s autopkgtest [17:24:24]:  summary
111s integration-test FAIL non-zero exit status 1
--- End Message ---
--- Begin Message ---

Source: gavodachs
Source-Version: 2.8+dfsg-2
Done: Markus Demleitner 

This bug was closed by uploading a new version; however the autoclose didn't 
work.
("fixes:" instead of "closes:")

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 26 Jul 2023 16:45:08 +0200
Source: gavodachs
Architecture: source
Version: 2.8+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Astronomy Team 

Changed-By: Markus Demleitner 
Changes:
 gavodachs (2.8+dfsg-2) unstable; urgency=medium
 .
   * Update for pillow API change (fixes: #1040630)
   * Making dachs limits work.
Checksums-Sha1:
 13dbeaba30a6dd1f319ad3baf953fccbe4d56384 2400 gavodachs_2.8+dfsg-2.dsc
 b78b14707497cb70f771fc59093b44be7e2b96ee 10088 
gavodachs_2.8+dfsg-2.debian.tar.xz
Checksums-Sha256:
 6bff6cfbd11297ee2edcb671186363ad4a2ca871cf20634c0ffbda6bb5a397d0 2400 
gavodachs_2.8+dfsg-2.dsc
 dd30ef2591396cd5d33a2062d7a8cf558b2c2f5bbfc4c65a2f8530f838d52e10 10088 
gavodachs_2.8+dfsg-2.debian.tar.xz
Files:
 f638a2a0778164499553223e6937aa29 2400 python optional gavodachs_2.8+dfsg-2.dsc
 dc3febc1f2c21c66a5dc0e0a91b1bd2b 10088 python optional 
gavodachs_2.8+dfsg-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEuvxshffLFD/utvsVcRWv0HcQ3PcFAmTCVtAACgkQcRWv0HcQ
3PeiNRAApzLVxsJ1lAeMgl+q/d0JyNbAwODzNDrwcenKqBhWnDWP/c2OZlfvGhDp
DqYrs5N1OeK2Ii1eWqx4IhnH2Chdk0cU3BYrqNDY9yqVk5apX4ZtTKrilIOHHxxK
DoPlqfj922oSK7v7OehuVg1oTw4fEc73feuXbijBYA9aA41gWSPvsgL+Oa+WUF84
9Hesp0HdS2vE03TZn4ZmZYiwAIspb+x9wGZncfSiqexO0tvHuRSqp8rwnBTMy0c+
u44iXDLsQb4hygYhAOSRrX3aciSRaRZiWPUwoxo8PmppncjL3pwB0DEpl9JGTQHa
oJl8IF+X8nx9CnngBFFMUjlMmOWG38EpamPbCg57GFd5iKxCzhqfsz3PLqbsNeJG
zWzmdoTqMZqjdeATwszHHjQ07FtYK8DQVzD3VpTSLVY4K8GpfjGyjku8nR/sXAJ5
fl9au2qFrcpDESxcpzV1Rr+hfue+/bIbwEVb8+e4/mPDsmYYASDzAqbk234EqOee
HSJaK6GiCB4/90wuhCG5d6zgRIts3BQq2g6XjJG41xY791fQihL3+qMDwLy+Dkiy
7aVf9NRMEmmSF5b9mf0a0z18S0lWoJB1Njdd1FWeaQRGOMNzHARap8yzNjj8Wj+7
IwyQVr9eHC4CFNSQnXl9LmZWSu8AinqPZgYcELT+DvA4blHndd8=
=RLuL
-END PGP SIGNATURE End Message ---

Bug#1037736: [Pkg-sass-devel] Bug#1037736: libsass: ftbfs with GCC-13

[Bo YU]

Hi Jonas!

Sorry for the later reply, I was travelling some days and now I can own my time.

On Mon, Jul 31, 2023 at 1:09 AM Jonas Smedegaard  wrote:
>
> Hi Bo,
>
> Quoting Bo YU (2023-07-30 18:40:01)
> > I have updated the symbols file to fix the issue, could you apply it on
> > next upload?
>
> Thanks a lot.  I will apply now.
>
> If you are generally interested in SASS tools and want to help maintain
> them in Debian, then you are very welcome to join the team (which is
> effectively only me at the moment).
Thanks for the invitation. I am happy to maintain SASS tools packages.
At the moment I need to take some time to understand their technical details
but maintaining them should be okay given the packages were in a good sharp.
Thanks your work!

BR,
Bo
>
> If you just wanted to help fix this one issue, then that is fine too, of
> course.
>
>
> > BTW, The issue should be the same with #1042201
>
> Agreed, that is same issue.
>
>
> Kind regards,
>
>  - Jonas
>
> --
>  * Jonas Smedegaard - idealist & Internet-arkitekt
>  * Tlf.: +45 40843136  Website: http://dr.jones.dk/
>  * Sponsorship: https://ko-fi.com/drjones
>
>  [x] quote me freely  [ ] ask before reusing  [ ] keep private

Bug#1025563: marked as done (gdebi: dependency on transitional policykit-1 package)

[Debian Bug Tracking System]

Your message dated Sun, 06 Aug 2023 11:07:08 +
with message-id 
and subject line Bug#1025563: fixed in gdebi 0.9.5.7+nmu7
has caused the Debian Bug report #1025563,
regarding gdebi: dependency on transitional policykit-1 package
to be marked as done.

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

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


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

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

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

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

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

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

This is part of a mass bug filing, see
.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Source: gdebi
Source-Version: 0.9.5.7+nmu7
Done: Bastian Germann 

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

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

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

Debian distribution maintenance software
pp.
Bastian Germann  (supplier of updated gdebi 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: Sun, 06 Aug 2023 12:33:07 +0200
Source: gdebi
Architecture: source
Version: 0.9.5.7+nmu7
Distribution: unstable
Urgency: medium
Maintainer: gdebi developers 
Changed-By: Bastian Germann 
Closes: 831050 887056 983683 1018366 1025563
Changes:
 gdebi (0.9.5.7+nmu7) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Replace policykit-1 with pkexec. (Closes: #1025563, #983683)
   * Remove X-Python3-Version.
   * Drop dependency against gnome-icon-theme. (Closes: #831050, #887056)
   * Drop unnecessary python3-nose. (Closes: #1018366)
Checksums-Sha1:
 7ef103f06bbde4c4df7957abef0245f1da95ea23 1560 gdebi_0.9.5.7+nmu7.dsc
 cfccf3793f3eb26f27e2873aeed4013f9bdd278b 191524 gdebi_0.9.5.7+nmu7.tar.xz
 22a0567016d65d92178ecb843a96575397e62081 15591 
gdebi_0.9.5.7+nmu7_source.buildinfo
Checksums-Sha256:
 62f82393c15b72a8e7efb9457447ff2ce32ee159af7b7c44adf4ffc44e701620 1560 
gdebi_0.9.5.7+nmu7.dsc
 46ae953fa14cca9927ac6c8ff760a7a9e2dbb9c43eeb074ad5d9a3becff8 191524 
gdebi_0.9.5.7+nmu7.tar.xz
 7aad422800d28a4b8a53b4692f1845511feebb31800c4482cee5ec565a3801ed 15591 
gdebi_0.9.5.7+nmu7_source.buildinfo
Files:
 6ce1f30bbe4ccbc3ca76cb3c7eba4fae 1560 admin optional gdebi_0.9.5.7+nmu7.dsc
 e73396b51f2261bce05bb9fb6a96d874 191524 admin optional 
gdebi_0.9.5.7+nmu7.tar.xz
 507cd4468ab554d5e5ef3c96728b5c15 15591 admin optional 
gdebi_0.9.5.7+nmu7_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmTPe9cQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFLF8C/9waf2K/Z7p77Fvqs0YZp127CoJqZbqSpDT
iZA/gEhbP8V7zTXx2jyCz5WCiUO0zxTC0FbrtgKUfGXfdB0fb4PaGRGM/0nxG6RZ
iVvHn4kl+Vgm5w3r35g6zx9ujEMla+C9c5s4tlsx2yhKeLtRDleDNu9x6eUwSePy
8JO8WrO1nAhFTwemb2IunlbOxh2CDkW8zPmCQ+ZwuqZdYw7sMB5RLiAVb/LnN72C
payTZYbtMGpfBSqg9jf4admYPOF0xOwXuVx/1pmKVvsrEwHzusvfVj2SF61M2aZK
mSz8Lx08D5+4OMHeUNO8cWekNwEgzqypocEJ0tKMMqVEe912T+RJifOP7++DC975
83D41PR5g76Q3GrQa2wbjNJr

Processed: r-cran-mlmrev: i386 autopkgtest regression with rmatrix 1.6-0-1

[Debian Bug Tracking System]

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

> reopen 1043130
Bug #1043130 {Done: Paul Gevers } [src:r-cran-mlmrev] 
r-cran-mlmrev: i386 autopkgtest regression with rmatrix 1.6-0-1
Bug reopened
Ignoring request to alter fixed versions of bug #1043130 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#1025563: gdebi: dependency on transitional policykit-1 package

[Bastian Germann]

I am uploading a NMU to fix this. The debdiff is attached.diff -Nru gdebi-0.9.5.7+nmu6/data/gdebi.desktop.in 
gdebi-0.9.5.7+nmu7/data/gdebi.desktop.in
--- gdebi-0.9.5.7+nmu6/data/gdebi.desktop.in2021-01-13 19:45:14.0 
+0100
+++ gdebi-0.9.5.7+nmu7/data/gdebi.desktop.in2023-08-06 12:33:07.0 
+0200
@@ -3,7 +3,7 @@
 _GenericName=Package Installer
 _Comment=Install and view software packages
 Exec=gdebi-gtk %f
-Icon=gnome-mime-application-x-deb
+Icon=package-x-generic
 Terminal=false
 Type=Application
 Categories=System;
diff -Nru gdebi-0.9.5.7+nmu6/debian/changelog 
gdebi-0.9.5.7+nmu7/debian/changelog
--- gdebi-0.9.5.7+nmu6/debian/changelog 2021-10-14 23:45:16.0 +0200
+++ gdebi-0.9.5.7+nmu7/debian/changelog 2023-08-06 12:33:07.0 +0200
@@ -1,3 +1,13 @@
+gdebi (0.9.5.7+nmu7) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Replace policykit-1 with pkexec. (Closes: #1025563, #983683)
+  * Remove X-Python3-Version.
+  * Drop dependency against gnome-icon-theme. (Closes: #831050, #887056)
+  * Drop unnecessary python3-nose. (Closes: #1018366)
+
+ -- Bastian Germann   Sun, 06 Aug 2023 12:33:07 +0200
+
 gdebi (0.9.5.7+nmu6) unstable; urgency=medium
 
   * Non-maintainer upload
diff -Nru gdebi-0.9.5.7+nmu6/debian/control gdebi-0.9.5.7+nmu7/debian/control
--- gdebi-0.9.5.7+nmu6/debian/control   2021-05-19 21:07:02.0 +0200
+++ gdebi-0.9.5.7+nmu7/debian/control   2023-08-06 12:33:07.0 +0200
@@ -10,13 +10,11 @@
python3-all,
python3-apt,
python3-gi,
-   python3-nose,
python3-setuptools,
intltool,
xvfb,
xauth,
lintian,
-X-Python3-Version: >= 3.3
 Standards-Version: 3.9.6
 Vcs-Bzr: https://code.launchpad.net/~gdebi-developers/gdebi/trunk
 
@@ -45,8 +43,7 @@
  gir1.2-gtk-3.0,
  gir1.2-vte-2.91,
  python3-gi,
- policykit-1,
- gnome-icon-theme
+ pkexec
 Recommends: libgtk2-perl, shared-mime-info, lintian
 Description: simple tool to view and install deb files - GNOME GUI
  gdebi lets you install local deb packages resolving and installing
@@ -57,18 +54,3 @@
  possible to inspect the control and data members of the packages.
  .
  This package contains the graphical user interface.
-
-#Package: gdebi-kde
-#Architecture: all
-#Depends: ${python3:Depends},
-# ${misc:Depends},
-# gdebi-core (= ${source:Version}),
-# python3-pykde4,
-# kdebase-runtime | kde-runtime | kdesudo
-#Recommends: shared-mime-info
-#Description: simple tool to install deb files - KDE GUI
-# gdebi lets you install local deb packages resolving and installing
-# its dependencies. apt does the same, but only for remote (http, ftp)
-# located packages.
-# .
-# This package contains the KDE user interface.
diff -Nru gdebi-0.9.5.7+nmu6/GDebi/GDebiGtk.py 
gdebi-0.9.5.7+nmu7/GDebi/GDebiGtk.py
--- gdebi-0.9.5.7+nmu6/GDebi/GDebiGtk.py2021-10-14 21:58:18.0 
+0200
+++ gdebi-0.9.5.7+nmu7/GDebi/GDebiGtk.py2023-08-06 12:33:07.0 
+0200
@@ -71,7 +71,7 @@
 # use a nicer default icon
 icons = Gtk.IconTheme.get_default()
 try:
-  logo=icons.load_icon("gnome-mime-application-x-deb", 48, 0)
+  logo=icons.load_icon("package-x-generic", 48, 0)
   if logo != "":
 Gtk.Window.set_default_icon_list([logo])
 except Exception as e:

Processed: r-cran-mlmrev: i386 autopkgtest regression with rmatrix 1.6-0-1

[Debian Bug Tracking System]

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

> clone 1041738 -1
Bug #1041738 {Done: Paul Gevers } [src:lme4] src:lme4: fails 
to migrate to testing for too long: causes timeout in autopkgtests on i386
Bug 1041738 cloned as bug 1043130
> reassign -1 src:r-cran-mlmrev 1.0-8-2
Bug #1043130 {Done: Paul Gevers } [src:lme4] src:lme4: fails 
to migrate to testing for too long: causes timeout in autopkgtests on i386
Bug reassigned from package 'src:lme4' to 'src:r-cran-mlmrev'.
No longer marked as found in versions lme4/1.1-31-1.
No longer marked as fixed in versions lme4/1.1-34-1.
Bug #1043130 {Done: Paul Gevers } [src:r-cran-mlmrev] 
src:lme4: fails to migrate to testing for too long: causes timeout in 
autopkgtests on i386
Marked as found in versions r-cran-mlmrev/1.0-8-2.
> retitle -1 r-cran-mlmrev: i386 autopkgtest regression with rmatrix 1.6-0-1
Bug #1043130 {Done: Paul Gevers } [src:r-cran-mlmrev] 
src:lme4: fails to migrate to testing for too long: causes timeout in 
autopkgtests on i386
Changed Bug title to 'r-cran-mlmrev: i386 autopkgtest regression with rmatrix 
1.6-0-1' from 'src:lme4: fails to migrate to testing for too long: causes 
timeout in autopkgtests on i386'.
> thanks
Stopping processing here.

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

Bug#1041738: src:lme4: fails to migrate to testing for too long: causes timeout in autopkgtests on i386

[Graham Inggs]

Hi All

Just a quick update.

On Sun, 23 Jul 2023 at 15:07, Graham Inggs  wrote:
> For what it's worth, r-cran-afex[1] and r-cran-mertools[2] **are**
> passing in unstable.  So perhaps whatever package fixed this condition
> has been uploaded, but not yet migrated.

Since rmatrix 1.6-0-1 migrated, these tests are now passing on i386
and no longer blocking the migrating of lme4.

> Yet r-cran-mlmrev[3] still seems to have the timeout issue in unstable.

The timeout of r-cran-mlmrev's autopkgtests on i386 is the last
blocker for lme4, so I will allow lme4 to migrate and (attempt) to
clone this bug to r-cran-mlmrev.

As Dirk wrote:

On Sun, 23 Jul 2023 at 16:32, Dirk Eddelbuettel  wrote:
> So if it were me I'd just skip that test file on i386 and move on.

Maybe this is the sane option, but CC'ing the i386 porters (Hi Adrian!) anyway.

Regards
Graham

Bug#1043128: kodi: FTBFS on s390x

[Sebastian Ramacher]

Source: kodi
Version: 2:20.2+dfsg-3
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=kodi&arch=s390x&ver=2%3A20.2%2Bdfsg-3&stamp=1691212083&raw=0

make[3]: *** Waiting for unfinished jobs
[  7%] Building CXX object 
build/windowing/X11/CMakeFiles/windowing_X11.dir/WinSystemX11.cpp.o
cd /<>/obj-s390x-linux-gnu/build/windowing/X11 && /usr/bin/c++  
-I/<>/obj-s390x-linux-gnu -I/<> 
-I/<>/lib -I/<>/xbmc 
-I/<>/xbmc/platform/linux 
-I/<>/xbmc/cores/VideoPlayer 
-I/<>/obj-s390x-linux-gnu/build 
-I/<>/xbmc/platform/posix -isystem 
/<>/obj-s390x-linux-gnu/build/include -isystem 
/usr/include/dbus-1.0 -isystem /usr/lib/s390x-linux-gnu/dbus-1.0/include 
-isystem /usr/include/pipewire-0.3 -isystem /usr/include/spa-0.2 -isystem 
/usr/include/python3.11 -isystem /usr/include/samba-4.0 -isystem 
/usr/include/libxml2 -isystem 
/<>/obj-s390x-linux-gnu/build/cores/RetroPlayer/messages -isystem 
/usr/include/freetype2 -isystem /usr/include/fribidi -isystem /usr/include/lzo 
-isystem /usr/include/libdrm -g -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -O3 -Wdate-time 
-D_FORTIFY_SOURCE=2 -D_XBMC -DDEB_VERSION=\"2:20.2+dfsg-3\" -Wall 
-Wdouble-promotion -Wmissing-field-initializers -Wsign-compare -Wextra 
-Wno-unused-parameter -Wno-cast-function-type -Wnon-virtual-dtor -O2 -g 
-DNDEBUG -std=c++17 -DTARGET_POSIX -DTARGET_LINUX -D_GNU_SOURCE 
-DHAVE_LINUX_UDMABUF=1 -DHAVE_LINUX_DMA_HEAP=1 -DHAVE_LINUX_DMA_BUF=1 
-DHAVE_MKOSTEMP=1 -DHAVE_LINUX_MEMFD=1 -DWORDS_BIGENDIAN=1 -DHAVE_STATX=1 
-D__STDC_CONSTANT_MACROS -D_FILE_OFFSET_BITS=64 -DHAS_POSIX_NETWORK 
-DHAS_LINUX_NETWORK -DHAS_BUILTIN_SYNC_ADD_AND_FETCH=1 
-DHAS_BUILTIN_SYNC_SUB_AND_FETCH=1 -DHAS_BUILTIN_SYNC_VAL_COMPARE_AND_SWAP=1 
-DHAVE_INOTIFY=1 -DHAVE_POSIX_FADVISE=1 -DHAVE_LOCALTIME_R=1 -DHAVE_GMTIME_R=1 
-DHAVE_INTTYPES_H=1 -DHAS_ALSA=1 -DHAS_AVAHI=1 -DHAS_ZEROCONF=1 
-DHAVE_LIBBLURAY=1 -DHAVE_LIBBLURAY_BDJ=1 -DHAVE_LIBCEC=1 -DHAS_DBUS=1 
-DHAS_ISO9660PP=1 -DHAVE_LCMS2=1 -DCMS_NO_REGISTER_KEYWORD=1 -DHAS_LIRC=1 
-DHAS_WEB_SERVER=1 -DHAS_WEB_INTERFACE=1 -DHAS_FILESYSTEM_NFS=1 
-DHAS_NFS_SET_TIMEOUT -DHAS_PIPEWIRE=1 -DHAS_AIRPLAY=1 -DHAS_PULSEAUDIO=1 
-DHAS_PYTHON=1 -DHAS_FILESYSTEM_SMB=1 -DHAS_SNDIO=1 -DHAVE_LIBUDEV=1 
-DHAS_UDFREAD=1 -DHAVE_LIBXSLT=1 -DHAVE_LIBVA=1 -DHAS_GLX=1 -DHAVE_LIBVDPAU=1 
-DDATE_HAS_STRINGVIEW -DFFMPEG_VER_SHA=\"4.4.1\" -DHAVE_GCRYPT=1 
-DSPDLOG_FMT_EXTERNAL -DSPDLOG_DEBUG_ON -DSPDLOG_NO_ATOMIC_LEVELS 
-DSPDLOG_ENABLE_PATTERN_PADDING -DSPDLOG_COMPILED_LIB -DSPDLOG_SHARED_LIB 
-DHAS_EGL=1 -DHAVE_EGLEXTANGLE=1 -DHAVE_X11=1 -DHAVE_LIBXRANDR=1 
-DHAVE_HDR_OUTPUT_METADATA=1 -DHAVE_DRM_MODIFIER_NAME=1 -DHAS_GL=1 
-DHAVE_WAYLAND=1 -DHAVE_GBM=1 -DHAS_GBM_BO_MAP=1 -DHAS_GBM_MODIFIERS=1 
-DHAS_MYSQL=1 -DHAS_UPNP=1 -DHAS_DVD_DRIVE -DHAS_CDDA_RIPPER -DHAS_AIRTUNES=1 
-DBIN_INSTALL_PATH=\"/usr/lib/s390x-linux-gnu/kodi\" 
-DINSTALL_PATH=\"/usr/share/kodi\" -Werror=double-promotion 
-Werror=missing-field-initializers -Werror=sign-compare -MD -MT 
build/windowing/X11/CMakeFiles/windowing_X11.dir/WinSystemX11.cpp.o -MF 
CMakeFiles/windowing_X11.dir/WinSystemX11.cpp.o.d -o 
CMakeFiles/windowing_X11.dir/WinSystemX11.cpp.o -c 
/<>/xbmc/windowing/X11/WinSystemX11.cpp
In file included from /<>/xbmc/guilib/VisibleEffect.h:23,
 from /<>/xbmc/guilib/GUIControl.h:17,
 from /<>/xbmc/guilib/GUIControlLookup.h:11,
 from /<>/xbmc/guilib/GUIControlGroup.h:16,
 from /<>/xbmc/guilib/GUIWindow.h:17,
 from /<>/xbmc/guilib/GUIWindowManager.h:12,
 from /<>/xbmc/windowing/X11/WinEventsX11.cpp:16:
/<>/xbmc/utils/TransformMatrix.h: In member function ‘void 
TransformMatrix::SetFader(float)’:
/<>/xbmc/utils/TransformMatrix.h:129:19: error: implicit 
conversion from ‘float’ to ‘double’ to match other operand of binary expression 
[-Werror=double-promotion]
  129 | identity = (a == 1.0f);
  | ~~^~~
/<>/xbmc/utils/TransformMatrix.h: In member function ‘void 
TransformMatrix::SetFader(float, float, float, float)’:
/<>/xbmc/utils/TransformMatrix.h:141:20: error: implicit 
conversion from ‘float’ to ‘double’ to match other operand of binary expression 
[-Werror=double-promotion]
  141 | identity = ((a == 1.0f) && (r == 1.0f) && (g == 1.0f) && (b == 
1.0f));
  |  ~~^~~
/<>/xbmc/utils/TransformMatrix.h:141:35: error: implicit 
conversion from ‘float’ to ‘double’ to match other operand of binary expression 
[-Werror=double-promotion]
  141 | identity = ((a == 1.0f) && (r == 1.0f) && (g == 1.0f) && (b == 
1.0f));
  | ~~^~~
/<>/xbmc/utils/TransformMatrix.h:141:50: error: implicit 
conversion from ‘float’ to ‘double’ to match other operand of binary expression 
[-Werror=double-promotion]
  141 | identity = ((a

Processed: severity of 1017663 is serious, found 1017663 in 9.0.2-5, fixed 1017663 in 9.4.5-1~exp3

[Debian Bug Tracking System]

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

> severity 1017663 serious
Bug #1017663 [src:ghc] ghc: Please upgrade to llvm-toolchain-14
Severity set to 'serious' from 'important'
> found 1017663 9.0.2-5
Bug #1017663 [src:ghc] ghc: Please upgrade to llvm-toolchain-14
Marked as found in versions ghc/9.0.2-5.
> fixed 1017663 9.4.5-1~exp3
Bug #1017663 [src:ghc] ghc: Please upgrade to llvm-toolchain-14
Marked as fixed in versions ghc/9.4.5-1~exp3.
> thanks
Stopping processing here.

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

Processed: creduce: switch to current llvm default version

[Debian Bug Tracking System]

Processing control commands:

> block 1017679 by -1
Bug #1017679 [ftp.debian.org] RM: llvm-toolchain-13 -- ROM; Limit the number of 
llvm versions
1017679 was blocked by: 1017663 1017659 1000927 1017653 1000922 1017669 1017674 
1017667 1017661 1004883 1017662 1017656 1012329 1017677 1017668 1017665 1017672 
1021387 1017666 1012184 1017660 1017654 1017658 1017655
1017679 was not blocking any bugs.
Added blocking bug(s) of 1017679: 1043127

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

Bug#1043127: creduce: switch to current llvm default version

[Sebastian Ramacher]

Source: creduce
Version: 2.10.0+20220116-1
Severity: serious
Control: block 1017679 by -1
X-Debbugs-Cc: sramac...@debian.org

creduce currently blocks removal of llvm-toolchain-13. Please move to
the current default version (14) or newer. See #1017679 for the removal
bug.

Cheers
-- 
Sebastian Ramacher

Processed: tagging 1014623

[Debian Bug Tracking System]

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

> tags 1014623 + ftbfs
Bug #1014623 [src:xjig] xjig: build-depends on obsolete libnetpbm10-dev, ftbfs 
with libnetpbm11-dev
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: found 1043121 in 0.30.0+ds-1, notfound 1043121 in 0.30.0

[Debian Bug Tracking System]

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

> found 1043121 0.30.0+ds-1
Bug #1043121 [phoc] Needs breaks phosh << 0.30.0~
Marked as found in versions phoc/0.30.0+ds-1.
> notfound 1043121 0.30.0
Bug #1043121 [phoc] Needs breaks phosh << 0.30.0~
There is no source info for the package 'phoc' at version '0.30.0' with 
architecture ''
Unable to make a source version for version '0.30.0'
No longer marked as found in versions 0.30.0.
> thanks
Stopping processing here.

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

Bug#1043121: marked as pending in phoc

[Guido Günther]

Control: tag -1 pending

Hello,

Bug #1043121 in phoc 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/DebianOnMobile-team/phoc/-/commit/7a74970c068f47d9f98b29f247807c4e06d15f62


d/control: Add breaks on phosh older than 0.30.0

Phosh itself works but want a session without g-s-d settings.

Closes: #1043121


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1043121

Processed: Bug#1043121 marked as pending in phoc

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1043121 [phoc] Needs breaks phosh << 0.30.0~
Added tag(s) pending.

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

Bug#1043123: llvm-toolchain-13: do not release with trixie

[Sebastian Ramacher]

Source: llvm-toolchain-13
Version: 1:13.0.1-13
Severity: serious
X-Debbugs-Cc: sramac...@debian.org

Let's reduce the number of llvm-toolchains in trixie.

Cheers
-- 
Sebastian Ramacher

Processed: Re: Bug#1043113: mu-cade: this package should be rebuilt against GCC-13

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #1043113 [mu-cade] mu-cade: this package should be rebuilt against GCC-13
Severity set to 'normal' from 'serious'
> reassign -1 release.debian.org
Bug #1043113 [mu-cade] mu-cade: this package should be rebuilt against GCC-13
Bug reassigned from package 'mu-cade' to 'release.debian.org'.
No longer marked as found in versions mu-cade/0.11.dfsg1-13.
Ignoring request to alter fixed versions of bug #1043113 to the same values 
previously set
> retitle -1 nmu: mu-cade 0.11.dfsg1-13
Bug #1043113 [release.debian.org] mu-cade: this package should be rebuilt 
against GCC-13
Changed Bug title to 'nmu: mu-cade 0.11.dfsg1-13' from 'mu-cade: this package 
should be rebuilt against GCC-13'.

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

Bug#1043113: mu-cade: this package should be rebuilt against GCC-13

[Sebastian Ramacher]

Control: severity -1 normal
Control: reassign -1 release.debian.org
Control: retitle -1 nmu: mu-cade 0.11.dfsg1-13

On 2023-08-06 10:48:17 +0200, Alexandre Detiste wrote:
> Package: mu-cade
> Version: 0.11.dfsg1-13
> Severity: serious
> Justification: GCC-12 to be removed soon
> 
> Hi,
> 
> mu-cade depends against deprecated GCC-12 runtime,
> it should be rebuilt against GCC-13.

Rebuilds are requested via binNMU bugs against release.debian.org.
Reassigning accordingly.

Cheers
-- 
Sebastian Ramacher

Bug#1043122: rust-cargo-outdated FTBFS on i386

[Adrian Bunk]

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

Bug#1043121: Needs breaks phosh << 0.30.0~

[Guido Günther]

Package: phoc
Version: 0.30.0
Severity: critical

We can't run with phosh << 0.30.0 session due to XWayland changes that
crash g-s-d settings. Hence we need the breaks.
Cheers,
 -- Guido


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

Kernel: Linux 6.3.0-1-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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 phoc depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.40.0-4
ii  gsettings-desktop-schemas44.0-2
ii  libc62.37-5
ii  libcairo21.16.0-7
ii  libdrm2  2.4.115-1
ii  libegl1  1.6.0-1
ii  libgbm1  22.3.6-1+deb12u1
ii  libgles2 1.6.0-1
ii  libglib2.0-0 2.76.4-4
ii  libgnome-desktop-3-2044.0-1
ii  libinput10   1.23.0-2
ii  libjson-glib-1.0-0   1.6.6-1
ii  libpixman-1-00.42.2-1
ii  libseat1 0.7.0-6
ii  libudev1 252.11-1
ii  libwayland-client0   1.22.0-0.1
ii  libwayland-server0   1.22.0-0.1
ii  libxcb-composite01.15-1
ii  libxcb-dri3-01.15-1
ii  libxcb-icccm40.4.1-1.1
ii  libxcb-present0  1.15-1
ii  libxcb-render-util0  0.3.9-1+b1
ii  libxcb-render0   1.15-1
ii  libxcb-res0  1.15-1
ii  libxcb-shm0  1.15-1
ii  libxcb-xfixes0   1.15-1
ii  libxcb-xinput0   1.15-1
ii  libxcb1  1.15-1
ii  libxkbcommon01.5.0-1
ii  mutter-common44.0-2

Versions of packages phoc recommends:
ii  phosh  0.29.0+next20230727.1753.1

phoc suggests no packages.

-- no debconf information

Bug#1043120: gr-limesdr: breaks ABI without SONAME bump

[Sebastian Ramacher]

Source: gr-limesdr
Version: 3.0.1.10.69-1
Severity: serious
X-Debbugs-Cc: sramac...@debian.org

https://ci.debian.net/data/autopkgtest/testing/amd64/g/gnss-sdr/36539433/log.gz

31s (Reading database ... 13556 files and directories currently installed.)
 31s Removing autopkgtest-satdep (0) ...
 31s autopkgtest [04:58:26]: test testgnsssdr: [---
 31s gnss-sdr: symbol lookup error: gnss-sdr: undefined symbol: 
_ZN2gr7limesdr6source4makeENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEiRKS7_
 31s autopkgtest [04:58:26]: test testgnsssdr: ---]
 32s testgnsssdr  FAIL non-zero exit status 127

Cheers
-- 
Sebastian Ramacher

Bug#1043119: rust-sd: FTBFS

[Sebastian Ramacher]

Source: rust-sd
Version: 0.7.6-1
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-sd&arch=amd64&ver=0.7.6-1%2Bb4&stamp=1691270171&raw=0

dh_dwz -a -O--buildsystem=cargo
dwz: debian/sd/usr/bin/sd: Couldn't find DIE at [9a45a] referenced by 
DW_AT_abstract_origin from DIE at [1a54ea]
dh_dwz: error: dwz -- debian/sd/usr/bin/sd returned exit code 1
dh_dwz: error: Aborting due to earlier error
make: *** [debian/rules:3: binary-arch] Error 25

Cheers
-- 
Sebastian Ramacher

Bug#1043118: victoriametrics: FTBFS: test failure

[Sebastian Ramacher]

Source: victoriametrics
Version: 1.79.5+ds1-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=victoriametrics&arch=amd64&ver=1.79.5%2Bds1-2%2Bb6&stamp=1691274080&raw=0

=== RUN   TestMergeForciblyStop
2023-08-05T22:21:13.980Zpanic   
VictoriaMetrics/lib/storage/inmemory_part.go:37 BUG: Inmemory.InitFromRows must 
accept at least one row
--- FAIL: TestMergeForciblyStop (0.00s)
panic: BUG: Inmemory.InitFromRows must accept at least one row [recovered]
panic: BUG: Inmemory.InitFromRows must accept at least one row

goroutine 31839 [running]:
testing.tRunner.func1.2({0x6f7a60, 0xc003b2e4b0})
/usr/lib/go-1.20/src/testing/testing.go:1526 +0x24e
testing.tRunner.func1()
/usr/lib/go-1.20/src/testing/testing.go:1529 +0x39f
panic({0x6f7a60, 0xc003b2e4b0})
/usr/lib/go-1.20/src/runtime/panic.go:884 +0x213
github.com/VictoriaMetrics/VictoriaMetrics/lib/logger.logMessage({0x742b44, 
0x5}, {0xc00507f300, 0x37}, 0x0?)

/<>/_build/src/github.com/VictoriaMetrics/VictoriaMetrics/lib/logger/logger.go:269
 +0x965
github.com/VictoriaMetrics/VictoriaMetrics/lib/logger.logLevelSkipframes(0x1, 
{0x742b44, 0x5}, {0x75c548?, 0xc00503fcc8?}, {0x0?, 0x90?, 0x72aba0?})

/<>/_build/src/github.com/VictoriaMetrics/VictoriaMetrics/lib/logger/logger.go:137
 +0x1a5
github.com/VictoriaMetrics/VictoriaMetrics/lib/logger.logLevel(...)

/<>/_build/src/github.com/VictoriaMetrics/VictoriaMetrics/lib/logger/logger.go:129
github.com/VictoriaMetrics/VictoriaMetrics/lib/logger.Panicf(...)

/<>/_build/src/github.com/VictoriaMetrics/VictoriaMetrics/lib/logger/logger.go:125
github.com/VictoriaMetrics/VictoriaMetrics/lib/storage.(*inmemoryPart).InitFromRows(0xc7ccf0,
 {0x0, 0x0, 0x0})

/<>/_build/src/github.com/VictoriaMetrics/VictoriaMetrics/lib/storage/inmemory_part.go:37
 +0x5e
github.com/VictoriaMetrics/VictoriaMetrics/lib/storage.newTestBlockStreamReader(0xca6150?,
 {0x0, 0x0, 0x0})

/<>/_build/src/github.com/VictoriaMetrics/VictoriaMetrics/lib/storage/block_stream_reader_test.go:151
 +0x48
github.com/VictoriaMetrics/VictoriaMetrics/lib/storage.TestMergeForciblyStop(0xc004101380)

/<>/_build/src/github.com/VictoriaMetrics/VictoriaMetrics/lib/storage/merge_test.go:358
 +0xce
testing.tRunner(0xc004101380, 0x7e12e8)
/usr/lib/go-1.20/src/testing/testing.go:1576 +0x10b
created by testing.(*T).Run
/usr/lib/go-1.20/src/testing/testing.go:1629 +0x3ea
FAILgithub.com/VictoriaMetrics/VictoriaMetrics/lib/storage  10.215s

Cheers
-- 
Sebastian Ramacher

Bug#1043117: rust-zram-generator: FTBFS

[Sebastian Ramacher]

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

Bug#1041537: marked as done (python3 platlib points again to /usr/local)

[Debian Bug Tracking System]

Your message dated Sun, 6 Aug 2023 11:00:15 +0200
with message-id <20230806090015.mtjfkfc3ialrs...@enricozini.org>
and subject line Re: Bug#1041537: python3 platlib points again to /usr/local
has caused the Debian Bug report #1041537,
regarding python3 platlib points again to /usr/local
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.)


-- 
1041537: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041537
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: meson
Version: 1.2.0-1
Severity: serious

Hello,

Thank you for maintaining Meson!

At first glance it looks like there is a regression of
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026312

On stable:

   $ cat meson.build
   project('test', 'cpp', version: '3.36', license : 'GPL-2.0-or-later')
   
   pymod = import('python')
   python3 = pymod.find_installation('python3', required: false)
   message('PLATLIB', python3.get_path('platlib'))
   
   $ meson setup /tmp/zz
   The Meson build system
   Version: 1.0.1
   Source dir: [...]
   Build dir: /tmp/zz
   Build type: native build
   Project name: test
   Project version: 3.36
   C++ compiler for the host machine: ccache c++ (gcc 12.2.0 "c++ (Debian 
12.2.0-14) 12.2.0")
   C++ linker for the host machine: c++ ld.bfd 2.40
   Host machine cpu family: x86_64
   Host machine cpu: x86_64
   Program python3 found: YES (/usr/bin/python3)
   Message: PLATLIB /usr/lib/python3/dist-packages


On sid:

   $ cat meson.build
   project('test', 'cpp', version: '3.36', license : 'GPL-2.0-or-later')
   
   pymod = import('python')
   python3 = pymod.find_installation('python3', required: false)
   message('PLATLIB', python3.get_path('platlib'))
   
   $ meson setup /tmp/zz
   The Meson build system
   Version: 1.2.0
   Source dir: [...]
   Build dir: /tmp/zz
   Build type: native build
   Project name: test
   Project version: 3.36
   C++ compiler for the host machine: c++ (gcc 13.1.0 "c++ (Debian 13.1.0-8) 
13.1.0")
   C++ linker for the host machine: c++ ld.bfd 2.40.90.20230714
   Host machine cpu family: x86_64
   Host machine cpu: x86_64
   Program python3 found: YES (/usr/bin/python3)
   Message: PLATLIB /usr/local/lib/python3.11/dist-packages


This is affecting wreport, and I guess the same list of packages as
#1026312


Enrico


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

Kernel: Linux 6.1.0-9-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages meson depends on:
ii  ninja-build1.11.1-1
ii  python33.11.4-5
ii  python3-pkg-resources  68.0.0-1
ii  python3-setuptools 68.0.0-1

Versions of packages meson recommends:
ii  dpkg-dev  1.21.22

meson suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
On Thu, Aug 03, 2023 at 12:34:45PM +0300, Jussi Pakkanen wrote:

> Based on that thread I'd say that this is not a bug in Meson at all.
> Can I just close it or should it be reassigned to some other package
> so it is not forgotten?

I agree that it can be closed (closing it), especially since the proper
fix for this issue seems to have landed in dh-python in sid:
https://lists.debian.org/debian-devel/2023/08/msg00017.html

Thank you!

Enrico

-- 
GPG key: 4096R/634F4BD1E7AD5568 2009-05-08 Enrico Zini --- End Message ---

Bug#1043113: mu-cade: this package should be rebuilt against GCC-13

[Alexandre Detiste]

Package: mu-cade
Version: 0.11.dfsg1-13
Severity: serious
Justification: GCC-12 to be removed soon

Hi,

mu-cade depends against deprecated GCC-12 runtime,
it should be rebuilt against GCC-13.

Greetings,


# LANG=C apt purge gcc-12-base
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be REMOVED:
  gcc-12-base* libgphobos3* mu-cade*
0 upgraded, 0 newly installed, 3 to remove and 3 not upgraded.
After this operation, 12.6 MB disk space will be freed.
Do you want to continue? [Y/n]



-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (501, 'testing'), (450, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.4.0-1-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE:fr
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages mu-cade depends on:
ii  libbulletml0v5  0.0.6-7
ii  libc6   2.37-6
ii  libgcc-s1   13.2.0-1
ii  libgl1  1.6.0-1
ii  libglu1-mesa [libglu1]  9.0.2-1.1
ii  libgphobos3 12.3.0-6
ii  libode8 2:0.16.2-1
ii  libsdl-mixer1.2 1.2.12-17+b3
ii  libsdl1.2debian 1.2.64-5
ii  mu-cade-data0.11.dfsg1-13

mu-cade recommends no packages.

mu-cade suggests no packages.

-- no debconf information

Processed: bug 1043048 is forwarded to https://github.com/xianyi/OpenBLAS/issues/4181

[Debian Bug Tracking System]

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

> forwarded 1043048 https://github.com/xianyi/OpenBLAS/issues/4181
Bug #1043048 [libopenblas0-pthread] openblas: gives wrong results on mips64el, 
ignores test failures
Set Bug forwarded-to-address to 
'https://github.com/xianyi/OpenBLAS/issues/4181'.
> thanks
Stopping processing here.

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

Processed (with 1 error): Re: Bug#1043048: openblas: gives wrong results on mips64el, ignores test failures

[Debian Bug Tracking System]

Processing control commands:

> found -1 0.3.22+ds-1
Bug #1043048 [libopenblas0-pthread] openblas: gives wrong results on mips64el, 
ignores test failures
Marked as found in versions openblas/0.3.22+ds-1.
> forwarded -1 https://github.com/xianyi/OpenBLAS/issues/4181
Unknown command or malformed arguments to command.


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

Bug#1043048: openblas: gives wrong results on mips64el, ignores test failures

[Sébastien Villemot]

Control: found -1 0.3.22+ds-1
Control: forwarded -1 https://github.com/xianyi/OpenBLAS/issues/4181

Le samedi 05 août 2023 à 13:24 +0100, Rebecca N. Palmer a écrit :
> Control: tags -1 upstream
> 
> Upstream CI's mips64 qemu test has what look like the same FATAL ERRORs, 
> in MIPS64_GENERIC but not SICORTEX, but is still listed as passing.

Thanks. Forwarded upstream.

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  https://sebastien.villemot.name
⠈⠳⣄  https://www.debian.org




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

Processed: tagging 1043107

[Debian Bug Tracking System]

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

> tags 1043107 + trixie sid
Bug #1043107 [src:salmon] salmon FTBFS with gcc 13
Added tag(s) sid and trixie.
> thanks
Stopping processing here.

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

Bug#1042911: Breaks Emacs 29.1 upgrade: muse-split.el:41:2: Error: Cannot open load file: No such file or directory, assoc

[Manphiz]

Nicholas D Steeves  writes:

> Hi,
>
> Reply follows inline.  Can we move this discussion to #1016558 to not
> bother Axel with our discussion?
>
> Manphiz  writes:
>
>> Nicholas D Steeves  writes:
> Nicholas D Steeves  writes:
>
>> Thanks!  Though I'm not really a user of muse-el, I'd like to keep it in
>> a good shape as an exercise as an Emacs addon maintainer.  It looks like
>> there is not too much work thanks to Elisp being a fairly stable
>> language :)
>
> That's fine, thank you once again for adopting it, and yes, generally
> everything is ok :)
>
 [1] https://salsa.debian.org/emacsen-team/muse-el/-/merge_requests/3
>>>
>> Thanks for the tips!  I checked the Debian Policy Upgrading Checklist[1]
>> and agreed with Debian Janitor on the "no changes are needed" bit.  And
>> to avoid having to wait for the bot to do the rebase I've manually
>> resolved the conflicts and rebased my MR on top of it as well.
>>
>
> You're welcome, and good call.
>
>>> Let me know when your done, and we can talk about the next steps.
>>
>> Now all MRs are merged.  Please advise the next steps.  Thanks!
>>
>
> Wonderful!  I also see you have a GPG key now.  Have you generated
> revocations certificates yet?
>
>   https://wiki.debian.org/Keysigning#Step_2:_Generate_a_revocation_certificate

Now I have one.  Thanks for the tip!

>
> Next, where can I find your key?

I have previously uploaded my GPG key to pgp.mit.edu[1].

> I'm assuming that you're committed to
> maintaining this identity for the foreseeable future, and that you'd
> like to build reputation for future involvement in Debian.  It's not
> required at the stage you're at, but it's recommended.
>
>   https://wiki.debian.org/Keysigning#Step_3:_Make_your_public_key_public

Please advise if https://keyserver.ubuntu.com is still recommended for
prospective DMs.

>
> The subkey that I was able to download didn't include any identities.
>
> Other than that, this package isn't quite ready to upload, because there
> are three unaddressed lintian warnings.
>
>   https://wiki.debian.org/Lintian

I have a few more commits[2] that should have fixed most of the lintian
warnings.  There is another INFO level warning:

I: muse-el source: patch-not-forwarded-upstream 
[debian/patches/0005-convert-a-muse-init.el-example-to-UTF-8.patch]

I wonder whether you would also like to forward this patch upstream.

The rest warnings/infos are taken care of.  PTAL.

>
> Best,
> Nicholas
>


[1] http://pgp.mit.edu/pks/lookup?op=get&search=0x2DE965ED63825C93
[2] https://salsa.debian.org/emacsen-team/muse-el/-/commits/master
-- 
Manphiz


signature.asc
Description: PGP signature

Bug#1043107: salmon FTBFS with gcc 13

[Adrian Bunk]

Source: salmon
Version: 1.10.1+ds1-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=salmon&ver=1.10.1%2Bds1-1%2Bb2

...
In file included from /<>/src/VersionChecker.cpp:2:
/<>/include/SalmonConfig.hpp:32:11: error: ‘uint32_t’ does not 
name a type
   32 | constexpr uint32_t indexVersion = 5;
  |   ^~~~
/<>/include/SalmonConfig.hpp:1:1: note: ‘uint32_t’ is defined in 
header ‘’; did you forget to ‘#include ’?
  +++ |+#include 
...

Bug#1032557: marked as done (libvcflib breaks ABI without SONAME bump)

[Debian Bug Tracking System]

Your message dated Sun, 06 Aug 2023 08:10:11 +
with message-id 
and subject line Bug#1032557: fixed in libvcflib 1.0.9+dfsg1-1
has caused the Debian Bug report #1032557,
regarding libvcflib breaks ABI without SONAME bump
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.)


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

Source: libvcflib, freebayes
Control: found -1 libvcflib/1.0.9+dfsg-1
Control: found -1 freebayes/1.3.6-2
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

With a recent upload of libvcflib the autopkgtest of freebayes fails in 
testing when that autopkgtest is run with the binary packages of 
libvcflib from unstable. It passes when run with only packages from 
testing. In tabular form:


   passfail
libvcflib  from testing1.0.9+dfsg-1
freebayes  from testing1.3.6-2
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 libvcflib to 
testing [1]. Due to the nature of this issue, I filed this bug report 
against both packages. Can you please investigate the situation and 
reassign the bug to the right package?


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=libvcflib

https://ci.debian.net/data/autopkgtest/testing/amd64/f/freebayes/32031881/log.gz

.:
README.test_data
bash-tap
freebayes-env.yaml
performance
pipeline.sh
regression
runner.sh
snakemake-freebayes-parallel.smk
splice
t
targets.bed
test-simple-bash
test.alt
test.bam
test.bam.bai
test.bed
test.ref
test.ref.fai
test.vcf
tiny

./bash-tap:

./performance:
benchmark.md

./regression:
NA12878.chr22.tiny.vcf
README.md

./splice:
1:883884-887618.bam
1:883884-887618.bam.bai
1:883884-887618.fa
1:883884-887618.fa.fai

./t:
00_region_and_target_handling.t
01_call_variants.t
01b_call_variants.t
02_multi_bam.t
03_reference_bases.t

./test-simple-bash:

./tiny:
1read.bam
1read.bam.bai
NA12878.chr22.tiny.bam
NA12878.chr22.tiny.bam.bai
NA12878.chr22.tiny.cram
NA12878.chr22.tiny.giab.vcf
NA12878.chr22.tiny.hla.bam
NA12878.chr22.tiny.hla.bam.bai
hla.fa
hla.fa.fai
hla.vcf.gz
hla.vcf.gz.tbi
q with spaces.fa
q with spaces.fa.fai
q with spaces.regions
q.fa
q.fa.fai
q.regions
q.vcf.gz
q.vcf.gz.tbi
q_spiked.vcf.gz
q_spiked.vcf.gz.tbi
Test 1
Passed

Test 2
Passed

Test 3
Passed

Test 4
Passed

Test 5
Passed

Test 6
Passed

Test 7
Passed

Test 8
Error: signal 11:
freebayes(+0xa355a)[0x55743c9a055a]
/lib/x86_64-linux-gnu/libc.so.6(+0x3bf90)[0x7fc692924f90]
/lib/x86_64-linux-gnu/libvcflib.so.1(_ZN6vcfliblsERSoRNS_7VariantE+0xfa0)[0x7fc692e883e0]
freebayes(+0x1247b)[0x55743c90f47b]
/lib/x86_64-linux-gnu/libc.so.6(+0x2718a)[0x7fc69291018a]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x85)[0x7fc692910245]
freebayes(+0x150d1)[0x55743c9120d1]
autopkgtest [13:13:47]: test run-unit-test



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: libvcflib
Source-Version: 1.0.9+dfsg1-1
Done: Andreas Tille 

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

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

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated libvcflib 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: Sun, 23 Jul 2023 10:42:25 +0200
Source: libvcflib
Binary: libvcflib-dev libvcflib-tools libvcflib-tools-dbgsym libvcflib2 
libvcflib2-dbgsym
Architecture: source amd64
Version: 1.0.9+dfsg1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 libvcflib-dev - C++ library for parsing and manipulating VCF files 
(development)
 libvcflib-tools - C++ l