On 4 Jul 2018, at 23:00, Norbert Hartl wrote:
Am 04.07.2018 um 17:52 schrieb Max Leske <maxle...@gmail.com>:
Hi Norbert,
Where can I get my hands on that image that you say has no sender of
#newBinaryFileNamed:do: in it?
I cannot give away the image, sorry. I can try to reproduce it
somehow.
Do you expect the method to be there?
I would have, yes. But as you have discovered, the problem may lie with
ZnFileSystemUtils (although I would have expected that package to be
updated along with Zinc).
Max
Norbert
Max
On 4 Jul 2018, at 17:30, Norbert Hartl wrote:
I tried to see how hard it would be to load my current project in
pharo7. Cyril helped me to see that I load an old version of zinc
and it does not work that way. Upgrading to zinc 2.9.2 made it work
in pharo 7 but my jenkins build do not work anymore. I don’t fully
understand what is happening. I see in the log
Loading baseline of BaselineOfMobilityMap...
...RETRY->BaselineOfParasol
...RETRY->BaselineOfParasol[31mMessageNotUnderstood:
ZnFileSystemUtils class>>newBinaryFileNamed:do:
[0mZnFileSystemUtils class(Object)>>doesNotUnderstand:
#newBinaryFileNamed:do:
ZnClient>>downloadEntityTo:
ZnClient>>downloadTo:
IceMetacelloPharoPlatform(MetacelloPharoPlatform)>>downloadZipArchive:to:
The strange thing about it is that when I download that image where
the error occurred I cannot find a sender of #newBinaryFileNamed:do:
and the #downloadEntityTo: does not seem to use it. Downgrading to
zinc 2.8.10 makes it work again.
I feel a little bit stupid because the image does not load any new
package on startup and still there is this error message which does
not make sense to me at all.
Any ideas?
Norbert