Hi Gary,

Commit failed again.
I have attached the error snapshot and the svn info just below, please help
me to have a look.
Thanks.


<
https://mail.google.com/mail/u/0/?ui=2&ik=aaa0d8a81e&view=att&th=1400b3a78ff42730&attid=0.2&disp=safe&realattid=ii_1400b3a6213f374d&zw
>
>
</mail/u/0/s/?view=att&th=1400b40e0aed4072&attid=0.1&disp=emb&realattid=ii_1400b40bc0079028&zw&atsh=1>
>
>
>
>
</mail/u/0/s/?view=att&th=1400b571f94149d0&attid=0.1&disp=emb&realattid=ii_1400b568dbddf769&zw&atsh=1>

$ svn info
svn: E155036: Please see the 'svn upgrade' command
svn: E155036: The working copy at '/home/xiang/bep_0008_time_series_reports'
is too old (format 29) to work with client version '1.8.0 (r1490375)'
(expects format 31). You need to upgrade the working copy first.

> $ svn --version
> svn, version 1.8.0 (r1490375)
>    compiled Jun 19 2013, 10:42:54 on i686-pc-cygwin
> Copyright (C) 2013 The Apache Software Foundation.
> This software consists of contributions made by many people;
> see the NOTICE file for more information.
> Subversion is open source software, see http://subversion.apache.org/
> The following repository access (RA) modules are available:
> * ra_svn : Module for accessing a repository using the svn network
protocol.
>   - with Cyrus SASL authentication
>   - handles 'svn' scheme
> * ra_local : Module for accessing a repository on local disk.
>   - handles 'file' scheme
> * ra_serf : Module for accessing a repository via WebDAV protocol using
serf.
>   - handles 'http' scheme
>   - handles 'https' scheme
>
>
> 2013/7/23 Gary Martin <[email protected]>
>>
>> On 23/07/13 02:58, Hua Xiang wrote:
>>>
>>> 2013/7/23 Ryan Ollos <[email protected]>
>>>
>>>> On Mon, Jul 22, 2013 at 6:38 PM, Hua Xiang <[email protected]>
wrote:
>>>>
>>>>> 2013/7/23 Ryan Ollos <[email protected]>
>>>>>
>>>>>> On Mon, Jul 22, 2013 at 6:06 PM, Hua Xiang <[email protected]>
>>>>>
>>>>> wrote:
>>>>>>>
>>>>>>> Hi!
>>>>>>>
>>>>>>> I am doing the project 'generate time series reports'.
>>>>>>> Details are:
>>>>>>> (https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0008)
>>>>>>>
>>>>>>> I have created SQL statements to generate reports locally and I also
>>>>>>> committed the changes needed for display. However, I would like to
>>>>
>>>> know
>>>>>>
>>>>>> how
>>>>>>>
>>>>>>> to commit my SQL statements to the repository so that other
developer
>>>>>
>>>>> can
>>>>>>>
>>>>>>> see my change?
>>>>>>>
>>>>>>> Thanks!
>>>>>>>
>>>>>>> Best,
>>>>>>> Hua
>>>>>>>
>>>>>>
>>>>>> I had pasted a link to "ViewVC" earlier, so that could have been
>>>>>> misleading, sorry about that.
>>>>>>
>>>>>> Please try the following:
>>>>>>   - $ svn co
>>>>>>
>>>>
svn.apache.org/repos/asf/bloodhound/branches/bep_0008_time_series_reports
>>>>>>
>>>>>>   - apply your changes in the working copy
>>>>
>>>> "bep_0008_time_series_reports"
>>>>>>
>>>>>>   - check-in your changes as you did earlier (but you'll be pushing
to
>>>>>
>>>>> your
>>>>>>
>>>>>> branch this time, not the trunk).
>>>>>>
>>>>> Commit failed. Please check my last email.
>>>>
>>>> What error message do you see when the commit fails?
>>>
>>> "Error Access to '/repos/asf/!svn/me‘ forbidden"
>>>   However, I just committed to trunk successfully.
>>>
>>>
>>>> What is the output of "svn info" on your working copy?
>>>>
>>> TortoiseSVN 1.7.13, Build 24257 - 64 Bit , 2013/06/01 07:32:54
>>> Subversion 1.7.10,
>>> apr 1.4.6
>>> apr-utils 1.3.12
>>> neon 0.29.6
>>> OpenSSL 1.0.1e 11 Feb 2013
>>> zlib 1.2.7
>>
>> That doesn't look like svn info output to me. I don't have tortoisesvn
so I can't confirm the correct way of doing this but this link might help:
https://groups.google.com/forum/#!topic/tortoisesvn/BnHc_WoJkWs
>>
>> Anyway, if the failure is in committing changes then I would have to
guess that you saw no errors in the checkout phase. And given that you were
able to commit to trunk, there should be no differences in your ability to
commit to
https://svn.apache.org/repos/asf/bloodhound/branches/bep_0008_time_series_reports
>>
>> Do you want to get a fresh checkout of your branch to copy your changes
into with the equivalent of:
>>
>> svn co
https://svn.apache.org/repos/asf/bloodhound/branches/bep_0008_time_series_reports
>>
>> The only difference between that and what Ryan specified is the https pr

Reply via email to