<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, May 8, 2015 at 2:42 PM, Levente Uzonyi <span dir="ltr"><<a href="mailto:leves@elte.hu" target="_blank">leves@elte.hu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Eliot,<span class=""><br>
<br>
On Fri, 8 May 2015, Eliot Miranda wrote:<br>
<br>
</span><span class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Levente,<br>
On Fri, May 8, 2015 at 2:17 PM, Levente Uzonyi <<a href="mailto:leves@elte.hu" target="_blank">leves@elte.hu</a>> wrote:<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<br>
delete them, because while you can't delete the files from the server, you can overwrite them. This wouldn't help with the .mcds, but<br>
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>
I thought this too. But when I tried doing this yesterday, and earlier, the files were not replaced. I have a generated set waiting to upload as<br>
soon as the old ones have been deleted. <br>
</blockquote>
<br></span>
I just reuploaded Collections-ul.625.mcz, and the server happily accepted it. It even sent a mail about it.<br>
It's possible that it won't accept packages with different content, but it clearly accepts reuploads (which is a bug).</blockquote><div><br></div><div>Well, yesterday I uploaded a correct version of Collections.spur-tfel.624 and the server appeared to accept it, but when I downloaded the package from the server i got the old package. So I don't know. I think the safest thing is to nuke the old packages and upload freshly patched ones.</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="HOEnZb"><font color="#888888"><br>
<br>
Levente</font></span><div class="HOEnZb"><div class="h5"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
<br>
<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" target="_blank">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<br>
know is to delete the existing files and upload new ones. Can someone who has access to the box simply login<br>
with either ash or FTP and delete them with a single command? If I had access to the box that is what I would<br>
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" target="_blank">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>
<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>
<br>
<br>
<br>
<br>
<br>
<br>
--<br>
best,Eliot<br>
<br>
</blockquote>
</div></div><br><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature">best,<div>Eliot</div></div>
</div></div>