From: Luis Felipe <luis.felipe.la@protonmail.com>
To: Luis Felipe <luis.felipe.la@protonmail.com>
Cc: Kyle Andrews <kyle@posteo.net>, help-guix@gnu.org
Subject: Re: Mysteries of channel configuration during system reconfigure
Date: Thu, 09 Mar 2023 15:37:53 +0000 [thread overview]
Message-ID: <qQyJrOdnbK3VuEukICD4P9wjk-xITW1FF3aTiaHO9CE4VVYBiXBcowNjsndLz9m4Ezlk3JatqosCdq-MEgHZ1MD3rfBdGuf80fE5SYBAsrY=@protonmail.com> (raw)
In-Reply-To: <THJL8kgIimmpnSxUFsvJJpC2i3Ayf1xYZ20dvrFKB2B-k08NO32ZLqq0tee_63YKhirlWZEzwK2VAQw4lyt74hDxRi3pp1XsE0OJuldTF40=@protonmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1012 bytes --]
On Thursday, March 9th, 2023 at 15:12, Luis Felipe <luis.felipe.la@protonmail.com> wrote:
> Hi Kyle,
>
>
> On Thursday, March 9th, 2023 at 02:50, Kyle Andrews kyle@posteo.net wrote:
>
> > [...]
>
> > One of the selling points in Guix marketing for me is that the system
> > configuration should be self contained within /etc/config.scm and
> > channels.scm. However, this appears to not be the case. There seems a
> > third element hidden away which prevents me from running:
>
> > `guix system reconfigure /etc/config.scm`
>
>
> This should be:
>
> sudo guix system reconfigure /etc/config.scm
>
> Also, the manual recommends the following:
>
> "Note: It is highly recommended to run guix pull once before you run guix system reconfigure for the first time (see Invoking guix pull). Failing to do that you would see an older version of Guix once reconfigure has completed."
Oops! Sorry I rushed to respond without reading the last part of your message :)
[-- Attachment #1.2: publickey - luis.felipe.la@protonmail.com - 0x12DE1598.asc --]
[-- Type: application/pgp-keys, Size: 1722 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 509 bytes --]
next prev parent reply other threads:[~2023-03-09 15:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-09 2:50 Mysteries of channel configuration during system reconfigure Kyle Andrews
2023-03-09 6:46 ` Julien Lepiller
2023-03-11 0:16 ` Kyle Andrews
2023-03-11 8:08 ` Julien Lepiller
2023-03-09 15:12 ` Luis Felipe
2023-03-09 15:37 ` Luis Felipe [this message]
2023-03-09 15:32 ` SeerLite
2023-03-09 17:58 ` Kyle Andrews
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='qQyJrOdnbK3VuEukICD4P9wjk-xITW1FF3aTiaHO9CE4VVYBiXBcowNjsndLz9m4Ezlk3JatqosCdq-MEgHZ1MD3rfBdGuf80fE5SYBAsrY=@protonmail.com' \
--to=luis.felipe.la@protonmail.com \
--cc=help-guix@gnu.org \
--cc=kyle@posteo.net \
/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).