From: Bill Kenworthy <billk@iinet.net.au>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] syncing via via git and signature failure
Date: Sat, 7 Jul 2018 07:40:00 +0800 [thread overview]
Message-ID: <b4ea8d35-cf90-cfbb-26a8-c5e1ddbb8201@iinet.net.au> (raw)
In-Reply-To: <20180705160604.q5f2yo4ucflmnhsa@31c0.net>
On 06/07/18 00:06, Floyd Anderson wrote:
> On Wed, 04 Jul 2018 22:57:05 -0400
> John Covici <covici@ccs.covici.com> wrote:
>>
>> I got the following when running your command:
>> gemato verify -K /tmp/gentoo-release.asc.20180703 /usr/portage/
>> INFO:root:Refreshing keys from keyserver...
>> INFO:root:Keys refreshed.
>
> To be more specific, I wasn't interested in verifying the tree. My
> main goal was to get:
>
> INFO:root:Keys refreshed.
>
> because my sync/update script hung at:
>
> INFO:root:Refreshing keys from keyserver...
>
> all the time, caused by:
>
> gpg: Can't check signature: No public key
>
> result, so I wasn't able to update.
>
>> ERROR:root:Top-level Manifest not found in /usr/portage/
>>
>> How can I fix, or do I need to fix?
>
> I've no idea why your portage tree doesn't have a top-level Manifest
> file (assuming "/usr/portage" is the location of your tree), but it
> should be created/updated on next syncing.
>
>
I still have this error and Ive tried a number of things including:
gemato create -p ebuild -K /usr/share/openpgp-keys/gentoo-release.asc
/usr/portage/
next emerge --sync error-ed on a lot of private manifest files but
missing toot manifest error disappeared. Deleted them and successfully
resynced.
olympus /usr/portage # gemato verify -s -K
/usr/share/openpgp-keys/gentoo-release.asc /usr/portage/
INFO:root:Refreshing keys from keyserver...
INFO:root:Keys refreshed.
ERROR:root:Top-level Manifest /usr/portage/Manifest is not OpenPGP signed
olympus /usr/portage #
also did a "git reset --hard"
still get:
olympus /usr/portage # emerge --sync
>>> Syncing repository 'gentoo' into '/usr/portage'...
/usr/bin/git pull
Already up to date.
* Using keys from /usr/share/openpgp-keys/gentoo-release.asc
* Refreshing keys from keyserver
...
[ ok ]
* No valid signature found: unable to verify signature (missing key?)
q: Updating ebuild cache in /usr/portage ...
BillK
next prev parent reply other threads:[~2018-07-06 23:41 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
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 [this message]
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=b4ea8d35-cf90-cfbb-26a8-c5e1ddbb8201@iinet.net.au \
--to=billk@iinet.net.au \
--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