‘guix refresh -u’ stops at the first failure to determine releases

  • Done
  • quality assurance status badge
Details
2 participants
  • Ludovic Courtès
  • Ludovic Courtès
Owner
unassigned
Submitted by
Ludovic Courtès
Severity
normal
L
L
Ludovic Courtès wrote on 1 Jul 2022 15:54
(address . bug-guix@gnu.org)
87o7y92b26.fsf@inria.fr
Starting from commit 53b9c27aa59bebf955f0aa24fef60a101480ef5c (a fix for

Toggle snippet (6 lines)
$ ./pre-inst-env guix refresh -t cran r-a3 r-googlesheets r-a4 -u
gnu/packages/bioconductor.scm:9233:2: warning: no updater for r-a4
guix refresh: warning: failed to retrieve package information from https://cran.r-project.org/web/packages/googlesheets/DESCRIPTION: 404 (Not Found)
guix refresh: error: updater failed to determine available releases for r-googlesheets

That is, ‘guix refresh -u’ stops on the first failure (in this case
‘r-a3’ is not processed). That makes it hard to use for mass updates as
in ‘guix refresh -t cran -u’.

(Reported by Ricardo on #guix.)

Ludo’.
L
L
Ludovic Courtès wrote on 1 Jul 2022 23:55
Re: bug#56338: ‘guix refresh -u ’ stops at the first failure to determine releases
(address . 56338-done@debbugs.gnu.org)(name . Ricardo Wurmus)(address . rekado@elephly.net)
874k0033ck.fsf@gnu.org
Ludovic Courtès <ludovic.courtes@inria.fr> skribis:

Toggle quote (8 lines)
> Starting from commit 53b9c27aa59bebf955f0aa24fef60a101480ef5c (a fix for
> <https://issues.guix.gnu.org/55987>), we get:
>
> $ ./pre-inst-env guix refresh -t cran r-a3 r-googlesheets r-a4 -u
> gnu/packages/bioconductor.scm:9233:2: warning: no updater for r-a4
> guix refresh: warning: failed to retrieve package information from https://cran.r-project.org/web/packages/googlesheets/DESCRIPTION: 404 (Not Found)
> guix refresh: error: updater failed to determine available releases for r-googlesheets

Fixed in b512dadfd603869ac009a432b56f55945841cce0.

Ludo'.
Closed
?
Your comment

This issue is archived.

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

To respond to this issue using the mumi CLI, first switch to it
mumi current 56338
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