failure behavior for "guix package --upgrade"

  • Done
  • quality assurance status badge
Details
3 participants
  • Ludovic Courtès
  • Reed Campbell Meyerson
  • zimoun
Owner
unassigned
Submitted by
Reed Campbell Meyerson
Severity
normal
R
R
Reed Campbell Meyerson wrote on 16 Nov 2018 01:37
(address . bug-guix@gnu.org)
CAMHc6K8UGRtcobPSRwFzOVMYHATKfEKmFFpvT7M6y27-PuNKPQ@mail.gmail.com
Hello,

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.

Best,
Reed
Attachment: file
Attachment: 2018-11-15-163434_1366x768_scrot.png
L
L
Ludovic Courtès wrote on 16 Nov 2018 22:22
(name . Reed Campbell Meyerson)(address . reedmeye@uw.edu)(address . 33404@debbugs.gnu.org)
87sh00sony.fsf@gnu.org
Hello,

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

Toggle quote (8 lines)
> 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’.
R
R
Reed Campbell Meyerson wrote on 18 Nov 2018 00:53
(address . ludo@gnu.org)
CAMHc6K946yJFMb22Q4T2gs5bvzHdod_E-O9r-WXg-kkoq2C4dQ@mail.gmail.com
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:

Toggle quote (21 lines)
> 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: file
Z
Z
zimoun wrote on 19 Dec 2020 00:47
(name . Reed Campbell Meyerson)(address . reedmeye@uw.edu)(address . 33404@debbugs.gnu.org)
863602u15k.fsf@gmail.com
Hi,

Thank you for the report of the bug33404.


It appears it was a transient issue. And since it is old (~2years),
then I am in favor to close it if no moreinfo is provided.

All the best,
simon
Z
Z
zimoun wrote on 11 Jan 2021 16:31
(name . Reed Campbell Meyerson)(address . reedmeye@uw.edu)(address . 33404-done@debbugs.gnu.org)
867dojsd6a.fsf@gmail.com
Hi,

On Sat, 19 Dec 2020 at 00:47, zimoun <zimon.toutoune@gmail.com> wrote:

Toggle quote (3 lines)
> It appears it was a transient issue. And since it is old (~2years),
> then I am in favor to close it if no moreinfo is provided.

After the usual 3 weeks, since it requires moreinfo and seems transient,
I am closing. Feel free to reopen if I am missing something.


All the best,
simon
Closed
?
Your comment

This issue is archived.

To comment on this conversation send an email to 33404@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 33404
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch