| 1 |
On Thursday, 5 July 2018 23:05:51 BST Grant Edwards wrote: |
| 2 |
> On 2018-07-05, Grant Edwards <grant.b.edwards@×××××.com> wrote: |
| 3 |
> > On 2018-07-05, Grant Edwards <grant.b.edwards@×××××.com> wrote: |
| 4 |
> >> On 2018-07-05, Grant Edwards <grant.b.edwards@×××××.com> wrote: |
| 5 |
> >>> As of today, I seem to be unable to a an "emerge --sync". |
| 6 |
> >> |
| 7 |
> >>> The process either hangs forever at the "Refreshing keys from keyserver |
| 8 |
step: |
| 9 |
> >> [...] |
| 10 |
> >> |
| 11 |
> >>> Or, it fails because there are no public key to verify a manfest: |
| 12 |
> >> For now, I've had to set add "sync-rsync-verify-metamanifest = no" to |
| 13 |
> >> my repo conf file so that I can actually do updates, but that seems |
| 14 |
> >> like a dangerous work-around. |
| 15 |
> > |
| 16 |
> > After turning off sync-rsync-verify-metamanifest and doing a sync and |
| 17 |
> > update (which included app-crypt/openpgp-keys-gentoo-release-20180703), |
| 18 |
> > |
| 19 |
> > I had hoped that I would be able to turn it back on, but now I get this: |
| 20 |
> > # emerge --sync |
| 21 |
> > |
| 22 |
> > >>> Syncing repository 'gentoo' into '/usr/portage'... |
| 23 |
> > |
| 24 |
> > * Using keys from /usr/share/openpgp-keys/gentoo-release.asc |
| 25 |
> > |
| 26 |
> > * Refreshing keys from keyserver ...OpenPGP keyring refresh failed: |
| 27 |
> > gpg: refreshing 4 keys from hkps://hkps.pool.sks-keyservers.net |
| 28 |
> > gpg: keyserver refresh failed: General error |
| 29 |
> > |
| 30 |
> > OpenPGP keyring refresh failed: |
| 31 |
> > gpg: refreshing 4 keys from hkps://hkps.pool.sks-keyservers.net |
| 32 |
> > gpg: keyserver refresh failed: General error |
| 33 |
> > |
| 34 |
> > OpenPGP keyring refresh failed: |
| 35 |
> > gpg: refreshing 4 keys from hkps://hkps.pool.sks-keyservers.net |
| 36 |
> > gpg: keyserver refresh failed: General error |
| 37 |
> > |
| 38 |
> > The last four lines repeat forever with an increasingly longer period. |
| 39 |
> |
| 40 |
> I never did figure what was causing the "General error". After about |
| 41 |
> an hour of googling and reading descriptions of unrelated problems, it |
| 42 |
> just started working with no changes to any configuration. Apparently |
| 43 |
> a server issue? |
| 44 |
|
| 45 |
It could be a congestion issue. I have noticed the same with different key |
| 46 |
servers at times. |
| 47 |
-- |
| 48 |
Regards, |
| 49 |
Mick |
Archives