Re: [Pharo-project] [ANN 1.2.1Core] pre-build 1.2.1 Core image
On Mar 29, 2011, at 9:38 PM, Lukas Renggli wrote:
Is this intentional that the image was saved with a newer VM than previous builds?
This interpreter (vers. 6502) cannot read image file (vers. 6505).
Oh, yes... I have a new VM on my system (one compiled by our build system). And on the build server use right now Ian's latest unix vm that can read these images, too. This shows that 1.2 should have been released weeks ago. The world is moving on and it gets really difficult to go back to the past just to relase 1.2. So what do we do? The shity gforge means that we would need to generate a new link. Maybe named "1.2.1 this time really final?". I am getting tired of 1.2... Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.
I don't care if we move to 6505, I will just have to update my build server to use the new VM as well. So far I built with the old VM to make sure that the images also work on older VMs. Lukas On 29 March 2011 21:46, Marcus Denker <marcus.denker@inria.fr> wrote:
On Mar 29, 2011, at 9:38 PM, Lukas Renggli wrote:
Is this intentional that the image was saved with a newer VM than previous builds?
  This interpreter (vers. 6502) cannot read image file (vers. 6505).
Oh, yes... I have a new VM on my system (one compiled by our build system).
And on the build server use right now Ian's latest unix vm that can read these images, too.
This shows that 1.2 should have been released weeks ago. The world is moving on and it gets really difficult to go back to the past just to relase 1.2.
So what do we do? The shity gforge means that we would need to generate a new link.
Maybe named "1.2.1 this time really final?".
I am getting tired of 1.2...
    Marcus
-- Marcus Denker  -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.
-- Lukas Renggli www.lukas-renggli.ch
On Mar 29, 2011, at 9:49 PM, Lukas Renggli wrote:
I don't care if we move to 6505, I will just have to update my build server to use the new VM as well. So far I built with the old VM to make sure that the images also work on older VMs.
For the moment lukas this is the best solution. Because not all the plugins are not yeat available. We can do the bleeding edge test with our hudson and this is good to have yours as a backup for olderVMs. I use the old vm so far also for that (and because I'm slow :)).
Lukas
On 29 March 2011 21:46, Marcus Denker <marcus.denker@inria.fr> wrote:
On Mar 29, 2011, at 9:38 PM, Lukas Renggli wrote:
Is this intentional that the image was saved with a newer VM than previous builds?
This interpreter (vers. 6502) cannot read image file (vers. 6505).
Oh, yes... I have a new VM on my system (one compiled by our build system).
And on the build server use right now Ian's latest unix vm that can read these images, too.
This shows that 1.2 should have been released weeks ago. The world is moving on and it gets really difficult to go back to the past just to relase 1.2.
So what do we do? The shity gforge means that we would need to generate a new link.
Maybe named "1.2.1 this time really final?".
I am getting tired of 1.2...
Marcus
-- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.
-- Lukas Renggli www.lukas-renggli.ch
Pharo 1.2.1 looks good so far, except for the GLMOrangeUITheme that is still in a circular dependency. Lukas On 29 March 2011 22:07, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
On Mar 29, 2011, at 9:49 PM, Lukas Renggli wrote:
I don't care if we move to 6505, I will just have to update my build server to use the new VM as well. So far I built with the old VM to make sure that the images also work on older VMs.
For the moment lukas this is the best solution. Because not all the plugins are not yeat available. We can do the bleeding edge test with our hudson and this is good to have yours as a backup for olderVMs. I use the old vm so far also for that (and because I'm slow :)).
Lukas
On 29 March 2011 21:46, Marcus Denker <marcus.denker@inria.fr> wrote:
On Mar 29, 2011, at 9:38 PM, Lukas Renggli wrote:
Is this intentional that the image was saved with a newer VM than previous builds?
  This interpreter (vers. 6502) cannot read image file (vers. 6505).
Oh, yes... I have a new VM on my system (one compiled by our build system).
And on the build server use right now Ian's latest unix vm that can read these images, too.
This shows that 1.2 should have been released weeks ago. The world is moving on and it gets really difficult to go back to the past just to relase 1.2.
So what do we do? The shity gforge means that we would need to generate a new link.
Maybe named "1.2.1 this time really final?".
I am getting tired of 1.2...
    Marcus
-- Marcus Denker  -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.
-- Lukas Renggli www.lukas-renggli.ch
-- Lukas Renggli www.lukas-renggli.ch
On 29 March 2011 22:18, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
Pharo 1.2.1 looks good so far, except for the GLMOrangeUITheme that is still in a circular dependency.
Lukas
Can you open a ticket? I want to clean all the themes soon in 1.3
i wonder how it is happen that this bug not eliminated before switching to 1.3 line? i remember that we fixed it few updates later.
Stef
-- Best regards, Igor Stasenko AKA sig.
On Mar 29, 2011, at 9:46 PM, Marcus Denker wrote:
On Mar 29, 2011, at 9:38 PM, Lukas Renggli wrote:
Is this intentional that the image was saved with a newer VM than previous builds?
This interpreter (vers. 6502) cannot read image file (vers. 6505).
Oh, yes... I have a new VM on my system (one compiled by our build system).
Ok. So I will redo the image... Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.
participants (4)
-
Igor Stasenko -
Lukas Renggli -
Marcus Denker -
Stéphane Ducasse