Re: silva.pas.* problems
Marc Petitmermet <[email protected]> Wed, 25 Nov 2009 20:00:04 +0100
| Newsgroups | gmane.comp.web.zope.silva.devel |
|---|---|
| Message-ID | <[email protected]> |
(this message never reached the mailing list yesterday so i try it again) On 25. Nov 2009, at 16:10 Uhr, Sylvain Viollon wrote: > On Sun, 22 Nov 2009 21:13:38 +0100 > Marc Petitmermet <[email protected]> wrote: > >> dear developers >> > > Hello, > >> can you do something so that silva.pas.* work with the latest >> silva-2.1.7 buildout? >> >> silva.pas.base: ok >> >> silva.pas.sql: Error: Couldn't find a distribution for 'silva.pas.sql' >> > > I don't think that extension is released in the outside world, it's > only available on the svn for the moment. hmmm, how can one determine if something is released or not? in the past it was very easy: just go to http://www.infrae.com/download and download the tar-ball, if something is not available it's not released. but with buildout? >> silva.pas.openid: >> Error: There is a version conflict. We already have: Zope2 0.0 >> but Products.PluggableAuthService 1.7.0b1 requires 'Zope2>=2.12'. >> > > You should pin down the version PAS to get versions compatible with > Zope 2.11 (and not 2.12): > > [versions] > Products.PluggableAuthService = 1.6.1 > Products.PluginRegistry = 1.1.3.1 > Products.GenericSetup = 1.3.4 > > This is something you should always do. how did you figure out those version numbers? is there a database where we can look this up? for the installation of silva.pas.openid i just followed the README.txt and expected it to just work. isn't buildout meant to take care of all these dependencies for us and make our life easier? i probably have too high expectations for buildout;-) >> and for whatever reason the installation of silva.pas.openid deletes >> the complete "instance" directory with my conf files and other stuff >> and nothings works anymore... >> > > Everything in parts can be delete, to be regenerated again. It's a > normal behavior. i was annoyed that my settings in zope.conf did not survive a new buildout leading to a non-working zope instance. in the meantime i have figured out that i can use buildout.cfg for this as well and i have updated the documentation with this info. regards, marc