unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Pjotr Prins <pjotr.public12@thebird.nl>
To: Alex Vong <alexvong1995@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [Post Installation]: Unable to guix pull
Date: Sun, 4 Nov 2018 08:10:12 +0100	[thread overview]
Message-ID: <20181104071012.awpky5wvjptps7b7@thebird.nl> (raw)
In-Reply-To: <87y3a9perv.fsf@gmail.com>

For new users I think we ought to authorize and access these servers
by default. I know this was shot down before, but there really is no
reason not to. 

When you install guix you implicitely decide to trust its servers. I
know no one who does not want to install the keys.  I.e., everyone
needs the keys installed anyway.

So, why don't they just work and be part of the guix package? It is
one of these areas we could do better with little effort.

Pj.

  reply	other threads:[~2018-11-04  7:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-03 22:51 [Post Installation]: Unable to guix pull rohit yadav
2018-11-04  5:50 ` Alex Vong
2018-11-04  5:56   ` Alex Vong
2018-11-04  7:10     ` Pjotr Prins [this message]
2018-11-05 14:38       ` rohit yadav
2018-11-04  8:04 ` New detailed troubleshooting section in the manual swedebugia
2018-11-04 15:28   ` Laura Lazzati
     [not found]     ` <5b7d7e06-d76e-4c35-673c-6392fcbe9291@riseup.net>
     [not found]       ` <CAPNLzUN4MLdUF+_LzO3fSEnxxWnE48qn=qv_n0bf+TqXoNZ+_A@mail.gmail.com>
2018-11-04 19:04         ` Locale error (Was: Re: New detailed troubleshooting section in the manual) swedebugia
2018-11-04 19:14           ` Laura Lazzati
2018-11-06 11:30     ` New detailed troubleshooting section in the manual Ludovic Courtès
2018-11-08 19:52       ` Laura Lazzati
2018-11-09  6:38         ` alex sassmannshausen
2018-11-10 14:47           ` Laura Lazzati
2018-11-10 21:41             ` alex sassmannshausen

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=20181104071012.awpky5wvjptps7b7@thebird.nl \
    --to=pjotr.public12@thebird.nl \
    --cc=alexvong1995@gmail.com \
    --cc=guix-devel@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).