Could you clarify why using the mirror system isn't appropriate? Several users have told me that the mirror system works fine with the apt repositories they set up, and it seems to me that using the mirror system would provide better download availability and performance.
That is, if you hard code to files directly, you'd need to designate a specific mirror (which we don't recommend), which would mean 1) some users may be forced to a mirror halfway across the globe, 2) you'll run into availability issues if the mirror goes down or needs to be taken offline for some reason, and 3) you miss out on download statistics (which only get logged if the downloads go through our mirror redirector). Best Regards, Chris Tsai SourceForge Support sfnet_...@geek.net On Tue, May 29, 2012 at 12:14 PM, Marcelo Santana <marcgsant...@yahoo.com.br > wrote: > On Tue, 29 May 2012 09:26:53 -0400, Christopher Tsai <ct...@geek.net> > wrote: > > > Hello, > > Hello Chistopher, > > > I run support for SourceForge, and one of my colleagues (Roberto) > > passed on this message to me. Perhaps I can shed some light on this. > > > > It looks like the previous attempt to host a Debian repo on our > > site[1] was using the "Project Web" hosting space on our site, > > however, that space is designed to be used only for web site content, > > not downloads. That rationale, coupled with past abuse on that space > > led to us implementing the bandwidth limits. > > [1]http://apacheoo-deb.sourceforge.net/ > > Yes, I had configured the web space as a Debian repository. When I > saw the warning about temporary lock because of bandwidth limitation I > stopped my tests and deleted all the files. My sincere apologies for > the inconvenience. > > > The File Release System[2] on the other hand, does not have said > > bandwidth limits, and while I haven't done this myself, I've heard > > from several users that they've had no problems setting up a Debian > > repos in this space. They said that all they did was set up the repo > > locally, then used rsync[3] to upload it to the File Release System. > > Doing it this way also gives the added benefit of utilizing both our > > worldwide mirror system, as well as our file statistics systems. > > [2]http://sourceforge.net/projects/apacheoo-deb/files/ > > [3]https://sourceforge.net/apps/trac/sourceforge/wiki/Rsync%20over%20SSH > > > > Let me know if this helps! > > I've tried to set up the repository by the File Release System today > but it isn't good for use as a Debian repository, because doesn't permit > direct downloads but just via mirrors system. > > Is there another alternative to do this on sourceforge.net? > > We need a hosting with good bandwidth that provide direct access to > download of archives from repository. Thus we can just add a new entry > in /etc/apt/sources.list and run "sudo apt-get update && sudo apt-get > install openoffice.org3-writer..." on any i386 or amd64 Debian machine > or derivative. > > I hope this help to understand our needs. > > Regards, > > -- > Marcelo G. Santana(aka msantana) | GNU/Linux User number: #208778 > JID:marcelo.sant...@jabber-br.org | GNU Privacy Guard ID: 89C55467 > http://blog.msantana.eng.br | http://identi.ca/mgsantana > http://www.debianbrasil.org | http://br.gnome.org > -- ==== This e- mail message is intended only for the named recipient(s) above. It may contain confidential and privileged information. If you are not the intended recipient you are hereby notified that any dissemination, distribution or copying of this e-mail and any attachment(s) is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender by replying to this e-mail and delete the message and any attachment(s) from your system. Thank you.
