From: gevisz <gevisz@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] syncing via via git and signature failure
Date: Wed, 4 Jul 2018 20:57:56 +0300 [thread overview]
Message-ID: <CA+t6X7fx=M4jHwOJ54dc=JikKVaoAw+Z-iKrxeAgxW4CNftxng@mail.gmail.com> (raw)
In-Reply-To: <CAB5mfcny6vVN74UaaOuoEQnhE9cT7UoYoso=YCO3dkC6Ga=ROw@mail.gmail.com>
2018-07-04 11:55 GMT+03:00 Alex Thorne <lexiconifernelius@gmail.com>:
>>>
>> 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.
No. Gentoo maintainers just overlooked that all Gentoo signing keys expired
on July 1, and added new openpgp-keys-gentoo into portage tree only on July 2.
So, since July 1, rsync cannot verify any new portage tree and cannot download
app-crypt/openpgp-keys-gentoo-release-20180702
It was discovered in the thread
"All Gentoo signing key expired and no way to fix it"
next prev parent reply other threads:[~2018-07-04 17:58 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
2018-07-04 17:57 ` gevisz [this message]
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='CA+t6X7fx=M4jHwOJ54dc=JikKVaoAw+Z-iKrxeAgxW4CNftxng@mail.gmail.com' \
--to=gevisz@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