[squeak-dev] Updating Trunk gives: "SM is already defined..."

Hi Bert,

El 15/08/2009, a las 14:21, Bert Freudenberg escribió:


I updated to monticello 1.5, because, Trying to install a MC package I  
have, gives me an error without any "message". I suppose, this message  
was about dependencies, because once I installed Aida, I installed my  
package without troubles.

I will try to reproduce without MC15, because, I'm seeing, how I can't  
save to my MC repository. Probably all this errors comes from the same  
thing.

Cheers.

Giuseppe Luigi Punzi Ruiz
Blog: http://www.lordzealon.com
Twitter & Skype & GoogleTalk accounts: glpunzi

On Sat, 2009-08-15 at 10:05 +0200, Giuseppe Luigi Punzi Ruiz wrote:
> About the log, AFAIR, Squeak, saves in SqueakDebug.log various errors,
> don't only the last one, true? In this log, only appears the last MNU,
> not the previous error.

No, in fact the file is overwritten with only the most recent error.

Ken

You are not on a clean trunk image. Apparently, some packages you have loaded interfere with the ones in the trunk.

E.g., there is no implementor nor sender of #manager in trunk, and no "MCPackageLoader1b".

Googling for that class reveals it's part of Monticello 1.5, so there is some incompatibility, not quite unexpectedly.

As I wrote before, it would be great if we could get the latest Monticello into trunk, but I failed when I tried (and I didn't want to spend too many hours on it).

- Bert -

On 15.08.2009, at 10:05, Giuseppe Luigi Punzi Ruiz wrote:

Hi, this morning, I decided to update (it's the second time I update it, first, was last night), after the mail of Andreas.

First, I get an error (1)

If I click on Poceed, updating cotinues, after a window asking me about merging changes.

I click on Rest Remote, and then on Merge (don't know if this is the way to do it), and updating continues, until at (log attached):

"MNU: PackageInfo>>manager"

About the log, AFAIR, Squeak, saves in SqueakDebug.log various errors, don't only the last one, true? In this log, only appears the last MNU, not the previous error.

(1) http://img30.imageshack.us/img30/3126/updatingerroru.png

(2)

<SqueakDebug.log>

Giuseppe Luigi Punzi Ruiz

Blog: http://www.lordzealon.com

Twitter & Skype & GoogleTalk accounts: glpunzi

El sáb, 15-08-2009 a las 13:44 -0700, Ken G. Brown escribió:

Simple, start with Keith's build image, already has MC 1.5 and latest Installer with LPF, unless I'm mistaken about something, would seem like the sensible place to start. 

Ken,  from my iPhone

On Aug 15, 2009, at 5:21 AM, Bert Freudenberg <[hidden email]> wrote:

Hi Ken,

And where is this image? I tought the "only one" trunk ready image was this:
http://squeakvm.org/win32/release/Squeak-3.10.2-trunk.zip

Readed here:
http://www.nabble.com/-squeak-dev--trunk-update-problem-td24871248.html

Cheers.

Giuseppe Luigi Punzi <[hidden email]> apparently said:
Please forgive the time taken to respond, I am
away from home at the moment with only sporadic
computer access.

The latest version of 3.10.2 intended by the
release team for building the 3.11 images is
located at
<ftp.squeak.org/3.11/Squeak3.10.2-build/090628-1523/090628-1523_Squeak3.10.2-build.zip>
This image contains the latest board approved
release path stuff for the various packaged
images planned by the release team, contents of
the build image are documented here:
<ftp.squeak.org/3.11/Squeak3.10.2-build/090628-1523/090628-1523_Squeak3.10.2-build.info>
MC 1.5 is already there for one.

It is my understanding that Andreas forked off a
previous, dated version of 3.10.2 where he and a
few others are hacking experimentally in a
repository questionably called 'trunk' with
apparently no plan to rejoin the previous board
approved release path started in
ftp.squeak.org/3.11/.

Seems to me 090628-1523_Squeak3.10.2-build.zip
would have been a far better point to start the
recent hacking in the 'trunk' since it had latest
versions of MC, Installer, Installer Packages,
etc., however as Bert has said, it is only an
experiment so the work will probably need to be
reincorporated at some point into the release
path using Installer Sake/Packages. It is unclear
who will do this additional work.

Ken G. Brown