From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?B?QmrDtnJuIEjDtmZsaW5n?= Subject: Re: Re Recent hydra.gnu.org maintenance window Date: Mon, 29 Oct 2018 21:38:45 +0100 Message-ID: <20181029213845.2d840916@alma-ubu> References: <87r2g8vm6i.fsf@lassieur.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; boundary="Sig_/kxZMKmPREsQevmcdJXSp5oL"; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:59752) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gHEJJ-0004w4-NK for help-guix@gnu.org; Mon, 29 Oct 2018 16:38:54 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gHEJE-0001c5-Lh for help-guix@gnu.org; Mon, 29 Oct 2018 16:38:53 -0400 Received: from m4s11.vlinux.de ([83.151.27.109]:48298 helo=bjoernhoefling.de) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gHEJE-0001bN-DX for help-guix@gnu.org; Mon, 29 Oct 2018 16:38:48 -0400 In-Reply-To: List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org Sender: "Help-Guix" To: Nalin Ranjan Cc: help-guix@gnu.org, clement@lassieur.org --Sig_/kxZMKmPREsQevmcdJXSp5oL Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi Nalin, On Tue, 30 Oct 2018 00:37:29 +0530 Nalin Ranjan wrote: > It's just that I am not trying to upgrade Guix, but have been trying > to unsuccessfully install GuixSD for the first time ever on my > laptop. In the past week or so I have ran the command system init > like 7-8 times,and every time it fails into 504(Gateway timeout), or > Patch not found(may be 404), and couple of occasions SHA mismatch. I In addition to what Gabor already said: The 504 is possibly due to Hydra/Berlin not working. The 404 could be a patch no longer existing on the net? Though I thought we attach all patches directly to the packages? But maybe it was not a patch but the package sources as such. That can happen if you build from sources and they are gone. Unfortunately some upstream maintainers don't let old sources stay on the server but only the newest release. Likewise the SHA mismatch could be because a tarball was updated in-place. This problem also is the case with some github URLs. If you get those 404s or SHA-mismatches again, you can try to recompile a specific package with guix build --no-substitutes and then concentrate on that specific package. You can then come back with detailed log of just that package, then someone can investigate and might update the package definition to reflect the changed world. Bj=C3=B6rn --Sig_/kxZMKmPREsQevmcdJXSp5oL Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlvXb9YACgkQvyhstlk+X/0MPACeJ2T6TzoWRcBnJs//f6ok6kD7 vG0An1P2TjrsRXJFE7RW60YNLGeocuxU =kPs0 -----END PGP SIGNATURE----- --Sig_/kxZMKmPREsQevmcdJXSp5oL--