Re: Sourceforge file release bugs.

Kristian Kvilekval writes:



>> I figured out that if I don't do anything on the 2.2.5 release page, but 
>> merely push "Update/Refresh" for each file, the file will then appear on the 
>> download page.  Definitely a bug.
> 
> Couldn't this be a feature and not a bug, as you can setup all the 
> release file, then do one update/refresh and they magically all appear?

No.  I have to hit "Update/Refresh" for _every_ file that that gets moved.

Sourceforge's file release system really sucks when you're working with 
multiple files.  To move a bunch of files from release A to release B you 
have to:

A) Open release A, then change the release of each file, one file at a time 
and hitting "Update/Refresh".  You can't even change all files to release B, 
then just hit "Update/Refresh" for each file.

The "Update/Refresh" button updates the info for a single file only, and 
everything else gets reset to what it was before.

B) Open release B, then hit "Update/Refresh" again for each file you've just 
moved.  Again, "Update/Refresh" affects a single file only, and all other 
files are ignored.

"B" is definitely a bug.  The files are still in the FTP directory, and are 
registered against release B properly, except that they don't appear on the 
download page, for release B, until you hit "Update/Refresh".

>> Also, a "zinf-2.2.5.tar.gz" file was initially uploaded for the beta 
>> package, and there's now a "zinf-2.2.5.tar.gz" uploaded in the zinf 2.2.5 
>> package.  I've hidden the beta package, but did not touch the actual file 
>> entry.  I suspect that if I tell sourceforge to drop the file from the beta 
>> release, it'll drop the new file instead.  I'll wait until 2.2.6 is 
>> released, before experimenting.
> 
> So even though they are different packages (zinf vs zinf-beta) they
> are stored in the same place?  I am not really sure what you are saying
> here.

That's exactly what I'm saying.  The entire project has a single FTP 
directory.  The master FTP site is 
ftp://osdn.dl.sourceforge.net/pub/sourceforge/zinf, and all sourceforge 
mirrors sync against that.

Everything in the zinf project gets dumped into this directory.  When you 
upload a file and pick it up on the file release page, that's where it ends 
up going.  It doesn't appear there until you've assigned its file type, but 
as soon as you've done that, it appears in this directory.

Meaning that if you upload another file, it will go into this directory and 
blow away the older file, even if it's linked to another release.

I've been using Sourceforge almost since its inception.  Initially, 
distribution was heavily FTP-oriented, and the links off the download page 
went to the project FTP directory directly.

Immediately after a file release, the FTP links went always to the master 
osdn.dl site.  After a few days, when the mirrors picked up everything, 
sourceforge began round-robin-ing the FTP links out.

Eventually Sourceforge switched to HTTP for distribution, but it's mostly a 
thick layer of make-up for the existing FTP infrastructure, and beneath the 
stage each project is still nothing more than a single FTP directory.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQBALv5ox9p3GYHlUOIRAtecAJ9shF1mN3L7n/795HSJTp6T07ThygCfTNd+
LU0BFr7LPRfd1H+R9LfGpGQ=
=ECmv
-----END PGP SIGNATURE-----