From: Nome Grey <greynome72@gmail.com>
To: zimoun <zimon.toutoune@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: bug#26608: channels.scm supporting substitutes
Date: Wed, 4 Dec 2019 04:25:17 -0800 [thread overview]
Message-ID: <CANUb+mVUa_dWvxzRi-NgXp_+AkO4zeEdHxSL4=9ndvCxs--R7A@mail.gmail.com> (raw)
In-Reply-To: <CAJ3okZ32PKyUoCmU55cDy77dnMLO0MSuXHYPZr5fO6Mv_5Jvdg@mail.gmail.com>
Simon, thanks for your attention.
On Wed, Dec 4, 2019, 2:23 AM zimoun <zimon.toutoune@gmail.com> wrote:
> Dear,
>
> On Wed, 4 Dec 2019 at 00:32, Nome Grey <greynome72@gmail.com> wrote:
>
> > [...] I'm trying to get guix going and upgrading on my resource-starved
> system without doing much compilation, using substitutes instead.
>
> Have you already Guix installed on your system?
> If yes, how did you install it? And what is the current version of
> Guix that you are running?
>
Yes, as mentioned in my previous email I am working with the channels.scm
file used by 'guix pull'.
I installed a foreign distribution of guix 1.0.1 i686 using the binary
installation steps from the manual.
I am currently running guix aca2bf5 but have a long-running process to
downgrade to 1b6c5e8 in order to find a substitute for ungoogled-chromium 78
>
next prev parent reply other threads:[~2019-12-04 12:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-22 16:03 bug#26608: Provide --only-substitutes flag to "guix package --upgrade" Christopher Allan Webber
2017-04-22 23:03 ` Ludovic Courtès
2019-12-03 17:55 ` bug#26608: channels.scm supporting substitutes Nome Grey
2019-12-03 21:14 ` zimoun
2019-12-03 23:32 ` Nome Grey
2019-12-04 10:23 ` zimoun
2019-12-04 12:25 ` Nome Grey [this message]
2019-12-04 12:39 ` Nome Grey
2019-12-04 13:56 ` zimoun
2019-12-04 14:55 ` Nome Grey
2019-12-04 17:33 ` zimoun
2019-12-04 21:50 ` Nome Grey
2019-12-05 11:45 ` zimoun
2019-12-05 14:35 ` Nome Grey
2019-12-10 16:41 ` bug#32022: " Ludovic Courtès
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='CANUb+mVUa_dWvxzRi-NgXp_+AkO4zeEdHxSL4=9ndvCxs--R7A@mail.gmail.com' \
--to=greynome72@gmail.com \
--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.
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.