anthony at bnovc.com
Fri Jan 16 01:19:51 EST 2009
Thanks, that gave some more information.
$ cat /var/mail/newnam| ./parsemail.py
Traceback (most recent call last):
File "./parsemail.py", line 36, in <module>
from patchwork.parser import parse_patch
ImportError: No module named patchwork.parser
Is my test even going to work? It seems like my emails have to have a
39 list_id_headers = ['List-ID', 'X-Mailing-List']
If it helps
$ python --version
(run from /srv/patchwork/apps/patchwork)
$ grep patchwork.parser **/*
bin/parsemail.py:from patchwork.parser import parse_patch
models.py:from patchwork.parser import hash_patch
Binary file models.pyc matches
Binary file parser.pyc matches
Thanks for any information!
On Wed, Jan 14, 2009 at 5:40 PM, Nate Case <ncase at xes-inc.com> wrote:
> On Wed, 2009-01-14 at 17:17 -0600, Anthony Newnam wrote:
>> I've finally gotten close to having patchwork work. I am using
>> fetchmail to send email to postfix to forward it to the python script.
>> This all appears to be working. In the admin interface, I put some
>> random names into the linkname and name and then I put Anthony.Newnam
>> in the listid and Anthony.Newnam at domain.tld in the listemail. I then
>> sent an email to Anthony.Newnam at domain.tld with the subject "[PATCH]
>> bla bla" and a .patch file attached to it. It got to the postfix
>> python script I added to /etc/aliases, but there is no entry in the
>> table when I go to the patchwork website.
>> Is any part of what I explained wrong?
> You should probably try piping the raw contents of the e-mail message
> you sent into the parsemail.sh script to see what's going on:
> $ cat message.txt | /path/to/patchwork/apps/patchwork/bin/parsemail.sh
> Nate Case <ncase at xes-inc.com>
More information about the Patchwork