Processed: severity of 1013903 is serious

[Debian Bug Tracking System]

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

> severity 1013903 serious
Bug #1013903 [src:sight] Fails to build with new opencv 4.6.0
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#1013988: marked as done (node-blob: FTBFS with nodejs 18.4.0)

[Debian Bug Tracking System]

Your message dated Sat, 02 Jul 2022 05:33:46 +
with message-id 
and subject line Bug#1013988: fixed in node-blob 0.0.4-4
has caused the Debian Bug report #1013988,
regarding node-blob: FTBFS with nodejs 18.4.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.)


-- 
1013988: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013988
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-blob
Version: 0.0.4-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source

node >= 18 exports Blob already,
making node-blob fail.

I suggest node-blob should be removed,
it is a leaf package without reverse build-deps.


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

Kernel: Linux 5.18.0-2-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: node-blob
Source-Version: 0.0.4-4
Done: Yadd 

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

Debian distribution maintenance software
pp.
Yadd  (supplier of updated node-blob package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 02 Jul 2022 07:20:04 +0200
Source: node-blob
Built-For-Profiles: nocheck
Architecture: source
Version: 0.0.4-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Yadd 
Closes: 1013988
Changes:
 node-blob (0.0.4-4) unstable; urgency=medium
 .
   * Team upload
   * Declare compliance with policy 4.6.1
   * Fix test for Node.js >= 18 (Closes: #1013988)
Checksums-Sha1: 
 a4c049296027785ef833b876d648cf9c452f5a6d 2020 node-blob_0.0.4-4.dsc
 b6b613fee24776446ea95c05ba779042467d3bcb 3356 node-blob_0.0.4-4.debian.tar.xz
Checksums-Sha256: 
 abcedd4fe597de1475188b37eeaaeab54808ee6b30974defb6983571dcb45739 2020 
node-blob_0.0.4-4.dsc
 43b839fba0bf3074fef84f97b24c01967af9587fc5df6d6bd031a2575d594220 3356 
node-blob_0.0.4-4.debian.tar.xz
Files: 
 0fdf75bdfa7183ef38aef81f8a6c8230 2020 javascript optional node-blob_0.0.4-4.dsc
 3c923d9ef8a8abe9b7541fe2643ae46e 3356 javascript optional 
node-blob_0.0.4-4.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmK/1b4ACgkQ9tdMp8mZ
7ukDqQ/7B3SCODZ+m4UilM0tJF11L48QmjOOK8cjFqg+ZqEuAjmHez51VDcI4TS9
JkK4XMn99Q29ESUZ5WrkRGpZ7ZEAUmLFeVOTe0Ibb9MKoI958Zs3Wl7itZxV05Mb
U5mx+nKGF6RjkyWivUoSK7pl5G0wffOp/rpCB44IH+ZswDmaMPCBbOVlD0vo9Knt
KXgNKpEa+Jxybfg/0sC5pxNS8UGl71rgVzSfFAg5oaqMQO0KtPxz2fL76tMSeX6x
WpXv6rzsLCpKClD/7zJlsLhFgaQEc0EdRvHw3ZRJvhRMh4lTgBzyWw4vgyX6pxXn
gNxKflB1noGuZDde1NK4mDPREqq2c0amTBFADILdnGZ96JWVHhPFUHIYJgMOvnp/
mT8S5brrc/07/8cbdvXzK1ttn5f+RRIkHhlIgT3+lpmWAkNW/K1IG0tnAKwbv9bP
XBzxCr4eQnXe/YDP3r6e/gnUeEMBGm5xA3kNRguYaV/vJeNh/6UDSOskBm8wv/b0
1nobz8W7slhkp9Vu+3VkknBtjzw8GkgirEzJiOy7Pi75oesVgOZ32jK8j1Gk0SSe
YNK1uERmEA/L7vBvH/ECFWf4yKCV9U2YjCH9jpcwWPB2oxPCUMIxjOpRISMLCZRN
sCyClMs68i4tBGJ9yLo1H4Psq3tO136psQp+sN0rpItNhoCuDxY=
=F9W3
-END PGP SIGNATURE End Message ---

Bug#1011712: olm: diff for NMU version 3.2.11~dfsg-1.1

[Evangelos Ribeiro Tzaras]

Dear maintainer,

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

This is a second version, because I forgot to remove the autopkgtest suite,
which depends on the removed libjs-olm.

Sorry for any confusion this may have caused.

Regards.

diff -Nru olm-3.2.11~dfsg/debian/changelog olm-3.2.11~dfsg/debian/changelog
--- olm-3.2.11~dfsg/debian/changelog	2022-04-16 10:37:50.0 +0200
+++ olm-3.2.11~dfsg/debian/changelog	2022-07-02 02:57:25.0 +0200
@@ -1,3 +1,11 @@
+olm (3.2.11~dfsg-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Remove javascript bindings
+Closes: #1011712 (thanks Lucas Nussbaum)
+
+ -- Evangelos Ribeiro Tzaras   Sat, 02 Jul 2022 02:57:25 +0200
+
 olm (3.2.11~dfsg-1) unstable; urgency=medium
 
   [ upstream ]
diff -Nru olm-3.2.11~dfsg/debian/tests/control olm-3.2.11~dfsg/debian/tests/control
--- olm-3.2.11~dfsg/debian/tests/control	2022-04-16 10:37:50.0 +0200
+++ olm-3.2.11~dfsg/debian/tests/control	1970-01-01 01:00:00.0 +0100
@@ -1,30 +0,0 @@
-Test-Command:
- sed -i -e 's,\.\./olm,@matrix-org/olm,' javascript/test/*.spec.js
- && cd javascript && jasmine --config=test/jasmine.json
-Depends:
- node-jasmine,
- node-matrix-org-olm,
-
-Test-Command: node -e "
- const domino = require('domino');
- const window = domino.createWindow('');
- const document = window.document;
- require('/usr/share/javascript/olm/olm');
- require('/usr/share/javascript/olm/olm.min');
- require('/usr/share/javascript/olm/olm_legacy');
- require('/usr/share/javascript/olm/olm_legacy.min');
- "
-Depends:
- libjs-olm,
- node-domino,
- nodejs,
-Restrictions: superficial
-
-Test-Command:
- cd /usr/share/javascript &&
- eslint --no-eslintrc --format tap --env browser  --parser-options '{ "ecmaVersion": 2015 }' olm/*.js
-Depends:
- eslint,
- libjs-olm,
- node-js-yaml,
-Restrictions: superficial

Bug#1011712: olm: diff for NMU version 3.2.11~dfsg-1.1

[Evangelos Ribeiro Tzaras]

Control: tags 1011712 + patch
Control: tags 1011712 + pending

Dear maintainer,

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

Regards.

diff -Nru olm-3.2.11~dfsg/debian/changelog olm-3.2.11~dfsg/debian/changelog
--- olm-3.2.11~dfsg/debian/changelog	2022-04-16 10:37:50.0 +0200
+++ olm-3.2.11~dfsg/debian/changelog	2022-07-02 02:57:25.0 +0200
@@ -1,3 +1,11 @@
+olm (3.2.11~dfsg-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Remove javascript bindings
+Closes: #1011712 (thanks Lucas Nussbaum)
+
+ -- Evangelos Ribeiro Tzaras   Sat, 02 Jul 2022 02:57:25 +0200
+
 olm (3.2.11~dfsg-1) unstable; urgency=medium
 
   [ upstream ]

Processed: olm: diff for NMU version 3.2.11~dfsg-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 1011712 + patch
Bug #1011712 [src:olm] olm: FTBFS: unsatisfiable build-dependency: binaryen (< 
105+) but 106-1 is to be installed
Added tag(s) patch.
> tags 1011712 + pending
Bug #1011712 [src:olm] olm: FTBFS: unsatisfiable build-dependency: binaryen (< 
105+) but 106-1 is to be installed
Added tag(s) pending.

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

Bug#1011712: olm: FTBFS: unsatisfiable build-dependency: binaryen (< 105+) but 106-1 is to be installed

[Evangelos Ribeiro Tzaras]

Hi,

On Sun, 26 Jun 2022 10:18:13 +0200 Hubert Chathi  wrote:
> On Sat, 25 Jun 2022 00:49:15 +0200, Evangelos Ribeiro Tzaras
 said:
> 
> [...]
> 
> > - Drop the javascript bindings for olm (libjs-olm). The only reverse
> > dependency of libjs-olm is libjs-matrix-sdk which itself has no
> > reverse dependencies.
> 
> FWIW, libjs-matrix-js-sdk upstream is looking into switching to the new
> rust implementation of olm, so some future version may stop using
> libjs-olm anyways.  But I'm not sure of the timeline for that.

Good to know :)

> 
> Aside from that, I'd like to look into updating emscripten somehow, but
> I'm currently on VAC so I won't be able to do it for a little while.  So
> in the mean time, I don't have any objection to someone doing something
> to resolve the situation temporarily.

Alright, nmudiff following shortly (which removes the javascript bindings).


-- 
Cheers,

Evangelos
PGP: B938 6554 B7DD 266B CB8E 29A9 90F0 C9B1 8A6B 4A19

Bug#1004788: marked as done (audacious-plugins: FTBFS with ffmpeg 5.0)

[Debian Bug Tracking System]

Your message dated Sat, 02 Jul 2022 00:20:49 +
with message-id 
and subject line Bug#1004788: fixed in audacious-plugins 4.1-3
has caused the Debian Bug report #1004788,
regarding audacious-plugins: FTBFS with ffmpeg 5.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.)


-- 
1004788: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004788
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: audacious-plugins
Version: 4.1-2
Severity: important
X-Debbugs-Cc: sramac...@debian.org
Tags: sid bookworm ftbfs
Usertags: ffmpeg5.0

audacious-plugins FTBFS with ffmpeg 5.0 in experimental:

ffaudio-core.cc: In constructor ‘ScopedPacket::ScopedPacket()’:
ffaudio-core.cc:103:26: warning: ‘void av_init_packet(AVPacket*)’ is deprecated 
[-Wdeprecated-declarations]
  103 | { av_init_packet (this); }
  |   ~~~^~
In file included from /usr/include/x86_64-linux-gnu/libavformat/avformat.h:316,
 from ffaudio-stdinc.h:26,
 from ffaudio-core.cc:24:
/usr/include/x86_64-linux-gnu/libavcodec/packet.h:506:6: note: declared here
  506 | void av_init_packet(AVPacket *pkt);
  |  ^~
ffaudio-core.cc: In function ‘AVInputFormat* get_format_by_content(const char*, 
VFSFile&)’:
ffaudio-core.cc:291:36: error: invalid conversion from ‘const AVInputFormat*’ 
to ‘AVInputFormat*’ [-fpermissive]
  291 | f = av_probe_input_format2 (& d, true, & score);
  | ~~~^~~~
  ||
  |const AVInputFormat*
ffaudio-core.cc: In function ‘bool find_codec(AVFormatContext*, CodecInfo*)’:
ffaudio-core.cc:364:52: error: invalid conversion from ‘const AVCodec*’ to 
‘AVCodec*’ [-fpermissive]
  364 | AVCodec * codec = avcodec_find_decoder 
(stream->codecpar->codec_id);
  |   
~^~~~
  ||
  |const AVCodec*
ffaudio-core.cc: In member function ‘virtual bool FFaudio::play(const char*, 
VFSFile&)’:
ffaudio-core.cc:572:28: warning: ‘void av_init_packet(AVPacket*)’ is deprecated 
[-Wdeprecated-declarations]
  572 | av_init_packet (& tmp);
  | ~~~^~~
In file included from /usr/include/x86_64-linux-gnu/libavformat/avformat.h:316,
 from ffaudio-stdinc.h:26,
 from ffaudio-core.cc:24:
/usr/include/x86_64-linux-gnu/libavcodec/packet.h:506:6: note: declared here
  506 | void av_init_packet(AVPacket *pkt);
  |  ^~
Failed to compile ffaudio-core.cc (plugin)!
make[6]: *** [../../buildsys.mk:435: ffaudio-core.plugin.o] Error 1

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: audacious-plugins
Source-Version: 4.1-3
Done: Mateusz Łukasik 

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

Debian distribution maintenance software
pp.
Mateusz Łukasik  (supplier of updated audacious-plugins 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 25 Jun 2022 20:47:30 +0200
Source: audacious-plugins
Architecture: source
Version: 4.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Mateusz Łukasik 
Closes: 1004788
Changes:
 audacious-plugins (4.1-3) unstable; urgency=medium
 .
   * Add upstream patch for fix FTBFS with ffmpeg 5.0. (Closes: #1004788)
Checksums-Sha1:
 f17153dc95bd338f709679cce89e4d81232b9ee1 2976 audacious-plugins_4.1-3.dsc
 13eadfd351c1d7a3b88f7fdbce444a920c99515b 52068 
audacious-plugins_4.1-3.debian.tar.xz
 36f408a65643fb3acb8c55159bdb0b5761a5f567 10089 
audacious-plugins_4.1-3_source.buildinfo
Checksums-Sha256:
 d298de09346429d494b5a48eeb998514ce9818a96b2cb50f99c5c5f204a6d60c 2976 
audacious-plugins_4.1-3.dsc
 

Bug#1014198: deepin-movie: binary packages still depend on old libav* packages after rebuild.

[Peter Michael Green]

Package: deepin-movie
Version: 5.7.15-3
Severity: serious

The deepin-movie-reborn source package was recently binnmu'd for the 
ffmpeg transtion,
unfortunately though the resulting binary packages still depend on the 
old libav* packages.

Bug#1005508: marked as done (hitori: FTBFS with Meson 0.61: ../data/meson.build:3:0: ERROR: Function does not take positional arguments)

[Debian Bug Tracking System]

Your message dated Fri, 01 Jul 2022 21:05:53 +
with message-id 
and subject line Bug#1005508: fixed in hitori 3.38.4-1
has caused the Debian Bug report #1005508,
regarding hitori: FTBFS with Meson 0.61: ../data/meson.build:3:0: ERROR: 
Function does not take positional arguments
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.)


-- 
1005508: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005508
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hitori
Version: 3.38.3-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220212 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_configure -- \
>   --bindir=games
>   cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. 
> --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc 
> --localstatedir=/var --libdir=lib/x86_64-linux-gnu --bindir=games
> The Meson build system
> Version: 0.61.1
> Source dir: /<>
> Build dir: /<>/obj-x86_64-linux-gnu
> Build type: native build
> Project name: hitori
> Project version: 3.38.3
> C compiler for the host machine: cc (gcc 11.2.0 "cc (Debian 11.2.0-16) 
> 11.2.0")
> C linker for the host machine: cc ld.bfd 2.38
> Host machine cpu family: x86_64
> Host machine cpu: x86_64
> Found pkg-config: /usr/bin/pkg-config (0.29.2)
> Run-time dependency glib-2.0 found: YES 2.70.3
> Run-time dependency gio-2.0 found: YES 2.70.3
> Run-time dependency gtk+-3.0 found: YES 3.24.31
> Run-time dependency gmodule-2.0 found: YES 2.70.3
> Run-time dependency cairo found: YES 1.16.0
> Compiler for C supports arguments -fno-strict-aliasing: YES 
> Compiler for C supports arguments -fstack-protector-strong: YES 
> Compiler for C supports arguments -Waggregate-return: YES 
> Compiler for C supports arguments -Wall: YES 
> Compiler for C supports arguments -Wunused: YES 
> Compiler for C supports arguments -Warray-bounds: YES 
> Compiler for C supports arguments -Wcast-align: YES 
> Compiler for C supports arguments -Wclobbered: YES 
> Compiler for C supports arguments -Wno-declaration-after-statement: YES 
> Compiler for C supports arguments -Wduplicated-branches: YES 
> Compiler for C supports arguments -Wduplicated-cond: YES 
> Compiler for C supports arguments -Wempty-body: YES 
> Compiler for C supports arguments -Wformat=2: YES 
> Compiler for C supports arguments -Wformat-nonliteral: YES 
> Compiler for C supports arguments -Wformat-security: YES 
> Compiler for C supports arguments -Wformat-signedness: YES 
> Compiler for C supports arguments -Wignored-qualifiers: YES 
> Compiler for C supports arguments -Wimplicit-function-declaration: YES 
> Compiler for C supports arguments -Wincompatible-pointer-types: YES 
> Compiler for C supports arguments 
> -Wincompatible-pointer-types-discards-qualifiers: NO 
> Compiler for C supports arguments -Winit-self: YES 
> Compiler for C supports arguments -Wint-conversion: YES 
> Compiler for C supports arguments -Wlogical-op: YES 
> Compiler for C supports arguments -Wmisleading-indentation: YES 
> Compiler for C supports arguments -Wmissing-declarations: YES 
> Compiler for C supports arguments -Wmissing-format-attribute: YES 
> Compiler for C supports arguments -Wmissing-include-dirs: YES 
> Compiler for C supports arguments -Wmissing-noreturn: YES 
> Compiler for C supports arguments -Wmissing-parameter-type: YES 
> Compiler for C supports arguments -Wmissing-prototypes: YES 
> Compiler for C supports arguments -Wnested-externs: YES 
> Compiler for C supports arguments -Wno-error=cpp: YES 
> Compiler for C supports arguments -Wno-discarded-qualifiers: YES 
> Compiler for C supports arguments -Wno-missing-field-initializers: YES 
> Compiler for C supports arguments -Wno-suggest-attribute=format: YES 
> Compiler for C supports arguments -Wno-unused-parameter: YES 
> Compiler for C supports arguments -Wnull-dereference: YES 
> Compiler for C supports arguments -Wold-style-definition: YES 
> Compiler for C supports arguments -Woverflow: YES 
> Compiler for C supports arguments -Woverride-init: YES 
> Compiler for C supports arguments -Wparentheses: YES 
> Compiler for C supports arguments -Wpointer-arith: YES 
> Compiler for C supports arguments -Wredundant-decls: YES 
> Compiler for C supports arguments -Wreturn-type: YES 
> Compiler for C supports arguments -Wshadow: YES 
> Compiler for C supports arguments -Wsign-compare: YES 
> Compiler for C supports arguments 

Bug#832116: music assets

[Matt Barry]

Hello!

I am looking at the possibility of getting edgar updated and back into
the archive, which obviously involves this bug.

I don't desperately want to dredge up an entirely old discussion, so
I'll just document my starting point here.  My working assumption is 
that existing practice reflects more or less the correct interpretation
of the relevant documents; there are still plenty of games in the
archive with unsourced ogg files.  Fwiw, [0] is roughly my
interpretation; however, the disagreement over this has been going on
for many years; if anyone feels it needs to be relitigated, my humble
suggestion is that you migrate that discussion to one of the mailing
lists.  (You may assume I am subscribed.)

With regard to the actual bug report:

- medcine.ogg is correctly attributed upstream now
- I have reached out to Johan Brodd, requesting a) source, or b) dual
licensing options.. will give it a bit to see if he responds.
- If we cannot reach the author, I believe the next step is to approach
upstream; they are redistributing the file incorrectly as well.

If I have misunderstood anything so far, kindly let me know; again,
larger questions of non-programmatic works really need a larger
audience than a bug report.

Cheers,
Matt

[0] https://lists.debian.org/debian-devel/2014/03/msg00301.html


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

Processed: Re: Bug#1004632: wxsvg: FTBFS with ffmpeg 5.0

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1004632 [src:wxsvg] wxsvg: FTBFS with ffmpeg 5.0
Added tag(s) patch.

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

Bug#1004632: wxsvg: FTBFS with ffmpeg 5.0

[Bastian Germann]

Control: tags -1 patch

Patch available at 
https://gitweb.gentoo.org/repo/gentoo.git/tree/media-libs/wxsvg/files/ffmpeg5.patch?id=d6fd9cfb26299c76be7483cac4451a226ab8e37f

Bug#1012741: modprobe: ERROR: could not insert 'crc_itu_t': Key was rejected by service

[Ben Hutchings]

On Sun, 2022-06-26 at 10:30 -0500, Daniel Lewart wrote:
> Ben, et al,
> 
> On Mon, 13 Jun 2022 18:23:18 +0200 Ben Hutchings  wrote:
> 
> > Since the truncated signatures are in the source packages, this is a
> > problem introduced by the code signing service and will need to be
> > fixed there.
> 
> Assuming that the code-signing service uses the kernel's scripts/sign-file
> and calls PKCS7_sign() ...
> 
> Which version of OpenSSL/libssl is used?

I don't know that; you would have to ask the FTP team.

> Are kernel build logs available for download or viewing?

All package build logs are available from ,
but the code signing step is separate.

Ben.

-- 
Ben Hutchings
Never put off till tomorrow what you can avoid all together.


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

Bug#1014189: marked as done (devhelp: can't launch DevHelp GUI)

[Debian Bug Tracking System]

Your message dated Fri, 1 Jul 2022 20:53:11 +0100
with message-id 
and subject line Re: Bug#1014189: devhelp: can't launch DevHelp GUI
has caused the Debian Bug report #1014189,
regarding devhelp: can't launch DevHelp GUI
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.)


-- 
1014189: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014189
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: devhelp
Version: 41.2-2
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: tmcconnell...@gmail.com

Dear Maintainer,

What led up to the situation?Attempt to launch Dev Help from Icon or via
command line.

What exactly did you do (or not do) that was effective (or ineffective)?Attempt
to use the program: Ineffective it fails.

What was the outcome of this action?From Icon nothing happened and program
fails to launch. typing devhelp in command line gives this:
devhelp

(devhelp:735030): devhelp-WARNING **: 12:46:14.787: The file
'file:///usr/share/gtk-doc/html/gtk-faq/gtk-faq.devhelp' uses the Devhelp index
file format version 1, which is deprecated. A future version of Devhelp may
remove the support for the format version 1. The index file should be ported to
the Devhelp index file format version 2.

(devhelp:735030): devhelp-WARNING **: 12:46:14.811: The file
'file:///usr/share/gtk-doc/html/gtk-tutorial/gtk-tutorial.devhelp' uses the
Devhelp index file format version 1, which is deprecated. A future version of
Devhelp may remove the support for the format version 1. The index file should
be ported to the Devhelp index file format version 2.

(devhelp:735030): devhelp-WARNING **: 12:46:14.839: The file
'file:///usr/share/gtk-doc/html/gtkglext/gtkglext.devhelp.gz' uses the Devhelp
index file format version 1, which is deprecated. A future version of Devhelp
may remove the support for the format version 1. The index file should be
ported to the Devhelp index file format version 2.

(devhelp:735030): devhelp-WARNING **: 12:46:15.306: The file
'file:///usr/share/devhelp/books/python3.10/python3.10.devhelp.gz' uses the
Devhelp index file format version 1, which is deprecated. A future version of
Devhelp may remove the support for the format version 1. The index file should
be ported to the Devhelp index file format version 2.
bwrap: Creating new namespace failed: No space left on device
 and still doesn't launch.

What outcome did you expect instead? To be able to use the program.



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

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

Versions of packages devhelp depends on:
ii  libc6 2.33-7
ii  libdevhelp-3-641.2-2
ii  libglib2.0-0  2.72.2-2
ii  libgtk-3-03.24.34-1
ii  libpango-1.0-01.50.7+ds-1
ii  libwebkit2gtk-4.0-37  2.36.3-1
ii  python3   3.10.4-1+b1

Versions of packages devhelp recommends:
ii  libglib2.0-doc   2.72.2-2
ii  libgtk-3-doc 3.24.34-1
ii  libpango1.0-doc  1.50.7+ds-1

devhelp suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
On Fri, 01 Jul 2022 at 13:08:19 -0500, Tim McConnell wrote:
> bwrap: Creating new namespace failed: No space left on device

This looks like the same root cause as #1014188. devhelp uses WebKitGTK,
which requires a system configuration in which bubblewrap works: see
/usr/share/doc/bubblewrap/README.Debian.gz for details.
In your case it seems that /proc/sys/user/max_user_namespaces is set to 0,
which prevents namespace-based sandboxing from working.

smcv--- End Message ---

Bug#1014115: uninstall does not properly remove enablement symlinks

[Michael Biebl]

Am 30.06.22 um 22:31 schrieb Luca Boccassi:

The problem is some files leftover, no? Just delete them in the
postinst or postrm?


My main motivation is to "stop the bleeding" as quickly as possible.

If we continue to create those broken state files, we'd have to keep 
those postinst/postrm cleanup routines for a possibly long time.


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1012510: marked as done (firejail: CVE-2022-31214: local root exploit reachable via --join logic)

[Debian Bug Tracking System]

Your message dated Fri, 01 Jul 2022 19:17:22 +
with message-id 
and subject line Bug#1012510: fixed in firejail 0.9.58.2-2+deb10u3
has caused the Debian Bug report #1012510,
regarding firejail: CVE-2022-31214: local root exploit reachable via --join 
logic
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.)


-- 
1012510: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012510
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: firejail
Version: 0.9.68-3
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for firejail.

CVE-2022-31214[0]:
| local root exploit reachable via --join logic

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2022-31214
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-31214
[1] https://www.openwall.com/lists/oss-security/2022/06/08/10
[2] 
https://github.com/netblue30/firejail/commit/27cde3d7d1e4e16d4190932347c7151dc2a84c50
[3] 
https://github.com/netblue30/firejail/commit/dab835e7a0eb287822016f5ae4e87f46e1d363e7
[4] 
https://github.com/netblue30/firejail/commit/1884ea22a90d225950d81c804f1771b42ae55f54

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: firejail
Source-Version: 0.9.58.2-2+deb10u3
Done: Reiner Herrmann 

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

Debian distribution maintenance software
pp.
Reiner Herrmann  (supplier of updated firejail package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 21 Jun 2022 19:54:44 +0200
Source: firejail
Architecture: source
Version: 0.9.58.2-2+deb10u3
Distribution: buster-security
Urgency: medium
Maintainer: Reiner Herrmann 
Changed-By: Reiner Herrmann 
Closes: 1012510
Changes:
 firejail (0.9.58.2-2+deb10u3) buster-security; urgency=medium
 .
   * Fix local root exploit reachable via --join logic. (CVE-2022-31214)
 (Closes: #1012510)
Checksums-Sha1:
 aa5f2238915eaadc77dbc515fbaa99f7cb06c57e 2521 firejail_0.9.58.2-2+deb10u3.dsc
 116a6bab8dd02f20c12d623aefffa260bc6ccf34 27444 
firejail_0.9.58.2-2+deb10u3.debian.tar.xz
 1ee64249ee5350e3d5ea26180ea2ca182c753d7d 5427 
firejail_0.9.58.2-2+deb10u3_source.buildinfo
Checksums-Sha256:
 056081684a07e1e128b862ad52718aefc20b1a6bb16babfbaf1d655fe8baae16 2521 
firejail_0.9.58.2-2+deb10u3.dsc
 f68b407eea33eefdf3a6b6d7f3e3b30c61b6c8c19de98143c7859177e9b89695 27444 
firejail_0.9.58.2-2+deb10u3.debian.tar.xz
 d061c59444df49b73c1e52996faae8d1f073e7456b2d726fe15ae4a8f55d6d94 5427 
firejail_0.9.58.2-2+deb10u3_source.buildinfo
Files:
 d0395323782e87b4501466f38e0a4cf6 2521 utils optional 
firejail_0.9.58.2-2+deb10u3.dsc
 5594bbd23576759061683b7ca8c548ce 27444 utils optional 
firejail_0.9.58.2-2+deb10u3.debian.tar.xz
 889fda865ea38c516815b8c9425b52c7 5427 utils optional 
firejail_0.9.58.2-2+deb10u3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEtuYvPRKsOElcDakFEMKTtsN8TjYFAmKy4kkACgkQEMKTtsN8
TjazeRAAlbarFTWYGFf63Ckfphd8NljGhb9DHcD75hWXRSKAn/JdZNj3guXdzRZG
yYbMDClcBW5fT68Rt9bNB9Pcm1uRCmtAbKPQJBXfT+hnwSOVgvOX4weVBvFvGGun
Qh6Q+0A/sff8+P73VvAR2Z6xJ83Eh+MaqGLW2uURyNmXuTjK9ynZJIpfEZUgHFeW
PP7ZeR6l/dIJtapzTqSv1Ni5eY818x2TnyJAPYpfF/ScOsNwTWPiSHVGuwSpb9Ai
65juD/fBG0DN13JJN5HBoL5lkVuTOuvJ28gRepLB+/wuQxlpcgee4foiLU8HLv6j
ekGt9DIdtmbde145ZMalOqoIMxxdMcYdY7O0GG6Mz8+Efgv0XIjeNPewTcm4bhi6
O15/IH7WvAR/+l4TAxc2AVM9cC5A5reyyA0lK2ioZNUa6iHJA0OwVhBPKj7WiEbJ
LZvp1IolrwM9RMytduZqxTOmUid84yWF49iBKTC/dRiBMBS5u9tVPEDEeCgtSR8B
es2dGqRT4TRL5W8ANGbxfJt8VfyZs44GbDwh0015GliHUqVTcSsE/EdOmBIlUQAX
fygoHR2OAjoVMzouaxlMoSZ7O3bu7ltRI/w9oTAEXQbBVFQaSYC98a44hLOXcJFK
iyIQJny1XeGXiwYRzveGq3C2qkoaXKIyH6PwgZZcCpMeDHg3mAo=
=YQce
-END PGP SIGNATURE End Message ---

Processed: reassign 1014077 to src:haskell-bimap, forcibly merging 1014081 1014077

[Debian Bug Tracking System]

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

> reassign 1014077 src:haskell-bimap
Bug #1014077 [src:haskell-bimap_] haskell-bimap_0.4.0-2_mips64el-buildd.changes 
REJECTED
Warning: Unknown package 'src:haskell-bimap_'
Bug reassigned from package 'src:haskell-bimap_' to 'src:haskell-bimap'.
No longer marked as found in versions haskell-bimap_/0.4.0-2.
Ignoring request to alter fixed versions of bug #1014077 to the same values 
previously set
> forcemerge 1014081 1014077
Bug #1014081 [src:haskell-bimap] haskell-bimap REJECTED: has 1 file(s) with a 
timestamp too far in the past
Bug #1014077 [src:haskell-bimap] haskell-bimap_0.4.0-2_mips64el-buildd.changes 
REJECTED
The source haskell-bimap and version 0.4.0-2 do not appear to match any binary 
packages
Marked as found in versions haskell-bimap/0.4.0-2.
Added tag(s) ftbfs.
Merged 1014077 1014081
> thanks
Stopping processing here.

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

Processed: pyranges ftbfs unreproducible, possibly caused by timeout

[Debian Bug Tracking System]

Processing control commands:

> tag -1 moreinfo
Bug #1013703 [src:pyranges] pyranges: FTBFS: pytest7 regression, py3.9 OK; 
py3.10 fails with Fatal Python error: Bus error
Added tag(s) moreinfo.

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

Processed (with 1 error): forcibly merging 1014081 1014077

[Debian Bug Tracking System]

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

> forcemerge 1014081 1014077
Bug #1014081 [src:haskell-bimap] haskell-bimap REJECTED: has 1 file(s) with a 
timestamp too far in the past
Unable to merge bugs because:
package of #1014077 is 'src:haskell-bimap_' not 'src:haskell-bimap'
Failed to forcibly merge 1014081: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Bug#1014189: devhelp: can't launch DevHelp GUI

[Tim McConnell]

Package: devhelp
Version: 41.2-2
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: tmcconnell...@gmail.com

Dear Maintainer,

What led up to the situation?Attempt to launch Dev Help from Icon or via
command line.

What exactly did you do (or not do) that was effective (or ineffective)?Attempt
to use the program: Ineffective it fails.

What was the outcome of this action?From Icon nothing happened and program
fails to launch. typing devhelp in command line gives this:
devhelp

(devhelp:735030): devhelp-WARNING **: 12:46:14.787: The file
'file:///usr/share/gtk-doc/html/gtk-faq/gtk-faq.devhelp' uses the Devhelp index
file format version 1, which is deprecated. A future version of Devhelp may
remove the support for the format version 1. The index file should be ported to
the Devhelp index file format version 2.

(devhelp:735030): devhelp-WARNING **: 12:46:14.811: The file
'file:///usr/share/gtk-doc/html/gtk-tutorial/gtk-tutorial.devhelp' uses the
Devhelp index file format version 1, which is deprecated. A future version of
Devhelp may remove the support for the format version 1. The index file should
be ported to the Devhelp index file format version 2.

(devhelp:735030): devhelp-WARNING **: 12:46:14.839: The file
'file:///usr/share/gtk-doc/html/gtkglext/gtkglext.devhelp.gz' uses the Devhelp
index file format version 1, which is deprecated. A future version of Devhelp
may remove the support for the format version 1. The index file should be
ported to the Devhelp index file format version 2.

(devhelp:735030): devhelp-WARNING **: 12:46:15.306: The file
'file:///usr/share/devhelp/books/python3.10/python3.10.devhelp.gz' uses the
Devhelp index file format version 1, which is deprecated. A future version of
Devhelp may remove the support for the format version 1. The index file should
be ported to the Devhelp index file format version 2.
bwrap: Creating new namespace failed: No space left on device
 and still doesn't launch.

What outcome did you expect instead? To be able to use the program.



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

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

Versions of packages devhelp depends on:
ii  libc6 2.33-7
ii  libdevhelp-3-641.2-2
ii  libglib2.0-0  2.72.2-2
ii  libgtk-3-03.24.34-1
ii  libpango-1.0-01.50.7+ds-1
ii  libwebkit2gtk-4.0-37  2.36.3-1
ii  python3   3.10.4-1+b1

Versions of packages devhelp recommends:
ii  libglib2.0-doc   2.72.2-2
ii  libgtk-3-doc 3.24.34-1
ii  libpango1.0-doc  1.50.7+ds-1

devhelp suggests no packages.

-- no debconf information

Bug#1013704: closing 1013704

[Timo Röhling]

close 1013704 1.5.26+ds-1
thanks

Hi,
I believe this bug has been fixed with the new upstream version.

Cheers
Timo

-- 
⢀⣴⠾⠻⢶⣦⠀   
╭────────────────────────────────────────────────────╮
⣾⠁⢠⠒⠀⣿⡁   │ Timo Röhling   
│
⢿⡄⠘⠷⠚⠋⠀   │ 9B03 EBB9 8300 DF97 C2B1  23BF CC8C 6BDD 1403 F4CA 
│
⠈⠳⣄⠀⠀⠀⠀   
╰────────────────────────────────────────────────────╯

Processed: closing 1013704

[Debian Bug Tracking System]

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

> close 1013704 1.5.26+ds-1
Bug #1013704 [src:pyglet] pyglet: FTBFS: pytest7 regression, py3.9 OK; py3.10 
fails
Marked as fixed in versions pyglet/1.5.26+ds-1.
Bug #1013704 [src:pyglet] pyglet: FTBFS: pytest7 regression, py3.9 OK; py3.10 
fails
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#945254: marked as done (py-libzfs: FTBFS against python3.8)

[Debian Bug Tracking System]

Your message dated Fri, 01 Jul 2022 17:50:07 +
with message-id 
and subject line Bug#945254: fixed in py-libzfs 0.0+git20220621.a99d1db-1
has caused the Debian Bug report #945254,
regarding py-libzfs: FTBFS against python3.8
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.)


-- 
945254: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945254
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: py-libzfs
Version: 0.0+git20191113.2991805-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source

py-libzfs FTBFS in sid since python3.8 was added to the list of python
versions to build against:

https://buildd.debian.org/status/package.php?p=py-libzfs=experimental


Andreas
--- End Message ---
--- Begin Message ---
Source: py-libzfs
Source-Version: 0.0+git20220621.a99d1db-1
Done: Boyuan Yang 

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

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated py-libzfs 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: Fri, 01 Jul 2022 13:31:10 -0400
Source: py-libzfs
Architecture: source
Version: 0.0+git20220621.a99d1db-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Boyuan Yang 
Closes: 945254
Changes:
 py-libzfs (0.0+git20220621.a99d1db-1) experimental; urgency=medium
 .
   * Team upload.
 .
   [ Ondřej Nový ]
   * d/control: Update Maintainer field with new Debian Python Team
 contact address.
   * d/control: Update Vcs-* fields with new Debian Python Team Salsa
 layout.
 .
   [ Boyuan Yang ]
   * debian/watch: Fix monitoring of upstream HEAD
   * New upstream version 0.0+git20220621.a99d1db. (Closes: #945254)
   * debian/control: Bump Standards-Version to 4.6.1.
   * debian/control: Update homepage address following upstream rename.
 .
   [ William Grzybowski ]
   * d/control: add missing python3-all-dev build dependency
Checksums-Sha1:
 1bbdf6144afc68cc7b9635111cf5dc233ec79def 2193 
py-libzfs_0.0+git20220621.a99d1db-1.dsc
 c36b55cb21d7594e332a1d1a04e7e23bc4eeec2d 72212 
py-libzfs_0.0+git20220621.a99d1db.orig.tar.xz
 ad24ec03a9a6481ffe3ee137c691c24596123d98 2680 
py-libzfs_0.0+git20220621.a99d1db-1.debian.tar.xz
 82ba1e0c7391bfe52b6e12ac3dcd5e6257e0d76f 7857 
py-libzfs_0.0+git20220621.a99d1db-1_amd64.buildinfo
Checksums-Sha256:
 12052b24dc340b3253d3840be31819c377307960142d7bb097c465c361963909 2193 
py-libzfs_0.0+git20220621.a99d1db-1.dsc
 33efb5873dfc8654d31d612931a86933d528fb022b0169234ba647592001f14e 72212 
py-libzfs_0.0+git20220621.a99d1db.orig.tar.xz
 2033078bef21d259b2e39e8b589e09a591542244f70f8e91f378999277708f79 2680 
py-libzfs_0.0+git20220621.a99d1db-1.debian.tar.xz
 392f462c6816f8cae1a46f085206890cc61524ff234c54deb55d3bb46ec39ee9 7857 
py-libzfs_0.0+git20220621.a99d1db-1_amd64.buildinfo
Files:
 bd8855bb7ae1f6f1efcee478c2255380 2193 contrib/python optional 
py-libzfs_0.0+git20220621.a99d1db-1.dsc
 f4b1fdc45d76f047c3911237ca5c11fb 72212 contrib/python optional 
py-libzfs_0.0+git20220621.a99d1db.orig.tar.xz
 5e280a9ccace142ed449a36f9e6bb8e0 2680 contrib/python optional 
py-libzfs_0.0+git20220621.a99d1db-1.debian.tar.xz
 10567567c98376cfe99f2b54ca9126bd 7857 contrib/python optional 
py-libzfs_0.0+git20220621.a99d1db-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmK/MLMACgkQwpPntGGC
Ws4QzxAArRyqgU3woF9dwoJx0zEIm9Zd4NGDZd+2EMLWOsHfmRYkALLNmgedzxY5
mERaiXxcpaeoGfp4v3fy7ShCd4gf80DUKbt1uJY9ZCdUpMX/zDepjtVLUD3dq7We
9+fDCjWkLrfpvOeHWD4BTy/fVnRaQVteSGdjFwgGwQ4Kd+Amt00TUXPDnQ7HjO9b
zBTrmihyKmJWI1FlbO4K7LnXT3IS/Ut/q2QMqZeZ04Brj18bou2eqMjnsh7R3hw7
VNJNoEgxHjRr9NBw0VGJ7YNr8/HcI3+koHySwSzkKKn+9saaJn33HiLrpQW5zZeC
4aDNjuT5I5bgMkJDQZKspJMDjbVceJ5gRQ/ia9BUtZPr9VIaiQCUzanOQoG3CofE
UxpnkT+Wsp727ib/9aOP13UB5PXV0PjqUsXl76sW44CCnRL/bDhgj7O5tTh4JXb5
6FmNhQh/cApyxpVJvPs4gES2rgi/oIsYnx2eTvBVK1LhJiKieGM4UqWkNpglHzKK
YsUkG3TgM6ZQiiabbqpYDSJSZdxJSf6CAbJwvvfGNu/mJJ94wCbG19lIeCdX/HAF
rzQSzKu9JuqabCBHiNONY4pH8qUwKhFsKv0DM0XbA675H2BaaciGfwZI8dvfvxc2

Bug#1014187: fruit: Binary file inside package

[Marcos Talau]

Package: fruit
Version: 2.1.dfsg-9
Severity: serious
Justification: Policy 2.1

Dear Maintainer,

The fruit package comes with a binary file named `book_small.bin'. This
binary file does not have a source code.

Discussion about this can be found on debian-legal [1].

[1] https://lists.debian.org/debian-legal/2022/06/threads.html#6


Best Regards,
mt

Bug#1006389: marked as done (libdigidoc: FTBFS with OpenSSL 3.0)

[Debian Bug Tracking System]

Your message dated Fri, 01 Jul 2022 17:35:24 +
with message-id 
and subject line Bug#1006389: fixed in libdigidoc 3.10.5-3
has caused the Debian Bug report #1006389,
regarding libdigidoc: 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.)


-- 
1006389: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006389
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libdigidoc
Version: 3.10.5-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:

| [ 76%] Building C object libdigidoc/CMakeFiles/digidoc.dir/DigiDocOCSP.c.o
| cd /<>/obj-x86_64-linux-gnu/libdigidoc && /usr/bin/cc 
-DBUILD_DATE=\"31.12.2020\" -DBUILD_VER=0 -DMAJOR_VER=3 -DMINOR_VER=10 
-DRELEASE_VER=5 -DVER_SUFFIX=\"\" -Ddigidoc_EXPORTS -I/<> 
-I/<>/obj-x86_64-linux-gnu -I/usr/include/libxml2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-fvisibility=hidden -MD -MT libdigidoc/CMakeFiles/digidoc.dir/DigiDocOCSP.c.o 
-MF CMakeFiles/digidoc.dir/DigiDocOCSP.c.o.d -o 
CMakeFiles/digidoc.dir/DigiDocOCSP.c.o -c 
/<>/libdigidoc/DigiDocOCSP.c
…
| In file included from /<>/libdigidoc/DigiDocOCSP.c:38:
| /<>/libdigidoc/DigiDocOCSP.c:983:37: error: 
‘OCSP_R_SERVER_RESPONSE_PARSE_ERROR’ undeclared (first use in this 
function); did you mean ‘OCSP_R_SERVER_READ_ERROR’?
|   983 | 
OCSPerr(OCSP_F_OCSP_SENDREQ_BIO,OCSP_R_SERVER_RESPONSE_PARSE_ERROR);
|   | ^~
| /<>/libdigidoc/DigiDocOCSP.c:983:37: note: each undeclared 
identifier is reported only once for each function it appears in
| /<>/libdigidoc/DigiDocOCSP.c:1022:37: error: 
‘OCSP_R_SERVER_RESPONSE_ERROR’ undeclared (first use in this function); did 
you mean ‘OCSP_R_SERVER_READ_ERROR’?
|  1022 | OCSPerr(OCSP_F_OCSP_SENDREQ_BIO,OCSP_R_SERVER_RESPONSE_ERROR);
|   | ^~~~
| In file included from /<>/libdigidoc/DigiDocLib.h:36,
|  from /<>/libdigidoc/DigiDocConfig.h:29,
|  from /<>/libdigidoc/DigiDocOCSP.c:23:
| /<>/libdigidoc/DigiDocOCSP.c: In function 
‘verifyOCSPResponse’:
| /<>/libdigidoc/DigiDocOCSP.c:1603:31: warning: passing argument 
1 of ‘ossl_check_X509_type’ discards ‘const’ qualifier from pointer 
target type [-Wdiscarded-qualifiers]
…
| make[3]: *** [libdigidoc/CMakeFiles/digidoc.dir/build.make:317: 
libdigidoc/CMakeFiles/digidoc.dir/DigiDocOCSP.c.o] Error 1
| make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
| make[2]: *** [CMakeFiles/Makefile2:131: 
libdigidoc/CMakeFiles/digidoc.dir/all] Error 2
| make[2]: Leaving directory '/<>/obj-x86_64-linux-gnu'
| make[1]: *** [Makefile:139: all] Error 2
| make[1]: Leaving directory '/<>/obj-x86_64-linux-gnu'
| dh_auto_build: error: cd obj-x86_64-linux-gnu && make -j1 "INSTALL=install 
--strip-program=true" VERBOSE=1 returned exit code 2

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

Sebastian
--- End Message ---
--- Begin Message ---
Source: libdigidoc
Source-Version: 3.10.5-3
Done: William 'jawn-smith' Wilson 

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

Debian distribution maintenance software
pp.
William 'jawn-smith' Wilson  (supplier of updated 
libdigidoc package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 28 Jun 2022 15:07:48 -0500
Source: libdigidoc
Built-For-Profiles: noudeb
Architecture: source
Version: 3.10.5-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: William 'jawn-smith' Wilson 
Closes: 1006389
Changes:
 libdigidoc (3.10.5-3) unstable; urgency=medium
 .
   * QA upload.
   * Resolve FTBFS with openssl v3 (Closes: #1006389)
   * d/control: Update Standards-Version to 4.6.1, no changes needed
   * d/control: Mark 

Bug#1004587: marked as done (pyglet: FTBFS with ffmpeg 5.0)

[Debian Bug Tracking System]

Your message dated Fri, 01 Jul 2022 17:19:42 +
with message-id 
and subject line Bug#1004587: fixed in pyglet 1.5.26+ds-1
has caused the Debian Bug report #1004587,
regarding pyglet: FTBFS with ffmpeg 5.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.)


-- 
1004587: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004587
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pyglet
Version: 1.5.14-2
Severity: important
X-Debbugs-Cc: sramac...@debian.org
Tags: sid bookworm ftbfs
Usertags: ffmpeg5.0

pyglet FTBFS with ffmpeg 5.0 (available in experimental):
|dh_auto_test -O--buildsystem=pybuild
| I: pybuild base:237: cd /<>/.pybuild/cpython3_3.10_pyglet/build; 
python3.10 -m pytest >/dev/null 2>&1; cd 
/<>/.pybuild/cpython3_3.10_pyglet/build; xvfb-run --auto-servernum 
--server-num=20 -s "-screen 0 1024x768x24 -ac +extension GLX +render -noreset" 
python3.10 -m pytest -v -k "not interactive and not PulseAudio and not 
test_pulse and not test_player_play and not test_player_play_multiple and not 
test_player_silent_audio_driver and not test_freetype_face and not 
test_fontconfig and not test_linux_fontconfig and not test_driver and not 
test_openal and not ClockTimingTestCase" --ignore=tests/interactive
| = test session starts 
==
| platform linux -- Python 3.10.2, pytest-6.2.5, py-1.10.0, pluggy-0.13.0 -- 
/usr/bin/python3.10
| cachedir: .pytest_cache
| rootdir: /<>
| collecting ... collected 400 items / 5 errors / 87 deselected / 308 selected

|  ERRORS 

| _ ERROR collecting 
.pybuild/cpython3_3.10_pyglet/build/tests/integration/media/test_directsound.py 
_
| tests/integration/media/test_directsound.py:11: in 
| from pyglet.media.codecs import AudioFormat
| pyglet/media/__init__.py:143: in 
| add_default_media_codecs()
| pyglet/media/codecs/__init__.py:102: in add_default_media_codecs
| if have_ffmpeg():
| pyglet/media/codecs/__init__.py:118: in have_ffmpeg
| from . import ffmpeg_lib
| pyglet/media/codecs/ffmpeg_lib/__init__.py:36: in 
| from .libavcodec import *
| pyglet/media/codecs/ffmpeg_lib/libavcodec.py:46: in 
| from . import libavutil
| pyglet/media/codecs/ffmpeg_lib/libavutil.py:206: in 
| avutil.av_frame_get_best_effort_timestamp.restype = c_int64
| /usr/lib/python3.10/ctypes/__init__.py:387: in __getattr__
| func = self.__getitem__(name)
| /usr/lib/python3.10/ctypes/__init__.py:392: in __getitem__
| func = self._FuncPtr((name_or_ordinal, self))
| E   AttributeError: /usr/lib/x86_64-linux-gnu/libavutil.so.57: undefined 
symbol: av_frame_get_best_effort_timestamp
| _ ERROR collecting 
.pybuild/cpython3_3.10_pyglet/build/tests/integration/media/test_player.py _
| tests/integration/media/test_player.py:11: in 
| from pyglet.media import Player
| pyglet/media/__init__.py:143: in 
| add_default_media_codecs()
| pyglet/media/codecs/__init__.py:102: in add_default_media_codecs
| if have_ffmpeg():
| pyglet/media/codecs/__init__.py:118: in have_ffmpeg
| from . import ffmpeg_lib
| pyglet/media/codecs/ffmpeg_lib/__init__.py:36: in 
| from .libavcodec import *
| pyglet/media/codecs/ffmpeg_lib/libavcodec.py:46: in 
| from . import libavutil
| pyglet/media/codecs/ffmpeg_lib/libavutil.py:206: in 
| avutil.av_frame_get_best_effort_timestamp.restype = c_int64
| /usr/lib/python3.10/ctypes/__init__.py:387: in __getattr__
| func = self.__getitem__(name)
| /usr/lib/python3.10/ctypes/__init__.py:392: in __getitem__
| func = self._FuncPtr((name_or_ordinal, self))
| E   AttributeError: /usr/lib/x86_64-linux-gnu/libavutil.so.57: undefined 
symbol: av_frame_get_best_effort_timestamp
| _ ERROR collecting 
.pybuild/cpython3_3.10_pyglet/build/tests/integration/media/test_pulse.py _
| tests/integration/media/test_pulse.py:12: in 
| from pyglet.media.drivers.pulse import interface
| pyglet/media/drivers/pulse/__init__.py:36: in 
| from .adaptation import PulseAudioDriver
| pyglet/media/drivers/pulse/adaptation.py:39: in 
| from pyglet.media.events import MediaEvent
| pyglet/media/__init__.py:143: in 
| add_default_media_codecs()
| pyglet/media/codecs/__init__.py:102: in add_default_media_codecs
| if have_ffmpeg():
| pyglet/media/codecs/__init__.py:118: in have_ffmpeg
| from . import ffmpeg_lib
| pyglet/media/codecs/ffmpeg_lib/__init__.py:36: in 
| from .libavcodec import *
| pyglet/media/codecs/ffmpeg_lib/libavcodec.py:46: in 
| from . import libavutil
| 

Processed: fixed 1013593 in 3.22.4-3, fixed 1013596 in 3.22.4-3

[Debian Bug Tracking System]

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

> fixed 1013593 3.22.4-3
Bug #1013593 {Done: Shengjing Zhu } 
[golang-github-shirou-gopsutil] consul: FTBFS: make: *** [debian/rules:32: 
build] Error 25
There is no source info for the package 'golang-github-shirou-gopsutil' at 
version '3.22.4-3' with architecture ''
Unable to make a source version for version '3.22.4-3'
Marked as fixed in versions 3.22.4-3.
> fixed 1013596 3.22.4-3
Bug #1013596 {Done: Shengjing Zhu } 
[golang-github-shirou-gopsutil] packer: FTBFS: cannot find package 
"github.com/shirou/gopsutil/process"
There is no source info for the package 'golang-github-shirou-gopsutil' at 
version '3.22.4-3' with architecture ''
Unable to make a source version for version '3.22.4-3'
Marked as fixed in versions 3.22.4-3.
> thanks
Stopping processing here.

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

Bug#991931: marked as done (CVE-2021-32686 / AST-2021-009: pjproject/pjsip: crash when SSL socket destroyed during handshake)

[Debian Bug Tracking System]

Your message dated Fri, 01 Jul 2022 17:02:07 +
with message-id 
and subject line Bug#991931: fixed in asterisk 1:16.16.1~dfsg-1+deb11u1
has caused the Debian Bug report #991931,
regarding CVE-2021-32686 / AST-2021-009: pjproject/pjsip: crash when SSL socket 
destroyed during handshake
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.)


-- 
991931: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991931
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:asterisk
Severity: serious
Tags: security upstream patch

https://downloads.asterisk.org/pub/security/AST-2021-009.html

Summary:pjproject/pjsip: crash when SSL socket destroyed during 
handshake
Nature of Advisory: Denial of service
Susceptibility: Remote unauthenticated sessions
Severity:   Major
Exploits Known: Yes

Description
| Depending on the timing, it’s possible for Asterisk to crash when using a TLS
| connection if the underlying socket parent/listener gets destroyed during the
| handshake.
--- End Message ---
--- Begin Message ---
Source: asterisk
Source-Version: 1:16.16.1~dfsg-1+deb11u1
Done: Bernhard Schmidt 

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

Debian distribution maintenance software
pp.
Bernhard Schmidt  (supplier of updated asterisk 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, 09 Aug 2021 08:48:31 +0200
Source: asterisk
Architecture: source
Version: 1:16.16.1~dfsg-1+deb11u1
Distribution: bullseye-security
Urgency: medium
Maintainer: Debian VoIP Team 
Changed-By: Bernhard Schmidt 
Closes: 991710 991931
Changes:
 asterisk (1:16.16.1~dfsg-1+deb11u1) bullseye-security; urgency=medium
 .
   * CVE-2021-32558 / AST-2021-008 (Closes: #991710)
 If the IAX2 channel driver receives a packet that contains an unsupported
 media format it can cause a crash to occur in Asterisk
   * CVE-2021-32686 / AST-2021-009 (Closes: #991931)
 pjproject/pjsip: crash when SSL socket destroyed during handshake
   * d/gbp.conf for Bullseye branch
Checksums-Sha1:
 084c8ebf5f267ac172504bebbd7648f4cfecc1d3 4233 
asterisk_16.16.1~dfsg-1+deb11u1.dsc
 f0b46a4eabe561df5c690f73862746fa01d67739 7055724 
asterisk_16.16.1~dfsg.orig.tar.xz
 5ac73590577b4821d18dd3515e7522f09199d316 5953420 
asterisk_16.16.1~dfsg-1+deb11u1.debian.tar.xz
 19ba4db88523dbc91f4b20d23f50e056ec6a0d95 27939 
asterisk_16.16.1~dfsg-1+deb11u1_amd64.buildinfo
Checksums-Sha256:
 ad664a54385066c5032e2fe29e7113922d0c8b68a9251169f1703edea90eb09e 4233 
asterisk_16.16.1~dfsg-1+deb11u1.dsc
 42268f21025a0fab9288f616951609f8b10118fb63e35fae80e7d110eb5dda6e 7055724 
asterisk_16.16.1~dfsg.orig.tar.xz
 25eac97078e99ce9dc345da75639d5e9bb5cc0b9c9a50dd447e45c246491a70a 5953420 
asterisk_16.16.1~dfsg-1+deb11u1.debian.tar.xz
 071bb9c82ca6552570066d273e028738ea4ee73d4b26805e782da42326a4aca5 27939 
asterisk_16.16.1~dfsg-1+deb11u1_amd64.buildinfo
Files:
 37c0ba19cc3012535930dc4d4e52014d 4233 comm optional 
asterisk_16.16.1~dfsg-1+deb11u1.dsc
 ad421903a111f0a43e25d64b7aadc2e9 7055724 comm optional 
asterisk_16.16.1~dfsg.orig.tar.xz
 4647ac3e939cfed2fea75b27139d9467 5953420 comm optional 
asterisk_16.16.1~dfsg-1+deb11u1.debian.tar.xz
 db5b862051a9cfecfc678a47857905d4 27939 comm optional 
asterisk_16.16.1~dfsg-1+deb11u1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE1uAexRal3873GVbTd1B55bhQvJMFAmEj9QIRHGJlcm5pQGRl
Ymlhbi5vcmcACgkQd1B55bhQvJNMYA/7BHIp5g+qySH2kMQlHf91aowKnwXN7oq1
Wh/+5eOMe0Y5t/gqeFY/PvcyXzquTNMdStW5OkDyfVqp4ddXZZJqUnc+dKwvez8F
t/3twBYH/grscLhHQlPWs9LvzfgIPZJJmP7rYKVjJxRxkWeKNpwoNhbohYMITjpJ
bhpnb+KwjurCUUwNberFc9epKxClXaav+1ZqK+GEFwMsgG88REdOtaPzIUB/WoF7
CpQMTuUtJgtYO0Up4x7W1g+ebUF6dAkBr4N+CvctF8Tktbfv1z9inYQvfzGfw6P1
Dtj3qlvtT6kuZqYtwjMZGdoRF8ISm4ZY+sEQ1EqLI2s59FoIqmG35V93cohh0bkx
AW9enPTwJr4Hvk6His0ca3eJScf1j7nmS5c3K2fCcCwZawABxmRjD77dNQYuqHm+
PnGuxRq9d32eUsCXo7dqYbJIHIhsME2PCByTfhKy0hDTkPevhctPNwm31MVRUi95
dMUAN68cAZSPKSjYITwfIl8fXLPjRWaWy8s7nF4rT6YrZH2Sqh8DwnuBAVXxF4al

Processed: reassign 1013593 to golang-github-shirou-gopsutil, reassign 1013596 to golang-github-shirou-gopsutil

[Debian Bug Tracking System]

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

> reassign 1013593 golang-github-shirou-gopsutil 3.22.4-2
Bug #1013593 {Done: Shengjing Zhu } [src:consul] consul: 
FTBFS: make: *** [debian/rules:32: build] Error 25
Bug reassigned from package 'src:consul' to 'golang-github-shirou-gopsutil'.
No longer marked as found in versions consul/1.8.7+dfsg1-5.
No longer marked as fixed in versions golang-github-shirou-gopsutil/3.22.4-3.
Bug #1013593 {Done: Shengjing Zhu } 
[golang-github-shirou-gopsutil] consul: FTBFS: make: *** [debian/rules:32: 
build] Error 25
There is no source info for the package 'golang-github-shirou-gopsutil' at 
version '3.22.4-2' with architecture ''
Unable to make a source version for version '3.22.4-2'
Marked as found in versions 3.22.4-2.
> reassign 1013596 golang-github-shirou-gopsutil 3.22.4-2
Bug #1013596 {Done: Shengjing Zhu } [src:packer] packer: 
FTBFS: cannot find package "github.com/shirou/gopsutil/process"
Bug reassigned from package 'src:packer' to 'golang-github-shirou-gopsutil'.
No longer marked as found in versions packer/1.6.6+ds1-4.
No longer marked as fixed in versions golang-github-shirou-gopsutil/3.22.4-3.
Bug #1013596 {Done: Shengjing Zhu } 
[golang-github-shirou-gopsutil] packer: FTBFS: cannot find package 
"github.com/shirou/gopsutil/process"
There is no source info for the package 'golang-github-shirou-gopsutil' at 
version '3.22.4-2' with architecture ''
Unable to make a source version for version '3.22.4-2'
Marked as found in versions 3.22.4-2.
> thanks
Stopping processing here.

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

Processed: Re: python-seqcluster: FTBFS: ModuleNotFoundError: No module named 'attr'

[Debian Bug Tracking System]

Processing control commands:

> notfound -1 python-seqcluster/1.2.8+ds-2
Bug #1012386 [src:python-seqcluster] python-seqcluster: FTBFS: 
ModuleNotFoundError: No module named 'attr'
No longer marked as found in versions python-seqcluster/1.2.8+ds-2.
> close -1
Bug #1012386 [src:python-seqcluster] python-seqcluster: FTBFS: 
ModuleNotFoundError: No module named 'attr'
Marked Bug as done

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

Bug#1012386: python-seqcluster: FTBFS: ModuleNotFoundError: No module named 'attr'

[Bastian Germann]

Control: notfound -1 python-seqcluster/1.2.8+ds-2
Control: close -1

This was obviously an issue in myst_parser module which is not part of 
python-seqcluster.
It is already fixed, so the FTBFS is as well.

Bug#1013494: marked as done (python-django-bootstrap-form: FTBFS: AssertionError: )

[Debian Bug Tracking System]

Your message dated Fri, 1 Jul 2022 12:52:28 -0400
with message-id <582a6ca2-a721-913f-52d5-805aa3f78...@mailbox.org>
and subject line fixed in 3.4-6
has caused the Debian Bug report #1013494,
regarding python-django-bootstrap-form: FTBFS: AssertionError: 
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.)


-- 
1013494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013494
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-django-bootstrap-form
Version: 3.4-5
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220624 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> make: pyversions: No such file or directory
> py3versions: no X-Python3-Version in control file, using supported versions
> dh binary --buildsystem=pybuild --with python3,sphinxdoc
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:239: python3.9 setup.py config 
> running config
> I: pybuild base:239: python3.10 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:239: /usr/bin/python3.9 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.9/build/bootstrapform
> copying bootstrapform/__init__.py -> 
> /<>/.pybuild/cpython3_3.9/build/bootstrapform
> copying bootstrapform/models.py -> 
> /<>/.pybuild/cpython3_3.9/build/bootstrapform
> copying bootstrapform/tests.py -> 
> /<>/.pybuild/cpython3_3.9/build/bootstrapform
> copying bootstrapform/config.py -> 
> /<>/.pybuild/cpython3_3.9/build/bootstrapform
> copying bootstrapform/meta.py -> 
> /<>/.pybuild/cpython3_3.9/build/bootstrapform
> creating 
> /<>/.pybuild/cpython3_3.9/build/bootstrapform/templatetags
> copying bootstrapform/templatetags/__init__.py -> 
> /<>/.pybuild/cpython3_3.9/build/bootstrapform/templatetags
> copying bootstrapform/templatetags/bootstrap.py -> 
> /<>/.pybuild/cpython3_3.9/build/bootstrapform/templatetags
> running egg_info
> creating django_bootstrap_form.egg-info
> writing django_bootstrap_form.egg-info/PKG-INFO
> writing dependency_links to 
> django_bootstrap_form.egg-info/dependency_links.txt
> writing requirements to django_bootstrap_form.egg-info/requires.txt
> writing top-level names to django_bootstrap_form.egg-info/top_level.txt
> writing manifest file 'django_bootstrap_form.egg-info/SOURCES.txt'
> reading manifest file 'django_bootstrap_form.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> adding license file 'LICENSE'
> writing manifest file 'django_bootstrap_form.egg-info/SOURCES.txt'
> creating /<>/.pybuild/cpython3_3.9/build/bootstrapform/templates
> creating 
> /<>/.pybuild/cpython3_3.9/build/bootstrapform/templates/bootstrapform
> copying bootstrapform/templates/bootstrapform/field.html -> 
> /<>/.pybuild/cpython3_3.9/build/bootstrapform/templates/bootstrapform
> copying bootstrapform/templates/bootstrapform/form.html -> 
> /<>/.pybuild/cpython3_3.9/build/bootstrapform/templates/bootstrapform
> copying bootstrapform/templates/bootstrapform/formset.html -> 
> /<>/.pybuild/cpython3_3.9/build/bootstrapform/templates/bootstrapform
> I: pybuild base:239: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.10/build/bootstrapform
> copying bootstrapform/__init__.py -> 
> /<>/.pybuild/cpython3_3.10/build/bootstrapform
> copying bootstrapform/models.py -> 
> /<>/.pybuild/cpython3_3.10/build/bootstrapform
> copying bootstrapform/tests.py -> 
> /<>/.pybuild/cpython3_3.10/build/bootstrapform
> copying bootstrapform/config.py -> 
> /<>/.pybuild/cpython3_3.10/build/bootstrapform
> copying bootstrapform/meta.py -> 
> /<>/.pybuild/cpython3_3.10/build/bootstrapform
> creating 
> /<>/.pybuild/cpython3_3.10/build/bootstrapform/templatetags
> copying bootstrapform/templatetags/__init__.py -> 
> /<>/.pybuild/cpython3_3.10/build/bootstrapform/templatetags
> copying bootstrapform/templatetags/bootstrap.py -> 
> /<>/.pybuild/cpython3_3.10/build/bootstrapform/templatetags
> running egg_info
> writing django_bootstrap_form.egg-info/PKG-INFO
> writing dependency_links to 
> django_bootstrap_form.egg-info/dependency_links.txt
> writing requirements to django_bootstrap_form.egg-info/requires.txt
> writing top-level names to django_bootstrap_form.egg-info/top_level.txt
> reading manifest file 'django_bootstrap_form.egg-info/SOURCES.txt'
> reading 

Bug#1014180: src:boost1.74: Cleanup code of boost::asio causes crashes with OpenSSL 3+

[Gianfranco Costamagna]

Hello Hilko
On Fri, 01 Jul 2022 18:03:10 +0200 Hilko Bengen  wrote:

Source: boost1.74
Version: 1.74.0-16
Severity: grave
Tags: patch, upstream
X-Debbugs-Cc: Hilko Bengen 

Dear Maintainer,

I recently received #1013470 (nbdkit FTBFS because of segfaults when
running test suite); this turned out to be caused by #1013931 (segfault
in libtorrent-rasterbar cleanup code), I was able to track the root
cause to an incomplete #ifdef condition in
libs/asio/include//boost/asio/ssl/detail/impl/openssl_init.ipp as of
1.74.0-16 that caused CONF_modules_unload to crash after OpenSSL 3.0+
had done its own cleanup which included calling that function.

(See discussion in .)

Please apply upstream's patch
.

After applying this patch, and rebuilding boost1.74 +
libtorrent-rasterbar, I am no longer able to reproduce the sagfaults.


I found the very same issue on cpprest and websocketpp but I couldn't go deeper 
into asio code and find the patch.

I merged the other bugs to this one, but I don't know how many others are there.

We should NMU ASAP.

G.

Bug#1013472: reassign to openssl package

[Gianfranco Costamagna]

control: reassign -1 src:boost1.74
control: found -1 1.74.0-16
control: forcemerge -1 1014180
control: affects -1 cpprest
control: affects -1 websocketpp

G.

Processed: Re: reassign to openssl package

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:boost1.74
Bug #1013530 [openssl] cpprest: FTBFS: dh_auto_test: error: cd 
obj-x86_64-linux-gnu && make -j8 test ARGS\+=--verbose ARGS\+=-j8 returned exit 
code 2
Bug reassigned from package 'openssl' to 'src:boost1.74'.
No longer marked as found in versions openssl/3.0.4-2.
Ignoring request to alter fixed versions of bug #1013530 to the same values 
previously set
> found -1 1.74.0-16
Bug #1013530 [src:boost1.74] cpprest: FTBFS: dh_auto_test: error: cd 
obj-x86_64-linux-gnu && make -j8 test ARGS\+=--verbose ARGS\+=-j8 returned exit 
code 2
Marked as found in versions boost1.74/1.74.0-16.
> forcemerge -1 1014180
Bug #1013530 [src:boost1.74] cpprest: FTBFS: dh_auto_test: error: cd 
obj-x86_64-linux-gnu && make -j8 test ARGS\+=--verbose ARGS\+=-j8 returned exit 
code 2
Bug #1013472 [src:boost1.74] websocketpp: FTBFS: test failed: 18 - 
test_transport_asio_timers (SEGFAULT)
Removed indication that 1013472 affects cpprest and websocketpp
Removed indication that 1014180 affects cpprest and websocketpp
Bug #1013530 [src:boost1.74] cpprest: FTBFS: dh_auto_test: error: cd 
obj-x86_64-linux-gnu && make -j8 test ARGS\+=--verbose ARGS\+=-j8 returned exit 
code 2
Added tag(s) upstream and patch.
Bug #1014180 [src:boost1.74] src:boost1.74: Cleanup code of boost::asio causes 
crashes with OpenSSL 3+
Merged 1013472 1013530 1014180
> affects -1 cpprest
Bug #1013530 [src:boost1.74] cpprest: FTBFS: dh_auto_test: error: cd 
obj-x86_64-linux-gnu && make -j8 test ARGS\+=--verbose ARGS\+=-j8 returned exit 
code 2
Bug #1013472 [src:boost1.74] websocketpp: FTBFS: test failed: 18 - 
test_transport_asio_timers (SEGFAULT)
Bug #1014180 [src:boost1.74] src:boost1.74: Cleanup code of boost::asio causes 
crashes with OpenSSL 3+
Added indication that 1013530 affects cpprest
Added indication that 1013472 affects cpprest
Added indication that 1014180 affects cpprest
> affects -1 websocketpp
Bug #1013530 [src:boost1.74] cpprest: FTBFS: dh_auto_test: error: cd 
obj-x86_64-linux-gnu && make -j8 test ARGS\+=--verbose ARGS\+=-j8 returned exit 
code 2
Bug #1013472 [src:boost1.74] websocketpp: FTBFS: test failed: 18 - 
test_transport_asio_timers (SEGFAULT)
Bug #1014180 [src:boost1.74] src:boost1.74: Cleanup code of boost::asio causes 
crashes with OpenSSL 3+
Added indication that 1013530 affects websocketpp
Added indication that 1013472 affects websocketpp
Added indication that 1014180 affects websocketpp

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

Processed: Re: reassign to openssl package

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:boost1.74
Bug #1013472 [openssl] websocketpp: FTBFS: test failed: 18 - 
test_transport_asio_timers (SEGFAULT)
Bug reassigned from package 'openssl' to 'src:boost1.74'.
No longer marked as found in versions openssl/3.0.4-2.
Ignoring request to alter fixed versions of bug #1013472 to the same values 
previously set
> found -1 1.74.0-16
Bug #1013472 [src:boost1.74] websocketpp: FTBFS: test failed: 18 - 
test_transport_asio_timers (SEGFAULT)
Marked as found in versions boost1.74/1.74.0-16.
> forcemerge -1 1014180
Bug #1013472 [src:boost1.74] websocketpp: FTBFS: test failed: 18 - 
test_transport_asio_timers (SEGFAULT)
Bug #1014180 [src:boost1.74] src:boost1.74: Cleanup code of boost::asio causes 
crashes with OpenSSL 3+
Severity set to 'serious' from 'grave'
Added tag(s) sid, ftbfs, and bookworm.
Bug #1013472 [src:boost1.74] websocketpp: FTBFS: test failed: 18 - 
test_transport_asio_timers (SEGFAULT)
Added tag(s) upstream and patch.
Merged 1013472 1014180
> affects -1 cpprest
Bug #1013472 [src:boost1.74] websocketpp: FTBFS: test failed: 18 - 
test_transport_asio_timers (SEGFAULT)
Bug #1014180 [src:boost1.74] src:boost1.74: Cleanup code of boost::asio causes 
crashes with OpenSSL 3+
Added indication that 1013472 affects cpprest
Added indication that 1014180 affects cpprest
> affects -1 websocketpp
Bug #1013472 [src:boost1.74] websocketpp: FTBFS: test failed: 18 - 
test_transport_asio_timers (SEGFAULT)
Bug #1014180 [src:boost1.74] src:boost1.74: Cleanup code of boost::asio causes 
crashes with OpenSSL 3+
Added indication that 1013472 affects websocketpp
Added indication that 1014180 affects websocketpp

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

Processed: reassign to openssl package

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 openssl
Bug #1013530 [src:cpprest] cpprest: FTBFS: dh_auto_test: error: cd 
obj-x86_64-linux-gnu && make -j8 test ARGS\+=--verbose ARGS\+=-j8 returned exit 
code 2
Bug reassigned from package 'src:cpprest' to 'openssl'.
No longer marked as found in versions cpprest/2.10.18-1.
Ignoring request to alter fixed versions of bug #1013530 to the same values 
previously set
> found -1 3.0.4-2
Bug #1013530 [openssl] cpprest: FTBFS: dh_auto_test: error: cd 
obj-x86_64-linux-gnu && make -j8 test ARGS\+=--verbose ARGS\+=-j8 returned exit 
code 2
Marked as found in versions openssl/3.0.4-2.

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

Processed: reassign to openssl package

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 openssl
Bug #1013472 [src:websocketpp] websocketpp: FTBFS: test failed: 18 - 
test_transport_asio_timers (SEGFAULT)
Bug reassigned from package 'src:websocketpp' to 'openssl'.
No longer marked as found in versions websocketpp/0.8.2-4.
Ignoring request to alter fixed versions of bug #1013472 to the same values 
previously set
> found -1 3.0.4-2
Bug #1013472 [openssl] websocketpp: FTBFS: test failed: 18 - 
test_transport_asio_timers (SEGFAULT)
Marked as found in versions openssl/3.0.4-2.

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

Bug#1013931: libtorrent-rasterbar2.0: Crash on exit

[Hilko Bengen]

I think I found the root cuase in boost1.74 – and reported it as
#1014180. Please note that libtorrent-rasterbar has to be rebuilt for
the change to take effect.

(It might be a good idea to add a Built-Using line to debian/control.)

Cheers,
-Hilko

Bug#1005720: [debian-mysql] Bug#1005720: mysql-8.0: FTBFS with OpenSSL 3.0

[Robie Basak]

On Fri, Jul 01, 2022 at 05:45:12PM +0200, Bastian Germann wrote:
> Lena, please tag the changelog entries accordingly, at least for RC bugs so 
> they do not keep the package from migrating.

Note that mysql-8.0 is permanently blocked from migrating by order of
the release team. They want MariaDB in testing to the exclusion of
MySQL. The maintainers would prefer to have both, but the release team
overrode that.

We will continue fixing bugs against the MySQL packaging, but with no
expectation that it will ever migrate.


signature.asc
Description: PGP signature

Bug#1014180: src:boost1.74: Cleanup code of boost::asio causes crashes with OpenSSL 3+

[Hilko Bengen]

Source: boost1.74
Version: 1.74.0-16
Severity: grave
Tags: patch, upstream
X-Debbugs-Cc: Hilko Bengen 

Dear Maintainer,

I recently received #1013470 (nbdkit FTBFS because of segfaults when
running test suite); this turned out to be caused by #1013931 (segfault
in libtorrent-rasterbar cleanup code), I was able to track the root
cause to an incomplete #ifdef condition in
libs/asio/include//boost/asio/ssl/detail/impl/openssl_init.ipp as of
1.74.0-16 that caused CONF_modules_unload to crash after OpenSSL 3.0+
had done its own cleanup which included calling that function.

(See discussion in .)

Please apply upstream's patch
.

After applying this patch, and rebuilding boost1.74 +
libtorrent-rasterbar, I am no longer able to reproduce the sagfaults.

Cheers,
-Hilko

Bug#1005720: mysql-8.0: FTBFS with OpenSSL 3.0

[Bastian Germann]

Control: fixed -1 8.0.29-1
X-Debbugs-Cc: Lena Voytek 

The issue has obviously been fixed with 8.0.29-1.
Lena, please tag the changelog entries accordingly, at least for RC bugs so 
they do not keep the package from migrating.

Processed: Re: mysql-8.0: FTBFS with OpenSSL 3.0

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 8.0.29-1
Bug #1005720 [src:mysql-8.0] mysql-8.0: FTBFS with OpenSSL 3.0
Marked as fixed in versions mysql-8.0/8.0.29-1.

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

Bug#1010052: mysql-8.0 FTBFS: error: ‘size_t’ has not been declared

[Bastian Germann]

Control: fixed -1 8.0.28-1

The issue has obviously been fixed with that upload, maybe in an earlier 
version that was not released in Debian.

Processed: Re: mysql-8.0 FTBFS: error: ‘size_t’ has not been declared

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 8.0.28-1
Bug #1010052 [src:mysql-8.0] mysql-8.0 FTBFS: error: ‘size_t’ has not been 
declared
Marked as fixed in versions mysql-8.0/8.0.28-1.

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

Bug#1006051: marked as done (nuitka: FTBFS: Error, results differed (stdout).)

[Debian Bug Tracking System]

Your message dated Fri, 01 Jul 2022 15:35:49 +
with message-id 
and subject line Bug#1006051: fixed in nuitka 0.9+ds-1
has caused the Debian Bug report #1006051,
regarding nuitka: FTBFS: Error, results differed (stdout).
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.)


-- 
1006051: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006051
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nuitka
Version: 0.6.19.1+ds-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> # The RUN_TEST_PYTHON is not the one to execute tests, just the for the
> # test runner.
> python3 ./tests/run-tests --skip-reflection-test --no-python2.7 --no-python2.6
> Cannot execute tests with Python 2.6, disabled or not installed.
> Cannot execute tests with Python 2.7, disabled or not installed.
> Cannot execute tests with Python 2.6, disabled or not installed.
> Cannot execute tests with Python 2.7, disabled or not installed.
> Cannot execute tests with Python 3.3, disabled or not installed.
> Cannot execute tests with Python 3.4, disabled or not installed.
> Cannot execute tests with Python 3.5, disabled or not installed.
> Cannot execute tests with Python 3.6, disabled or not installed.
> Cannot execute tests with Python 3.7, disabled or not installed.
> Cannot execute tests with Python 3.8, disabled or not installed.
> Executing test case called 'python3.9-nodebug' with CPython 'python3.9' and 
> extra flags ''.
> Running the basic tests with options '' with 'python3.9':
> Run '/usr/bin/python3 ./tests/basics/run_all.py search' in '/<>'.
> Using concrete python 3.9.10 on x86_64
> Comparing output of 'Asserts.py' using '/usr/bin/python3' with flags silent, 
> expect_success, remove_output, --nofollow-imports, 
> --file-reference-choice=original, cpython_cache, timing, 
> plugin_enable:pylint-warnings ...
> CPython took 0.03s vs 5.28s Nuitka.
> Comparing output of 'Assignments.py' using '/usr/bin/python3' with flags 
> silent, expect_success, remove_output, --nofollow-imports, 
> --file-reference-choice=original, cpython_cache, timing, 
> plugin_enable:pylint-warnings ...
> CPython took 0.02s vs 2.99s Nuitka.
> Comparing output of 'Assignments32.py' using '/usr/bin/python3' with flags 
> silent, expect_success, remove_output, --nofollow-imports, 
> --file-reference-choice=original, cpython_cache, timing, 
> plugin_enable:pylint-warnings ...
> CPython took 0.01s vs 6.78s Nuitka.
> Comparing output of 'Branching.py' using '/usr/bin/python3' with flags 
> silent, expect_success, remove_output, --nofollow-imports, 
> --file-reference-choice=original, cpython_cache, timing, 
> plugin_enable:pylint-warnings ...
> CPython took 0.02s vs 2.57s Nuitka.
> Comparing output of 'BuiltinOverload.py' using '/usr/bin/python3' with flags 
> silent, expect_success, remove_output, --nofollow-imports, 
> --file-reference-choice=original, cpython_cache, timing, 
> plugin_enable:pylint-warnings, ignore_warnings ...
> CPython took 0.01s vs 2.35s Nuitka.
> Comparing output of 'BuiltinSuper.py' using '/usr/bin/python3' with flags 
> silent, expect_success, remove_output, --nofollow-imports, 
> --file-reference-choice=original, cpython_cache, timing, 
> plugin_enable:pylint-warnings ...
> CPython took 0.01s vs 2.53s Nuitka.
> Comparing output of 'BuiltinsTest.py' using '/usr/bin/python3' with flags 
> silent, expect_success, remove_output, --nofollow-imports, 
> --file-reference-choice=original, cpython_cache, timing, 
> plugin_enable:pylint-warnings ...
> CPython took 0.03s vs 6.52s Nuitka.
> Comparing output of 'ClassMinimal.py' using '/usr/bin/python3' with flags 
> silent, expect_success, remove_output, --nofollow-imports, 
> --file-reference-choice=original, cpython_cache, timing, 
> plugin_enable:pylint-warnings ...
> CPython took 0.01s vs 2.38s Nuitka.
> Comparing output of '/var/tmp/basics-xp9r8rpq/Classes.py' using 
> '/usr/bin/python3' with flags silent, expect_success, remove_output, 
> --nofollow-imports, --file-reference-choice=original, cpython_cache, timing, 
> plugin_enable:pylint-warnings ...
> CPython took 0.02s vs 3.53s Nuitka.
> Comparing output of 'Classes32.py' using '/usr/bin/python3' with flags 
> silent, expect_success, remove_output, --nofollow-imports, 
> --file-reference-choice=original, cpython_cache, timing, 
> plugin_enable:pylint-warnings ...
> CPython took 0.02s vs 2.64s Nuitka.
> Comparing output of 'Classes34.py' using '/usr/bin/python3' 

Bug#1014179: pytango FTBFS on IPV6-only buildds

[Adrian Bunk]

Source: pytango
Version: 9.3.4-2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=pytango=all=9.3.4-2=1656689069=0

...
def get_host_ip():
"""Get the primary external host IP.

This is useful because an explicit IP is required to get
tango events to work properly. Note that localhost does not work
either.
"""
s = socket.socket(socket.AF_INET, socket.SOCK_DGRAM)
# Connecting to a UDP address doesn't send packets
>   s.connect(('8.8.8.8', 0))
E   OSError: [Errno 101] Network is unreachable
...

Bug#1013656: marked as done (node-zrender: FTBFS: make: *** [debian/rules:8: binary] Error 25)

[Debian Bug Tracking System]

Your message dated Fri, 01 Jul 2022 14:52:54 +
with message-id 
and subject line Bug#1013656: fixed in node-zrender 5.3.2+dfsg-1
has caused the Debian Bug report #1013656,
regarding node-zrender: FTBFS: make: *** [debian/rules:8: binary] Error 25
to be marked as done.

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

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


-- 
1013656: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013656
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-zrender
Version: 5.3.1+dfsg-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220624 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure --buildsystem=nodejs
> Link ./node_modules/@rollup/plugin-typescript -> 
> /usr/share/nodejs/@rollup/plugin-typescript
> Link ./node_modules/tslib -> /usr/share/nodejs/tslib
> Link ./node_modules/typescript -> /usr/share/nodejs/typescript
> Link ./node_modules/@types/node -> /usr/share/nodejs/@types/node
> Copy /usr/share/nodejs/jest-diff -> ./node_modules/
> Copy /usr/share/nodejs/pretty-format -> ./node_modules/
> Copy /usr/share/nodejs/ts-jest -> ./node_modules/
> Copy /usr/share/nodejs/@types/jest -> ./node_modules/@types
>dh_auto_build --buildsystem=nodejs
> Found debian/nodejs/./build
>   cd ./. && sh -ex debian/nodejs/./build
> + set -e
> + node build/build.js --minify
> [1/0]: index.ts
> [2/0]: src/all.ts
> [3/0]: src/zrender.ts
> [4/0]: src/export.ts
> [5/0]: src/canvas/Painter.ts
> [6/0]: src/svg/Painter.ts
> [7/0]: src/core/env.ts
> [8/0]: src/core/util.ts
> [9/0]: src/Handler.ts
> [10/0]: src/Storage.ts
> [11/0]: src/animation/Animation.ts
> [12/0]: src/dom/HandlerProxy.ts
> [13/0]: src/tool/color.ts
> [14/0]: src/config.ts
> [15/0]: src/graphic/Group.ts
> [16/0]: src/core/matrix.ts
> [17/0]: src/core/vector.ts
> [18/0]: src/tool/path.ts
> [19/0]: src/tool/parseSVG.ts
> [20/0]: src/tool/morphPath.ts
> [21/0]: src/core/Point.ts
> [22/0]: src/Element.ts
> [23/0]: src/graphic/Displayable.ts
> [24/0]: src/graphic/Path.ts
> [25/0]: src/graphic/Image.ts
> [26/0]: src/graphic/CompoundPath.ts
> [27/0]: src/graphic/TSpan.ts
> [28/0]: src/graphic/IncrementalDisplayable.ts
> [29/0]: src/graphic/Text.ts
> [30/0]: src/graphic/shape/Arc.ts
> [31/0]: src/graphic/shape/BezierCurve.ts
> [32/0]: src/graphic/shape/Circle.ts
> [33/0]: src/graphic/shape/Droplet.ts
> [34/0]: src/graphic/shape/Ellipse.ts
> [35/0]: src/graphic/shape/Heart.ts
> [36/0]: src/graphic/shape/Isogon.ts
> [37/0]: src/graphic/shape/Line.ts
> [38/0]: src/graphic/shape/Polygon.ts
> [39/0]: src/graphic/shape/Polyline.ts
> [40/0]: src/graphic/shape/Rect.ts
> [41/0]: src/graphic/shape/Ring.ts
> [42/0]: src/graphic/shape/Rose.ts
> [43/0]: src/graphic/shape/Sector.ts
> [44/0]: src/graphic/shape/Star.ts
> [45/0]: src/graphic/shape/Trochoid.ts
> [46/0]: src/graphic/LinearGradient.ts
> [47/0]: src/graphic/RadialGradient.ts
> [48/0]: src/graphic/Pattern.ts
> [49/0]: src/core/BoundingRect.ts
> [50/0]: src/core/OrientedBoundingRect.ts
> [51/0]: src/debug/showDebugDirtyRect.ts
> [52/0]: src/core/platform.ts
> [53/0]: src/canvas/Layer.ts
> [54/0]: src/animation/requestAnimationFrame.ts
> [55/0]: src/canvas/graphic.ts
> [56/0]: src/graphic/constants.ts
> [57/0]: src/canvas/helper.ts
> [58/0]: src/svg/graphic.ts
> [59/0]: src/svg/core.ts
> [60/0]: src/svg/helper.ts
> [61/0]: src/svg/patch.ts
> [62/1]: src/mixin/Draggable.ts
> [63/1]: src/core/Eventful.ts
> [64/1]: src/core/event.ts
> [65/1]: src/core/GestureMgr.ts
> [66/1]: src/core/timsort.ts
> [67/1]: src/animation/Animator.ts
> [68/1]: src/core/LRU.ts
> [69/1]: src/core/PathProxy.ts
> [70/1]: src/tool/transformPath.ts
> [71/1]: src/tool/parseXML.ts
> [72/1]: src/core/curve.ts
> [73/1]: src/core/Transformable.ts
> [74/1]: src/tool/dividePath.ts
> [75/1]: src/tool/convertPath.ts
> [76/1]: src/contain/text.ts
> [77/1]: src/contain/path.ts
> [78/1]: src/graphic/helper/parseText.ts
> [79/1]: src/graphic/helper/subPixelOptimize.ts
> [80/1]: src/graphic/helper/poly.ts
> [81/1]: src/graphic/helper/roundRect.ts
> [82/1]: src/graphic/helper/roundSector.ts
> [83/1]: src/graphic/Gradient.ts
> [84/1]: src/graphic/helper/image.ts
> [85/1]: src/canvas/dashStyle.ts
> [86/1]: src/svg/SVGPathRebuilder.ts
> [87/1]: src/svg/mapStyleToAttrs.ts
> [88/1]: src/svg/cssAnimation.ts
> [89/1]: src/svg/domapi.ts
> [90/1]: src/core/dom.ts
> [91/1]: src/animation/Clip.ts
> [92/1]: src/animation/easing.ts
> [93/1]: 

Bug#1013310: jsonnet: FTBFS on several release architectures

[Bastian Germann]

Am 01.07.22 um 11:44 schrieb Daichi Fukui:

Hello Bastian,

Thanks for reporting this.
And apologies for a late reply.

To address this FTBFS issue, I uploaded the following changes to s 
alsa.

   * fix FTBFS on several release architectures
   * fix FTBFS error on armel
   * Remove mipsel, mips64el, s390x as build target

For further information, kindly visit the following URL:
https://salsa.debian.org/dfukui/jsonnet/-/commits/debian/0.18.0+ds-2 





Please first read and address my comments on
https://mentors.debian.net/package/jsonnet/


If you don't mind, I would appreciate it if you sponsor and help me upload this 
package.
The following are some technical comments.

According to the original source code [0], c4core does not support the 
following CPU architectures:
s390x, mipsel, mips64el
Thus, we should drop these ones from the Architecture field on d/control.

Meanwhile, debugbreak should have been successfully built by falling back to raising SIGTRAP [1] for several 
architectures, but build fails due to a bug in upstream.
This issue has already been addressed [2], so a patch [3] was created and added to d/patches based on upstream. In a 
similar story, I fixed FTBFS on armel and filed a patch [4].


Thanks for reading.

[0] https://github.com/biojppm/c4core/blob/52f3ff57b287ce57c2bbf80dc091bd21e4d9f977/src/c4/cpu.hpp 

[1] 
https://github.com/google/jsonnet/blob/v0.18.0/third_party/rapidyaml/rapidyaml/ext/c4core/src/c4/ext/debugbreak/debugbreak.h#L123 

[2] https://github.com/scottt/debugbreak/commit/8b4a755e76717103adc814c0c05ceb3b91befa7d 

[3] https://salsa.debian.org/dfukui/jsonnet/-/commit/1bea08d549c450b8c9624e686df88f025e1d3d5c 

[4] https://salsa.debian.org/dfukui/jsonnet/-/commit/efb346e3ec210104897c38979291ab68e1eead73 



Best,
Fukui

Bug#1014166: bitcoin: CVE-2021-31876

[Moritz Mühlenhoff]

Source: bitcoin
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerability was published for bitcoin.

CVE-2021-31876[0]:
| Bitcoin Core 0.12.0 through 0.21.1 does not properly implement the
| replacement policy specified in BIP125, which makes it easier for
| attackers to trigger a loss of funds, or a denial of service attack
| against downstream projects such as Lightning network nodes. An
| unconfirmed child transaction with nSequence = 0xff_ff_ff_ff, spending
| an unconfirmed parent with nSequence = 0xff_ff_ff_fd, should be
| replaceable because there is inherited signaling by the child
| transaction. However, the actual PreChecks implementation does not
| enforce this. Instead, mempool rejects the replacement attempt of the
| unconfirmed child transaction.

https://en.bitcoin.it/wiki/Common_Vulnerabilities_and_Exposures#CVE-2021-31876
https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2021-May/018893.html


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2021-31876
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-31876

Please adjust the affected versions in the BTS as needed.

Processed: your mail

[Debian Bug Tracking System]

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

> found 928224 1:3.18.1-1
Bug #928224 [src:valgrind] Valgrind is broken on armhf
Bug #1014091 [src:valgrind] armhf: gcc has wrong configuration
Marked as found in versions valgrind/1:3.18.1-1.
Marked as found in versions valgrind/1:3.18.1-1.
>
End of message, stopping processing here.

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

Bug#1014094: marked as done (xsimd: autopkgtest regression on i386: ‘any’ is not a member of ‘xsimd’)

[Debian Bug Tracking System]

Your message dated Fri, 01 Jul 2022 13:43:36 +0200
with message-id 
and subject line Re: Bug#1014094 xsimd: autopkgtest regression on i386: ‘any’ 
is not a member of ‘xsimd’
has caused the Debian Bug report #1014094,
regarding xsimd: autopkgtest regression on i386: ‘any’ is not a member of 
‘xsimd’
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.)


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

Source: xsimd
Version: 8.1.0-4
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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


   passfail
xsimd  from testing8.1.0-4
all others from testingfrom testing

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

Currently this regression is blocking the migration to testing [1]. Can 
you please investigate the situation and fix it?


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

https://ci.debian.net/data/autopkgtest/testing/i386/x/xsimd/23188370/log.gz

Testing with gcc:
mandelbrot.cpp: In function ‘xsimd::batch xsimd::mandel(const 
xsimd::batch_bool&, const xsimd::batch&, const 
xsimd::batch&, int)’:

mandelbrot.cpp:74:25: error: ‘any’ is not a member of ‘xsimd’
   74 | if (!xsimd::any(active))
  | ^~~
mandelbrot.cpp: In function ‘void xsimd::mandelbrot(float, float, float, 
float, int, int, int, int*)’:
mandelbrot.cpp:112:71: error: ‘aligned_mode’ is not a member of ‘xsimd’; 
did you mean ‘aligned_free’?
  112 | auto programIndex = float_batch_type::load([0], 
xsimd::aligned_mode());
  | 
   ^~~~
  | 
   aligned_free

autopkgtest [18:16:18]: test command1



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

On 2022-07-01 13:20, Drew Parsons wrote:

Control: fixed 1014094 8.1.0-5

Fixed already in xsimd 8.1.0-5


i.e. this bug is done--- End Message ---

Bug#1014133: asterisk: Asterisk fails to build from source

[Bernhard Schmidt]

Control: severity -1 important
Control: found -1 1:16.16.1~dfsg-1
Control: fixed -1 1:16.16.1~dfsg+~2.10-1

Hi Ralf,

I am not very familiar with asterisk as packaged for Bullseye - only
know that it was pretty unusually done.

Maybe try build in a pristine build-environment.


What do you mean by this?


As Jonas already wrote, please use something like sbuild/cowbuilder. The 
packages for Bullseye have been built from source by the buildd, so 
generally they should work just fine.


I might have a look later, but since Jonas changed the packaging for 
Bullseye (in a way I don't grasp anymore :-) ) this is definitely not 
affecting the next release and it's definitely not stable-update 
material. So downgrading.


Bernhard

Processed: Re: Bug#1014133: asterisk: Asterisk fails to build from source

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #1014133 [asterisk] asterisk: Asterisk fails to build from source
Severity set to 'important' from 'serious'
> found -1 1:16.16.1~dfsg-1
Bug #1014133 [asterisk] asterisk: Asterisk fails to build from source
Marked as found in versions asterisk/1:16.16.1~dfsg-1.
> fixed -1 1:16.16.1~dfsg+~2.10-1
Bug #1014133 [asterisk] asterisk: Asterisk fails to build from source
Marked as fixed in versions asterisk/1:16.16.1~dfsg+~2.10-1.

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

Bug#1014094: xsimd: autopkgtest regression on i386: ‘any’ is not a member of ‘xsimd’

[Drew Parsons]

Control: fixed 1014094 8.1.0-5

Fixed already in xsimd 8.1.0-5

Processed: Re: Bug#1014094 xsimd: autopkgtest regression on i386: ‘any’ is not a member of ‘xsimd’

[Debian Bug Tracking System]

Processing control commands:

> fixed 1014094 8.1.0-5
Bug #1014094 [src:xsimd] xsimd: autopkgtest regression on i386: ‘any’ is not a 
member of ‘xsimd’
Marked as fixed in versions xsimd/8.1.0-5.

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

Bug#928224: patch

[Richard Earnshaw]

On Fri, 1 Jul 2022 11:54:58 +0200 Mathieu Malaterre 
wrote:

valgrind should apply the following patch:

sed -i -e 's/cortex-a8/generic-armv7-a+vfpv3-d16/g' Makefile.all.am




A better change would be

  sed -i -e 's/cortex-a8/generic-armv7-a/g' Makefile.all.am

There's no need for the fpu selection to be specified as generic-armv7-a
defaults to vfpv3-d16.

R.
IMPORTANT NOTICE: The contents of this email and any attachments are 
confidential and may also be privileged. If you are not the intended recipient, 
please notify the sender immediately and do not disclose the contents to any 
other person, use it for any purpose, or store or copy the information in any 
medium. Thank you.

Bug#1014091: armhf: gcc has wrong configuration

[Richard Earnshaw]

On 01/07/2022 10:58, Mathieu Malaterre wrote:

Hi Richard !




I've suggested valgrind people the following patch:

% sed -i -e 's/cortex-a8/generic-armv7-a+vfpv3-d16/g' Makefile.all.am

Hopefully my understanding is correct this time.



Pretty close, but  -mcpu=generic-armv7-a is actually enough, since this
selects armv7-a+fp as the architecture, and +fp is equivalent to
vfpv3-d16.  Furthermore, leaving off the +fp from the setting will
ensure better backwards compatibility with older versions of GCC (though
that's getting quite a long way back now, about GCC-7, IIRC).

R.
IMPORTANT NOTICE: The contents of this email and any attachments are 
confidential and may also be privileged. If you are not the intended recipient, 
please notify the sender immediately and do not disclose the contents to any 
other person, use it for any purpose, or store or copy the information in any 
medium. Thank you.

Processed: your mail

[Debian Bug Tracking System]

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

> reassign 928224 src:valgrind
Bug #928224 [valgrind] Valgrind is broken on armhf
Bug reassigned from package 'valgrind' to 'src:valgrind'.
No longer marked as found in versions valgrind/1:3.14.0-3.
Ignoring request to alter fixed versions of bug #928224 to the same values 
previously set
> forcemerge 928224 1014091
Bug #928224 [src:valgrind] Valgrind is broken on armhf
Bug #1014091 [src:valgrind] armhf: gcc has wrong configuration
Set Bug forwarded-to-address to 'https://bugs.kde.org/show_bug.cgi?id=456200'.
Severity set to 'grave' from 'serious'
928224 was blocked by: 1014091
928224 was blocking: 983377
Removed blocking bug(s) of 928224: 1014091
983377 was blocked by: 928224
983377 was not blocking any bugs.
Added blocking bug(s) of 983377: 1014091
Added tag(s) patch, confirmed, and upstream.
Merged 928224 1014091
>
End of message, stopping processing here.

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

Bug#1014091: armhf: gcc has wrong configuration

[Mathieu Malaterre]

Hi Richard !

On Thu, Jun 30, 2022 at 4:45 PM Richard Earnshaw
 wrote:
>
> I think the problem is valgrind's Makefiles are passing -mcpu=cortex-a8
> to the compiler.  Cortex-a8 has Neon and the compiler now makes use of that.
>
> On the subject of the configuration of GCC
>
> --with-arch=armv7-a+fp

Thanks for the quick response.

> *is* the correct configuration for the baseline GCC; it adds a vfpv3
> with 16 double-precision registers.  +vfpv3-fp16 would add support for
> the float16 load/store operations, while +nosimd is a nop because no
> other options have been added to enable SIMD.

I managed to misread the gcc arm options page (fp16 != d16). Thanks
for the explanation.

I've suggested valgrind people the following patch:

% sed -i -e 's/cortex-a8/generic-armv7-a+vfpv3-d16/g' Makefile.all.am

Hopefully my understanding is correct this time.

-M

Processed: your mail

[Debian Bug Tracking System]

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

> forwarded 928224 https://bugs.kde.org/show_bug.cgi?id=456200
Bug #928224 [valgrind] Valgrind is broken on armhf
Changed Bug forwarded-to-address to 
'https://bugs.kde.org/show_bug.cgi?id=456200' from 
'https://sourceforge.net/p/valgrind/mailman/message/37673816/'.
> tags 928224 upstream confirmed patch
Bug #928224 [valgrind] Valgrind is broken on armhf
Added tag(s) confirmed, patch, and upstream.
>
End of message, stopping processing here.

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

Bug#928224: patch

[Mathieu Malaterre]

valgrind should apply the following patch:

sed -i -e 's/cortex-a8/generic-armv7-a+vfpv3-d16/g' Makefile.all.am

Processed (with 1 error): your mail

[Debian Bug Tracking System]

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

> forcemerge 928224 1014091
Bug #928224 [valgrind] Valgrind is broken on armhf
Unable to merge bugs because:
package of #1014091 is 'src:valgrind' not 'valgrind'
Failed to forcibly merge 928224: Did not alter merged bugs.

>
End of message, stopping processing here.

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

Bug#1013310: jsonnet: FTBFS on several release architectures

[Daichi Fukui]

Hello Bastian,

Thanks for reporting this.
And apologies for a late reply.

To address this FTBFS issue, I uploaded the following changes to s
alsa.

  * fix FTBFS on several release architectures
  * fix FTBFS error on armel
  * Remove mipsel, mips64el, s390x as build target

For further information, kindly visit the following URL:
https://salsa.debian.org/dfukui/jsonnet/-/commits/debian/0.18.0+ds-2

If you don't mind, I would appreciate it if you sponsor and help me upload
this package.
The following are some technical comments.

According to the original source code [0], c4core does not support the
following CPU architectures:
s390x, mipsel, mips64el
Thus, we should drop these ones from the Architecture field on d/control.

Meanwhile, debugbreak should have been successfully built by falling back
to raising SIGTRAP [1] for several architectures, but build fails due to a
bug in upstream.
This issue has already been addressed [2], so a patch [3] was created and
added to d/patches based on upstream. In a similar story, I fixed FTBFS on
armel and filed a patch [4].

Thanks for reading.

[0]
https://github.com/biojppm/c4core/blob/52f3ff57b287ce57c2bbf80dc091bd21e4d9f977/src/c4/cpu.hpp
[1]
https://github.com/google/jsonnet/blob/v0.18.0/third_party/rapidyaml/rapidyaml/ext/c4core/src/c4/ext/debugbreak/debugbreak.h#L123
[2]
https://github.com/scottt/debugbreak/commit/8b4a755e76717103adc814c0c05ceb3b91befa7d
[3]
https://salsa.debian.org/dfukui/jsonnet/-/commit/1bea08d549c450b8c9624e686df88f025e1d3d5c
[4]
https://salsa.debian.org/dfukui/jsonnet/-/commit/efb346e3ec210104897c38979291ab68e1eead73

Best,
Fukui

Bug#1004830: marked as done (gerbera: FTBFS with ffmpeg 5.0)

[Debian Bug Tracking System]

Your message dated Fri, 01 Jul 2022 09:05:00 +
with message-id 
and subject line Bug#1004830: fixed in gerbera 1.1.0+dfsg-3.1
has caused the Debian Bug report #1004830,
regarding gerbera: FTBFS with ffmpeg 5.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.)


-- 
1004830: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004830
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gerbera
Version: 1.1.0+dfsg-3
Severity: important
X-Debbugs-Cc: sramac...@debian.org
Tags: sid bookworm ftbfs
Usertags: ffmpeg5.0

gerbera FTBFS with ffmpeg 5.0 in experimental:

/usr/lib/ccache/c++ -DAUTO_CREATE_DATABASE -DEXTEND_PROTOCOLINFO 
-DEXTERNAL_TRANSCODING -DHAVE_AVSTREAM_CODECPAR -DHAVE_CURL -DHAVE_EXIV2 
-DHAVE_FFMPEG -DHAVE_FFMPEGTHUMBNAILER -DHAVE_INOTIFY -DHAVE_JS -DHAVE_LIBEXIF 
-DHAVE_MAGIC -DHAVE_MYSQL -DHAVE_NL_LANGINFO -DHAVE_SETLOCALE -DHAVE_SQLITE3 
-DHAVE_TAGLIB -DONLINE_SERVICES -DPACKAGE_DATADIR=\"/usr/share/gerbera\" 
-DPACKAGE_NAME=\"gerbera\" -DTOMBDEBUG -DVERSION=\"1.1.0\" -DYOUTUBE 
-D__FILENAME__=\"src/metadata/taglib_handler.cc\" -I/<>/src 
-I/usr/include/upnp -I/usr/include/mysql -I/usr/include/libexif 
-I/usr/include/exiv2 -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wall -std=c++14 -MD -MT 
CMakeFiles/libgerbera.dir/src/metadata/taglib_handler.cc.o -MF 
CMakeFiles/libgerbera.dir/src/metadata/taglib_handler.cc.o.d -o 
CMakeFiles/libgerbera.dir/src/metadata/taglib_handler.cc.o -c 
/<>/src/metadata/taglib_handler.cc
/<>/src/metadata/ffmpeg_handler.cc: In member function ‘virtual 
void FfmpegHandler::fillMetadata(zmm::Ref)’:
/<>/src/metadata/ffmpeg_handler.cc:233:5: error: ‘av_register_all’ 
was not declared in this scope
  233 | av_register_all();
  | ^~~
make[3]: *** [CMakeFiles/libgerbera.dir/build.make:541: 
CMakeFiles/libgerbera.dir/src/metadata/ffmpeg_handler.cc.o] Error 1
make[3]: *** Waiting for unfinished jobs
/<>/src/metadata/taglib_handler.cc: In member function ‘virtual 
zmm::Ref TagLibHandler::serveContent(zmm::Ref, int, 
off_t*)’:
/<>/src/metadata/taglib_handler.cc:307:41: warning: 
‘TagLib::MP4::ItemListMap’ is deprecated [-Wdeprecated-declarations]
  307 | const TagLib::MP4::ItemListMap& itemsListMap = 
f.tag()->itemListMap();
  | ^~~~
In file included from /usr/include/taglib/mp4file.h:33,
 from /<>/src/metadata/taglib_handler.cc:45:
/usr/include/taglib/mp4tag.h:45:57: note: declared here
   45 | TAGLIB_DEPRECATED typedef TagLib::Map ItemListMap;
  | ^~~
/<>/src/metadata/taglib_handler.cc:307:76: warning: 
‘TagLib::MP4::ItemMap& TagLib::MP4::Tag::itemListMap()’ is deprecated 
[-Wdeprecated-declarations]
  307 | const TagLib::MP4::ItemListMap& itemsListMap = 
f.tag()->itemListMap();
  |
^~
In file included from /usr/include/taglib/mp4file.h:33,
 from /<>/src/metadata/taglib_handler.cc:45:
/usr/include/taglib/mp4tag.h:77:36: note: declared here
   77 | TAGLIB_DEPRECATED ItemMap ();
  |^~~
/<>/src/metadata/taglib_handler.cc: In member function ‘void 
TagLibHandler::extractMP4(TagLib::IOStream*, zmm::Ref)’:
/<>/src/metadata/taglib_handler.cc:573:30: warning: 
‘TagLib::MP4::ItemListMap’ is deprecated [-Wdeprecated-declarations]
  573 | TagLib::MP4::ItemListMap itemsListMap = mp4.tag()->itemListMap();
  |  ^~~~
In file included from /usr/include/taglib/mp4file.h:33,
 from /<>/src/metadata/taglib_handler.cc:45:
/usr/include/taglib/mp4tag.h:45:57: note: declared here
   45 | TAGLIB_DEPRECATED typedef TagLib::Map ItemListMap;
  | ^~~
/<>/src/metadata/taglib_handler.cc:573:67: warning: 
‘TagLib::MP4::ItemMap& TagLib::MP4::Tag::itemListMap()’ is deprecated 
[-Wdeprecated-declarations]
  573 | TagLib::MP4::ItemListMap itemsListMap = mp4.tag()->itemListMap();
  | ~~^~
In file included from /usr/include/taglib/mp4file.h:33,
 from /<>/src/metadata/taglib_handler.cc:45:
/usr/include/taglib/mp4tag.h:77:36: note: declared here
   77 | TAGLIB_DEPRECATED ItemMap ();
  |^~~
make[3]: Leaving directory 

Bug#1004815: marked as done (qtox: FTBFS with ffmpeg 5.0)

[Debian Bug Tracking System]

Your message dated Fri, 01 Jul 2022 09:05:09 +
with message-id 
and subject line Bug#1004815: fixed in qtox 1.17.6-0.1
has caused the Debian Bug report #1004815,
regarding qtox: FTBFS with ffmpeg 5.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.)


-- 
1004815: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004815
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qtox
Version: 1.17.4-1
Severity: important
X-Debbugs-Cc: sramac...@debian.org
Tags: sid bookworm ftbfs
Usertags: ffmpeg5.

qtox FTBFS with ffmpeg 5.0 in experimental:

[ 32%] Building CXX object 
CMakeFiles/qtox_static.dir/src/video/genericnetcamview.cpp.o
/usr/lib/ccache/c++ -DDESKTOP_NOTIFICATIONS=0 
-DGIT_DESCRIBE=\"v1.17.4-1-debian\" -DGIT_VERSION="\"build without git\"" 
-DLOG_TO_FILE=1 -DQTOX_PLATFORM_EXT -DQT_CORE_LIB -DQT_GUI_LIB 
-DQT_MESSAGELOGCONTEXT=1 -DQT_NETWORK_LIB -DQT_NO_DEBUG -DQT_OPENGL_LIB 
-DQT_SVG_LIB -DQT_WIDGETS_LIB -DQT_XML_LIB -DSPELL_CHECKING 
-I/<>/obj-x86_64-linux-gnu/qtox_static_autogen/include 
-I/<>/obj-x86_64-linux-gnu -I/<> 
-I/usr/include/sqlcipher -I/usr/include/opus -I/usr/include/AL -isystem 
/usr/include/x86_64-linux-gnu/qt5 -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtCore -isystem 
/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtOpenGL -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtSvg -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtXml -isystem /usr/include/KF5/SonnetUi 
-isystem /usr/include/KF5 -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wall -pedantic 
-Wdate-time -D_FORTIFY_SOURCE=2 -std=c++11 -fno-exceptions -fno-rtti 
-Wstrict-overflow -Wstrict-aliasing -Wdate-time -fstack-protector-all 
-Wstack-protector -fPIC -MD -MT 
CMakeFiles/qtox_static.dir/src/video/genericnetcamview.cpp.o -MF 
CMakeFiles/qtox_static.dir/src/video/genericnetcamview.cpp.o.d -o 
CMakeFiles/qtox_static.dir/src/video/genericnetcamview.cpp.o -c 
/<>/src/video/genericnetcamview.cpp
/<>/src/video/cameradevice.cpp: In static member function ‘static 
bool CameraDevice::getDefaultInputFormat()’:
/<>/src/video/cameradevice.cpp:515:42: error: invalid conversion 
from ‘const AVInputFormat*’ to ‘AVInputFormat*’ [-fpermissive]
  515 | idesktopFormat = av_find_input_format("x11grab");
  |  ^~~
  |  |
  |  const AVInputFormat*
/<>/src/video/cameradevice.cpp:523:40: error: invalid conversion 
from ‘const AVInputFormat*’ to ‘AVInputFormat*’ [-fpermissive]
  523 | if ((iformat = av_find_input_format("v4l2")))
  |^~~~
  ||
  |const AVInputFormat*
make[3]: *** [CMakeFiles/qtox_static.dir/build.make:4225: 
CMakeFiles/qtox_static.dir/src/video/cameradevice.cpp.o] Error 1
make[3]: *** Waiting for unfinished jobs
/<>/src/video/camerasource.cpp: In member function ‘void 
CameraSource::openDevice()’:
/<>/src/video/camerasource.cpp:324:33: error: invalid conversion 
from ‘const AVCodec*’ to ‘AVCodec*’ [-fpermissive]
  324 | codec = avcodec_find_decoder(codecId);
  | ^
  | |
  | const AVCodec*
make[3]: *** [CMakeFiles/qtox_static.dir/build.make:4239: 
CMakeFiles/qtox_static.dir/src/video/camerasource.cpp.o] Error 1

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: qtox
Source-Version: 1.17.6-0.1
Done: Nicholas Guriev 

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

Debian distribution maintenance software
pp.
Nicholas Guriev  (supplier of updated qtox 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 

Processed: aubio: diff for NMU version 0.4.9-4.2

[Debian Bug Tracking System]

Processing control commands:

> tags 1004787 + patch
Bug #1004787 {Done: IOhannes m zmölnig (Debian/GNU) } 
[src:aubio] aubio: FTBFS with ffmpeg 5.0
Added tag(s) patch.
> tags 1004787 + pending
Bug #1004787 {Done: IOhannes m zmölnig (Debian/GNU) } 
[src:aubio] aubio: FTBFS with ffmpeg 5.0
Added tag(s) pending.

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

Bug#1004787: aubio: diff for NMU version 0.4.9-4.2

[IOhannes m zmölnig]

Control: tags 1004787 + patch
Control: tags 1004787 + pending

Dear maintainer,

I've prepared an NMU for aubio (versioned as 0.4.9-4.2) and
uploaded it to DELAYED/0 (:facepalm:, that was actually unintentional, but i
guess it's too late now). Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru aubio-0.4.9/debian/changelog aubio-0.4.9/debian/changelog
--- aubio-0.4.9/debian/changelog	2021-09-09 20:11:53.0 +0200
+++ aubio-0.4.9/debian/changelog	2022-06-30 22:35:01.0 +0200
@@ -1,3 +1,12 @@
+aubio (0.4.9-4.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add patch to build against ffmpeg-5.0 (Closes: #1004787)
+  * Add salsa-ci configuration
+  * Call dh_numpy3 to add dependency on numpy abi
+
+ -- IOhannes m zmölnig (Debian/GNU)   Thu, 30 Jun 2022 22:35:01 +0200
+
 aubio (0.4.9-4.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru aubio-0.4.9/debian/patches/ffmpeg5.patch aubio-0.4.9/debian/patches/ffmpeg5.patch
--- aubio-0.4.9/debian/patches/ffmpeg5.patch	1970-01-01 01:00:00.0 +0100
+++ aubio-0.4.9/debian/patches/ffmpeg5.patch	2022-06-30 22:35:01.0 +0200
@@ -0,0 +1,20 @@
+Description: Fix compilation with ffmpeg-5.0
+Author: Paul Brossier
+Origin: upstream
+Applied-Upstream: https://github.com/aubio/aubio/commit/8a05420e5dd8c7b8b2447f82dc919765876511b3
+Last-Update: 2022-06-30
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- aubio.orig/src/io/source_avcodec.c
 aubio/src/io/source_avcodec.c
+@@ -68,6 +68,10 @@
+ #define AUBIO_AVCODEC_MAX_BUFFER_SIZE AV_INPUT_BUFFER_MIN_SIZE
+ #endif
+ 
++#if LIBAVCODEC_VERSION_MAJOR >= 59
++#define FF_API_LAVF_AVCTX 1
++#endif
++
+ struct _aubio_source_avcodec_t {
+   uint_t hop_size;
+   uint_t samplerate;
diff -Nru aubio-0.4.9/debian/patches/series aubio-0.4.9/debian/patches/series
--- aubio-0.4.9/debian/patches/series	2020-01-04 19:53:25.0 +0100
+++ aubio-0.4.9/debian/patches/series	2022-06-30 22:35:01.0 +0200
@@ -3,3 +3,4 @@
 fixpowerpc.patch
 fixi386.patch
 wscript_py3.patch
+ffmpeg5.patch
diff -Nru aubio-0.4.9/debian/rules aubio-0.4.9/debian/rules
--- aubio-0.4.9/debian/rules	2020-01-08 13:04:19.0 +0100
+++ aubio-0.4.9/debian/rules	2022-06-30 22:35:01.0 +0200
@@ -59,4 +59,4 @@
 	# python extension
 	dh_auto_install --buildsystem=pybuild
 	# call dh_numpy to add dependency on numpy abi
-	if [ -x /usr/bin/dh_numpy ]; then dh_numpy; fi
+	if [ -x /usr/bin/dh_numpy3 ]; then dh_numpy3; fi
diff -Nru aubio-0.4.9/debian/salsa-ci.yml aubio-0.4.9/debian/salsa-ci.yml
--- aubio-0.4.9/debian/salsa-ci.yml	1970-01-01 01:00:00.0 +0100
+++ aubio-0.4.9/debian/salsa-ci.yml	2022-06-30 22:35:01.0 +0200
@@ -0,0 +1,4 @@
+---
+include:
+  - https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/salsa-ci.yml
+  - https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/pipeline-jobs.yml

Bug#1004787: marked as done (aubio: FTBFS with ffmpeg 5.0)

[Debian Bug Tracking System]

Your message dated Fri, 01 Jul 2022 06:50:20 +
with message-id 
and subject line Bug#1004787: fixed in aubio 0.4.9-4.2
has caused the Debian Bug report #1004787,
regarding aubio: FTBFS with ffmpeg 5.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.)


-- 
1004787: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004787
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: aubio
Version: 0.4.9-4.1
Severity: important
X-Debbugs-Cc: sramac...@debian.org
Tags: sid bookworm ftbfs
Usertags: ffmpeg5.0

aubio FTBFS with ffmpeg 5.0 in experimental:

[ 66/232] Compiling tests/src/io/test-sink_wavwrite.c
14:59:53 runner ['/usr/lib/ccache/gcc', '-g', '-Wall', '-Wextra', '-O2', '-g', 
'-O2', '-ffile-prefix-map=/<>=.', '-fstack-protector-strong', 
'-Wformat', '-Werror=format-security', '-fPIC', '-Isrc', '-I../src', '-Itests', 
'-I../tests', '-I/usr/include/opus', '-I/usr/include/x86_64-linux-gnu', 
'-DHAVE_CONFIG_H=1', '-DAUBIO_PREFIX="/usr"', '-DPACKAGE="aubio"', 
'-DAUBIO_UNSTABLE_API=1', 
'-DAUBIO_TESTS_SOURCE=/<>/build/tests/44100Hz_44100f_sine441_stereo.wav',
 '../tests/src/io/test-sink_wavwrite.c', '-c', 
'-o/<>/build/tests/src/io/test-sink_wavwrite.c.5.o', 
'-Wdate-time', '-D_FORTIFY_SOURCE=2']
../src/io/source_avcodec.c: In function ‘new_aubio_source_avcodec’:
../src/io/source_avcodec.c:195:32: error: ‘AVStream’ has no member named ‘codec’
  195 | if (avFormatCtx->streams[i]->codec->codec_type == 
AVMEDIA_TYPE_AUDIO) {
  |^~
../src/io/source_avcodec.c:229:53: error: ‘AVStream’ has no member named ‘codec’
  229 |   avCodecCtx = avFormatCtx->streams[selected_stream]->codec;
  | ^~
../src/io/source_avcodec.c:230:9: warning: assignment discards ‘const’ 
qualifier from pointer target type [-Wdiscarded-qualifiers]
  230 |   codec = avcodec_find_decoder(avCodecCtx->codec_id);
  | ^
../src/io/source_avcodec.c: In function ‘aubio_source_avcodec_readframe’:
../src/io/source_avcodec.c:381:3: warning: ‘av_init_packet’ is deprecated 
[-Wdeprecated-declarations]
  381 |   av_init_packet ();
  |   ^~
In file included from /usr/include/x86_64-linux-gnu/libavcodec/avcodec.h:45,
 from ../src/io/source_avcodec.c:25:
/usr/include/x86_64-linux-gnu/libavcodec/packet.h:506:6: note: declared here
  506 | void av_init_packet(AVPacket *pkt);
  |  ^~
../src/io/source_avcodec.c:425:9: warning: implicit declaration of function 
‘avcodec_decode_audio4’; did you mean ‘avcodec_decode_subtitle2’? 
[-Wimplicit-function-declaration]
  425 |   len = avcodec_decode_audio4(avCodecCtx, avFrame, _frame, 
);
  | ^
  | avcodec_decode_subtitle2

Waf: Leaving directory `/<>/build'
Build failed
 -> task in 'lib_objects' failed with exit status 1: 
{task 140115336892592: c source_avcodec.c -> source_avcodec.c.1.o}
['/usr/lib/ccache/gcc', '-g', '-Wall', '-Wextra', '-O2', '-g', '-O2', 
'-ffile-prefix-map=/<>=.', '-fstack-protector-strong', '-Wformat', 
'-Werror=format-security', '-fPIC', '-Isrc', '-I../src', '-I/usr/include/opus', 
'-I/usr/include/x86_64-linux-gnu', '-DHAVE_CONFIG_H=1', 
'-DAUBIO_PREFIX="/usr"', '-DPACKAGE="aubio"', '../src/io/source_avcodec.c', 
'-c', '-o/<>/build/src/io/source_avcodec.c.1.o', '-Wdate-time', 
'-D_FORTIFY_SOURCE=2']
make[1]: *** [debian/rules:48: override_dh_auto_build] Error 1


Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: aubio
Source-Version: 0.4.9-4.2
Done: IOhannes m zmölnig (Debian/GNU) 

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

Debian distribution maintenance software
pp.
IOhannes m zmölnig (Debian/GNU)  (supplier of updated 
aubio 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: Thu, 30 Jun 2022 22:35:01 +0200
Source: aubio
Architecture: source
Version: 0.4.9-4.2
Distribution: unstable
Urgency: medium
Maintainer: Paul