unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: dal-blazej--- via Bug reports for GNU Guix <bug-guix@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Josselin Poiret <dev@jpoiret.xyz>, 53904@debbugs.gnu.org
Subject: bug#53904: Using an http proxy, derivation failed
Date: Tue, 08 Mar 2022 20:35:55 +0100	[thread overview]
Message-ID: <878rtkz17o.fsf@onenetbeyond.org> (raw)
In-Reply-To: <87pmnvj170.fsf@onenetbeyond.org>


Hi,

Ludovic Courtès <ludo@gnu.org> writes:

>> guix pull: error: failed to connect to `/var/guix/daemon-socket/socket': Connection refused
>
> This suggests that guix-daemon is not running.  Could it be that it
> failed to start?  Does ‘journalctl -u guix-daemon.service’ contain any
> clue?
>
> BTW, according to the output you pasted earlier (in particular the noisy
> locale warnings), it seems that your daemon needs an update.  Check out
> <https://guix.gnu.org/manual/devel/en/html_node/Upgrading-Guix.html>.

Yes It needs an update but it can't. That's the issue ;)

Sorry, I think my CC error has lead to some confusion.

My last mail stated I started from scratch (new virtual machine, new
guix installation) :
- with the https_proxy defined inside the systems service file.
- with the daemon running
So please, ignore the first errors.

In this case the error seems clearly that :
$ guix pull
use git, and _guix does not pass to git the https_proxy_.

Fortunately I can update by passing the https_proxy on the command:
$ https_proxy=https://127.0.0.1:8082 guix pull

To make it clear, both the variable in the systemd service file and on
the command line are necessary to successfully run guix pull.

But as you stated it shouldn't, it still looks like a bug.




      reply	other threads:[~2022-03-08 19:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-09 19:21 bug#53904: Using an http proxy, derivation failed dal-blazej--- via Bug reports for GNU Guix
2022-02-12 11:21 ` Josselin Poiret via Bug reports for GNU Guix
2022-03-02 14:50   ` dal-blazej--- via Bug reports for GNU Guix
2022-03-08  8:42     ` Ludovic Courtès
2022-03-08 19:35       ` dal-blazej--- via Bug reports for GNU Guix [this message]

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=878rtkz17o.fsf@onenetbeyond.org \
    --to=bug-guix@gnu.org \
    --cc=53904@debbugs.gnu.org \
    --cc=dal-blazej@onenetbeyond.org \
    --cc=dev@jpoiret.xyz \
    --cc=ludo@gnu.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).