Your message dated Mon, 09 May 2016 18:21:39 +0000 with message-id <[email protected]> and subject line Bug#823767: Removed package(s) from unstable has caused the Debian Bug report #823767, regarding RM: drush -- RoQA; not maintained in debian 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.) -- 823767: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823767 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: ftp.debian.org Severity: normal I have orphaned Drush about 9 months ago, and no one picked it up. About once a month, I get a message from someone asking me to update it in Debian because well, it's out of date. The last request suggested that I remove it from Debian to make it clear that Debian doesn't ship with Drush anymore and that upstream has the correct way of installing the latest version. So please remove drush from Debian unstable. I guess it could also be removed from all suites as well, since there is absolutely no support upstream for those prehistory releases. For me packaging Drush was a step towards packaging Aegir. It now seems that Aegir itself doesn't use the Drush package anymore because it is also out of date, as of Aegir 3.x. And Aegir 2.x ships its own Drush release: http://debian.aegirproject.org/pool/main/d/drush/ So there is really no point in keeping Drush in Debian anymore.
--- End Message ---
--- Begin Message ---We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: drush | 5.10.0-2 | source, all ------------------- Reason ------------------- RoQA; not maintained in debian ---------------------------------------------- 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/823767 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. Scott Kitterman (the ftpmaster behind the curtain)
--- End Message ---
