Smalltalk › Squeak › Squeak - Dev

4.1 release candidate 3

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

15 messages Options

Andreas.Raab

4.1 release candidate 3

Folks -

I just finished rc3 for the 4.1 release and unless I'm missing something
this is probably "it". It feels solid, there are no pending issues and
consequently I'd like everyone to treat this as if it is the release.
Download it here:

http://ftp.squeak.org/trunk/4.1rc3

There are several changes in this build including:

* We now have a full set of updated VMs. Ian's 4.0.2 series isn't
announced yet but he compiled the x86 variants already so I've included
it for rc3.

* This candidate uses the 4.1 release repository at
http://source.squeak.org/squeak41 for updates instead of the trunk. The
4.1 release repository has also been added to the default set of
repositories in the build. To receive trunk updates you will have to
change the preference to point it to the trunk repository instead.

* The sources file has been rebuilt. If you'll recall rc2 had
overwritten the beginning of the sources file with a timestamp so it was
no good. Please make sure you DELETE any rc2's that you might be using
since the sources file is not compatible between rc2 and rc3.

Since I haven't seen any changes on the remaining Mantis bugs (most of
the ones left open are beyond scope for this late in the release cycle)
I don't see anything at this point that would prevent us from publishing
rc3 as the release in a couple of days.

Please keep testing. If everything goes well I'd like to copy rc3 simply
to its final location next week and declare victory.

Cheers,
- Andreas

Bert Freudenberg

Re: 4.1 release candidate 3

On 11.04.2010, at 09:36, Andreas Raab wrote:

>
> Folks -
>
> I just finished rc3 for the 4.1 release and unless I'm missing something this is probably "it". It feels solid, there are no pending issues and consequently I'd like everyone to treat this as if it is the release. Download it here:
>
> http://ftp.squeak.org/trunk/4.1rc3
>
> There are several changes in this build including:
>
> * We now have a full set of updated VMs. Ian's 4.0.2 series isn't announced yet but he compiled the x86 variants already so I've included it for rc3.
>
> * This candidate uses the 4.1 release repository at http://source.squeak.org/squeak41 for updates instead of the trunk. The 4.1 release repository has also been added to the default set of repositories in the build. To receive trunk updates you will have to change the preference to point it to the trunk repository instead.
>
> * The sources file has been rebuilt. If you'll recall rc2 had overwritten the beginning of the sources file with a timestamp so it was no good. Please make sure you DELETE any rc2's that you might be using since the sources file is not compatible between rc2 and rc3.
>
> Since I haven't seen any changes on the remaining Mantis bugs (most of the ones left open are beyond scope for this late in the release cycle) I don't see anything at this point that would prevent us from publishing rc3 as the release in a couple of days.
>
> Please keep testing. If everything goes well I'd like to copy rc3 simply to its final location next week and declare victory.
>
> Cheers,
> - Andreas

I did not test rc3 yet but updated my #9854 image. Reproducably, updating leaves an "empty" progress bar behind:

Unless someone else sees this it probably is safe to ignore, just wanted to let you know. Seems to be just a one-time glitch, further updates work fine.

- Bert -

PastedGraphic-4.png (29K) Download Attachment

Göran Krampe

Re: 4.1 release candidate 3

In reply to this post by Andreas.Raab

Hi!

Andreas Raab wrote:
> Please keep testing. If everything goes well I'd like to copy rc3 simply
> to its final location next week and declare victory.

I need to go away right now, but in... 4 hours or so when I get back I
will commit some changes to make SM functional (you know, so that it can
actually install stuff!).

regards, Göran

LawsonEnglish

Re: 4.1 release candidate 3

In reply to this post by Andreas.Raab

Andreas Raab wrote:
> Folks -
>
> I just finished rc3 for the 4.1 release and unless I'm missing
> something this is probably "it". It feels solid, there are no pending
> issues and consequently I'd like everyone to treat this as if it is
> the release. Download it here:
>
> http://ftp.squeak.org/trunk/4.1rc3
>

A slight nit: In http://ftp.squeak.org/trunk/4.1rc3/mac/ , the VM
included in the Squeak4.1.1-mac.zip is damaged. You have to replace it
with the Squeak 4.2.3beta1U.app.zip that sits next to it. No biggie,
but an extra step that shouldn't be there for the final release.

But wow you guys sure work fast.

Lawson

bpi

Re: 4.1 release candidate 3

Isn't the newer Squeak 4.2.4beta1U.app even better?

Cheers,
Bernhard

