<div dir="ltr">Hi Tobias,<div><br></div><div><br></div><div> looking at the commit messages everything looks fine with the Collections.spur, Compiler.spur and System.spur packages, but I see no Kernel.spur upload messages. Did you perhaps not delete those files? If so, could you please delete just the Kernel.spur files and I'll upload just those.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, May 11, 2015 at 9:12 AM, Eliot Miranda <span dir="ltr"><<a href="mailto:eliot.miranda@gmail.com" target="_blank">eliot.miranda@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Thanks Tobias, I'm uploading the packages now.</div><div class="gmail_extra"><div><div class="h5"><br><div class="gmail_quote">On Mon, May 11, 2015 at 1:08 AM, <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">Hi all,<br>
<span><br>
On 09.05.2015, at 00:23, Tobias Pape <<a href="mailto:Das.Linux@gmx.de" target="_blank">Das.Linux@gmx.de</a>> wrote:<br>
<br>
> Hi all,<br>
><br>
><br>
<br>
<br>
</span>I just wiped the indicated packages from <a href="http://source.squeak.org" target="_blank">source.squeak.org</a>.<br>
Please report any problems; there shouldn't be one, but no one knows.<br>
David, no action required from you.<br>
<br>
Best regards<br>
<span><font color="#888888"> -Tobias<br>
</font></span><br>
PS: I adapted the 'run' script of squeaksource to be able to be used with<br>
'svc -t squeaksource' to hard-cycle the image (using exec and setuidgid)<br>
<div><div><br>
> I just tried wiping the versions Eliot asked to be removed.<br>
> I am able to remove the corresponding files from the disk and also remove<br>
> the Squeaksource version entries.<br>
><br>
> However, it seems that <a href="http://source.squeak.org" target="_blank">source.squeak.org</a> is running on some kind of<br>
> Magma-backend, where wiping the versions is virtually impossible for me.<br>
> I put together the following script:<br>
><br>
> "=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-"<br>
> | project projectDir rawVersions fs candidates condition mcModel |<br>
> project := SSRepository current projects detect: [:p | p id = 'trunk'].<br>
> mcModel := (SSRepository storage respondsTo: #mcModelFor: ) ifTrue: [<br>
> SSRepository storage mcModelFor: project].<br>
> projectDir := SSFilesystem new projectDirectoryFor: project.<br>
> " we really want to delete the versions, so circumvent the accessor that filters them "<br>
> rawVersions := project instVarNamed: 'versions'.<br>
> condition := [:version |<br>
> #('Collections.spur' 'Compiler.spur' 'Kernel.spur' 'System.spur')<br>
> anySatisfy: [:pat | version fileName beginsWith: pat]].<br>
> candidates := (rawVersions select: condition) values.<br>
> candidates<br>
> do: [:version| | fileName |<br>
> fileName := version fileName.<br>
> Transcript showln: '> ', fileName.<br>
> version diffs copy keysDo: [:diffName |<br>
> projectDir deleteFileNamed: diffName ifAbsent: ["ok"].<br>
> Transcript showln: ' Removed ', diffName.<br>
> version diffs removeKey: diffName.<br>
> Transcript showln: ' Wiped ', diffName].<br>
> projectDir deleteFileNamed: fileName ifAbsent: ["ok"].<br>
> Transcript showln: ' Removed ', fileName.<br>
> rawVersions removeKey: fileName.<br>
> " mcModel ifNotNil: [:m | m removeVersion: (project mcVersionFrom: version)]. " "<============== this does not work, chris"<br>
> Transcript showln: ' Wiped ', fileName]<br>
> displayingProgress: [:version | 'Wiping ', version fileName].<br>
> self assert: [rawVersions noneSatisfy: condition].<br>
> "=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-"<br>
><br>
> At the position Indicated I tried removing the faulty version from the magma-based<br>
> data structures, but #removeVersion: tries to remove from an (magma)array, which fail.<br>
><br>
> I can't help any further here, sorry. Please somebody step in?<br>
><br>
> Best regards<br>
> -Tobias<br>
><br>
> PS: I already backed up all affected files to ~squeaksoure/spur-backup<br>
><br>
><br>
> On 08.05.2015, at 23:42, Levente Uzonyi <<a href="mailto:leves@elte.hu" target="_blank">leves@elte.hu</a>> wrote:<br>
><br>
>> Hi Eliot,<br>
>><br>
>> On Fri, 8 May 2015, Eliot Miranda wrote:<br>
>><br>
>>> 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>
>>> 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>
>><br>
>> 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).<br>
>><br>
>> Levente<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>
>>> 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>
>>> best,Eliot<br>
><br>
><br>
<br>
</div></div></blockquote></div><br><br clear="all"><div><br></div></div></div><span class="HOEnZb"><font color="#888888">-- <br><div>best,<div>Eliot</div></div>
</font></span></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature">best,<div>Eliot</div></div>
</div>