unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
To: Nalin Ranjan <ranjanified@gmail.com>
Cc: help-guix@gnu.org, clement@lassieur.org
Subject: Re: Re Recent hydra.gnu.org maintenance window
Date: Mon, 29 Oct 2018 21:38:45 +0100	[thread overview]
Message-ID: <20181029213845.2d840916@alma-ubu> (raw)
In-Reply-To: <CACE+zkLriFZo56VxxBexo_HbVXTkVfB2YP38GDv7+oP=WeSoyQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1415 bytes --]

Hi Nalin,

On Tue, 30 Oct 2018 00:37:29 +0530
Nalin Ranjan <ranjanified@gmail.com> 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 <packagename>

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örn



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  parent reply	other threads:[~2018-10-29 20:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-29 11:53 Re Recent hydra.gnu.org maintenance window Nalin Ranjan
2018-10-29 14:53 ` Clément Lassieur
2018-10-29 19:07   ` Nalin Ranjan
2018-10-29 20:25     ` Gábor Boskovits
2018-10-29 20:38     ` Björn Höfling [this message]
2018-10-29 20:45     ` Clément Lassieur

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20181029213845.2d840916@alma-ubu \
    --to=bjoern.hoefling@bjoernhoefling.de \
    --cc=clement@lassieur.org \
    --cc=help-guix@gnu.org \
    --cc=ranjanified@gmail.com \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).