Re: silva.pas.* problems

On 27. Nov 2009, at 10:05 Uhr, Sylvain Viollon wrote:

> On Wed, 25 Nov 2009 20:00:04 +0100
> Marc Petitmermet <[email protected]> wrote:
> 
> Hello,
> 
> 
>>> 
>>> 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?
>> 
> 
>  For the moment, buildout software is released on dist.infrae.com,
>  specially dist.infrae.com/download for the Infrae software.
> 
>  infrae.com is a bit too old to host directly tarballs for buildout.
>  This going to be changed soon, as soon as we released Silva 2.2b1, it
>  will run under it, that will let us merge dist.infrae.com and
>  infrae.com.
> 
>  I guess we send a mail about that, on the mailing list, quite a long
>  time ago (around 1year~8months ago).

now that you mention this i can remember it. maybe you can add some note about dist.infrae.com/download on http://www.infrae.com/download.

> 
>>>> 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;-)
>> 
> 
>  All recent buildout include a utility which tells you at the end of
>  the execution which are the software which have version not pinned.
> 
>  When you have a working buildout, it's the first thing you should
>  do, otherwise will try each time to find the latest version for each
>  requirement of your setup.
> 
>  This ensure that new releases incompatible with the current software
>  you use won't break your setup if you try to reproduce it a couple of
>  month later.
> 
>  As soon as your configuration is pinned it will be reproducible
>  without reading a README.txt.
> 
>>>> 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.
>> 
> 
>  Your settings can be set in buildout.cfg, yes. This should be
>  explained here:
> 
>  http://docs.infrae.com/silva/buildout/extending.html#changing-your-zope-instance-settings
> 
>  With a link to all the proper documentation on how to do it.
> 

thanks, Sylvain, for all the great info. i certainly have still a lot of reading about buildout to do.

regards,
marc