xcfa_5.0.2-1.1_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 05 Feb 2021 13:03:24 +0200 Source: xcfa Architecture: source Version: 5.0.2-1.1 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Adrian Bunk Closes: 940143 957973

Bug#957055: marked as done (bristol: ftbfs with GCC-10)

Your message dated Sat, 06 Feb 2021 12:04:26 + with message-id and subject line Bug#957055: fixed in bristol 0.60.11-3.1 has caused the Debian Bug report #957055, regarding bristol: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If

bristol_0.60.11-3.1_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 05 Feb 2021 22:08:58 +0200 Source: bristol Architecture: source Version: 0.60.11-3.1 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Adrian Bunk Closes: 957055

Bug#957973: marked as done (xcfa: ftbfs with GCC-10)

Your message dated Sat, 06 Feb 2021 10:42:37 + with message-id and subject line Bug#957973: fixed in xcfa 5.0.2-1.1 has caused the Debian Bug report #957973, regarding xcfa: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#940143: marked as done (xcfa: cdda2wav is required but can't be found)

Your message dated Sat, 06 Feb 2021 10:42:37 + with message-id and subject line Bug#940143: fixed in xcfa 5.0.2-1.1 has caused the Debian Bug report #940143, regarding xcfa: cdda2wav is required but can't be found to be marked as done. This means that you claim that the problem has been