[DONE] Re: [Box-Admins] Wiping Eliot's versions Re: [squeak-dev] automated way to delete specific trunk packages?

[Levente Uzonyi]

No, I was wrong about the problem. It's still the Spur Bootstrap. 
Character >> #isAlphaNumeric in Collections.spur-ul.627 is:

isAlphaNumeric
 	"Answer whether the receiver is a letter or a digit."

 	self asInteger > 255 ifFalse: [ ^((ClassificationTable at: self asInteger + 1) bitAnd: AlphaNumericMask) > 0 ].
 	^self encodedCharSet isAlphaNumeric: self

But it should be

isAlphaNumeric
 	"Answer whether the receiver is a letter or a digit."

 	^self encodedCharSet isAlphaNumeric: self

As it is in Collections-ul.627.


Levente

On Tue, 12 May 2015, Levente Uzonyi wrote:

> I think that image is not in sync with the Trunk updates, because it still 
> has the old branch of .spur packages loaded. This makes the update process 
> behave in an unexpected way (it downloads all kind of strange .mcds, 
> including some with smaller version number).
>
> The point where it gets stuck should not happen, so it's a load order issue, 
> which is probably related to the image not being in sync with the repository.
> If you really want to proceed from that point, then evaluate [Character 
> initializeClassificationTable] in the emergency evaluator.
>
> Levente
>
> On Mon, 11 May 2015, David T. Lewis wrote:
>
>> On Mon, May 11, 2015 at 09:12:57AM -0700, Eliot Miranda wrote:
>>> 
>>> On Mon, May 11, 2015 at 1:08 AM, <Das.Linux at gmx.de> wrote:
>>> 
>>>> Hi all,
>>>> 
>>>> On 09.05.2015, at 00:23, Tobias Pape <Das.Linux at gmx.de> wrote:
>>>> 
>>>> I just wiped the indicated packages from source.squeak.org.
>>>> Please report any problems; there shouldn't be one, but no one knows.
>>>> David, no action required from you.
>>>> 
>>> Thanks Tobias, I'm uploading the packages now.
>>> 
>> 
>> I just tried doing a trunk.spur update starting with the image at
>> http://www.mirandabanda.org/files/Cog/SpurImages/trunk46-spur.image
>> 
>> The update stream seems to work fine, although I did eventually end up
>> in an emergency evaluator. I expect that this is a problem in the update
>> maps (not Spur image or VM). Attached is a screen shot of the evaluator
>> to show where the problem occurred.
>> 
>> Dave
>> 
>> 
>