public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] syncing via via git and signature failure
Date: Wed, 04 Jul 2018 18:13:35 +0100	[thread overview]
Message-ID: <2169401.7bseUmWxuf@dell_xps> (raw)
In-Reply-To: <CAB5mfcny6vVN74UaaOuoEQnhE9cT7UoYoso=YCO3dkC6Ga=ROw@mail.gmail.com>

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

On Wednesday, 4 July 2018 09:55:25 BST Alex Thorne wrote:
> >> I use rsync and get the following for more than a day now;
> > 
> > !!! Manifest verification failed:
> > OpenPGP verification failed:
> > gpg: Signature made Wed 04 Jul 2018 04:08:28 AM UTC
> > gpg:                using RSA key E1D6ABB63BFCFB4BA02FDF1CEC590EEAC9189250
> > gpg: Can't check signature: No public key
> > 
> > 
> > I'm seeing this too. For me `app-crypt/gentoo-keys` is somehow no longer
> 
> installed and `/var/lib/gentoo/gkeys` is missing. I have no idea how this
> happened. Perhaps it somehow got into `emerge --depclean` and I didn't
> catch it.
> 
> Alex

I use good ol' rsync, because git creates too big a local portage for my disk 
space requirements.

I came across the same problem today, after noticing the sync was hanging for 
a few minutes at:

>>> Syncing repository 'gentoo' into '/usr/portage'...
 * Using keys from /usr/share/openpgp-keys/gentoo-release.asc
 * Refreshing keys from keyserver ...

I'm guessing it was trying to connect to a key server and failing.  Eventually 
it continued, then sync'ed with a mirror and then arrived at the same "no 
public key" error.  Having waited for 15 years to arrive at a more secure 
method of validating the portage content, the need to sort out the 
infrastructure to support this shouldn't hopefully take too long.

Are there any news how/when this problem may be overcome?
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2018-07-04 17:13 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-04  3:16 [gentoo-user] syncing via via git and signature failure Bill Kenworthy
2018-07-04  5:14 ` Adam Carter
2018-07-04  8:55   ` Alex Thorne
2018-07-04 17:13     ` Mick [this message]
2018-07-04 17:57     ` gevisz
2018-07-04 18:01       ` Mick
2018-07-04 18:32         ` gevisz
2018-07-04 22:25           ` Mick
2018-07-04 23:06             ` Floyd Anderson
2018-07-05  2:57               ` John Covici
2018-07-05 16:06                 ` Floyd Anderson
2018-07-06 23:40                   ` Bill Kenworthy
2018-07-07  1:42                     ` Floyd Anderson
2018-07-07  4:15                       ` Bill Kenworthy
2018-07-04 23:28             ` methylherd
2018-07-05  9:47             ` gevisz
2018-07-04 22:32           ` Bill Kenworthy

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=2169401.7bseUmWxuf@dell_xps \
    --to=michaelkintzios@gmail.com \
    --cc=gentoo-user@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox