Thanks!  It's all merged.

BTW, I was shocked to learn of that DependencyBrowser!  Man oh man
that is great!


On Fri, Jan 7, 2011 at 4:04 PM, Bernhard Pieber <bernhard at pieber.com> wrote:
> I found the reason for this. I just saved Monticello-bp.416 with a fix to the inbox.
>
> When you do Smalltalk cleanUp: aggressive all the PackageInfos are flushed. The reason is that I implemented cleanUp: in MCPackageManager and not in its subclass MCWorkingCopy because flushObsoletePackageInfos, which I call in cleanUp:, was implemented there as well. However, if you do MCPackageManager flushObsoletePackageInfos instead of MCWorkingCopy flushObsoletePackageInfos it flushes all PackageInfos.
>
> Solution: Move flushObsoletePackageInfos and cleanUp: from MCPackageManager to MCWorkingCopy.
>
> To test:
> 1. Take the latest trunk image.
> 2. Load Monticello-bp.416 from the inbox.
> 3. Do Smalltalk cleanUp: true.
> 4. Do DependencyBrowser open. Note that all the packages are still there.
> 5. Run PackageDependencyTest. Only testMorphic and testSUnitGUI remain. (A fix for testSUnitGUI is in the inbox. ;-)
>
> Cheers,
> Bernhard
>
> Am 06.01.2011 um 20:56 schrieb Bernhard Pieber:
>
>> Am 06.01.2011 um 18:33 schrieb Chris Muller:
>>> Please also test your applications with this image over the next weeks
>>> to ensure they will be compatible with this new release, and also
>>> flush out any final problems.
>> I think there is something wrong with the PackageDependencyTest in the beta image. I did not understand why testSunitUI does not fail without my fixes and looked into it. All 35 tests pass but it runs very fast. In the trunk image it takes several seconds. When I do DependencyBrowser open it is completely empty.
>>
>> Cheers,
>> Bernhard
>
>
>