problem getting moose

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

problem getting moose

Ben Coman
I wanted to try out Peter's XMI Analyser with Roassal and went to
download Moose but had a couple of problems.

First try...
In the Launcher under Common Tools, I downloaded and Moose 5.1(stable)
fine, but it is Pharo 4, so tried to download Moose 6.0(beta) -- but
got a problem - big pause, no progress bars, the later ZipArchive
reporting "Error: can't find EOCD position"

Second try...
The web site advises for Moose 6.0 to download the Moose code in a
Pharo 5.0 image per...
      Gofer new
         smalltalkhubUser: 'Moose' project: 'Moose';
         configuration;
         loadDevelopment.

Doing that in build 50760 download with the Launcher produced...
Could not resolve: Phexample [Phexample-NikoSchwarz.57] in
/home/ben/.local/share/Pharo/images/Moose6-50760/package-cache
http://www.squeaksource.com/Moose ERROR: 'GoferRepositoryError: Could
not access http://www.squeaksource.com/phexample: ZnInvalidUTF8:
Illegal leading byte for utf-8 encoding'

Could someone check if they see the same, or maybe my Internet is flakey atm?
(preferably someone who doesn't normally use Moose to avoid package
cache differences)

cheers -ben

Reply | Threaded
Open this post in threaded view
|

Re: problem getting moose

Ben Coman
On Sun, Jun 5, 2016 at 1:34 PM, Ben Coman <[hidden email]> wrote:

> I wanted to try out Peter's XMI Analyser with Roassal and went to
> download Moose but had a couple of problems.
>
> First try...
> In the Launcher under Common Tools, I downloaded and Moose 5.1(stable)
> fine, but it is Pharo 4, so tried to download Moose 6.0(beta) -- but
> got a problem - big pause, no progress bars, the later ZipArchive
> reporting "Error: can't find EOCD position"
>
> Second try...
> The web site advises for Moose 6.0 to download the Moose code in a
> Pharo 5.0 image per...
>       Gofer new
>          smalltalkhubUser: 'Moose' project: 'Moose';
>          configuration;
>          loadDevelopment.
>
> Doing that in build 50760 download with the Launcher produced...
> Could not resolve: Phexample [Phexample-NikoSchwarz.57] in
> /home/ben/.local/share/Pharo/images/Moose6-50760/package-cache
> http://www.squeaksource.com/Moose ERROR: 'GoferRepositoryError: Could
> not access http://www.squeaksource.com/phexample: ZnInvalidUTF8:
> Illegal leading byte for utf-8 encoding'
>
> Could someone check if they see the same, or maybe my Internet is flakey atm?
> (preferably someone who doesn't normally use Moose to avoid package
> cache differences)

More info..

The repository defined in Monticello is
    MCSqueaksourceRepository
    location: 'http://www.squeaksource.com/phexample'
    user: ''
    password: ''
which I could not open, again getting...
  MCRepositoryError: Could not access
http://www.squeaksource.com/phexample: ZnInvalidUTF8: Illegal leading
byte for utf-8 encoding

I tried changing to...
   MCHttpRepository
       location: 'http://www.squeaksource.com/phexample'
       user: ''
       password: ''
with no luck.

But from Monticello I can define and successfully open another repository...
MCHttpRepository
    location: 'http://www.squeaksource.com/DavidLightsOut'
    user: ''
    password: ''

The top of stack is...
"a MetacelloFetchingMCSpecLoader(atomic load : 4.4-beta.1 [ConfigurationOfMoose]
load : Filesystem-tg.85
load : Nile-Base-DamienCassou.81)"

btw,
Phexample-NikoSchwarz.57 (2010-10-26) seems quite old,
with the latest on Squeaksource being Phexample-NikoSchwarz.63.mcz2011-08-29;
latest on Smalltalkhub/PharoExtras/Phexample being
Phexample-Core-CamilloBruni.67 (05/03/2013);
latest on Smalltalk/Phexample/Phexample being
Phexample-DenisKudryashov.75 (08/04/2016)

cheers -ben

Reply | Threaded
Open this post in threaded view
|

Re: problem getting moose

Tudor Girba-2
In reply to this post by Ben Coman
Hi,

