Sargastic
n00b
Joined: 28 Aug 2011
Posts: 58
|
 Posted: Wed Jun 13, 2018 12:14 pm Post subject: Key refresh and authenticating proxy |
 |
|
Hello,
We are behind an authenticating proxy for web browsing and the like. The make.conf file contains the proper http_proxy and https_proxy variables definitions, so sources and patches downloading has been working for several years.
With the new 'tree verify' feature (using portage 2.3.24-r1), the portage tree sync always fails, the key refresh ending on timeout.
| Code: |
$ eix-sync
* Running emerge --sync
>>> Syncing repository 'gentoo' into '/usr/portage'...
* Using keys from /usr/share/openpgp-keys/gentoo-release.asc
* Refreshing keys from keyserver ...OpenPGP keyring refresh failed:
gpg: refreshing 4 keys from hkps://hkps.pool.sks-keyservers.net
gpg: keyserver refresh failed: Connection timed out
[... several failures ...]
!!! Manifest verification impossible due to keyring problem:
OpenPGP keyring refresh failed:
gpg: refreshing 4 keys from hkps://hkps.pool.sks-keyservers.net
gpg: keyserver refresh failed: Connection timed out
q: Updating ebuild cache in /usr/portage ...
q: Finished 36643 entries in 0.127503 seconds
* emerge --sync failed
|
If, before running eix-sync, we manually define/export http_proxy and https_proxy variables, the key test/refresh works and eix-sync does its job.
Are there some config variables to add « somewhere » for proper key test/refresh through an authenticating proxy, or should we open a bug ? |
|
Portage & Programming
