Recommended installation environment?

[Jeremy Kerr]

Hi Wolfgang,

> Sorry for asking a propbably stupid beginner's question:
> 
> Is there a recommended installation envrionment for patchwork?
> I mean a combination of Linux distribution and set of packages that is
> known give the least problems (or that should better be avoided)?

There is no official recommendation, but patchwork gets the most testing on:

 * Ubuntu, with postgres (my development & test environment)
 * Debian, with postgres (patchwork.ozlabs.org)

IIRC, patchwork.kernel.org is Fedora with MySQL. Although the support for this 
is trailing behind a little, J.H. lets me know when something breaks, and it 
usually gets fixed fairly soon after.

> I tried to get this runnign on Fedora 13 with MySQL, and ran into a
> few minor issues (eventually the "INSTALL" document is not complete
> and up to dat?), but in the end I run into more serious problems
> where I have no clue how to debug:
> 
> There is a large number of
> 
> 	[notice] child pid ... exit signal Segmentation fault (11)

This sounds like an issue with apache and/or the modules used for the python 
environment. Are there any other messages or debug info that you can send?

> 	[client ...] TemplateSyntaxError: Caught ImportError while rendering: No
> module named patchwork [client ...] mod_wsgi (pid=13865): Exception
> occurred processing WSGI script '/var/www/patchwork/patchwork.wsgi'.
> [client ...] Traceback (most recent call last):
> 	...
> 	[client ...] TemplateSyntaxError: Caught ImportError while rendering: No
> module named patchwork

Looks like your python needs to include /var/www/patchwork/apps; the 
documentation for mod_wsgi should have details about this:

 https://code.google.com/p/modwsgi/wiki/IntegrationWithDjango

I think that modifying patchwork.wsgi to look like this:

basedir = os.path.dirname(__file__)
sys.path.append(basedir)
sys.path.append('/var/www/patchwork/apps')

- should fix this. If not, let me know. In fact, let me know either way :)

> Is this some stupid pilot error, or would it be easier to swicth to a
> Ubuntu / PostgreSQL combo instead?

I'd suggest sticking with what you're familiar with; we can fix patchwork to 
suit, and once it's installed it should run OK.

Cheers,


Jeremy