Really? I thought the same but then I didn’t believe it works like that. Anyway this would be very easy to solve. We just need to ask Sven if he is fine with doing an empty .16 version for Zinc-FileSystem and does an in-place version reset of 2.9.2 or a new 2.9.3. I’m not fully convinced that will solve it but the cost won’t be very high.
Norbert > Am 07.07.2018 um 13:22 schrieb Cyril Ferlicot <[email protected]>: > > > 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. > > If there is a package .15 in the image and a package .15 in the repo, I think > Metacello will not update because it rely on the numbers to know when to > update. If it find a .15 and currently have a .15 I think Metacello will > think they are at the same version. > > > > Norbert > > > > > > > > -- > Cyril Ferlicot > https://ferlicot.fr <https://ferlicot.fr/>