Am 11.04.2010 um 17:41 schrieb Lawson English:

> Andreas Raab wrote:
>> Folks -
>>
>> I just finished rc3 for the 4.1 release and unless I'm missing something this is probably "it". It feels solid, there are no pending issues and consequently I'd like everyone to treat this as if it is the release. Download it here:
>>
>> http://ftp.squeak.org/trunk/4.1rc3
>>
>
> A slight nit: In http://ftp.squeak.org/trunk/4.1rc3/mac/ , the VM included in the Squeak4.1.1-mac.zip is damaged. You have to replace it with the Squeak 4.2.3beta1U.app.zip that sits next to it. No biggie, but an extra step that shouldn't be there for the final release.
>
> But wow you guys sure work fast.
>
> Lawson
>
>
>

Ken G. Brown

Re: 4.1 release candidate 3

In reply to this post by LawsonEnglish

At 8:41 AM -0700 4/11/10, Lawson English apparently wrote:

>Andreas Raab wrote:
>>Folks -
>>
>>I just finished rc3 for the 4.1 release and unless I'm missing something this is probably "it". It feels solid, there are no pending issues and consequently I'd like everyone to treat this as if it is the release. Download it here:
>>
>> http://ftp.squeak.org/trunk/4.1rc3
>>
>
>A slight nit: In http://ftp.squeak.org/trunk/4.1rc3/mac/ , the VM included in the Squeak4.1.1-mac.zip is damaged. You have to replace it with the Squeak 4.2.3beta1U.app.zip that sits next to it. No biggie, but an extra step that shouldn't be there for the final release.
>
>But wow you guys sure work fast.
>
>Lawson

Why isn't it the later Squeak 4.2.4beta1U.app?

Ken G. Brown

Andreas.Raab

Re: 4.1 release candidate 3

In reply to this post by LawsonEnglish

On 4/11/2010 8:41 AM, Lawson English wrote:

> Andreas Raab wrote:
>> Folks -
>>
>> I just finished rc3 for the 4.1 release and unless I'm missing
>> something this is probably "it". It feels solid, there are no pending
>> issues and consequently I'd like everyone to treat this as if it is
>> the release. Download it here:
>>
>> http://ftp.squeak.org/trunk/4.1rc3
>>
>
> A slight nit: In http://ftp.squeak.org/trunk/4.1rc3/mac/ , the VM
> included in the Squeak4.1.1-mac.zip is damaged.

Ouch. Damaged? In what form? The build process simply extracts the VM
and puts it into the same directory. Is this a permission issue perhaps?
(i.e., do I need some or all of the VM to be executable when I make the
build?)

Cheers,
- Andreas

Andreas.Raab

Re: 4.1 release candidate 3

In reply to this post by Bert Freudenberg

On 4/11/2010 5:36 AM, Bert Freudenberg wrote:
> I did not test rc3 yet but updated my #9854 image. Reproducably, updating leaves an "empty" progress bar behind:
>
> Unless someone else sees this it probably is safe to ignore, just wanted to let you know. Seems to be just a one-time glitch, further updates work fine.

I had the same issue and decided to simply ignore it (i.e., delete the
progress morph and move on).

Cheers,
- Andreas

LawsonEnglish

Re: 4.1 release candidate 3

In reply to this post by Andreas.Raab

Andreas Raab wrote:

> On 4/11/2010 8:41 AM, Lawson English wrote:
>> Andreas Raab wrote:
>>> Folks -
>>>
>>> I just finished rc3 for the 4.1 release and unless I'm missing
>>> something this is probably "it". It feels solid, there are no pending
>>> issues and consequently I'd like everyone to treat this as if it is
>>> the release. Download it here:
>>>
>>> http://ftp.squeak.org/trunk/4.1rc3
>>>
>>
>> A slight nit: In http://ftp.squeak.org/trunk/4.1rc3/mac/ , the VM
>> included in the Squeak4.1.1-mac.zip is damaged.
>
> Ouch. Damaged? In what form? The build process simply extracts the VM
> and puts it into the same directory. Is this a permission issue
> perhaps? (i.e., do I need some or all of the VM to be executable when
> I make the build?)

Haven't looked into it further. Just the icon is grey on my mac. Double
clicking informs you its damaged. The same file sitting outside that
zipped directory works just fine.

Lawson
.

Josh Gargus

Re: 4.1 release candidate 3

It's pretty weird... it seems like there's a directory with the same name as the VM that contains the VM:

