[Glass] Warning: GsDevKitHome scripts for building pharo images are currently broken ...
Locked
[Glass] Warning: GsDevKitHome scripts for building pharo images are currently broken ...
 
|
Apparently when the folks updating the Pharo ZeroConf scripts[1] used
for downloading Pharo3.0 finished their work, they decided that the urls used for downloading the pharo vm would be discontinued: nehalem:pharo daleh$ wget -O- get.pharo.org/vmLatest | bash --2015-04-07 21:15:05-- http://get.pharo.org/vmLatest Resolving get.pharo.org... 128.93.162.72 Connecting to get.pharo.org|128.93.162.72|:80... connected. HTTP request sent, awaiting response... 404 Not Found 2015-04-07 21:15:06 ERROR 404: Not Found. This of course breaks the $GS_HOME/bin/installPharo script. It looks like the workaround is to replace get.pharo.org/vmLatest with get.pharo.org/vm30 in the $GS_HOME/bin/installPharo script ... I am not going to push out a patch until I decide whether to continue to use get.pharo.org or go with the more stable route of downloading vms and images directly from the ftp site ... Sorry for any convenience this may cause ... I've created an issue[2] for this if you're interested ... Dale [1] http://forum.world.st/Updating-ZeroConf-Please-do-not-use-it-until-new-advice-td4818041.html [2] https://github.com/GsDevKit/gsDevKitHome/issues/76 _______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
Re: [Glass] Warning: GsDevKitHome scripts for building pharo images are currently broken ...
|
|
The Pharo folks have restored the http://get.pharo.org/vmLatest service
and have acknowledged that it was a mistake to just turn it off ... The service will be maintained for another 2-3 months giving us time to convert in an orderly fashion. I am still torn about using get.pharo.org. The little bash script that get's run when you hit the url, is awfully convenient and if I were to switch to direct ftp downloads, I'd have to duplicate (and maintain) a similar script myself and learn more about pharo's (potentially changing) execution model than I'd like ... Thoughts? Dale On 4/7/15 9:37 PM, Dale Henrichs wrote: > Apparently when the folks updating the Pharo ZeroConf scripts[1] used > for downloading Pharo3.0 finished their work, they decided that the > urls used for downloading the pharo vm would be discontinued: > > nehalem:pharo daleh$ wget -O- get.pharo.org/vmLatest | bash > --2015-04-07 21:15:05-- http://get.pharo.org/vmLatest > Resolving get.pharo.org... 128.93.162.72 > Connecting to get.pharo.org|128.93.162.72|:80... connected. > HTTP request sent, awaiting response... 404 Not Found > 2015-04-07 21:15:06 ERROR 404: Not Found. > > This of course breaks the $GS_HOME/bin/installPharo script. It looks > like the workaround is to replace get.pharo.org/vmLatest with > get.pharo.org/vm30 in the $GS_HOME/bin/installPharo script ... > > I am not going to push out a patch until I decide whether to continue > to use get.pharo.org or go with the more stable route of downloading > vms and images directly from the ftp site ... > > Sorry for any convenience this may cause ... I've created an issue[2] > for this if you're interested ... > > Dale > > [1] > http://forum.world.st/Updating-ZeroConf-Please-do-not-use-it-until-new-advice-td4818041.html > [2] https://github.com/GsDevKit/gsDevKitHome/issues/76 _______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
Re: [Glass] Warning: GsDevKitHome scripts for building pharo images are currently broken ...
|
|
Why not use the new url?
> On 08 Apr 2015, at 16:41, Dale Henrichs via Glass <[hidden email]> wrote: > > The Pharo folks have restored the http://get.pharo.org/vmLatest service and have acknowledged that it was a mistake to just turn it off ... > > The service will be maintained for another 2-3 months giving us time to convert in an orderly fashion. > > I am still torn about using get.pharo.org. > > The little bash script that get's run when you hit the url, is awfully convenient and if I were to switch to direct ftp downloads, I'd have to duplicate (and maintain) a similar script myself and learn more about pharo's (potentially changing) execution model than I'd like ... > > Thoughts? > > Dale > > On 4/7/15 9:37 PM, Dale Henrichs wrote: >> Apparently when the folks updating the Pharo ZeroConf scripts[1] used for downloading Pharo3.0 finished their work, they decided that the urls used for downloading the pharo vm would be discontinued: >> >> nehalem:pharo daleh$ wget -O- get.pharo.org/vmLatest | bash >> --2015-04-07 21:15:05-- http://get.pharo.org/vmLatest >> Resolving get.pharo.org... 128.93.162.72 >> Connecting to get.pharo.org|128.93.162.72|:80... connected. >> HTTP request sent, awaiting response... 404 Not Found >> 2015-04-07 21:15:06 ERROR 404: Not Found. >> >> This of course breaks the $GS_HOME/bin/installPharo script. It looks like the workaround is to replace get.pharo.org/vmLatest with get.pharo.org/vm30 in the $GS_HOME/bin/installPharo script ... >> >> I am not going to push out a patch until I decide whether to continue to use get.pharo.org or go with the more stable route of downloading vms and images directly from the ftp site ... >> >> Sorry for any convenience this may cause ... I've created an issue[2] for this if you're interested ... >> >> Dale >> >> [1] http://forum.world.st/Updating-ZeroConf-Please-do-not-use-it-until-new-advice-td4818041.html >> [2] https://github.com/GsDevKit/gsDevKitHome/issues/76 > > _______________________________________________ > Glass mailing list > [hidden email] > http://lists.gemtalksystems.com/mailman/listinfo/glass _______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
Re: [Glass] Warning: GsDevKitHome scripts for building pharo images are currently broken ...
|
|
The simple issue is I am concerned that support for the vm30 url will
eventually go away and if that is going to happen I am better off biting the bullet now (while I "know the pharo details") and writing an ftp-based script that will work forever There was discussion several months ago about dropping zeroconf support older pharo versions which implies that eventually the vm30 url will go away. AFAIK there is no stated policy about how long these urls will be kept around. Recently an url that I had been using for an older version of Pharo (1.3 I think) was no longer reachable and when I went to the new site, the version that I downloaded had vm-related issues (where the vm and image didn't match) ... so I had to scramble to figure out a combination of image releases and vm releases that would work together without the benefit of having the old site/url to use as a reference ... so I've been burned by this in the recent past and I'm not looking into figuring out how to reverse engineer the vm30 script a couple of years from now... Does that make sense? Dale On 4/8/15 7:45 AM, Johan Brichau wrote: > Why not use the new url? > >> On 08 Apr 2015, at 16:41, Dale Henrichs via Glass <[hidden email]> wrote: >> >> The Pharo folks have restored the http://get.pharo.org/vmLatest service and have acknowledged that it was a mistake to just turn it off ... >> >> The service will be maintained for another 2-3 months giving us time to convert in an orderly fashion. >> >> I am still torn about using get.pharo.org. >> >> The little bash script that get's run when you hit the url, is awfully convenient and if I were to switch to direct ftp downloads, I'd have to duplicate (and maintain) a similar script myself and learn more about pharo's (potentially changing) execution model than I'd like ... >> >> Thoughts? >> >> Dale >> >> On 4/7/15 9:37 PM, Dale Henrichs wrote: >>> Apparently when the folks updating the Pharo ZeroConf scripts[1] used for downloading Pharo3.0 finished their work, they decided that the urls used for downloading the pharo vm would be discontinued: >>> >>> nehalem:pharo daleh$ wget -O- get.pharo.org/vmLatest | bash >>> --2015-04-07 21:15:05-- http://get.pharo.org/vmLatest >>> Resolving get.pharo.org... 128.93.162.72 >>> Connecting to get.pharo.org|128.93.162.72|:80... connected. >>> HTTP request sent, awaiting response... 404 Not Found >>> 2015-04-07 21:15:06 ERROR 404: Not Found. >>> >>> This of course breaks the $GS_HOME/bin/installPharo script. It looks like the workaround is to replace get.pharo.org/vmLatest with get.pharo.org/vm30 in the $GS_HOME/bin/installPharo script ... >>> >>> I am not going to push out a patch until I decide whether to continue to use get.pharo.org or go with the more stable route of downloading vms and images directly from the ftp site ... >>> >>> Sorry for any convenience this may cause ... I've created an issue[2] for this if you're interested ... >>> >>> Dale >>> >>> [1] http://forum.world.st/Updating-ZeroConf-Please-do-not-use-it-until-new-advice-td4818041.html >>> [2] https://github.com/GsDevKit/gsDevKitHome/issues/76 >> _______________________________________________ >> Glass mailing list >> [hidden email] >> http://lists.gemtalksystems.com/mailman/listinfo/glass _______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
Re: [Glass] Warning: GsDevKitHome scripts for building pharo images are currently broken ...
|
|
It does make sense if you want to keep supporting older versions.
So, the question ultimately boils down to wether you want to still build using older versions of Pharo which the Pharo team does no longer ‘support’? I’m not criticizing, just asking out loud :) Johan > On 08 Apr 2015, at 17:45, Dale Henrichs <[hidden email]> wrote: > > The simple issue is I am concerned that support for the vm30 url will eventually go away and if that is going to happen I am better off biting the bullet now (while I "know the pharo details") and writing an ftp-based script that will work forever > > There was discussion several months ago about dropping zeroconf support older pharo versions which implies that eventually the vm30 url will go away. AFAIK there is no stated policy about how long these urls will be kept around. > > Recently an url that I had been using for an older version of Pharo (1.3 I think) was no longer reachable and when I went to the new site, the version that I downloaded had vm-related issues (where the vm and image didn't match) ... so I had to scramble to figure out a combination of image releases and vm releases that would work together without the benefit of having the old site/url to use as a reference ... so I've been burned by this in the recent past and I'm not looking into figuring out how to reverse engineer the vm30 script a couple of years from now... > > Does that make sense? > > Dale > > On 4/8/15 7:45 AM, Johan Brichau wrote: >> Why not use the new url? >> >>> On 08 Apr 2015, at 16:41, Dale Henrichs via Glass <[hidden email]> wrote: >>> >>> The Pharo folks have restored the http://get.pharo.org/vmLatest service and have acknowledged that it was a mistake to just turn it off ... >>> >>> The service will be maintained for another 2-3 months giving us time to convert in an orderly fashion. >>> >>> I am still torn about using get.pharo.org. >>> >>> The little bash script that get's run when you hit the url, is awfully convenient and if I were to switch to direct ftp downloads, I'd have to duplicate (and maintain) a similar script myself and learn more about pharo's (potentially changing) execution model than I'd like ... >>> >>> Thoughts? >>> >>> Dale >>> >>> On 4/7/15 9:37 PM, Dale Henrichs wrote: >>>> Apparently when the folks updating the Pharo ZeroConf scripts[1] used for downloading Pharo3.0 finished their work, they decided that the urls used for downloading the pharo vm would be discontinued: >>>> >>>> nehalem:pharo daleh$ wget -O- get.pharo.org/vmLatest | bash >>>> --2015-04-07 21:15:05-- http://get.pharo.org/vmLatest >>>> Resolving get.pharo.org... 128.93.162.72 >>>> Connecting to get.pharo.org|128.93.162.72|:80... connected. >>>> HTTP request sent, awaiting response... 404 Not Found >>>> 2015-04-07 21:15:06 ERROR 404: Not Found. >>>> >>>> This of course breaks the $GS_HOME/bin/installPharo script. It looks like the workaround is to replace get.pharo.org/vmLatest with get.pharo.org/vm30 in the $GS_HOME/bin/installPharo script ... >>>> >>>> I am not going to push out a patch until I decide whether to continue to use get.pharo.org or go with the more stable route of downloading vms and images directly from the ftp site ... >>>> >>>> Sorry for any convenience this may cause ... I've created an issue[2] for this if you're interested ... >>>> >>>> Dale >>>> >>>> [1] http://forum.world.st/Updating-ZeroConf-Please-do-not-use-it-until-new-advice-td4818041.html >>>> [2] https://github.com/GsDevKit/gsDevKitHome/issues/76 >>> _______________________________________________ >>> Glass mailing list >>> [hidden email] >>> http://lists.gemtalksystems.com/mailman/listinfo/glass > _______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
Re: [Glass] Warning: GsDevKitHome scripts for building pharo images are currently broken ...
|
|
On 04/08/2015 10:02 AM, Johan Brichau wrote: > It does make sense if you want to keep supporting older versions. > So, the question ultimately boils down to wether you want to still build using older versions of Pharo which the Pharo team does no longer ‘support’? > Of the 15 forks of gsDevKitHome, I am the only person running on the latest version of the master branch. So it appears that folks already aren't in the habit of upgrading the scripts and I am worried that in 4 years when I presume Pharo3.0 is dropped from the zeroconf site and you start getting a 404 for the vm30 and pharo30 urls that you guys will be faced with this question ... If the Pharo folks said: The zeroconf urls will work as long as the site is alive. When a Pharo release goes off support the image, changes, sources and vm download urls will be changed to be static urls that provide the last supported version. then this would not be an issue. It will definitely be easier to "just use the url", but I don't relish the thought of dealing with the fire drill that I hit yesterday when a perfectly good url starts giving 404's... So I am guilty of thinking ahead ... and perhaps I shouldn't worry... Dale _______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
Re: [Glass] Warning: GsDevKitHome scripts for building pharo images are currently broken ...
|
|
Maybe you could just set up an http mirror of get.pharo.org, and copy the zeroconf script and associated file storage to it. If this is simple, it would last forever and avoid having to learn too much about pharo internals. On Wed, Apr 8, 2015 at 12:48 PM, Dale Henrichs via Glass <[hidden email]> wrote:
_______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
Re: [Glass] Warning: GsDevKitHome scripts for building pharo images are currently broken ...
|
|
Lyn,
this isn't a bad idea ... to be honest I have figured that if I were to spend the time writing "my own zeroconf script" I would start with the current zeroconf script for 30:) If folks feel that I am too worried about this problem, then just editing the script to use the new url is the path I will take ... If folks would prefer that we "take control of the problem" and manage the downloads directly from the web-site, then I will take the time to do so while the "iron is hot" I am in the midst of trying to get 1.0.0 out the door and now would be the time to add the script ... Dale On 04/09/2015 09:27 AM, Lyn Headley
wrote:
_______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
«
Return to GLASS
|
1 view|%1 views
| Free forum by Nabble | Edit this page |