Hi David,

     and to be very clear, the *only* packages to be deleted are those matching

Collections.spur*
Compiler.spur*
Kernel.spur*
System.spur*

Eliot (phone)

On May 8, 2015, at 7:22 AM, Eliot Miranda <eliot.miranda at gmail.com> wrote:

> Hi David,
> 
>     it is always possible to fix it another way but it would be hugely expensive.  The only affordable way I know is to delete the existing files and upload new ones.  Can someone who has access to the box simply login with either ash or FTP and delete them with a single command?  If I had access to the box that is what I would do.
> 
> Eliot (phone)
> 
> On May 7, 2015, at 7:19 PM, "David T. Lewis" <lewis at mail.msen.com> wrote:
> 
>> On Thu, May 07, 2015 at 04:58:55PM -0700, Eliot Miranda wrote:
>>> Hi All,
>>> 
>>>   I need to delete all the patched Spur packages in trunk to ensure that
>>> correctly patched versions replace them.  Is there an automated way of
>>> deleting packages on trunk?  I've used the web interface, but it'll take
>>> all day :-(
>>> -- 
>>> best,
>>> Eliot
>> 
>> I don't know the answer to your question, but if I look at the files in
>> the squeaksource repository, there are quite a few:
>> 
>>   davidlewis at squeak-box4:/home/squeaksource/sso2/ss/trunk$ ls *spur*mcz | wc -l
>>   246
>>   davidlewis at squeak-box4:/home/squeaksource/sso2/ss/trunk$ ls *spur*mcd | wc -l
>>   152
>>   davidlewis at squeak-box4:/home/squeaksource/sso2/ss/trunk$ ls *spur*mcm | wc -l
>>   33
>>   davidlewis at squeak-box4:/home/squeaksource/sso2/ss/trunk$ ls *spur* | wc -l
>>   450
>> 
>> Is it really necessary to delete all of this stuff? Or could we keep it as is, and
>> work around the problems in some other way?
>> 
>> Dave
>> 
>> 
>>