[kforge-user] Re: enquiry about KForge codebase

Thu Jun 8 17:44:37 UTC 2006

Mike Hostetler wrote:
> I tried posting this to the mailing list, but was rejected:

Have you  signed up as a list member? Unfortunately due to spamming 
problems only list members can post.

> I'm attempting to install Kforge on a OpenSuse 10.0.  It's been a bit of 
> a process, but I've reached a point I can't get past.

Great. What version of KForge are you using? I'd really recommend using 
trunk (which is about to become KForge 0.11) as this is a major 
improvement over 0.10. However if you've gone with KForge 0.10 it 
doesn't matter as it is very easy to upgrade later.

> I've got the database set up, kforge installed, the kforge data 
> directory initialized and also hooked into Apache.  My current problem 
> lies with Django. 
> 
> As per the INSTALL instructions, I checked out rev 304 (11 Months Old) 
> of Django and installed it.  When going to the admin vhost, I got the 
> following error:
> [Thu Jun 08 08:17:55 2006] [error] [client 63.123.142.1 
> <http://63.123.142.1/>] PythonHandler django.core.handlers.modpython: 
> ImproperlyConfigured: Could not load database b        ackend: No module 
> named psycopg. Is your DATABASE_ENGINE setting (currently, 'postgresql') 
> spelled correctly? Available options are: 'mysql', 'postgre        sql', 
> 'sqlite3'
> 
> I an RPM of psycopg2 installed, is there a reason that it isn't being 

I think you want psycopg not psycopg2. You should be able to open a 
python prompt and do

 >>> import psycopg

If this doesn't work you've got psycopg2 which is *not* compatible with 
psycopg (v1).

> picked up?  Why does Kforge use such an old version of Django?

This was the original version we started using and it still works. We 
only use a very small part of django (form manipulators and modpython 
handler) so there has been no great need to update to the latest 
version. At some point we plan either to:
   1. Remove django and replace with something simpler and more specific 
to what we need
   2. Incorporate the small portions of the django codebase we need so 
there is no external dependency
   3. Upgrade to latest version of django (if we choose this option we 
will likely wait until django 1.0)

> Thanks for the help, I am hoping to set up Kforge for the Qcodo project 
> ( www.qcodo.com <http://www.qcodo.com/>) which I am involved with.

That's great. Let us know if you have any more problems or comments.

Regards,

Rufus Pollock

> On 6/4/06, * Mike Hostetler* <mike.hostetler at gmail.com 
> <mailto:mike.hostetler at gmail.com>> wrote:
> 
>     Thanks!!!!!
> 
>     On 6/2/06, Rufus Pollock <rufus.pollock at okfn.org
>     <mailto:rufus.pollock at okfn.org>> wrote:
>      > > Where can we find this newest version? Is there an SVN
>     repository somewhere?
>      > >
>      > > Thanks,
>      > >
>      > > Mike
>      >
>      > Yes there is. KForge development is hosted on
>      > http://www.knowledgeforge.net/ and its main page is:
>      > http://www.knowledgeforge.net/project/kforge/ which provides links to
>      > the associated svn and trac services.
>      >
>      > The svn repository can be found at:
>      >
>      >    http://project.knowledgeforge.net/kforge/svn/
>      >
>      > More info at:
>      >
>      >    http://www.kforgeproject.com/code/
>     <http://www.kforgeproject.com/code/>
>      >
>      > Regards,
>      >
>      > Rufus Pollock
>      >
> 
> 
>     --
>     Mike Hostetler
>     mike.hostetler at gmail.com <mailto:mike.hostetler at gmail.com>
>     http://www.amountaintop.com <http://www.amountaintop.com>
> 
> 
> 
> 
> -- 
> Mike Hostetler
> mike.hostetler at gmail.com <mailto:mike.hostetler at gmail.com>
> http://www.amountaintop.com