> On Jun 5, 2016, at 7:34 AM, Ben Coman <[hidden email]> wrote:
>
> I wanted to try out Peter's XMI Analyser with Roassal and went to
> download Moose but had a couple of problems.
>
> First try...
> In the Launcher under Common Tools, I downloaded and Moose 5.1(stable)
> fine, but it is Pharo 4, so tried to download Moose 6.0(beta) -- but
> got a problem - big pause, no progress bars, the later ZipArchive
> reporting "Error: can't find EOCD position”

You can download the image as well:
https://ci.inria.fr/moose/job/moose-6.0/lastSuccessfulBuild/artifact/moose-6.0.zip


> Second try...
> The web site advises for Moose 6.0 to download the Moose code in a
> Pharo 5.0 image per...
>      Gofer new
>         smalltalkhubUser: 'Moose' project: 'Moose';
>         configuration;
>         loadDevelopment.

Indeed, this is what the CI job does.

> Doing that in build 50760 download with the Launcher produced...
> Could not resolve: Phexample [Phexample-NikoSchwarz.57] in
> /home/ben/.local/share/Pharo/images/Moose6-50760/package-cache
> http://www.squeaksource.com/Moose ERROR: 'GoferRepositoryError: Could
> not access http://www.squeaksource.com/phexample: ZnInvalidUTF8:
> Illegal leading byte for utf-8 encoding’

Strange. If you download the Moose image, you get the SmalltalkHub repo:
MCSmalltalkhubRepository
        owner: 'Phexample'
        project: 'Phexample'
        user: ''
        password: ''

> Could someone check if they see the same, or maybe my Internet is flakey atm?
> (preferably someone who doesn't normally use Moose to avoid package
> cache differences)

I am trying right now.

Doru

> cheers -ben
>

--
www.tudorgirba.com
www.feenk.com

"Beauty is where we see it."





Reply | Threaded
Open this post in threaded view
|

Re: problem getting moose

Tudor Girba-2
Hi,

I figured out the problem. When you run that script, you actually load "4.4-beta.1 [ConfigurationOfMoose]”

This is because of the mismatch between what loadDevelopment means in Gofer and the meaning of the symbolic version in Metacello.

Instead, please use this:

Metacello new
                smalltalkhubUser: 'Moose' project: 'Moose';
                configuration: 'Moose';
                version: #development;
                load.

I also updated the Moose webpage.

Cheers,
Doru


> On Jun 5, 2016, at 8:22 AM, Tudor Girba <[hidden email]> wrote:
>
> Hi,
>
>> On Jun 5, 2016, at 7:34 AM, Ben Coman <[hidden email]> wrote:
>>
>> I wanted to try out Peter's XMI Analyser with Roassal and went to
>> download Moose but had a couple of problems.
>>
>> First try...
>> In the Launcher under Common Tools, I downloaded and Moose 5.1(stable)
>> fine, but it is Pharo 4, so tried to download Moose 6.0(beta) -- but
>> got a problem - big pause, no progress bars, the later ZipArchive
>> reporting "Error: can't find EOCD position”
>
> You can download the image as well:
> https://ci.inria.fr/moose/job/moose-6.0/lastSuccessfulBuild/artifact/moose-6.0.zip
>
>
>> Second try...
>> The web site advises for Moose 6.0 to download the Moose code in a
>> Pharo 5.0 image per...
>>     Gofer new
>>        smalltalkhubUser: 'Moose' project: 'Moose';
>>        configuration;
>>        loadDevelopment.
>
> Indeed, this is what the CI job does.
>
>> Doing that in build 50760 download with the Launcher produced...
>> Could not resolve: Phexample [Phexample-NikoSchwarz.57] in
>> /home/ben/.local/share/Pharo/images/Moose6-50760/package-cache
>> http://www.squeaksource.com/Moose ERROR: 'GoferRepositoryError: Could
>> not access http://www.squeaksource.com/phexample: ZnInvalidUTF8:
>> Illegal leading byte for utf-8 encoding’
>
> Strange. If you download the Moose image, you get the SmalltalkHub repo:
> MCSmalltalkhubRepository
> owner: 'Phexample'
> project: 'Phexample'
> user: ''
> password: ''
>
>> Could someone check if they see the same, or maybe my Internet is flakey atm?
>> (preferably someone who doesn't normally use Moose to avoid package
>> cache differences)
>
> I am trying right now.
>
> Doru
>
>> cheers -ben
>>
>
> --
> www.tudorgirba.com
> www.feenk.com
>
> "Beauty is where we see it."
>
>
>
>

