suil_0.10.12-1_source.changes ACCEPTED into unstable

2022-05-30 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 30 May 2022 23:51:07 +0200 Source: suil Architecture: source Version: 0.10.12-1 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Dennis Braun Changes: suil (0.10.12-1

Processing of suil_0.10.12-1_source.changes

2022-05-30 Thread Debian FTP Masters
suil_0.10.12-1_source.changes uploaded successfully to localhost along with the files: suil_0.10.12-1.dsc suil_0.10.12.orig.tar.bz2 suil_0.10.12.orig.tar.bz2.asc suil_0.10.12-1.debian.tar.xz suil_0.10.12-1_source.buildinfo Greetings, Your Debian queue daemon (running on host usp

serd_0.30.12-1_source.changes ACCEPTED into unstable

2022-05-30 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 30 May 2022 23:18:52 +0200 Source: serd Architecture: source Version: 0.30.12-1 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Dennis Braun Changes: serd (0.30.12-1

Processing of serd_0.30.12-1_source.changes

2022-05-30 Thread Debian FTP Masters
serd_0.30.12-1_source.changes uploaded successfully to localhost along with the files: serd_0.30.12-1.dsc serd_0.30.12.orig.tar.bz2 serd_0.30.12.orig.tar.bz2.asc serd_0.30.12-1.debian.tar.xz serd_0.30.12-1_source.buildinfo Greetings, Your Debian queue daemon (running on host usp

Processed: tagging 1012138

2022-05-30 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1012138 + upstream Bug #1012138 [src:sox] CVE-2021-40426 Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 1012138: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012138 Debian Bug Tr

Processed: Bug#935590 marked as pending in opusfile

2022-05-30 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #935590 [libopusfile0] libopusfile0: Please make multi-arch co-installable Added tag(s) pending. -- 935590: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935590 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1012138: CVE-2021-40426

2022-05-30 Thread Moritz Muehlenhoff
Source: sox Version: 14.4.2+git20190427-3 Severity: grave Tags: security X-Debbugs-Cc: Debian Security Team https://talosintelligence.com/vulnerability_reports/TALOS-2021-1434 The report states that upstream was notified, but we need to figure out whether this was addressed by upstream already o

Processed: Re: Bug#935590: libopusfile0: Please make multi-arch co-installable

2022-05-30 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + patch Bug #935590 [libopusfile0] libopusfile0: Please make multi-arch co-installable Ignoring request to alter tags of bug #935590 to the same tags previously set -- 935590: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935590 Debian Bug Tracking Syst

Bug#935590: libopusfile0: Please make multi-arch co-installable

2022-05-30 Thread Simon McVittie
Control: tags -1 + patch On Mon, 30 May 2022 at 17:33:37 +0100, Simon McVittie wrote: > On Sat, 24 Aug 2019 at 11:43:35 +0100, Simon McVittie wrote: > > libopusfile0 and libopusfile-dev are not Multi-Arch co-installable > > This is still the case as of 0.12-1: Helmut's patch from #899138 has > be

Processed: reopening 935590, found 935590 in 0.12-1

2022-05-30 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reopen 935590 Bug #935590 {Done: IOhannes m zmölnig (Debian/GNU) } [libopusfile0] libopusfile0: Please make multi-arch co-installable 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and

Bug#935590: libopusfile0: Please make multi-arch co-installable

2022-05-30 Thread Simon McVittie
Control: reopen -1 0.12-1 On Sat, 24 Aug 2019 at 11:43:35 +0100, Simon McVittie wrote: > libopusfile0 and libopusfile-dev are not Multi-Arch co-installable This is still the case as of 0.12-1: Helmut's patch from #899138 has been applied but my follow-up has not. I'll send a tested patch when I h

Bug#1012110: multimedia-devel: Recommended package libart-2.0-dev is no longer a relevant recommendation

2022-05-30 Thread Bastian Germann
Package: multimedia-devel Version: 0.10 Severity: minor Please remove the deprecated (see #895349) recommendation libart-2.0-dev.

opusfile_0.12-1_source.changes ACCEPTED into unstable

2022-05-30 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 30 May 2022 11:22:59 +0200 Source: opusfile Architecture: source Version: 0.12-1 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: IOhannes m zmölnig (Debian/GNU) Close

Processing of opusfile_0.12-1_source.changes

2022-05-30 Thread Debian FTP Masters
opusfile_0.12-1_source.changes uploaded successfully to localhost along with the files: opusfile_0.12-1.dsc opusfile_0.12-1.debian.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org)

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

2022-05-30 Thread Debian Bug Tracking System
Your message dated Mon, 30 May 2022 09:50:08 + with message-id and subject line Bug#965762: fixed in opusfile 0.12-1 has caused the Debian Bug report #965762, regarding opusfile: Removal of obsolete debhelper compat 5 and 6 in bookworm to be marked as done. This means that you claim that the

Bug#935591: marked as done (libopusfile0: new upstream version 0.11 available)

2022-05-30 Thread Debian Bug Tracking System
Your message dated Mon, 30 May 2022 09:50:08 + with message-id and subject line Bug#935591: fixed in opusfile 0.12-1 has caused the Debian Bug report #935591, regarding libopusfile0: new upstream version 0.11 available to be marked as done. This means that you claim that the problem has been

Bug#923031: marked as done (opusfile: updated package (new upstream, multiarch-capable, etc.))

2022-05-30 Thread Debian Bug Tracking System
Your message dated Mon, 30 May 2022 09:50:08 + with message-id and subject line Bug#923031: fixed in opusfile 0.12-1 has caused the Debian Bug report #923031, regarding opusfile: updated package (new upstream, multiarch-capable, etc.) to be marked as done. This means that you claim that the p

Bug#935590: marked as done (libopusfile0: Please make multi-arch co-installable)

2022-05-30 Thread Debian Bug Tracking System
Your message dated Mon, 30 May 2022 09:50:08 + with message-id and subject line Bug#935590: fixed in opusfile 0.12-1 has caused the Debian Bug report #935590, regarding libopusfile0: Please make multi-arch co-installable to be marked as done. This means that you claim that the problem has bee

Bug#899138: marked as done (libopusfile-dev: move opusfile.pc to a multiarch location)

2022-05-30 Thread Debian Bug Tracking System
Your message dated Mon, 30 May 2022 09:50:08 + with message-id and subject line Bug#899138: fixed in opusfile 0.12-1 has caused the Debian Bug report #899138, regarding libopusfile-dev: move opusfile.pc to a multiarch location to be marked as done. This means that you claim that the problem h

Bug#881788: marked as done (opusfile: please make the build reproducible)

2022-05-30 Thread Debian Bug Tracking System
Your message dated Mon, 30 May 2022 09:50:08 + with message-id and subject line Bug#881788: fixed in opusfile 0.12-1 has caused the Debian Bug report #881788, regarding opusfile: please make the build reproducible to be marked as done. This means that you claim that the problem has been dealt

Bug#1007053: marked as done (opusfile: please consider upgrading to 3.0 source format)

2022-05-30 Thread Debian Bug Tracking System
Your message dated Mon, 30 May 2022 09:50:08 + with message-id and subject line Bug#1007053: fixed in opusfile 0.12-1 has caused the Debian Bug report #1007053, regarding opusfile: please consider upgrading to 3.0 source format to be marked as done. This means that you claim that the problem

Bug#1009854: marked as done (ITS: opusfile)

2022-05-30 Thread Debian Bug Tracking System
Your message dated Mon, 30 May 2022 09:50:08 + with message-id and subject line Bug#1009854: fixed in opusfile 0.12-1 has caused the Debian Bug report #1009854, regarding ITS: opusfile to be marked as done. This means that you claim that the problem has been dealt with. If this is not the cas

Processed: merging 1009854 1011231

2022-05-30 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > merge 1009854 1011231 Bug #1009854 {Done: IOhannes m zmölnig (Debian/GNU) } [src:opusfile] ITS: opusfile Bug #1011231 {Done: IOhannes m zmölnig (Debian/GNU) } [src:opusfile] opusfile: diff for NMU version 0.12-1~exp1 Marked as fixed in versions

Processed: severity of 1011231 is important

2022-05-30 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1011231 important Bug #1011231 {Done: IOhannes m zmölnig (Debian/GNU) } [src:opusfile] opusfile: diff for NMU version 0.12-1~exp1 Severity set to 'important' from 'normal' > thanks Stopping processing here. Please contact me if you need

Processed: reassign 1011231 to src:opusfile

2022-05-30 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1011231 src:opusfile Bug #1011231 {Done: IOhannes m zmölnig (Debian/GNU) } [opusfile] opusfile: diff for NMU version 0.12-1~exp1 Bug reassigned from package 'opusfile' to 'src:opusfile'. No longer marked as found in versions 0.9+20170913

Processed: notfixed 990562 in 2:7.0~rc4-1, fixed 990562 in 1:7.0~rc4-1, tagging 965762, tagging 1012083

2022-05-30 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > notfixed 990562 2:7.0~rc4-1 Bug #990562 {Done: Michael Tokarev } [src:qemu] qemu: CVE-2021-3611: intel-hda: segmentation fault due to stack overflow The source 'qemu' and version '2:7.0~rc4-1' do not appear to match any binary packages No longer