Re: Error E145001

2018-11-08 Thread xxsawer
Hi Brane,
thank you for quick response.
Unfortunately I cannot update to newer Subversion.
I have removed it without the --keep-local parameter

Thanks,
Dan

On 2018/11/06 14:41:01, Branko Čibej  wrote: 
> On 06.11.2018 13:29, xxsa...@seznam.cz wrote:
> > Hello,
> > I am trying to remove symbolic link that is currently under version control 
> > but with keeping it in the file system. I try to do it like this:
> > svn delete --keep-local xyz
> >
> > When now trying to commit this change, I get following error:
> > svn: E145001: Commit failed (details follow):
> > svn: E145001: Entry 'xyz' has unexpectedly changed special status
> >
> > svn --version
> > svn, version 1.7.14 (r1542130)
> >
> > Is this a bug or just wrong approach?
> 
> It's a bug in a version of Subversion that's far too old. You really
> should upgrade if you can; 1.7.x and 1.8.x are no longer supported.
> 
> It works with 1.11:
> 
> $ svnadmin create repo
> $ svn co file://$(pwd)/repo wc
> Checked out revision 0.
> $ ln -s foo wc/bar
> $ svn add wc/bar
> A wc/bar
> $ svn ci -mm wc
> Adding wc/bar
> Transmitting file data .done
> Committing transaction...
> Committed revision 1.
> $ svn rm --keep-local wc/bar 
> D wc/bar
> $ svn ci -mm wc
> Deleting   wc/bar
> Committing transaction...
> Committed revision 2.
> $ svn st wc
> ?   wc/bar
> $ ls -l wc
> total 0
> lrwxr-xr-x  1 brane  staff  3  6 Nov 15:36 bar -> foo
> 
> 
> 
> -- Brane
> 
> 


Re: Error: Could not access revision times

2018-11-08 Thread Daniel Shahaf
Mark Phippard wrote on Wed, 07 Nov 2018 08:20 -0500:
> Yes, the user that got this error was using SVNKit.  I do not know if it
> was via Jenkins, Eclipse or something else and that is why I am not sure
> what the command was.  I asked to recreate using SVN command line so we
> could better understand what triggered it.

To better understand what triggers the error we should patch 
subversion/mod_dav_svn/reports/dated-rev.c
to log the error that libsvn_repos returns there, and probably the
input date too.

It's a wild guess but perchance it's a 'svn co ${URL}@{DATE}' and the
binary search (to resolve {DATE} to a number) is failing due to authz?