Custom Query (332 matches)
Results (208 - 210 of 332)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#124 | fixed | new ticket creation fails: AttributeError: 'NoneType' object has no attribute 'replace' | anonymous | gdh@… |
Description |
Hi - I've used dpkg-buildpackage on Ubuntu hardy to build email2trac 0.70 with trac 0.11. Trying either run_email2trac in /etc/aliases, or email2trac in /etc/aliases.nobody (chowned + postalias'd) fails with this error when I run 'mail tracproj <msg.txt' Feb 23 12:56:54 dev postfix/qmgr[25750]: F07E51F49FE: from=<root@…>, size=2214, nrcpt=1 (que ue active) Feb 23 12:56:55 dev email2trac: Traceback (most recent call last): Feb 23 12:56:55 dev email2trac: File "/usr/bin/email2trac", line 1466, in <module> tktparser.parse(sys .stdin) Feb 23 12:56:55 dev email2trac: File "/usr/bin/email2trac", line 835, in parse m.replace_header('Subje ct', mSubject?.replace('\r', ).replace('\n', )) Feb 23 12:56:55 dev email2trac: AttributeError?: 'NoneType?' object has no attribute 'replace' Feb 23 12:56:55 dev postfix/local[25758]: F07E51F49FE: to=<tracproj@…>, orig_to=<tracproj>, relay=local, delay=0.44, delays=0.02/0.01/0/0.42, dsn=5.3.0, status=bounced (Command died with status 1: "/usr/bin/email2trac ". Command output: TD: saving email to /tmp/tmpSOrsIb.email2trac ) If I run 'email2trac <msg.txt' manually from the commandline as root, then the new ticket is created OK :/ My /etc/aliases.nobody is this one line: tracproj: |"/usr/bin/email2trac " |
|||
#135 | wontfix | Great Product, Please help me install it! | bas | gary@… |
Description | ||||
#15 | fixed | Milestone Handling | bas | Garrett McGrath <gmcgrath@…> |
Description |
To whom it may concern: I'm looking at modifying the email2trac script to enable it to handle a 'category' flag. Specifically we are using Trac as a data portal for our users and are exploring using the ticket system to track help requests to make life easier for our users (quick referrence to past issues and etc.). I'm thinking that the milestones system would be an easy way to segregate our emailed tickets automatically. eg. if we get a feature request for our calendar that goes to 1 email, and general help to a second email address, these simply populate the same ticket system in trac but with different milestones attached to them (or components as that would be nice to split things up with as well). So my question is has anyone does this before, and do I just need to modify the email2trac.py program or do the .c and .h files get modified as well. -Garrett McGrath |