#!/usr/bin/perl
-# $Id: mailsummary.in,v 1.8 2001/08/16 17:40:22 doogie Exp $
+# $Id: mailsummary.in,v 1.11 2003/04/28 23:51:15 cjwatson Exp $
-$config_path = '/org/bugs.debian.org/etc';
-$lib_path = '/org/bugs.debian.org/scripts';
+$config_path = '/etc/debbugs';
+$lib_path = '/usr/lib/debbugs';
require("$config_path/config");
require("$lib_path/errorlib");
$intro=
"The following problem reports have not yet been marked as `taken up\' by a
message to done\@$gEmailDomain or or `forwarded\' by a
-message to fowarded\@$gEmailDomain."
+message to forwarded\@$gEmailDomain."
;
} elsif ($ARGV[0] eq 'bymaint') {
$vdef= "(no outstanding $gBug reports on file, or problem running script)\n";
Variant versions of the Maintainer field for the same actual package
maintainer will be listed separately.
-Maintainers with few outstanding $gBug appear first, to avoid those with few
+Maintainers with few outstanding $gBugs appear first, to avoid those with few
$gBugs being lost deep in the message.
"
;
$intro=
"The following problem reports are very old but have not yet been marked
as `taken up\' by a message to done\@$gEmailDomain as forwarded
-to a developer by CCing a message to fowarded\@$gEmailDomain.
+to a developer by CCing a message to forwarded\@$gEmailDomain.
Please help ensure that these $gBugs are dealt with quickly, even if you
are not the package maintainer in question. (NB a full list of outstanding
$gBug reports is posted periodically - this is a partial list only!)
$intro
$v
Every Tuesday, the listing by package maintainer is posted.
-Every Frideay, the listing by age of the report is posted.
+Every Friday, the listing by age of the report is posted.
Please see the documentation for more information about how to
use the $gBug tracking system. It is available on the WWW at