--
www.tudorgirba.com
www.feenk.com

"Speaking louder won't make the point worthier."


Reply | Threaded
Open this post in threaded view
|

Re: problem getting moose

Ben Coman
>> On Jun 5, 2016, at 8:22 AM, Tudor Girba <[hidden email]> wrote:
>>
>> Hi,
>>
>>> On Jun 5, 2016, at 7:34 AM, Ben Coman <[hidden email]> wrote:
>>>
>>> I wanted to try out Peter's XMI Analyser with Roassal and went to
>>> download Moose but had a couple of problems.
>>>
>>> First try...
>>> In the Launcher under Common Tools, I downloaded and Moose 5.1(stable)
>>> fine, but it is Pharo 4, so tried to download Moose 6.0(beta) -- but
>>> got a problem - big pause, no progress bars, the later ZipArchive
>>> reporting "Error: can't find EOCD position”
>>
>> You can download the image as well:
>> https://ci.inria.fr/moose/job/moose-6.0/lastSuccessfulBuild/artifact/moose-6.0.zip
>>
>>
>>> Second try...
>>> The web site advises for Moose 6.0 to download the Moose code in a
>>> Pharo 5.0 image per...
>>>     Gofer new
>>>        smalltalkhubUser: 'Moose' project: 'Moose';
>>>        configuration;
>>>        loadDevelopment.
>>
>> Indeed, this is what the CI job does.
>>
>>> Doing that in build 50760 download with the Launcher produced...
>>> Could not resolve: Phexample [Phexample-NikoSchwarz.57] in
>>> /home/ben/.local/share/Pharo/images/Moose6-50760/package-cache
>>> http://www.squeaksource.com/Moose ERROR: 'GoferRepositoryError: Could
>>> not access http://www.squeaksource.com/phexample: ZnInvalidUTF8:
>>> Illegal leading byte for utf-8 encoding’
>>
>> Strange. If you download the Moose image, you get the SmalltalkHub repo:
>> MCSmalltalkhubRepository
>>       owner: 'Phexample'
>>       project: 'Phexample'
>>       user: ''
>>       password: ''
>>
>>> Could someone check if they see the same, or maybe my Internet is flakey atm?
>>> (preferably someone who doesn't normally use Moose to avoid package
>>> cache differences)
>>
>> I am trying right now.
>>
>> Doru



On Sun, Jun 5, 2016 at 2:47 PM, Tudor Girba <[hidden email]> wrote:

> Hi,
>
> I figured out the problem. When you run that script, you actually load "4.4-beta.1 [ConfigurationOfMoose]”
>
> This is because of the mismatch between what loadDevelopment means in Gofer and the meaning of the symbolic version in Metacello.
>
> Instead, please use this:
>
> Metacello new
>                 smalltalkhubUser: 'Moose' project: 'Moose';
>                 configuration: 'Moose';
>                 version: #development;
>                 load.
>
> I also updated the Moose webpage.
>
> Cheers,
> Doru

Thanks Doru.  That appears to have worked.  Although an error popped up...
    SubclassResponsibility: AnObsoleteRubShoutStylerDecorator class
had the subclass responsibility to implement #key

Maybe because I had a Playground, Monticello & Pharo 5.0 Welcome
windows open when I ran it.

I tried again in a fresh image, running it from the old Workspace and
that error did not occur, but when I choose World > Playground I
get...
    MessageNotUnderstood: receiver of "beForSmalltalkScripting" is nil

