From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christopher Lemmer Webber Subject: Re: Golly... what's up with Golly? Date: Thu, 01 Mar 2018 11:27:14 -0600 Message-ID: <87r2p3aeq5.fsf@dustycloud.org> References: <87woyxap24.fsf@dustycloud.org> <87a7vsixao.fsf@netris.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:39707) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1erRzE-0004XW-7f for guix-devel@gnu.org; Thu, 01 Mar 2018 12:27:21 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1erRzA-0007GS-4f for guix-devel@gnu.org; Thu, 01 Mar 2018 12:27:20 -0500 Received: from dustycloud.org ([50.116.34.160]:53034) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1erRz9-0007Ft-WB for guix-devel@gnu.org; Thu, 01 Mar 2018 12:27:16 -0500 In-reply-to: <87a7vsixao.fsf@netris.org> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Mark H Weaver Cc: Guix-devel Mark H Weaver writes: > Christopher Lemmer Webber writes: > >> I think Sourceforge may have gone through a recent upgrade that broke >> some things: >> >> Starting download of /gnu/store/k857xn4vnppdp5z853c92lfa7h5fhdii-golly-3.1-src.tar.gz >> From http://tenet.dl.sourceforge.net/project/golly/golly-3.1/golly-3.1-src.tar.gz... >> following redirection to `http://downloads.sourceforge.net/project/golly/golly-3.1/golly-3.1-src.tar.gz?download&failedmirror=tenet.dl.sourceforge.net'... >> ERROR: download failed >> "http://downloads.sourceforge.net/project/golly/golly-3.1/golly-3.1-src.tar.gz?download&failedmirror=tenet.dl.sourceforge.net" >> 404 "Not Found" > > I suspect that the URL in the package recipe is wrong, and has always > been wrong. I noticed this same error on Hydra's first attempt to build > golly, but never got around to reporting it. > > Mark It looks like you're right... the error was on our end, not SourceForge's. I've pushed a commit correcting the URL.