Subversion version on server
This is just a simple question that I can't find the answer to. How do I go about finding out what version of subversion (e.g. 1.6.#) is on the server. The svn help doesn't give that type of information and there is no 'about' that usually has that info. Thanks, Rich
Re: Subversion version on server
Thank you all for the education. --- On Wed, 12/15/10, Norbert Unterberg wrote: From: Norbert Unterberg Subject: Re: Subversion version on server To: "K F" Cc: users@subversion.apache.org Date: Wednesday, December 15, 2010, 12:20 PM 2010/12/14 K F > > This is just a simple question that I can't find the answer to. How do I go > about finding out what version of subversion (e.g. 1.6.#) is on the server. > The svn help doesn't give that type of information and there is no 'about' > that usually has that info. > Just open the repository URL in any web browser. In the last line, the server displays the version numbers like this: Apache/2.2.16 (Unix) mod_ssl/2.2.16 OpenSSL/0.9.8k DAV/2 mod_wsgi/3.1 Python/2.6.4 SVN/1.6.12 Server at svn.apache.org Port 443 SVN/1.6.12 means it uses subversion version 1.6.12 Norbert
Re: access denied errors Windows 7
Just curious, you state you are trying to run "TortoiseSVN 1.6.16, Build 21511 - 32 Bit", isn't Windows 7 64 bit? --- On Wed, 6/29/11, Ken G. Brown wrote: From: Ken G. Brown Subject: Re: access denied errors Windows 7 To: "Thorsten Schöning" , "users@subversion.apache.org" Date: Wednesday, June 29, 2011, 4:04 PM Thx, I'll look into these. At the moment I am trying to export a single file rather than a directory into my local destination directory, do you think that would make a difference? Ken At 9:42 AM +0200 6/29/11, Thorsten Schöning wrote: >Guten Tag Ken G. Brown, >am Dienstag, 28. Juni 2011 um 19:46 schrieben Sie: > >> I have AVG Free running, the error persists when I turn off its protection >> temporarily. > >As it seems that ideas are getting less, I would take a chance on >Filemon or Process Monitor to see if something strange is shown. The >error don't necessarily has to come from the rename of the temporary >folder to the new one, but can happen before that operation because of >something, > >http://technet.microsoft.com/de-de/sysinternals/bb896645 > >Mit freundlichen Grüßen, > >Thorsten Schöning > >-- >Thorsten Schöning >AM-SoFT IT-Systeme - Hameln | Potsdam | Leipzig > >Telefon: Potsdam: 0331-743881-0 >E-Mail: tschoen...@am-soft.de >Web: http://www.am-soft.de > >AM-SoFT GmbH IT-Systeme, Konsumhof 1-5, 14482 Potsdam >Amtsgericht Potsdam HRB 21278 P, Geschäftsführer: Andreas Muchow
Move to a new repo and keep the history
I’ve been searching and can’t seem to find an answer on whether I can move some directories from one repository to another while keeping the history. Repo1/tags/tag1 and move tag1 to Repo2 Repo2/tags/tag1 Is it possible? Thanks, Rich
Move to a new repo and keep the history, Part 2
Recap – I would like to move some directories from one repository to another while keeping the history. Repo1/tags/tag1 and move tag1 to Repo2 Repo2/tags/tag1 I’ve run svnadmin dump /svnrepo/ Repo1/ > repo1/ repo1_dump and the resulting file appears to be correct (get Dumped revision). I’ve then run svndumpfilter include tags < repo1_dump > stags and the resulting file appears to be correct (get Dropped nodes for branches and trunk). I then tried doing another dumpfilter on stags, svndumpfilter include tag1 < stags > tag1 to get just the tag1 folder but it doesn't seem to work, it drops all nodes under it. Am I doing something incorrectly or is it impossible to do a 'double' filter? I do not want all the tags under the tag directory, just specific ones (all at once preferably, but I would guess would have to be done one at a time). Thanks, Rich
New Server because of Crash
Our Subversion server crashed because of a disk fail. We are in the process of setting up a new server to move the repos to. What is the consensus to do the restore from a backup? Is it straight forward? What problems if any would there be for users using TortoiseSVN in connecting to the new server? Thanks, Rich
Re: New Server because of Crash
--- On Tue, 12/6/11, Thorsten Schöning wrote: > From: Thorsten Schöning > Subject: Re: New Server because of Crash > To: users@subversion.apache.org > Date: Tuesday, December 6, 2011, 3:46 PM > Guten Tag K F, > am Dienstag, 6. Dezember 2011 um 16:22 schrieben Sie: > > > What is the consensus to do the restore from a backup? Is it > straight forward? > > Doesn't this mainly depend on how your backup looks like? > :-) > > > What problems if any would there be for users using > TortoiseSVN in connecting to the new server? > > This depends on how you set up the new server and how the working > copies were checked out. If your users checked out using IPs and it > changed, they have to svn switch --relocate, same for changed DNS > names etc. > > Mit freundlichen Grüßen, > > Thorsten Schöning > > --- The backups were done using svn dump. The new server is planned to be named the same. Does that mean the switch wouldn't need to be done?
Re: New Server because of Crash
--- On Tue, 12/6/11, Thorsten Schöning wrote: > From: Thorsten Schöning > Subject: Re: New Server because of Crash > To: users@subversion.apache.org > Date: Tuesday, December 6, 2011, 4:19 PM > Guten Tag K F, > am Dienstag, 6. Dezember 2011 um 16:58 schrieben Sie: > > > The backups were done using svn dump. > > This means you have to manually create each repository and > copy all > hooks, configurations etc. from the old server. On svnadmin > load you > have to take special care on using the old uuids for the > new > repositories or all working copies need to get checked out, > I think, > not even switch --relocate works anymore. > > > The new server is planned to > > be named the same. Does that mean the switch wouldn't > need to be done? > > I think so, if you use the same uuids for your newly > created > repository as the old ones used. > > Mit freundlichen Grüßen, > > Thorsten Schöning > How would I get the uuid's. We have the dump, but I believe that is it. Can the uuids be obtained from them, would it be simpler to just have everyone do a new checkout?
Re: New Server because of Crash
--- On Tue, 12/6/11, kmra...@rockwellcollins.com wrote: From: kmra...@rockwellcollins.com Subject: Re: New Server because of Crash To: users@subversion.apache.org Date: Tuesday, December 6, 2011, 7:30 PM > Stefan Sperling wrote on 12/06/2011 12:45:36 PM: > > > How would I get the uuid's. We have the dump, but I believe that > > is it. Can the uuids be obtained from them, would it be simpler to > > just have everyone do a new checkout? > > > > The UUID is somewhere near the top of the dump file in a line that > > starts with "UUID:". > > > > If you load into a repository which was freshly created with > > 'svnadmin create' the 'svnadmin load' process will change the UUID > > of this repository to match the one found in the dump. > > You may however want to force new uuids if there were any committed > changes that were not in the last dump. This would force users > to create new working copies, because their old ones may be "newer" > than the last dump that you restored from causing problems. > > My process (assuming changes were commited to the repository > after the dumpfile was created and you do not have incremental > dump files): > > 1) Rebuild server > 2) Create new empty repository > 3) Load dumpfile with a *new* UUID > 4) Find the most up-to-date working copy and compare with a > checkout of the new repository > 5) Manually apply any changes identified in step #4 and > commit them to the new repository > > And to ensure steps #4-5 are not needed in the future: > > 6) Implement incremental dumpfiles of each transaction as they > occur to secondary storage area > and/or > 7) Replicate repository to secondary storage/server > > Unless you have other backups, hooks scripts and file > locks will not be restored in the svndump file so > they will need to be manually re-created. Forgot to add that ALL users will need to re-create their working copies if the UUID changes. In my opinion this is probably best if you know transactions occurred since the last svn dumpfile was generated. Kevin R. Thank you all for the help. It appears we lucked out though. Since this was built using flat files and dumps taken, we just had to migrate in the dumps (words of the person doing the restore). No commits were made between the time of the crash and the last backup so no data was lost doing it that way. Once the DNS was changed on the new server to match what it was on the old server, everything started working like nothing was different.
Limited subdirectory access
We have repo ABC with 40+ subdirectories. Current svn security allows developers rw permissions and qa read only to ABC. We would like to have a subgroup of dev to have access to subdirectory DEF (ABC/DEF). Is there a way of doing this, or does the parent directory access take precedent? Thanks, Rich
Re: Limited subdirectory access
--- On Mon, 1/30/12, Andy Levy wrote: > From: Andy Levy > Subject: Re: Limited subdirectory access > To: "K F" > Cc: users@subversion.apache.org > Date: Monday, January 30, 2012, 8:45 PM > On Mon, Jan 30, 2012 at 15:39, K F > > wrote: > > We have repo ABC with 40+ subdirectories. Current svn > security allows developers rw permissions and qa read only > to ABC. We would like to have a subgroup of dev to have > access to subdirectory DEF (ABC/DEF). Is there a way of > doing this, or does the parent directory access take > precedent? > > The most specific path matches first. Just add a rule for > that > subgroup to have access to ABC/DEF and they'll be set. > OK, then I must be doing something wrong. This is how I have it setup in the authz file now: [/] @dev = rw @qa = r [/ABC/DEF] @dev1 = rw Do I need to be more specific?
Re: Limited subdirectory access
--- On Mon, 1/30/12, Andy Levy wrote: > From: Andy Levy > Subject: Re: Limited subdirectory access > To: "K F" > Cc: users@subversion.apache.org > Date: Monday, January 30, 2012, 8:57 PM > On Mon, Jan 30, 2012 at 15:52, K F > > wrote: > > > > > > --- On Mon, 1/30/12, Andy Levy > wrote: > > > >> From: Andy Levy > >> Subject: Re: Limited subdirectory access > >> To: "K F" > >> Cc: users@subversion.apache.org > >> Date: Monday, January 30, 2012, 8:45 PM > >> On Mon, Jan 30, 2012 at 15:39, K F > >> > >> wrote: > >> > We have repo ABC with 40+ subdirectories. > Current svn > >> security allows developers rw permissions and qa > read only > >> to ABC. We would like to have a subgroup of dev to > have > >> access to subdirectory DEF (ABC/DEF). Is there a > way of > >> doing this, or does the parent directory access > take > >> precedent? > >> > >> The most specific path matches first. Just add a > rule for > >> that > >> subgroup to have access to ABC/DEF and they'll be > set. > >> > > > > OK, then I must be doing something wrong. This is how I > have it setup in the authz file now: > > [/] > > @dev = rw > > @qa = r > > > > [/ABC/DEF] > > @dev1 = rw > > > > Do I need to be more specific? > > > > What exactly isn't working? > > Is dev1 a group, or an individual? > > Do you have the case of the path matched exactly? The rules > are case-sensitive. > I am able to commit with a login that is in the dev group that is not in the dev1 group. The actual path is /svnrepo/ABC/DEF so I tried [/svnrepo/sandbox/tags] @dev1 = rw and that doesn't work either. Based on the example in the file I also tried [repository:/svnrepo/sandbox/tags] @dev1 = rw with no luck. Any ideas as to what I am doing wrong?
Re: Limited subdirectory access
--- On Mon, 1/30/12, Stefan Sperling wrote: > From: Stefan Sperling > Subject: Re: Limited subdirectory access > To: "K F" > Cc: "Andy Levy" , users@subversion.apache.org > Date: Monday, January 30, 2012, 9:32 PM > On Mon, Jan 30, 2012 at 01:14:53PM > -0800, K F wrote: > > --- On Mon, 1/30/12, Andy Levy > wrote: > > > have it setup in the authz file now: > > > > [/] > > > > @dev = rw > > > > @qa = r > > > > > > > > [/ABC/DEF] > > > > @dev1 = rw > > > > > > > > Do I need to be more specific? > > > > > > > > > > What exactly isn't working? > > > > > > Is dev1 a group, or an individual? > > > > > > Do you have the case of the path matched exactly? > The rules > > > are case-sensitive. > > > > > > > I am able to commit with a login that is in the dev > group that is not in the dev1 group. > > > > The actual path is /svnrepo/ABC/DEF so I tried > > > > [/svnrepo/sandbox/tags] > > @dev1 = rw > > > > and that doesn't work either. Based on the example in > the file I also tried > > > > [repository:/svnrepo/sandbox/tags] > > @dev1 = rw > > > > with no luck. Any ideas as to what I am doing wrong? > > You'll need to tighten permissions for the 'dev' group in > /ABC/DEF also. > [/] > @dev = rw > @qa = r > > [/ABC/DEF] > @dev = r > @dev1 = rw > > See this snippet from > http://svnbook.red-bean.com/en/1.7/svn.serverconfig.pathbasedauthz.html > "Of course, permissions are inherited from parent to > child directory. > That means we can specify a subdirectory with a > different access policy > for Sally: > > [calc:/branches/calc/bug-142] > harry = rw > sally = r > > # give sally write access only to the 'testing' > subdir > [calc:/branches/calc/bug-142/testing] > sally = rw > > Now Sally can write to the testing subdirectory of > the branch, but can > still only read other parts. Harry, meanwhile, > continues to have > complete read/write access to the whole branch." > > The same applies when restricting access, rather than > expanding it. > I realize my explanation is wrong, my apologies. It is actually repo ABC with 40+ folders under it. I want to limit who has access to one of the folders (DEF). After looking at the svnbook, I thought the following would work but it is still not working: [ABC:/DEF] @dev = r @dev1 = rw
Re: Limited subdirectory access
--- On Mon, 1/30/12, Johan Corveleyn wrote: > From: Johan Corveleyn > Subject: Re: Limited subdirectory access > To: "K F" > Cc: "Stefan Sperling" , "Andy Levy" , > users@subversion.apache.org > Date: Monday, January 30, 2012, 10:13 PM > On Mon, Jan 30, 2012 at 10:55 PM, K F > > wrote: > > > > > > --- On Mon, 1/30/12, Stefan Sperling > wrote: > > > >> From: Stefan Sperling > >> Subject: Re: Limited subdirectory access > >> To: "K F" > >> Cc: "Andy Levy" , > users@subversion.apache.org > >> Date: Monday, January 30, 2012, 9:32 PM > >> On Mon, Jan 30, 2012 at 01:14:53PM > >> -0800, K F wrote: > >> > --- On Mon, 1/30/12, Andy Levy > >> wrote: > >> > > have it setup in the authz file now: > >> > > > [/] > >> > > > @dev = rw > >> > > > @qa = r > >> > > > > >> > > > [/ABC/DEF] > >> > > > @dev1 = rw > >> > > > > >> > > > Do I need to be more specific? > >> > > > > >> > > > >> > > What exactly isn't working? > >> > > > >> > > Is dev1 a group, or an individual? > >> > > > >> > > Do you have the case of the path matched > exactly? > >> The rules > >> > > are case-sensitive. > >> > > > >> > > >> > I am able to commit with a login that is in > the dev > >> group that is not in the dev1 group. > >> > > >> > The actual path is /svnrepo/ABC/DEF so I > tried > >> > > >> > [/svnrepo/sandbox/tags] > >> > @dev1 = rw > >> > > >> > and that doesn't work either. Based on the > example in > >> the file I also tried > >> > > >> > [repository:/svnrepo/sandbox/tags] > >> > @dev1 = rw > >> > > >> > with no luck. Any ideas as to what I am doing > wrong? > >> > >> You'll need to tighten permissions for the 'dev' > group in > >> /ABC/DEF also. > >> [/] > >> @dev = rw > >> @qa = r > >> > >> [/ABC/DEF] > >> @dev = r > >> @dev1 = rw > >> > >> See this snippet from > >> http://svnbook.red-bean.com/en/1.7/svn.serverconfig.pathbasedauthz.html > >> "Of course, permissions are inherited from > parent to > >> child directory. > >> That means we can specify a subdirectory with a > >> different access policy > >> for Sally: > >> > >> [calc:/branches/calc/bug-142] > >> harry = rw > >> sally = r > >> > >> # give sally write access only to the 'testing' > >> subdir > >> [calc:/branches/calc/bug-142/testing] > >> sally = rw > >> > >> Now Sally can write to the testing subdirectory > of > >> the branch, but can > >> still only read other parts. Harry, meanwhile, > >> continues to have > >> complete read/write access to the whole > branch." > >> > >> The same applies when restricting access, rather > than > >> expanding it. > >> > > > > I realize my explanation is wrong, my apologies. It is > actually repo ABC with 40+ folders under it. I want to limit > who has access to one of the folders (DEF). After looking at > the svnbook, I thought the following would work but it is > still not working: > > > > [ABC:/DEF] > > @dev = r > > @dev1 = rw > > Can you check if order of the rules matters? Either putting > this rule > with [ABC:/DEF] before or after the other one (for [ABC:/]). > I'm not > sure, but I vaguely remember some prior discussion about > this ... > > -- > Johan > I tried swapping the order and that didn't work either. Am I stating it correctly? [ABC:/DEF] @dev = r @dev1 = rw Do I need the ABC in the front?
Re: Limited subdirectory access
I had already tried [/DEF] @dev = r @dev1 = rw and that did not work. --- On Tue, 1/31/12, Thorsten Schöning wrote: > From: Thorsten Schöning > Subject: Re: Limited subdirectory access > To: users@subversion.apache.org > Date: Tuesday, January 31, 2012, 8:04 AM > Guten Tag K F, > am Montag, 30. Januar 2012 um 23:20 schrieben Sie: > > > [ABC:/DEF] > > @dev = r > > @dev1 = rw > > > Do I need the ABC in the front? > > If it's just one repository your configuring your authz file > for,your > shouldn't need to specify ABC, so try without. If this > doesn't work, > you really should provide the whole authz file with access > rules for > all paths, groups, members and describe with which user you > login and > can commit to which folder. > > Mit freundlichen Grüßen, > > Thorsten Schöning > > -- > Thorsten Schöning E-Mail:thorsten.schoen...@am-soft.de > AM-SoFT IT-Systeme http://www.AM-SoFT.de/ > > Telefon.030-2 1001-310 > Fax...05151- 9468- 88 > Mobil..0178-8 9468- 04 > > AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 > Hameln > AG Hanover HRB 207 694 - Geschäftsführer: Andreas Muchow > >
RE: Limited subdirectory access
--- On Tue, 1/31/12, Cooke, Mark wrote: > From: Cooke, Mark > Subject: RE: Limited subdirectory access > To: "K F" , "users@subversion.apache.org" > > Date: Tuesday, January 31, 2012, 9:25 AM > > -Original Message- > > From: K F [mailto:cmkfo...@yahoo.com] > > > Sent: 30 January 2012 20:40 > > To: users@subversion.apache.org > > Subject: Limited subdirectory access > > > > We have repo ABC with 40+ subdirectories. Current svn > > security allows developers rw permissions and qa read > only to > > ABC. We would like to have a subgroup of dev to have > access > > to subdirectory DEF (ABC/DEF). Is there a way of doing > this, > > or does the parent directory access take precedent? > > > > Thanks, > > Rich > > > > http://svnbook.red-bean.com/en/1.7/svn.serverconfig.pathbasedauthz.html > > The most specific access takes precedent. You would > need to 'revoke' the normal developer's access to the subdir > (if I understand you correctly) by assigning either 'r' or > just nothing to their group... > > ~ mark c > I tried without anything and still no good [/DEF] @dev = @dev1 = rw I have setup a test repo called sandbox with some subdirectories. Here is my authz file minus all the commented out lines: [aliases] [groups] dev = rcrespo, test dev1 = test qa = qagroup [/DEF] @dev = @dev1 = rw [/] @dev = rw @qa = r I am still able to commit files in the DEF directory using the rcrespo login.
Re: Limited subdirectory access
--- On Tue, 1/31/12, Andy Levy wrote: > From: Andy Levy > Subject: Re: Limited subdirectory access > To: "K F" > Cc: "users@subversion.apache.org" , "MarkCooke" > > Date: Tuesday, January 31, 2012, 1:54 PM > On Tue, Jan 31, 2012 at 08:22, K F > > wrote: > > > > > > --- On Tue, 1/31/12, Cooke, Mark > wrote: > > > >> From: Cooke, Mark > >> Subject: RE: Limited subdirectory access > >> To: "K F" , > "users@subversion.apache.org" > > >> Date: Tuesday, January 31, 2012, 9:25 AM > >> > -Original Message- > >> > From: K F [mailto:cmkfo...@yahoo.com] > >> > >> > Sent: 30 January 2012 20:40 > >> > To: users@subversion.apache.org > >> > Subject: Limited subdirectory access > >> > > >> > We have repo ABC with 40+ subdirectories. > Current svn > >> > security allows developers rw permissions and > qa read > >> only to > >> > ABC. We would like to have a subgroup of dev > to have > >> access > >> > to subdirectory DEF (ABC/DEF). Is there a way > of doing > >> this, > >> > or does the parent directory access take > precedent? > >> > > >> > Thanks, > >> > Rich > >> > > >> > >> http://svnbook.red-bean.com/en/1.7/svn.serverconfig.pathbasedauthz.html > >> > >> The most specific access takes precedent. You > would > >> need to 'revoke' the normal developer's access to > the subdir > >> (if I understand you correctly) by assigning either > 'r' or > >> just nothing to their group... > >> > >> ~ mark c > >> > > I tried without anything and still no good > > > > [/DEF] > > @dev = > > @dev1 = rw > > > > > > I have setup a test repo called sandbox with some > subdirectories. Here is my authz file minus all the > commented out lines: > > > > [aliases] > > > > [groups] > > dev = rcrespo, test > > dev1 = test > > qa = qagroup > > I can't explain why, and maybe it's been fixed in a later > version, but > I seem to recall having an issue with path-based > authorization when > the groups were defined with spaces. IOW, this: > > dev = rcrespo, test > > did not work properly but this: > > dev = rcrespo,test > > did. > I removed the space and that didn't work. I'm open to trying anything that is suggested.
Re: Limited subdirectory access
--- On Tue, 1/31/12, Philip Martin wrote: > From: Philip Martin > Subject: Re: Limited subdirectory access > To: "K F" > Cc: "users@subversion.apache.org" , "MarkCooke" > > Date: Tuesday, January 31, 2012, 2:00 PM > Stefan Sperling > writes: > > > On Tue, Jan 31, 2012 at 05:22:15AM -0800, K F wrote: > >> [groups] > >> dev = rcrespo, test > >> dev1 = test > >> qa = qagroup > >> > >> [/DEF] > >> @dev = > >> @dev1 = rw > >> > >> [/] > >> @dev = rw > >> @qa = r > >> > >> I am still able to commit files in the DEF > directory using the rcrespo login. > > > > Hmmm... I think you'll have to revoke the dev's group > rw access on the root. > > Then grant write permissions to subtrees individually. > I suspect this is > > because permissions for all path components are > combined to form the final > > set of permissions for a given full path. > > > > The book was wrong about this for a long time. > > It claimed that permissions for earlier components of a > path were > > overridden by permissions for later components, which > is incorrect. > > I think that's misleading. The error in the book > involved a user > matching multiple lines for a single location, like the user > 'test' > above. When that happens the user gets the union of > all the > permissions, the book mistakenly claimed the first matching > line was > used. > > Using the rules above in a file z.z: > > $ tools/server-side/svnauthz-validate z.z rcrespo /ABC > user 'rcrespo' has rw access to '/ABC' > $ tools/server-side/svnauthz-validate z.z rcrespo /DEF > user 'rcrespo' has no access to '/DEF' > $ tools/server-side/svnauthz-validate z.z test /DEF > user 'test' has rw access to '/DEF' > > It appears the authz file is correct and denies rcrespo > access to /DEF. > > I suspect the problem is a failure to enable authz at > all--editing the > wrong config file, accessing the wrong repository, failed to > restart > apache, something like that. > > -- > Philip > I verified the file is correct. I tried committing with a login other than rcrespo or test and it does not allow the commit. Apache was restarted and I can still commit with rcrespo. Here is what is in svnserve.conf in case something is set wrong there: [general] anon-access = none auth-access = write password-db = passwd authz-db = authz
RE: Limited subdirectory access
I tried your suggestion of [/] *=r and I can still commit. So does that point to an error in svnserve.conf? --- On Tue, 1/31/12, Bob Archer wrote: > From: Bob Archer > Subject: RE: Limited subdirectory access > To: "K F" , "users@subversion.apache.org" > , "Thorsten Schöning" > Date: Tuesday, January 31, 2012, 2:46 PM > > I had already tried > > > > [/DEF] > > @dev = r > > @dev1 = rw > > > > and that did not work. > > Did you step back further. 1st, svn is case sensitive, so is > the path in question actually all upper case? > > Even further back than that... did you try to just give all > users read only access to root to ensure your path auth is > working at all? Something like: > > [/] > *=r > > Maybe even turn of anon access to ensure your authentication > is working as well. > > Add stuff one step at a time. > > BOb > > > > > > --- On Tue, 1/31/12, Thorsten Schöning > wrote: > > > > > From: Thorsten Schöning > > > Subject: Re: Limited subdirectory access > > > To: users@subversion.apache.org > > > Date: Tuesday, January 31, 2012, 8:04 AM Guten Tag > K F, am Montag, 30. > > > Januar 2012 um 23:20 schrieben Sie: > > > > > > > [ABC:/DEF] > > > > @dev = r > > > > @dev1 = rw > > > > > > > Do I need the ABC in the front? > > > > > > If it's just one repository your configuring your > authz file for,your > > > shouldn't need to specify ABC, so try without. If > this doesn't work, > > > you really should provide the whole authz file > with access rules for > > > all paths, groups, members and describe with which > user you login and > > > can commit to which folder. > > > > > > Mit freundlichen Grüßen, > > > > > > Thorsten Schöning > > > > > > -- > > > Thorsten Schöning E-Mail:thorsten.schoen...@am-soft.de > > > AM-SoFT IT-Systeme http://www.AM-SoFT.de/ > > > > > > Telefon.030-2 1001-310 > > > Fax...05151- 9468- 88 > > > Mobil..0178-8 9468- 04 > > > > > > AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, > 31789 Hameln AG > > > Hanover HRB 207 694 - Geschäftsführer: Andreas > Muchow > > > > > > >
RE: Limited subdirectory access
--- On Tue, 1/31/12, Bob Archer wrote: > From: Bob Archer > Subject: RE: Limited subdirectory access > To: "K F" , "users@subversion.apache.org" > , "Thorsten Schöning" > Date: Tuesday, January 31, 2012, 3:24 PM > > I tried your suggestion of > > > > [/] > > *=r > > > > and I can still commit. So does that point to an error > in svnserve.conf? > > > > Yes, something is not configured properly. You are using the > svn:// protocol to access your repository? > > BOb > > > > --- On Tue, 1/31/12, Bob Archer > wrote: > > > > > From: Bob Archer > > > Subject: RE: Limited subdirectory access > > > To: "K F" , > "users@subversion.apache.org" > > > , > "Thorsten Schöning" > > > > > > Date: Tuesday, January 31, 2012, 2:46 PM > > > > I had already tried > > > > > > > > [/DEF] > > > > @dev = r > > > > @dev1 = rw > > > > > > > > and that did not work. > > > > > > Did you step back further. 1st, svn is case > sensitive, so is the path > > > in question actually all upper case? > > > > > > Even further back than that... did you try to just > give all users read > > > only access to root to ensure your path auth is > working at all? > > > Something like: > > > > > > [/] > > > *=r > > > > > > Maybe even turn of anon access to ensure your > authentication is > > > working as well. > > > > > > Add stuff one step at a time. > > > > > > BOb > > > > > > If I understand the question, yes. For the dir in question it is svn://subversion/svnrepo/sandbox/DEF
RE: Limited subdirectory access
--- On Tue, 1/31/12, K F wrote: > From: K F > Subject: RE: Limited subdirectory access > To: "users@subversion.apache.org" , "Thorsten > Schöning" , "Bob Archer" > Date: Tuesday, January 31, 2012, 3:29 PM > > > --- On Tue, 1/31/12, Bob Archer > wrote: > > > From: Bob Archer > > Subject: RE: Limited subdirectory access > > To: "K F" , > "users@subversion.apache.org" > , > "Thorsten Schöning" > > Date: Tuesday, January 31, 2012, 3:24 PM > > > I tried your suggestion of > > > > > > [/] > > > *=r > > > > > > and I can still commit. So does that point to an > error > > in svnserve.conf? > > > > > > > Yes, something is not configured properly. You are > using the > > svn:// protocol to access your repository? > > > > BOb > > > > > > > --- On Tue, 1/31/12, Bob Archer > > wrote: > > > > > > > From: Bob Archer > > > > Subject: RE: Limited subdirectory access > > > > To: "K F" , > > "users@subversion.apache.org" > > > > , > > "Thorsten Schöning" > > > > > > > > Date: Tuesday, January 31, 2012, 2:46 PM > > > > > I had already tried > > > > > > > > > > [/DEF] > > > > > @dev = r > > > > > @dev1 = rw > > > > > > > > > > and that did not work. > > > > > > > > Did you step back further. 1st, svn is case > > sensitive, so is the path > > > > in question actually all upper case? > > > > > > > > Even further back than that... did you try to > just > > give all users read > > > > only access to root to ensure your path auth > is > > working at all? > > > > Something like: > > > > > > > > [/] > > > > *=r > > > > > > > > Maybe even turn of anon access to ensure > your > > authentication is > > > > working as well. > > > > > > > > Add stuff one step at a time. > > > > > > > > BOb > > > > > > > > > > If I understand the question, yes. For the dir in question > it is > > svn://subversion/svnrepo/sandbox/DEF > I discovered what MY issue was. In the svnserve.conf file there were duplicate entries for anon-access = auth-access = Once I removed the duplicate entries and just had anon-access = none auth-access = write it started working as it should have. Thank you all for your patience and help. The whole thing was a learning process for me. Rich
Trouble with authorization
The repo in on a Unix box located at svnrepo/sandbox accessing via tortoise on a windows machine with the latest releases. When I try to do a commit as user dev1, psswd dev1, I get the following error: Command: Commit Error: Commit failed (details follow): Error: Authorization failed Finished!: I am not sure what is wrong. I did some searching on the web and can’t find anything wrong with what I am doing. Here is what I have in the pertinent files. passwd file: dev1 = dev1 dev2 = dev2 dev3 = dev3 authz file: [aliases] [groups] deva = dev1, dev2 devb = dev3 [svnrepo/sandbox:/] deva = rw devb = r svnserve.conf file: [general] anon-access=none auth-access=write password-db=passwd authz-db=authz
RE: Trouble with authorization
> From: K F [mailto:cmkfo...@yahoo.com] > Sent: 05 May 2010 20:43 > > The repo in on a Unix box located at svnrepo/sandbox > accessing via tortoise on a windows machine with the latest > releases. When I try to do a commit as user dev1, psswd dev1, > I get the following error: > > Command: Commit > Error: Commit failed (details follow): > Error: Authorization failed > Finished!: > > I am not sure what is wrong. I did some searching on the web > and can't find anything wrong with what I am doing. Here is > what I have in the pertinent files. > > passwd file: > dev1 = dev1 > dev2 = dev2 > dev3 = dev3 > > authz file: > [aliases] > > [groups] > deva = dev1, dev2 > devb = dev3 > > [svnrepo/sandbox:/] > deva = rw > devb = r Personally I had some issues with using [groups] that I unfotunately did not have time to resolve. I suggest that you start by using the usernames (dev1 etc) directly in the authz file to test: Also, I think that [svnrepo/sandbox:/] is wrong. I would only ever expect to see one name before the slash (a specific repo in a parentpath setup) then the path within the repo comes after the ":/". [sandbox:/] dev1 = rw dev2 = rw dev3 = r If you only have one repo / are not using parentpath then you can just set the default global access level: [/] dev1 = rw dev2 = rw dev3 = r Are you using parentpath in your setup? Unless your client is 1.6.11+, you need to grant read access to the root (you do seem to be doing that, just thought it worth mentioning). Finally, a link to path-based authorization in the nightly red book: http://svnbook.red-bean.com/nightly/en/svn.serverconfig.pathbasedauthz.html ~ mark c > svnserve.conf file: > [general] > anon-access=none > auth-access=write > > password-db=passwd > > authz-db=authz > Mark, I looked at the link you offered for Path-Based Authorization and really didn't see anything that I haven't tried. Based on your suggestions, to get it to work I am not using groups and am simply using the usernames. [/] dev1 = rw dev2 = rw dev3 = r As you can see I am also using the global level access. This all seems to work. I would still like to try and get the groups to work if anyone has any other ideas. Thanks, Rich
RE: Trouble with authorization
> > From: K F [mailto:cmkfo...@yahoo.com] > > Sent: 05 May 2010 20:43 > > > > The repo in on a Unix box located at svnrepo/sandbox > > accessing via tortoise on a windows machine with the latest > > releases. When I try to do a commit as user dev1, psswd dev1, > > I get the following error: > > > > Command: Commit > > Error: Commit failed (details follow): > > Error: Authorization failed > > Finished!: > > > > I am not sure what is wrong. I did some searching on the web > > and can't find anything wrong with what I am doing. Here is > > what I have in the pertinent files. > > > > passwd file: > > dev1 = dev1 > > dev2 = dev2 > > dev3 = dev3 > > > > authz file: > > [aliases] > > > > [groups] > > deva = dev1, dev2 > > devb = dev3 > > > > [svnrepo/sandbox:/] > > deva = rw > > devb = r > > Personally I had some issues with using [groups] that I > unfotunately did > not have time to resolve. I suggest that you start by using the > usernames (dev1 etc) directly in the authz file to test: > > Also, I think that [svnrepo/sandbox:/] is wrong. I would only ever > expect to see one name before the slash (a specific repo in a > parentpath > setup) then the path within the repo comes after the ":/". > > [sandbox:/] > dev1 = rw > dev2 = rw > dev3 = r > > If you only have one repo / are not using parentpath then you can just > set the default global access level: > > [/] > dev1 = rw > dev2 = rw > dev3 = r > > Are you using parentpath in your setup? Unless your client > is 1.6.11+, > you need to grant read access to the root (you do seem to be > doing that, > just thought it worth mentioning). > > Finally, a link to path-based authorization in the nightly red book: > http://svnbook.red-bean.com/nightly/en/svn.serverconfig.pathbasedauthz.h tml > > > ~ mark c > > > svnserve.conf file: > > [general] > > anon-access=none > > auth-access=write > > > > password-db=passwd > > > > authz-db=authz > > > From: K F [mailto:cmkfo...@yahoo.com] > Sent: 06 May 2010 13:36 > > Mark, > > I looked at the link you offered for Path-Based Authorization > and really didn't see anything that I haven't tried. Based on > your suggestions, to get it to work I am not using groups and > am simply using the usernames. > > [/] > dev1 = rw > dev2 = rw > dev3 = r > > As you can see I am also using the global level access. This > all seems to work. I would still like to try and get the > groups to work if anyone has any other ideas. > > Thanks, > Rich > Dang! I missed the obvious problem which is that according to the Red Book link you need to prefix group names with '@' which gives:- > authz file: > [aliases] > > [groups] > deva = dev1, dev2 > devb = dev3 > > [svnrepo/sandbox:/] > @deva = rw > @devb = r ...let me know if it works! (and for completeness: Aliases need to be prefixed by '&' which does work for me) Hmm, perhaps my problem with groups was trying to create groups just of aliases e.g. [aliases] user1=joe90 user2=adameve user3=spod [groups] devs=&user1, &user2 test=&user2, &user3 [/] @devs = rw @test = r Can anyone else confirm if this should /does (not) work? ~ mark c Mark, I had seen that in the book also and tried it with no luck. My latest try was: [aliases] dev10 = dev1 dev20 = dev2 dev30 = dev3 [groups] deva = &dev10, &dev20 devb = &dev30 [/] &deva = rw &devb = r This returns an error on commit of: Error: Commit failed (details follow): Error: An authz rule refers to alias '&deva', which is undefined Still looking at it to see if it something I am just missing sometjhing or doing something wrong. Rich
RE: Trouble with authorization
> > From: K F [mailto:cmkfo...@yahoo.com] > > Sent: 05 May 2010 20:43 > > > > The repo in on a Unix box located at svnrepo/sandbox > > accessing via tortoise on a windows machine with the latest > > releases. When I try to do a commit as user dev1, psswd dev1, > > I get the following error: > > > > Command: Commit > > Error: Commit failed (details follow): > > Error: Authorization failed > > Finished!: > > > > I am not sure what is wrong. I did some searching on the web > > and can't find anything wrong with what I am doing. Here is > > what I have in the pertinent files. > > > > passwd file: > > dev1 = dev1 > > dev2 = dev2 > > dev3 = dev3 > > > > authz file: > > [aliases] > > > > [groups] > > deva = dev1, dev2 > > devb = dev3 > > > > [svnrepo/sandbox:/] > > deva = rw > > devb = r > > Personally I had some issues with using [groups] that I > unfotunately did > not have time to resolve. I suggest that you start by using the > usernames (dev1 etc) directly in the authz file to test: > > Also, I think that [svnrepo/sandbox:/] is wrong. I would only ever > expect to see one name before the slash (a specific repo in a > parentpath > setup) then the path within the repo comes after the ":/". > > [sandbox:/] > dev1 = rw > dev2 = rw > dev3 = r > > If you only have one repo / are not using parentpath then you can just > set the default global access level: > > [/] > dev1 = rw > dev2 = rw > dev3 = r > > Are you using parentpath in your setup? Unless your client > is 1.6.11+, > you need to grant read access to the root (you do seem to be > doing that, > just thought it worth mentioning). > > Finally, a link to path-based authorization in the nightly red book: > http://svnbook.red-bean.com/nightly/en/svn.serverconfig.pathbasedauthz.h tml > > > ~ mark c > > > svnserve.conf file: > > [general] > > anon-access=none > > auth-access=write > > > > password-db=passwd > > > > authz-db=authz > > > From: K F [mailto:cmkfo...@yahoo.com] > Sent: 06 May 2010 13:36 > > Mark, > > I looked at the link you offered for Path-Based Authorization > and really didn't see anything that I haven't tried. Based on > your suggestions, to get it to work I am not using groups and > am simply using the usernames. > > [/] > dev1 = rw > dev2 = rw > dev3 = r > > As you can see I am also using the global level access. This > all seems to work. I would still like to try and get the > groups to work if anyone has any other ideas. > > Thanks, > Rich > Dang! I missed the obvious problem which is that according to the Red Book link you need to prefix group names with '@' which gives:- > authz file: > [aliases] > > [groups] > deva = dev1, dev2 > devb = dev3 > > [svnrepo/sandbox:/] > @deva = rw > @devb = r ...let me know if it works! (and for completeness: Aliases need to be prefixed by '&' which does work for me) Hmm, perhaps my problem with groups was trying to create groups just of aliases e.g. [aliases] user1=joe90 user2=adameve user3=spod [groups] devs=&user1, &user2 test=&user2, &user3 [/] @devs = rw @test = r Can anyone else confirm if this should /does (not) work? ~ mark c Mark, I had seen that in the book also and tried it with no luck. My latest try was: [aliases] dev10 = dev1 dev20 = dev2 dev30 = dev3 [groups] deva = &dev10, &dev20 devb = &dev30 [/] &deva = rw &devb = r This returns an error on commit of: Error: Commit failed (details follow): Error: An authz rule refers to alias '&deva', which is undefined Still looking at it to see if it something I am just missing sometjhing or doing something wrong. Rich === So I inserted an & instead of a @ at the bottom and that fixed things. @deva = rw @devb = r Just to clarify, in order to use authz you need to set up aliases? Unless I set aliases up it doesn't appear to work. Looking at the book, I do not see why aliases are required. If anyone can explain the reasoning or explain why I am wrong I would appreciate it. Thanks, Rich
RE: Trouble with authorization
> > From: K F [mailto:cmkfo...@yahoo.com] > > Sent: 05 May 2010 20:43 > > > > The repo in on a Unix box located at svnrepo/sandbox > > accessing via tortoise on a windows machine with the latest > > releases. When I try to do a commit as user dev1, psswd dev1, > > I get the following error: > > > > Command: Commit > > Error: Commit failed (details follow): > > Error: Authorization failed > > Finished!: > > > > I am not sure what is wrong. I did some searching on the web > > and can't find anything wrong with what I am doing. Here is > > what I have in the pertinent files. > > > > passwd file: > > dev1 = dev1 > > dev2 = dev2 > > dev3 = dev3 > > > > authz file: > > [aliases] > > > > [groups] > > deva = dev1, dev2 > > devb = dev3 > > > > [svnrepo/sandbox:/] > > deva = rw > > devb = r > > Personally I had some issues with using [groups] that I > unfotunately did > not have time to resolve. I suggest that you start by using the > usernames (dev1 etc) directly in the authz file to test: > > Also, I think that [svnrepo/sandbox:/] is wrong. I would only ever > expect to see one name before the slash (a specific repo in a > parentpath > setup) then the path within the repo comes after the ":/". > > [sandbox:/] > dev1 = rw > dev2 = rw > dev3 = r > > If you only have one repo / are not using parentpath then you can just > set the default global access level: > > [/] > dev1 = rw > dev2 = rw > dev3 = r > > Are you using parentpath in your setup? Unless your client > is 1.6.11+, > you need to grant read access to the root (you do seem to be > doing that, > just thought it worth mentioning). > > Finally, a link to path-based authorization in the nightly red book: > http://svnbook.red-bean.com/nightly/en/svn.serverconfig.pathbasedauthz.h tml > > > ~ mark c > > > svnserve.conf file: > > [general] > > anon-access=none > > auth-access=write > > > > password-db=passwd > > > > authz-db=authz > > > From: K F [mailto:cmkfo...@yahoo.com] > Sent: 06 May 2010 13:36 > > Mark, > > I looked at the link you offered for Path-Based Authorization > and really didn't see anything that I haven't tried. Based on > your suggestions, to get it to work I am not using groups and > am simply using the usernames. > > [/] > dev1 = rw > dev2 = rw > dev3 = r > > As you can see I am also using the global level access. This > all seems to work. I would still like to try and get the > groups to work if anyone has any other ideas. > > Thanks, > Rich > Dang! I missed the obvious problem which is that according to the Red Book link you need to prefix group names with '@' which gives:- > authz file: > [aliases] > > [groups] > deva = dev1, dev2 > devb = dev3 > > [svnrepo/sandbox:/] > @deva = rw > @devb = r ...let me know if it works! (and for completeness: Aliases need to be prefixed by '&' which does work for me) Hmm, perhaps my problem with groups was trying to create groups just of aliases e.g. [aliases] user1=joe90 user2=adameve user3=spod [groups] devs=&user1, &user2 test=&user2, &user3 [/] @devs = rw @test = r Can anyone else confirm if this should /does (not) work? ~ mark c Mark, I had seen that in the book also and tried it with no luck. My latest try was: [aliases] dev10 = dev1 dev20 = dev2 dev30 = dev3 [groups] deva = &dev10, &dev20 devb = &dev30 [/] &deva = rw &devb = r This returns an error on commit of: Error: Commit failed (details follow): Error: An authz rule refers to alias '&deva', which is undefined Still looking at it to see if it something I am just missing sometjhing or doing something wrong. Rich === So I inserted an & instead of a @ at the bottom and that fixed things. @deva = rw @devb = r Just to clarify, in order to use authz you need to set up aliases? Unless I set aliases up it doesn't appear to work. Looking at the book, I do not see why aliases are required. If anyone can explain the reasoning or explain why I am wrong I would appreciate it. Thanks, Rich === More testing reveals that aliases are not needed. Here is what works: With Groups [aliases] dev10 = dev1 dev20 = dev2 dev30 = dev3 [groups] deva = &dev10, &dev20 devb = &dev30 [/] @deva = rw @devb = r -- Without Groups [aliases] [groups] deva = dev1, dev2 devb = dev3 [/] @deva = rw @devb = r My problem was that I thought the ampersand was only necessary if you used aliases. I hope this helps anyone else that may have had problems. Rich
RE: Trouble with authorization
You are correct. With and with out aliases. Sometimes my fingers just don't listen to what my mind tells them to type. --- On Fri, 5/7/10, Bob Archer wrote: From: Bob Archer Subject: RE: Trouble with authorization To: "K F" , "MarkCooke" Cc: "Subversion Users" Date: Friday, May 7, 2010, 5:08 PM > More testing reveals that aliases are not needed. Here is what works: > > With Groups I assume here you mean "with aliases" > > [aliases] > dev10 = dev1 > dev20 = dev2 > dev30 = dev3 > > [groups] > deva = &dev10, &dev20 > devb = &dev30 > > [/] > @deva = rw > @devb = r > > -- > > Without Groups and here you mean "without aliases" > > [aliases] > > [groups] > deva = dev1, dev2 > devb = dev3 > > [/] > @deva = rw > @devb = r > > My problem was that I thought the ampersand was only necessary if you used > aliases. > > I hope this helps anyone else that may have had problems. > > Rich In both cases you are using groups. BOb
Functionality change request for revision compare
I was comparing two tags and if I select the older revision first it correctly shows a folder and the files under it as added. If I select the newer one first it shows the same directory as deleted but does not show the files under it as deleted. Is there a reason why it could not show the files under it as deleted? By not showing the files there is no reference to them as being a difference between the tags. It does the same thing if you just check between revisions. Thanks, Rich
