[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Why does acessing logs using "-r HEAD" doesn't provide results?

From: Daniel Shahaf <d.s_at_daniel.shahaf.name>
Date: Mon, 18 May 2020 16:52:38 +0000

Thorsten Schöning wrote on Mon, 18 May 2020 16:20 +00:00:
> Hi all,
>
> I'm having trouble understanding a problem with comparing paths in
> WebSVN: Comparing two paths uses HEAD as revision specifier by default
> and works in one setup and doesn't in another. The root cause is that
> accessing the history of the repo simply doesn't provide any results
> when used like the following:
>
> > C:\[...]>svn log -r HEAD C:\[...]\trunk --xml --limit 1
> > <?xml version="1.0" encoding="UTF-8"?>
> > <log>
> > </log>
>
> Using the concrete revision number the working copy is in or some
> different keyword works:
>
> > C:\[...]>svn log -r COMMITTED C:\[...]\trunk --xml --limit 1
> > <?xml version="1.0" encoding="UTF-8"?>
> > <log>
> > <logentry
> > revision="667">
> [...]
> > </logentry>
> > </log>
>
> So why does HEAD doesn't provide any details? Thanks!

rHEAD might have touched a path outside of trunk, or paths under trunk
that are authz-restricted, or it might actually be an empty revision.
To rule out these, look what paths rHEAD changed. Use «svnlook changed»
if you can, or «svn log -qvrHEAD ^/» (double the caret if using cmd.exe
or zsh -o extendedglob).

Another possibility is that trunk had been replaced between BASE and
HEAD. Try passing HEAD as a peg revision.

If none of these works, run «svn info -r HEAD --show-item=revision ^/»
before _and after_ reproducing the issue, and then see if you can
reproduce it against the specific revision number of HEAD at that time,
and we can take it from there.

Cheers,

Daniel
Received on 2020-05-18 18:53:06 CEST

This is an archived mail posted to the Subversion Users mailing list.