Your message dated Fri, 11 Apr 2025 13:24:10 +0000 with message-id <[email protected]> and subject line Bug#1100896: Removed package(s) from unstable has caused the Debian Bug report #1100896, regarding RM: dl10n -- RoQA; Maintainers MIA and package irrelevant for Debian users 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 [email protected] immediately.) -- 1100896: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1100896 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: ftp.debian.org Severity: normal X-Debbugs-Cc: [email protected], [email protected] Control: affects -1 + src:dl10n User: [email protected] Usertags: remove Dear Team, I am not an internal Debian person. But while a discussion with the QA team on IRC they pointed me to this option. The package is irrelvant for Debian users. Its features are used for internal things. Even the l10n team install that stuff from git and not via this package. I opened several tickets on this package. But no one responded. I asked on the maintainers mailing list. No response. I also triggered (by accident) auto- removal warning via modifying the severity some tickets. No response. Then again I asked for advice because of that auto-removal. No response. The team behind the package seems MIA or they are not interested in it anymore. Regards, Christian Buhtz
--- End Message ---
--- Begin Message ---We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: dl10n | 3.00+nmu1 | source, all ------------------- Reason ------------------- RoQA; Maintainers MIA and package irrelevant for Debian users ---------------------------------------------- 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 [email protected]. The full log for this bug can be viewed at https://bugs.debian.org/1100896 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing [email protected]. Debian distribution maintenance software pp. Paul Tagliamonte (the ftpmaster behind the curtain)
--- End Message ---
