Project Talk:Portage/Repository verification
From Gentoo Wiki
Note
This is a Talk page - please see the documentation about using talk pages. Add newer comments below older ones, sign comments using four tildes (
This is a Talk page - please see the documentation about using talk pages. Add newer comments below older ones, sign comments using four tildes (
~~~~), and indent successive comments with colons (:).
Add new sections at the bottom of the page, under a heading (== ==). Please remember to mark sections as "open for discussion" using {{talk|open}}, so they will show up in the list of open discussions.Keys package incorrect
Talk status
This discussion is done.
>In order for verification work correctly, the user has to have an up-to-date Infrastructure OpenPGP public key installed. Currently, this is done through the app-crypt/gentoo-keys package. The key has a yearly expiration date, therefore the user needs to sync and upgrade the package before the previous key expires.
Is this still "current"? As of portage-2.3.40-r1, I don't have gentoo-keys installed, yet verification is working:
* Running emerge --sync >>> Syncing repository 'gentoo' into '/usr/portage'... * Using keys from /usr/share/openpgp-keys/gentoo-release.asc * Refreshing keys from keyserver ... [ ok ] >>> Starting rsync with rsync://88.198.69.178/gentoo-portage...
$ equery b /usr/share/openpgp-keys/gentoo-release.asc
* Searching for /usr/share/openpgp-keys/gentoo-release.asc ...app-crypt/openpgp-keys-gentoo-release-20180530 (/usr/share/openpgp-keys/gentoo-release.asc)
— The preceding unsigned comment was added by Thinrope (talk • contribs)
Table outdated?
Talk status
This discussion is still ongoing.
My impression is that the information in the table is outdated. See git-mirror_repositories.