Garrett Rooney <rooneg@electricjellyfish.net> wrote:
> On Monday, October 28, 2002, at 08:07 AM, Rafael Garcia-Suarez wrote:
>
> > Isn't this supposed to be the new syntax (according to the docs ?)
> >
> > $ svnadmin undeltify repos -r368 /
> > svn: Unsupported repository version
> > svn: Expected version '1' of repository; found no version at all; is
> > `/' a valid repository path?
> > svn: No such file or directory
> > svn: svn_io_file_open: can't open `/format'
> >
> > I remember having used successfully undeltify, but with another
> > syntax, with r3200. I tried various permutation of the arguments, with
> > no luck. (Maybe it's me, if this bug has been fixed recently,
> > please excuse me.)
>
> are you sure that the repository was created with the same version of
> libsvn_fs that svnadmin was linked with? it can't seem to find the
> version file, which implies that it was created with an old svn.
Yes -- I created it this morning.
In fact it searches for the version file in / instead of repos/,
but / should be interpreted as a repository path.
If I permute the arguments, I got :
$ svnadmin undeltify / -r368 repos
svn: Filesystem has no item
svn: file not found: revision `368', path `repos'
OK I think I begin to understand this. Command-line arguments are misparsed.
The 1st one is ignored, and the 3rd one is interpreted as a repository path
and as a path inside the repository. (I haven't looked at the source yet.)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Oct 28 14:27:44 2002