Re: svnadmin create repo/path - Error
Hi No, it does. I have run this command on linux (RHEL4) on local path. It creates. However, in this case, even if I mention the full path then also, it is giving this error. Btw, the path is nfs mounted. Regards, Rajesh On Fri, Feb 11, 2011 at 1:07 PM, Curley, John john.cur...@windriver.comwrote: -Original Message- From: Rajesh Saha [mailto:rajeshsaha...@gmail.com] Sent: Thursday, February 10, 2011 10:46 PM To: users@subversion.apache.org Subject: Re: svnadmin create repo/path - Error Hi I was trying to create a repository with this command. svnadmin create --fs-type fsfs newrepo But, it is giving error as follows. svnadmin: Repository creation failed svnadmin: Creating db lock file svnadmin: Can't open file 'newrepo/locks/db.lock': Permission denied My SVN version is 1.5.6. The OS is Solaris 8 Anybody have any idea/resolution ? Thanks in advance, Rajesh Hi, According to 'Version Control with Subversion', chapter 5, section 'Creating and Configuration Your Repository', the command should resemble: svnadmin create --fs-type fsfs /var/svn/repos Where you specify the path to your repository in place of /var/svn/repos. It does not understand your current location. HTH, John
Re: Subversion Permissions Question.
Guten Tag MonicaS, am Donnerstag, 10. Februar 2011 um 17:33 schrieben Sie: We are using an old version that we are going to upgrade as soon as we are confident that we understand the current configuration and setup. It should be possible to upgrade to a newer version even without understanding, because unless you dump and load your repositories, the old format and configuration is kept and should just work. You would just loose benefits of newer FSFS-versions or stuff like that, but can dump and load whenever you like. The authz file contains the following three lines. If I understood correctly, svnadmin will have rw permissions to the whole repository and the rest of the users will have read-only access. But all users are able to 'checkout' and 'submit' files. So what are these permissions really doing? [/] svnadmin = rw * = r Which users are in the group svadmin? If all, then all should be able to commit etc. I see the files svnserve.conf and authz on different subdirectories. Shouldn't these files be only in the main or initial folders of the repository? Per default those files should be in the conf-directory of the repository, but the location of authz can be configured in svnserve.conf. ### Uncomment the line below to use the default authorization file. authz-db = authz vs. ### Uncomment the line below to use the default authorization file. authz-db = ../../foo/bar/authz Other questions that I have are: - How can I get a full repository layout? svn help list svn list -R - How can I get the repository history since the revision 0 to the newest? svn help log svn log -r 0:HEAD - How can I get the list of revisions or commits for the whole repository? I'm doing using 'svn log' but I only get the current folder not recursive to the whole repo. The list of revisions euqals the log history, in your working copy you have to change to the root of the working copy. Also, I don't think I understand when a repository is a repository and when it is a directory under that repository. I checked some of the folders under the repository directory structure and I found that i can follow the directory structure up to certain point and then I cannot. For example: svn+ssh://user@server/Repo_name/main_folder1 Repo_name should be the repository itself, everything beneath is content in it. The repository is the name of the folder which has db, hooks, conf etc. a s subfolders in your file system. I cannot follow using a normal cd command the directory level of 'trunk', 'branches' and 'tags' in the repository directory. I only have the folders conf, dav, db,format, hooks, locks, README.txt but not 'branches', 'tags' and 'trunk'. The contents of the repository is unknown to your file system, therefore you need svn tools. svn help ls So, are main_folder1 and main_folder2 two different repositories or only one under Repo_name? Should be one under Repo_name, depending on the name of the folder with db, hooks etc. in it. Where I can find information about the database FSFS layout, schema and design? Maybe in the subversion sources, I don't know. But do you really think you need those information for administration purposes? 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
Re: svnadmin create complains about subrepositories
Am Thu, 10 Feb 2011 14:27:17 -0600 schrieb Ryan Schmidt subversion-20...@ryandesign.com: $ svnadmin create repo1 $ svnadmin create repo1/repo2 svnadmin: 'repo1/repo2' is a subdirectory of an existing repository rooted at 'repo1' $ svnadmin create repo2 $ mv repo2 repo1 $ ls repo1 README.txtdb hooks repo2 conf format locks $ Et voilà, you have repo2's directory inside repo1's directory. Yes, this is the only way I would be able to do it, though its a pretty nasty thing if you have scripts, creating your repositories on the fly. Again because noone really understood the problem: I need nested repositories because without I can not grant granular access rights. Eg: I have a redmine project called x and a repository called x. I have access to that repos and some other dudes. Now I need to create a new subproject that belongs virtually to x called z. To maintain this connection I want it to be visible within redmine as a subproject to x. I also want to grant access to that project to different people than I granted to x. Still I need to maintain the connection to x and hence the need of creating subrepositories... Funny noone of you mentioned one damn reason why the force option would be bad. You just said Its not like we want it to be but apart from that, your argumentation is not present. signature.asc Description: PGP signature
Re: svnadmin create complains about subrepositories
Guten Tag Fabian Richter, am Freitag, 11. Februar 2011 um 10:18 schrieben Sie: I also want to grant access to that project to different people than I granted to x. authz-file and it's directory dependant permissions doesn't fit your needs? Funny noone of you mentioned one damn reason why the force option would be bad. You just said Its not like we want it to be but apart from that, your argumentation is not present. The reasons was mentioned: It's unlikely that the devs want to maintain such a setup. If they provide a switch to enforce such a setup, it becomes some kind of an official way to create a setup nobody really seem to want and whoever used the switch to create such a repository layout will blame the devs if they do something in future which is incompatible with this layout, because one just used the --force option. Especially if you are using scripts to create your layout, it should be fairly simple to add a directory move. 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
RE: svnadmin create complains about subrepositories
-Original Message- From: Fabian Richter [mailto:fabian.rich...@trust.cased.de] Sent: 11 February 2011 09:18 To: users@subversion.apache.org Subject: Re: svnadmin create complains about subrepositories Am Thu, 10 Feb 2011 14:27:17 -0600 schrieb Ryan Schmidt subversion-20...@ryandesign.com: $ svnadmin create repo1 $ svnadmin create repo1/repo2 svnadmin: 'repo1/repo2' is a subdirectory of an existing repository rooted at 'repo1' $ svnadmin create repo2 $ mv repo2 repo1 $ ls repo1 README.txt db hooks repo2 confformat locks $ Et voilà, you have repo2's directory inside repo1's directory. Yes, this is the only way I would be able to do it, though its a pretty nasty thing if you have scripts, creating your repositories on the fly. I personally think what you are trying to do is pretty nasty. Again because noone really understood the problem: I need nested repositories because without I can not grant granular access rights. Have you read the subversion book and in particular the parts about path based authorisation? http://svnbook.red-bean.com/nightly/en/svn.serverconfig.pathbasedauthz.html Perhaps noone understood because you asked how to _do_ something specific (which people are cautioning you against) without asking how you can achieve what you _need_ in a way that subversion is designed for and supports? Having said that... Eg: I have a redmine project called x and a repository called x. I have access to that repos and some other dudes. Now I need to create a new subproject that belongs virtually to x called z. To maintain this connection I want it to be visible within redmine as a subproject to x. I also want to grant access to that project to different people than I granted to x. Still I need to maintain the connection to x and hence the need of creating subrepositories... I think you can do all that by creating your (sub)hierarchy within the 'x' repository and using path based authorisation. The most specific path is used for auth so subproject 'z' can have its own auth which overrides that given to 'x'. Unless this conflicts some specific requirement(s) of RedMine that you have not mentioned? What source control does RedMine normally work with? Perhaps you would be better off using that? Funny noone of you mentioned one damn reason why the force option would be bad. You just said Its not like we want it to be but apart from that, your argumentation is not present. One IMHO very good argument was mentioned and you ignored it: you would not dream of messing around inside the file-system location of e.g. PostgreSQL database data files yet that is exactly what you are proposing to do with the subversion system. Are you proposing only to use File:\\ repo access? As also mentioned, implementing what you are asking for may cause unnecessary implementation constraints for the project in the future by implicitly supporting a possibly unique use case? Finally I am wondering: how are you proposing to provide access to the repositories? I shudder to think of the sort of apache config that would be required to serve a repo from inside another repos folder... Subversion supports paths inside repositories and grouping of repos using ParentPaths, all with authorisation mechanisms that satisfy most existing users. ~ mark c
Re: svnadmin create repo/path - Error
On Fri, Feb 11, 2011 at 02:59, Rajesh Saha rajeshsaha...@gmail.com wrote: Hi No, it does. I have run this command on linux (RHEL4) on local path. It creates. However, in this case, even if I mention the full path then also, it is giving this error. Btw, the path is nfs mounted. When you put a repository on an NFS mount, it must be configured properly for file locking. See http://subversion.apache.org/faq.html#nfs On Fri, Feb 11, 2011 at 1:07 PM, Curley, John john.cur...@windriver.com wrote: -Original Message- From: Rajesh Saha [mailto:rajeshsaha...@gmail.com] Sent: Thursday, February 10, 2011 10:46 PM To: users@subversion.apache.org Subject: Re: svnadmin create repo/path - Error Hi I was trying to create a repository with this command. svnadmin create --fs-type fsfs newrepo But, it is giving error as follows. svnadmin: Repository creation failed svnadmin: Creating db lock file svnadmin: Can't open file 'newrepo/locks/db.lock': Permission denied My SVN version is 1.5.6. The OS is Solaris 8 Anybody have any idea/resolution ? Thanks in advance, Rajesh Hi, According to 'Version Control with Subversion', chapter 5, section 'Creating and Configuration Your Repository', the command should resemble: svnadmin create --fs-type fsfs /var/svn/repos Where you specify the path to your repository in place of /var/svn/repos. It does not understand your current location. HTH, John
Strange tree conflict problem
HI! I am merging the diff between branch A and branch B to a working copy of branch C. Now I get a tree conflict for some files. TortoiseSVN 1.6.12 says The last merge operation tried to delete/move/rename the file 'name', but it was already edited. I also get a tree conflict, if I do the merge with the svn commandline client 1.6.12. The strange thing is: When I do a diff between the file in branch A and in branch B, it is not different at all. So what does it want to merge? Also, the file does exist in the target working copy and it is not locally modified. Our server runs svn 1.6.13. Any help would be greatly appreciated. Thomas
svn externals
Hi all, In my project I need to use a library that's only available using git, I wonder if there is some way to have svn:externals point to a git repo (just doing a git pull) ? TIA /Rob
RE: svnadmin create complains about subrepositories
On Thursday 10 February 2011, Stefan Sperling wrote: On Thu, Feb 10, 2011 at 07:02:18PM +0100, Fabian Richter wrote: Am Thu, 10 Feb 2011 11:24:09 -0600 schrieb Ryan Schmidt subversion-20...@ryandesign.com: On Feb 10, 2011, at 09:59, Stefan Sperling wrote: and can you please add an --force switch to still being able to create Repositories within the path of another? That's a reasonable request, I think. Not a usual use case but why not? Really? What possible reason could exist for doing this? :) I have no idea, to be honest. But then again I'm not going to guess. Maybe someone can present a good use case for this? Dunno. The only reason I'm aware of is that you want to make browsing easier when you have multiple repositories, as there is otherwise no way to do that. The idea is that you have a parent FS-dir that contains the parent repo. The parent repo FS-contains the child repos. Further, it has repo-directories for each child repository, too. Since SVN tries to walk the FS-path as far as possible for locating the repository. Therefore, a svn ls parent will show the repo-content of the parent's root but a svn ls parent/child-x will not show the repo-content of the parent's child-x subdir but show the root of the parent/child-x repository. In that light, I support the suggested --force option for people that really, really need it. If I have a project that has child sub-project I really really want them to be in the same repository. Actually, I put all my projects in the same repository so I can browser them in some repository browser like T-SVN of ViewVC. We have multiple repositories but they are for different product groups that work on projects that have no relationship to each other what so ever. Even those could be in the same repository but seeing how path based auth slows things down it seemed to make more sense to give each product group their own repo. BOb
RE: svnadmin create complains about subrepositories
Am Thu, 10 Feb 2011 14:27:17 -0600 schrieb Ryan Schmidt subversion-20...@ryandesign.com: $ svnadmin create repo1 $ svnadmin create repo1/repo2 svnadmin: 'repo1/repo2' is a subdirectory of an existing repository rooted at 'repo1' $ svnadmin create repo2 $ mv repo2 repo1 $ ls repo1 README.txt db hooks repo2 confformat locks $ Et voilà, you have repo2's directory inside repo1's directory. Yes, this is the only way I would be able to do it, though its a pretty nasty thing if you have scripts, creating your repositories on the fly. Again because noone really understood the problem: I need nested repositories because without I can not grant granular access rights. Eg: I have a redmine project called x and a repository called x. I have access to that repos and some other dudes. Now I need to create a new subproject that belongs virtually to x called z. To maintain this connection I want it to be visible within redmine as a subproject to x. I also want to grant access to that project to different people than I granted to x. Still I need to maintain the connection to x and hence the need of creating subrepositories... Funny noone of you mentioned one damn reason why the force option would be bad. You just said Its not like we want it to be but apart from that, your argumentation is not present. Have you brought this up on the redmine support or users list? It seems to me that more than one person would be using nested projects in RedMine and since nested repositories in svn is an anti-pattern I expect there is a better way to do this... or you are not understanding RedMine's sub-projects... or there is a deficiency in redminds security that doesn't allow you to set different permissions to a nested subprojects in a single repository. Perhaps redmine doesn't require the nested projects to actually point to nested repositories? BOb
Re: svnadmin create complains about subrepositories
Stefan Sperling wrote on Thu, Feb 10, 2011 at 16:59:11 +0100: But I also think that the check for an existing repository should work within any subdirectory of the repository, not just within the top-level directory of the repository. Can you help by filing a DEFECT issue in our issue tracker (http://subversion.tigris.org/issue-tracker.html) requesting that the check be expanded to also work within subdirectories of a repository? Don't. It's already this way. Hyrum+I wrote it some time back. The reason? Because the URLs would be ambiguous: what should % svn info file://$PWD/path/to/dir/trunk | grep -i 'repository root:' print?
Re: svnadmin create repo/path - Error
1.5.6 has a known security hole, consider upgrading. Rajesh Saha wrote on Fri, Feb 11, 2011 at 12:16:22 +0530: Hi I was trying to create a repository with this command. svnadmin create --fs-type fsfs newrepo But, it is giving error as follows. svnadmin: Repository creation failed svnadmin: Creating db lock file svnadmin: Can't open file 'newrepo/locks/db.lock': Permission denied My SVN version is 1.5.6. The OS is Solaris 8 Anybody have any idea/resolution ? Thanks in advance, Rajesh
Re: Combining public and private paths
Workaround: you could run two svnserves with different configs, one allowing only anonymous access and only only authenticated access. I know httpd has the problem you're describing, I don't recall previous reports of it with svnserve. Victor Sudakov wrote on Thu, Feb 10, 2011 at 21:14:24 +0600: == conf/authz: [/] @noc = rw [/foo] $anonymous = r $authenticated = rw does not work. A valid user from the noc group receives the following reply: $ svn diff -c2237 www.txt svn: Unreadable path encountered; access denied It would be relevant to know www.txt absolute path.
Re: Do commit hooks work with the file:// protocol?
Jonathan Reeve wrote on Tue, Feb 08, 2011 at 17:19:54 +: I want to be able to prevent commits to a repository in some circumstances. I've set up a local svn repository to test, but my commit hook doesn't get called. I'm using the file:// protocol. Should hooks work with that? Yes unless your users use a patched svn(1) client that bypasses the hooks. (it's trivial to write a client that doesn't call hooks for file://; the default client does call hooks)
Re: svnadmin create complains about subrepositories
Daniel Shahaf wrote on Fri, Feb 11, 2011 at 19:16:24 +0200: The reason? Because the URLs would be ambiguous: what should % svn info file://$PWD/path/to/dir/trunk | grep -i 'repository root:' print? (forgot to say that both $PWD and $PWD/path/to are repositories)
Re: Combining public and private paths
Can two svnserves share one repository? There will be no data corruption, will there? Daniel Shahaf wrote: Workaround: you could run two svnserves with different configs, one allowing only anonymous access and only only authenticated access. I know httpd has the problem you're describing, I don't recall previous reports of it with svnserve. Victor Sudakov wrote on Thu, Feb 10, 2011 at 21:14:24 +0600: == conf/authz: [/] @noc = rw [/foo] $anonymous = r $authenticated = rw does not work. A valid user from the noc group receives the following reply: $ svn diff -c2237 www.txt svn: Unreadable path encountered; access denied It would be relevant to know www.txt absolute path. -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN sip:suda...@sibptus.tomsk.ru
What is a baton from subversion sources?
Hello. I'm learning subversion API right now and examining it's source code and examples. It's a lot of things in subversion source code that is called a baton. For example, svn_cmdline_create_auth_baton() create auth baton, and callbacks takes callback function pointer and, again, batons. I never heard of a term baton related to the programming. That is the baton concept subversion source code refers to? Maybe i can read somewhere about batons used in programming? Or is it a well-known term of some origin? Best, Grigory.
Re: What is a baton from subversion sources?
On Sat, Feb 12, 2011 at 1:01 AM, Grigory Petrov grigory@gmail.comwrote: Hello. I'm learning subversion API right now and examining it's source code and examples. It's a lot of things in subversion source code that is called a baton. For example, svn_cmdline_create_auth_baton() create auth baton, and callbacks takes callback function pointer and, again, batons. I never heard of a term baton related to the programming. That is the baton concept subversion source code refers to? Maybe i can read somewhere about batons used in programming? Or is it a well-known term of some origin? Probably dev list will be better place to ask such questions. Best, Grigory. -- Vishwajeet Singh +91-9657702154 | dextrou...@gmail.com | http://bootstraptoday.com Twitter: http://twitter.com/vishwajeets | LinkedIn: http://www.linkedin.com/in/singhvishwajeet
Re: Subversion Permissions Question.
On Feb 11, 3:21 am, Thorsten Schöning tschoen...@am-soft.de wrote: Guten Tag MonicaS, am Donnerstag, 10. Februar 2011 um 17:33 schrieben Sie: We are using an old version that we are going to upgrade as soon as we are confident that we understand the current configuration and setup. It should be possible to upgrade to a newer version even without understanding, because unless you dump and load your repositories, the old format and configuration is kept and should just work. You would just loose benefits of newer FSFS-versions or stuff like that, but can dump and load whenever you like. It is good to know that. I'm going to try to do it as soon as the team is ready. The authz file contains the following three lines. If I understood correctly, svnadmin will have rw permissions to the whole repository and the rest of the users will have read-only access. But all users are able to 'checkout' and 'submit' files. So what are these permissions really doing? [/] svnadmin = rw * = r Which users are in the group svadmin? If all, then all should be able to commit etc. only one user belong to the svnadmin group. I see the files svnserve.conf and authz on different subdirectories. Shouldn't these files be only in the main or initial folders of the repository? Per default those files should be in the conf-directory of the repository, but the location of authz can be configured in svnserve.conf. ### Uncomment the line below to use the default authorization file. authz-db = authz vs. ### Uncomment the line below to use the default authorization file. authz-db = ../../foo/bar/authz OK, so only the repositories have the sub-directories db, conf, dav, format, hooks and locks. If this is true, this installation looks like only one repository but I really have 506 repositories. I have repositories under repositories. Other questions that I have are: - How can I get a full repository layout? svn help list svn list -R - How can I get the repository history since the revision 0 to the newest? svn help log svn log -r 0:HEAD - How can I get the list of revisions or commits for the whole repository? I'm doing using 'svn log' but I only get the current folder not recursive to the whole repo. The list of revisions euqals the log history, in your working copy you have to change to the root of the working copy. Also, I don't think I understand when a repository is a repository and when it is a directory under that repository. I checked some of the folders under the repository directory structure and I found that i can follow the directory structure up to certain point and then I cannot. For example: svn+ssh://user@server/Repo_name/main_folder1 Repo_name should be the repository itself, everything beneath is content in it. The repository is the name of the folder which has db, hooks, conf etc. a s subfolders in your file system. I cannot follow using a normal cd command the directory level of 'trunk', 'branches' and 'tags' in the repository directory. I only have the folders conf, dav, db,format, hooks, locks, README.txt but not 'branches', 'tags' and 'trunk'. The contents of the repository is unknown to your file system, therefore you need svn tools. Again, this open my eyes, we have one folder and everybody thinks that we have only one repository, but we really have 506, I was confused. Thank you for clarifying. svn help ls So, are main_folder1 and main_folder2 two different repositories or only one under Repo_name? Should be one under Repo_name, depending on the name of the folder with db, hooks etc. in it. Where I can find information about the database FSFS layout, schema and design? Maybe in the subversion sources, I don't know. But do you really think you need those information for administration purposes? I really don't need this. I love databases and each of the configuration tools that I worked, I always try to understand the database structure. For example a lot of people don't like ClearCase but I was an CC administrator for a while and I loved the database, they have a lot of documentation. I also understood the Peforce and I enjoyed doing some test :-) Thank you for your answers. Monica 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
Re: diff-cmd =
On Fri, Feb 11, 2011 at 12:13:36PM +0600, Victor Sudakov wrote: Ryan Schmidt wrote: [dd] This looks like http://subversion.tigris.org/issues/show_bug.cgi?id=2930 i.e., you've found the current status quo; there is no better method currently available. I have always been told that I am a good tester (i.e. have the ability to come across bugs), but my rate of tripping on all the subversion rakes is alarming. This isn't particularly hard to fix, so it's an ideal problem for new contributors. This may be one reason why it hasn't been fixed yet. In the big picture, it doesn't hurt to let little problems like this linger. Most people will just write a wrapper script and move on. Too bad. But someone will eventually be looking for things to get their feet wet, and issues like this are ideal for that. Or it will annoy someone so much that they take the time to fix it. The existing developers have much harder sets of problems to juggle. And yes, of course, sometimes existing developers find time to fix simple problems like this. However we have a strong culture of encouraging new contributors so having issues like this open is also a good thing for the project. So, take the plunge if you can! Thanks.
Re: svnadmin create complains about subrepositories
On Fri, Feb 11, 2011 at 11:26:36AM -0500, Bob Archer wrote: Perhaps redmine doesn't require the nested projects to actually point to nested repositories? It doesn't. In redmine, each subproject has some repository location associated with it. For Subversion, that's a URL. So it can be in its own repos or some path within an existing repository shared with other projects. I would say that the project grouping in redmine is a *UI feature*. It has nothing to do with how things are stored on the server. The storage doesn't need to mirror what you see in the UI.
Re: svnadmin create complains about subrepositories
On Fri, Feb 11, 2011 at 07:16:24PM +0200, Daniel Shahaf wrote: Stefan Sperling wrote on Thu, Feb 10, 2011 at 16:59:11 +0100: But I also think that the check for an existing repository should work within any subdirectory of the repository, not just within the top-level directory of the repository. Can you help by filing a DEFECT issue in our issue tracker (http://subversion.tigris.org/issue-tracker.html) requesting that the check be expanded to also work within subdirectories of a repository? Don't. It's already this way. Hyrum+I wrote it some time back. The reason? Because the URLs would be ambiguous: what should % svn info file://$PWD/path/to/dir/trunk | grep -i 'repository root:' print? What has this got to do with running svnadmin create within repos/db or repos/hooks? Maybe you qouted the wrong paragraph and you were referring to the ENHANCEMENT I mentioned that would allow creating nested repositories? I've since changed my mind.
Re: Combining public and private paths
On Fri, Feb 11, 2011 at 11:55:08PM +0600, Victor Sudakov wrote: Can two svnserves share one repository? Yes. You can run as many server instances as you like, also with different access methods (e.g. http:// and svn:// at the same time). There will be no data corruption, will there? In general, no. There are some multi-access problems with BDB-based repositories running into issues with berkeleyDB where you might have to unwedge repositories using svnadmin recover: http://subversion.apache.org/faq.html#stuck-bdb-repos However, these days FSFS-based repositories are the default and they don't have that issue.
Re: svnadmin create complains about subrepositories
Stefan Sperling wrote on Fri, Feb 11, 2011 at 21:10:20 +0100: On Fri, Feb 11, 2011 at 07:16:24PM +0200, Daniel Shahaf wrote: Stefan Sperling wrote on Thu, Feb 10, 2011 at 16:59:11 +0100: But I also think that the check for an existing repository should work within any subdirectory of the repository, not just within the top-level directory of the repository. Can you help by filing a DEFECT issue in our issue tracker (http://subversion.tigris.org/issue-tracker.html) requesting that the check be expanded to also work within subdirectories of a repository? Don't. It's already this way. Hyrum+I wrote it some time back. The reason? Because the URLs would be ambiguous: what should % svn info file://$PWD/path/to/dir/trunk | grep -i 'repository root:' print? What has this got to do with running svnadmin create within repos/db or repos/hooks? Maybe you qouted the wrong paragraph and you were referring to the ENHANCEMENT I mentioned that would allow creating nested repositories? I've since changed my mind. I was trying to say that nested repositories are blocked (at any depth-distance) because any URL referring to the deeper repository could also refer to the parent/ancestor repository, and there's no way to resolve the ambiguity.
RE: Subversion Permissions Question.
On Feb 11, 3:21 am, Thorsten Schöning tschoen...@am-soft.de wrote: Guten Tag MonicaS, am Donnerstag, 10. Februar 2011 um 17:33 schrieben Sie: We are using an old version that we are going to upgrade as soon as we are confident that we understand the current configuration and setup. It should be possible to upgrade to a newer version even without understanding, because unless you dump and load your repositories, the old format and configuration is kept and should just work. You would just loose benefits of newer FSFS-versions or stuff like that, but can dump and load whenever you like. It is good to know that. I'm going to try to do it as soon as the team is ready. The authz file contains the following three lines. If I understood correctly, svnadmin will have rw permissions to the whole repository and the rest of the users will have read-only access. But all users are able to 'checkout' and 'submit' files. So what are these permissions really doing? [/] svnadmin = rw * = r Which users are in the group svadmin? If all, then all should be able to commit etc. only one user belong to the svnadmin group. Did you verify that subversion is actually configured to use the authz file? Just because it exists doesn't mean it is being used. I see the files svnserve.conf and authz on different subdirectories. Shouldn't these files be only in the main or initial folders of the repository? Per default those files should be in the conf-directory of the repository, but the location of authz can be configured in svnserve.conf. ### Uncomment the line below to use the default authorization file. authz-db = authz vs. ### Uncomment the line below to use the default authorization file. authz-db = ../../foo/bar/authz OK, so only the repositories have the sub-directories db, conf, dav, format, hooks and locks. If this is true, this installation looks like only one repository but I really have 506 repositories. I have repositories under repositories. That's not good. But are you sure about that. Where are you seeing 506 repositories? Perhaps you just have 506 projects in a single repository. BOb
RE: What is a baton from subversion sources?
I'm learning subversion API right now and examining it's source code and examples. It's a lot of things in subversion source code that is called a baton. For example, svn_cmdline_create_auth_baton() create auth baton, and callbacks takes callback function pointer and, again, batons. I never heard of a term baton related to the programming. That is the baton concept subversion source code refers to? Maybe i can read somewhere about batons used in programming? Or is it a well- known term of some origin? I don't know the svn code at all... but I expect it is analogous to a baton that relay race team uses. The first person starts running with the baton... he runs his leg and passes the baton to the next runner on the team... who takes it through his part of the course. So, I would expect that a baton is some symbol or reference to an object that is passed from one function to another and each function performs its responsibility modifying the baton or possible using information stored in the baton. BOb
Re: svn externals
On Feb 11, 2011, at 08:28, Robert Bielik wrote: In my project I need to use a library that's only available using git, I wonder if there is some way to have svn:externals point to a git repo (just doing a git pull) ? svn:externals is for accessing other (or the same) Subversion repositories only.
Re: What is a baton from subversion sources?
On Feb 11, 2011, at 13:31, Grigory Petrov wrote: I'm learning subversion API right now and examining it's source code and examples. It's a lot of things in subversion source code that is called a baton. For example, svn_cmdline_create_auth_baton() create auth baton, and callbacks takes callback function pointer and, again, batons. I never heard of a term baton related to the programming. That is the baton concept subversion source code refers to? Maybe i can read somewhere about batons used in programming? Or is it a well-known term of some origin? Google search for subversion baton gives: http://svn.haxx.se/dev/archive-2002-07/0396.shtml
Re: Subversion Permissions Question.
On Feb 11, 3:21 pm, Bob Archer bob.arc...@amsi.com wrote: On Feb 11, 3:21 am, Thorsten Schöning tschoen...@am-soft.de wrote: Guten Tag MonicaS, am Donnerstag, 10. Februar 2011 um 17:33 schrieben Sie: We are using an old version that we are going to upgrade as soon as we are confident that we understand the current configuration and setup. It should be possible to upgrade to a newer version even without understanding, because unless you dump and load your repositories, the old format and configuration is kept and should just work. You would just loose benefits of newer FSFS-versions or stuff like that, but can dump and load whenever you like. It is good to know that. I'm going to try to do it as soon as the team is ready. The authz file contains the following three lines. If I understood correctly, svnadmin will have rw permissions to the whole repository and the rest of the users will have read-only access. But all users are able to 'checkout' and 'submit' files. So what are these permissions really doing? [/] svnadmin = rw * = r Which users are in the group svadmin? If all, then all should be able to commit etc. only one user belong to the svnadmin group. Did you verify that subversion is actually configured to use the authz file? Just because it exists doesn't mean it is being used. Well, I checked all the svnserve.conf files, sometimes the line with the authz file was commented and sometimes it was not. The problem is that I have a lot of snvserve.conf files; I checked each of then, some have more permissions for users or groups. The one with svnadmin only was what I did think was the repository but inside of it I found at least 3 more repositories and on them I found the svnserve.conf using the authz file, and the authz file open the permissions for users. I see the files svnserve.conf and authz on different subdirectories. Shouldn't these files be only in the main or initial folders of the repository? Per default those files should be in the conf-directory of the repository, but the location of authz can be configured in svnserve.conf. ### Uncomment the line below to use the default authorization file. authz-db = authz vs. ### Uncomment the line below to use the default authorization file. authz-db = ../../foo/bar/authz OK, so only the repositories have the sub-directories db, conf, dav, format, hooks and locks. If this is true, this installation looks like only one repository but I really have 506 repositories. I have repositories under repositories. That's not good. But are you sure about that. Where are you seeing 506 repositories? Perhaps you just have 506 projects in a single repository. Well, I looked for all the folder with the subfolders conf, db,dav,format, hooks and locks and I found 506. Some of them are empty, for example I have the following: Eng-Tech/conf /dav /db /format /hooks /locks /README.txt ABC-SDKs/conf /dav /db /format /hooks /locks /README.txt J-SDKs/conf /dav /db /format /hooks /locks /README.txt If I'm understating correctly, the above directory structure have 3 repositories, one called Eng-Tech, another called ABC-SDKs and another called J-SDKs. If I check with tortoiseSVN or with SVN list to Eng-Tech I get the following: ABC-SDKs J-SDKs If I check with tortoiseSVN or with SVN list to ABC-SDK I get the following: A-SDKs B-SDKs C-SDKs This means that A thru C SDKs folder belong to the repository ABC-SDKs and J-SDKs belongs to the J-SDKs repository; and Eng-Tech is empty. This is why I'm or was confused. I wanted to understand why we have so many repositories. I noticed that some of the repositories are hard links to other file-systems. Maybe this was done because of the disk space... I don't know. Please let me know if my understanding is not correct. Thank you. Monica BOb
Re: svnadmin create complains about subrepositories
On 2/11/2011 10:22 AM, Bob Archer wrote: If I have a project that has child sub-project I really really want them to be in the same repository. Actually, I put all my projects in the same repository so I can browser them in some repository browser like T-SVN of ViewVC. Viewvc is perfectly happy to let you browse multiple repositories that are created in the same root directory. -- Les Mikesell lesmikes...@gmail.com
Re: svnadmin create repo/path - Error
On Fri, Feb 11, 2011 at 2:59 AM, Rajesh Saha rajeshsaha...@gmail.com wrote: Hi No, it does. I have run this command on linux (RHEL4) on local path. It creates. However, in this case, even if I mention the full path then also, it is giving this error. Btw, the path is nfs mounted. Regards, Rajesh Get *off* of RHEL 4. Seriously, it's no longer feasible to maintain the current Subversion with that OS. Jump up to RHEL 6, which has subversion-1.6.13, or at least update to RHEL 5 and use Subversion-1.6.16 from the RPMforge repository. The Subversion-1.4.2 that comes with RHEL 4 is dangerously out of date and should not be used in any production environment.
Dangerous to keep re-integrated branches alive?
Hi all, My development group uses quite a bit of branching. I'm trying to train folks to delete a task branch once it is integrated and create a new one for the next task. Of course the svnbook gives the recipe for Keeping a reintegrated branch alive, by using a record-only merge to block the integrated revision from being merged back to the task branch later on. (when sync-ing up the branch) It has always seemed to me that that is risky. If there were changes in the re-integration merge for conflict resolution, etc, then those changes are also being blocked from being merged back to the (kept-alive) task branch. Future changes on the task branch don't include those fixes and future re-integrations could potentially even over-write them (since the mergeinfo data says we're all up-to-date with respect to that prior revision). I hope that description is not too abstract. Am I worrying about a non-existent problem, or is there really potential to drop a change that should have gotten merged forward? I know we can always go back in history and find the change, but I'd rather set up our branch/merge process to be as correct as possible and not rely on testing to find that we dropped bit of code. TIA, -Steve
Re: Dangerous to keep re-integrated branches alive?
On Sat, Feb 12, 2011 at 1:10 PM, Varnau, Steve (Neoview) steve.var...@hp.com wrote: Hi all, My development group uses quite a bit of branching. I’m trying to train folks to delete a task branch once it is integrated and create a new one for the next task. Of course the svnbook gives the recipe for “Keeping a reintegrated branch alive”, by using a record-only merge to block the integrated revision from being merged back to the task branch later on. (when sync-ing up the branch) It has always seemed to me that that is risky. If there were changes in the re-integration merge for conflict resolution, etc, then those changes are also being blocked from being merged back to the (kept-alive) task branch. Future changes on the task branch don’t include those fixes and future re-integrations could potentially even over-write them (since the mergeinfo data says we’re all up-to-date with respect to that prior revision). My understanding is that this should never happen. During a reintegration merge, there is validation that all revisions from the target (normally /trunk) have been merged across into the branch - any conflict resolution is done during this merge. The reintegration merge then does a basic file compare, and merges across. After the reintegration merge, /trunk and the branch should be bit-by-bit identical. Period. If not, then either your use case for merging is a little strange, or there is a problem. Cheers, Daniel B.
Re: svn externals
Ryan Schmidt skrev 2011-02-11 22:20: On Feb 11, 2011, at 08:28, Robert Bielik wrote: In my project I need to use a library that's only available using git, I wonder if there is some way to have svn:externals point to a git repo (just doing a git pull) ? svn:externals is for accessing other (or the same) Subversion repositories only. Yes, I know, but I had hopes :) Wouldn't it be cool with a svn:command feature in which you'd be able to write a git pull command ? I.e. a generic property which executes written commands when you update ? ;) Rgrds, /Rob
