rm.bug-close 2.0 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253
  1. From: __RM_ADDRESS__
  2. To: __BUG_NUMBER__-close@__BUG_SERVER__
  3. __CC__
  4. __BCC__
  5. X-Debian: DAK
  6. Debian: DAK
  7. Debian-Archive-Action: remove
  8. Debian-Source: __SOURCES__
  9. Debian-Suite: __SUITES__
  10. MIME-Version: 1.0
  11. Content-Type: text/plain; charset="utf-8"
  12. Content-Transfer-Encoding: 8bit
  13. Subject: Bug#__BUG_NUMBER__: __SUBJECT__
  14. We believe that the bug you reported is now fixed; the following
  15. package(s) have been removed from __SUITE_LIST__:
  16. __SUMMARY__
  17. Note that the package(s) have simply been removed from the tag
  18. database and may (or may not) still be in the pool; this is not a bug.
  19. The package(s) will be physically removed automatically when no suite
  20. references them (and in the case of source, when no binary references
  21. it). Please also remember that the changes have been done on the
  22. master archive and will not propagate to any mirrors until the next
  23. dinstall run at the earliest.
  24. Packages are usually not removed from testing by hand. Testing tracks
  25. unstable and will automatically remove packages which were removed
  26. from unstable when removing them from testing causes no dependency
  27. problems. The release team can force a removal from testing if it is
  28. really needed, please contact them if this should be the case.
  29. Bugs which have been reported against this package are not automatically
  30. removed from the Bug Tracking System. Please check all open bugs and
  31. close them or re-assign them to another package if the removed package
  32. was superseded by another one.
  33. The version of this package that was in Debian prior to this removal
  34. can still be found using https://snapshot.debian.org/.
  35. Thank you for reporting the bug, which will now be closed. If you
  36. have further comments please address them to __BUG_NUMBER__@__BUG_SERVER__.
  37. The full log for this bug can be viewed at https://__BUG_SERVER__/__BUG_NUMBER__
  38. This message was generated automatically; if you believe that there is
  39. a problem with it please contact the archive administrators by mailing
  40. __ADMIN_ADDRESS__.
  41. __DISTRO__ distribution maintenance software
  42. pp.
  43. __WHOAMI__ (the ftpmaster behind the curtain)