From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:43443) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gQYuk-0006Eu-G6 for guix-patches@gnu.org; Sat, 24 Nov 2018 09:28:08 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gQYug-0000in-Ay for guix-patches@gnu.org; Sat, 24 Nov 2018 09:28:06 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:40624) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gQYug-0000ia-7a for guix-patches@gnu.org; Sat, 24 Nov 2018 09:28:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1gQYuf-0001yW-Rl for guix-patches@gnu.org; Sat, 24 Nov 2018 09:28:01 -0500 Subject: [bug#33473] gnurl: Update to 7.62.0 Resent-Message-ID: Date: Sat, 24 Nov 2018 14:28:05 +0000 From: ng0@n0.is Message-ID: <20181124142805.pfs6flahr4fblqsj@abyayala> References: <20181123152809.qnx7omlqnyabsdqv@abyayala> <878t1joej3.fsf@fastmail.com> <20181123182120.quegqbudg5esrk6k@abyayala> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20181123182120.quegqbudg5esrk6k@abyayala> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: Marius Bakke Cc: 33473@debbugs.gnu.org ng0@n0.is transcribed 599 bytes: > Marius Bakke transcribed 1.0K bytes: > > ng0@n0.is writes: > > > > > From 8b0b2726c585ac51570c70d3b55d2e75a8401606 Mon Sep 17 00:00:00 2001 > > > From: ng0 > > > Date: Fri, 23 Nov 2018 15:24:57 +0000 > > > Subject: [PATCH] gnu: gnurl: Update to 7.62.0. > > > > > > * gnu/packages/gnunet.scm: Update to 7.62.0. > > > > I tried building this, but the source tarball seems unavailable: > > . > > > > Are we downloading from the correct URL? > > > Wow. this is weird. > I thought it was published when I did the release email a while back. > Guess I have to talk to the FTP admin. > > Sorry. I just tried to upload again. Got published now. Must've been something with the infrastructure on their side.