Re: Proposal for root cause fix "svn co --force"
On Tue, May 19, 2009 at 07:56:09PM +0200, Simon Paillard wrote:
> On Tue, May 19, 2009 at 06:57:01AM -0700, Matt Kraai wrote:
> > 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.
> [...]
> > Maybe file a bug report against Subversion asking for such an option?
>
> Or use svn export --force URL ?
$ svn help export
export: Create an unversioned copy of a tree.
usage: 1. export [-r REV] URL[@PEGREV] [PATH]
1. Exports a clean directory tree from the repository specified by
URL, at revision REV if it is given, otherwise at HEAD, into
PATH. If PATH is omitted, the last component of the URL is used
for the local directory name.
Valid options:
-q [--quiet] : print nothing, or only summary information
--force : force operation to run
...
Yes, this sounds like what we need.
Currently: The script does a svn update, and then make -C manuals clean publish.
The script should do a svn export --force URL, and then make -C manuals clean publish.
Osamu
Reply to: