Your message dated Mon, 26 Feb 2024 18:42:35 +0000 with message-id <[email protected]> and subject line Bug#1064640: Removed package(s) from unstable has caused the Debian Bug report #1064640, regarding RM: pyrcb2 -- ROM; Not maintained upstream, no rdepends 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.) -- 1064640: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064640 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:pyrcb2 User: [email protected] Usertags: remove Hello FTP team, I packaged pyrcb2 when trying to create a debian packaging for a Python IRC bot. I packaged it under the Debian Python Team as maintainer for making it easier for others to contribute, but that never happened. Considering: - The package did not have any upstream release in 3 years [1]. - Other librares are available and more mature to create IRC bots in Debian [2]. - The package currently has no known rdepends (used the reverse-depends command, could not connect to the ftp-masters mirror). - The popcon score of the package is 4 [3]. - The package has 2 serious bugs [4] (FTBFS and Python 3.12 migration) that the Python team should probably not waste any efforts to fix given this package was probably only used by me. I think we should RM this package from the archive. I only asked for unstable, but maybe we also should remove it from stable so that it does not stays a burden for the duration of a stable release's life. Please let me know if you need anything else. Thanks. Agathe. [1] https://github.com/taylordotfish/pyrcb2 [2] https://tracker.debian.org/pkg/limnoria [3] https://qa.debian.org/popcon.php?package=pyrcb2 [4] https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=no&src=pyrcb2
--- End Message ---
--- Begin Message ---We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: pyrcb2 | 0.6.2-2 | source python-pyrcb2-doc | 0.6.2-2 | all python3-pyrcb2 | 0.6.2-2 | all ------------------- Reason ------------------- ROM; Not maintained upstream, no rdepends ---------------------------------------------- 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/1064640 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. Thorsten Alteholz (the ftpmaster behind the curtain)
--- End Message ---
