unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Luis Felipe <luis.felipe.la@protonmail.com>
To: zimoun <zimon.toutoune@gmail.com>
Cc: Alex <aleksq@protonmail.ch>, "help-guix@gnu.org" <help-guix@gnu.org>
Subject: Re: Status of GNOME?
Date: Tue, 23 Nov 2021 20:09:54 +0000	[thread overview]
Message-ID: <rOlI7LtX2R_8eoOiffzcXwXc7hZvmWFPKF_6hEkkF2ZO_Thvt-bGgIzTyiPXHjj9fRTIqIspObqywUYuwLjpDVDHvia6CKruuavIC3Ipqkc=@protonmail.com> (raw)
In-Reply-To: <CAJ3okZ2AU8OD_N_cR=GighYs0yLqoscamkyjCkeTjoDWXBj--g@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 671 bytes --]

Hi, zimoun :)

On Tuesday, November 23rd, 2021 at 2:32 PM, zimoun <zimon.toutoune@gmail.com> wrote:
> 

> You can run:
> 

> guix pull --branch=core-updates-frozen
> 

> and upgrade your system. Report the failures. Note that it is
> 

> possible that substitutes are missing; maybe check using "guix
> 

> weather" the availability if you cannot or do not want to burn CPU.

Is there a way to see this information on the web (https://ci.guix.gnu.org/)? Say, substitute availability for packages in core-updates-frozen (x86_64-linux).

The machine I use is not capable of building much, and running "guix weather -s x86_64-linux" takes a lot of time.

[-- Attachment #1.2: publickey - luis.felipe.la@protonmail.com - 0x12DE1598.asc --]
[-- Type: application/pgp-keys, Size: 1815 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 509 bytes --]

  reply	other threads:[~2021-11-23 20:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-22 13:37 Status of GNOME? Alex via
2021-11-23 14:32 ` zimoun
2021-11-23 20:09   ` Luis Felipe [this message]
2021-11-23 20:30     ` zimoun
2021-11-23 22:32       ` Luis Felipe

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='rOlI7LtX2R_8eoOiffzcXwXc7hZvmWFPKF_6hEkkF2ZO_Thvt-bGgIzTyiPXHjj9fRTIqIspObqywUYuwLjpDVDHvia6CKruuavIC3Ipqkc=@protonmail.com' \
    --to=luis.felipe.la@protonmail.com \
    --cc=aleksq@protonmail.ch \
    --cc=help-guix@gnu.org \
    --cc=zimon.toutoune@gmail.com \
    /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).