Need help setting up Patchwork

[Deen Sethanandha]

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

  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?

  Without modifying the code how can I process multiple email at once?

  I saw the parsemail-batch.sh, but it seems to require one email per file
because it uses the parsemail.py.

Thank you very much
Deen

----- Example of a email archived  --------
>From krh at bitplanet.net  Sat May  1 10:31:58 2010
From: krh at bitplanet.net (=?UTF-8?q?Kristian=20H=C3=B8gsberg?=)
Date: Sat,  1 May 2010 13:31:58 -0400
Subject: [PATCH 2/4] glxdri2: Hard-code the extension version we need
In-Reply-To: <1272735120-10941-1-git-send-email-krh at bitplanet.net>
References: <1272735120-10941-1-git-send-email-krh at bitplanet.net>
Message-ID: <1272735120-10941-2-git-send-email-krh at bitplanet.net>

If we use the #define'd version from dri_interface.h, the server will
require at least that version of the extension.  If we're compiling against
a dri_interface.h with a newer version we don't really require, glxdri2
will require a too high version of the extension.

The right approach is to just hard-code the version we need instead of
using the #defines.

Signed-off-by: Kristian H?gsberg <krh at bitplanet.net>
---
 glx/glxdri2.c |    6 +++---
 1 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/glx/glxdri2.c b/glx/glxdri2.c
index 74d6ebc..c34e29a 100644
--- a/glx/glxdri2.c
+++ b/glx/glxdri2.c
@@ -653,7 +653,7 @@ initializeExtensions(__GLXDRIscreen *screen)

 #ifdef __DRI2_FLUSH
  if (strcmp(extensions[i]->name, __DRI2_FLUSH) == 0 &&
-    extensions[i]->version >= __DRI2_FLUSH_VERSION) {
+    extensions[i]->version >= 3) {
  screen->flush = (__DRI2flushExtension *) extensions[i];
  }
 #endif
@@ -713,11 +713,11 @@ __glXDRIscreenProbe(ScreenPtr pScreen)

     for (i = 0; extensions[i]; i++) {
         if (strcmp(extensions[i]->name, __DRI_CORE) == 0 &&
-    extensions[i]->version >= __DRI_CORE_VERSION) {
+    extensions[i]->version >= 1) {
  screen->core = (const __DRIcoreExtension *) extensions[i];
  }
         if (strcmp(extensions[i]->name, __DRI_DRI2) == 0 &&
-    extensions[i]->version >= __DRI_DRI2_VERSION) {
+    extensions[i]->version >= 1) {
  screen->dri2 = (const __DRIdri2Extension *) extensions[i];
  }
     }
-- 
1.7.0.1


On Thu, Jul 1, 2010 at 10:21 AM, Jeremy Kerr <jk at ozlabs.org> wrote:

> Hi Deen,
>
> >   I am trying to setup a patchwork test my code with real data.  I am
> able
> > to set up patchwork server using python manage.py runserver.
> >
> >   Will this be sufficient setup for development purpose?
>
> Yes, that will be fine; you shouldn't use this to run a production server
> though.
>
> >   I haven't setup the email address to receive patches.  Can I use the
> > email from the mailing list archive to populate the database?
>
> You certainly can.
>
> >   I tried to run the following command but got error.
> >
> >  sudo -u nobody /srv/patchwork/apps/patchwork/bin/parsemail.sh < mail
> >
> >
> > $ sudo -u nobody /srv/patchwork/apps/patchwork/bin/parsemail.sh <
> > 2010-May.txt
> > sudo: unable to execute /srv/patchwork/apps/patchwork/bin/parsemail.sh:
> No
> > such file or directory
>
> Does that file exist? And does /bin/sh work?
>
> Also, you don't need to run that under sudo; as long as you have
> permissions
> to update the database, this should work.
>
> Cheers,
>
>
> Jeremy
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/patchwork/attachments/20100702/8a23e864/attachment.htm>