RE: Need Help : Purging very old (/unwanted) revisions
Please try to post in * plain * text (not html or rich text). We also prefer to add text in-line or at the bottom as it makes it easier to read the whole story... > From: vinay modi [mailto:modivi...@gmail.com > ] > Sent: Tuesday, September 04, 2012 4:04 PM > To: users@subversion.apache.org 'cvml', 'users@subversion.apache.org');> > Subject: Need Help : Purging very old (/unwanted) revisions > > Hi > > My organization's svn repository size has grown too > large and most of the old revisions of documents are never being used. Can we stop here and ask what the problem actually is? There are repositories around with millions of revisions and files that work without problems, so what are your issues? > Consider I have 4 documents in my repository, of which > I have 10 revisions: > 4 for document A > 3 for document B > 2 for document C > 1 for document D. > > Now, I want to keep only the last 2 revisions of all > documents i.e 2 for A, 2 for B, 2 for C and 1 for D.. > Is there any way I can achieve this in my subversion repository? Short answer: no. Long answer: subversion (along with other such tools) is designed to keep all your history! Removing stuff is not generally considered "a good thing" and is therefore not something you can easily do. As JPM mentions below, it probably can be done, with a lot of effort by someone who knows what they are doing, but I would urge you to consider and explain why you think this is necessary. There may be other ways around whatever problems you are having that we can suggest once we understand your issues. ~ mark c > Thanks in Advance > > Regards > > Vinay > > On Wednesday, September 5, 2012, John Maher wrote: > > Hello, > > You can create a new repository then get the second to > last revision and use that to create a new project in that > new repository. Then create a working copy and replace it > with the current revision. Then do a commit and you're done. > > JPM >
Question about Basic Authentication
Hello, System Configuration: Windows Server 2003 Apache Subversion 1.7.6 TortoiseSVN 1.7.9 HTTP Server 2.2.22 I am trying to configure Subversion with Basic Authentication but the error log indicates the user cannot be found which tells me the passwd file is not being seen. In this example the top level directory of the Repository is C:\svnrepos\test1. IP has been masked for security purposes. Should the passwd file reside elsewhere? Perhaps relative to the ServerRoot? LoadModules: - The "mod_auth_basic.so" load module is enabled in httpd.conf LoadModule auth_basic_module modules/mod_auth_basic.so Fragment of httpd.conf directive (it references full path to the passwd file...) DAV svn SVNParentPath c:/svnrepos AuthType Basic AuthName "Subversion repositories" AuthUserFile C:/svnrepos/test1/conf/passwd Require valid-user Fragment from access log: xxx..xx.x.xx - "" [06/Sep/2012:15:38:37 +0100] "OPTIONS /svn/test1 HTTP/1.1" 401 401 xxx..xx.x.xx - "" [06/Sep/2012:15:38:37 +0100] "OPTIONS /svn/test1 HTTP/1.1" 401 401 Fragment from error log: Thu Sep 06 15:30:48 2012] [error] [client xxx..xx.x.xx] user jimmy not found: /svn/test1 URL from within the TortoiseSVN GUI (on the local machine): http:///svn/test1 David Anastasio Jacobs Technology
Re: better messaging w/ mod_dontdothat?
On Wed, Sep 5, 2012 at 4:46 PM, Mark Phippard wrote: > Assume you already looked at the code? The comments are interesting and > might point in a direction to go: I did, but as I read it that only makes reference to populating the Apache logs. Where there does it show that I can set the Apache status code (or similar) so I can use my own custom error messaging? Apologies if it should be obvious, I'm not a coder -- Douglas J Hunley (doug.hun...@gmail.com) Twitter: @hunleyd Web: douglasjhunley.com G+: http://goo.gl/sajR3
Re: better messaging w/ mod_dontdothat?
On Thu, Sep 6, 2012 at 11:26 AM, Doug Hunley wrote: > On Wed, Sep 5, 2012 at 4:46 PM, Mark Phippard wrote: > > Assume you already looked at the code? The comments are interesting and > > might point in a direction to go: > > I did, but as I read it that only makes reference to populating the > Apache logs. Where there does it show that I can set the Apache status > code (or similar) so I can use my own custom error messaging? > > Apologies if it should be obvious, I'm not a coder > > Me neither. But there were two things that jumped out at me. The first is this comment: * TODO: Try and pass back a custom document body containing a * serialized svn_error_t so the client displays a better * error message. */ It implies someone thought it might be possible to pass back an error message the client could handle. I do not know if they tried and failed or it is genuinely possible for someone to try. The other thing was just the return code itself: e = ap_bucket_error_create(403, "No Soup For You!", f->r->pool, f->c->bucket_alloc); It seems that it would be easy to return a different HTTP error code if you were just looking for a different error code. That said, it seems like 403 is the appropriate error code. A 403 means that client authentication was successful. There is no reason to think that credentials were wrong. 403 means they are not allowed to do what they tried to do and should not try again. -- Thanks Mark Phippard http://markphip.blogspot.com/
RE: Question about Basic Authentication
[Note: please post in plain text if at all possible!] > -Original Message- > From: Anastasio, David M CTR USAF AFMC AFLCMC/HNID > [mailto:david.anastasio@hanscom.af.mil] > Sent: 06 September 2012 16:26 > To: users@subversion.apache.org > Subject: Question about Basic Authentication > > Hello, > > System Configuration: > > Windows Server 2003 > Apache Subversion 1.7.6 > TortoiseSVN 1.7.9 > HTTP Server 2.2.22 > > I am trying to configure Subversion with Basic Authentication > but the error log indicates the user cannot be found which > tells me the passwd file is not being seen. > > In this example the top level directory of the Repository is > C:\svnrepos\test1. > > IP has been masked for security purposes. > > Should the passwd file reside elsewhere? Perhaps relative to > the ServerRoot? > > LoadModules: - The "mod_auth_basic.so" load module is > enabled in httpd.conf > > LoadModule auth_basic_module modules/mod_auth_basic.so Just in case... Something that caught me when I started with apache is that the `require valid_user` directive is provided by `mod_authz_user` and I had disabled that as I thought I wasn't using it with basic etc. It took quite a bit of to-ing and fro-ing through the apache docs [1] before I got it right... [1] http://httpd.apache.org/docs/2.2/mod/mod_authz_user.html ~ mark c > Fragment of httpd.conf directive (it references > full path to the passwd file...) > > > DAV svn > SVNParentPath c:/svnrepos > AuthType Basic > AuthName "Subversion repositories" > AuthUserFile C:/svnrepos/test1/conf/passwd > Require valid-user > > > Fragment from access log: > > xxx..xx.x.xx - "" [06/Sep/2012:15:38:37 +0100] "OPTIONS > /svn/test1 HTTP/1.1" 401 401 > > xxx..xx.x.xx - "" [06/Sep/2012:15:38:37 +0100] "OPTIONS > /svn/test1 HTTP/1.1" 401 401 > > Fragment from error log: > > Thu Sep 06 15:30:48 2012] [error] [client xxx..xx.x.xx] user > jimmy not found: /svn/test1 > > URL from within the TortoiseSVN GUI (on the local machine): > > http:///svn/test1 > > David Anastasio > Jacobs Technology
RE: Question about Basic Authentication
The mod_authz_user shared object was already enabled in my configuration. Still looking for an answer. Thanks -Original Message- From: Cooke, Mark [mailto:mark.co...@siemens.com] Sent: Thursday, September 06, 2012 11:44 AM To: Anastasio, David M CTR USAF AFMC AFLCMC/HNID; users@subversion.apache.org Subject: RE: Question about Basic Authentication [Note: please post in plain text if at all possible!] > -Original Message- > From: Anastasio, David M CTR USAF AFMC AFLCMC/HNID > [mailto:david.anastasio@hanscom.af.mil] > Sent: 06 September 2012 16:26 > To: users@subversion.apache.org > Subject: Question about Basic Authentication > > Hello, > > System Configuration: > > Windows Server 2003 > Apache Subversion 1.7.6 > TortoiseSVN 1.7.9 > HTTP Server 2.2.22 > > I am trying to configure Subversion with Basic Authentication > but the error log indicates the user cannot be found which > tells me the passwd file is not being seen. > > In this example the top level directory of the Repository is > C:\svnrepos\test1. > > IP has been masked for security purposes. > > Should the passwd file reside elsewhere? Perhaps relative to > the ServerRoot? > > LoadModules: - The "mod_auth_basic.so" load module is > enabled in httpd.conf > > LoadModule auth_basic_module modules/mod_auth_basic.so Just in case... Something that caught me when I started with apache is that the `require valid_user` directive is provided by `mod_authz_user` and I had disabled that as I thought I wasn't using it with basic etc. It took quite a bit of to-ing and fro-ing through the apache docs [1] before I got it right... [1] http://httpd.apache.org/docs/2.2/mod/mod_authz_user.html ~ mark c > Fragment of httpd.conf directive (it references > full path to the passwd file...) > > > DAV svn > SVNParentPath c:/svnrepos > AuthType Basic > AuthName "Subversion repositories" > AuthUserFile C:/svnrepos/test1/conf/passwd > Require valid-user > > > Fragment from access log: > > xxx..xx.x.xx - "" [06/Sep/2012:15:38:37 +0100] "OPTIONS > /svn/test1 HTTP/1.1" 401 401 > > xxx..xx.x.xx - "" [06/Sep/2012:15:38:37 +0100] "OPTIONS > /svn/test1 HTTP/1.1" 401 401 > > Fragment from error log: > > Thu Sep 06 15:30:48 2012] [error] [client xxx..xx.x.xx] user > jimmy not found: /svn/test1 > > URL from within the TortoiseSVN GUI (on the local machine): > > http:///svn/test1 > > David Anastasio > Jacobs Technology smime.p7s Description: S/MIME cryptographic signature
Re: Question about Basic Authentication
"Anastasio, David M CTR USAF AFMC AFLCMC/HNID" writes: > The mod_authz_user shared object was already enabled in my configuration. > Still looking for an answer. >> SVNParentPath c:/svnrepos >> AuthType Basic >> AuthName "Subversion repositories" >> AuthUserFile C:/svnrepos/test1/conf/passwd It looks like you are using the standard location for the svnserve password file as the location for the Apache password file. I suspect you are trying to use as svnserve password file which has the wrong format for Apache; you need to use a file created using htpasswd. You are using a single password file for all repositories in /svnrepos but you have chosen to put that single file inside the /svnrepos/test1 repository. That can work but is a bit odd. -- Philip
RE: Question about Basic Authentication
Yes, I think that is exactly the problem here. I will try to create the password file with htpasswd. Does Apache suggest where the password file should reside? Is it restricted to a certain location? I couldn't find this in the documentation. Thank you. Dave -Original Message- From: MARTIN PHILIP [mailto:codematt...@ntlworld.com] On Behalf Of Philip Martin Sent: Thursday, September 06, 2012 2:02 PM To: Anastasio, David M CTR USAF AFMC AFLCMC/HNID Cc: users@subversion.apache.org Subject: Re: Question about Basic Authentication "Anastasio, David M CTR USAF AFMC AFLCMC/HNID" writes: > The mod_authz_user shared object was already enabled in my configuration. > Still looking for an answer. >> SVNParentPath c:/svnrepos >> AuthType Basic >> AuthName "Subversion repositories" >> AuthUserFile C:/svnrepos/test1/conf/passwd It looks like you are using the standard location for the svnserve password file as the location for the Apache password file. I suspect you are trying to use as svnserve password file which has the wrong format for Apache; you need to use a file created using htpasswd. You are using a single password file for all repositories in /svnrepos but you have chosen to put that single file inside the /svnrepos/test1 repository. That can work but is a bit odd. -- Philip smime.p7s Description: S/MIME cryptographic signature
Re: Question about Basic Authentication
On 9/6/2012 11:08 AM, Anastasio, David M CTR USAF AFMC AFLCMC/HNID wrote: Yes, I think that is exactly the problem here. I will try to create the password file with htpasswd. Does Apache suggest where the password file should reside? Is it restricted to a certain location? I couldn't find this in the documentation. Thank you. Dave There is no standard password file location, as AuthUserFile is specified directly in the block in your httpd.conf. Under Linux I put the password file in /etc with the rest of the system password files. The essential requirement is that the file *not* be visible from outside the server, i.e. don't put it into your repository directory or another directory under your DocumentRoot. Unfortunately, I have seen this happen - "hey, what's in http://server.name/passwd.txt";? It wasn't a Subversion repository that time (and worse yet, the passwords were plaintext), but password file location is a trap for the unwary. I've never set up Apache under Windows, so I can't suggest a "good" location. Maybe the directory in which httpd.conf is stored? -- David Chapman dcchap...@acm.org Chapman Consulting -- San Jose, CA Software Development Done Right. www.chapman-consulting-sj.com
RE: Question about Basic Authentication
Hello I am trying to create a repository without a lot of junk that exists with the source. Namely 2 files and two folders. The import command doesn't seem to allow exclusion, at least not in the book. These exclusions also need to be applied to all users so a directory property is required. But the directory property is not allowed if a working copy does not exist. This project contains 44 modules in separate directories. So the best way I can figure out how to do this is edit the config file, import the project, set the svn:ignore property on each of the 44 directories and I'm done. In which case every time I add a module I must remember to repeat setting the svn:ignore. Note: the documentation says the config file accepts whitespace delimited "ignores" while the svn:ignore accepts new-line separated "ignores". I hope that is an error since I do not know if I can type a new line at my command prompt. Very tedious, unless, of course, there is a better way. JM
Re: Question about Basic Authentication
Guten Tag John Maher, am Donnerstag, 6. September 2012 um 21:52 schrieben Sie: > Very tedious, unless, of course, there is a better way. You really should start a new thread and maybe ask a question. 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 Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
RE: Question about Basic Authentication
Thank you, David I did come across another thread with an example that places the password file under the 'conf' sub-directory alongside the http.conf file; so your suggestion is a good one. I also noticed in the same thread that the password file is actually called "svn-password.pass" as opposed to "passwd" which may account for the problems I've had with authentication. On Windows, one must run the htpasswd.exe file from the DOS command line. Thanks, Dave -Original Message- From: David Chapman [mailto:dcchap...@acm.org] Sent: Thursday, September 06, 2012 2:39 PM To: Anastasio, David M CTR USAF AFMC AFLCMC/HNID Cc: users@subversion.apache.org Subject: Re: Question about Basic Authentication On 9/6/2012 11:08 AM, Anastasio, David M CTR USAF AFMC AFLCMC/HNID wrote: > Yes, I think that is exactly the problem here. > I will try to create the password file with htpasswd. > Does Apache suggest where the password file should reside? > Is it restricted to a certain location? I couldn't find this in the > documentation. > Thank you. > Dave > There is no standard password file location, as AuthUserFile is specified directly in the block in your httpd.conf. Under Linux I put the password file in /etc with the rest of the system password files. The essential requirement is that the file *not* be visible from outside the server, i.e. don't put it into your repository directory or another directory under your DocumentRoot. Unfortunately, I have seen this happen - "hey, what's in http://server.name/passwd.txt";? It wasn't a Subversion repository that time (and worse yet, the passwords were plaintext), but password file location is a trap for the unwary. I've never set up Apache under Windows, so I can't suggest a "good" location. Maybe the directory in which httpd.conf is stored? -- David Chapman dcchap...@acm.org Chapman Consulting -- San Jose, CA Software Development Done Right. www.chapman-consulting-sj.com smime.p7s Description: S/MIME cryptographic signature
