Processed: severity of 1013903 is serious

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:

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

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

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

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

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

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

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

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+)

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

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

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

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

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

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)

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

Bug#832116: music assets

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

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

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

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

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. >

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

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

Bug#1014115: uninstall does not properly remove enablement symlinks

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

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

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

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

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

Processed: pyranges ftbfs unreproducible, possibly caused by timeout

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

Processed (with 1 error): forcibly merging 1014081 1014077

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

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

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

Bug#1013704: closing 1013704

close 1013704 1.5.26+ds-1 thanks Hi, I believe this bug has been fixed with the new upstream version. Cheers Timo -- ⢀⣴⠾⠻⢶⣦⠀

Processed: closing 1013704

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

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

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

Bug#1014187: fruit: Binary file inside package

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]

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

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

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

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

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

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'

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

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

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

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

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

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]

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

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: )

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

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

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

Bug#1013472: reassign to openssl package

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

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

Processed: Re: reassign to openssl package

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

Processed: reassign to openssl package

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

Processed: reassign to openssl package

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Bug#1014179: pytango FTBFS on IPV6-only buildds

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

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

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

Bug#1013310: jsonnet: FTBFS on several release architectures

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

Bug#1014166: bitcoin: CVE-2021-31876

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

Processed: your mail

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

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

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

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

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

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

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

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

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’

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

Bug#928224: patch

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

Bug#1014091: armhf: gcc has wrong configuration

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

Processed: your mail

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

Bug#1014091: armhf: gcc has wrong configuration

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

Processed: your mail

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

Bug#928224: patch

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

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,

Bug#1013310: jsonnet: FTBFS on several release architectures

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

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

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

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

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

Processed: aubio: diff for NMU version 0.4.9-4.2

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

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

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

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

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