sonic-pi is marked for autoremoval from testing

sonic-pi 3.2.2~repack-8 is marked for autoremoval from testing on 2022-11-14 It (build-)depends on packages with these RC bugs: 1019995: supercollider: FTBFS: sndfile.h:356:33: error: conflicting declaration ‘typedef struct sf_private_tag SNDFILE’ https://bugs.debian.org/1019995 This mail

easyeffects is marked for autoremoval from testing

easyeffects 6.3.0-1 is marked for autoremoval from testing on 2022-11-13 It (build-)depends on packages with these RC bugs: 1020046: slimit: FTBFS: ModuleNotFoundError: No module named 'minifier' https://bugs.debian.org/1020046 This mail is generated by: https://salsa.debian.org/release-team/r

calf is marked for autoremoval from testing

calf 0.90.3-3 is marked for autoremoval from testing on 2022-11-13 It (build-)depends on packages with these RC bugs: 1020046: slimit: FTBFS: ModuleNotFoundError: No module named 'minifier' https://bugs.debian.org/1020046 This mail is generated by: https://salsa.debian.org/release-team/release

supercollider is marked for autoremoval from testing

supercollider 1:3.11.2+repack-1 is marked for autoremoval from testing on 2022-11-01 It is affected by these RC bugs: 1019995: supercollider: FTBFS: sndfile.h:356:33: error: conflicting declaration ‘typedef struct sf_private_tag SNDFILE’ https://bugs.debian.org/1019995 This mail is gener

dgedit is marked for autoremoval from testing

dgedit 0.10.0-1 is marked for autoremoval from testing on 2022-10-30 It is affected by these RC bugs: 1020034: dgedit: FTBFS: gcc: error: unrecognized command-line option '-V' https://bugs.debian.org/1020034 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/

supercollider-sc3-plugins is marked for autoremoval from testing

supercollider-sc3-plugins 3.9.1~repack-4 is marked for autoremoval from testing on 2022-11-01 It (build-)depends on packages with these RC bugs: 1019995: supercollider: FTBFS: sndfile.h:356:33: error: conflicting declaration ‘typedef struct sf_private_tag SNDFILE’ https://bugs.debian.org/10

setbfree_0.8.11-3_source.changes REJECTED

Version check failed: Your upload included the source package setbfree, version 0.8.11-3, however unstable already has version 0.8.11-3. Uploads to unstable must have a higher version than present in unstable. === Please feel free to respond to this email if you don't understand why your fil

Processing of setbfree_0.8.11-3_source.changes

setbfree_0.8.11-3_source.changes uploaded successfully to localhost along with the files: setbfree_0.8.11-3.dsc setbfree_0.8.11-3.debian.tar.xz setbfree_0.8.11-3_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

zita-dc1_0.3.3-2_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 16 Oct 2022 22:53:05 +0200 Source: zita-dc1 Architecture: source Version: 0.3.3-2 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Dennis Braun Closes: 1003392 Changes

setbfree_0.8.11-3_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 16 Oct 2022 22:55:34 +0200 Source: setbfree Architecture: source Version: 0.8.11-3 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Dennis Braun Closes: 1021841 Change

Bug#1021841: marked as done (setbfree FTCBFS -- multiple reasons)

Your message dated Sun, 16 Oct 2022 21:20:55 + with message-id and subject line Bug#1021841: fixed in setbfree 0.8.11-3 has caused the Debian Bug report #1021841, regarding setbfree FTCBFS -- multiple reasons to be marked as done. This means that you claim that the problem has been dealt with

Bug#1003392: marked as done (zita-dc1 FTCBFS: uses build architecture tools)

Your message dated Sun, 16 Oct 2022 21:22:15 + with message-id and subject line Bug#1003392: fixed in zita-dc1 0.3.3-2 has caused the Debian Bug report #1003392, regarding zita-dc1 FTCBFS: uses build architecture tools to be marked as done. This means that you claim that the problem has been

Processing of zita-dc1_0.3.3-2_source.changes

zita-dc1_0.3.3-2_source.changes uploaded successfully to localhost along with the files: zita-dc1_0.3.3-2.dsc zita-dc1_0.3.3-2.debian.tar.xz zita-dc1_0.3.3-2_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

Processing of setbfree_0.8.11-3_source.changes

setbfree_0.8.11-3_source.changes uploaded successfully to localhost along with the files: setbfree_0.8.11-3.dsc setbfree_0.8.11-3.debian.tar.xz setbfree_0.8.11-3_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

Bug#1021901: ardour: Ardour 7.0.0 out :)

Package: ardour Version: 1:6.9.0+ds0-2+b1 Severity: wishlist Dear Maintainer, In case you didn't notice yet, Ardour 7.0.0 has been released on October 15th. Since I wanted to give it a go, I thought I'd try to upgrade to the last upstream release. So I created a MR on salsa for you to review: h

Processed: Bug#1021841 marked as pending in setbfree

Processing control commands: > tag -1 pending Bug #1021841 [setbfree] setbfree FTCBFS -- multiple reasons Added tag(s) pending. -- 1021841: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021841 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

liblc3_1.0.1-1_amd64.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 10 Oct 2022 22:59:57 +0200 Source: liblc3 Binary: liblc3-0 liblc3-0-dbgsym liblc3-dev liblc3-tools liblc3-tools-dbgsym Architecture: source amd64 Version: 1.0.1-1 Distribution: unstable Urgency: medium Maintainer:

libde265_1.0.8-1.1_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 16 Oct 2022 15:26:20 +0200 Source: libde265 Architecture: source Version: 1.0.8-1.1 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Philipp Kern Closes: 1014977 Chang

Bug#1014977: marked as done (libde265: CVE-2022-1253 CVE-2021-36411 CVE-2021-36410 CVE-2021-36408 CVE-2021-35452)

Your message dated Sun, 16 Oct 2022 15:35:49 + with message-id and subject line Bug#1014977: fixed in libde265 1.0.8-1.1 has caused the Debian Bug report #1014977, regarding libde265: CVE-2022-1253 CVE-2021-36411 CVE-2021-36410 CVE-2021-36408 CVE-2021-35452 to be marked as done. This means t

Processing of libde265_1.0.8-1.1_source.changes

libde265_1.0.8-1.1_source.changes uploaded successfully to localhost along with the files: libde265_1.0.8-1.1.dsc libde265_1.0.8-1.1.debian.tar.xz libde265_1.0.8-1.1_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

Processed: tagging 1014977

Processing commands for cont...@bugs.debian.org: > tags 1014977 + pending Bug #1014977 [src:libde265] libde265: CVE-2022-1253 CVE-2021-36411 CVE-2021-36410 CVE-2021-36408 CVE-2021-35452 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1014977

Bug#1014977: libde265: CVE-2022-1253 CVE-2021-36411 CVE-2021-36410 CVE-2021-36408 CVE-2021-35452

tags -1 + pending thanks Hey Moritz, On Fri, Jul 15, 2022 at 05:48:41PM +0200, Moritz Mühlenhoff wrote: > The following vulnerabilities were published for libde265. [...] Thanks for clearly linking to the upstream commits, that was very helpful! Compared to the older bug these were quite straigh