1 |
Hi all, |
2 |
|
3 |
In tracing down problems with the git->rsync path, it has been noticed |
4 |
that some developers have significant clock drift on their local systems |
5 |
(up to one case of 14 days wrong), and it's potentially contributing to |
6 |
problems in generating the rsync tree. |
7 |
|
8 |
I have implemented a check as part of the hook that validates Git push |
9 |
certificates (require-signed-push). It looks for clock drift or an |
10 |
overly long push, and aborts if needed. |
11 |
|
12 |
The tolerances are presently set to: |
13 |
- 5 seconds of clock drift. |
14 |
- 'git push' must be completed in 60 seconds. |
15 |
|
16 |
The two possible errors you will get during push are: |
17 |
=== |
18 |
Your system clock is off by 119 seconds (limit 5). |
19 |
Run NTP, rebase your commits as needed, and push again. |
20 |
=== |
21 |
Try again! Your push took 80 seconds (limit 60). |
22 |
=== |
23 |
|
24 |
If you do get the first error, please strongly look at running ntpd, |
25 |
tlsdate or some other time keeping solution. |
26 |
|
27 |
This applies to all Git repos that require signed pushes presently: |
28 |
- data/* |
29 |
- foundation/* |
30 |
- infra/* |
31 |
- proj/portage |
32 |
- repo/gentoo |
33 |
- repo/proj/gen-b0rk |
34 |
(and a few more) |
35 |
|
36 |
-- |
37 |
Robin Hugh Johnson |
38 |
Gentoo Linux: Dev, Infra Lead, Foundation Trustee & Treasurer |
39 |
E-Mail : robbat2@g.o |
40 |
GnuPG FP : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85 |
41 |
GnuPG FP : 7D0B3CEB E9B85B1F 825BCECF EE05E6F6 A48F6136 |