Hi Philip, I'm not sure if the attached screenshot of the dialogue box will help, but I don't have access to 'svn status', 'commit', or any other SVN options since the SVN version was upgraded from 1.6 to 1.7. Yes, version 1.6 was installed previously, and I used to make commits from this directory, which is the root directory for this repository. We have two other repositories that we used in 1.6 that upgraded to 1.7 without issues, so this problem came as a surprise. I have not been able to do any commits or updates to try to move or delete anything since version 1.7 was installed.
Is there another way for me to run 'svn status'? Thanks for your assistance, Ryan Schmitz | OLAP Developer / Kalido Specialist | MarketStar | People + Knowledge Accelerating Sales e jschm...@marketstar.com | w 801.786.5287 | m 435.553.1230 | f 801.393.4115 -----Original Message----- From: MARTIN PHILIP [mailto:codematt...@ntlworld.com] On Behalf Of Philip Martin Sent: Monday, April 30, 2012 11:11 AM To: Ryan Schmitz Cc: users@subversion.apache.org Subject: Re: error when upgrading working copy Ryan Schmitz <jschm...@marketstar.com> writes: > 'D:\Development\SVN\Releases\TortoiseSVN-1.7.6\ext\subversion\subversion\libsvn_wc\entries.c' > line 126: assertion failed (entry->schedule == svn_wc_schedule_add || > entry->schedule == svn_wc_schedule_normal) Not seen that one before. Do you have 1.6 installed? The working copy is still in 1.6 format, if you run 'svn status' on it do an local modifications show up? Do you make commits from this working copy? Have any commits moved or deleted anything? -- Philip This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. Dissemination, distribution or copying of this e-mail or the information herein by anyone other than the intended recipient, or an employee or agent responsible for delivering the message to the intended recipient, is prohibited. If you have received this e-mail in error, please immediately notify us by replying to sender.
