[V3dot10] Re: Problem with ReleaseBuilderFor3dot10

[Ken Causey]

On Fri, 2007-06-15 at 07:30 -0300, Edgar J. De Cleene wrote:
> 
> 
> El 6/14/07 7:25 PM, "Ken Causey" <ken at kencausey.com> escribió:
> 
> > Yeah, as I mentioned in a later message in that thread this surmise
> > regarding the hyphens was a red herring (although there is a bug in at
> > least once method of ReleaseBuilderFor3dot10 that mistakenly assumes
> > that the first hyphen delimits the package name).
> > 
> > As it turns out the copy of Installer-Core-edc.86 in the 310 repository
> > refers to an Installer-Core-edc.85 with a UUID that does not match the
> > UUID of the copy of 85 in the 310 repository.  Which leaves two
> > questions: 1. What is the 'right' was to fix this?  2. How did it end up
> > broken?
> > 
> > Ken
> 
> I resume the choices as Ralph know and still don't decide
> 
> People , I repeat nothing go public without Ralph agree !

Sure and I will repeat my arguments for public consumption.

> 1) Putting my 7113 . It's in use for students without new problems.
> Using my own dir for build, always my machine reach any update .

Adding a new update cannot fix the core problem.  It is still going to
be the case that anyone that attempts to update through 7109 is going to
fail if neither 7109, .85, or .86 change.

> 2) Using the last patch by Mathieu Suen. My student say works.

I'm assuming you are referring to the patch at

http://lists.squeakfoundation.org/pipermail/v3dot10/2007-June/000597.html

I have the same complaint about this patch as I did about yours.  It is
merely a workaround and a very dangerous one at that.  It simply gives
the user an opportunity to ignore the fact that the UUID does not match.
At best this is going to confuse users.  At worst this may result in
users trashing images with damaged package files.

> 3) Using a alternative repository as 'sanbox', build there, test in another
> machine all works .
> When works transfer right files to 310 repository.

I certainly have no complaint with testing out solutions.  But there is
no statement of solution in this example.  You aren't saying how you
plan to actually fix the actual problem.

Ken
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.squeakfoundation.org/pipermail/v3dot10/attachments/20070615/9cd39216/attachment.pgp