UndefinedObject(Object)>>doesNotUnderstand: #beForSmalltalkScripting
RubSmalltalkScriptingMode>>updateTextAreaWhenPlugged
RubSmalltalkScriptingMode(RubEditingMode)>>plugin:
RubEditingArea(RubAbstractTextArea)>>editingMode:
RubEditingArea>>beForSmalltalkScripting
RubScrolledTextMorph>>beForSmalltalkScripting
GLMMorphicPharoScriptRenderer>>morph
GLMMorphicPharoScriptRenderer(GLMMorphicRubricTextRenderer)>>render:
GLMMorphicPharoScriptRenderer class(GLMMorphicWidgetRenderer
class)>>render:from:
GLMMorphicRenderer>>renderPharoScriptPresentation:
GLMPharoScriptPresentation>>renderGlamorouslyOn:
GLMMorphicRenderer(GLMRenderer)>>render:
GLMMorphicTabbedRenderer(GLMMorphicWidgetRenderer)>>renderObject:
[ self renderObject: each ] in [ :each |
tabs
addLazyPage: [ self renderObject: each ]
label: (self titleOrIconOf: each in: tabs)
toolbar: (self renderToolbarForPresentation: each inMorph: tabs)
action: (self labelActionBrickFor: each) ] in GLMMorphicTabbedRenderer>>render:
LazyTabPage>>actualPageMorph
LazyTabGroupMorph>>pageAt:
LazyTabGroupMorph>>updatePageIndex:
LazyTabGroupMorph(TabGroupMorph)>>update:
LazyTabGroupMorph(Object)>>update:with:
MorphChangedWithArguments>>deliverTo:
LazyTabGroupMorph(Morph)>>handleUpdate:
MessageSend>>value:
MessageSend>>cull:
MessageSend>>cull:cull:
[ action cull: anAnnouncement cull: announcer ] in
AnnouncementSubscription>>deliver:
BlockClosure>>on:do:
BlockClosure>>on:fork:
AnnouncementSubscription>>deliver:
[ subscription deliver: anAnnouncement ] in
SubscriptionRegistry>>deliver:to:startingAt:
BlockClosure>>ifCurtailed:
SubscriptionRegistry>>deliver:to:startingAt:
SubscriptionRegistry>>deliver:to:
SubscriptionRegistry>>deliver:
Announcer>>announce:
GLMTabSelectorBrick(Morph)>>doAnnounce:
GLMTabSelectorBrick(Morph)>>changed:with:
GLMTabSelectorBrick>>selectedIndex:
LazyTabGroupMorph(TabGroupMorph)>>selectedPageIndex:
[ tabs selectedPageIndex: index ] in GLMMorphicTabbedRenderer>>render:
BlockClosure>>ensure:
GLMAnnouncer>>suspendAllWhile:
GLMMorphicTabbedRenderer>>render:
GLMMorphicTabbedRenderer class(GLMMorphicWidgetRenderer class)>>render:from:
GLMMorphicRenderer>>renderTabbedCompositePresentation:
GLMTabbedArrangement>>renderGlamorouslyOn:
GLMCompositePresentation>>renderGlamorouslyOn:
GLMMorphicRenderer(GLMRenderer)>>render:
GLMMorphicPaneRenderer(GLMMorphicWidgetRenderer)>>renderObject:
GLMMorphicPaneRenderer>>renderContainerFor:
GLMMorphicPaneRenderer>>render:
GLMMorphicPaneRenderer class(GLMMorphicWidgetRenderer class)>>render:from:
GLMMorphicRenderer>>renderPane:
GLMPane>>renderGlamorouslyOn:
GLMMorphicRenderer(GLMRenderer)>>render:
GLMMorphicPagerRenderer(GLMMorphicWidgetRenderer)>>renderObject:
[ :each | container brickRoot pushPane: (self renderObject: each) ] in
GLMMorphicPagerRenderer>>render:
OrderedCollection>>do:
GLMMorphicPagerRenderer>>render:
GLMMorphicPagerRenderer class(GLMMorphicWidgetRenderer class)>>render:from:
GLMMorphicRenderer>>renderPager:
GLMPager>>renderGlamorouslyOn:
GLMMorphicRenderer(GLMRenderer)>>render:
GLMMorphicTabbedRenderer(GLMMorphicWidgetRenderer)>>renderObject:
GLMMorphicTabbedRenderer(GLMMorphicWidgetRenderer)>>renderWithTitleOrNil:
GLMMorphicTabbedRenderer>>render:
GLMMorphicTabbedRenderer class(GLMMorphicWidgetRenderer class)>>render:from:
GLMMorphicRenderer>>renderTabbedCompositePresentation:
GLMTabbedArrangement>>renderGlamorouslyOn:
GTInspector(GLMCompositePresentation)>>renderGlamorouslyOn:
GLMMorphicRenderer(GLMRenderer)>>render:
GLMMorphicTabbedRenderer(GLMMorphicWidgetRenderer)>>renderObject:
GLMMorphicTabbedRenderer(GLMMorphicWidgetRenderer)>>renderWithTitleOrNil:
GLMMorphicTabbedRenderer>>render:
GLMMorphicTabbedRenderer class(GLMMorphicWidgetRenderer class)>>render:from:
GLMMorphicRenderer>>renderTabbedCompositePresentation:
GLMTabbedArrangement>>renderGlamorouslyOn:
GTPlayground(GLMCompositePresentation)>>renderGlamorouslyOn:
GLMMorphicRenderer(GLMRenderer)>>render:
GLMMorphicWindowRenderer(GLMMorphicWidgetRenderer)>>renderObject:
GLMMorphicWindowRenderer>>render:
GLMMorphicWindowRenderer class(GLMMorphicWidgetRenderer class)>>render:from:
GLMMorphicRenderer>>open:
GTPlayground(GLMCompositePresentation)>>openWith:
GTPlayground(GLMCompositePresentation)>>openOn:with:
GTPlayground(GLMCompositePresentation)>>openOn:
GTPlayground>>openOn:
GTPlayground class(GLMCompositePresentation class)>>openOn:
GTPlayground class>>open
PharoCommonTools(ToolRegistry)>>openWorkspace

