unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Reed Campbell Meyerson <reedmeye@uw.edu>
Cc: 33404@debbugs.gnu.org
Subject: bug#33404: failure behavior for "guix package --upgrade"
Date: Fri, 16 Nov 2018 22:22:41 +0100	[thread overview]
Message-ID: <87sh00sony.fsf@gnu.org> (raw)
In-Reply-To: <CAMHc6K8UGRtcobPSRwFzOVMYHATKfEKmFFpvT7M6y27-PuNKPQ@mail.gmail.com> (Reed Campbell Meyerson's message of "Fri, 16 Nov 2018 00:37:59 +0000")

Hello,

Reed Campbell Meyerson <reedmeye@uw.edu> skribis:

> I am experiencing some strange behavior when upgrading packages. After a
> substitution fails, the upgrade will fail at the same point every time
> until I upgrade that point on its own, and then it will proceed until it
> potentially fails at a different point.
>
> I have attached a screenshot of the output. This was while trying to
> upgrade qutebrowser, but it happened before when upgrading GHC.

Which substitute server(s) are you using?

It could be that the substitute Guix was trying to fetch was temporarily
unavailable from the server and eventually came back—hydra.gnu.org has
been under maintenance a week ago as you might have seen.

Thanks for reporting the issue,
Ludo’.

  reply	other threads:[~2018-11-16 21:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-16  0:37 bug#33404: failure behavior for "guix package --upgrade" Reed Campbell Meyerson
2018-11-16 21:22 ` Ludovic Courtès [this message]
2018-11-17 23:53   ` Reed Campbell Meyerson
2020-12-18 23:47 ` zimoun
2021-01-11 15:31   ` zimoun

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=87sh00sony.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=33404@debbugs.gnu.org \
    --cc=reedmeye@uw.edu \
    /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. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).