Hi all, In tracing down problems with the git->rsync path, it has been noticed that some developers have significant clock drift on their local systems (up to one case of 14 days wrong), and it's potentially contributing to problems in generating the rsync tree.
I have implemented a check as part of the hook that validates Git push certificates (require-signed-push). It looks for clock drift or an overly long push, and aborts if needed. The tolerances are presently set to: - 5 seconds of clock drift. - 'git push' must be completed in 60 seconds. The two possible errors you will get during push are: === Your system clock is off by 119 seconds (limit 5). Run NTP, rebase your commits as needed, and push again. === Try again! Your push took 80 seconds (limit 60). === If you do get the first error, please strongly look at running ntpd, tlsdate or some other time keeping solution. This applies to all Git repos that require signed pushes presently: - data/* - foundation/* - infra/* - proj/portage - repo/gentoo - repo/proj/gen-b0rk (and a few more) -- Robin Hugh Johnson Gentoo Linux: Dev, Infra Lead, Foundation Trustee & Treasurer E-Mail : robb...@gentoo.org GnuPG FP : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85 GnuPG FP : 7D0B3CEB E9B85B1F 825BCECF EE05E6F6 A48F6136
signature.asc
Description: Digital signature
