On Tue, Sep 29, 2009 at 8:19 AM, Stefan Sperling <stsp_at_elego.de> wrote:
> On Mon, Sep 28, 2009 at 05:35:49PM -0400, Jim Sokoloff wrote:
> > We have a strange situation on a 1.6.3 svn repo. I'm stopping short of
> > calling it a bug right now, but I suspect it is.
> >
> > I have a handful of revisions (all from the same user and roughly the
> > same time) containing no changed paths, no changed props, etc.
> >
> > Meaning: when I svnadmin dump those revisions, they have a log message,
> > author, etc, but no paths or props. (This is not the case of doing an
> > svn log from the "wrong" part of the tree and finding nothing. There is
> > nothing to be found.)
> >
> > a. Any explanation for how that can happen?
>
> Yes. Use a pre-1.6 server and commit the deletion of a file which has
> already been deleted in the repository. If you make no other changes
> within the same commit, you will get an empty revision.
>
> This was fixed in 1.6.x as part of the tree conflicts effort.
> A 1.6.x server will perform an out-of-dateness check before deleting
> an item, and reject the commit if the item is out-of-date (i.e. its
> BASE revision is not HEAD).
>
<snipped />
Just to confirm, by 'use a pre-1.6' server, this is referring just to the
process serving the repository, or to the repository format itself? ie will
using a 1.6.x binary to access a 1.5.x repository still perform the check?
Sorry, would attempt this, but unfortunately do not have the spare time.
Cheers,
Daniel B.
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2401828
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-09-30 02:29:47 CEST