Re: Proposal for root cause fix "svn co --force"
On Tue, May 19, 2009 at 10:08:22PM +0900, Osamu Aoki wrote:
> On Mon, May 18, 2009 at 06:51:08AM -0700, Matt Kraai wrote:
> > On Mon, May 18, 2009 at 10:31:21PM +0900, Osamu Aoki wrote:
> > > Well it happend again when I added new file which happen to conflict
> > > with broken build file. I think I can work around this ... but...
> > >
> > > I think root cause fix this problem is to run "svn checkout" with
> > > "--force" option. Since no one is commiting from www-master checkout,
> > > it should not be problem as I understand.
> > >
> > > This should make build process more robust.
> >
> > According to "svn help checkout," if an unversioned obstructing path
> > already exists, using the --force option will allow the checkout to
> > succeed but will keep the contents of the existing file. This seems
> > like a worse failure mode than before, since it will still need to be
> > removed but now that's less obvious.
>
> --force : force operation to run
>
> I thought it meant quietly overwrites ... But it is not as I tested..
> you are right.
>
> I agree it is worse.
>
> Is there any good way to **force overwrite**
>
> po file can be updated on www-master while building but next cron may
> try to overwrite with new po file .. then conflict happens.
>
> I know we need to sync po before commiting to avoid this. But build
> system relying on such consistency is not-so-robust.
Maybe file a bug report against Subversion asking for such an option?
--
Matt http://ftbfs.org/
Reply to: