[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#42810: Guix doesn't follow all symlinks

From: Steffen Rytter Postas
Subject: bug#42810: Guix doesn't follow all symlinks
Date: Wed, 16 Sep 2020 12:24:01 +0200
User-agent: Evolution 3.36.4-0ubuntu1


ons, 16 09 2020 kl. 11:33 +0200, skrev zimoun:
> Dear,
> On Wed, 16 Sep 2020 at 09:35, Steffen Rytter Postas <nc@scalehost.eu>
> wrote:
> > This may well be the point of Guix, and maybe I'm' following too
> > much
> > of a classical paradigm, but for me on a classical Linux desktop
> > system, it is much easier for me to just use _one_ version of Guix,
> > regardless of using it as my own user, or installing applications
> > as
> > root.
> You are using Guix on foreign distro, right?
> Therefore, the concept of "installing applications as root" does not
> apply any more.
> There is _one_ version of Guix, the one you use as regular user.
> And as said before, "sudo guix pull" just updates the daemon and for
> typical use-cases (not Guix developer), you can do that only each
> full
> moon. :-)

Why does the concept of installing applications as root not apply?
While I am aware that all applications are installed in the /gnu/store,
this does not imply that there are different application needs between
the root user and a normal user.

> > I'm not sure why this should _not_ work. What is the arguments
> > against
> > my use case? Is it that each user _MUST_ run `guix pull` as their
> > own
> > user and _NEVER_ use the system-wide Guix with local channels?
> There is no argument against.  You use case should work, you just
> need
> to set up correctly, with for example:
>    sudo guix pull -p /usr/
> But it is not standard for Guix.  That's why you need a bit of more
> work.
> Otherwise, yes each user runs "guix pull" as their own user and never
> uses the system-wide Guix.
> Each user specifies their own local channels.  If the sysadmin wants
> that each user pulls with a specific channels file, the easiest is to
> add a symlink from ~/.config/guix/current/channels.scm to say
> /etc/guix/channels.scm for all the users on the machine.
> On the machine, 2 users can run different Guix and so install
> different versions of the same packages.  That's why it is important
> to report the "guix describe" of the user.

So rather than being a bug in Guix itself, it's a bug in the
installation script that does not setup the host distribution for being
able to process the correct location then, no?

Or if it's because the user of Guix on a foreign distribution needs to
setup more for the use case of adding channels to work, when running
only one version of guix on the system, then it would be missing

While I don't have a say in this, I also do not mind changing this from
a bug of guix to an issue somewhere else, but where would it be? Or is
the casual user of guix that elects to simply add a channel simply left
to their own devices on undocumented behaviour?

> > I do not mind being able to by-pass any setup I've made. This is
> > for my
> > own system(s) only, but the issue happens on any non-GuixSD system
> > running Guix on a foreign distribution.
> I am not sure there is an issue but an incorrect setup. :-)
> > I am aware there may be workarounds, and currently I'm using the
> > workaround as specified in the bug report, but if this is _NOT_ a
> > bug,
> > then I shall continue to use my workaround.
> I am not convinced it is a bug.  But I can have wrong and miss
> something.
> > It does seem to me that this is indeed a bug, as Guix behaves
> > differently based upon who is executing it.
> Yes, it is expected.
> For example, I am running Guix on a Debian.
> There is:
>  - the system-wide Guix version at version f6dfe42 (4 "guix pull" and
> last on Sep 15 2020 01:42:11)
>  - user kioo at the version 1a9af96 (1 "guix pull" and last on Apr 18
> 2020 20:13:23)
>  - mine at the version 9e7b265 (44 "guix pull" and last on Sep 16
> 2020 11:28:36)
> Well, the sysadmin did "guix pull" 4 times and me I did 44 times, so
> clearly the command 'guix' behaves differently based upon who is
> executing it.
> For example, if the user kikoo run "guix install emacs" then they
> will
> install the version 26.3. and me instead wll install version 27.1,
> If I want to install the same version as the user kikoo, I can do:
>   guix pull --commit=1a9af96
>   guix install emacs
> or better:
>   guix time-machine --commit=1a9af96 -- install emacs
> The first will create another generation and my version of Guix will
> be at 1a9af96.  Which is not a good Guix practise, IMHO.
> Instead, the second creates a temporary version of Guix and use it to
> install the package emacs; without polluting my version of guix.
> Does it make sense?
> All the best,
> simon

reply via email to

[Prev in Thread] Current Thread [Next in Thread]