Description of problem: Working with OpenWRT attitude adjustment trunk svn up Updating '.': svn: E235000: In file 'subversion/libsvn_wc/update_editor.c' line 1583: assertion failed (action == svn_wc_conflict_action_edit || action == svn_wc_conflict_action_delete || action == svn_wc_conflict_action_replace) Aborted (core dumped) Occured even after exporting an EDITOR ... export EDITOR=vim Version-Release number of selected component: subversion-1.7.6-1.fc17 Additional info: libreport version: 2.0.14 abrt_version: 2.0.13 backtrace_rating: 4 cmdline: svn up crash_function: svn_error_abort_on_malfunction kernel: 3.5.6-1.fc17.x86_64 truncated backtrace: :Thread no. 1 (10 frames) : #2 svn_error_abort_on_malfunction at subversion/libsvn_subr/error.c:648 : #3 check_tree_conflict at subversion/libsvn_wc/update_editor.c:1587 : #4 close_file at subversion/libsvn_wc/update_editor.c:4085 : #5 ra_svn_handle_close_file at subversion/libsvn_ra_svn/editorp.c:772 : #6 svn_ra_svn_drive_editor2 at subversion/libsvn_ra_svn/editorp.c:916 : #7 ra_svn_finish_report at subversion/libsvn_ra_svn/client.c:299 : #8 svn_wc_crawl_revisions5 at subversion/libsvn_wc/adm_crawler.c:865 : #9 update_internal at subversion/libsvn_client/update.c:401 : #10 svn_client__update_internal at subversion/libsvn_client/update.c:543 : #11 svn_client_update4 at subversion/libsvn_client/update.c:600
Created attachment 625524 [details] File: core_backtrace
Created attachment 625525 [details] File: environ
Created attachment 625526 [details] File: limits
Created attachment 625527 [details] File: backtrace
Created attachment 625528 [details] File: cgroup
Created attachment 625529 [details] File: maps
Created attachment 625530 [details] File: dso_list
Created attachment 625531 [details] File: open_fds
Created attachment 625532 [details] File: var_log_messages
1) Is this reproducible? A fresh checkout of that repo seems to work here. 2) If so, what revision was your working copy in when you tried to update? ("svn info ." output?)
I have the previous revision 33725 latest is currently 33726 svn info . Path: . Working Copy Root Path: /home/simong/svnhome/AA URL: svn://svn.openwrt.org/openwrt/trunk Repository Root: svn://svn.openwrt.org/openwrt Repository UUID: 3c298f89-4303-0410-b956-a3cf2f4a3e73 Revision: 33725 Node Kind: directory Schedule: normal Last Changed Author: nbd Last Changed Rev: 33650 Last Changed Date: 2012-10-08 01:24:02 +0200 (Mon, 08 Oct 2012)
Just tried a clean co of 33725, then svn up and that worked. The only diff between the two is a small change to target/linux/ar7/image/Makefile Must have something to do with local changes I have? But now I have removed my local changes and did an svn up and it crashed the same way. But mysteriously Im at r 33726 now. svn diff shows nothing. svn up still crashes ?? Would be interesting to see whats wrong. But otherwise I can just go to the clean co and add in my local changes!
Can you tar up your working copy and attach it here?
(In reply to comment #13) > Can you tar up your working copy and attach it here? It's 1.1GB as a bzip2ed tar file. Is it OK to upload here ?
Created attachment 626461 [details] Bzipped openwrt AA repo. minus lots of unnessary directorys for this test. Unpack this tar file. Go into the 1st directory (aa) svn up Updating '.': svn: E235000: In file 'subversion/libsvn_wc/update_editor.c' line 1583: assertion failed (action == svn_wc_conflict_action_edit || action == svn_wc_conflict_action_delete || action == svn_wc_conflict_action_replace) Aborted (core dumped)
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.