Re: Issue: empty commit(no changes) in an fsfs repository.

["D.J. Heap" <dj...@gmail.com>]

On 7/31/06, Garrett Rooney <ro...@electricjellyfish.net> wrote:
> On 7/31/06, Lieven Govaerts <lg...@mobsol.be> wrote:
> > Hi,
> >
> > in one of our repositories we found an empty revision. Empty meaning: author,
> > date and log message are filled in correctly, but no changes were stored.
> > Clients are TortoiseSVN 1.2.3 on Windows 2000, server is svn 1.2.3 with ra_dav
> > on SLES 9.
> >
> > I checked the mailing list archive and issue tracker with the query 'empty
> > commit' and couldn't find anything at all. I'm wondering of this is a known
> > issue in svn 1.2.3? It looks like a problem with setting/changing a property on
> > a folder.
>
> I'm not sure about any known problem that could cause that, but I do
> know that it's perfectly possible to have empty commits like that.
> svnsync can generate them, for example, when you don't have access to
> any of the changed paths in a given revision.  I'd be interested to
> see if you could reproduce the problem manually with the command line
> client though.
>
> -garrett
>


svndumpfilter can also generate them.

DJ

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: Issue: empty commit(no changes) in an fsfs repository.

[Lieven Govaerts <lg...@mobsol.be>]

Quoting Lieven Govaerts <lg...@mobsol.be>:

> D.J. Heap wrote:
> > On 7/31/06, Garrett Rooney <ro...@electricjellyfish.net> wrote:
> >>
> >> I'm not sure about any known problem that could cause that, but I do
> >> know that it's perfectly possible to have empty commits like that.
> >> svnsync can generate them, for example, when you don't have access to
> >> any of the changed paths in a given revision.  I'd be interested to
> >> see if you could reproduce the problem manually with the command line
> >> client though.
> >>
> >
> > svndumpfilter can also generate them.
> >
>
> Neither svnsync nor svndumpfilter was used on this repository. Can I
> assume that it should be impossible to create empty revisions using only
> the svn client? Or are you suggesting otherwise?
>

I've searched the list with 'empty revision' and found this thread:
http://svn.haxx.se/dev/archive-2005-08/0091.shtml

In fact, what I see here seems to be a result of issue 2220: "svn propdel
returns success on deleting a non-existent prop". I've tested it also with
deleting a file that's already deleted which also creates an empty revision.

Since the propdel issue is already reported (I don't know about the double
delete issue) this thread can be closed.

regards,

Lieven.



----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: Issue: empty commit(no changes) in an fsfs repository.

[Lieven Govaerts <lg...@mobsol.be>]

D.J. Heap wrote:
> On 7/31/06, Garrett Rooney <ro...@electricjellyfish.net> wrote:
>>
>> I'm not sure about any known problem that could cause that, but I do
>> know that it's perfectly possible to have empty commits like that.
>> svnsync can generate them, for example, when you don't have access to
>> any of the changed paths in a given revision.  I'd be interested to
>> see if you could reproduce the problem manually with the command line
>> client though.
>>
> 
> svndumpfilter can also generate them.
> 

Neither svnsync nor svndumpfilter was used on this repository. Can I 
assume that it should be impossible to create empty revisions using only 
the svn client? Or are you suggesting otherwise?

Lieven.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org