Your message dated Sat, 29 Jun 2024 22:26:07 +0000 with message-id <e1sngwf-00axz6...@fasolo.debian.org> and subject line Bug#1071904: Removed package(s) from unstable has caused the Debian Bug report #1071904, regarding RM: wuzzah -- RoQA; unmaintained upstream and in Debian; FTBFS to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1071904: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071904 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: ftp.debian.org Severity: normal User: ftp.debian....@packages.debian.org Usertags: remove X-Debbugs-Cc: wuz...@packages.debian.org Control: affects -1 + src:wuzzah Control: tags -1 + moreinfo wuzzah has recently started FTBFSing. It also has not seen any upstream activity since 2003 (no typo), and the last maintainer upload to Debian was in 2014. Popcon data suggests this package is very unpopular. I'm also expecting it to become a problem when new utmp interfaces will be introduced soon. I'm filing this tagged moreinfo for now, and will untag in a month if nobody wants to take over the package until then. Chris
--- End Message ---
--- Begin Message ---We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: wuzzah | 0.53-3.1 | source, amd64, arm64, armel, armhf, i386, mips64el, ppc64el, s390x wuzzah | 0.53-3.1+b1 | riscv64 ------------------- Reason ------------------- RoQA; unmaintained upstream and in Debian; FTBFS ---------------------------------------------- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. We try to close bugs which have been reported against this package automatically. But please check all old bugs, if they were closed correctly or should have been re-assigned to another package. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1071...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/1071904 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)
--- End Message ---
