all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Reed Campbell Meyerson <reedmeye@uw.edu>
To: ludo@gnu.org
Subject: bug#33404: failure behavior for "guix package --upgrade"
Date: Sat, 17 Nov 2018 23:53:59 +0000	[thread overview]
Message-ID: <CAMHc6K946yJFMb22Q4T2gs5bvzHdod_E-O9r-WXg-kkoq2C4dQ@mail.gmail.com> (raw)
In-Reply-To: <87sh00sony.fsf@gnu.org>

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

I'm not quite sure how to check, but I don't think I added anything that
wasn't default.

On Fri, Nov 16, 2018 at 9:23 PM Ludovic Courtès <ludo@gnu.org> wrote:

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

[-- Attachment #2: Type: text/html, Size: 1420 bytes --]

  reply	other threads:[~2018-11-19 20:13 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
2018-11-17 23:53   ` Reed Campbell Meyerson [this message]
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

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

  git send-email \
    --in-reply-to=CAMHc6K946yJFMb22Q4T2gs5bvzHdod_E-O9r-WXg-kkoq2C4dQ@mail.gmail.com \
    --to=reedmeye@uw.edu \
    --cc=ludo@gnu.org \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.