Subversion Exception! line 647: assertion failed (peg_revnum != SVN_INVALID_REVNUM)

[Sandeepan Kundu <sa...@gmail.com>]

the following error received:


---------------------------
Subversion Exception!
---------------------------
Subversion encountered a serious problem.
Please take the time to report this on the Subversion mailing list
with as much information as possible about what
you were trying to do.
But please first search the mailing list archives for the error message
to avoid reporting the same problem repeatedly.
You can find the mailing list archives at
http://subversion.apache.org/mailing-lists.html

Subversion reported the following
(you can copy the content of this dialog
to the clipboard using Ctrl-C):

In file
 'D:\Development\SVN\Releases\TortoiseSVN-1.8.0\ext\subversion\subversion\libsvn_client\ra.c'
 line 647: assertion failed (peg_revnum != SVN_INVALID_REVNUM)
---------------------------
OK
---------------------------


was using tortoise svn 1.7
Installed Visual SVN client for dotnet
Visual SVN installation advised for 1.8 upgrate.
Downloaded and installed the same.
Henceforth not able to perform SVN operation!!!!

No Commit, No Update,, nothing

Tried going back to 1.7, but it is telling project is in higher version :((

how to use now, my development is getting affected!!!

Re: Subversion Exception! line 647: assertion failed (peg_revnum != SVN_INVALID_REVNUM)

[Shannon <sh...@gmail.com>]

Thomas Harold <thomas-lists <at> nybeta.com> writes:

> 
> On 6/20/2013 11:55 PM, Sandeepan Kundu wrote:
> >
> > Tried going back to 1.7, but it is telling project is in higher version :
((
> >
> > how to use now, my development is getting affected!!!
> 
> I suggest renaming your old (upgraded to 1.8) working copy out of the 
> way, doing a fresh checkout using 1.7 into a fresh working copy folder, 
> then copying over changed files from the upgraded 1.8 working copy which 
> isn't working.
> 
> Naturally, making a backup of the borked working copy is strongly 
> suggested if you had uncommitted changes.
> 
> 


I am getting the same error.  Fresh install of 1.8. I was trying to Import a 
folder into a new Repository.  then I tried to invoke the repo browser.  Same 
error both times. Trying to connect to Unfuddle.

Re: Subversion Exception! line 647: assertion failed (peg_revnum != SVN_INVALID_REVNUM)

[Thomas Harold <th...@nybeta.com>]

On 6/20/2013 11:55 PM, Sandeepan Kundu wrote:
>
> Tried going back to 1.7, but it is telling project is in higher version :((
>
> how to use now, my development is getting affected!!!

I suggest renaming your old (upgraded to 1.8) working copy out of the 
way, doing a fresh checkout using 1.7 into a fresh working copy folder, 
then copying over changed files from the upgraded 1.8 working copy which 
isn't working.

Naturally, making a backup of the borked working copy is strongly 
suggested if you had uncommitted changes.