(no subject)
Locked
12
12
 
|
On Wed, Sep 20, 2017 at 1:12 PM, Ben Coman <[hidden email]> wrote:
but this works okay... $ curl get.pharo.org/70+vm | bash $ ./pharo-ui + World > Tools > Iceberg ==> iceberg opens okay while this PharoLauncher alternative fails... $ curl get.pharo.org | bash $ ./pharo-ui + World > Tools > Catalog > PharoLauncher <Install stable configuration> + World > PharoLauncher ==> Doesn't show Pharo 7 templates + World > Monticello > ...PharoLauncher/main <Open Repository> + ConfigurationOfPharoLauncher-ChristopheDemarey.56 <Load> + World > Playground > "ConfigurationOfPharoLauncher load" <DoIt> + World > PharoLauncher > Settings > Hard reset persistant state ==> Pharo 7 templates showing + '7latest32' <Launch> "i.e. the previously downloaded image" + World > Tools > Iceberg ==> "Error: External module not found" + World > Monticello... load latest mczs... * PharoLauncher-Core-ChristopheDemarey.123 * PharoLauncher-Spec-ChristopheDemarey.51 + '7latest32' <Launch> "i.e. the previously downloaded image" ==> "Fetching VM to run Pharo 70 images" + World > Tools > Iceberg ==> "Error: External module not found" Version comparison... direct get.pharo.org/70+vm /home/ben/Pharo/adhoc/Pharo7/Pharo.image Pharo7.0alpha.build.132.sha.4ea2f39a9f43185d31b844be5ad33b677f43bf17 /home/ben/Pharo/adhoc/Pharo7/pharo-vm/lib/pharo/5.0-201708271955/pharo CoInterpreter VMMaker.oscog-eem.2265 uuid: 76b62109-629a-4c39-9641-67b53321df9a Aug 27 2017 via PharoLauncher... /home/ben/Pharo/images/7latest32/7latest32.image Pharo7.0alpha.build.132.sha.4ea2f39a9f43185d31b844be5ad33b677f43bf17 /home/ben/Pharo/vms/70-x86/lib/pharo/5.0-201708271955/pharo CoInterpreter VMMaker.oscog-eem.2265 uuid: 76b62109-629a-4c39-9641-67b53321df9a Aug 27 2017 Must be something environmental in lookup paths. Can you reproduce or suggest further investigation I can do? cheers -ben |
|
|
On 20-09-17 08:26, Ben Coman wrote:
> Must be something environmental in lookup paths. Can you reproduce or > suggest further investigation I can do? If I understand it correctly it is a problem with the unzipping. Not handling symlinks and preserving permissions. Is that a plugin problem? Stephan |
|
|
Hi Sean, Stephan,
I just updated the PharoLauncher and it should now work fine for 64-bits images. I just had time to test it roughly but you can give it a try (https://ci.inria.fr/pharo/view/Launcher/job/Launcher/149/). Christophe. > Le 20 sept. 2017 à 10:52, stephan <[hidden email]> a écrit : > > On 20-09-17 08:26, Ben Coman wrote: > >> Must be something environmental in lookup paths. Can you reproduce or suggest further investigation I can do? > > If I understand it correctly it is a problem with the unzipping. Not handling symlinks and preserving permissions. Is that a plugin problem? > > Stephan > > |
|
|
On 20/09/17 12:17, Christophe Demarey wrote:
> I just updated the PharoLauncher and it should now work fine for 64-bits images. > I just had time to test it roughly but you can give it a try (https://ci.inria.fr/pharo/view/Launcher/job/Launcher/149/). Pharo7 64 bit starts fine on Mac. Good work. Stephan |
|
|
In reply to this post by Sean P. DeNigris
On 17/09/17 05:21, Sean P. DeNigris wrote:
> demarey wrote >> Let us know if everything is fine. > > Was this issue [1] fixed: >> I think I found it. It seems to be a bug in the way Launcher/Pharo unzips >> the downloaded VM. >> The symlink libgit2.dylib becomes unlinked and appears as just a regular >> file. If I delete the >> Pharo.app and unzip 70.zip (which btw maybe should have been deleted >> during cleanup after >> the dl) to ./vms/70, the error disappears! With todays bleedingEdge PharoLauncher on mac I was able to download and start 60510. When trying to load GToolKit Iceberg enableMetacelloIntegration: true. Metacello new baseline: 'GToolkit'; repository: 'github://feenkcom/gtoolkit/src'; load. I ran into some problem with libgit2 that I could solve by doing the unzipping of the downloaded vm zipfile with the Archive Utility and replacing the vm (and re-adding the sources). Stephan |
|
|
In reply to this post by demarey
Christophe
which version should we take? Stef On Wed, Sep 20, 2017 at 12:17 PM, Christophe Demarey <[hidden email]> wrote: > Hi Sean, Stephan, > > I just updated the PharoLauncher and it should now work fine for 64-bits images. > I just had time to test it roughly but you can give it a try (https://ci.inria.fr/pharo/view/Launcher/job/Launcher/149/). > > Christophe. > > >> Le 20 sept. 2017 à 10:52, stephan <[hidden email]> a écrit : >> >> On 20-09-17 08:26, Ben Coman wrote: >> >>> Must be something environmental in lookup paths. Can you reproduce or suggest further investigation I can do? >> >> If I understand it correctly it is a problem with the unzipping. Not handling symlinks and preserving permissions. Is that a plugin problem? >> >> Stephan >> >> > > |
|
|
In reply to this post by Stephan Eggermont-3
> Le 20 sept. 2017 à 23:36, Stephan Eggermont <[hidden email]> a écrit : > > On 17/09/17 05:21, Sean P. DeNigris wrote: >> demarey wrote >>> Let us know if everything is fine. >> Was this issue [1] fixed: >>> I think I found it. It seems to be a bug in the way Launcher/Pharo unzips >>> the downloaded VM. >>> The symlink libgit2.dylib becomes unlinked and appears as just a regular >>> file. If I delete the >>> Pharo.app and unzip 70.zip (which btw maybe should have been deleted >>> during cleanup after >>> the dl) to ./vms/70, the error disappears! > > With todays bleedingEdge PharoLauncher on mac I was able to download and start 60510. When trying to load GToolKit > > Iceberg enableMetacelloIntegration: true. > Metacello new > baseline: 'GToolkit'; > repository: 'github://feenkcom/gtoolkit/src'; > load. > > I ran into some problem with libgit2 that I could solve by doing the unzipping of the downloaded vm zipfile with the Archive Utility and replacing the vm (and re-adding the sources). I tried to reproduce the problem with the same configuration without success. It works well. I guess you already downloaded the required VM with a previous version of the launcher (using Pharo unzipping). If you delete this VM and use the launcher to run the image, it should download the VM and uses your system unzip command to extract it. |
|
|
In reply to this post by Stephane Ducasse-3
> Le 21 sept. 2017 à 13:25, Stephane Ducasse <[hidden email]> a écrit : > > Christophe > > which version should we take? For now, the bleeding edge. I will publish a stable as soon as it gets tested enough. |
|
|
In reply to this post by Ben Coman
Hi Ben,
Could you test it with the bleedingEdge version of the launcher to see if the problem is solved? Thanks, Christophe.
|
|
|
Could you clarify where to download from?
I tried PharoLauncher-user-bleedingEdge-2017.09.20.zip from... https://ci.inria.fr/pharo/view/Launcher/job/Launcher/149/PHARO=61,VERSION=bleedingEdge,VM=vm,label=linux/ with the Pharo-linux-0.2.13.zip I previously downloaded (limited time before bed) cheers -ben On Thu, Sep 21, 2017 at 9:45 PM, Christophe Demarey <[hidden email]> wrote:
|
«
Return to Pharo Smalltalk Users
|
1 view|%1 views
| Free forum by Nabble | Edit this page |