Ok - then it could be that the jobs that produce those Platform specific builds could be messed up (at least for windows).
If you want the latest build - follow the CI link mentioned on Smalltalk hub - which will end up on Jenkins, and the latex build is 886 - https://ci.inria.fr/pharo-contribution/job/PharoLauncher/886/PHARO=30,VERSION=bleedingEdge,VM=vm/ If you take that .image file you will have the absolute latest - which does show Moose and Pharo 4. And I agree - we will leave Damien alone and when he gets back he said he would look at my changes anyway - which should cause new platform builds. Tim On 27 Aug 2014, at 16:55, kilon alios <[email protected]> wrote: > No dont talk to Damien if he is on holiday , I prefer to respect people free > time / relaxation time. This can wait for when Damien will be back. Both > Damien and I frequent the irc channel so we will talk , its not a problem. > > As I said in my original post I am downloading PharoLauncher from > Smalltalkhub links that can be located here > > http://www.smalltalkhub.com/#!/~Pharo/PharoLauncher > > the link you posted is not contained in there , I used this > > https://ci.inria.fr/pharo-contribution/job/PharoLauncher-Win-Package/lastSuccessfulBuild/artifact/pharo-ci/pharo_installer.exe > > and this > > https://ci.inria.fr/pharo-contribution/job/PharoLauncherFinalUserImage/lastSuccessfulBuild/artifact/PharoLauncher.zip > > As I said my problem is on Windows, on MacOS its fine . > > > On Wed, Aug 27, 2014 at 5:49 PM, Tim Mackinnon <[email protected]> wrote: > Hmmm that sounds strange (it could be I messed something up) - but did you > get your zip file from: > https://ci.inria.fr/pharo-contribution/job/PharoLauncher/885/PHARO=30,VERSION=bleedingEdge,VM=vm/ > ?? > > I just tested that one (but on OSX) and it shows my change as well as > templates for Moose 5 and Pharo 4. > > I’ve just pushed another change (which would be 886), which also fixes a bug > Stef mentioned (if underlying files change, it used to terminate instead of > refreshing) - that should build shortly. > > However - the links on SmalltalkHub are still pointing to images from Jun > (the Hudson jobs aren’t triggered automatically it seems) - so I think you > might be running something other than what you think you are running. > > Anyway - let me know what happens, and I’ll try and talk to Damien (who is on > holiday) - and sort it out if I’ve broken it. > > Tim > > On 27 Aug 2014, at 15:16, kilon alios <[email protected]> wrote: > >> I mean PharoLauncher cannot download Pharo 4 because it displays no such >> option. No Moose 5 , etc etc. Its also the old GUI. So this must be the >> latest version, I am not near my window pc now at work so I will try >> tomorrow the developer mode to see exactly which version of PharoLauncher it >> is. >> >> Are you on windows ? >> >> >> On Wed, Aug 27, 2014 at 5:07 PM, Tim Mackinnon <[email protected]> wrote: >> What do you mean by Pharo 4 template? I just made a contribution yesterday - >> watched it build the new zip file, and I just downloaded that zip and I am >> seeing a “Pharo 4.0 (beta)” template tree? >> >> Just to check you are using the latest version, if you right click on a >> template and choose “Create Image” - does it prefix the parent of the >> template to the suggested name (e.g. Pharo 3.0-latest)? (this was the change >> I made). >> >> It might be worth checking your settings as well (click on the icon lower >> right) and check that you haven’t accidentally unticked the Pharo 4.0 >> repository. >> >> Tim >> >> On 27 Aug 2014, at 09:28, kilon alios <[email protected]> wrote: >> >>> I also downloaded the zip file it still does not give me the same version >>> as MacOSX, no Pharo 4 template >>> >>> >>> On Wed, Aug 27, 2014 at 11:04 AM, kilon alios <[email protected]> wrote: >>> I downloaded PharoLauncher from smalltalkhub for Windows and it appears is >>> not the latest version for example it has no template for downloading Pharo >>> 4. >>> >> >> > >
