Your message dated Sat, 16 Jul 2022 18:20:39 +0000 with message-id <e1ocmp9-000gri...@fasolo.debian.org> and subject line Bug#1014632: Removed package(s) from unstable has caused the Debian Bug report #1014632, regarding RM: sapphire -- RoQA; FTBFS; dead upstream; unmaintained; very low popcon 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.) -- 1014632: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014632 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: ftp.debian.org Severity: normal Hi, sapphire has not seen a new upstream release since 2002 (!), and upstream seems to have stopped working on it long long time ago. Furthermore: - the upstream website is a SourceForce page that only hosts very old releases, and has no source repositories - I cannot find anywhere a potential repository that continues the development - the last maintainer upload was in 2009, and since then it got only one NMU in 2017 - currently FTBFSes due to the very old packaging - it has a very low popcon count (19 at the time I'm writing this) - plenty of alternatives ("minimalist/lightweights" WMs) exist Hence, it looks to me it would be a better idea to simply remove sapphire from Debian. Thanks, -- Pino
--- End Message ---
--- Begin Message ---We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: sapphire | 0.15.8-9.1 | source, amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x ------------------- Reason ------------------- RoQA; FTBFS; dead upstream; unmaintained; very low popcon ---------------------------------------------- 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 1014...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/1014632 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. Thorsten Alteholz (the ftpmaster behind the curtain)
--- End Message ---
