Re: Cloning errors

[Tait <gnu...@t4...>]

Curious; I don't get that error. What version of git are you
using, on what OS?

Cloning into 'gnuplot-main'...
remote: Enumerating objects: 86573, done.
remote: Counting objects: 100% (86573/86573), done.
remote: Compressing objects: 100% (18752/18752), done.
remote: Total 86573 (delta 70470), reused 83123 (delta 67685)
Receiving objects: 100% (86573/86573), 24.98 MiB | 8.77 MiB/s, done.
Resolving deltas: 100% (70470/70470), done.

But that said, the referenced commit does clearly have an
invalid date:
  tree 31bef65a8811b246449435d6334cd03b80364528
  parent 8d0b9267c9f623c99a2f949652180e2e07845847
  author Timothee Lecomte <tim...@en...> 7465328412 +0200
  committer Timothee Lecomte <tim...@en...> 1154067612 +0200
  
  Reword the warning about problems with piping /dev/null with mouse support...
  
  ...to reflect 4.2 behaviour.

If I've calculated correctly, 7465328412 would be about July,
2206. In any case, it and others (like 3cc23982) are part of
history now, so I can't understand why git doesn't warn by
default instead of treating it as fatal.

I'm guessing this only affects old versions. There was a config
option to turn it down to a warning, which I assume would let
you clone successfully:
  https://github.com/c3e/grundgesetz-dev/issues/28


Colin Baxter <m4...@ya...> said (on 2020/06/25):
> Hello,
> 
> Git cloning https://git.code.sf.net/p/gnuplot/.... fails with
> 
> remote: Compressing objects: 100% (18752/18752), done.        
> error: object f20ad5ffaa212876da3efb6a9a6f1ea3f8082734: badDateOverflow: invalid author/committer line - date causes integer overflow
> fatal: Error in object
> fatal: index-pack failed
> 
> Best wishes,
> 
> 
> Colin Baxter