On Tue, Aug 30, 2011 at 11:26 PM, Dale Henrichs <dhenrich@vmware.com> wrote:

Mariano,

I think that addVersion: is very old gofer/metacello code ... not fancy new code. It sounds like an old version of Metacello is being loaded/bootstrapped. #addVersion: isn't sent from the current code base ... At a minimum, you should have these packages loaded:

�'Metacello-Base-DaleHenrichs.19'
�'Metacello-Core-DaleHenrichs.455'
�'Metacello-MC-DaleHenrichs.505'

Wow. This is weird. The versions that are being loaded are:
Metacello-Core-dkh.302
Metacello-MC-dkh.258
...

So...terribly old.� Of course, the problem was that out #ensureMetacello was very old. But how we didn't discovered before doing the release? of course, because we used Pharo images that already come with Metacello hahahha.

I have just commited the fix. I took the latest #ensureMetacello from here: http://code.google.com/p/metacello/wiki/EnsureMetacello
I hope this is correct.

Thanks Dale for the help and thanks Laszlo for the report!
�

if the bootstrapping process is working.

Keep in mind that pharo1.4.x has not yet been defined in Metacello (see Issue 4613[1]), so there will be other Metacello issues in 1.4 for the moment ... the proposed bugfix in 4613 would mean that a new version of Metacello would no longer be needed to define the platform specific attributes ...

Dale

[1] http://code.google.com/p/pharo/issues/detail?id=4613

----- Original Message -----
| From: "Mariano Martinez Peck" <marianopeck@gmail.com>
| To: dbxtalk@googlegroups.com, "Pharo Development" <pharo-project@lists.gforge.inria.fr>
| Sent: Tuesday, August 30, 2011 2:00:26 PM
| Subject: [Pharo-project] Gofer/Metacello problem in 1.4 [WAS] Re: DBXTalk � � and Pharo 1.4
|
|
|
|
| On Tue, Aug 30, 2011 at 9:14 PM, Laszlo Zsolt Kiss <
| lzskiss@gmail.com > wrote:
|
|
|
|
| hi.
| first i load the ConfigurationOfOpenDBX and the 1.4 version is
| missing from the spec.:
|
|
|
| stable: spec
| <symbolicVersion: #stable>
|
| spec for: #'pharo1.2.x' version: '1.0'.
| spec for: #'pharo1.3.x' version: '1.0'.
|
|
| then i added the next line to the spec:
|
|
| spec for: #'pharo1.4.x' version: '1.0'.
|
|
| then i probally do it this:
|
|
| (((Smalltalk globals at: #ConfigurationOfOpenDBXDriver) perform:
| #project) perform: #version: with: #stable) load.
|
|
| i gived back a warring:
|
|
|
| "The method Gofer addVersion: has been deprecated.
| Instead of #addVersion: simply use #version:
|
| Hi. Yes, I can reproduce this problem :(
|
|
|
|
|
|
|
|
| Select Proceed to continue, or close this window to cancel the
| operation."
|
|
| I proceed this warrning.
|
|
| Then gived back an error message, I think this error came from the
| Metacello.
|
| I attached the PharoDebug file.
|
|
|
|
| The error is in the method #updateProject where it does:
|
| (GoferPackageReference name: mgr packageName repository: mgr
| repositoryGroup) versionReference.
|
| GoferPackageReference dnu #name:repository: instead, it is
| implemented in GoferResolvedReference
|
|
| Dale any idea?
|
| Versions: Gofer-Core-StephaneDucasse.135.
| Metacello version is ...... ConfigurationOfMetacello project
| currentVersion raises dnu #setName
|
| So...I guess Pharo 1.4 is using a very new version of Gofer, which
| brings lot of changes that break Metacello ?
|
| Thanks!
|
|
|
|
|
|
|
|
| Byte
| Laszlo Zsolt
|
|
| Ps: the image is clean #14112 and the CogVM is the last..
|
|
| inez Peck < marianopeck@gmail.com >
|
|
|
|
|
|
|
|
|
| On Tue, Aug 30, 2011 at 9:53 AM, Laszlo Zsolt Kiss <
| lzskiss@gmail.com > wrote:
|
|
| Hi Developers!
|
|
| Can I use any way this combination: DBXTalk with Pharo 1.4?
|
| Hi. Yes, sure. Did you try it? You shouldn't have any problem.
| Please let us know if you do have.
|
|
| --
| Mariano
| http://marianopeck.wordpress.com
|
|
|
|
|
| --
| Mariano
| http://marianopeck.wordpress.com
|
|