On 26 Aug 2014, at 09:09, Marcus Denker <marcus.denker@inria.fr> wrote:
On 26 Aug 2014, at 00:18, Sven Van Caekenberghe <sven@stfx.eu> wrote:
A slice is nothing more than an empty mcz package with as requirements some other packages, namely the ones that you changed and want to include. I guess that if you take a fresh image and merge in your packages, you can create a new slice over them (provided they are dirty, sometimes this is a bit hard, you could make a trivial change). Make sure to save the slice with a higher version number.
The problem that the bug seems deeper⦠I have the impression that âSave Sliceâ does not search all the repos and if the number already exists, increase (like normal slice saving). Then, when saving, it *saves* the wrong version as it asks the cache âgive me name Xâ, and âname Xâ is already there, and it uses that for upload (or even skips the upload as the file is already there?). Even re-saving the slice does not help, as unchanged members are not re-saved with a new name.
But even if this would work, everything fails as soon as you end up with two MCZ files with the same name (e.g. working in two images offline, or working on a package, save, but then only merge it *after* you did another change in the main branch that led to the same name).
Maybe we should really add the hash in the filenameâ¦
I added an issue: https://pharo.fogbugz.com/f/cases/13921/Problem-committing-Slices-duplicated...