From mboxrd@z Thu Jan  1 00:00:00 1970
From: Alex Griffin <a@ajgrf.com>
Subject: Re: SourceForge URLs changed
Date: Fri, 15 Jul 2016 13:15:50 -0500
Message-ID: <1468606550.1350818.667482953.14E7F10E@webmail.messagingengine.com>
References: <87zipmmpgd.fsf@gnu.org>
	<1468366639.988393.664541057.3070633A@webmail.messagingengine.com>
	<87shvdn8r2.fsf@gnu.org>
	<1468596493.1316361.667333481.4DA63202@webmail.messagingengine.com>
	<20160715175819.GA19508@jasmine>
Mime-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:51769)
	by lists.gnu.org with esmtp (Exim 4.71) (envelope-from <a@ajgrf.com>)
	id 1bO7ek-0008Dd-2g
	for guix-devel@gnu.org; Fri, 15 Jul 2016 14:16:11 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <a@ajgrf.com>) id 1bO7ef-0001zR-1Q
	for guix-devel@gnu.org; Fri, 15 Jul 2016 14:16:08 -0400
In-Reply-To: <20160715175819.GA19508@jasmine>
List-Id: "Development of GNU Guix and the GNU System distribution."
	<guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/guix-devel/>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
Sender: "Guix-devel" <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org

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

-- 
Alex Griffin