| 1 |
On 19-02-22 22:19:54, Rich Freeman wrote: |
| 2 |
> On Fri, Feb 22, 2019 at 9:58 PM Matthew Thode <prometheanfire@g.o> wrote: |
| 3 |
> > |
| 4 |
> > Ok, after setting that up portage wants to update pgp keys, which fail |
| 5 |
> > because keyservers suck. It doesn't look like we can change the |
| 6 |
> > keyservers or disable the update entirely but we can set the retries to |
| 7 |
> > 0 (which better disable it...). Robbat2 had a patch to allow disabling |
| 8 |
> > the update but it doesn't look like it was applied. |
| 9 |
> |
| 10 |
> I assume that it proceeds after some timeout? Or does it completely |
| 11 |
> bail? IMO failing successful makes more sense though it is less |
| 12 |
> secure. |
| 13 |
> |
| 14 |
> It definitely makes sense to attempt a keyserver update since that is |
| 15 |
> going to be the mechanism to catch key revocations. It also will make |
| 16 |
> life easier on users using an older stage3 that happens to have |
| 17 |
> expired keys. Well, assuming the keyserver works... |
| 18 |
> |
| 19 |
|
| 20 |
Na, times out the build (1.5 hour gate time...). It retried nine |
| 21 |
times... I agree that updating is best, but nine times? |
| 22 |
|
| 23 |
http://logs.openstack.org/02/608102/12/check/openstack-ansible-functional-gentoo-17-0-systemd/f866472/logs/host/lxc-cache-prep-commands.log.txt.gz |
| 24 |
|
| 25 |
-- |
| 26 |
Matthew Thode (prometheanfire) |
Archives