I've done that myself... repeatedly :-(

On Dec 16, 2017 1:53 AM, "Tobias Pape" <Das.Linux at gmx.de> wrote:

>
> > On 15.12.2017, at 23:18, Phil B <pbpublist at gmail.com> wrote:
> >
> > Thanks Tobias!  Probably no cookie for me but I'd guess the page
> generation choked on something in the readme or a file name? (i.e. didn't
> properly escape a character or sequence of chars)
> >
>
> Yea, the readme used  <...> somewhere and the brower thought it had to
> interpret that as xml…
>
> Best regards
>         -Tobias
>
> > On Dec 15, 2017 4:06 PM, "Tobias Pape" <Das.Linux at gmx.de> wrote:
> >
> > > On 15.12.2017, at 21:38, Phil B <pbpublist at gmail.com> wrote:
> > >
> > > I was doing some spelunking on historical images and ran into a couple
> issues...
> > >
> > > The page at files.squeak.org/2.8 has problems rendering (tag mismatch
> on cpu-vendor-os in both Firefox and Chromium) so I can't get a download
> link. (The 2.7 and 3.0 pages are fine so it appears specific to this
> version)
> > >
> >
> > Thats what one gets for trying cheap fancy directory indexes :)
> > (that means: sorry, my fault)
> >
> > Fixed now.
> >
> > Best regards
> >         -Tobias
> > PS: you get a cookie if you guess what happened
> >
> > > Also on a somewhat related note, I am not able to run 1.x images using
> the classic VM... should this be expected to work or is there another Linux
> VM around that will work?
> > >
> > > Thanks,
> > > Phil
> > >
> >
> >
> >
> >
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20171218/6df11714/attachment.html>