[Glass] Cannot load Metacello nor Glass in Glass itself (spot bug)

Dale Henrichs dale.henrichs at gemtalksystems.com
Fri Jan 17 12:12:10 PST 2014

On Fri, Jan 17, 2014 at 5:57 AM, Mariano Martinez Peck <
marianopeck at gmail.com> wrote:

> Hi guys,
> Dale, I think I have the exact same problem as Johan. I am checking the
> .cs attached to the issue tracker and I see some differences to what I have
> loaded in my current glass.

"exact same problem"? I understood that your problem were related to user
permissions on files in the /tmp directory ... this is a flaw in the
current design ...there are no bugfixes for that

> First, in #extractRepositoryFrom: zipFile to: directory      I notice some
> difference and after checking, it seems I am
> using Metacello-Platform.gemstone-dkh.29 .. and that was committed
> in Metacello-Platform.gemstone-dkh.32.  but the comment in the issue
> tracker says the issue was integrated in  Metacello-Preview
> 1.0.0-beta.32.8. As far as I know, I am using last stable glass....
> Same for #downloadFile: url to: outputFileName

> #projectDirectoryFrom: projectPath version: versionStrin I see a
> completly different version I have in my glass and I don't see Johan
> changes committed. Moreover, there are new versions committed for that
> package that still change this method but I am not sure if it includes
> Johan changes. I think these may have been lost.
> #downloadErrorFileNameFor: zipFileName I don't even see it nor in my
> current version nor in the latest committed version...
> So...all in all, those 2 last methods may have been lost.
> Google bug #184[4] was indeed "fixed" in Metacello-Preview
1.0.0-beta.32.8, but the current #stable version of the Metacello-Preview
is 1.0.0-beta.32.12[6] and it includes an additional bugfix in this area
(Github bug #209[1]). The relevant package version is

#downloadErrorFileNameFor: is in the class MetacelloPlatform and was
introduced as part of the Google bug #184 bugfix[8].

So it appears that you aren't using the latest Metacello-Preview version....

But that is not the end of the story ... Metacello-Preview 1.0.0-beta.32.13
is in progress[7] and there are two open bugs in this area: Github Issue
#226[2] and Github issue #232[3] (your multi-linux user bug)...

So even if you are using the latest version, there are still open issues in
this area ...

So we have two particular issues to figure out ...

- how come you are using an older version of Metacello?
- how can we get you to the point where you can at least use the latest
code base?

Using Metacello-Platform.gemstone-dkh.29 as the key, you must have
Metacello 1.0-beta.32 loaded and Metacello 1.0-beta.32 implies that you
have GLASS 1.0-beta.9 or GLASS 1.0-beta.9.1 loaded ... GLASS 1.0-beta.9 is
the latest release, so now we understand where you are at -- I think:)

If you want to use the latest release version of Metacello, then you need
to update to GLASS 1.0-beta.9.1 and then load the #stable version of the
Metacello Preview:

ConfigurationOfGLASS project updateProject. GsDeployer deploy: [
(ConfigurationOfGLASS project version: '1.0-beta.9.1') load ].
  Metacello new
    baseline: 'Metacello';
    repository: 'github://dalehenrich/metacello-work:master/repository';
    load: 'ALL'.
    ] on: Warning
      do: [:ex |
        Transcript cr; show: ex description.
        ex resume].

Be forewarned that the load of Metacello baseline downloads from github and
you are exposed to the /tmp bugs until you get past the load, but then you
are still exposed to the two unfixed bugs ([2] and [3]).

If you would like to help fix the bugs, then I suggest that you fork the
Metacello repository on github and then clone it locally:

  cd /opt/git
  git clone git at github.com:<your name>/metacello-work.git

and modify the Metacello load script to the following:

  Metacello new
    baseline: 'Metacello';
    repository: 'filtree:///opt/git/metacello-work/repository';
    load: 'ALL'.
    ] on: Warning
      do: [:ex |
        Transcript cr; show: ex description.
        ex resume].

In the long run it is good idea to make local copies of all of the
repositories that you are using in production so you can decide when you
are ready to update to newer versions and insulate yourself from network
outages and the like ...


[4] https://code.google.com/p/metacello/issues/detail?id=184
[3] https://github.com/dalehenrich/metacello-work/issues/232
[2] https://github.com/dalehenrich/metacello-work/issues/226
[1] https://github.com/dalehenrich/metacello-work/issues/209

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gemtalksystems.com/mailman/private/glass/attachments/20140117/c5927927/attachment.html>

More information about the Glass mailing list