You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Mark Phippard <ma...@gmail.com> on 2012/12/04 15:17:23 UTC
Error running update using trunk
I have a working copy created like this:
$ svn co --depth=immediates http://svn.apache.org/repos/asf/subversion
$ svn up --set-depth=infinity subversion/trunk
$ svn up --set-depth=immediates subversion/branches
$ svn up --set-depth=infinity subversion/branches/fsfs-format7
This all worked fine. But when I tried to expand another folder, I
get an error:
$ svn up --set-depth=infinity subversion/branches/ev2-export
subversion/svn/update-cmd.c:168: (apr_err=22)
subversion/libsvn_client/update.c:639: (apr_err=22)
subversion/libsvn_client/update.c:579: (apr_err=22)
subversion/libsvn_client/update.c:440: (apr_err=22)
subversion/libsvn_wc/adm_crawler.c:858: (apr_err=22)
subversion/libsvn_ra_serf/update.c:2857: (apr_err=22)
svn: E000022: Error retrieving REPORT: Invalid argument
Segmentation fault: 11
$ svn cleanup
subversion/svn/svn.c:2755: (apr_err=155004)
svn: E155004: Run 'svn cleanup' to remove locks (type 'svn help
cleanup' for details)
subversion/svn/cleanup-cmd.c:99: (apr_err=155004)
subversion/libsvn_client/cleanup.c:63: (apr_err=155004)
subversion/libsvn_wc/cleanup.c:213: (apr_err=155004)
subversion/libsvn_wc/cleanup.c:152: (apr_err=155004)
subversion/libsvn_wc/wc_db.c:13124: (apr_err=155004)
subversion/libsvn_wc/wc_db_util.c:211: (apr_err=155004)
subversion/libsvn_subr/sqlite.c:1107: (apr_err=155004)
subversion/libsvn_wc/wc_db_util.c:189: (apr_err=155004)
subversion/libsvn_wc/wc_db.c:13036: (apr_err=155004)
svn: E155004: Working copy
'/Users/markphip/testing/subversion/branches/ev2-export' locked.
subversion/libsvn_wc/wc_db.c:13028: (apr_err=155004)
svn: E155004: '/Users/markphip/testing/subversion/branches' is already locked.
subversion/libsvn_wc/wc_db.c:1622: (apr_err=155037)
svn: E155037: Additional errors:
subversion/libsvn_wc/wc_db.c:1622: (apr_err=155037)
subversion/libsvn_wc/wc_db_wcroot.c:684: (apr_err=155037)
subversion/libsvn_wc/wc_db_wcroot.c:293: (apr_err=155037)
subversion/libsvn_wc/wc_db_wcroot.c:159: (apr_err=155037)
svn: E155037: Previous operation has not finished; run 'cleanup' if it
was interrupted
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
Re: Error running update using trunk
Posted by Mark Phippard <ma...@gmail.com>.
On Tue, Dec 4, 2012 at 10:56 AM, Julian Foad <ju...@btopenworld.com> wrote:
> Ugh. It's important that we improve the error message. Please could you file an issue for that with milestone 1.8 unless it's going to get done today.
Done: http://subversion.tigris.org/issues/show_bug.cgi?id=4268
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
Re: Error running update using trunk
Posted by Julian Foad <ju...@btopenworld.com>.
> Mark Phippard wrote:
> Philip Martin wrote:
>> Mark Phippard <ma...@gmail.com> writes:
>>> $ svn cleanup
>>> svn: E155004: Run 'svn cleanup' to remove locks (type 'svn
>>> help cleanup' for details)
>>> svn: E155004: Working copy
>>> '/Users/markphip/testing/subversion/branches/ev2-export' locked.
>>> svn: E155004: '/Users/markphip/testing/subversion/branches' is
>>> already locked.
>>> svn: E155037: Additional errors:
>>> svn: E155037: Previous operation has not finished; run
>>> 'cleanup' if it was interrupted
>>
>> I think that means you didn't run cleanup at the root of the working
>> copy. We should either improve the error message or perhaps
>> automatically apply cleanup to the root.
>
> Ahh, thanks. In my case, I had to run it from the parent folder
> (branches). That caused cleanup to work.
Ugh. It's important that we improve the error message. Please could you file an issue for that with milestone 1.8 unless it's going to get done today.
- Julian
Re: Error running update using trunk
Posted by Mark Phippard <ma...@gmail.com>.
On Tue, Dec 4, 2012 at 9:57 AM, Philip Martin
<ph...@wandisco.com> wrote:
> Mark Phippard <ma...@gmail.com> writes:
>
>> I have a working copy created like this:
>>
>> $ svn co --depth=immediates http://svn.apache.org/repos/asf/subversion
>> $ svn up --set-depth=infinity subversion/trunk
>> $ svn up --set-depth=immediates subversion/branches
>> $ svn up --set-depth=infinity subversion/branches/fsfs-format7
>>
>> This all worked fine. But when I tried to expand another folder, I
>> get an error:
>>
>> $ svn up --set-depth=infinity subversion/branches/ev2-export
>>
>> subversion/svn/update-cmd.c:168: (apr_err=22)
>> subversion/libsvn_client/update.c:639: (apr_err=22)
>> subversion/libsvn_client/update.c:579: (apr_err=22)
>> subversion/libsvn_client/update.c:440: (apr_err=22)
>> subversion/libsvn_wc/adm_crawler.c:858: (apr_err=22)
>> subversion/libsvn_ra_serf/update.c:2857: (apr_err=22)
>> svn: E000022: Error retrieving REPORT: Invalid argument
>> Segmentation fault: 11
>
> Difficult to say what happened there. That sequence of commands worked
> for me using my local mirror.
>
>> $ svn cleanup
>> subversion/svn/svn.c:2755: (apr_err=155004)
>> svn: E155004: Run 'svn cleanup' to remove locks (type 'svn help
>> cleanup' for details)
>> subversion/svn/cleanup-cmd.c:99: (apr_err=155004)
>> subversion/libsvn_client/cleanup.c:63: (apr_err=155004)
>> subversion/libsvn_wc/cleanup.c:213: (apr_err=155004)
>> subversion/libsvn_wc/cleanup.c:152: (apr_err=155004)
>> subversion/libsvn_wc/wc_db.c:13124: (apr_err=155004)
>> subversion/libsvn_wc/wc_db_util.c:211: (apr_err=155004)
>> subversion/libsvn_subr/sqlite.c:1107: (apr_err=155004)
>> subversion/libsvn_wc/wc_db_util.c:189: (apr_err=155004)
>> subversion/libsvn_wc/wc_db.c:13036: (apr_err=155004)
>> svn: E155004: Working copy
>> '/Users/markphip/testing/subversion/branches/ev2-export' locked.
>> subversion/libsvn_wc/wc_db.c:13028: (apr_err=155004)
>> svn: E155004: '/Users/markphip/testing/subversion/branches' is already locked.
>> subversion/libsvn_wc/wc_db.c:1622: (apr_err=155037)
>> svn: E155037: Additional errors:
>> subversion/libsvn_wc/wc_db.c:1622: (apr_err=155037)
>> subversion/libsvn_wc/wc_db_wcroot.c:684: (apr_err=155037)
>> subversion/libsvn_wc/wc_db_wcroot.c:293: (apr_err=155037)
>> subversion/libsvn_wc/wc_db_wcroot.c:159: (apr_err=155037)
>> svn: E155037: Previous operation has not finished; run 'cleanup' if it
>> was interrupted
>
> I think that means you didn't run cleanup at the root of the working
> copy. We should either improve the error message or perhaps
> automatically apply cleanup to the root.
Ahh, thanks. In my case, I had to run it from the parent folder
(branches). That caused cleanup to work.
I then updated the folder to depth=empty and back to infinity without
problem this time. So not sure what caused the segfault but it was
not reproduced.
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
Re: Error running update using trunk
Posted by Philip Martin <ph...@wandisco.com>.
Mark Phippard <ma...@gmail.com> writes:
> I have a working copy created like this:
>
> $ svn co --depth=immediates http://svn.apache.org/repos/asf/subversion
> $ svn up --set-depth=infinity subversion/trunk
> $ svn up --set-depth=immediates subversion/branches
> $ svn up --set-depth=infinity subversion/branches/fsfs-format7
>
> This all worked fine. But when I tried to expand another folder, I
> get an error:
>
> $ svn up --set-depth=infinity subversion/branches/ev2-export
>
> subversion/svn/update-cmd.c:168: (apr_err=22)
> subversion/libsvn_client/update.c:639: (apr_err=22)
> subversion/libsvn_client/update.c:579: (apr_err=22)
> subversion/libsvn_client/update.c:440: (apr_err=22)
> subversion/libsvn_wc/adm_crawler.c:858: (apr_err=22)
> subversion/libsvn_ra_serf/update.c:2857: (apr_err=22)
> svn: E000022: Error retrieving REPORT: Invalid argument
> Segmentation fault: 11
Difficult to say what happened there. That sequence of commands worked
for me using my local mirror.
> $ svn cleanup
> subversion/svn/svn.c:2755: (apr_err=155004)
> svn: E155004: Run 'svn cleanup' to remove locks (type 'svn help
> cleanup' for details)
> subversion/svn/cleanup-cmd.c:99: (apr_err=155004)
> subversion/libsvn_client/cleanup.c:63: (apr_err=155004)
> subversion/libsvn_wc/cleanup.c:213: (apr_err=155004)
> subversion/libsvn_wc/cleanup.c:152: (apr_err=155004)
> subversion/libsvn_wc/wc_db.c:13124: (apr_err=155004)
> subversion/libsvn_wc/wc_db_util.c:211: (apr_err=155004)
> subversion/libsvn_subr/sqlite.c:1107: (apr_err=155004)
> subversion/libsvn_wc/wc_db_util.c:189: (apr_err=155004)
> subversion/libsvn_wc/wc_db.c:13036: (apr_err=155004)
> svn: E155004: Working copy
> '/Users/markphip/testing/subversion/branches/ev2-export' locked.
> subversion/libsvn_wc/wc_db.c:13028: (apr_err=155004)
> svn: E155004: '/Users/markphip/testing/subversion/branches' is already locked.
> subversion/libsvn_wc/wc_db.c:1622: (apr_err=155037)
> svn: E155037: Additional errors:
> subversion/libsvn_wc/wc_db.c:1622: (apr_err=155037)
> subversion/libsvn_wc/wc_db_wcroot.c:684: (apr_err=155037)
> subversion/libsvn_wc/wc_db_wcroot.c:293: (apr_err=155037)
> subversion/libsvn_wc/wc_db_wcroot.c:159: (apr_err=155037)
> svn: E155037: Previous operation has not finished; run 'cleanup' if it
> was interrupted
I think that means you didn't run cleanup at the root of the working
copy. We should either improve the error message or perhaps
automatically apply cleanup to the root.
--
Certified & Supported Apache Subversion Downloads:
http://www.wandisco.com/subversion/download