Hi Jeremy,<div><br></div><div> 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".<br>
<br></div><div> I can execute the parsemail.sh if I boot into Ubuntu. 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. Does this mean that the parsemail.sh only work on the mbox format? </div>
<div><br></div><div> 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?</div>
<div><br></div><div> Without modifying the code how can I process multiple email at once?</div><div> </div><div> I saw the parsemail-batch.sh, but it seems to require one email per file because it uses the parsemail.py.</div>
<div><br></div><div>Thank you very much</div><div>Deen</div><div><br></div><div>----- Example of a email archived --------</div><div><div>From krh at <a href="http://bitplanet.net" target="_blank">bitplanet.net</a> Sat May 1 10:31:58 2010</div>
<div>From: krh at <a href="http://bitplanet.net" target="_blank">bitplanet.net</a> (=?UTF-8?q?Kristian=20H=C3=B8gsberg?=)</div>
<div>Date: Sat, 1 May 2010 13:31:58 -0400</div><div>Subject: [PATCH 2/4] glxdri2: Hard-code the extension version we need</div><div>In-Reply-To: <<a href="mailto:1272735120-10941-1-git-send-email-krh@bitplanet.net" target="_blank">1272735120-10941-1-git-send-email-krh@bitplanet.net</a>></div>
<div>References: <<a href="mailto:1272735120-10941-1-git-send-email-krh@bitplanet.net" target="_blank">1272735120-10941-1-git-send-email-krh@bitplanet.net</a>></div><div>Message-ID: <<a href="mailto:1272735120-10941-2-git-send-email-krh@bitplanet.net" target="_blank">1272735120-10941-2-git-send-email-krh@bitplanet.net</a>></div>
<div><br></div><div>If we use the #define'd version from dri_interface.h, the server will</div><div>require at least that version of the extension. If we're compiling against</div><div>a dri_interface.h with a newer version we don't really require, glxdri2</div>
<div>will require a too high version of the extension.</div><div><br></div><div>The right approach is to just hard-code the version we need instead of</div><div>using the #defines.</div><div><br></div><div>Signed-off-by: Kristian H?gsberg <krh at <a href="http://bitplanet.net" target="_blank">bitplanet.net</a>></div>
<div>---</div><div> glx/glxdri2.c | 6 +++---</div><div> 1 files changed, 3 insertions(+), 3 deletions(-)</div><div><br></div><div>diff --git a/glx/glxdri2.c b/glx/glxdri2.c</div><div>index 74d6ebc..c34e29a 100644</div>
<div>--- a/glx/glxdri2.c</div><div>+++ b/glx/glxdri2.c</div><div>@@ -653,7 +653,7 @@ initializeExtensions(__GLXDRIscreen *screen)</div><div> </div><div> #ifdef __DRI2_FLUSH</div><div> <span style="white-space:pre-wrap"> </span>if (strcmp(extensions[i]->name, __DRI2_FLUSH) == 0 &&</div>
<div>-<span style="white-space:pre-wrap"> </span> extensions[i]->version >= __DRI2_FLUSH_VERSION) {</div><div>+<span style="white-space:pre-wrap"> </span> extensions[i]->version >= 3) {</div>
<div> <span style="white-space:pre-wrap"> </span>screen->flush = (__DRI2flushExtension *) extensions[i];</div><div> <span style="white-space:pre-wrap"> </span>}</div><div> #endif</div>
<div>@@ -713,11 +713,11 @@ __glXDRIscreenProbe(ScreenPtr pScreen)</div><div> </div><div> for (i = 0; extensions[i]; i++) {</div><div> if (strcmp(extensions[i]->name, __DRI_CORE) == 0 &&</div><div>
-<span style="white-space:pre-wrap"> </span> extensions[i]->version >= __DRI_CORE_VERSION) {</div><div>+<span style="white-space:pre-wrap"> </span> extensions[i]->version >= 1) {</div>
<div> <span style="white-space:pre-wrap"> </span>screen->core = (const __DRIcoreExtension *) extensions[i];</div><div> <span style="white-space:pre-wrap"> </span>}</div><div> if (strcmp(extensions[i]->name, __DRI_DRI2) == 0 &&</div>
<div>-<span style="white-space:pre-wrap"> </span> extensions[i]->version >= __DRI_DRI2_VERSION) {</div><div>+<span style="white-space:pre-wrap"> </span> extensions[i]->version >= 1) {</div>
<div> <span style="white-space:pre-wrap"> </span>screen->dri2 = (const __DRIdri2Extension *) extensions[i];</div><div> <span style="white-space:pre-wrap"> </span>}</div><div> }</div>
<div>-- </div><div>1.7.0.1</div></div><div><br></div><div><br><div class="gmail_quote">On Thu, Jul 1, 2010 at 10:21 AM, Jeremy Kerr <span dir="ltr"><<a href="mailto:jk@ozlabs.org" target="_blank">jk@ozlabs.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Deen,<br>
<div><br>
> I am trying to setup a patchwork test my code with real data. I am able<br>
> to set up patchwork server using python manage.py runserver.<br>
><br>
> Will this be sufficient setup for development purpose?<br>
<br>
</div>Yes, that will be fine; you shouldn't use this to run a production server<br>
though.<br>
<div><br>
> I haven't setup the email address to receive patches. Can I use the<br>
> email from the mailing list archive to populate the database?<br>
<br>
</div>You certainly can.<br>
<div><br>
> I tried to run the following command but got error.<br>
><br>
> sudo -u nobody /srv/patchwork/apps/patchwork/bin/parsemail.sh < mail<br>
><br>
><br>
> $ sudo -u nobody /srv/patchwork/apps/patchwork/bin/parsemail.sh <<br>
> 2010-May.txt<br>
> sudo: unable to execute /srv/patchwork/apps/patchwork/bin/parsemail.sh: No<br>
> such file or directory<br>
<br>
</div>Does that file exist? And does /bin/sh work?<br>
<br>
Also, you don't need to run that under sudo; as long as you have permissions<br>
to update the database, this should work.<br>
<br>
Cheers,<br>
<font color="#888888"><br>
<br>
Jeremy<br>
</font></blockquote></div><br></div>