A hack workaround was to commenting-out as follows...
   RubSmalltalkScriptingMode>>updateTextAreaWhenPlugged
        super updateTextAreaWhenPlugged.
        "self textArea shoutStyler beForSmalltalkScripting"

Loading this fixes it...
    Name: Rubric-PavelKrivanek.370
    Author: PavelKrivanek
    Time: 30 May 2016, 10:00:45.805722 am
    UUID: 8c58b690-fd8f-44e7-abba-468218ec4658
    Ancestors: Rubric-TheIntegrator.369, Rubric-AlexandreBergel.369
    - issue 18349: add method comment

Loading this breaks it again...
    Name: Rubric-PavelKrivanek.371
    uthor: PavelKrivanek
    Time: 31 May 2016, 1:38:35.400467 pm
    UUID: 9d7bfec6-9b4d-494b-a84b-079125e9fce4
    Ancestors: Rubric-PavelKrivanek.370
    move styling (Shout) support to standalone package

cheers -ben

Reply | Threaded
Open this post in threaded view
|

Re: problem getting moose

Ben Coman
Final thing...
after loading, the following packages are dirty...
  AST-Core
        - removal of NumberParser>>#isNumber:
  Collections-Abstract
        - but when checked ==> no changes
  Famix-Core
        - but when checked ==> no changes
 Rubric-Rules
        - but when checked ==> no changes

cheers -ben

Reply | Threaded
Open this post in threaded view
|

Re: problem getting moose

stepharo
In reply to this post by Ben Coman
Hi ben

I got some similar behavior when the network is not good.

We should improve the loading of packages but this is simple than
actually having a bullet proof solution.

It is a couple of years that I think about it: loading in a separate
environment and on crash do not install

Stef


Le 5/6/16 à 08:18, Ben Coman a écrit :

