-----BEGIN PGP SIGNED MESSAGE-----
On Thu, 4 Jun 2009 21:19:23 +0300
Nikodemus Siivola <nikodemus@...> mentioned:
> 2009/6/4 Nikodemus Siivola <nikodemus@...>:
> > Oh feh. This release is probably going to win the "buggiest since 1.0"
> > award at this rate.
> > I think the best solution is for me to replace the .bz2's with new
> > ones that have a placeholder SUPPORT.
> Done. (I should probably say that the "buggiest" comment was somewhat
> over the top -- while there is one known regression in the release,
> otherwise is should now be fine. Sourceforge release area contains a
> hotpatch for the 64-bit platform (COMPLEX SINGLE-FLOAT) FILL bug,
> which is also fixed in 18.104.22.168.)
Thanks for info, I missed that patch when updating the FreeBSD port.
Can you, please, don't reroll the original tarball and just uppload
the new one under another name? Otherwise it breaks packet systems
which rely on these tarballs.
> Please do let us know if anything else turns up.
It looks like the new tarball contains a number of weird files like
thise: contrib/sb-bsd-sockets/._win32-sockets.lisp. I don't know
what these files are, but they weren't present in the previous version.
As sbcl installs all files found in its directories, this files
get installed too, which is bad thing, especially since the old
tarball is not available anymore. Can you check, please?
-----BEGIN PGP SIGNATURE-----
-----END PGP SIGNATURE-----