[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Problem with capital file extensions when using the autoprops feature in the svn config file

From: <erik.wuestner_at_etas.com>
Date: Tue, 15 Jul 2008 16:14:17 +0200

Hi, everyone,

I'm using SVN 1.4.5 on Windows Server 2003 R2 SP2 with Apache 2.2.8.
Client-side I'm running Win XP SP2 with TortoiseSVN 1.4.7, Build 11792.
In my SVN config file I've got the following lines:

...
enable-auto-props = yes
...
[auto-props]
...
*.jpg = svn:needs-lock=true;svn:mime-type=image/jpeg
*.JPG = svn:needs-lock=true;svn:mime-type=image/jpeg
...

If I add example1.jpg in TortoiseSVN everything works great. However, if I
add example2.JPG the autoprops are not applied, i.e. example2.JPG ends up
with svn:mime-type = application/octet-stream and svn:needs-lock NOT set.

If I configure my settings file like this, i.e. I switch the order of both
lines:
*.JPG = svn:needs-lock=true;svn:mime-type=image/jpeg
*.jpg = svn:needs-lock=true;svn:mime-type=image/jpeg

then only example2.JPG gets the correct props set, but example1.jpg
doesn't. I can reproduce that with other extensions (doc/DOC) as well.
I think that the entries in the config file should either both be
recognized or it should be case-insensitive. The way it is right now only
all lower-case or all upper-case works, which is not sufficient.

Any suggestions?

Thanks a lot,
Erik
Received on 2008-07-15 18:41:37 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.