That sounds like the most probable source of the problem.
Thanks Sven for the new version, I will update my configuration (or
“BaselineOf”).
Hernán, maybe you can try loading it in a new image to see if you get the same
problem?
> On Jan 22, 2016, at 12:42 PM, Cyril Ferlicot <[email protected]> wrote:
>
> Hi,
> If there is already a version of NeoJSON in the image the new version can be
> skip (ahah!) during the loading. I had this problem before, I had to load the
> bleeding edge in a new image.
>
>
>
> On Friday, January 22, 2016, Skip Lentz <[email protected]
> <mailto:[email protected]>> wrote:
> Thanks Hernán for your report.
> As Sven said, it is not yet present in the stable version of NeoJSON.
> But it should not matter as I load the bleeding-edge version.
>
> I will look into this.
> Can you tell me which script you used to load the tool? Is it the one in the
> first e-mail?
>
>
> --
> Cheers
> Cyril Ferlicot
>
