Re: Updating source

[Anton Shepelev]

Nathan Hartman to Anton Shepelev:

> > That was my initial suggestion, too, but when I tried `svn up'
> > at a random location that was not an SVN working directory it
> > printed:
> >
> >   Skipped '.'
> >   Summary of conflicts:
> > Skipped paths: 1
> >
> > which is not very polite. I expected:
> >
> >   svn: E155007: 'C:\Program Files\Far Manager' is not a working
> > copy
> 
> Interesting. I think you are using an older Subversion client. For
> example, Subversion 1.8.14 prints this when I run "svn update" in
> a random non-working-copy directory:
> 
> E:\junk>svn up
> Skipped '.'
> Summary of conflicts:
>   Skipped paths: 1
> 
> But Subversion 1.13.0 prints this:
> 
> junk $ svn up
> Skipped '.'
> svn: E155007: None of the targets are working copies

Thank you. I should not have believed the handling of so basic an
error has changed so recently. It it time I upgraded my svn client.

-- 
()  ascii ribbon campaign - against html e-mail
/\  http://preview.tinyurl.com/qcy6mjc [archived]

Re: commit failed due to "backwards-sliding source views" - what do I do?

[Nathan Hartman]

On Thu, Apr 30, 2020 at 1:23 AM Chaya  wrote:

> Hi all,
>
> Thanks for all the suggestions and hints given.
>
> The problem is finally solved.
> Here is my analysis:
> I copied the SVN repository to my local machine (which was on network drive
> before).
> The 'git svn clone' command does not work for file based repository. And
> this is why I had to convert the repo to svn protocol as I mentioned
> before.
> So now, I again converted the local repository link to svn protocol and
> tried git svn clone again. But unfortunately, it again failed at the same
> point.
> So, instead of git-svn , I used subgit (https://subgit.com/documentation/).
>
> Subgit allows to use file based repository and also conversion happens
> aggressively. Using subgit , I was able to migrate successfully.
> Still have no clue why I get this "svndiff has backwards-sliding source
> views" error while performing git svn clone on svn protocol.


Glad you were able to solve this.

Thank you for letting us know, and for explaining your solution to help
others who might have the same question in the future.

Best regards,
Nathan