[Silva-general] Upgrading buildout to different version

[Kit BLAKE]

Jon,
I'll answer this on a lightweight level (because I don't program  
buildouts, I just run them).

You really should be installing everything in 'parts'. That's what  
it's meant for.

If you do that, and then want to experiment with something, you put  
that something in 'products' and it will override the one in 'parts'.  
You can then implement changes in the something, and later update the  
buildout to get the modified something and put it in parts.

Kit


On 18 Jan 2010, at 13:27, Jonathan Bowlas wrote:

> Hi All,
>
> I followed the instructions here
> http://docs.infrae.com/silva/buildout.html#upgrading-your-setup to
> upgrade my buildout setup however when I bin\buildout afterwards I get
> the following error:
>
> An internal error occured due to a bug in either zc.buildout or in a
> recipe being used:
> Traceback (most recent call last):
>  File "c:\silva-2.0.13-new\eggs\zc.buildout-1.4.2-py2.4.egg\zc 
> \buildout\buildou
> t.py", line 1660, in main
>    getattr(buildout, command)(args)
>  File "c:\silva-2.0.13-new\eggs\zc.buildout-1.4.2-py2.4.egg\zc 
> \buildout\buildou
> t.py", line 471, in install
>    self._uninstall_part(part, installed_part_options)
>  File "c:\silva-2.0.13-new\eggs\zc.buildout-1.4.2-py2.4.egg\zc 
> \buildout\buildou
> t.py", line 589, in _uninstall_part
>    uninstaller(part, installed_part_options[part])
>  File "c:\silva-2.0.13-new\eggs\infrae.subversion-1.4.5-py2.4.egg 
> \infrae\subver
> sion\Native.py", line 132, in uninstall
>    checkAddedPaths(location, urls)
>  File "c:\silva-2.0.13-new\eggs\infrae.subversion-1.4.5-py2.4.egg 
> \infrae\subver
> sion\Common.py", line 72, in checkAddedPaths
>    raise ValueError(msg % ', '.join(added_paths))
> ValueError: New path have been added to the location: C: 
> \Silva-2.0.13-new\produc
> ts\SilvaFind, C:\Silva-2.0.13-new\products\Annotations, C: 
> \Silva-2.0.13-new\prod
> ucts\Sprout, C:\Silva-2.0.13-new\products\SilvaViews, C: 
> \Silva-2.0.13-new\produc
> ts\SilvaLayout, C:\Silva-2.0.13-new\products\README.txt, C: 
> \Silva-2.0.13-new\pro
> ducts\z3locales, C:\Silva-2.0.13-new\products\SilvaExternalSources,  
> C:\Silva-2.0
> .13-new\products\Formulator, C:\Silva-2.0.13-new\products\kupu, C: 
> \Silva-2.0.13-
> new\products\FileSystemSite, C:\Silva-2.0.13-new\products\Groups, C: 
> \Silva-2.0.1
> 3-new\products\ParsedXML, C:\Silva-2.0.13-new\products\ZMySQLDA, C: 
> \Silva-2.0.13
> -new\products\XMLWidgets, C:\Silva-2.0.13-new\products 
> \SilvaMetadata, C:\Silva-2
> .0.13-new\products\SilvaDocument, C:\Silva-2.0.13-new\products 
> \ProxyIndex, C:\Si
> lva-2.0.13-new\products\Silva.
>
> It seems that checkAddedPaths is checking for any products that aren't
> added via buildout into 'parts' but since I revised our buildout
> scripts to install everything in 'products' the script raises this
> exception informing me that these are new paths.
>
> To resove this I've commented out the call to checkAddedPaths from
> Native.py and it works fine. So my question is twofold - is it ok to
> comment out checkAddedPaths and should I really be installing
> everything in 'parts'?
>
> Cheers
>
> Jon
>
> _______________________________________________
> silva-general mailing list
> silva-general at lists.infrae.com
> https://lists.infrae.com/mailman/listinfo/silva-general