unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Kyle Andrews <kyle@posteo.net>
To: Julien Lepiller <julien@lepiller.eu>
Cc: help-guix@gnu.org
Subject: Re: Mysteries of channel configuration during system reconfigure
Date: Sat, 11 Mar 2023 00:16:21 +0000	[thread overview]
Message-ID: <87bkl0dq2i.fsf@posteo.net> (raw)
In-Reply-To: <604D4DC9-0417-42D9-BC78-8B02B28D02E3@lepiller.eu>


Julien Lepiller <julien@lepiller.eu> writes:

> guix system describe lists channels used to build your system, but
> they can be different from the ones currently known to guix.

That seems consistent with what I have observed.

> Does your /etc/channels.scm list the extra channels?

At this point it does not. I "restored" a backup from my old computer
into my home directory. Now I have several more channels than I had
configured in generation one. Unfortunately, now my shepherd is broken
just like on my old computer.

I wish I understood how to experiment with e.g. virtual machines to
better understand this process. However, there seems to be quite a large
knowledge barrier. I also don't feel comfortable with my current
capabilities exploring the Guix codebase to see what the relevant
procedures are. There is a lot to learn!

> "guix describe" will be more accurate about what channels your current
> guix knows about.

It's not clear to me what "your current guix" even is in my case. Does the latest pull define the current guix?

On my old computer guix system describe shows a slightly older revision
of Guix channels than guix describe. Meanwhile, the root user's guix describe shows just the one Guix channel with yet another commit.

As a naive user, I'm understandably more scared that my computer will
fail to boot if I upgrade, so I tend to run guix system reconfigure less
frequently than guix pull.

> If you type "type guix" and "which guix", they should agree it's
> ~/.config/guix/current/bin/guix, not something else like
> ~/.guix-profile or ~/.guix-home or even /run/current-system

I had never heard of the type command! I noticed type and which give
different results for "type cd" and "which cd". I also noticed that which --all guix shows two lines: the latter being /run/current-system.

I have to admit I'm not still sure what general insight I should be gleaning from your statement, however it sounds like it is pretty neat.

> If you reconfigure as the root user, you should pull as the root
> user. If you use sudo, which is recommended, make sure that the above
> works properly with sudo too.

I'm curious to learn more about your rationale for this statement as I
was successful at building a second generation only once I used the "sudo" path with my non-root user.

Thanks for your help!


  reply	other threads:[~2023-03-11  1:39 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 [this message]
2023-03-11  8:08     ` Julien Lepiller
2023-03-09 15:12 ` Luis Felipe
2023-03-09 15:37   ` Luis Felipe
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=87bkl0dq2i.fsf@posteo.net \
    --to=kyle@posteo.net \
    --cc=help-guix@gnu.org \
    --cc=julien@lepiller.eu \
    /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).