Project

General

Profile

Actions
Copy link

Bug #2046

open

Git clone doesn't keep original modification time of files

Added by Evgeny Novikov almost 13 years ago. Updated almost 13 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Infrastructure
Start date:
11/30/2011
Due date:
% Done:

0%

Estimated time:
Detected in build:
svn
Platform:
Published in build:

Description

When somebody does git clone of ldv-tools he or she obtains files having modification time in accordance with a current system time stamp like this:

...
drwxr-xr-x  3 joker users  4096 2011-11-30 11:38:56.030799526 +0400 rule-instrumentor
drwxr-xr-x  6 joker users  4096 2011-11-30 11:39:00.114675132 +0400 shared
drwxr-xr-x  5 joker users  4096 2011-11-30 11:39:00.118674491 +0400 stats-visualizer
-rw-r--r--  1 joker users  6835 2011-11-30 11:38:43.906799859 +0400 TUTORIAL
...

But sometimes it leads to strange consequences. For instance, QA encounters the situation when configure.in has a newer modification time that configure:
-rwxrwxr-x  1 qarobot qa 185916 2011-11-30 00:01:44.999833120 +0300 configure
-rw-rw-r--  1 qarobot qa  17718 2011-11-30 00:01:45.000945873 +0300 configure.in

that leads to the following error:
configure: error: configure is older than configure.in; you forgot to run autoconf
make[4]: *** [compile-cil] Error 1
make[4]: Leaving directory `/all/qaserver-work/build/master-2011-11-30/dscv/rcv/backends/blast/blast'

I suggest that the correct solution is to find out how to preserve original modification time of files in git cloning (not pulling and so on because of see "Why isn't Git preserving modification time on files?" here).
Other solution is to invoke autoconf, touch and so on when it's required.

Actions
Copy link
 #1

Updated by Evgeny Novikov almost 13 years ago

  • Assignee deleted (Vadim Mutilin)
  • Priority changed from High to Normal

This problem seems to be rather seldom, so lower its priority.

Actions
Copy link

Also available in: Atom PDF