On Tuesday 14 December 2010 16:27:17 Daxter wrote: > I know that's there (I noted that in my original message). We're currently on > build 1310, though, not 1306. The problem isn't that no source code is > available; it's that [a] the link on our main website consistently 404's and > [b] the most recent source isn't available through the only method noted on > the Freenet download page.
Sorry, scripting foulup. Will be fixed as soon as the uploads complete (hour or less). > > On Dec 14, 2010, at 10:08 AM, Mel Charters wrote: > > > Check > > http://code.google.com/p/freenet/downloads/detail?name=freenet-build01306-source.tar.bz2&can=2&q= > > Mel Charters > > mcharter...@q.com > > > > > > > > On Dec 14, 2010, at 2:27 AM, Daxter wrote: > > > >> I noticed this problem previously but I never bothered until now to report > >> it. That is, the /download.html page on freenetproject.org has a link to > >> source code that rarely can actually be accessed. The last line of the > >> page links to the source code here: > >> http://freenet.googlecode.com/files/freenet-build01310-source.tar.bz2 and > >> yet it cannot be accessed because it isn't actually there. After some > >> checking I found that build 1306 is the newest version available this way. > >> So, for at least 4 releases this (likely auto-updated) link has been > >> pointing to (a manually updated) file that hasn't been uploaded, resulting > >> in a lot of responses like my initial one: "WTC? Why can't I download > >> this!? Are they trying to hide some CIA call-home code??" > >> > >> Whatever people might think, this consistently unavailable link only > >> serves to turn away those who might help improve our code in the future. > >> Now, how do we keep this from happening again? > >> > >> This is a particularly unique problem because, unlike with most projects > >> where the vast majority of normal users only update when major releases > >> come around every couple months/years, our entire user-base must update to > >> the newest code something like once a week. It's easy for everyone else to > >> simply triple-check their links before publishing, but for us it can get > >> quite tiring to do that every week. > >> > >> I don't know what the best solution would be, but I think it's important > >> that we fix this chronic broken-link syndrome.
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Support mailing list Support@freenetproject.org http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:support-requ...@freenetproject.org?subject=unsubscribe
