Bump. I wonder nobody sees the problem. Or do I misunderstand there is something wrong in pharo?
Norbert > Am 05.07.2018 um 09:09 schrieb Norbert Hartl <[email protected]>: > > Ok, > > I think I’ve found something. If you look at the screenshot (that is my image > from jenkins, 6.1 with my code loaded and that throw the error) you can see > that Zinc-FileSystem.15 is already loaded. But the Author gives the hint that > this was loaded by the image integrator. And it differs from the .15 from > Sven’s repo. Exactly the difference that could cause my error. I’m not sure > if metacello upgrades only packages that have a higher version number. But > that would be the explanation why it doesn’t work for me. I checked it by > download a fresh 6.1 image and the situation is the same here. > So reproducing the problem should be as easy as creating a baseline that > loads zinc 2.9.2 and later something from github. My case was that in the > first step the project code was loaded in the image including zinc 2.9.2. > That image was saved and on the next invocation it loads the test code and > parasol was the first dependency to load from github and it failed. > > Norbert > > <Bildschirmfoto 2018-07-05 um 08.59.10.png> > >> Am 05.07.2018 um 08:44 schrieb Max Leske <[email protected] >> <mailto:[email protected]>>: >> >> On 4 Jul 2018, at 23:00, Norbert Hartl wrote: >> >>>> Am 04.07.2018 um 17:52 schrieb Max Leske <[email protected] >>>> <mailto:[email protected]>>: >>>> >>>> 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 >>>> >> >
