Bug#909129: marked as done (gkermit FTCBFS: does not pass cross tools to make)

Your message dated Fri, 15 Oct 2021 23:04:13 + with message-id and subject line Bug#909129: fixed in gkermit 2.00-1 has caused the Debian Bug report #909129, regarding gkermit FTCBFS: does not pass cross tools to make to be marked as done. This means that you claim that the problem has been

Bug#732938: marked as done (gkermit: Description states "non-free package ckermit". ckermit is now free software in main)

Your message dated Fri, 15 Oct 2021 23:04:13 + with message-id and subject line Bug#732938: fixed in gkermit 2.00-1 has caused the Debian Bug report #732938, regarding gkermit: Description states "non-free package ckermit". ckermit is now free software in main to be marked as done. This

Bug#701604: marked as done (gkermit: cobwebby package description)

Your message dated Fri, 15 Oct 2021 23:04:13 + with message-id and subject line Bug#701604: fixed in gkermit 2.00-1 has caused the Debian Bug report #701604, regarding gkermit: cobwebby package description to be marked as done. This means that you claim that the problem has been dealt with.

Processed: Re: libloki: ftbfs with GCC-11

Processing control commands: > tags -1 patch Bug #984186 [src:libloki] libloki: ftbfs with GCC-11 Added tag(s) patch. -- 984186: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984186 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#984186: libloki: ftbfs with GCC-11

Package: libloki Version: 0.1.7-3 Followup-For: Bug #984186 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu ubuntu-patch X-Debbugs-Cc: sl...@ubuntu.com Control: tags -1 patch Dear Maintainer, GCC 11 defaults to C++17 which does not allow dynamic exception specifications anymore:

Bug#950943: marked as done (psad: missing-systemd-service-for-init.d-script)

Your message dated Fri, 15 Oct 2021 12:34:25 + with message-id and subject line Bug#950943: fixed in psad 2.4.6-2 has caused the Debian Bug report #950943, regarding psad: missing-systemd-service-for-init.d-script to be marked as done. This means that you claim that the problem has been

Bug#984083: lasi: ftbfs with GCC-11

Package: lasi Version: 1.1.0-2 Followup-For: Bug #984083 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu ubuntu-patch X-Debbugs-Cc: sl...@ubuntu.com Control: tags -1 patch Dear Maintainer, lasi fails to build from source with GCC-11. Fix FTFBFS with C++17/GCC-11, by avoiding dynamic

Processed: Re: lasi: ftbfs with GCC-11

Processing control commands: > tags -1 patch Bug #984083 [src:lasi] lasi: ftbfs with GCC-11 Added tag(s) patch. -- 984083: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984083 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

qr-tools_2.1~bzr45-1~bpo11+1_amd64.changes ACCEPTED into bullseye-backports, bullseye-backports

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 10 Oct 2021 11:31:20 -0400 Source: qr-tools Binary: python3-qrtools qtqr Architecture: source all Version: 2.1~bzr45-1~bpo11+1 Distribution: bullseye-backports Urgency: medium Maintainer: Debian QA Group

Bug#993774: Removed package(s) from unstable

Version: 0.5.0-5+rm Dear submitter, as the package shatag has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/993774 The

Bug#993774: Removed package(s) from unstable

We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: shatag |0.5.0-5 | source, all --- Reason --- ROM; Orphaned, not used -- Note that the package(s) have

Bug#992595: Removed package(s) from unstable

Version: 1.9.2-21+rm Dear submitter, as the package nwrite has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/992595 The

Bug#992595: Removed package(s) from unstable

We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: nwrite | 1.9.2-21 | source, amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x --- Reason --- RoQA; obsoleted over time;

Bug#989005: Removed package(s) from unstable

Version: 1.3.12-7+rm Dear submitter, as the package aewm has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/989005 The

Bug#989005: Removed package(s) from unstable

We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: aewm | 1.3.12-7 | source, amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x --- Reason --- RoQA; dead upstream; unmaintained;

Bug#450016: marked as done (nwrite: debian/watch fails to report upstream's version)

Your message dated Fri, 15 Oct 2021 06:11:59 + with message-id and subject line Bug#992595: Removed package(s) from unstable has caused the Debian Bug report #450016, regarding nwrite: debian/watch fails to report upstream's version to be marked as done. This means that you claim that the

Bug#228993: marked as done (nwrite complains about X logins unnecessarily)

Your message dated Fri, 15 Oct 2021 06:11:59 + with message-id and subject line Bug#992595: Removed package(s) from unstable has caused the Debian Bug report #228993, regarding nwrite complains about X logins unnecessarily to be marked as done. This means that you claim that the problem has

Bug#989074: marked as done (Ship upstream-dead aewm with bullseye?)

Your message dated Fri, 15 Oct 2021 06:01:50 + with message-id and subject line Bug#989005: Removed package(s) from unstable has caused the Debian Bug report #989074, regarding Ship upstream-dead aewm with bullseye? to be marked as done. This means that you claim that the problem has been

Bug#715621: marked as done ([Mayhem] Bug report on aewm: aedesk crashes with exit status 139)

Your message dated Fri, 15 Oct 2021 06:01:50 + with message-id and subject line Bug#989005: Removed package(s) from unstable has caused the Debian Bug report #715621, regarding [Mayhem] Bug report on aewm: aedesk crashes with exit status 139 to be marked as done. This means that you claim

Bug#974436: marked as done (aewm: autopkgtest must be marked superficial)

Your message dated Fri, 15 Oct 2021 06:01:50 + with message-id and subject line Bug#989005: Removed package(s) from unstable has caused the Debian Bug report #974436, regarding aewm: autopkgtest must be marked superficial to be marked as done. This means that you claim that the problem has

Bug#224336: marked as done (problems with menus.)

Your message dated Fri, 15 Oct 2021 06:01:50 + with message-id and subject line Bug#989005: Removed package(s) from unstable has caused the Debian Bug report #224336, regarding problems with menus. to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#967244: marked as done (aewm: depends on deprecated GTK 2)

Your message dated Fri, 15 Oct 2021 06:01:50 + with message-id and subject line Bug#989005: Removed package(s) from unstable has caused the Debian Bug report #967244, regarding aewm: depends on deprecated GTK 2 to be marked as done. This means that you claim that the problem has been dealt

Bug#185099: marked as done (aewm: resize outline displays in black even on black backgrounds)

Your message dated Fri, 15 Oct 2021 06:01:50 + with message-id and subject line Bug#989005: Removed package(s) from unstable has caused the Debian Bug report #185099, regarding aewm: resize outline displays in black even on black backgrounds to be marked as done. This means that you claim