Add by-hash support

[dak.git] / templates / rm.bug-close-with-related

diff --git a/templates/rm.bug-close-with-related b/templates/rm.bug-close-with-related
index 6a8f8c831bbcb641dd5ce0df794329f215370fa9..31623dbdef3cf06d88feb618cfd51f3b09c92cfb 100644 (file)
--- a/templates/rm.bug-close-with-related
+++ b/templates/rm.bug-close-with-related
@@ -1,6 +1,6 @@
 From: __RM_ADDRESS__
 To: __BUG_NUMBER__-close@__BUG_SERVER__
-__CC__ 
+__CC__
 __BCC__
 X-Debian: DAK
 MIME-Version: 1.0
@@ -17,9 +17,8 @@ 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 (__MASTER_ARCHIVE__) and will not propagate to any
-mirrors (__PRIMARY_MIRROR__ included) until the next cron.daily run at the
-earliest.
+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
@@ -27,14 +26,14 @@ 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 where closed
-correctly or should have been re-assign to another package.
+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 __BUG_NUMBER__@__BUG_SERVER__.
 
-The full log for this bug can be viewed at http://__BUG_SERVER__/__BUG_NUMBER__
+The full log for this bug can be viewed at https://__BUG_SERVER__/__BUG_NUMBER__
 
 This message was generated automatically; if you believe that there is
 a problem with it please contact the archive administrators by mailing