> On Sun, Jun 5, 2016 at 1:34 PM, Ben Coman <[hidden email]> wrote:
>> I wanted to try out Peter's XMI Analyser with Roassal and went to
>> download Moose but had a couple of problems.
>>
>> First try...
>> In the Launcher under Common Tools, I downloaded and Moose 5.1(stable)
>> fine, but it is Pharo 4, so tried to download Moose 6.0(beta) -- but
>> got a problem - big pause, no progress bars, the later ZipArchive
>> reporting "Error: can't find EOCD position"
>>
>> Second try...
>> The web site advises for Moose 6.0 to download the Moose code in a
>> Pharo 5.0 image per...
>>        Gofer new
>>           smalltalkhubUser: 'Moose' project: 'Moose';
>>           configuration;
>>           loadDevelopment.
>>
>> Doing that in build 50760 download with the Launcher produced...
>> Could not resolve: Phexample [Phexample-NikoSchwarz.57] in
>> /home/ben/.local/share/Pharo/images/Moose6-50760/package-cache
>> http://www.squeaksource.com/Moose ERROR: 'GoferRepositoryError: Could
>> not access http://www.squeaksource.com/phexample: ZnInvalidUTF8:
>> Illegal leading byte for utf-8 encoding'
>>
>> Could someone check if they see the same, or maybe my Internet is flakey atm?
>> (preferably someone who doesn't normally use Moose to avoid package
>> cache differences)
> More info..
>
> The repository defined in Monticello is
>      MCSqueaksourceRepository
>      location: 'http://www.squeaksource.com/phexample'
>      user: ''
>      password: ''
> which I could not open, again getting...
>    MCRepositoryError: Could not access
> http://www.squeaksource.com/phexample: ZnInvalidUTF8: Illegal leading
> byte for utf-8 encoding
>
> I tried changing to...
>     MCHttpRepository
>         location: 'http://www.squeaksource.com/phexample'
>         user: ''
>         password: ''
> with no luck.
>
> But from Monticello I can define and successfully open another repository...
> MCHttpRepository
>      location: 'http://www.squeaksource.com/DavidLightsOut'
>      user: ''
>      password: ''
>
> The top of stack is...
> "a MetacelloFetchingMCSpecLoader(atomic load : 4.4-beta.1 [ConfigurationOfMoose]
> load : Filesystem-tg.85
> load : Nile-Base-DamienCassou.81)"
>
> btw,
> Phexample-NikoSchwarz.57 (2010-10-26) seems quite old,
> with the latest on Squeaksource being Phexample-NikoSchwarz.63.mcz2011-08-29;
> latest on Smalltalkhub/PharoExtras/Phexample being
> Phexample-Core-CamilloBruni.67 (05/03/2013);
> latest on Smalltalk/Phexample/Phexample being
> Phexample-DenisKudryashov.75 (08/04/2016)
>
> cheers -ben
>
>


Reply | Threaded
Open this post in threaded view
|

Re: problem getting moose

Peter Uhnak
In reply to this post by Ben Coman
On Sun, Jun 05, 2016 at 04:13:16PM +0800, Ben Coman wrote:

> Final thing...
> after loading, the following packages are dirty...
>   AST-Core
>         - removal of NumberParser>>#isNumber:
>   Collections-Abstract
>         - but when checked ==> no changes
>   Famix-Core
>         - but when checked ==> no changes
>  Rubric-Rules
>         - but when checked ==> no changes
>
> cheers -ben
>

The CI actually does more than just loading Moose: https://ci.inria.fr/moose/job/moose-6.0/1759/console

But the best way to download is imho through Pharo Launcher (which downloads it from the CI)

~~~~~~~ CI SCRIPT ~~~~~~~
wget --quiet -O - http://get.pharo.org/50+vm | bash
./pharo Pharo.image save moose-6.0

REPO=http://www.smalltalkhub.com/mc/Moose/Moose/main

./pharo moose-6.0.image eval Gofer new smalltalkhubUser: 'Pharo' project: 'Rubric'; package: 'ConfigurationOfRubric'; load. Gofer new smalltalkhubUser: 'Moose' project: 'Glamour'; package: 'ConfigurationOfGlamourCore'; load. Gofer new smalltalkhubUser: 'Moose' project: 'GToolkit'; package: 'ConfigurationOfGTInspector'; package: 'ConfigurationOfGTInspectorCore'; package: 'ConfigurationOfGTSpotter'; package: 'ConfigurationOfGTPlayground'; package: 'ConfigurationOfGTPlaygroundCore'; package: 'ConfigurationOfGToolkit'; package: 'ConfigurationOfGToolkitCore'; package: 'ConfigurationOfGTEventRecorder'; load. Gofer new smalltalkhubUser: 'Moose' project: 'Moose'; package: 'ConfigurationOfMoose'; load. Smalltalk snapshot: true andQuit: true.

./pharo moose-6.0.image config http://www.smalltalkhub.com/mc/Moose/Moose/main ConfigurationOfGlamourCore --install=development
./pharo moose-6.0.image config http://www.smalltalkhub.com/mc/Moose/Moose/main ConfigurationOfMoose --install=development

./pharo moose-6.0.image eval Gofer new smalltalkhubUser: 'Moose' project: 'GToolkit'; package: 'GT-InspectorExtensions-CoreRoassal'; unload; cleanup; load. Gofer new smalltalkhubUser: 'Moose' project: 'GToolkit'; package: 'GT-SpotterExtensions-CoreRoassal'; unload; cleanup; load. Smalltalk snapshot: true andQuit: true.

