Smalltalk › Squeak › Squeak - Dev

4.4 release update map is update-bf.217

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

4 messages Options

Bert Freudenberg

4.4 release update map is update-bf.217

Somehow we forgot to publish an update map corresponding exactly to the 4.4 release image package versions.

I now retroactively did that by replacing update-cwp.217 in the trunk repo with update-bf.217. That is, I opened update-cwp.217, updated it from a fresh 4.4-12327 image, stored as update-bf.217, and deleted update-cwp.217 using the web interface.

The result is that if you browse update-bf.217 in vanilla 4.4, all package versions match (as indicated by no bold or italic entries).

- Bert -

Frank Shearar-3

Re: 4.4 release update map is update-bf.217

On 11 January 2013 22:01, Bert Freudenberg <[hidden email]> wrote:
> Somehow we forgot to publish an update map corresponding exactly to the 4.4 release image package versions.
>
> I now retroactively did that by replacing update-cwp.217 in the trunk repo with update-bf.217. That is, I opened update-cwp.217, updated it from a fresh 4.4-12327 image, stored as update-bf.217, and deleted update-cwp.217 using the web interface.
>
> The result is that if you browse update-bf.217 in vanilla 4.4, all package versions match (as indicated by no bold or italic entries).
>
> - Bert -

This means that one should now be able to hit "update" on the 44
update stream and not have an error, right?

I had thought/hoped that the error would resolve itself when the first
update to 44 went in. But I think it's just another area where I can
become less ignorant.

How best would we fix this for 4.5? We have a script in the
ReleaseBuilder (#transferCurrentPackages) that pushes all the latest
versions of trunk to the new update stream, so perhaps we can tweak
that to also produce an update map?

frank

Bert Freudenberg

Re: 4.4 release update map is update-bf.217

On 11.01.2013, at 14:14, Frank Shearar <[hidden email]> wrote:

> On 11 January 2013 22:01, Bert Freudenberg <[hidden email]> wrote:
>> Somehow we forgot to publish an update map corresponding exactly to the 4.4 release image package versions.
>>
>> I now retroactively did that by replacing update-cwp.217 in the trunk repo with update-bf.217. That is, I opened update-cwp.217, updated it from a fresh 4.4-12327 image, stored as update-bf.217, and deleted update-cwp.217 using the web interface.
>>
>> The result is that if you browse update-bf.217 in vanilla 4.4, all package versions match (as indicated by no bold or italic entries).
>>
>> - Bert -
>
> This means that one should now be able to hit "update" on the 44
> update stream and not have an error, right?

What error? Didn't try that, this is about the trunk update stream, not the 4.4 update stream.

> I had thought/hoped that the error would resolve itself when the first
> update to 44 went in. But I think it's just another area where I can
> become less ignorant.

If 4.4 has no update map yet then this would explain the error. Yes, you should publish one as update-fbs.1.

> How best would we fix this for 4.5? We have a script in the
> ReleaseBuilder (#transferCurrentPackages) that pushes all the latest
> versions of trunk to the new update stream, so perhaps we can tweak
> that to also produce an update map?
>
> frank

Sounds about right.

- Bert -

Frank Shearar-3

Re: 4.4 release update map is update-bf.217

On 11 January 2013 22:39, Bert Freudenberg <[hidden email]> wrote:

>
> On 11.01.2013, at 14:14, Frank Shearar <[hidden email]> wrote:
>
>> On 11 January 2013 22:01, Bert Freudenberg <[hidden email]> wrote:
>>> Somehow we forgot to publish an update map corresponding exactly to the 4.4 release image package versions.
>>>
>>> I now retroactively did that by replacing update-cwp.217 in the trunk repo with update-bf.217. That is, I opened update-cwp.217, updated it from a fresh 4.4-12327 image, stored as update-bf.217, and deleted update-cwp.217 using the web interface.
>>>
>>> The result is that if you browse update-bf.217 in vanilla 4.4, all package versions match (as indicated by no bold or italic entries).
>>>
>>> - Bert -
>>
>> This means that one should now be able to hit "update" on the 44
>> update stream and not have an error, right?
>
> What error? Didn't try that, this is about the trunk update stream, not the 4.4 update stream.
>
>> I had thought/hoped that the error would resolve itself when the first
>> update to 44 went in. But I think it's just another area where I can
>> become less ignorant.
>
> If 4.4 has no update map yet then this would explain the error. Yes, you should publish one as update-fbs.1.

OK, I wrote a bad update-fbs.1 (bad, because no repository) but
update-fbs.2 looks to be good. And updating from squeak44 now doesn't
fail.

>> How best would we fix this for 4.5? We have a script in the
>> ReleaseBuilder (#transferCurrentPackages) that pushes all the latest
>> versions of trunk to the new update stream, so perhaps we can tweak
>> that to also produce an update map?
>>
>> frank
>
> Sounds about right.

I'll take a look at automating it (naturally):
http://bugs.squeak.org/view.php?id=7715

frank

> - Bert -