Hi Bill,
On Sat, 07 Jul 2018 07:40:00 +0800
Bill Kenworthy <[email protected]> wrote:
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 ...
please be aware of the context of my response to Mick. He use *rsync*
and so do I. It seems you are using Git and thus, a different tree
verification mechanism. I don't know why you have gemato installed,
because it comes usually only with sys-apps/portage[rsync-verify] set
and is only related to *rsync* therefore.
Have a look at:
- [1] <https://www.gentoo.org/glep/glep-0074.html>
- [2]
<https://www.gentoo.org/support/news-items/2018-01-30-portage-rsync-verification.html>
- [3] <https://wiki.gentoo.org/wiki/Portage_Security>
for some further information. Maybe:
$ git status --untracked-files
within your tree location can help to identify and sanitise the tree
from any of your (with gemato) created files.
--
Regards,
floyd
