From: ludo@gnu.org (Ludovic Courtès)
To: Alex Griffin <a@ajgrf.com>
Cc: guix-devel@gnu.org
Subject: Re: SourceForge URLs changed
Date: Sat, 16 Jul 2016 14:17:02 +0200 [thread overview]
Message-ID: <877fclbww1.fsf@gnu.org> (raw)
In-Reply-To: <1468606550.1350818.667482953.14E7F10E@webmail.messagingengine.com> (Alex Griffin's message of "Fri, 15 Jul 2016 13:15:50 -0500")
Alex Griffin <a@ajgrf.com> skribis:
> On Fri, Jul 15, 2016, at 12:58 PM, Leo Famulari wrote:
>> I contacted SourceForge to ask about this. They said that they did have
>> an outage that lasted for ~23 hours but that, otherwise, there has been
>> no change to the URLs from which they serve things.
>>
>> Is anyone still noticing problems on our end? If so, can you give some
>> details that I can pass on to SourceForge?
>
> I haven't done a whole lot of testing, but as an example I've run into
> problems when trying to update wesnoth for example. I can download the
> source from the web interface or from a new URL, but the old URL we used
> is broken now.
>
> So this used to work, but doesn't any more:
>
> https://downloads.sourceforge.net/project/wesnoth/wesnoth-1.12.5.tar.bz2
>
> Now it has to be:
>
> https://downloads.sourceforge.net/project/wesnoth/wesnoth-1.12/wesnoth-1.12.5/wesnoth-1.12.5.tar.bz2
Right, and before that, it was “/sourceforge” instead of “/project” (see
commit cd4c41fdcf469524161fbbec58c2756f36bcef56.)
Ludo’.
next prev parent reply other threads:[~2016-07-16 12:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-12 23:00 SourceForge URLs changed Ludovic Courtès
2016-07-12 23:37 ` Alex Griffin
2016-07-13 10:16 ` Ludovic Courtès
2016-07-15 15:28 ` Alex Griffin
2016-07-15 17:58 ` Leo Famulari
2016-07-15 18:15 ` Alex Griffin
2016-07-16 12:17 ` Ludovic Courtès [this message]
2016-07-16 2:58 ` Leo Famulari
2016-07-16 3:00 ` Leo Famulari
2016-07-17 20:58 ` Leo Famulari
2016-07-17 21:40 ` Ricardo Wurmus
2016-07-17 21:50 ` Leo Famulari
2016-07-18 18:30 ` Alex Griffin
2016-07-18 22:21 ` Leo Famulari
2016-07-21 14:33 ` Leo Famulari
2016-07-21 15:32 ` Andreas Enge
2016-07-21 16:34 ` Ludovic Courtès
2016-07-21 20:41 ` Alex Griffin
2016-07-21 22:13 ` Leo Famulari
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877fclbww1.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=a@ajgrf.com \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.