Re: auto-props syntax in file vs. property

On 22.02.2018 13:52, Chris wrote: > Re-awakening my previous thread about the auto-properties. I get really > confused by where to use ;; and ; as a separator. > > I currently have this in the auto-props on the repo: > *.txt = svn:mime-type=text/plain;;charset=iso-8859-1;svn:eol-style=LF > > And

Re: auto-props syntax in file vs. property

Re-awakening my previous thread about the auto-properties. I get really confused by where to use ;; and ; as a separator. I currently have this in the auto-props on the repo: *.txt = svn:mime-type=text/plain;;charset=iso-8859-1;svn:eol-style=LF And then if I add a text file: prompt> touch

SHA-1 collision in repository?

When we try to commit a very specific version of a very specific binary file, we get a SHA-1 collision error from the Subversion repository: D:\confidential>svn commit secret.bin -m "Testing broken commit" Sendingsecret.bin Transmitting file data .svn: E16: Commit failed (details

Re: SHA-1 collision in repository?

I would get more advice from people here before you invest that time. I'm a relative amateur and would listen to people with more experience than myself. --Matt On Thu, Feb 22, 2018 at 2:29 PM, Myria wrote: > That was one document we ran into when searching, yes. > > We

Re: SHA-1 collision in repository?

On 22.02.2018 21:30, Myria wrote: > When we try to commit a very specific version of a very specific > binary file, we get a SHA-1 collision error from the Subversion > repository: > > D:\confidential>svn commit secret.bin -m "Testing broken commit" > Sendingsecret.bin > Transmitting file

Re: SHA-1 collision in repository?

Branko Čibej writes: > On 22.02.2018 21:30, Myria wrote: >> When we try to commit a very specific version of a very specific >> binary file, we get a SHA-1 collision error from the Subversion >> repository: >> >> D:\confidential>svn commit secret.bin -m "Testing broken commit"

Re: SHA-1 collision in repository?

Hi Melissa, That definitely is interesting. I assume you have read http://blogs.collab.net/subversion/subversion-sha1-collision-problem-statement-prevention-remediation-options If you do an svnsync to another location and attempt the commit there, does the problem replicate itself? --Matt

Re: SHA-1 collision in repository?

That was one document we ran into when searching, yes. We can do an svnsync, but this will take about a week to run--the repository is 43 GB with 600,000 commits. I guess we'll start it now. On Thu, Feb 22, 2018 at 2:04 PM, Matt Simmons wrote: > Hi Melissa, > > That

Re: auto-props syntax in file vs. property

Hi Brane, thanks for the reply. Then I understand why it's acting the way it is. It would have been nicer with different separators for the two cases, but it is what it is and I agree that it works. The downside is that my initial fix (earlier in this thread) for svn_apply_autoprops.py isn't