Need help setting up Patchwork
Jeremy Kerr
jk at ozlabs.org
Mon Jul 5 10:22:00 EST 2010
Hi Deen,
> Hi Jeremy,
>
> Thanks for your reply. I ran patchwork on Virtualbox Ubuntu guest. I
>
> don't know why I got the error "unable to execute
> /srv/patchwork/apps/patchwork/bin/parsemail.sh: No such file or
> directory".
>
> I can execute the parsemail.sh if I boot into Ubuntu.
So it works if you boot directly to Ubuntu, but not if you boot Ubuntu as a
virtual machine?
> However, when I run it against the email archived it retured "no project
> found". I notice that that it doesn't contain mailinglist (List-ID) value.
Yes, patchwork needs a List-Id (or X-Mailing-List) header to determine which
project an email is for. If the mbox you have is from a mailing list, it
should have one of these headers. You will need to check that the settings for
the project (in the patchwork /admin/ interface) have the matching list-id
setting.
For example, the List-Id headers on the patchwork mailing list are:
List-Id: Patchwork development <patchwork.lists.ozlabs.org>
So the setting for this project in the admin interface is:
patchwork.lists.ozlabs.org
If your file does not have List-Id headers, you can use formail to add them:
formail -i 'List-Id: My project <bar.foo.com>' < old.mbox > new.mbox
> Does this mean that the parsemail.sh only work on the mbox format?
> Does parsemail.sh assume one email per file? I create a file and
> manually copy mbox text from an email account that I subscribe to a mailing
> list.
>
> Parsemail.sh works on the first email only. Would it be useful if I try
> to add code so that it support multiple email one file?
parsemail.py expects one email on its input.
However, you can use formail to execute the parser on each mail of a multiple-
mail mbox file:
formail -s /srv/patchwork/apps/patchwork/bin/parsemail.sh < your-file.mbox
> I saw the parsemail-batch.sh, but it seems to require one email per
> file because it uses the parsemail.py.
This is for importing a maildir-style directory of single-mail files
Cheers,
Jeremy
More information about the Patchwork
mailing list