svnmucc and creating new files in existing directories

2017-06-05 Thread Sam Ruby
When I moved whimsy from Ubuntu 14.04 (svn 1.8.8) to Ubuntu 16.04 (svn 
1.9.3), svnmucc commands started failing for me:


$ svnmucc --revision 0 --message 'test data, please ignore' -- put - 
https://svn.apache.org/repos/private/financials/Bills/paid/test < test
svnmucc: E160016: Can't commit to 
'https://svn.apache.org/repos/private/financials/Bills/paid' because it 
is not a directory


I can continue to replace svnmucc with svn checkout --depth empty; svn 
add, svn commit sequences; but I was wondering if I'm using svnmucc 
incorrectly?


- Sam Ruby



Re: svnmucc and creating new files in existing directories

2017-06-05 Thread Sam Ruby

On 06/05/2017 02:10 PM, Daniel Shahaf wrote:

Sam Ruby wrote on Mon, 05 Jun 2017 10:08 -0400:

When I moved whimsy from Ubuntu 14.04 (svn 1.8.8) to Ubuntu 16.04 (svn
1.9.3), svnmucc commands started failing for me:

$ svnmucc --revision 0 --message 'test data, please ignore' -- put -
https://svn.apache.org/repos/private/financials/Bills/paid/test < test
svnmucc: E160016: Can't commit to
'https://svn.apache.org/repos/private/financials/Bills/paid' because it
is not a directory

I can continue to replace svnmucc with svn checkout --depth empty; svn
add, svn commit sequences; but I was wondering if I'm using svnmucc
incorrectly?


I assume it works if you leave the --revision out?  The directory in
question doesn't exist in r0, so I wouldn't expect the command to work
as written.


OK, that worked.  Thanks!

FWIW, I'm pretty sure that was cargo-culted from a script you had 
written (the mailing list subscription tool, to be specific), and the 
comment that line had was as follows:


# add file to svn (--revision 0 means it won't overwrite an existing file)

Which leads to a question: what will svnmucc do if the file already exists?

- Sam Ruby