Need help setting up Patchwork

[Deen Sethanandha]

Thank you very much for your reply!


> So it works if you boot directly to Ubuntu, but not if you boot Ubuntu as a
> virtual machine?
>
>
Yes that's what happened.  I didn't know why either. The /bin/sh worked
fine.
I didn't try to trouble shoot it since it worked on Ubuntu host.


> 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.
>

When I am taking about mailinglist, I meant the archive from this page.
http://lists.ozlabs.org/pipermail/patchwork/.  When I unzip the archive
it didn't have the List-ID information.


>  formail -i 'List-Id: My project <bar.foo.com>' < old.mbox > new.mbox
>

Thank you very much.  I modified it a bit so that it works with multiple
email per 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
>

This works fine.  Thanks!

>
> >   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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/patchwork/attachments/20100706/2e24b7e1/attachment.htm>