From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp12.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms9.migadu.com with LMTPS id 2Je6Ahs3DGToGQAASxT56A (envelope-from ) for ; Sat, 11 Mar 2023 09:08:59 +0100 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp12.migadu.com with LMTPS id SFefAhs3DGQ7UwEAauVa8A (envelope-from ) for ; Sat, 11 Mar 2023 09:08:59 +0100 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 719AD973E for ; Sat, 11 Mar 2023 09:08:58 +0100 (CET) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pauHR-0000Kf-Dk; Sat, 11 Mar 2023 03:08:41 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pauHQ-0000KV-Hz for help-guix@gnu.org; Sat, 11 Mar 2023 03:08:40 -0500 Received: from lepiller.eu ([89.234.186.109]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pauHM-00073Q-IA for help-guix@gnu.org; Sat, 11 Mar 2023 03:08:40 -0500 Received: from lepiller.eu (localhost [127.0.0.1]) by lepiller.eu (OpenSMTPD) with ESMTP id fcc475fa; Sat, 11 Mar 2023 08:08:31 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=lepiller.eu; h=date:from :to:cc:subject:in-reply-to:references:message-id:mime-version :content-type:content-transfer-encoding; s=dkim; bh=lBhcNafnl0Sk mmBOOkoHHdimNDMlUUnSDzAqlfj2cBI=; b=VAQv4qeEm/t4cXu1pzkUReVjXWQW uukzJzLxXEMmQF4c2pRyQD0ZrKUhiFv2NBVZMZlIRvZayVYLy/h1mUZIlHNt0O8s UP6PB6RkJnzuFHcBTjb8VDhEtKF9x2cvhlqkPynIDpz36NWlwObxJ8Ydvc7MNZLm g0M5spxGNGOoCB8rlpULRXfDhdLNXkh3NXzFnHmGFCxAshF3T176WQ/Sdl15Oxvo ibSl6deNxcnn/pYff+O/v0xP6dTjbDjqugnCRQxzOCQwCZjetT/aufApVQv4j8BQ 1PEJE4PjKpcQnrVDeAxPssN4LOLj1k6TvCUoc8voHDxDEtLGqvFgIGz9hQ== Received: by lepiller.eu (OpenSMTPD) with ESMTPSA id 2729eca8 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Sat, 11 Mar 2023 08:08:31 +0000 (UTC) Date: Sat, 11 Mar 2023 09:08:28 +0100 From: Julien Lepiller To: Kyle Andrews CC: help-guix@gnu.org Subject: Re: Mysteries of channel configuration during system reconfigure User-Agent: K-9 Mail for Android In-Reply-To: <87bkl0dq2i.fsf@posteo.net> References: <87bkl2mwt6.fsf@posteo.net> <604D4DC9-0417-42D9-BC78-8B02B28D02E3@lepiller.eu> <87bkl0dq2i.fsf@posteo.net> Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Received-SPF: pass client-ip=89.234.186.109; envelope-from=julien@lepiller.eu; helo=lepiller.eu X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: help-guix@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+larch=yhetil.org@gnu.org Sender: help-guix-bounces+larch=yhetil.org@gnu.org X-Migadu-Country: US X-Migadu-Flow: FLOW_IN ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=lepiller.eu header.s=dkim header.b=VAQv4qeE; spf=pass (aspmx1.migadu.com: domain of "help-guix-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="help-guix-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=none) header.from=lepiller.eu ARC-Seal: i=1; s=key1; d=yhetil.org; t=1678522138; a=rsa-sha256; cv=none; b=qPr6yr+ui982mbCO0JfkIBTK9uxwEvZ6bX+x5LxrpHVzCn+GeFmE/e0QaiNGfp+M/aA6wU rRy28MVX4WlxS5qRdcCJkld8L9hn4SIl4o1/kquLWVeq5zWH3PdBBvrlv8pXH2UyWiEFAt ju/5tQDxp8gB43Jg15TSpkpNJF+qkumTtrkcTKeiIFr7hOHz5sIwnf7z77lMvJaqKB7gq0 VWO+DVf7SbxPWvjQa5+BwSS2e7VxVXrYPEcRBFJpWjjvoyDEKyLjNum4WUN/f8Gr4fdbbR xvKYg2Jt80+afwFzozE1dy15VTarYBPECJculO5anrarhy8fIXgsvDEOVibIkQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1678522138; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:list-id:list-help: list-unsubscribe:list-subscribe:list-post:dkim-signature; bh=lBhcNafnl0SkmmBOOkoHHdimNDMlUUnSDzAqlfj2cBI=; b=jaE4Aht8BKo+zpWdP1H1aXrwtqnlqq8ue73YZJkVLlPWq05NeoBErW+hdOzQV5jfZUkcNc /ILaZs1A7OkYRowedkCAgUZeQ37vaoiark3qBxeIHh7g/IU0p7ZGuJzUcXfV2IU0hO1jmd llbb2U5fVP0UvQspppBZfkkVaAamVtTklURW99HLeRvrgjbGcGukXaJIktEgFq8p3Zcmux EHpqze7EGXH4hjYabh3JPmi/HthR96NIxA1G2H99FfWfSZMkaZ03Mo5J20Hra2MGNdOMCL OjSZmVb/loHJqTKZ/VXqBcXyCgqS6LHJJLQaKVLk6nH4RRKdXC/wpNQBxI/Xuw== X-Migadu-Spam-Score: -6.43 X-Spam-Score: -6.43 X-Migadu-Queue-Id: 719AD973E X-Migadu-Scanner: scn1.migadu.com Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=lepiller.eu header.s=dkim header.b=VAQv4qeE; spf=pass (aspmx1.migadu.com: domain of "help-guix-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="help-guix-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=none) header.from=lepiller.eu X-TUID: mFvFo1Wk3vIM Le 11 mars 2023 01:16:21 GMT+01:00, Kyle Andrews a =C3= =A9crit=C2=A0: > >Julien Lepiller writes: > >> Does your /etc/channels=2Escm list the extra channels? > >At this point it does not=2E I "restored" a backup from my old computer >into my home directory=2E Now I have several more channels than I had >configured in generation one=2E Unfortunately, now my shepherd is broken >just like on my old computer=2E > >I wish I understood how to experiment with e=2Eg=2E virtual machines to >better understand this process=2E However, there seems to be quite a larg= e >knowledge barrier=2E I also don't feel comfortable with my current >capabilities exploring the Guix codebase to see what the relevant >procedures are=2E There is a lot to learn! I'm not sure what manages /etc/channels=2Escm, but I don't think Guix crea= tes it? In any case, you use that file when pulling, so at the time you pul= l, you should list all the channels you want to use in that file=2E > >> "guix describe" will be more accurate about what channels your current >> guix knows about=2E > >It's not clear to me what "your current guix" even is in my case=2E Does = the latest pull define the current guix? It should, but what I meant by that is "whatever your shell believes it sh= ould run when you type guix" > >On my old computer guix system describe shows a slightly older revision >of Guix channels than guix describe=2E Meanwhile, the root user's guix de= scribe shows just the one Guix channel with yet another commit=2E > >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=2E If it fails to boot, you should still be able to select an older, known to= work, generation at the grub screen=2E That's the magic of Guix :) > >> If you type "type guix" and "which guix", they should agree it's >> ~/=2Econfig/guix/current/bin/guix, not something else like >> ~/=2Eguix-profile or ~/=2Eguix-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"=2E I also noticed that whi= ch --all guix shows two lines: the latter being /run/current-system=2E cd is a builtin, so "type cd" should tell you that=2E "which" will only lo= ok for a binary in your $PATH, so it should report that it can't find it=2E type itself is a builtin, and it will tell you what a binary is, according= to the shell=2E Bash and other shells have a cache of command name to loca= tion=2E When you use "type guix" it should tell you where it finds guix, ac= cording to that cache=2E If it's different from "which guix", which only lo= oks in $PATH, not in the shell cache, it means you should refresh that cach= e with "hash guix" (I think hash is also a builtin)=2E If which does not tell it's your pulled guix (ie=2E ~/=2Econfig/guix/curre= nt/bin/guix), it means your $PATH is not set properly=2E A guix command could come from different locations in your system=2E At le= ast one is installed with your system at /run/current-system=2E > >I have to admit I'm not still sure what general insight I should be glean= ing from your statement, however it sounds like it is pretty neat=2E > >> If you reconfigure as the root user, you should pull as the root >> user=2E If you use sudo, which is recommended, make sure that the above >> works properly with sudo too=2E > >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=2E Your user's and root's guix are different, as you noticed=2E So, I was jus= t wondering whether you were doing something like su then reconfigure, or s= udo guix=2E When you use su, you login as root, and use root's guix=2E When= you sudo, you run the user program with root priviledges, which is quite d= ifferent in that case=2E With su, you run root's guix, so you should pull as root=2E With sudo, you= run the user's guix, so you should pull as a user (don't pull with sudo, i= t will mess up rights in your home directory)=2E Also, I don't personnaly use the recommended way as I find sudo confusing= =2E I wanted to make sure the above is correct, so does "guix describe" giv= e you the same as "sudo guix describe"? > >Thanks for your help!