| 1 |
Hi Bill, |
| 2 |
|
| 3 |
On Sat, 07 Jul 2018 07:40:00 +0800 |
| 4 |
Bill Kenworthy <billk@×××××××××.au> wrote: |
| 5 |
> |
| 6 |
>I still have this error and Ive tried a number of things including: |
| 7 |
> |
| 8 |
>gemato create -p ebuild -K /usr/share/openpgp-keys/gentoo-release.asc |
| 9 |
>/usr/portage/ |
| 10 |
> |
| 11 |
>next emerge --sync error-ed on a lot of private manifest files but |
| 12 |
>missing toot manifest error disappeared. Deleted them and successfully |
| 13 |
>resynced. |
| 14 |
> |
| 15 |
>olympus /usr/portage # gemato verify -s -K |
| 16 |
>/usr/share/openpgp-keys/gentoo-release.asc /usr/portage/ |
| 17 |
>INFO:root:Refreshing keys from keyserver... |
| 18 |
>INFO:root:Keys refreshed. |
| 19 |
>ERROR:root:Top-level Manifest /usr/portage/Manifest is not OpenPGP signed |
| 20 |
>olympus /usr/portage # |
| 21 |
> |
| 22 |
>also did a "git reset --hard" |
| 23 |
> |
| 24 |
>still get: |
| 25 |
> |
| 26 |
>olympus /usr/portage # emerge --sync |
| 27 |
>>>> Syncing repository 'gentoo' into '/usr/portage'... |
| 28 |
>/usr/bin/git pull |
| 29 |
>Already up to date. |
| 30 |
> * Using keys from /usr/share/openpgp-keys/gentoo-release.asc |
| 31 |
> * Refreshing keys from keyserver |
| 32 |
>... |
| 33 |
>[ ok ] |
| 34 |
> * No valid signature found: unable to verify signature (missing key?) |
| 35 |
>q: Updating ebuild cache in /usr/portage ... |
| 36 |
|
| 37 |
please be aware of the context of my response to Mick. He use *rsync* |
| 38 |
and so do I. It seems you are using Git and thus, a different tree |
| 39 |
verification mechanism. I don't know why you have gemato installed, |
| 40 |
because it comes usually only with sys-apps/portage[rsync-verify] set |
| 41 |
and is only related to *rsync* therefore. |
| 42 |
|
| 43 |
Have a look at: |
| 44 |
|
| 45 |
- [1] <https://www.gentoo.org/glep/glep-0074.html> |
| 46 |
- [2] <https://www.gentoo.org/support/news-items/2018-01-30-portage-rsync-verification.html> |
| 47 |
- [3] <https://wiki.gentoo.org/wiki/Portage_Security> |
| 48 |
|
| 49 |
for some further information. Maybe: |
| 50 |
|
| 51 |
$ git status --untracked-files |
| 52 |
|
| 53 |
within your tree location can help to identify and sanitise the tree |
| 54 |
from any of your (with gemato) created files. |
| 55 |
|
| 56 |
|
| 57 |
-- |
| 58 |
Regards, |
| 59 |
floyd |
Archives