[squeak-dev] MCMUpdater and CI

Tobias Pape Das.Linux at gmx.de
Sun May 31 09:47:12 UTC 2015


On 31.05.2015, at 01:32, David T. Lewis <lewis at mail.msen.com> wrote:

> On Sat, May 30, 2015 at 06:52:30PM -0400, David T. Lewis wrote:
>> On Fri, May 29, 2015 at 09:25:58PM +0200, Tobias Pape wrote:
>>> Hey
>>> 
>>> We have changed the way the MCMUpdater works, I recall.
>>> Probably this has broken the CI Build:
>>>  http://build.squeak.org/job/SqueakTrunk/1493/console
>>> 
>>> Who can take a look at it?
>>> 
>> 
>> It's partly fixed, but not quite.
>> 
>> The SqueakTrunk CI uses MCMcmUpdater class>>updateFromDefaultRepository,
>> so I restored an implementation (delegating to MCMcmUpdater current) in
>> MonticelloConfigurations-dtl.135.
>> 
>> With that in place, the update from Squeak4.5 to current trunk fails because the
>> old image is evaluating a block that expects MCMcmUpdater class>>useLatestPackagesFrom:
>> so I added that back to the class side of MCMcmUpdater in 46Deprecated-dtl.4.
>> 
>> I think I still need to fix the update maps to load the missing method, and
>> then it will probably work.
>> 
>> I will edit update-eem.315.mcm and have it load 46Deprecated-dtl.4 instead of
>> 46Deprecated-mt.3. If this works, update.spur-eem.mcm will need the same change.
> 
> I edited and saved both update-eem.315.mcm and update.spur-eem.mcm so that they
> both require 46Deprecated-dtl.4. This seems like a bad thing do do, since I am
> modifying an mcm with someone else's author initials, but it did seem to work,
> and the SqueakTrunk CI job is no longer failing.

Yay!
Thank you :)

Best regards
	-Tobias


More information about the Squeak-dev mailing list