How will this upgrade path will be handled?
In some email of previous week this is mentioned: SystemVersion newVersion: 'Pharo1.2.2a'. But evaluated in a Pharo 1.2.1 update 12345 starts updating from 12342 and stops on 12345, so I think that is wrong. Evaluating SystemVersion newVersion: 'Pharo1.2.2a' begin the update from 12346 and stops on 12350 so I think that is the correct one, right? Or should users begin with: https://gforge.inria.fr/frs/download.php/28436/PharoCore-1.2.2a-12345.zip and update from there? (This implies migrate to a new image, not so much a update from 1.2.1 to 1.2.2 but a migration). Thanks in advance. -- Miguel Cobá http://twitter.com/MiguelCobaMtz http://miguel.leugim.com.mx |
El lun, 25-04-2011 a las 11:00 -0500, Miguel Cobá escribió:
> How will this upgrade path will be handled? > > In some email of previous week this is mentioned: > > SystemVersion newVersion: 'Pharo1.2.2a'. I meant: SystemVersion newVersion: 'Pharo1.2.1a'. > > But evaluated in a Pharo 1.2.1 update 12345 starts updating from 12342 > and stops on 12345, so I think that is wrong. > > Evaluating > > SystemVersion newVersion: 'Pharo1.2.2a' > > begin the update from 12346 and stops on 12350 so I think that is the > correct one, right? > > Or should users begin with: > > https://gforge.inria.fr/frs/download.php/28436/PharoCore-1.2.2a-12345.zip > > and update from there? (This implies migrate to a new image, not so much > a update from 1.2.1 to 1.2.2 but a migration). > > Thanks in advance. > > Anyone? -- Miguel Cobá http://twitter.com/MiguelCobaMtz http://miguel.leugim.com.mx |
In reply to this post by Miguel Cobá
Hello,
In 1.2 we did a bad change: updating is not possible as soon as there is no letter in the version name. This means that you need to change the version number before you can updated. I fixe that in 1.2.2, though, so this is the last time this is needed. On Apr 26, 2011, at 2:09 AM, Miguel Cobá wrote: > El lun, 25-04-2011 a las 11:00 -0500, Miguel Cobá escribió: >> How will this upgrade path will be handled? >> >> In some email of previous week this is mentioned: >> >> SystemVersion newVersion: 'Pharo1.2.2a'. > > I meant: > > SystemVersion newVersion: 'Pharo1.2.1a'. > > >> >> But evaluated in a Pharo 1.2.1 update 12345 starts updating from 12342 >> and stops on 12345, so I think that is wrong. >> >> Evaluating >> >> SystemVersion newVersion: 'Pharo1.2.2a' >> >> begin the update from 12346 and stops on 12350 so I think that is the >> correct one, right? >> >> Or should users begin with: >> >> https://gforge.inria.fr/frs/download.php/28436/PharoCore-1.2.2a-12345.zip >> >> and update from there? (This implies migrate to a new image, not so much >> a update from 1.2.1 to 1.2.2 but a migration). >> >> Thanks in advance. >> >> > > Anyone? > > -- > Miguel Cobá > http://twitter.com/MiguelCobaMtz > http://miguel.leugim.com.mx > > > > -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD. |
Thanks, I understand.
Cheers El mié, 27-04-2011 a las 16:32 +0200, Marcus Denker escribió: > Hello, > > In 1.2 we did a bad change: updating is not possible as soon as there is no letter in the version name. > This means that you need to change the version number before you can updated. > > I fixe that in 1.2.2, though, so this is the last time this is needed. > > On Apr 26, 2011, at 2:09 AM, Miguel Cobá wrote: > > > El lun, 25-04-2011 a las 11:00 -0500, Miguel Cobá escribió: > >> How will this upgrade path will be handled? > >> > >> In some email of previous week this is mentioned: > >> > >> SystemVersion newVersion: 'Pharo1.2.2a'. > > > > I meant: > > > > SystemVersion newVersion: 'Pharo1.2.1a'. > > > > > >> > >> But evaluated in a Pharo 1.2.1 update 12345 starts updating from 12342 > >> and stops on 12345, so I think that is wrong. > >> > >> Evaluating > >> > >> SystemVersion newVersion: 'Pharo1.2.2a' > >> > >> begin the update from 12346 and stops on 12350 so I think that is the > >> correct one, right? > >> > >> Or should users begin with: > >> > >> https://gforge.inria.fr/frs/download.php/28436/PharoCore-1.2.2a-12345.zip > >> > >> and update from there? (This implies migrate to a new image, not so much > >> a update from 1.2.1 to 1.2.2 but a migration). > >> > >> Thanks in advance. > >> > >> > > > > Anyone? > > > > -- > > Miguel Cobá > > http://twitter.com/MiguelCobaMtz > > http://miguel.leugim.com.mx > > > > > > > > > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > -- Miguel Cobá http://twitter.com/MiguelCobaMtz http://miguel.leugim.com.mx |
Free forum by Nabble | Edit this page |