My fault. You need to run "./bin/buildout" again, after doing an "svn up".
Seb 2009/5/8 Jaap A. Haitsma <[email protected]> > 2009/5/8 Sébastien Nicouleaud <[email protected]>: > > The python-imaging contains no python2.4 modules (2.5/2.6 only): > > > > $ dpkg -L python-imaging | grep python2.4 | wc -l > > 0 > > $ dpkg -L python-imaging | grep -E 'python2.5|python2.6' | wc -l > > 178 > > $ > > > > I've got all necessary packages installed and just did an "svn up" > > I think I run into the issue that python-imaging does not have 2.4 modules > > Any ideas > > Jaap > > > > > > > 2009/5/8 Sébastien Nicouleaud <[email protected]> > >> > >> I ran into the same issue. > >> > >> I added a PIL dependency in buildout.cfg: > >> http://dev.plone.org/collective/changeset/85732 > >> > >> You just need to "svn up". > >> > >> Seb > >> > >> > >> 2009/5/8 Jaap A. Haitsma <[email protected]> > >>> > >>> I'm trying this on Ubuntu Jaunty but > >>> > >>> ./bin/instance run src/wgo.installsite/wgo/installsite/installsite.py > >>> > >>> returns an error that I have: "No module named PIL" > >>> > >>> I've installed python-imaging and python2.4 but Jaunty by default uses > >>> python2.6 > >>> > >>> Any ideas on how to solve this > >>> > >>> Thanks > >>> > >>> Jaap > >>> > >>> 2009/5/8 Davi Lima <[email protected]>: > >>> > I followed this link directions and it was fine: > >>> > > >>> > > http://live.gnome.org/GnomeWeb/CmsSetup#head-eaedb971ca574848ff39be8f3fc10d22c3c535d5 > >>> > > >>> > -- > >>> > Davi Lima > >>> > > >>> > 2009/5/8 Jaap A. Haitsma <[email protected]> > >>> >> > >>> >> OK, my apologies for bringing it up.When there are good instructions > >>> >> on how to setup a good test environment I'll be interested in trying > >>> >> to help a bit. > >>> >> > >>> >> Jaap > >>> >> > >>> >> On Fri, May 8, 2009 at 16:42, Lefty (石�R ) <[email protected]> > wrote: > >>> >> > On 5/8/09 2:44 AM, "Andreas Nilsson" <[email protected]> wrote: > >>> >> >> > >>> >> >> Talking CMS choices are one of those things that are just going > to > >>> >> >> end > >>> >> >> up in a really long and boring thread without any real consensus. > >>> >> >> What > >>> >> >> I > >>> >> >> would like for us to focus on first is to get all the > organization, > >>> >> >> content and design together and get it really, really good. Then > we > >>> >> >> can > >>> >> >> implement that in whatever thing suits best. > >>> >> > > >>> >> > I'd have to agree with Andreas that this is an unprofitable way to > >>> >> > approach > >>> >> > the discussion. There are better and worse kinds of hammers, but > >>> >> > they > >>> >> > can > >>> >> > all pretty much be used to drive nails, and talking about the > >>> >> > relative > >>> >> > merits of the various hammers won't get any nails driven. > >>> >> > > >>> >> > Changing tools will not cause work which hasn't gotten done so far > >>> >> > to > >>> >> > magically become accomplished independently of someone's sitting > >>> >> > down > >>> >> > and > >>> >> > doing it. My favorite flute instruction book has this advice on > the > >>> >> > first > >>> >> > page, in large letters: "MERE POSSESSION OF THIS BOOK IS _NOT_ > >>> >> > SUFFICIENT." > >>> >> > > >>> >> > > >>> >> > > >>> >> > > >>> >> _______________________________________________ > >>> >> gnome-web-list mailing list > >>> >> [email protected] > >>> >> http://mail.gnome.org/mailman/listinfo/gnome-web-list > >>> >> > >>> > > >>> > > >>> > _______________________________________________ > >>> > gnome-web-list mailing list > >>> > [email protected] > >>> > http://mail.gnome.org/mailman/listinfo/gnome-web-list > >>> > > >>> > > >>> _______________________________________________ > >>> gnome-web-list mailing list > >>> [email protected] > >>> http://mail.gnome.org/mailman/listinfo/gnome-web-list > >> > > > > >
_______________________________________________ gnome-web-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/gnome-web-list
