> Obviously something went wrong somewhere, but I cannot see what exactly. It is a while ago, and integration processes have been in flux.
> Zinc is being developed in its own repo(s), but sometimes changes are made in the main Pharo repo that get copied back upstream. From time to time, Zinc itself is updated in Pharo itself.
> If Zinc-FileSystem-TheIntegrator.15 is indeed different from Zinc-FileSystem-SvenVanCaekenberghe.15 then the best solution would be to merge them and create a newer, more correct version.
Need to investigate more. There are two .15 versions but there is 1 year in between (if you didn’t notice TheIntegratior.15 is from 2017). Just want to have more context information because I can only see that this is strange but lacking insight.
I’m trying to figure out why it does not update Zinc-FileSystem. No matter what I do I cannot get Metacello to load the newer package. That would fix the issue because I’m loading 2.9.2 which should have Zinc-FileSystem-SVC.15 and not stay on the one included in the image.
I think this is important for everyone that has a product based on 6.1 and that want to migrate someday to pharo7. This way it is impossible to do it step by step.
>> On 7 Jul 2018, at 12:29, Norbert Hartl <
[hidden email]> wrote:
>>
>> Can anyone explain how zinc is managed? The package Zinc-FileSystem in pharo 6.1 is
>>
>> Name: Zinc-FileSystem-TheIntegrator.15
>> Author: TheIntegrator
>> Time: 15 March 2017, 1:16:56.199425 pm
>> UUID: b9684fa8-2507-0d00-a4da-a21207d152a4
>> Ancestors: Zinc-FileSystem-HenrikNergaard.14
>>
>> 19838 ZnMonticelloServerDelegate>>#repositoryListing sends self self
>>
https://pharo.fogbugz.com/f/cases/19838>>
>>
>> In Sven’s repo there is
>>
>> Name: Zinc-FileSystem-SvenVanCaekenberghe.14
>> Author: SvenVanCaekenberghe
>> Time: 14 March 2018, 11:29:06.12468 am
>> UUID: 885ce694-be23-0d00-a4f2-9f24027c8ee7
>> Ancestors: Zinc-FileSystem-GitHub.1520938892, Zinc-FileSystem-SvenVanCaekenberghe.13
>>
>> tracking pharo 7 changes
>>
>> and
>>
>> Name: Zinc-FileSystem-SvenVanCaekenberghe.15
>> Author: SvenVanCaekenberghe
>> Time: 14 March 2018, 2:08:47.155993 pm
>> UUID: 9c55f9cf-c023-0d00-9b4a-76f3014de7ca
>> Ancestors: Zinc-FileSystem-SvenVanCaekenberghe.14
>>
>> patch to dynamically work on older pharo versions
>>
>> How do this packages relate?
>>
>> Norbert
>>
>>> Am 06.07.2018 um 16:34 schrieb Norbert Hartl <
[hidden email]>:
>>>
>>> Sven,
>>>
>>> I use Metacello and that seems to be different in behaviour. I prepared the case for you. What I did
>>>
>>> - save the attachment of this mail into a clean directory and open a terminal there
>>>
>>> $> unzip baseline-of-zincproblem.zip
>>> $> curl get.pharo.org/64/61 | bash
>>> $> /Applications/Pharo64.app/Contents/MacOS/Pharo ./Pharo.image eval „Metacello new repository: 'filetree://src'; baseline: 'ZincProblem'; load"
>>>
>>> Look at ZnClient>>#downloadEntityTo:
>>>
>>> Norbert
>>>
>>> <baseline-of-zincproblem.zip>
>>>
>>>> Am 06.07.2018 um 13:19 schrieb Sven Van Caekenberghe <
[hidden email]>:
>>>>
>>>> Norbert,
>>>>
>>>> I did (on macOS):
>>>>
>>>> $ mkdir pharo61
>>>>
>>>> $ cd pharo61/
>>>>
>>>> $ curl get.pharo.org/61+vm | bash
>>>> % Total % Received % Xferd Average Speed Time Time Time Current
>>>> Dload Upload Total Spent Left Speed
>>>> 100 3036 100 3036 0 0 24386 0 --:--:-- --:--:-- --:--:-- 24483
>>>> Downloading the latest 61 Image:
>>>>
http://files.pharo.org/get-files/61/pharo.zip>>>> Pharo.image
>>>> Downloading the latest pharoVM:
>>>>
http://files.pharo.org/get-files/61/pharo-mac-stable.zip>>>> pharo-vm/Pharo.app/Contents/MacOS/Pharo
>>>> Downloading PharoV61.sources:
>>>>
http://files.pharo.org/get-files/61/sources.zip>>>> Creating starter scripts pharo and pharo-ui
>>>>
>>>> $ ./pharo-ui Pharo.image
>>>>
>>>> I loaded ConfigurationOfZincHTTPComponents via the Catalog, but since that was not the latest, I loaded it manually and did
>>>>
>>>> ConfigurationOfZincHTTPComponents project latestVersion load.
>>>>
>>>> Here is the Transcript
>>>>
>>>>
>>>> Loading 2.8.3 of ConfigurationOfZincHTTPComponents...
>>>> Fetched -> Zodiac-Core-SvenVanCaekenberghe.42 ---
http://mc.stfx.eu/Zodiac ---
http://mc.stfx.eu/Zodiac>>>> Fetched -> Zodiac-Tests-SvenVanCaekenberghe.13 ---
http://mc.stfx.eu/Zodiac ---
http://mc.stfx.eu/Zodiac>>>> Fetched -> Zinc-Character-Encoding-Tests-SvenVanCaekenberghe.29 ---
http://mc.stfx.eu/ZincHTTPComponents ---
http://mc.stfx.eu/ZincHTTPComponents>>>> Fetched -> Zinc-FileSystem-SvenVanCaekenberghe.12 ---
http://mc.stfx.eu/ZincHTTPComponents ---
http://mc.stfx.eu/ZincHTTPComponents>>>> Fetched -> Zinc-HTTP-SvenVanCaekenberghe.453 ---
http://mc.stfx.eu/ZincHTTPComponents ---
http://mc.stfx.eu/ZincHTTPComponents>>>> Fetched -> Zinc-Zodiac-SvenVanCaekenberghe.36 ---
http://mc.stfx.eu/ZincHTTPComponents ---
http://mc.stfx.eu/ZincHTTPComponents>>>> Loaded -> Zodiac-Core-SvenVanCaekenberghe.42 ---
http://mc.stfx.eu/Zodiac --- /private/tmp/pharo61/pharo-local/package-cache
>>>> Loaded -> Zodiac-Tests-SvenVanCaekenberghe.13 ---
http://mc.stfx.eu/Zodiac --- /private/tmp/pharo61/pharo-local/package-cache
>>>> Loaded -> Zinc-Character-Encoding-Tests-SvenVanCaekenberghe.29 ---
http://mc.stfx.eu/ZincHTTPComponents --- cache
>>>> Loaded -> Zinc-FileSystem-SvenVanCaekenberghe.12 ---
http://mc.stfx.eu/ZincHTTPComponents --- cache
>>>> Loaded -> Zinc-HTTP-SvenVanCaekenberghe.453 ---
http://mc.stfx.eu/ZincHTTPComponents --- cache
>>>> Loaded -> Zinc-Zodiac-SvenVanCaekenberghe.36 ---
http://mc.stfx.eu/ZincHTTPComponents --- cache
>>>> ...finished 2.8.3
>>>>
>>>> Loading 2.9.2 of ConfigurationOfZincHTTPComponents...
>>>> Fetched -> Zodiac-Core-TorstenBergmann.48 ---
http://mc.stfx.eu/Zodiac ---
http://mc.stfx.eu/Zodiac>>>> Fetched -> Zodiac-Tests-SvenVanCaekenberghe.22 ---
http://mc.stfx.eu/Zodiac ---
http://mc.stfx.eu/Zodiac>>>> Fetched -> Zodiac-Extra-SvenVanCaekenberghe.8 ---
http://mc.stfx.eu/Zodiac ---
http://mc.stfx.eu/Zodiac>>>> Fetched -> Zinc-Character-Encoding-Core-SvenVanCaekenberghe.64 ---
http://mc.stfx.eu/ZincHTTPComponents ---
http://mc.stfx.eu/ZincHTTPComponents>>>> Fetched -> Zinc-Character-Encoding-Tests-SvenVanCaekenberghe.43 ---
http://mc.stfx.eu/ZincHTTPComponents ---
http://mc.stfx.eu/ZincHTTPComponents>>>> Fetched -> Zinc-Resource-Meta-Core-SvenVanCaekenberghe.68 ---
http://mc.stfx.eu/ZincHTTPComponents ---
http://mc.stfx.eu/ZincHTTPComponents>>>> Fetched -> Zinc-Resource-Meta-Tests-SvenVanCaekenberghe.38 ---
http://mc.stfx.eu/ZincHTTPComponents ---
http://mc.stfx.eu/ZincHTTPComponents>>>> Fetched -> Zinc-FileSystem-SvenVanCaekenberghe.15 ---
http://mc.stfx.eu/ZincHTTPComponents ---
http://mc.stfx.eu/ZincHTTPComponents>>>> Fetched -> Zinc-HTTP-SvenVanCaekenberghe.474 ---
http://mc.stfx.eu/ZincHTTPComponents ---
http://mc.stfx.eu/ZincHTTPComponents>>>> Fetched -> Zinc-Tests-SvenVanCaekenberghe.245 ---
http://mc.stfx.eu/ZincHTTPComponents ---
http://mc.stfx.eu/ZincHTTPComponents>>>> Fetched -> Zinc-Zodiac-SvenVanCaekenberghe.44 ---
http://mc.stfx.eu/ZincHTTPComponents ---
http://mc.stfx.eu/ZincHTTPComponents>>>> Fetched -> Zinc-Resource-Meta-FileSystem-SvenVanCaekenberghe.9 ---
http://mc.stfx.eu/ZincHTTPComponents ---
http://mc.stfx.eu/ZincHTTPComponents>>>> Loaded -> Zodiac-Core-TorstenBergmann.48 ---
http://mc.stfx.eu/Zodiac --- /private/tmp/pharo61/pharo-local/package-cache
>>>> Loaded -> Zodiac-Tests-SvenVanCaekenberghe.22 ---
http://mc.stfx.eu/Zodiac --- /private/tmp/pharo61/pharo-local/package-cache
>>>> Loaded -> Zodiac-Extra-SvenVanCaekenberghe.8 ---
http://mc.stfx.eu/Zodiac --- /private/tmp/pharo61/pharo-local/package-cache
>>>> ZnBase64Encoder (DefaultInverse is Undeclared)
>>>> ZnBase64Encoder (DefaultAlphabet is Undeclared)
>>>> ZnSimplifiedByteEncoder class>>initializeByteTextConverters (ByteTextConverters is Undeclared)
>>>>
>>>> ZnSimplifiedByteEncoder class>>initializeByteTextConverters (ByteTextConverters is Undeclared)
>>>>
>>>> ZnSimplifiedByteEncoder class>>initializeByteTextConverters (ByteTextConverters is Undeclared)
>>>>
>>>> ZnSimplifiedByteEncoder class>>byteTextConverters (ByteTextConverters is Undeclared)
>>>>
>>>> Loaded -> Zinc-Character-Encoding-Core-SvenVanCaekenberghe.64 ---
http://mc.stfx.eu/ZincHTTPComponents --- cache
>>>> Loaded -> Zinc-Character-Encoding-Tests-SvenVanCaekenberghe.43 ---
http://mc.stfx.eu/ZincHTTPComponents --- cache
>>>> Loaded -> Zinc-Resource-Meta-Core-SvenVanCaekenberghe.68 ---
http://mc.stfx.eu/ZincHTTPComponents --- cache
>>>> Loaded -> Zinc-Resource-Meta-Tests-SvenVanCaekenberghe.38 ---
http://mc.stfx.eu/ZincHTTPComponents --- cache
>>>> Loaded -> Zinc-FileSystem-SvenVanCaekenberghe.15 ---
http://mc.stfx.eu/ZincHTTPComponents --- cache
>>>> ZnSingleThreadedServer class>>adoptAsDefault: (Default is Undeclared)
>>>>
>>>> ZnSingleThreadedServer class>>initialize (Default is Undeclared)
>>>>
>>>> ZnSingleThreadedServer class>>default (Default is Undeclared)
>>>>
>>>> ZnSingleThreadedServer class>>stopDefault (Default is Undeclared)
>>>>
>>>> ZnSingleThreadedServer class>>stopDefault (Default is Undeclared)
>>>>
>>>> ZnSingleThreadedServer class>>stopDefault (Default is Undeclared)
>>>>
>>>> ZnSingleThreadedServer class>>defaultOn: (Default is Undeclared)
>>>>
>>>> ZnSingleThreadedServer class>>defaultOn: (Default is Undeclared)
>>>>
>>>> ZnSingleThreadedServer class>>defaultOn: (Default is Undeclared)
>>>>
>>>> Loaded -> Zinc-HTTP-SvenVanCaekenberghe.474 ---
http://mc.stfx.eu/ZincHTTPComponents --- cache
>>>> Loaded -> Zinc-Tests-SvenVanCaekenberghe.245 ---
http://mc.stfx.eu/ZincHTTPComponents --- cache
>>>> Loaded -> Zinc-Zodiac-SvenVanCaekenberghe.44 ---
http://mc.stfx.eu/ZincHTTPComponents --- cache
>>>> Loaded -> Zinc-Resource-Meta-FileSystem-SvenVanCaekenberghe.9 ---
http://mc.stfx.eu/ZincHTTPComponents --- cache
>>>> ...finished 2.9.2
>>>>
>>>> (The Undeclared references are eventually resolved).
>>>>
>>>> The code you mentioned is present in the image. Unit tests (apart from one) are green.
>>>>
>>>> ===
>>>> Name: Zinc-FileSystem-SvenVanCaekenberghe.15
>>>> Author: SvenVanCaekenberghe
>>>> Time: 14 March 2018, 2:08:47.155993 pm
>>>> UUID: 9c55f9cf-c023-0d00-9b4a-76f3014de7ca
>>>> Ancestors: Zinc-FileSystem-SvenVanCaekenberghe.14
>>>> ===
>>>>
>>>> Sven
>>>>
>>>>> On 6 Jul 2018, at 12:50, Norbert Hartl <
[hidden email]> wrote:
>>>>>
>>>>> 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 <
[hidden email]>:
>>>>>>
>>>>>> 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 <
[hidden email]>:
>>>>>>>
>>>>>>> On 4 Jul 2018, at 23:00, Norbert Hartl wrote:
>>>>>>>
>>>>>>>>> Am 04.07.2018 um 17:52 schrieb Max Leske <
[hidden email]>:
>>>>>>>>>
>>>>>>>>> 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
>>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>
>>
>
>
Locked
baseline-of-zincproblem.zip (6K)