Re: Subversion Permissions Question.

2011-02-18 Thread Monica Gmail
Thank you very much for your help.

- Monica

On Feb 13, 2011, at 9:04 AM, Thorsten Schöning tschoen...@am-soft.de wrote:

 Guten Tag MonicaS,
 am Freitag, 11. Februar 2011 um 22:55 schrieben Sie:
 
 If I check with tortoiseSVN or with SVN list to Eng-Tech I get the
 following:
 
 ABC-SDKs
 J-SDKs
 
 I would think that this means that those directories are folders
 within the repo Eng-Tech, regardless of your file system structure,
 because svn list etc. doesn't combine file system level directories
 and repo level directories in their output. But they should have if
 those to folders where the repos beneath Eng-Tech in your file system.
 
 If I check with tortoiseSVN or with SVN list to ABC-SDK I get the
 following:
 
 A-SDKs
 B-SDKs
 C-SDKs
 
 This should be really the content of the repository itself.
 
 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.
 
 Maybe I'm wrong but I think Eng-Tech is not empty, but consists the
 folders you wrote first. Maybe Eng-Tech does have content, like the
 other repos unter Eng-Tech in the file system, but thos directories
 aren't used for some reason? Maybe your repos started that way,
 something didn't work as expected and things have changed?
 
 Are you able to rename the repos beneath Eng-Tech in your file system?
 That way nobody coudl use them anymore and you were really sure what
 is in the repo Eng-Tech and what is not. If you rename name ABC-SDKs
 to ABC-SDKs_ for some seconds, your svn list of Eng-Tech should
 refelct those renamings or it's clear that Eng-Tech does have content,
 the versioned directories ABC-SDKS and J-SDKs.
 
 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.
 
 In any case, your repo structure is not supported and you should
 change it after fully understanding it and possible.
 
 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: Subversion Permissions Question.

2011-02-13 Thread Thorsten Schöning
Guten Tag MonicaS,
am Freitag, 11. Februar 2011 um 22:55 schrieben Sie:

 If I check with tortoiseSVN or with SVN list to Eng-Tech I get the
 following:

 ABC-SDKs
 J-SDKs

I would think that this means that those directories are folders
within the repo Eng-Tech, regardless of your file system structure,
because svn list etc. doesn't combine file system level directories
and repo level directories in their output. But they should have if
those to folders where the repos beneath Eng-Tech in your file system.

 If I check with tortoiseSVN or with SVN list to ABC-SDK I get the
 following:

 A-SDKs
 B-SDKs
 C-SDKs

This should be really the content of the repository itself.

 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.

Maybe I'm wrong but I think Eng-Tech is not empty, but consists the
folders you wrote first. Maybe Eng-Tech does have content, like the
other repos unter Eng-Tech in the file system, but thos directories
aren't used for some reason? Maybe your repos started that way,
something didn't work as expected and things have changed?

Are you able to rename the repos beneath Eng-Tech in your file system?
That way nobody coudl use them anymore and you were really sure what
is in the repo Eng-Tech and what is not. If you rename name ABC-SDKs
to ABC-SDKs_ for some seconds, your svn list of Eng-Tech should
refelct those renamings or it's clear that Eng-Tech does have content,
the versioned directories ABC-SDKS and J-SDKs.

 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.

In any case, your repo structure is not supported and you should
change it after fully understanding it and possible.

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: Subversion Permissions Question.

2011-02-11 Thread Thorsten Schöning
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: Subversion Permissions Question.

2011-02-11 Thread MonicaS


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: Subversion Permissions Question.

2011-02-11 Thread Bob Archer
 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: Subversion Permissions Question.

2011-02-11 Thread MonicaS


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


Subversion Permissions Question.

2011-02-10 Thread MonicaS
Hello,

A Subversion server with a big repository was inherited to me recently
and I'm trying to figure out its configuration. 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.

We have subversion 1.4.3 (r23084) installed on a SunOS.
The server configuration is  svnserve over SSH.

I have experience administering other source control tools, like
Perforce, ClearCase, MKS, PVCS, etc. on Unix and Windows.

I read the the book 'Version Control with Subversion' and I still have
some questions.

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

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?

Other questions that I have are:
- How can I get a full repository layout?
- How can I get the repository history since the revision 0 to the
newest?
- 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.

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
   /main_folder1/
subfolder1
   /main_folder1/
subfolder1/trunk
   /main_folder1/
subfolder1/branches
   /main_folder1/
subfolder1/tags

   /main_folder2/
subfolder1
   /main_folder2/
subfolder1/trunk
   /main_folder2/
subfolder1/branches
   /main_folder2/
subfolder1/tags

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'.

So, are main_folder1 and main_folder2 two different repositories or
only one under Repo_name?

Where I can find information about the database FSFS layout, schema
and design?

I'm sorry if this are silly questions, please let me know of any book
or other information that will help me understand better the
subversion whole system.

Thank you.
Monica Sanchez