[Seaside-dev] Seaside-Core-pmm.693 and Seaside-HTML5-pmm.19 define same method

[Dale Henrichs]

Julian,

I'm doing a build in PharoCore1.1.1, so I'll be able to validate your 
reversion... I hit one test error in PharoCore1.0, so I also want to see 
if the test has problems in PharoCore1.1.1 or not ...

As long as the current progress toward a resolution of Issue641 isn't 
worse than the original bug (which you can decide), I'll just pick up 
the state of the system tomorrow ..

I'll send mail to this list when I start the process (late morning/early 
afternoon PST) and mail when I've got a snapshot that passes the unit 
tests ...

Dale


On 02/09/2011 04:43 PM, Julian Fitzell wrote:
> On Wed, Feb 9, 2011 at 11:56 PM, Dale Henrichs<dhenrich at vmware.com>  wrote:
>> [snip]
>
> I'll leave the early questions for Philippe and Avi Sheffi to answer.
>
>> Looking at Issue 640, there were later versions of Seaside-Core committed
>> somewhere:
>>
>> Name: Seaside-Core-as.694
>> Author: as
>> Time: 6 February 2011, 9:08:58 pm
>> UUID: 5450d506-8db5-414b-996a-b434ec532cea
>> Ancestors: Seaside-Core-pmm.693
>>
>> Name: Seaside-Core-as.695
>> Author: as
>> Time: 6 February 2011, 9:39:13 pm
>> UUID: f017aa59-fdf2-604e-84c2-776bfdab18c2
>> Ancestors: Seaside-Core-as.694
>>
>> These files are no longer present in the Seaside30 repository (if they ever
>> were), so perhaps, Philippe's changes got lost along the way (committed
>> after Seaside-Core-as.695 possibly)...not a good idea to delete packages, in
>> case a mistake like this one is made...hard to tell what other work was lost
>> by the deletion... if indeed mcz files were deleted...
>
> They were moved to the obsolete repository:
> http://www.squeaksource.com/Seaside29old/
>
> I had only using that repository for packages that had been deleted,
> though, and I'd try to leave an empty "tip" version of the package in
> the main repo in that case.
>
> Since you at least have hit the problem, I'll commit a reversion.
>
>> Also it looks like there is active seaside30 development work going on on
>> today (Issue 641) is this something that I should wait to be finished or
>> should I try to exclude the additional work or what ... Normally I can get
>> my snapshot of mcz files done in an hour or two, but since the packaging is
>> messed up and possibly mcz files missing I'll have to wait until at least
>> tomorrow before I pick up the latest mcz files ...
>
> Yes, there are a number of people contributing fixes at the moment so
> you'll have to coordinate on the list. Re: 641 specifically, either
> wait for it to settle or ignore the recent commit.
>
> Julian
> _______________________________________________
> seaside-dev mailing list
> seaside-dev at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev