<div dir="ltr">Seems better to blow everything away and re-"git clone" for an automated build machine.<div style><br>Robby</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, Mar 10, 2013 at 7:56 PM, Jon Rafkind <span dir="ltr"><<a href="mailto:rafkind@cs.utah.edu" target="_blank">rafkind@cs.utah.edu</a>></span> wrote:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On 03/10/2013 06:14 PM, Eli Barzilay wrote:<br> > 20 minutes ago, Jon Rafkind wrote:<br> >> The ubuntu ppa build has been failing for a while, and I finally<br> >> tracked it down to this issue: src/racket/src/schemef.h has a newer<br> >> timestamp than src/racket/src/schemex.h on a fresh git checkout from<br> >> github.<br> > This shouldn't be right. Git doesn't track modification times<br> > (intentionally), so a fresh clone should have all of the dates be the<br> > same. If you update the tree (eg, if you checkout a different<br> > branch), then files that were modified get a new date -- as usual.<br> ><br> <br> </div>Ok, good point. I think the issue is that I only do a 'git pull' on the machine that sends the plt tar to the ubuntu build machine, and so schemef.h was updated without schemex.h being rebuilt. This is likely only going to occur for people who have automated builds setup for racket, which is probably few. So I'll just go with the 'touch *' solution for now.<br> <br> On the 'git pull' machine:<br> <br> $ ls -l scheme*<br> -rw-rw-r-- 1 jon jon 65162 Mar 1 01:00 schemef.h<br> -rw-rw-r-- 1 jon jon 58815 Feb 21 01:00 schemex.h<br> -rw-rw-r-- 1 jon jon 51616 Feb 1 14:12 schemex.inc<br> -rw-rw-r-- 1 jon jon 54988 Feb 1 14:12 schemexm.h<br> <div class="HOEnZb"><div class="h5">_________________________<br> Racket Developers list:<br> <a href="http://lists.racket-lang.org/dev" target="_blank">http://lists.racket-lang.org/dev</a><br> </div></div></blockquote></div><br></div>