[Tracker-discuss] Fwd: Failed issue tracker submission
Paul Dubois
pfdubois at gmail.com
Mon Jan 15 22:58:40 CET 2007
I got the error Martin got. I don't understand this, in all the years we've
used Roundup on my project this has never happened.
The Re: [Tracker-discuss] is supposed to be stripped. The hypen in the
tracker name maybe?
---------- Forwarded message ----------
From: Meta Tracker <roundup-admin at psf.upfronthosting.co.za>
Date: Jan 15, 2007 1:54 PM
Subject: Failed issue tracker submission
To: pfdubois at gmail.com
The class name you identified in the subject line ("Tracker-discuss") does
not exist in the
database.
Valid class names are: file, issue, keyword, msg, priority, query, status,
user
Subject was: "Re: [Tracker-discuss] [issue73] Issue numbering"
Mail Gateway Help
=================
Incoming messages are examined for multiple parts:
. In a multipart/mixed message or part, each subpart is extracted and
examined. The text/plain subparts are assembled to form the textual
body of the message, to be stored in the file associated with a "msg"
class node. Any parts of other types are each stored in separate files
and given "file" class nodes that are linked to the "msg" node.
. In a multipart/alternative message or part, we look for a text/plain
subpart and ignore the other parts.
Summary
-------
The "summary" property on message nodes is taken from the first non-quoting
section in the message body. The message body is divided into sections by
blank lines. Sections where the second and all subsequent lines begin with
a ">" or "|" character are considered "quoting sections". The first line of
the first non-quoting section becomes the summary of the message.
Addresses
---------
All of the addresses in the To: and Cc: headers of the incoming message are
looked up among the user nodes, and the corresponding users are placed in
the "recipients" property on the new "msg" node. The address in the From:
header similarly determines the "author" property of the new "msg"
node. The default handling for addresses that don't have corresponding
users is to create new users with no passwords and a username equal to the
address. (The web interface does not permit logins for users with no
passwords.) If we prefer to reject mail from outside sources, we can simply
register an auditor on the "user" class that prevents the creation of user
nodes with no passwords.
Actions
-------
The subject line of the incoming message is examined to determine whether
the message is an attempt to create a new item or to discuss an existing
item. A designator enclosed in square brackets is sought as the first thing
on the subject line (after skipping any "Fwd:" or "Re:" prefixes).
If an item designator (class name and id number) is found there, the newly
created "msg" node is added to the "messages" property for that item, and
any new "file" nodes are added to the "files" property for the item.
If just an item class name is found there, we attempt to create a new item
of that class with its "messages" property initialized to contain the new
"msg" node and its "files" property initialized to contain any new "file"
nodes.
Triggers
--------
Both cases may trigger detectors (in the first case we are calling the
set() method to add the message to the item's spool; in the second case we
are calling the create() method to create a new node). If an auditor raises
an exception, the original message is bounced back to the sender with the
explanatory message given in the exception.
$Id: mailgw.py,v 1.180 2006/12/19 01:13:31 richard Exp $
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.python.org/pipermail/tracker-discuss/attachments/20070115/3428dee8/attachment.html
-------------- next part --------------
Return-Path: <pfdubois at gmail.com>
X-Original-To: metatracker at psf.upfronthosting.co.za
Delivered-To: metatracker at psf.upfronthosting.co.za
Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.249])
by psf.localdomain (Postfix) with ESMTP id 47A4A78054
for <metatracker at psf.upfronthosting.co.za>; Mon, 15 Jan 2007 21:54:17 +0000 (UTC)
Received: by an-out-0708.google.com with SMTP id c35so653776anc
for <metatracker at psf.upfronthosting.co.za>; Mon, 15 Jan 2007 13:54:15 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; c=nofws;
d=gmail.com; s=beta;
h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
b=sryuAMk+OY2uaS6DKO+p2rO389PdsTZRLxNa49FpWIRwCxRUseV5UfLBWwn5Xq2BcH2kyxveVQRUPgnh/2bpTvUKkXKj7gMFNrTgoALq6w1ZsiM/7NIcJ5VldT7D3fnRGwNYVTYK/YTKACw/e1iyy0hgnyxvsq7CqrscfThTKI4=
Received: by 10.35.69.11 with SMTP id w11mr8505894pyk.1168898054773;
Mon, 15 Jan 2007 13:54:14 -0800 (PST)
Received: by 10.35.40.8 with HTTP; Mon, 15 Jan 2007 13:54:14 -0800 (PST)
Message-ID: <f74a6c2f0701151354v5b5cd9e8p6ec17509f430afb4 at mail.gmail.com>
Date: Mon, 15 Jan 2007 13:54:14 -0800
From: "Paul Dubois" <pfdubois at gmail.com>
To: "Meta Tracker" <metatracker at psf.upfronthosting.co.za>
Subject: Re: [Tracker-discuss] [issue73] Issue numbering
In-Reply-To: <87irf82cbw.fsf at uterus.efod.se>
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_Part_42543_16268805.1168898054310"
References: <1168894595.6709.47.camel at kwaaitjie>
<87irf82cbw.fsf at uterus.efod.se>
------=_Part_42543_16268805.1168898054310
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
This also has the virtue that at some point we could drop it. I like it.
On 1/15/07, Erik Forsberg <metatracker at psf.upfronthosting.co.za> wrote:
>
>
> Erik Forsberg added the comment:
>
> > Roch=E9 Compaan added the comment:
>
> > Is it not an option to use a prefix for sourceforge bug ids, say SF, an=
d
> > then restart with a lower number for bugs generated in Roundup?
>
> Here's one idea:
>
> 1) Add a new property to the issue class, sf_id=3DNumber()
>
> 2) Rewrite importer to set sf_id to the original sourceforge id of
> each issue, but don't set the roundup ID to the sourceforge id -
> instead, allocate issue IDs on the go, beginning with 1, ending
> with about 9940 (that's the number of issues currently in the sf
> database).
>
> 3) Add ability to search for sourceforge ID in search interface.
>
> 4) Make sf bug redirector aware of the mechanism, so that
> python.org/sf/<id> redirects to the correct issue.
>
> This will break the one to one mapping between the sourceforge
> artifact IDs and the new roundup issue ids, but it might be a better
> solution for day to day use.
>
> Comments?
>
> \EF
> --
> Erik Forsberg http://efod.se
> GPG/PGP Key: 1024D/0BAC89D9
>
> ______________________________________________________
> Meta Tracker <metatracker at psf.upfronthosting.co.za>
> <http://psf.upfronthosting.co.za/roundup/meta/issue73>
> ______________________________________________________
> _______________________________________________
> Tracker-discuss mailing list
> Tracker-discuss at python.org
> http://mail.python.org/mailman/listinfo/tracker-discuss
>
------=_Part_42543_16268805.1168898054310
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
This also has the virtue that at some point we could drop it. I like it.<br=
><br><div><span class=3D"gmail_quote">On 1/15/07, <b class=3D"gmail_sendern=
ame">Erik Forsberg</b> <<a href=3D"mailto:metatracker at psf.upfronthosting=
.co.za">
metatracker at psf.upfronthosting.co.za</a>> wrote:</span><blockquote class=
=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, 204, 204); margin=
: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>Erik Forsberg added the commen=
t:
<br><br>> Roch=E9 Compaan added the comment:<br><br>> Is it not an op=
tion to use a prefix for sourceforge bug ids, say SF, and<br>> then rest=
art with a lower number for bugs generated in Roundup?<br><br>Here's on=
e idea:
<br><br>1) Add a new property to the issue class, sf_id=3DNumber()<br><br>2=
) Rewrite importer to set sf_id to the original sourceforge id of<br> =
each issue, but don't set the roundup ID to the sourceforge id -=
<br> instead, allocate issue IDs on the go, beginning with 1, e=
nding
<br> with about 9940 (that's the number of issues currently=
in the sf<br> database).<br><br>3) Add ability to search for s=
ourceforge ID in search interface.<br><br>4) Make sf bug redirector aware o=
f the mechanism, so that
<br> <a href=3D"http://python.org/sf/">python.org/sf/</a><id=
> redirects to the correct issue.<br><br>This will break the one to one =
mapping between the sourceforge<br>artifact IDs and the new roundup issue i=
ds, but it might be a better
<br>solution for day to day use.<br><br>Comments?<br><br>\EF<br>--<br>Erik =
Forsberg &=
nbsp; <a href=3D"http://efod.se">http://efod.se</a>=
<br>GPG/PGP Key: 1024D/0BAC89D9<br><br>____________________________________=
__________________
<br>Meta Tracker <<a href=3D"mailto:metatracker at psf.upfronthosting.co.za=
">metatracker at psf.upfronthosting.co.za</a>><br><<a href=3D"http://psf=
.upfronthosting.co.za/roundup/meta/issue73">http://psf.upfronthosting.co.za=
/roundup/meta/issue73
</a>><br>______________________________________________________<br>_____=
__________________________________________<br>Tracker-discuss mailing list<=
br><a href=3D"mailto:Tracker-discuss at python.org">Tracker-discuss at python.org
</a><br><a href=3D"http://mail.python.org/mailman/listinfo/tracker-discuss"=
>http://mail.python.org/mailman/listinfo/tracker-discuss</a><br></blockquot=
e></div><br>
------=_Part_42543_16268805.1168898054310--
More information about the Tracker-discuss
mailing list