Lumi-4:~ schwa$ cd /Users/schwa/Squeak/images/pristine/Squeak4.1.1-mac/Squeak\ 4.2.3beta1U.app
Lumi-4:Squeak 4.2.3beta1U.app schwa$ ls
Squeak 4.2.3beta1U.app __MACOSX

If I look inside the inner Squeak 4.2.3beta1U.app, it looks like a normal OS X Squeak VM (eg: the actual executable is inside in "Contents/MacOS/Squeak VM Opt"). When I try to run the inner VM, it works fine.

Not sure how this could have happened. Perhaps the unzipper created a directory with the same name and unzipped into that?

Cheers,
Josh

On Apr 11, 2010, at 3:55 PM, Lawson English wrote:

> Andreas Raab wrote:
>> On 4/11/2010 8:41 AM, Lawson English wrote:
>>> Andreas Raab wrote:
>>>> Folks -
>>>>
>>>> I just finished rc3 for the 4.1 release and unless I'm missing
>>>> something this is probably "it". It feels solid, there are no pending
>>>> issues and consequently I'd like everyone to treat this as if it is
>>>> the release. Download it here:
>>>>
>>>> http://ftp.squeak.org/trunk/4.1rc3
>>>>
>>>
>>> A slight nit: In http://ftp.squeak.org/trunk/4.1rc3/mac/ , the VM
>>> included in the Squeak4.1.1-mac.zip is damaged.
>>
>> Ouch. Damaged? In what form? The build process simply extracts the VM and puts it into the same directory. Is this a permission issue perhaps? (i.e., do I need some or all of the VM to be executable when I make the build?)
> Haven't looked into it further. Just the icon is grey on my mac. Double clicking informs you its damaged. The same file sitting outside that zipped directory works just fine.
>
> Lawson
> .
>
>

Andreas.Raab

Re: 4.1 release candidate 3

On 4/11/2010 6:05 PM, Josh Gargus wrote:
> It's pretty weird... it seems like there's a directory with the same name as the VM that contains the VM:
>
> Lumi-4:~ schwa$ cd /Users/schwa/Squeak/images/pristine/Squeak4.1.1-mac/Squeak\ 4.2.3beta1U.app
> Lumi-4:Squeak 4.2.3beta1U.app schwa$ ls
> Squeak 4.2.3beta1U.app __MACOSX
>
> If I look inside the inner Squeak 4.2.3beta1U.app, it looks like a normal OS X Squeak VM (eg: the actual executable is inside in "Contents/MacOS/Squeak VM Opt"). When I try to run the inner VM, it works fine.
>
> Not sure how this could have happened. Perhaps the unzipper created a directory with the same name and unzipped into that?

