Bug in SVN? (Was Re: [PATCH] "svnadmin dump": An optional XML output format.

[David Summers <da...@summersoft.fay.ar.us>]

One thing I noticed when I dumped out a working project repository of 
about 9 Meg, 117 revisions:

I found several instances where the file was binary but was not noted in 
the repository as being binary.  (A couple of *.ps.gz files and a 
CodeWarrior *.mcp file).

I checked back through the revision histories and at one point they were 
noted as being binary and another point they were not noted as being 
binary.

I'm trying to figure out how this happened, and if I should be worried 
about it for the integrety of my existing repositories (about 25 of them 
currently).

Basically somewhere the repository lost the information that the files 
are binary.  The file contents appears to be OK, just the meta-data was 
lost.

I can send a dump or provide one to be picked up if any one is interested.

Is this something I/we should be worried about?

    Thanks!

-- 
David Wayne Summers          "Linux: Because reboots are for hardware upgrades!"
david@summersoft.fay.ar.us   PGP Key: http://summersoft.fay.ar.us/~david/pgp.txt
PGP Key fingerprint =  C0 E0 4F 50 DD A9 B6 2B  60 A1 31 7E D2 28 6D A8 


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

Re: Bug in SVN? (Was Re: [PATCH] "svnadmin dump": An optional XML output format.

[Branko Čibej <br...@xbc.nu>]

David Summers wrote:

>One thing I noticed when I dumped out a working project repository of 
>about 9 Meg, 117 revisions:
>
>I found several instances where the file was binary but was not noted in 
>the repository as being binary.  (A couple of *.ps.gz files and a 
>CodeWarrior *.mcp file).
>
>I checked back through the revision histories and at one point they were 
>noted as being binary and another point they were not noted as being 
>binary.
>
>I'm trying to figure out how this happened, and if I should be worried 
>about it for the integrety of my existing repositories (about 25 of them 
>currently).
>
Sounds like somebody changed the svn:mime-type property. The server
certainly doesn't do that by itself. In fact, the /client/ decides
whether a file is binary or not.

>Basically somewhere the repository lost the information that the files 
>are binary.  The file contents appears to be OK, just the meta-data was 
>lost.
>
You don't have to worry about corruption, unless you also enabled
keyword expansion anr/or newline conversion on those files. By default,
Subversion never transmogrifies file contents.

Good thing we decided that should be the default, eh?
/me sprains arm patting self on back

>I can send a dump or provide one to be picked up if any one is interested.
>
>Is this something I/we should be worried about?
>
>    Thanks!
>
>  
>


-- 
Brane Čibej   <br...@xbc.nu>   http://www.xbc.nu/brane/


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