Re: Valid Syntax for commit-access-control.cfg
What type of "error" are you getting? Is the script running, but not giving you the results you expect (i.e., it rejects a commit that it should accept or visa versa), or is the script erroring out with a message? I'm looking at the code, and I really don't see an issue with periods in the name since user names are white space separated. However, it could be due to an error in the module "Config::IniFiles". Have you tried running the script by hand to see what you get? Have you tried adding a few debug lines in the script to see why the user ID isn't what you expect? This hook script has been replaced by the "svnperms.py" script, a Python script. Have you tried that script. If you prefer a Perl script, you're also welcome to try my configuration script which I wrote to specifically replace the commit-access-control.pl script. You can get that here: http://dl.dropbox.com/u/433257/hooks.zip. This does work with periods in the user names. On Wed, Feb 3, 2010 at 5:49 PM, Steven Hansen wrote: > > > Hi, > > I'm trying to find some documentation describing "valid" syntax for the > commit-access-control.cfg > file. I've been bitten in the past by using something like: > > [SVN - config modification permissions] > match = ^SVN > access = read-write > users = first.lastname > > Having a '.' in the username causes errors. > > Also, does anyone know why does this cause errors? If possible I'd like to > include usernames that > include the '.' > > Thanks, > Steven > > > > -- David Weintraub qazw...@gmail.com
Re: Valid Syntax for commit-access-control.cfg
Hi David, I get an error like this: svn: 'pre-commit' hook failed with error output: /svn/repo/hooks/commit-access-control.pl: error in loading configuration file `/svn/repo/hooks/commit-access-control.cfg': Line 308 in file /svn/repo/hooks/commit-access-control.cfg is mal-formed: This has happened 3-4 times when various people have updated the file. It is always a result of using a '.' in a user's name. I don't know perl very well and assumed it has to do with the '.' being interpreted as a regex character instead of a literal '.' I wasn't aware that svnperms.py is a replacement script. I'll take a look and see if I can replace. Thanks! ~Steven David Weintraub wrote: What type of "error" are you getting? Is the script running, but not giving you the results you expect (i.e., it rejects a commit that it should accept or visa versa), or is the script erroring out with a message? I'm looking at the code, and I really don't see an issue with periods in the name since user names are white space separated. However, it could be due to an error in the module "Config::IniFiles". Have you tried running the script by hand to see what you get? Have you tried adding a few debug lines in the script to see why the user ID isn't what you expect? This hook script has been replaced by the "svnperms.py" script, a Python script. Have you tried that script. If you prefer a Perl script, you're also welcome to try my configuration script which I wrote to specifically replace the commit-access-control.pl script. You can get that here: http://dl.dropbox.com/u/433257/hooks.zip. This does work with periods in the user names. On Wed, Feb 3, 2010 at 5:49 PM, Steven Hansen wrote: Hi, I'm trying to find some documentation describing "valid" syntax for the commit-access-control.cfg file. I've been bitten in the past by using something like: [SVN - config modification permissions] match = ^SVN access = read-write users = first.lastname Having a '.' in the username causes errors. Also, does anyone know why does this cause errors? If possible I'd like to include usernames that include the '.' Thanks, Steven
Problems merging with 1.6.2 client and 1.5.6 server
Hi, Are there known issues merging between branches using a 1.6.2 client and a 1.5.6 server? Here's what I'm seeing. I create a release branch with svn cp, commit changes to the head, and do `svn merge -cNNN ^/trunk/path` in the branch's working copy to backport a change to the branch. It takes a long time (never finishes under http/mod_dav_svn, takes almost a minute under svn+ssh), and then svn status shows a propset modification for svn:mergeinfo for every file recursively under my working copy of the branch, including files that I didn't touch in the change I'm merging. Help? Thanks, -Clint
Problems setting svn:ignore property to "*" via windows command line
Hi, i am trying to set the svn:ignore property of a specific folder to "*", so that all files and folders inside this folder are beeing ignored by svn. Somehow i don't get this done, i tried lots of different aproaches, but it always seems as if the pattern is beeing expanded, so that either the command fails, or the property it beeing set to the wrong value. Target folder> svn propset svn:ignore * . ( command is executed on all contents of . with property value ".svn" (??)) Target folder> svn propset svn:ignore "*" . ( same result) Target folder> svn propset svn:ignore "\*" . ( error: "\xxx is not a working copy" ) Target folder> svn propset svn:ignore "^*" . (no expansion takes place, but property is set to "^*") ... What would be the way to do what i want? Why is this so difficult? Where does the expansion take place, is it the command line, or is ist svn? If it is svn, should the property value not be used without expansion? Janosch
Re: Problems setting svn:ignore property to "*" via windows command line
On Sun, Feb 07, 2010 at 08:40:19PM +0100, Janosch Scharlipp wrote: > > Hi, i am trying to set the svn:ignore property of a specific folder to "*", > so that all files and folders inside this folder are beeing ignored by svn. > Somehow i don't get this done, i tried lots of different aproaches, but it > always seems as if the pattern is beeing expanded, so that either the > command fails, or the property it beeing set to the wrong value. > > Target folder> svn propset svn:ignore * . > ( command is executed on all contents of . with property value ".svn" (??)) > > Target folder> svn propset svn:ignore "*" . > ( same result) > > Target folder> svn propset svn:ignore "\*" . > ( error: "\xxx is not a working copy" ) > > Target folder> svn propset svn:ignore "^*" . > (no expansion takes place, but property is set to "^*") > > ... > > What would be the way to do what i want? Why is this so difficult? Where > does the expansion take place, is it the command line, or is ist svn? If it > is svn, should the property value not be used without expansion? See http://svn.haxx.se/users/archive-2009-05/0846.shtml Stefan
RE: Q: Changeset between two revisions
Hi Daniel, This command just gives the list of files changes. My requirements is to collect the files changes list and collect the listed files in both the revisions. Do u have any idea to do this? With Regards, Senthil -Original Message- From: Daniel Widenfalk [mailto:daniel.widenf...@iar.com] Sent: Friday, February 05, 2010 11:36 PM To: users@subversion.apache.org Subject: Re: Q: Changeset between two revisions Hi, Manickavel, Senthil wrote: > Hi, > I would like to create a changeset between > two revisions. I have created a script to do that with > svn commands. But this collects all the files in both > the revisions. Is it possible for me to collect only > the changed file? > > Script > > REM Create root folder > md Changeset > cd Changeset > > REM Collect old revision files. > md %1 > cd %1 > svn checkout -r %1 %3 > > REM Collect new revision files. > cd.. > md %2 > cd %2 > svn checkout -r %2 %3 > > REM Create changed files list > cd.. > svn log -r %1:%2 %3 -v > ChangedFiles.txt > cd.. > > Regards, > Senthil A quick "svn help diff" shows a --summarize option. Try "svn diff -r rev1:rev2 http://URL-to-repo --summarize" and see if it matches your need. You may need to filter the output slightly. Regards /Daniel The information contained in this message may be confidential and legally protected under applicable law. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, forwarding, dissemination, or reproduction of this message is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original message.
