You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Lieven Govaerts <lg...@mobsol.be> on 2006/07/31 09:36:37 UTC
Issue: empty commit(no changes) in an fsfs repository.
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.
This is the revision file:
> less 443
id: 0.0.r443/0
type: dir
pred: 0.0.r442/2966
count: 443
text: 442 2917 36 36 1baf9182994a7115c1033e3809d85017
cpath: /
copyroot: 0 /
0 134
====================================================
The apache access log (I've changed the username to developer and the ip address
to xx.xx.xx.xx):
====================================================
xx.xx.xx.xx - - [27/Jul/2006:16:20:58 +0200] "PROPFIND
/svn/pmt/main/branches/DEV_V0004.00.00/db/COLL/AFKS_COL.SQL HTTP/1.1" 401 495
xx.xx.xx.xx - developer [27/Jul/2006:16:20:58 +0200] "PROPFIND
/svn/pmt/main/branches/DEV_V0004.00.00/db/COLL/AFKS_COL.SQL HTTP/1.1" 404 350
xx.xx.xx.xx - developer [27/Jul/2006:16:20:58 +0200] "PROPFIND
/svn/pmt/main/branches/DEV_V0004.00.00/db/COLL HTTP/1.1" 404 337
xx.xx.xx.xx - developer [27/Jul/2006:16:20:58 +0200] "PROPFIND
/svn/pmt/main/branches/DEV_V0004.00.00/db HTTP/1.1" 207 738
xx.xx.xx.xx - developer [27/Jul/2006:16:20:58 +0200] "PROPFIND
/svn/pmt/!svn/vcc/default HTTP/1.1" 207 398
xx.xx.xx.xx - developer [27/Jul/2006:16:20:58 +0200] "PROPFIND
/svn/pmt/!svn/bln/442 HTTP/1.1" 207 453
xx.xx.xx.xx - developer [27/Jul/2006:16:20:58 +0200] "PROPFIND
/svn/pmt/main/branches/DEV_V0004.00.00/db/COLL/AFKS_COL.SQL HTTP/1.1" 404 350
xx.xx.xx.xx - developer [27/Jul/2006:16:20:58 +0200] "PROPFIND
/svn/pmt/main/branches/DEV_V0004.00.00/db/COLL HTTP/1.1" 404 337
xx.xx.xx.xx - developer [27/Jul/2006:16:20:58 +0200] "PROPFIND
/svn/pmt/main/branches/DEV_V0004.00.00/db HTTP/1.1" 207 738
xx.xx.xx.xx - developer [27/Jul/2006:16:20:58 +0200] "PROPFIND
/svn/pmt/!svn/vcc/default HTTP/1.1" 207 398
xx.xx.xx.xx - developer [27/Jul/2006:16:20:58 +0200] "PROPFIND
/svn/pmt/!svn/bln/442 HTTP/1.1" 207 453
xx.xx.xx.xx - - [27/Jul/2006:16:20:58 +0200] "PROPFIND
/svn/pmt/main/branches/DEV_V0004.00.00/db/COLL/AFKS_COL.SQL HTTP/1.1" 401 495
xx.xx.xx.xx - developer [27/Jul/2006:16:20:58 +0200] "PROPFIND
/svn/pmt/main/branches/DEV_V0004.00.00/db/COLL/AFKS_COL.SQL HTTP/1.1" 404 350
xx.xx.xx.xx - developer [27/Jul/2006:16:20:58 +0200] "PROPFIND
/svn/pmt/main/branches/DEV_V0004.00.00/db/COLL HTTP/1.1" 404 337
xx.xx.xx.xx - developer [27/Jul/2006:16:20:58 +0200] "PROPFIND
/svn/pmt/main/branches/DEV_V0004.00.00/db HTTP/1.1" 207 738
xx.xx.xx.xx - developer [27/Jul/2006:16:20:58 +0200] "PROPFIND
/svn/pmt/!svn/vcc/default HTTP/1.1" 207 453
xx.xx.xx.xx - developer [27/Jul/2006:16:20:58 +0200] "REPORT
/svn/pmt/!svn/bc/442/main/branches/DEV_V0004.00.00/db/COLL/AFKS_COL.SQL
HTTP/1.1" 404 362
xx.xx.xx.xx - - [27/Jul/2006:16:21:28 +0200] "OPTIONS
/svn/pmt/main/branches/DEV_V0004.00.00/db HTTP/1.1" 401 495
xx.xx.xx.xx - developer [27/Jul/2006:16:21:28 +0200] "OPTIONS
/svn/pmt/main/branches/DEV_V0004.00.00/db HTTP/1.1" 200 187
xx.xx.xx.xx - developer [27/Jul/2006:16:21:28 +0200] "MKACTIVITY
/svn/pmt/!svn/act/a171b5ac-1c8b-bf43-9a2b-acc6db20d58b HTTP/1.1" 201 322
xx.xx.xx.xx - developer [27/Jul/2006:16:21:28 +0200] "PROPFIND
/svn/pmt/main/branches/DEV_V0004.00.00/db HTTP/1.1" 207 463
xx.xx.xx.xx - developer [27/Jul/2006:16:21:28 +0200] "PROPFIND
/svn/pmt/!svn/vcc/default HTTP/1.1" 207 398
xx.xx.xx.xx - developer [27/Jul/2006:16:21:28 +0200] "CHECKOUT
/svn/pmt/!svn/bln/442 HTTP/1.1" 201 338
xx.xx.xx.xx - developer [27/Jul/2006:16:21:28 +0200] "PROPPATCH
/svn/pmt/!svn/wbl/a171b5ac-1c8b-bf43-9a2b-acc6db20d58b/442 HTTP/1.1" 207 354
xx.xx.xx.xx - developer [27/Jul/2006:16:21:28 +0200] "PROPFIND
/svn/pmt/main/branches/DEV_V0004.00.00/db HTTP/1.1" 207 448
xx.xx.xx.xx - developer [27/Jul/2006:16:21:28 +0200] "CHECKOUT
/svn/pmt/!svn/ver/442/main/branches/DEV_V0004.00.00/db HTTP/1.1" 201 367
xx.xx.xx.xx - developer [27/Jul/2006:16:21:28 +0200] "DELETE
/svn/pmt/!svn/wrk/a171b5ac-1c8b-bf43-9a2b-acc6db20d58b/main/branches/DEV_V0004.00.00/db/COLL
HTTP/1.1" 404 383
xx.xx.xx.xx - developer [27/Jul/2006:16:21:28 +0200] "MERGE
/svn/pmt/main/branches/DEV_V0004.00.00/db HTTP/1.1" 200 478
xx.xx.xx.xx - developer [27/Jul/2006:16:21:28 +0200] "DELETE
/svn/pmt/!svn/act/a171b5ac-1c8b-bf43-9a2b-acc6db20d58b HTTP/1.1" 204 -
xx.xx.xx.xx - - [27/Jul/2006:16:21:40 +0200] "PROPFIND
/svn/pmt/main/branches/DEV_V0004.00.00 HTTP/1.1" 401 495
xx.xx.xx.xx - developer [27/Jul/2006:16:21:40 +0200] "PROPFIND
/svn/pmt/main/branches/DEV_V0004.00.00 HTTP/1.1" 207 732
xx.xx.xx.xx - developer [27/Jul/2006:16:21:40 +0200] "PROPFIND
/svn/pmt/!svn/vcc/default HTTP/1.1" 207 398
xx.xx.xx.xx - developer [27/Jul/2006:16:21:40 +0200] "PROPFIND
/svn/pmt/!svn/bln/443 HTTP/1.1" 207 453
xx.xx.xx.xx - developer [27/Jul/2006:16:21:40 +0200] "PROPFIND
/svn/pmt/main/branches/DEV_V0004.00.00 HTTP/1.1" 207 732
====================================================
The actual commit 443 is the one at 16:21:28. The db/COLL folder doesn't exist
in the repository at r442.
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.
Posted by 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.
Posted by 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
Re: Issue: empty commit(no changes) in an fsfs repository.
Posted by "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.
Posted by Garrett Rooney <ro...@electricjellyfish.net>.
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org