./pharo moose-6.0.image mooseimagesetup --signature=https://ci.inria.fr/moose/job/moose-6.0/1759/
~~~~~~ /CI SCRIPT ~~~~~~~

Peter

Reply | Threaded
Open this post in threaded view
|

Re: problem getting moose

Dale Henrichs-3
In reply to this post by stepharo
Stef,

One of advantages of using local git repositories is that once you've
downloaded the git repo you can load code without hitting the network at
all ... another related advantage of local git repositories is that once
you have chosen a particular checkout (SHA) to use every single load
will be identical as the repositories don't change unless you choose to
change them --- you are completely insulated from the decisions that
project maintainers may make until you explicitly choose to change your
checkout ...

Dale

On 6/5/16 1:15 AM, stepharo wrote:

> Hi ben
>
> I got some similar behavior when the network is not good.
>
> We should improve the loading of packages but this is simple than
> actually having a bullet proof solution.
>
> It is a couple of years that I think about it: loading in a separate
> environment and on crash do not install
>
> Stef
>
>
> Le 5/6/16 à 08:18, Ben Coman a écrit :
>> On Sun, Jun 5, 2016 at 1:34 PM, Ben Coman <[hidden email]> wrote:
>>> I wanted to try out Peter's XMI Analyser with Roassal and went to
>>> download Moose but had a couple of problems.
>>>
>>> First try...
>>> In the Launcher under Common Tools, I downloaded and Moose 5.1(stable)
>>> fine, but it is Pharo 4, so tried to download Moose 6.0(beta) -- but
>>> got a problem - big pause, no progress bars, the later ZipArchive
>>> reporting "Error: can't find EOCD position"
>>>
>>> Second try...
>>> The web site advises for Moose 6.0 to download the Moose code in a
>>> Pharo 5.0 image per...
>>>        Gofer new
>>>           smalltalkhubUser: 'Moose' project: 'Moose';
>>>           configuration;
>>>           loadDevelopment.
>>>
>>> Doing that in build 50760 download with the Launcher produced...
>>> Could not resolve: Phexample [Phexample-NikoSchwarz.57] in
>>> /home/ben/.local/share/Pharo/images/Moose6-50760/package-cache
>>> http://www.squeaksource.com/Moose ERROR: 'GoferRepositoryError: Could
>>> not access http://www.squeaksource.com/phexample: ZnInvalidUTF8:
>>> Illegal leading byte for utf-8 encoding'
>>>
>>> Could someone check if they see the same, or maybe my Internet is
>>> flakey atm?
>>> (preferably someone who doesn't normally use Moose to avoid package
>>> cache differences)
>> More info..
>>
>> The repository defined in Monticello is
>>      MCSqueaksourceRepository
>>      location: 'http://www.squeaksource.com/phexample'
>>      user: ''
>>      password: ''
>> which I could not open, again getting...
>>    MCRepositoryError: Could not access
>> http://www.squeaksource.com/phexample: ZnInvalidUTF8: Illegal leading
>> byte for utf-8 encoding
>>
>> I tried changing to...
>>     MCHttpRepository
>>         location: 'http://www.squeaksource.com/phexample'
>>         user: ''
>>         password: ''
>> with no luck.
>>
>> But from Monticello I can define and successfully open another
>> repository...
>> MCHttpRepository
>>      location: 'http://www.squeaksource.com/DavidLightsOut'
>>      user: ''
>>      password: ''
>>
>> The top of stack is...
>> "a MetacelloFetchingMCSpecLoader(atomic load : 4.4-beta.1
>> [ConfigurationOfMoose]
>> load : Filesystem-tg.85
>> load : Nile-Base-DamienCassou.81)"
>>
>> btw,
>> Phexample-NikoSchwarz.57 (2010-10-26) seems quite old,
>> with the latest on Squeaksource being
>> Phexample-NikoSchwarz.63.mcz2011-08-29;
>> latest on Smalltalkhub/PharoExtras/Phexample being
>> Phexample-Core-CamilloBruni.67 (05/03/2013);
>> latest on Smalltalk/Phexample/Phexample being
>> Phexample-DenisKudryashov.75 (08/04/2016)
>>
>> cheers -ben
>>
>>
>
>