<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, May 8, 2015 at 2:26 PM, Tobias Pape <span dir="ltr"><<a href="mailto:Das.Linux@gmx.de" target="_blank">Das.Linux@gmx.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><br>
On 08.05.2015, at 23:17, Levente Uzonyi <<a href="mailto:leves@elte.hu">leves@elte.hu</a>> wrote:<br>
<br>
> Hi Eliot,<br>
><br>
> If you can generate the files while they are in the repository (on the server), then you can save the time waiting for someone to delete them, because while you can't delete the files from the server, you can overwrite them.<br>
<br>
</span>To my knowledge, you can't.<br></blockquote><div><br></div><div>+1.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span class=""><br>
> This wouldn't help with the .mcds, but I think those are not cached in the image, so deleting just the .mcds is probably a way easier thing to do.<br>
><br>
<br>
<br>
</span>Best regards<br>
<span class="HOEnZb"><font color="#888888"> -Tobias<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
> Levente<br>
><br>
> On Fri, 8 May 2015, Eliot Miranda wrote:<br>
><br>
>> Hi David,<br>
>><br>
>> and to be very clear, the *only* packages to be deleted are those matching<br>
>><br>
>> Collections.spur*<br>
>> Compiler.spur*<br>
>> Kernel.spur*<br>
>> System.spur*<br>
>><br>
>> Eliot (phone)<br>
>><br>
>> On May 8, 2015, at 7:22 AM, Eliot Miranda <<a href="mailto:eliot.miranda@gmail.com">eliot.miranda@gmail.com</a>> wrote:<br>
>><br>
>>> Hi David,<br>
>>><br>
>>> 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.<br>
>>><br>
>>> Eliot (phone)<br>
>>><br>
>>> On May 7, 2015, at 7:19 PM, "David T. Lewis" <<a href="mailto:lewis@mail.msen.com">lewis@mail.msen.com</a>> wrote:<br>
>>><br>
>>>> On Thu, May 07, 2015 at 04:58:55PM -0700, Eliot Miranda wrote:<br>
>>>>> Hi All,<br>
>>>>><br>
>>>>> I need to delete all the patched Spur packages in trunk to ensure that<br>
>>>>> correctly patched versions replace them. Is there an automated way of<br>
>>>>> deleting packages on trunk? I've used the web interface, but it'll take<br>
>>>>> all day :-(<br>
>>>>> --<br>
>>>>> best,<br>
>>>>> Eliot<br>
>>>><br>
>>>> I don't know the answer to your question, but if I look at the files in<br>
>>>> the squeaksource repository, there are quite a few:<br>
>>>><br>
>>>> davidlewis@squeak-box4:/home/squeaksource/sso2/ss/trunk$ ls *spur*mcz | wc -l<br>
>>>> 246<br>
>>>> davidlewis@squeak-box4:/home/squeaksource/sso2/ss/trunk$ ls *spur*mcd | wc -l<br>
>>>> 152<br>
>>>> davidlewis@squeak-box4:/home/squeaksource/sso2/ss/trunk$ ls *spur*mcm | wc -l<br>
>>>> 33<br>
>>>> davidlewis@squeak-box4:/home/squeaksource/sso2/ss/trunk$ ls *spur* | wc -l<br>
>>>> 450<br>
>>>><br>
>>>> Is it really necessary to delete all of this stuff? Or could we keep it as is, and<br>
>>>> work around the problems in some other way?<br>
>>>><br>
>>>> Dave<br>
<br>
<br>
<br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature">best,<div>Eliot</div></div>
</div></div>