bug#37347: 'guix environment' fails after trying to follow the steps from "Running Guix Before It Is Installed" page

2019-10-24 Thread Gábor Boskovits
The submitter solved the problem, and requested to close. Closing.

-- 
OpenPGP Key Fingerprint: 7988:3B9F:7D6A:4DBF:3719:0367:2506:A96C:CF63:0B21


bug#37347: 'guix environment' fails after trying to follow the steps from "Running Guix Before It Is Installed" page

2019-10-06 Thread Jan Wielkiewicz
Okay, never mind. Running "guix environment guix" instead of "guix
environment guix --pure" lets preserve the environment variables needed
for X.509 certificates to be available for git in the environment.
If that's not the correct way of doing this please let me know, but
now I'm able to run "guix refresh", so the issue can be closed.

Thank you all for suggestions.


Jan Wielkiewicz





bug#37347: 'guix environment' fails after trying to follow the steps from "Running Guix Before It Is Installed" page

2019-10-05 Thread Marius Bakke
Bengt Richter  writes:

> On +2019-10-04 09:15:56 +0200, Jelle Licht wrote:
>> Bengt Richter  writes:
>> 
>> > [snip]
>> > ...
>> > [19:40 ~/bs]$ ping guix.gnu.org
>> > ping: guix.gnu.org: Name or service not known
>> I actually have this sometimes as well. Are you on a less-than-stellar
>> WiFi-connection perhaps? I noticed the default (nscd?) configuration on
>> Guix systems caches 'negative' results for quite a while.
>> 
>> Could you try this command again after issuing:
>> `sudo herd invalidate nscd hosts'?
>> 
>> HTH!
>> - Jelle
>
> Hi Jelle, thanks for your reply.
>
> I am a grateful courtesy guest sharer of internet access in
> a small office complex via cat5 to their switches, so it should
> not be a WiFi problem.
>
> I get DNS automatically along with ip from their server dhcp,
> but I have other options I could explore.
>
> I can't try the herd command right now, as I am in strictly "foreign"
> mode at the moment.

If you are using systemd, perhaps you are hitting
?

Does it work if you create /etc/resolv.conf with a "nameserver x.x.x.x"
entry?


signature.asc
Description: PGP signature


bug#37347: 'guix environment' fails after trying to follow the steps from "Running Guix Before It Is Installed" page

2019-10-04 Thread Bengt Richter
On +2019-10-04 09:15:56 +0200, Jelle Licht wrote:
> Bengt Richter  writes:
> 
> > [snip]
> > ...
> > [19:40 ~/bs]$ ping guix.gnu.org
> > ping: guix.gnu.org: Name or service not known
> I actually have this sometimes as well. Are you on a less-than-stellar
> WiFi-connection perhaps? I noticed the default (nscd?) configuration on
> Guix systems caches 'negative' results for quite a while.
> 
> Could you try this command again after issuing:
> `sudo herd invalidate nscd hosts'?
> 
> HTH!
> - Jelle

Hi Jelle, thanks for your reply.

I am a grateful courtesy guest sharer of internet access in
a small office complex via cat5 to their switches, so it should
not be a WiFi problem.

I get DNS automatically along with ip from their server dhcp,
but I have other options I could explore.

I can't try the herd command right now, as I am in strictly "foreign"
mode at the moment.

--Ignorable note about that:
(I am busy making a ~/.my_login_ctl.d that will contain the means
to log in with and without guix profiles visible, and PATH etc set
alternately. The idea is so I can just use touch to select features
implemented as files to be sourced from ~/.my_login_ctl.d/my_login_ctl
which I'll call from ~/.bash_profile. (~/.bashrc is also modified),
and then log in and get guix and Shepherd/herd etc -- or not.

I'm hoping this will help me debug differences between plain ArchLinux
and the latter with guix binarily installed, with and w/o Shepherd/herd also.
as I don't expect my problems of /usr vs /gnu to go away for a while :-)

BTW, I don't want to define a whole different /home/me_for_alternate_mode,
I want to switch from console to console with Alt-Fx and start a new mode
at worst by touching a file or two and logging out and logging back in.)
--Ignorable note about that:--

If the ip number to guix.gnu.org is fixed and public, maybe I
could try putting it in /etc/hosts ?

If there is no objection, I'd like to try that.
TIA if posting the ip number, or explaining why not ;-)
--
Regards,
Bengt Richter





bug#37347: 'guix environment' fails after trying to follow the steps from "Running Guix Before It Is Installed" page

