/etc/portage/repos.conf/webrsync.conf

The example below shows how the main Gentoo repository is set up using the webrsync method via the webrsync.conf file in the /etc/portage/repos.conf directory. For more information visit the Portage Sync article.

FILE /etc/portage/repos.conf/webrsync.confwebrsync example

[DEFAULT]
main-repo = gentoo

[gentoo]
location = /usr/portage
sync-type = webrsync (or websync, depending on portage version)
auto-sync = yes

Optional: Install app-arch/tarsync

The app-arch/tarsync utility enables webrsync to sync directly from tarball, skips extraction, speeds up the process.

root #emerge app-arch/tarsync

Optional: Verify releng Signature

See the Validated Gentoo repository snapshots section in the handbook. Do not forget to occasionally refresh the keys:

root #gpg --homedir /var/lib/gentoo/gkeys/keyrings/gentoo/release --refresh-keys

gpg: refreshing 4 keys from hkps://hkps.pool.sks-keyservers.net
gpg: key BB572E0E2D182910: "Gentoo Linux Release Engineering (Automated Weekly Release Key) <releng@gentoo.org>" 1 new signature
gpg: key DB6B8C1F96D8BF6D: "Gentoo Portage Snapshot Signing Key (Automated Signing Key)" 2 new signatures
gpg: key 9E6438C817072058: "Gentoo Linux Release Engineering (Gentoo Linux Release Signing Key) <releng@gentoo.org>" 1 new signature
gpg: key 825533CBF6CD6C97: "Gentoo-keys Team <gkeys@gentoo.org>" 1 new signature
gpg: key 825533CBF6CD6C97: "Gentoo-keys Team <gkeys@gentoo.org>" 1 new subkey
gpg: Total number processed: 4
gpg:            new subkeys: 1
gpg:         new signatures: 5
gpg: [don't know]: invalid packet (ctb=0a)
gpg: keyring_get_keyblock: read error: Invalid packet
gpg: keyring_get_keyblock failed: Invalid keyring
gpg: failed to rebuild keyring cache: Invalid keyring
gpg: no ultimately trusted keys found

See also

• Project:Portage/Repository_Verification —

External resources

• bug #552556 - >=sys-apps/portage-2.2.16 emaint sync ignores sync-uri from repos.d/gentoo.conf for websync/webrsync type