File rename breaking builds

[Steven Danneman]

False alarm.  I didn't properly "git mv".  Instead I did a standard "mv"
with "git commit -a".  Thus, my newly renamed oplock.c file did not
actually get pushed.

Live and learn :)

-Steven

> -----Original Message-----
> From: samba-technical-bounces at lists.samba.org [mailto:samba-technical-
> bounces at lists.samba.org] On Behalf Of Steven Danneman
> Sent: Thursday, October 01, 2009 3:59 PM
> To: samba-technical at lists.samba.org
> Subject: File rename breaking builds
> 
> Hey,
> 
> 
> 
> I renamed an s4 torture file from oplocks.c to oplock.c and it seems
> this is causing some of the build machines to fail:
> 
> 
> 
>
http://build.samba.org/?function=View+Build;host=burns;tree=samba_4_0_t
> e
> st;compiler=gcc
> 
> 
> 
> This has something to do with S4s build system and possibly the use of
> ccache on the build machines, because a fresh build works fine.
> 
> 
> 
> Does anyone have an idea how to force machines in the build farm to do
> a
> fresh build?
> 
> 
> 
> -Steven