Ah, yes, of course. That would be it. The baseline makefile
(http://ftp.squeak.org/trunk/4.1rc1/makefile) says:

unzip -o "$(MACVM).zip" -d "tmp/mac/$(MACVM)"

I suppose this just needs to be

unzip -o "$(MACVM).zip" -d "tmp/mac/"

Thanks!
- Andreas

> On Apr 11, 2010, at 3:55 PM, Lawson English wrote:
>
>> Andreas Raab wrote:
>>> On 4/11/2010 8:41 AM, Lawson English wrote:
>>>> Andreas Raab wrote:
>>>>> Folks -
>>>>>
>>>>> I just finished rc3 for the 4.1 release and unless I'm missing
>>>>> something this is probably "it". It feels solid, there are no pending
>>>>> issues and consequently I'd like everyone to treat this as if it is
>>>>> the release. Download it here:
>>>>>
>>>>> http://ftp.squeak.org/trunk/4.1rc3
>>>>>
>>>>
>>>> A slight nit: In http://ftp.squeak.org/trunk/4.1rc3/mac/ , the VM
>>>> included in the Squeak4.1.1-mac.zip is damaged.
>>>
>>> Ouch. Damaged? In what form? The build process simply extracts the VM and puts it into the same directory. Is this a permission issue perhaps? (i.e., do I need some or all of the VM to be executable when I make the build?)
>> Haven't looked into it further. Just the icon is grey on my mac. Double clicking informs you its damaged. The same file sitting outside that zipped directory works just fine.
>>
>> Lawson
>> .
>>
>>
>
>
>

Chris Muller-3

Re: 4.1 release candidate 3

In reply to this post by Andreas.Raab

Damn, I thought this had gotten fixed. This has been an annoying bug
for us for a very long time; it happens all the time in 3.9, but I had
not seen in in 4.1, so I assumed someone had fixed it, but I guess it
didn't get fixed afterall! :(

On Sun, Apr 11, 2010 at 2:28 PM, Andreas Raab <[hidden email]> wrote:

> On 4/11/2010 5:36 AM, Bert Freudenberg wrote:
>>
>> I did not test rc3 yet but updated my #9854 image. Reproducably, updating
>> leaves an "empty" progress bar behind:
>>
>> Unless someone else sees this it probably is safe to ignore, just wanted
>> to let you know. Seems to be just a one-time glitch, further updates work
>> fine.
>
> I had the same issue and decided to simply ignore it (i.e., delete the
> progress morph and move on).
>
> Cheers,
> - Andreas
>
>

Alexander Lazarevic'

Re: 4.1 release candidate 3

In reply to this post by Andreas.Raab

> Damn, I thought this had gotten fixed. This has been an annoying bug
> for us for a very long time; it happens all the time in 3.9, but I had

I saw this for the first time at all and even not on the first update
run. And never read about any complains, that this "happens all the
time in 3.9". Is there some bug report or e-mail thread about this? I
wasn't always following the mailing list in the past.

I feel it is tricky to update the SystemProgressMorph using MC while
it is actually in use during updating itself. I got bitten by this a
few times and then was reluctant to do any more changes because of the
difficulties that could arise.
The last cosmetic change was to remove the borderlines of the bars.
Now this just takes an effect after the SystemProgressMorph gets
initialized again. Such code was missing at first in the postscript
and I added it later on.
Now I think the empty progress morph just stems from that attempt to
initialize it during a postscript while it is actually in use.
So my guess is, that this will only be seen once.

> not seen in in 4.1, so I assumed someone had fixed it, but I guess it
> didn't get fixed afterall! :(

>From my view there is and was nothing to be fixed.

Alex

Andreas.Raab

Re: 4.1 release candidate 3

In reply to this post by Chris Muller-3

On 4/13/2010 10:31 AM, Chris Muller wrote:
> Damn, I thought this had gotten fixed. This has been an annoying bug
> for us for a very long time; it happens all the time in 3.9, but I had
> not seen in in 4.1, so I assumed someone had fixed it, but I guess it
> didn't get fixed afterall! :(

The mechanism isn't robust in the face of resetting SystemProgressMorph.
Here is how to recreate the problem:

"First run this to reset SPM"
(1 to: 10) do:[:i|
(1 to: 10) do:[:j|
(i = 5 and:[j = 5]) ifTrue:[ SystemProgressMorph reset].
(Delay forMilliseconds: 10) wait.
] displayingProgress: 'Inner progress'.
] displayingProgress: 'Outer progress'.

"Now this will leave an empty SPM behind"
(1 to: 100) do:[:i| (Delay forMilliseconds: 10) wait]
displayingProgress: 'Yeeeha'.

"SystemProgressMorph reset" will fix it.

Cheers,
- Andreas

Igor Stasenko

Re: 4.1 release candidate 3

In reply to this post by Alexander Lazarevic'

I'm not sure if this related to 4.1,
but i found a minot glitch , after updating.

It shows me a list of Unbound methods after update done,
and this window doesn't bring forward when i clicking on it and remain
covered by other windows even after receiving
an input focus..
Every window/inspector i brought to life after update seems don't
having such glitch,
so i suspect this is related only to code which opens the 'Unbound
methods' window.

On 13 April 2010 21:53, Alexander Lazarević <[hidden email]> wrote:

>> Damn, I thought this had gotten fixed. This has been an annoying bug
>> for us for a very long time; it happens all the time in 3.9, but I had
>
> I saw this for the first time at all and even not on the first update
> run. And never read about any complains, that this "happens all the
> time in 3.9". Is there some bug report or e-mail thread about this? I
> wasn't always following the mailing list in the past.
>
> I feel it is tricky to update the SystemProgressMorph using MC while
> it is actually in use during updating itself. I got bitten by this a
> few times and then was reluctant to do any more changes because of the
> difficulties that could arise.
> The last cosmetic change was to remove the borderlines of the bars.
> Now this just takes an effect after the SystemProgressMorph gets
> initialized again. Such code was missing at first in the postscript
> and I added it later on.
> Now I think the empty progress morph just stems from that attempt to
> initialize it during a postscript while it is actually in use.
> So my guess is, that this will only be seen once.
>
>> not seen in in 4.1, so I assumed someone had fixed it, but I guess it
>> didn't get fixed afterall! :(
>
> >From my view there is and was nothing to be fixed.
>
> Alex
>
>

--
Best regards,
Igor Stasenko AKA sig.