Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
From: Sam Steingold <sds@po...> - 2008-07-08 17:27:58
Nelson H. F. Beebe wrote:
> The announcement of CLISP 2.46 was issued six days ago,
> but ftp.gnu.org still has a broken link to the distribution
> ncftp /gnu/clisp/release > pwd
> ncftp /gnu/clisp/release > dir -tr
> drwxr-xr-x 2 1003 1003 4096 May 16 15:50 2.45
> lrwxrwxrwx 1 1003 1003 4 Jul 2 15:50 latest -> 2.46
> ncftp /gnu/clisp/release > cd 2.46
> Could not chdir to 2.46: server said: Failed to change directory.
this is a byproduct of the "broken by design" gnu upload system.
I have to upload 4 files for each file I want to see on the ftp site
and I am _not_ notified whether the upload has succeeded or not.
in this case, the original upload failed in all facets except for the
symlink creation. I did not check whether it succeeded (ISTR that once
upon a time at least some errors were reported by e-mail - but not any
So, thanks to your alert, I now re-uploaded everything.
(BTW, it took me two upload attempts to get the bz2 file there).
just to make sure: when I say "upload success" here I do _not_ mean "no
ftp errors" - that is always assumed (ftp is always successful). what I
mean is that the gnu.org software _silently_ failed to copy the uploaded
files to the right place. no error messages, no explanations, no
Thanks for your vigilance.
Note that throughout all this time, all the files (plus woe32 binaries)
have been available on the SF download site,
as the first "official distribution site" on <http://clisp.cons.org/>
for precisely this reason: reliability.