[Paraview] Issue with Catalyst spack package

[Mark Olesen]

Yes this is something that Simone has been trying to tackle:

https://github.com/RemoteConnectionManager/spack/commits/packages/update_paraview

You can try a few different things, but nothing really helps.
In the spack package it might help to set the GIT_DIR env to point to 
the catalyst directory before the patch/staging part, but that might 
just prevent the warning about exploring across file boundaries.

On top of that someone (Andy!) probably needs to adjust the catalyze.py 
script to add the checks there, since this error will always occur when 
building from a tarball.

/mark


On 07/05/18 11:23, Dorier, Matthieu wrote:
> Hi,
> 
> 
> I've been trying to install Catalyst using Spack, but ran into an issue 
> that I think is caused by Catalyst (some python script in the ParaView 
> source tree trying to use git on a directory that isn't managed by git). 
> At least that's my first guess...
> 
> 
> Here is the full issue described on the Spack google group:
> 
> https://groups.google.com/forum/#!topic/spack/Pzn3C7KrF7w
> 
> 
> Thanks,
> 
> 
> Matthieu
> 
> 
> 
> _______________________________________________
> Powered by www.kitware.com
> 
> ParaView discussion is moving! Please visit https://discourse.paraview.org/ for future posts.
> 
> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
> 
> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView
> 
> Search the list archives at: http://markmail.org/search/?q=ParaView
> 
> Follow this link to subscribe/unsubscribe:
> https://public.kitware.com/mailman/listinfo/paraview
> 

-- 
Dr Mark OLESEN
Principal Engineer, ESI-OpenCFD
ESI GmbH | Einsteinring 24 | 85609 Munich | GERMANY
Mob. +49 171 9710 149
www.openfoam.com | www.esi-group.com | mark.olesen at esi-group.com