Dave Jones <davej@xxxxxxxxxx> writes: > On Thu, Sep 14, 2006 at 10:27:54AM -0700, Nishanth Aravamudan wrote: > > Hi Dave, > > > > For simplicities sake when I was running Debian Sarge on a server here, > > I was using your nightly tarballs of git to build a fresh up-to-date > > version on a regular basis. I noticed though, that the tarballs result > > in gits with a version of 1.3.GIT, while the git repository is at > > 1.4.2.1. Is that expected? > > No, it isn't. (at least by me). > What the snapshotting script does when cron runs it is just a 'git pull' > on a repo that was cloned a while back when I first set up the snapshotting > script. I could change it to do a fresh clone each time it runs, but > that seems somewhat wasteful when most of the time there's nothing new to pull. > > gitsters, any ideas what could be going wrong here ? > The original clone of the repo was just a straight clone of git://git.kernel.org/pub/scm/git/git.git When the build procesure assigns the version to the generated git binary, it does these checks and takes the first one: - Run "git describe" at the top of the source tree. If it returns some version (not an error message), use it. This case should not apply here since we are talking about a tarball of a working tree, and it does not have a repository. - See if 'version' file exists at the top of the source tree, and uses what is recorded there. This file is placed in the resulting tarball by the "make dist" target of the toplevel Makefile. - Otherwise use DEF_VER hardcoded in GIT-VERSION-GEN script. The 1.4.2 series is shipped with DEF_VER set to v1.4.2.GIT, so this does not explain why Nashanth sees "1.3.GIT" (or "v1.3.GIT", if the original report did not copy it right). I just snarfed your snapshot tarball from a few days ago, and I do not see any version file there (which indicates that it is not a product of "make dist"). Interestingly enough DEF_VER is set to v1.3.GIT in GIT-VERSION-GEN. This line was changed from v1.3.GIT to v1.4.GIT with commit 41292dd on June 10th and then updated to v1.4.2.GIT with commit 5a71682 on August 3rd. So a short conclusion is that the directory you are tarring up does not have snapshot of my tree. I would like to understand why. If an automated 'pull' is failing, that is somewhat worrysome, because I presume you do not do any development of your own in your snapshot directory and in that case everything should fast forward. Even if 'pull' failed somehow, if it is not reporting its failure, it is even more worrysome. - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html