unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lakshmi Prasannakumar <lakshmiprasannakumaran@gmail.com>
To: boskovits@gmail.com
Cc: guix-devel@gnu.org
Subject: Re: Help required for installation of GUIX
Date: Thu, 18 Oct 2018 20:58:11 +0530	[thread overview]
Message-ID: <CA+H0LRPK3wZG9eFc5Po4zZNu8R5kyHxntTQ3an-3pBMMCFZ5hA@mail.gmail.com> (raw)
In-Reply-To: <CAE4v=piDh6FabgPGoToFtQDwbMmb9UeDOOkGk4ycSraPZ8BA0g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2083 bytes --]

Hi  Gábor,

It crashed because of my fault. After running the script, I had rerun a few
of the steps and to resolve the issue I did try to remove few of the
folders, that corrupted my system.

Thanks,

Lakshmi Prasannakumar
Bangalore


On Thu, Oct 18, 2018 at 8:38 PM Gábor Boskovits <boskovits@gmail.com> wrote:

> Hello Lakshmi,
>
> Lakshmi Prasannakumar <lakshmiprasannakumaran@gmail.com> ezt írta
> (időpont: 2018. okt. 18., Cs, 16:27):
> >
> > Hi,
> >
> > While trying to install GUIX using Binary installation, I'm getting the
> following error at verifying sig file using the below command.
> >
> > $ sudo gpg --verify guix-binary-0.15.0.x86_64-linux.tar.xz.sig
> > gpg: WARNING: unsafe ownership on homedir '/home/lakshmi/.gnupg'
> > gpg: assuming signed data in 'guix-binary-0.15.0.x86_64-linux.tar.xz'
> > gpg: Signature made Friday 06 July 2018 02:50:33 PM IST
> > gpg:                using RSA key 090B11993D9AEBB5
> > gpg: Good signature from "Ludovic Courtès <ludo@gnu.org>" [unknown]
> > gpg:                 aka "Ludovic Courtès <ludo@chbouib.org>" [unknown]
> > gpg:                 aka "Ludovic Courtès (Inria) <
> ludovic.courtes@inria.fr>" [unknown]
> > gpg: WARNING: This key is not certified with a trusted signature!
> > gpg:          There is no indication that the signature belongs to the
> owner.
> > Primary key fingerprint: 3CE4 6455 8A84 FDC6 9DB4  0CFB 090B 1199 3D9A
> EBB5
> >
>
> This is ok, you can see Good signature from...
> This means that the signature is ok, but the key is not trusted on
> your keyring, and there are also unsafe
> permissions on the ~/.gnupg directory. So you can assume this step
> went fine, please go on to the next step.
>
> > Tried downloading the public key, still getting this error. Could you
> please help ?
> > Running the .sh script had crashed my standalone ubuntu system, hence
> I'm trying to do it step by step.
> >
> How did it crash?
>
> > Thanks,
> >
> >
> > Thanks,
> >
> >
> > Lakshmi Prasannakumar
> > Bangalore
> >
> >
> g_bor
>

[-- Attachment #2: Type: text/html, Size: 4609 bytes --]

      reply	other threads:[~2018-10-18 15:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.15135.1539798656.1281.guix-devel@gnu.org>
2018-10-18  4:50 ` Help required for installation of GUIX Lakshmi Prasannakumar
2018-10-18 15:08   ` Gábor Boskovits
2018-10-18 15:28     ` Lakshmi Prasannakumar [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=CA+H0LRPK3wZG9eFc5Po4zZNu8R5kyHxntTQ3an-3pBMMCFZ5hA@mail.gmail.com \
    --to=lakshmiprasannakumaran@gmail.com \
    --cc=boskovits@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).