2019-10-04 Thread Jelle Licht
Bengt Richter  writes:

> [snip]
> ...
> [19:40 ~/bs]$ ping guix.gnu.org
> ping: guix.gnu.org: Name or service not known
I actually have this sometimes as well. Are you on a less-than-stellar
WiFi-connection perhaps? I noticed the default (nscd?) configuration on
Guix systems caches 'negative' results for quite a while.

Could you try this command again after issuing:
`sudo herd invalidate nscd hosts'?

HTH!
- Jelle





bug#37347: 'guix environment' fails after trying to follow the steps from "Running Guix Before It Is Installed" page

2019-10-03 Thread Bengt Richter
On +2019-10-03 12:57:46 -0700, Bengt Richter wrote:
> 
> I could not get to that manual url:
> https://guix.gnu.org/manual/en/html_node/X_002e509-Certificates.html
> 
> Not with with lynx, nor
[...]

> IOW, I couldn't get to the manual.
> Am I in a DNS bubble of some kind?
> 
> If the site is just bogged down busy it shouldn't 404, right?
> Nor on some auth failure -- that should be another code, right?
> 
> Doesn't gnu.org have a little broken-link scanner for its own domain?
> 
> Does no one else encounter access problems and broken links??
> 
To be clearer, the url does not 404 when lynx tries to access
the manual URL -- the 404's were from broken links in another
page (see previous in thread).
Lynx just can't find the site for
https://guix.gnu.org/manual/en/html_node/X_002e509-Certificates.html

Alert!: Unable to connect to remote host.


Looking up guix.gnu.org
Unable to locate remote host guix.gnu.org.
Alert!: Unable to connect to remote host.

lynx: Can't access startfile 
https://guix.gnu.org/manual/en/html_node/X_002e509-Certificates.html
[19:39 ~/bs]$ stack
https://guix.gnu.org/manual/en/html_node/X_002e509-Certificates.html[19:39 
~/bs]$
[19:39 ~/bs]$ stack;echo
https://guix.gnu.org/manual/en/html_node/X_002e509-Certificates.html
[19:40 ~/bs]$ ping guix.gnu.org
ping: guix.gnu.org: Name or service not known
[19:40 ~/bs]$ ping gnu.org
PING gnu.org (209.51.188.148) 56(84) bytes of data.
^C64 bytes from 209.51.188.148: icmp_seq=1 ttl=49 time=93.4 ms

--- gnu.org ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 93.404/93.404/93.404/0.000 ms
[19:40 ~/bs]$ su -c 'setterm -file lynx-attempt.txt -dump 4'

(stack is a little hack I use to append arbitrary strings
to a datafile (with lengths on a metafile) using dd to effect
push and pop etc, so I can get around not having X running
all the time (mostly not :))

TIA again for clues.
--
Regards,
Bengt Richter







bug#37347: 'guix environment' fails after trying to follow the steps from "Running Guix Before It Is Installed" page

2019-10-03 Thread Bengt Richter
On +2019-09-16 18:01:04 +0200, Ludovic Courtès wrote:
> Hi Jan,
> 
> Jan  skribis:
> 
> > guix/build/download.scm:313:6: In procedure tls-wrap:
> > X.509 certificate of 'api.github.com' could not be verified:
> >   signer-not-found
> >   invalid
> 
> It looks like X.509 certificates used to authenticate web sites over
> HTTPS could not be found.
> 
> Did you set environment variables and all as described at
> ?
> 
> HTH,
> Ludo’.
> 
> 
> 

I could not get to that manual url:
https://guix.gnu.org/manual/en/html_node/X_002e509-Certificates.html

Not with with lynx, nor
emacs M-x eww, nor
weston-launch, click for terminal, firefox --private &, paste above url

As close as I could get (in firefox, but think lynx and eww would go too):
https://www.gnu.org/manual/manual.html

Where I found: broken links in the above:
https://www.gnu.org/software/guix/manual/
https://www.gnu.org/software/guix/

IOW, I couldn't get to the manual.
Am I in a DNS bubble of some kind?

If the site is just bogged down busy it shouldn't 404, right?
Nor on some auth failure -- that should be another code, right?

Doesn't gnu.org have a little broken-link scanner for its own domain?

Does no one else encounter access problems and broken links??

TIA for clues.
--
Regards,
Bengt Richter





bug#37347: 'guix environment' fails after trying to follow the steps from "Running Guix Before It Is Installed" page

2019-10-03 Thread Jan Wielkiewicz
On Mon, 16 Sep 2019 18:01:04 +0200
Ludovic Courtès  wrote:

> It looks like X.509 certificates used to authenticate web sites over
> HTTPS could not be found.
> 
> Did you set environment variables and all as described at
> ?
> 
> HTH,
> Ludo’.

Hi again, I've tried setting these variables in the environment but the
same effect. How can I get "guix refresh" to work in the environment?
I think this should be explained somewhere a bit more, because after
reading the packaging tutorial and parts of the documentation I
couldn't set up the development environment for Guix. 
A simple step-by-step tutorial or just list of things to do would make
it more understandable.
Is this already work in progress in the Cookbook?

For example in this section:
https://guix.gnu.org/manual/en/html_node/Building-from-Git.html#Building-from-Git

It is easy to miss the last step - running "make check", because it
isn't explained that running "make check" is necessary to be able to
run ./pre-inst-env. I thought I could just skip this and start hacking.

It would be more clear if the manual or the cookbook contained a
step-by-step list like this:

Quick setting up the environment:
1. git clone ...
2. ./bootstrap
3. ./configure --localstatedir=/var/
4. make check
5. setting certificates to be able to update a package
etc.


Jan Wielkiewicz





bug#37347: 'guix environment' fails after trying to follow the steps from "Running Guix Before It Is Installed" page

2019-09-16 Thread Jan
Dnia 2019-09-16, o godz. 18:01:04
Ludovic Courtès  napisał(a):

> Hi Jan,
> 
> Jan  skribis:
> 
> > guix/build/download.scm:313:6: In procedure tls-wrap:
> > X.509 certificate of 'api.github.com' could not be verified:
> >   signer-not-found
> >   invalid
> 
> It looks like X.509 certificates used to authenticate web sites over
> HTTPS could not be found.
> 
> Did you set environment variables and all as described at
> ?
> 
> HTH,
> Ludo’.

I have nss-certs installed as a global package in my config.scm and
refreshing only doesn't work in the environment created by "guix
environmnet guix --pure" - it works without an environment. Tried
using "--ad-hoc nss-certs", but it didn't work. The manual says I have
to add certs manually if I'm an unprivileged user or running Guix on a
foreign distro, but I'm running Guix natively on my machine. Do I have
to define variables like this anyway?

---
Jan Wielkiewicz





bug#37347: 'guix environment' fails after trying to follow the steps from "Running Guix Before It Is Installed" page

2019-09-16 Thread Ludovic Courtès
Hi Jan,

Jan  skribis:

> guix/build/download.scm:313:6: In procedure tls-wrap:
> X.509 certificate of 'api.github.com' could not be verified:
>   signer-not-found
>   invalid

It looks like X.509 certificates used to authenticate web sites over
HTTPS could not be found.

Did you set environment variables and all as described at
?

HTH,
Ludo’.





bug#37347: 'guix environment' fails after trying to follow the steps from "Running Guix Before It Is Installed" page

2019-09-11 Thread Jan
> Do not run ./configure alone, always specify --localstatedir=/var
> unless you plan to run the daemon from the repo too (then it's fine
> without the option, but you won't be able to pull or you'll get into
> trouble iiuc).

Thank you all for advice, after running 
./configure --localstatedir=/var the file has been generated. Then to
be able to run Guix, I had to do "make check". Now I have Guix available
and I would like to update a package, like showed in the manual or the
tutorial, but running for example "./pre-inst-env guix refresh opendht"
throws the following error:

Backtrace:
  18 (apply-smob/1 #)
In ice-9/boot-9.scm:
705:2 17 (call-with-prompt _ _ #)
In ice-9/eval.scm:
619:8 16 (_ #(#(#)))
In guix/ui.scm:
  1692:12 15 (run-guix-command _ . _)
In ice-9/boot-9.scm:
829:9 14 (catch _ _ # ?)
829:9 13 (catch _ _ # ?)
In guix/store.scm:
   623:10 12 (call-with-store _)
  1803:24 11 (run-with-store # _ # _ ?)
In guix/scripts/refresh.scm:
   541:14 10 (_ _)
In srfi/srfi-1.scm:
640:9  9 (for-each # ?)
In guix/scripts/refresh.scm:
344:2  8 (check-for-package-update # ?)
In guix/import/github.scm:
   231:25  7 (latest-release #)
   200:22  6 (latest-released-version "https://github.com/savoirfai?; ?)
163:2  5 (fetch-releases-or-tags _)
In ice-9/boot-9.scm:
829:9  4 (catch srfi-34 # ?)
In guix/import/json.scm:
41:19  3 (_)
In guix/http-client.scm:
88:25  2 (http-fetch _ #:port _ #:text? _ #:buffered? _ # _ # _ # ?)
In guix/build/download.scm:
426:4  1 (open-connection-for-uri _ #:timeout _ # _)
313:6  0 (tls-wrap # _ # _)

guix/build/download.scm:313:6: In procedure tls-wrap:
X.509 certificate of 'api.github.com' could not be verified:
  signer-not-found
  invalid

Am I missing a dependency in my environment? Running "guix refresh"
without ./pre-inst-env and "guix environment guix --pure" works.


Jan Wielkiewicz





bug#37347: 'guix environment' fails after trying to follow the steps from "Running Guix Before It Is Installed" page

2019-09-09 Thread Julien Lepiller
Le 9 septembre 2019 03:14:05 GMT+02:00, Jesse Gibbons  
a écrit :
>On Mon, 2019-09-09 at 02:49 +0200, Jan wrote:
>> Hi, I'm a new Guix user and I wanted to hack on Guix and update a
>> package, I hadn't known exactly how to do this, so I started
>> following
>> instructions from
>> https://guix.gnu.org/manual/en/html_node/Running-Guix-Before-It-Is-In
>> stalled.html#Running-Guix-Before-It-Is-Installed
>> and
>> https://guix.gnu.org/blog/2018/a-packaging-tutorial-for-guix/
>> 
>> The situation started to be interesting, when the tutorial told me to
>> run "cd $GUIX_CHECKOUT" and "./pre-inst-env guix package
>> --list-available=ruby"
>> I was confused, because I couldn't find any "./pre-inst-env" file, so
>> I
>> used 'find' to search for it and there were one file with a similar
>> name
>> in $GUIX_CHECKOUT/build-aux - ./pre-inst-env.in (as I'm composing
>> this
>> email now I see that's stupid, but I tried using this file, as I
>> don't
>> know what I was doing (still don't know))
>> So I started running the following stupid commands:
>> 
>> 
>> user@machine ~/Prog/repo/guix [env]$ sudo -E ./pre-inst-env.in
>> guix-daemon --build-users-group=guixbuild
>> 
>> sudo: /gnu/store/z26h622slm8p61myhk45v3jjg8p7qm8z-profile/bin/sudo
>> must
>> be owned by uid 0 and have the setuid bit set 
>> 
>> user@machine ~/Prog/repo/guix [env]$ ./pre-inst-env.in
>> bash: ./pre-inst-env.in: No such file or directory 
>> user@machine ~/Prog/repo/guix [env]$ cd build-aux/ 
>> user@machine ~/Prog/repo/guix/build-aux [env]$ sudo
>> -E ./pre-inst-env.in guix-daemon --build-users-group=guixbuild
>> sudo: /gnu/store/z26h622slm8p61myhk45v3jjg8p7qm8z-profile/bin/sudo
>> must
>> be owned by uid 0 and have the setuid bit set 
>> user@machine ~/Prog/repo/guix/build-aux [env]$ exit
>> ---
>> 
>> And then:
>> 
>> --
>> user@machine ~/Prog/repo/guix/build-aux$ chmod +x ./pre-inst-env.in 
>> user@machine ~/Prog/repo/guix/build-aux$ sudo -E ./pre-inst-env.in
>> guix-daemon --build-users-group=guixbuild Password: 
>> ./pre-inst-env.in: line 33: cd: @abs_top_srcdir@:
>> there is no such file or directory 
>> ./pre-inst-env.in: line 34: cd:
>> @abs_top_builddir@: there is no such file or directory
>> 
>> 
>> And after that I couldn't run "guix
>> environment" anymore, it threw an error:
>> 
>> guix environment: error: failed to connect to
>> `/var/guix/daemon-socket/socket': Connection refused
>> 
>> Restarting the computer helps, but doing the same stuff breaks it
>> again, so guess it's reproducible.
>> 
>> After doing it I ran the "history" command so you can know what I did
>> exactly (some commands were unfortunately run in an environment and I
>> can't provide them), here it is:
>> 
>>   371  git clone --recurse-submodules
>>   git://git.savannah.gnu.org/guix.git 
>>   372  guix environment guix --pure
>>   373  sudo -E
>>   374  sudo --help
>>   375  guix environment guix --pure
>>   376  guix environment guix --pure --ad-hoc sudo 
>>   377  ls
>>   378  cd guix/
>>   379  ls
>>   380  cd build-aux/
>>   381  ls
>>   382  .
>>   383  guix environment guix --pure
>>   384  chmod +x ./pre-inst-env.in 
>>   385  sudo -E ./pre-inst-env.in guix-daemon
>>   --build-users-group=guixbuild 
>>   386  ls
>>   387  cd ..
>>   388  ./configure 
>>   389  guix environment guix --pure
>>   390  history
>> 
>> As stupid and complicated as it is, something is definitely broken
>> here.
>> 
>> Sincerely,
>> Jan Wielkiewicz
>> 
>> 
>> 
>
>pre-inst-env.in is for generating the pre-inst-env script. Have you
>tried:
>./bootstrap
>./configure
>
>This should generate pre-inst-env for you.
>
>Also, make sure the guix daemon is running after you restart.

Do not run ./configure alone, always specify --localstatedir=/var unless you 
plan to run the daemon from the repo too (then it's fine without the option, 
but you won't be able to pull or you'll get into trouble iiuc).





bug#37347: 'guix environment' fails after trying to follow the steps from "Running Guix Before It Is Installed" page

2019-09-08 Thread Jesse Gibbons
On Mon, 2019-09-09 at 02:49 +0200, Jan wrote:
> Hi, I'm a new Guix user and I wanted to hack on Guix and update a
> package, I hadn't known exactly how to do this, so I started
> following
> instructions from
> https://guix.gnu.org/manual/en/html_node/Running-Guix-Before-It-Is-In
> stalled.html#Running-Guix-Before-It-Is-Installed
> and
> https://guix.gnu.org/blog/2018/a-packaging-tutorial-for-guix/
> 
> The situation started to be interesting, when the tutorial told me to
> run "cd $GUIX_CHECKOUT" and "./pre-inst-env guix package
> --list-available=ruby"
> I was confused, because I couldn't find any "./pre-inst-env" file, so
> I
> used 'find' to search for it and there were one file with a similar
> name
> in $GUIX_CHECKOUT/build-aux - ./pre-inst-env.in (as I'm composing
> this
> email now I see that's stupid, but I tried using this file, as I
> don't
> know what I was doing (still don't know))
> So I started running the following stupid commands:
> 
> 
> user@machine ~/Prog/repo/guix [env]$ sudo -E ./pre-inst-env.in
> guix-daemon --build-users-group=guixbuild
> 
> sudo: /gnu/store/z26h622slm8p61myhk45v3jjg8p7qm8z-profile/bin/sudo
> must
> be owned by uid 0 and have the setuid bit set 
> 
> user@machine ~/Prog/repo/guix [env]$ ./pre-inst-env.in
> bash: ./pre-inst-env.in: No such file or directory 
> user@machine ~/Prog/repo/guix [env]$ cd build-aux/ 
> user@machine ~/Prog/repo/guix/build-aux [env]$ sudo
> -E ./pre-inst-env.in guix-daemon --build-users-group=guixbuild
> sudo: /gnu/store/z26h622slm8p61myhk45v3jjg8p7qm8z-profile/bin/sudo
> must
> be owned by uid 0 and have the setuid bit set 
> user@machine ~/Prog/repo/guix/build-aux [env]$ exit
> ---
> 
> And then:
> 
> --
> user@machine ~/Prog/repo/guix/build-aux$ chmod +x ./pre-inst-env.in 
> user@machine ~/Prog/repo/guix/build-aux$ sudo -E ./pre-inst-env.in
> guix-daemon --build-users-group=guixbuild Password: 
> ./pre-inst-env.in: line 33: cd: @abs_top_srcdir@:
> there is no such file or directory 
> ./pre-inst-env.in: line 34: cd:
> @abs_top_builddir@: there is no such file or directory
> 
> 
> And after that I couldn't run "guix
> environment" anymore, it threw an error:
> 
> guix environment: error: failed to connect to
> `/var/guix/daemon-socket/socket': Connection refused
> 
> Restarting the computer helps, but doing the same stuff breaks it
> again, so guess it's reproducible.
> 
> After doing it I ran the "history" command so you can know what I did
> exactly (some commands were unfortunately run in an environment and I
> can't provide them), here it is:
> 
>   371  git clone --recurse-submodules
>   git://git.savannah.gnu.org/guix.git 
>   372  guix environment guix --pure
>   373  sudo -E
>   374  sudo --help
>   375  guix environment guix --pure
>   376  guix environment guix --pure --ad-hoc sudo 
>   377  ls
>   378  cd guix/
>   379  ls
>   380  cd build-aux/
>   381  ls
>   382  .
>   383  guix environment guix --pure
>   384  chmod +x ./pre-inst-env.in 
>   385  sudo -E ./pre-inst-env.in guix-daemon
>   --build-users-group=guixbuild 
>   386  ls
>   387  cd ..
>   388  ./configure 
>   389  guix environment guix --pure
>   390  history
> 
> As stupid and complicated as it is, something is definitely broken
> here.
> 
> Sincerely,
> Jan Wielkiewicz
> 
> 
> 

pre-inst-env.in is for generating the pre-inst-env script. Have you
tried:
./bootstrap
./configure

This should generate pre-inst-env for you.

Also, make sure the guix daemon is running after you restart.





bug#37347: 'guix environment' fails after trying to follow the steps from "Running Guix Before It Is Installed" page

2019-09-08 Thread Jan
Hi, I'm a new Guix user and I wanted to hack on Guix and update a
package, I hadn't known exactly how to do this, so I started following
instructions from
https://guix.gnu.org/manual/en/html_node/Running-Guix-Before-It-Is-Installed.html#Running-Guix-Before-It-Is-Installed
and
https://guix.gnu.org/blog/2018/a-packaging-tutorial-for-guix/

The situation started to be interesting, when the tutorial told me to
run "cd $GUIX_CHECKOUT" and "./pre-inst-env guix package
--list-available=ruby"
I was confused, because I couldn't find any "./pre-inst-env" file, so I
used 'find' to search for it and there were one file with a similar name
in $GUIX_CHECKOUT/build-aux - ./pre-inst-env.in (as I'm composing this
email now I see that's stupid, but I tried using this file, as I don't
know what I was doing (still don't know))
So I started running the following stupid commands:


user@machine ~/Prog/repo/guix [env]$ sudo -E ./pre-inst-env.in
guix-daemon --build-users-group=guixbuild

sudo: /gnu/store/z26h622slm8p61myhk45v3jjg8p7qm8z-profile/bin/sudo must
be owned by uid 0 and have the setuid bit set 

user@machine ~/Prog/repo/guix [env]$ ./pre-inst-env.in
bash: ./pre-inst-env.in: No such file or directory 
user@machine ~/Prog/repo/guix [env]$ cd build-aux/ 
user@machine ~/Prog/repo/guix/build-aux [env]$ sudo
-E ./pre-inst-env.in guix-daemon --build-users-group=guixbuild
sudo: /gnu/store/z26h622slm8p61myhk45v3jjg8p7qm8z-profile/bin/sudo must
be owned by uid 0 and have the setuid bit set 
user@machine ~/Prog/repo/guix/build-aux [env]$ exit
---

And then:

--
user@machine ~/Prog/repo/guix/build-aux$ chmod +x ./pre-inst-env.in 
user@machine ~/Prog/repo/guix/build-aux$ sudo -E ./pre-inst-env.in
guix-daemon --build-users-group=guixbuild Password: 
./pre-inst-env.in: line 33: cd: @abs_top_srcdir@:
there is no such file or directory 
./pre-inst-env.in: line 34: cd:
@abs_top_builddir@: there is no such file or directory


And after that I couldn't run "guix
environment" anymore, it threw an error:

guix environment: error: failed to connect to
`/var/guix/daemon-socket/socket': Connection refused

Restarting the computer helps, but doing the same stuff breaks it
again, so guess it's reproducible.

After doing it I ran the "history" command so you can know what I did
exactly (some commands were unfortunately run in an environment and I
can't provide them), here it is:

  371  git clone --recurse-submodules
  git://git.savannah.gnu.org/guix.git 
  372  guix environment guix --pure
  373  sudo -E
  374  sudo --help
  375  guix environment guix --pure
  376  guix environment guix --pure --ad-hoc sudo 
  377  ls
  378  cd guix/
  379  ls
  380  cd build-aux/
  381  ls
  382  .
  383  guix environment guix --pure
  384  chmod +x ./pre-inst-env.in 
  385  sudo -E ./pre-inst-env.in guix-daemon
  --build-users-group=guixbuild 
  386  ls
  387  cd ..
  388  ./configure 
  389  guix environment guix --pure
  390  history

As stupid and complicated as it is, something is definitely broken
here.

Sincerely,
Jan Wielkiewicz