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

Re: Working copy permissions changed by keyword substitution

From: Daniel Shahaf <d.s_at_daniel.shahaf.name>
Date: Fri, 22 Feb 2013 20:30:05 +0200

Joshua Root wrote on Fri, Feb 22, 2013 at 22:23:57 +1100:
> This seems like a bug to me, so I'm running it by the list as requested
> on the web site.
>
> My umask is 006, but I have changed the permissions on one of my svn
> working copies so that it is world readable. Whenever I commit a file
> that has property 'svn:keywords Id' and contains an Id line, the
> permissions are changed back to the new file default as per the umask.
> Committing files without svn:keywords leaves the permissions the way I
> set them.
>
> I'm trying to make a repro script, but keyword expansion doesn't seem to
> be working right in the context of repro-template.sh. I've added this
> where it said "This is where your reproduction recipe goes":
>

Please send the complete script in the future. Yes, that's redundant,
but self-containedness trumps.

> umask 006
> chmod a+r iota
> ${SVN} propset svn:keywords Id iota
> echo "# $Id$" >> iota
> ls -l iota
> ${SVN} ci -m "Add Id" iota
> ls -l iota
>
> The "# $Id$" line changes into "# $", and what's worse, the permissions

You need to use '' not "" to escape the $. (see sh(1) man page)

As to your actual problem: I expect the permissions will be reset every
time an update or switch changes the file, even if it doesn't have
svn:keywords set. Is it so?

> don't change.
>
> Please Cc me on replies.
>
> Cheers,
> Josh
Received on 2013-02-22 19:30:45 CET

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.