--On January 22, 2011 3:51:55 PM -0800 "Steve McMahon [via Plone]" <[email protected]> wrote:
> If you've got the environment to build binaries, just use the Unified > Installer. You can even use the "--with-python=..." if you'd prefer your > system's Python. Thanks for that suggestion. I went ahead and used the Unified Installer, and the problem went away. I added a comment to this effect in the ticket, but I think it would be good to have a blurb on the Plone download page that explains the difference between the 2 installers, and nudges folks towards the Unified Installer. This is an important decision, and one likely made before reading much documentation or browsing mailing lists. > On Fri, Jan 21, 2011 at 8:35 PM, rbrewer <[email protected]> wrote: > >> --On January 12, 2011 2:57:56 AM -0800 "Stefan Lange [via Plone]" >> <[hidden email] <http://user/SendEmail.jtp?type=node&node=5950160&i=0>> >> wrote: >> >> > Hi, >> > >> > I've found a solution to this issue: you have to install a newer PIL >> > version. >> > >> > Grab it from here: >> > http://effbot.org/downloads/Imaging-1.1.7.tar.gz >> > >> > Then install it so that your instance can use it. >> > Now you have to take care that the PIL egg (that came with the Plone >> > Installer) will no longer be used. Just remove (or comment) the >> > corresponding entry in the zinstance/bin/instance file. >> >> I'd rather install any new PIL version inside the Python instance >> provided by Plone, rather than use the system python. Are there any >> step-by-step instructions on how to make buildout download & use a newer >> version of a package? My exploratory attempts to modify the buildout.cfg >> file did not succeed. >> >> While I would like to resolve this problem swiftly, I also want to leave >> things in a maintainable state, so when I upgrade to the next Plone >> version, things don't break again. >> >> -- >> Robert Brewer >> http://excitedcuriosity.wordpress.com/ >> >> ------------------------------ >> View this message in context: Re: _imaging.so not >> found<http://plone.293351.n2.nabble.com/imaging-so-not-found-tp5887646p5 >> 950160.html> >> >> Sent from the Installation, Setup, Upgrades mailing list >> archive<http://plone.293351.n2.nabble.com/Installation-Setup-Upgrades-f2 >> 93353.html>at Nabble.com. >> >> _______________________________________________ >> Setup mailing list >> [email protected] >> https://lists.plone.org/mailman/listinfo/setup >> >> > > _______________________________________________ > Setup mailing list > [email protected] > https://lists.plone.org/mailman/listinfo/setup > > > _______________________________________________ > If you reply to this email, your message will be added to the discussion > below: > http://plone.293351.n2.nabble.com/imaging-so-not-found-tp5887646p5951877. > html > > To unsubscribe from _imaging.so not found, visit > http://plone.293351.n2.nabble.com/template/NamlServlet.jtp?macro=unsubscr > ibe_by_code&node=5887646&code=cmJyZXdlckBsYXZhLm5ldHw1ODg3NjQ2fDI5NjM5NTg > yMg== -- Robert Brewer http://excitedcuriosity.wordpress.com/ -- View this message in context: http://plone.293351.n2.nabble.com/imaging-so-not-found-tp5887646p5961588.html Sent from the Installation, Setup, Upgrades mailing list archive at Nabble.com.
_______________________________________________ Setup mailing list [email protected] https://lists.plone.org/mailman/listinfo/setup
