all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Arun Isaac <arunisaac@systemreboot.net>
To: help-guix <help-guix@gnu.org>
Subject: Re: Packaging packages with GPG signed source archives
Date: Thu, 01 Sep 2016 00:07:56 +0530	[thread overview]
Message-ID: <cu7k2ewpywr.fsf@systemreboot.net> (raw)
In-Reply-To: <20160831172204.GB28096@jasmine>

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


> Does Parabola have some sort of keyring that all the upstream keys go
> into? Or did I misinterpret your suggestion? I'm not familiar with the
> Parabola package management system.

No, Parabola does not collect upstream keys into any centralized keyring.

When you are building a package from source, the Parabola build system
verifies the GPG signature of the source archive if the developer's key
is in your keyring. Else, it raises an error and asks you to get the
required key manually. There is also an option that tells the build
system to automatically fetch the key if it is not in your keyring.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 472 bytes --]

  reply	other threads:[~2016-08-31 18:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-31  5:37 Packaging packages with GPG signed source archives Arun Isaac
2016-08-31  7:33 ` Alex Kost
2016-08-31  7:47   ` Arun Isaac
2016-08-31 10:00     ` ng0
2016-08-31 17:22     ` Leo Famulari
2016-08-31 18:37       ` Arun Isaac [this message]
2016-08-31 20:21         ` Ludovic Courtès
2016-08-31 20:42           ` Troy Sankey
2016-09-01  8:29             ` Ludovic Courtès
2016-08-31 21:53           ` ng0
2016-09-01  8:30             ` Ludovic Courtès
2016-09-02 10:10               ` ng0
2016-09-02 12:14                 ` Ludovic Courtès
2016-09-02 12:46                   ` ng0

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cu7k2ewpywr.fsf@systemreboot.net \
    --to=arunisaac@systemreboot.net \
    --cc=help-guix@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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.