Guix package manager installed

Guix package manager installed

[Gottfried]

[-- Attachment #1.1.1: Type: text/plain, Size: 982 bytes --]

Hi Guixers,

I am very thankful for all the Guixers who worked and are working for 
Guix, also for the manual...

because against all hope I was able to install the Guix package manager 
on another laptop on top of Trisquel on the basis of the manual.

I am wondering myself that I was able to understand the manual and step 
by step I did what it said.
Even sometimes there were messages of failures but at the end everything 
worked. (I had to look up for solutions  on the web several times, but 
at the end it was successful)

1.  As far as I understand it I have to do

guix pull

and a

guix package -u

but no

sudo guix system reconfigure /etc/config.scm

because there is no /etc/config.scm file

Is that right?


Where is the relevant file for the guix package manager I installed?


2.  Do I regularly have to do a "sudo guix pull" for root?

or is it enough that I did it once for setting up guix?



Kind regards

Gottfried


[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3191 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

Re: Guix package manager installed

[Ricardo Wurmus]

Hi Gottfried,

> I am very thankful for all the Guixers who worked and are working for
> Guix, also for the manual...
>
> because against all hope I was able to install the Guix package
> manager on another laptop on top of Trisquel on the basis of the
> manual.

Congratulations!

> 1.  As far as I understand it I have to do
>
> guix pull
>
> and a
>
> guix package -u
>
> but no
>
> sudo guix system reconfigure /etc/config.scm
>
> because there is no /etc/config.scm file
>
> Is that right?

Correct.  For the package manager all you need is “guix pull” and “guix
upgrade” (or “guix package -u” or “guix package -m” etc).

The configuration file at /etc/config.scm is for an operating system
declaration.  The “guix system” command deals with instances of Guix
System, the GNU+Linux distribution.  If you do not use Guix System you
don’t have any system to reconfigure.

You can still use “guix system” to build virtual machines and
containers, but “guix system reconfigure” is not useful on a “foreign
distribution”.

> Where is the relevant file for the guix package manager I installed?

The behavior of “guix pull” depends on an optional channels file, either
at /etc/guix/channels.scm or ~/.config/guix/channels.scm.  If you don’t
have either of these files Guix will use sensible defaults.

> 2.  Do I regularly have to do a "sudo guix pull" for root?
>
> or is it enough that I did it once for setting up guix?

If you actualy use Guix with the root user account then yes.

For convenience you could link your user’s “guix” so that it is the same
for the root user; then you only need to take care of running “guix
pull” for your main user account.

-- 
Ricardo

Re: Guix package manager installed

[Gottfried]

[-- Attachment #1.1.1: Type: text/plain, Size: 3168 bytes --]

Hi Ricardo,

thanks for your answer.

> The behavior of “guix pull” depends on an optional channels file, either
>> at /etc/guix/channels.scm or ~/.config/guix/channels.scm.  If you don’t
>> have either of these files Guix will use sensible defaults.

I have got:
~/.config/guix/current/ a bin etc lib and share folder and a manifest file
Are those the default?

I don't have a channel file or a manifest, because I don't know yet how 
to set it up, and what are the advantages for me at the moment to do 
that. In future, when I understand the advantages to do that, I can set 
them up.

> Do I regularly have to do a "sudo guix pull" for root?
>>>
>>> or is it enough that I did it once for setting up guix?
>> 
>> If you actualy use Guix with the root user account then yes.

What would be the benefit to use Guix with the root user account?


> For convenience you could link your user’s “guix” so that it is the same
>> for the root user; then you only need to take care of running “guix
>> pull” for your main user account.

How can set up a link from my user "guix" to the root user?

I guess this is also useful for my other laptop, where I have Guix 
system installed.

  Kind regards

Gottfried


Am 30.10.22 um 00:23 schrieb Ricardo Wurmus:
> 
> Hi Gottfried,
> 
>> I am very thankful for all the Guixers who worked and are working for
>> Guix, also for the manual...
>>
>> because against all hope I was able to install the Guix package
>> manager on another laptop on top of Trisquel on the basis of the
>> manual.
> 
> Congratulations!
> 
>> 1.  As far as I understand it I have to do
>>
>> guix pull
>>
>> and a
>>
>> guix package -u
>>
>> but no
>>
>> sudo guix system reconfigure /etc/config.scm
>>
>> because there is no /etc/config.scm file
>>
>> Is that right?
> 
> Correct.  For the package manager all you need is “guix pull” and “guix
> upgrade” (or “guix package -u” or “guix package -m” etc).
> 
> The configuration file at /etc/config.scm is for an operating system
> declaration.  The “guix system” command deals with instances of Guix
> System, the GNU+Linux distribution.  If you do not use Guix System you
> don’t have any system to reconfigure.
> 
> You can still use “guix system” to build virtual machines and
> containers, but “guix system reconfigure” is not useful on a “foreign
> distribution”.
> 
>> Where is the relevant file for the guix package manager I installed?
> 
> The behavior of “guix pull” depends on an optional channels file, either
> at /etc/guix/channels.scm or ~/.config/guix/channels.scm.  If you don’t
> have either of these files Guix will use sensible defaults.
> 
>> 2.  Do I regularly have to do a "sudo guix pull" for root?
>>
>> or is it enough that I did it once for setting up guix?
> 
> If you actualy use Guix with the root user account then yes.
> 
> For convenience you could link your user’s “guix” so that it is the same
> for the root user; then you only need to take care of running “guix
> pull” for your main user account.
> 



[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3191 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

Re: Guix package manager installed

[Felix Lechner via]

Hi,

On Sun, Oct 30, 2022 at 2:13 AM Gottfried <gottfried@posteo.de> wrote:
>
> What would be the benefit to use Guix with the root user account?

Using Guix with the root user account would give you access to
executables managed by Guix while you are logged in as root.

If you have root privileges, however, you could also say good-bye to
your host OS and switch to the Guix System.

Kind regards
Felix Lechner

Re: Guix package manager installed

[Steve George]

Hi,

The key concept to understand is that Guix runs a build daemon and 
package database (/gnu/store) on the machine which multiple 'normal' 
users can use. You can see it with:

   sudo systemctl status guix-daemon.service

The manual is trying to explain that you use the root user to update the 
guix daemon itself. So you do this:

   sudo -i pull guix
   sudo systemctl restart guix-daemon.service

The second step is that for each of your normal users, you then use 
guix. For example, to update guix for my main user and to install a package:

   # open a normal terminal
   $ guix pull
   $ guix upgrade
   $ guix install tmux

If you inspect the guix-daemon service the log will show your user 
connecting to the service and the guix-daemon handling the actions (e.g. 
download the software):

   sudo systemctl status guix-daemon.service

If you had multiple users then each individual user would do guix pull 
to update their definitions of what applications/versions are available. 
Each user has their own record (called a profile) of which applications 
they've installed.

The advantage of using the single daemon, is that if multiple users 
installed a program (e.g. tmux) then it would only be downloaded once.

Unless you use your root user regularly you don't need to install 
applications as the root user. I personally only run a small number of 
commands as root so I don't install any Guix software as root.

Hope that makes it easier to understand!


On 29/10/2022 21:57, Gottfried wrote:
> Hi Guixers,
> 
> I am very thankful for all the Guixers who worked and are working for 
> Guix, also for the manual...
> 
> because against all hope I was able to install the Guix package manager 
> on another laptop on top of Trisquel on the basis of the manual.
> 
> I am wondering myself that I was able to understand the manual and step 
> by step I did what it said.
> Even sometimes there were messages of failures but at the end everything 
> worked. (I had to look up for solutions  on the web several times, but 
> at the end it was successful)
> 
> 1.  As far as I understand it I have to do
> 
> guix pull
> 
> and a
> 
> guix package -u
> 
> but no
> 
> sudo guix system reconfigure /etc/config.scm
> 
> because there is no /etc/config.scm file
> 
> Is that right?
> 
> 
> Where is the relevant file for the guix package manager I installed?
> 
> 
> 2.  Do I regularly have to do a "sudo guix pull" for root?
> 
> or is it enough that I did it once for setting up guix?
> 
> 
> 
> Kind regards
> 
> Gottfried
> 

Re: Guix package manager installed

[Gottfried]

[-- Attachment #1.1.1: Type: text/plain, Size: 3112 bytes --]

  Hi Steve,

thanks for explanation
I am hacking on the basics.


I tried:

sudo systemctl status guix-daemon.service

but it said:

gfp@Tuxedo ~$ sudo systemctl status guix-daemon.service
Password:
sudo: systemctl: command not found

systemctl ?

Kind regards

Gottfried



Am 02.11.22 um 08:53 schrieb Steve George:
> Hi,
> 
> The key concept to understand is that Guix runs a build daemon and 
> package database (/gnu/store) on the machine which multiple 'normal' 
> users can use. You can see it with:
> 
>    sudo systemctl status guix-daemon.service
> 
> The manual is trying to explain that you use the root user to update the 
> guix daemon itself. So you do this:
> 
>    sudo -i pull guix
>    sudo systemctl restart guix-daemon.service
> 
> The second step is that for each of your normal users, you then use 
> guix. For example, to update guix for my main user and to install a 
> package:
> 
>    # open a normal terminal
>    $ guix pull
>    $ guix upgrade
>    $ guix install tmux
> 
> If you inspect the guix-daemon service the log will show your user 
> connecting to the service and the guix-daemon handling the actions (e.g. 
> download the software):
> 
>    sudo systemctl status guix-daemon.service
> 
> If you had multiple users then each individual user would do guix pull 
> to update their definitions of what applications/versions are available. 
> Each user has their own record (called a profile) of which applications 
> they've installed.
> 
> The advantage of using the single daemon, is that if multiple users 
> installed a program (e.g. tmux) then it would only be downloaded once.
> 
> Unless you use your root user regularly you don't need to install 
> applications as the root user. I personally only run a small number of 
> commands as root so I don't install any Guix software as root.
> 
> Hope that makes it easier to understand!
> 
> 
> On 29/10/2022 21:57, Gottfried wrote:
>> Hi Guixers,
>>
>> I am very thankful for all the Guixers who worked and are working for 
>> Guix, also for the manual...
>>
>> because against all hope I was able to install the Guix package 
>> manager on another laptop on top of Trisquel on the basis of the manual.
>>
>> I am wondering myself that I was able to understand the manual and 
>> step by step I did what it said.
>> Even sometimes there were messages of failures but at the end 
>> everything worked. (I had to look up for solutions  on the web several 
>> times, but at the end it was successful)
>>
>> 1.  As far as I understand it I have to do
>>
>> guix pull
>>
>> and a
>>
>> guix package -u
>>
>> but no
>>
>> sudo guix system reconfigure /etc/config.scm
>>
>> because there is no /etc/config.scm file
>>
>> Is that right?
>>
>>
>> Where is the relevant file for the guix package manager I installed?
>>
>>
>> 2.  Do I regularly have to do a "sudo guix pull" for root?
>>
>> or is it enough that I did it once for setting up guix?
>>
>>
>>
>> Kind regards
>>
>> Gottfried
>>
> 

-- 



[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3191 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

Re: Guix package manager installed

[Steve George]

Hi Gottfried,

In an earlier email you said you're running Trisequel: so you have Guix 
installed as a package manager on top of it.

That means when you installed Guix package manager your distributions 
'service manager' was used to install the Guix daemon.

As Trisequel is an Ubuntu derivative [0] I assumed it was running 
Systemd to manage services. Systemd uses the systemctl command: so you 
should be able to run that command as root.

I don't know enough about Trisequel to help you figure out which service 
manager you're running. You'll need to ask on the Trisequel forums for 
help on which service manager you have.

You can try doing some research on service managers and systemd - the 
Arch Wiki has good links [1]

Best of luck!


[0] https://en.wikipedia.org/wiki/Trisquel
[1] https://wiki.archlinux.org/title/Init#Service_managers and 
https://wiki.archlinux.org/title/Systemd



On 02/11/2022 19:59, Gottfried wrote:
>   Hi Steve,
> 
> thanks for explanation
> I am hacking on the basics.
> 
> 
> I tried:
> 
> sudo systemctl status guix-daemon.service
> 
> but it said:
> 
> gfp@Tuxedo ~$ sudo systemctl status guix-daemon.service
> Password:
> sudo: systemctl: command not found
> 
> systemctl ?
> 
> Kind regards
> 
> Gottfried
> 
> 
> 
> Am 02.11.22 um 08:53 schrieb Steve George:
>> Hi,
>>
>> The key concept to understand is that Guix runs a build daemon and 
>> package database (/gnu/store) on the machine which multiple 'normal' 
>> users can use. You can see it with:
>>
>>    sudo systemctl status guix-daemon.service
>>
>> The manual is trying to explain that you use the root user to update 
>> the guix daemon itself. So you do this:
>>
>>    sudo -i pull guix
>>    sudo systemctl restart guix-daemon.service
>>
>> The second step is that for each of your normal users, you then use 
>> guix. For example, to update guix for my main user and to install a 
>> package:
>>
>>    # open a normal terminal
>>    $ guix pull
>>    $ guix upgrade
>>    $ guix install tmux
>>
>> If you inspect the guix-daemon service the log will show your user 
>> connecting to the service and the guix-daemon handling the actions 
>> (e.g. download the software):
>>
>>    sudo systemctl status guix-daemon.service
>>
>> If you had multiple users then each individual user would do guix pull 
>> to update their definitions of what applications/versions are 
>> available. Each user has their own record (called a profile) of which 
>> applications they've installed.
>>
>> The advantage of using the single daemon, is that if multiple users 
>> installed a program (e.g. tmux) then it would only be downloaded once.
>>
>> Unless you use your root user regularly you don't need to install 
>> applications as the root user. I personally only run a small number of 
>> commands as root so I don't install any Guix software as root.
>>
>> Hope that makes it easier to understand!
>>
>>
>> On 29/10/2022 21:57, Gottfried wrote:
>>> Hi Guixers,
>>>
>>> I am very thankful for all the Guixers who worked and are working for 
>>> Guix, also for the manual...
>>>
>>> because against all hope I was able to install the Guix package 
>>> manager on another laptop on top of Trisquel on the basis of the manual.
>>>
>>> I am wondering myself that I was able to understand the manual and 
>>> step by step I did what it said.
>>> Even sometimes there were messages of failures but at the end 
>>> everything worked. (I had to look up for solutions  on the web 
>>> several times, but at the end it was successful)
>>>
>>> 1.  As far as I understand it I have to do
>>>
>>> guix pull
>>>
>>> and a
>>>
>>> guix package -u
>>>
>>> but no
>>>
>>> sudo guix system reconfigure /etc/config.scm
>>>
>>> because there is no /etc/config.scm file
>>>
>>> Is that right?
>>>
>>>
>>> Where is the relevant file for the guix package manager I installed?
>>>
>>>
>>> 2.  Do I regularly have to do a "sudo guix pull" for root?
>>>
>>> or is it enough that I did it once for setting up guix?
>>>
>>>
>>>
>>> Kind regards
>>>
>>> Gottfried
>>>
>>
> 

Re: Guix package manager installed

[Gottfried]

[-- Attachment #1.1.1: Type: text/plain, Size: 5105 bytes --]

Hi Steve,

thanks for your endeavouring.

I am sorry, I made a mistake.

I worked at the laptop with Guix system and tried:
sudo systemctl status guix-daemon.service
and it didn't work.

Today I tried it with the other laptop with Trisquel and Guix Package 
Manager installed and it worked of course.

2.

> The manual is trying to explain that you use the root user to update 
>>>> the guix daemon itself. So you do this:
>>>>
>>>>    sudo -i pull guix
>>>>    sudo systemctl restart guix-daemon.service

I did: sudo -i to log in as root
than: "pull guix"
but this doesn't work.
Probably you meant: "guix pull"


Kind regards

Gottfried




Am 03.11.22 um 08:25 schrieb Steve George:
> Hi Gottfried,
> 
> In an earlier email you said you're running Trisequel: so you have Guix 
> installed as a package manager on top of it.
> 
> That means when you installed Guix package manager your distributions 
> 'service manager' was used to install the Guix daemon.
> 
> As Trisequel is an Ubuntu derivative [0] I assumed it was running 
> Systemd to manage services. Systemd uses the systemctl command: so you 
> should be able to run that command as root.
> 
> I don't know enough about Trisequel to help you figure out which service 
> manager you're running. You'll need to ask on the Trisequel forums for 
> help on which service manager you have.
> 
> You can try doing some research on service managers and systemd - the 
> Arch Wiki has good links [1]
> 
> Best of luck!
> 
> 
> [0] https://en.wikipedia.org/wiki/Trisquel
> [1] https://wiki.archlinux.org/title/Init#Service_managers and 
> https://wiki.archlinux.org/title/Systemd
> 
> 
> 
> On 02/11/2022 19:59, Gottfried wrote:
>>   Hi Steve,
>>
>> thanks for explanation
>> I am hacking on the basics.
>>
>>
>> I tried:
>>
>> sudo systemctl status guix-daemon.service
>>
>> but it said:
>>
>> gfp@Tuxedo ~$ sudo systemctl status guix-daemon.service
>> Password:
>> sudo: systemctl: command not found
>>
>> systemctl ?
>>
>> Kind regards
>>
>> Gottfried
>>
>>
>>
>> Am 02.11.22 um 08:53 schrieb Steve George:
>>> Hi,
>>>
>>> The key concept to understand is that Guix runs a build daemon and 
>>> package database (/gnu/store) on the machine which multiple 'normal' 
>>> users can use. You can see it with:
>>>
>>>    sudo systemctl status guix-daemon.service
>>>
>>> The manual is trying to explain that you use the root user to update 
>>> the guix daemon itself. So you do this:
>>>
>>>    sudo -i pull guix
>>>    sudo systemctl restart guix-daemon.service
>>>
>>> The second step is that for each of your normal users, you then use 
>>> guix. For example, to update guix for my main user and to install a 
>>> package:
>>>
>>>    # open a normal terminal
>>>    $ guix pull
>>>    $ guix upgrade
>>>    $ guix install tmux
>>>
>>> If you inspect the guix-daemon service the log will show your user 
>>> connecting to the service and the guix-daemon handling the actions 
>>> (e.g. download the software):
>>>
>>>    sudo systemctl status guix-daemon.service
>>>
>>> If you had multiple users then each individual user would do guix 
>>> pull to update their definitions of what applications/versions are 
>>> available. Each user has their own record (called a profile) of which 
>>> applications they've installed.
>>>
>>> The advantage of using the single daemon, is that if multiple users 
>>> installed a program (e.g. tmux) then it would only be downloaded once.
>>>
>>> Unless you use your root user regularly you don't need to install 
>>> applications as the root user. I personally only run a small number 
>>> of commands as root so I don't install any Guix software as root.
>>>
>>> Hope that makes it easier to understand!
>>>
>>>
>>> On 29/10/2022 21:57, Gottfried wrote:
>>>> Hi Guixers,
>>>>
>>>> I am very thankful for all the Guixers who worked and are working 
>>>> for Guix, also for the manual...
>>>>
>>>> because against all hope I was able to install the Guix package 
>>>> manager on another laptop on top of Trisquel on the basis of the 
>>>> manual.
>>>>
>>>> I am wondering myself that I was able to understand the manual and 
>>>> step by step I did what it said.
>>>> Even sometimes there were messages of failures but at the end 
>>>> everything worked. (I had to look up for solutions  on the web 
>>>> several times, but at the end it was successful)
>>>>
>>>> 1.  As far as I understand it I have to do
>>>>
>>>> guix pull
>>>>
>>>> and a
>>>>
>>>> guix package -u
>>>>
>>>> but no
>>>>
>>>> sudo guix system reconfigure /etc/config.scm
>>>>
>>>> because there is no /etc/config.scm file
>>>>
>>>> Is that right?
>>>>
>>>>
>>>> Where is the relevant file for the guix package manager I installed?
>>>>
>>>>
>>>> 2.  Do I regularly have to do a "sudo guix pull" for root?
>>>>
>>>> or is it enough that I did it once for setting up guix?
>>>>
>>>>
>>>>
>>>> Kind regards
>>>>
>>>> Gottfried
>>>>
>>>
>>
> 




[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3191 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]