unnecessary mcz downloads

> Hi All,
>
>     I just followed a common enough workflow to commit partial changes:
>
> 1. in an image with some in-progress changes, implement a fix that I want to
> commit, excluding the in-progress changes
>
> 2. take a copy of the image, revert the in-progress changes, commit the fix
>
> 3. in the original image, merge with the committed package
>
> The strange thing is that while the step in 2. writes the package to the
> package-cache before uploading it, the step in 3. downloads the package
> again instead of simply using the identical copy in the package-cache.
> Anyone know why?  Is this easy to fix?  (This in a Squeak 4.5 trunk image)

> On 28 April 2014 18:24, Eliot Miranda <[hidden email]> wrote:
>> Hi All,
>>
>>    I just followed a common enough workflow to commit partial changes:
>>
>> 1. in an image with some in-progress changes, implement a fix that I want to
>> commit, excluding the in-progress changes
>>
>> 2. take a copy of the image, revert the in-progress changes, commit the fix
>>
>> 3. in the original image, merge with the committed package
>>
>> The strange thing is that while the step in 2. writes the package to the
>> package-cache before uploading it, the step in 3. downloads the package
>> again instead of simply using the identical copy in the package-cache.
>> Anyone know why?  Is this easy to fix?  (This in a Squeak 4.5 trunk image)
>
> Do you say "downloads" because MC displays a progress bar saying
> "Downloading..." or do you have additional evidence that MC downloads
> from the remote repository?