From: "Catriel Omar D'Elía" <cdelia@dc.uba.ar>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: help-guix@gnu.org
Subject: Re: enchant hash, fail to upgrade
Date: Tue, 24 Sep 2019 16:18:43 -0300 [thread overview]
Message-ID: <871rw5wlik.fsf@dc.uba.ar> (raw)
In-Reply-To: <87o8z9oeeb.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Tue, 24 Sep 2019 18:19:40 +0200")
Ludovic Courtès <ludo@gnu.org> writes:
> ¡Hola!
>
> "Catriel" <cdelia@dc.uba.ar> skribis:
>
>> $guix upgrade --fallback
>> guix upgrade: aviso: paquete 'libstdc++' ya no existe
>> guix upgrade: el paquete 'sbcl-next' ha sido reemplazado por 'next'
>> substitute: updating substitutes from 'https://mirror.hydra.gnu.org'... 100.0%
>
> Este servidor de substituciones está invalido ahora; deberías usar
> https://ci.guix.gnu.org en lugar de esta dirección:
>
> https://lists.gnu.org/archive/html/info-guix/2019-06/msg00001.html
>
> Ludo'.
Ah I was not aware of this...
porque casi nunca uso --fallback y no recordaba que si no hay server de
substitución --fallback es por defecto. Estaba comenzando a pensar que
siempre se construyen las derivaciones y entonces guix elige substituir
el paquete o compilarlo (build it). No, lo que siempre hace es calcular
el hash, las derivaciones solo cuando debe compilar (lógico, era un paso
innecesario). El link que me pasaste me aclaró la mente. Gracias!
maybe a command like:
guix news
could prove helpful for this kind of scenarios?
Chau!
PD: buen español Ludo'!
COD.
next prev parent reply other threads:[~2019-09-24 19:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-22 19:22 enchant hash, fail to upgrade Catriel
2019-09-22 21:30 ` Julien Lepiller
2019-09-22 22:38 ` Catriel
2019-09-23 10:11 ` Julien Lepiller
2019-09-23 16:09 ` Tobias Geerinckx-Rice
2019-09-24 18:44 ` Catriel Omar D'Elía
2019-09-24 19:25 ` Tobias Geerinckx-Rice
2019-09-24 15:32 ` Catriel Omar D'Elía
2019-09-24 16:19 ` Ludovic Courtès
2019-09-24 19:18 ` Catriel Omar D'Elía [this message]
2019-09-24 19:51 ` Tobias Geerinckx-Rice
2019-09-25 17:43 ` Catriel Omar D'Elía
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=871rw5wlik.fsf@dc.uba.ar \
--to=cdelia@dc.uba.ar \
--cc=help-guix@gnu.org \
--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.
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).