[kforge-dev] [Fwd: Re: enquiry about KForge codebase]

[Mike Hostetler]

I'm going to try posting to the list again.  I am subscribed to the list
with a fancy Gmail address (has a +lists in it), hopefully I can post now.

Anyways, thank you both for your feedback.  I will roll back to the r304
version of Django tonite and try it again.  I am using the newest Kforge
checked out from SVN.

Based on an email that Rufus sent to me and the list, I think my problem
lies in psycopg.  I am using version 2, looks like I need version 1.

I will try to get this thing installed and report back.

Thanks,
Mike

On 6/8/06, John Bywater <john.bywater at appropriatesoftwarefoundation.org>
wrote:
>
> Hi Mike,
>
> Thanks for all the information.
>
> I didn't know there was a permission problem, but I do know that kforge
> doesn't work with latest django.
>
> I'll look at the issues you've reported and get back to you asap.
>
> With best regards,
>
> John.
>
> PS Let's keep the discussion on the list!
>
>
>
> Mike Hostetler wrote:
>
> > John-
> >
> > After sending the email to Rufus that started this thread, I updated
> > to the SVN Head version of Django and received a new error.  I'm not
> > familiar enough with Python or Django to debug it very well.
> >
> > I also ran into the error of Apache having permission to access my
> > /usr/share/kforge/www/ directory.  I had to explicity allow that in my
> > httpd.conf file (server one, not kforge one) to get to this point.  I
> > didn't see any mention to that step in the documentation, so hopefully
> > that was the correct step.
> >
> > Thanks,
> > Mike
>
>
>
>


-- 
Mike Hostetler
mike.hostetler at gmail.com
http://www.amountaintop.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/kforge-dev/attachments/20060608/e01ba938/attachment-0002.html>