RE: Getting started with subversion
Okay, with those preliminaries out of the way, open the Terminal and do the following. The $ will represent your command prompt. This can be changed, so in Unix, it is common just to put $: $ cd $HOME $ svn mkdir svn_repos $ cd mkdir svn_repos $ svnadmin create newrepo This will create a Subversion repository at /Users/TommyHome/svn_repos called newrepo. You can find this in Pathfinder. Now, you will want to create a working directory: $ cd $HOME $ svn checkout file://$PWD/svn_repos/newrepo svn_project I think this should be $ svn checkout file:///$HOME/svn_repos/newrepo I know that with the cd command before, $PWD and $HOME are the same, but it's safer to use $HOME, as it will always point to the correct location. Also, notice the three /. According to the book you should either have file://localhost/$HOME... Or file:///$HOME... However I tried on a RHEL and file://$HOME works too Giulio Linedata Limited Registered Office: 85 Gracechurch St., London, EC3V 0AA Registered in England and Wales No 3475006 VAT Reg No 710 3140 03
Re: Getting started with subversion
On Jul 15, 2010, at 02:35, Giulio Troccoli wrote: Okay, with those preliminaries out of the way, open the Terminal and do the following. The $ will represent your command prompt. This can be changed, so in Unix, it is common just to put $: $ cd $HOME $ svn mkdir svn_repos $ cd mkdir svn_repos $ svnadmin create newrepo This will create a Subversion repository at /Users/TommyHome/svn_repos called newrepo. You can find this in Pathfinder. Now, you will want to create a working directory: $ cd $HOME $ svn checkout file://$PWD/svn_repos/newrepo svn_project I think this should be $ svn checkout file:///$HOME/svn_repos/newrepo Except that now your working copy will get created with the name newrepo which is weird since it's not a repo, it's a working copy. So from the original example, $ svn checkout file://$HOME/svn_repos/newrepo svn_project would be clearer. I know that with the cd command before, $PWD and $HOME are the same, but it's safer to use $HOME, as it will always point to the correct location. Six of one, half a dozen of the other, if you know what you're doing. Also, notice the three /. According to the book you should either have file://localhost/$HOME... Or file:///$HOME... However I tried on a RHEL and file://$HOME works too $HOME begins with a slash, hence file://$HOME/... is correct.
RE: Getting started with subversion
Hi List, First, thanks to David for an excellent explanation. However, I am confused a little by the sequence of commands suggested... Okay, with those preliminaries out of the way, open the Terminal and do the following. The $ will represent your command prompt. This can be changed, so in Unix, it is common just to put $: $ cd $HOME $ svn mkdir svn_repos $ cd mkdir svn_repos $ svnadmin create newrepo This will create a Subversion repository at /Users/TommyHome/svn_repos called newrepo. You can find this in Pathfinder. Now, you will want to create a working directory: $ cd $HOME $ svn checkout file://$PWD/svn_repos/newrepo svn_project This will allow you to checkout an EMPTY repository in Subversion in a directory under your $HOME directory called svn_project. When you open a new Pathfinder window, you should see this directory. If we want to create a new home for repositories to start with, then is that right? $ cd $HOME OK, go to known location $ svn mkdir svn_repos Why svn mkdir and not just mkdir ~ this is to create a new repo not to add a directory to a repo? $ cd mkdir svn_repos Should this not fail because 'mkdir' does not exist? $ svnadmin create newrepo ...should create the new repository which can then be accessed as file://$PWD/svn_repos/newrepo ok. Sorry if I am just confused about the way macs work or something... ~ mark c
RE: Getting started with subversion
I think this should be $ svn checkout file:///$HOME/svn_repos/newrepo Except that now your working copy will get created with the name newrepo which is weird since it's not a repo, it's a working copy. So from the original example, $ svn checkout file://$HOME/svn_repos/newrepo svn_project would be clearer. Sorry, my mistake. I was focusing on the $HOME bit and I forgot the svn_project. You're absolutely right Linedata Limited Registered Office: 85 Gracechurch St., London, EC3V 0AA Registered in England and Wales No 3475006 VAT Reg No 710 3140 03
Re: how to contribute feature of unknown popularity
On Wed, Jul 14, 2010 at 10:03:53PM +, svnusert...@href.com wrote: Re: export --skipfilesmatchingsize Prior thread link: http://svn.haxx.se/users/archive-2010-06/0040.shtmlhttp://svn.haxx.se/users/archive-2010-06/0040.shtml Hi, I am the person who wanted this feature and worked on testing it over recent months. It has been working well for some time, and I use it often. I use it because I build a lot of deployment servers where, on a daily or weekly basis, much (often more than 90%) of a system stays as-is and a small amount needs to be brought in from subversion. I use export (as opposed to update) to avoid having .svn files scattered throughout production machines. The main reason I like the skip feature is that it lets me deal with DLLs and other files that are (a) unchanging and (b) in use at the time of export. The normal export feature aborts when it encounters a pre-existing file that cannot be overwritten because it is in use; with the skip option, I can still export that branch of the repository and pick up any new/additional/changed files. Originally, I thought the skip feature would be a good way to save bandwidth and time. In the end, that was not as critical for me as being able to skip over in-use, unchanged DLLs. Hi Ann, Why don't you use rsync, which was designed to solve exactly this problem? rsync avoids unnecessary transfers of file data over the network, by transmitting only the changes necessary to sync two data sets. You could do a local export on the machine where the Subversion repository is located, and then use rsync to sync the exported result to your deployment servers. You can run rsync on windows using cygwin, or you can use one of the Windows ports (google mentions DeltaCopy and cwrsync on the first page, there are probably more). rsync is free software, licensed under the GPL. See http://en.wikipedia.org/wiki/Rsync for more details. If you require encryption, rsync traffic can be encrypted using SSH or stunnel (see stunnel.org). If your server runs Linux, SSH is probably the easier solution. With a Windows server, stunnel might be the better option since running an SSH server on Windows requires cygwin. As I've said before, I object to a feature that is not general enough to be useful to a lot of our users. What if the next person wants svn export to skip files containing java code, for instance? By your logic, we'd then add another option called --skip-files-containing-java-code. Proliferation of option flags like this is a wrong approach in my opinion. I think that using a high-quality sync tool such as rsync is definitely a better solution to the problem you're trying to solve. Thanks, Stefan
Re: how to contribute feature of unknown popularity
On Thu, Jul 15, 2010 at 6:34 AM, Stefan Sperling s...@elego.de wrote: On Wed, Jul 14, 2010 at 10:03:53PM +, svnusert...@href.com wrote: Re: export --skipfilesmatchingsize Prior thread link: http://svn.haxx.se/users/archive-2010-06/0040.shtmlhttp://svn.haxx.se/users/archive-2010-06/0040.shtml Hi, I am the person who wanted this feature and worked on testing it over recent months. It has been working well for some time, and I use it often. I use it because I build a lot of deployment servers where, on a daily or weekly basis, much (often more than 90%) of a system stays as-is and a small amount needs to be brought in from subversion. I use export (as opposed to update) to avoid having .svn files scattered throughout production machines. The main reason I like the skip feature is that it lets me deal with DLLs and other files that are (a) unchanging and (b) in use at the time of export. The normal export feature aborts when it encounters a pre-existing file that cannot be overwritten because it is in use; with the skip option, I can still export that branch of the repository and pick up any new/additional/changed files. Originally, I thought the skip feature would be a good way to save bandwidth and time. In the end, that was not as critical for me as being able to skip over in-use, unchanged DLLs. Hi Ann, Why don't you use rsync, which was designed to solve exactly this problem? rsync avoids unnecessary transfers of file data over the network, by transmitting only the changes necessary to sync two data sets. You could do a local export on the machine where the Subversion repository is located, and then use rsync to sync the exported result to your deployment servers. You can run rsync on windows using cygwin, or you can use one of the Windows ports (google mentions DeltaCopy and cwrsync on the first page, there are probably more). rsync is free software, licensed under the GPL. See http://en.wikipedia.org/wiki/Rsync for more details. And, at last check as part of an attempt at an rsnapshot based backup system, it hangs on open files. I had to do it my original way, which was to export the filesystem via CIFS, mount it and do the backups on the relevant rsnapshot server, because the hanging rsync issue was deadly. If you require encryption, rsync traffic can be encrypted using SSH or stunnel (see stunnel.org). If your server runs Linux, SSH is probably the easier solution. With a Windows server, stunnel might be the better option since running an SSH server on Windows requires cygwin. There are some commercial SSH servers and toolkits as well. If you need both rsync and SSH services on the same windows server, CygWin is the way to go. As I've said before, I object to a feature that is not general enough to be useful to a lot of our users. What if the next person wants svn export to skip files containing java code, for instance? By your logic, we'd then add another option called --skip-files-containing-java-code. Proliferation of option flags like this is a wrong approach in my opinion. It also won't work against files that are open, for example in a text editor, but don't happen to be .dll files. I think that using a high-quality sync tool such as rsync is definitely a better solution to the problem you're trying to solve. I'm mystified about using export on his core server. Do a checkout and svn update to a something like SRCDIR on the core server, to avoid the this file is locked issue, and use rsync -av --exclude=.svn /SRCDIR/ REMOTEHOST:/TARGETDIR/ syntax to push only that updated code. Thanks, Stefan
Re: how to contribute feature of unknown popularity
On Thu, Jul 15, 2010 at 07:27:57AM -0400, Nico Kadel-Garcia wrote: On Thu, Jul 15, 2010 at 6:34 AM, Stefan Sperling s...@elego.de wrote: Why don't you use rsync, which was designed to solve exactly this problem? And, at last check as part of an attempt at an rsnapshot based backup system, it hangs on open files. That is a Windows problem. Windows cannot handle deletions of files that are open. The rsync windows ports should have special logic to deal with this. If they don't, that needs to be fixed. (Or even better, Windows should be fixed...) I think that using a high-quality sync tool such as rsync is definitely a better solution to the problem you're trying to solve. I'm mystified about using export on his core server. Do a checkout and svn update to a something like SRCDIR on the core server, to avoid the this file is locked issue, and use rsync -av --exclude=.svn /SRCDIR/ REMOTEHOST:/TARGETDIR/ syntax to push only that updated code. What is the this file is locked issue? There is no difference between checkout and export, except that export does not create the .svn directories. Stefan
Re: how to contribute feature of unknown popularity
Nico Kadel-Garcia wrote: You can run rsync on windows using cygwin, or you can use one of the Windows ports (google mentions DeltaCopy and cwrsync on the first page, there are probably more). rsync is free software, licensed under the GPL. See http://en.wikipedia.org/wiki/Rsync for more details. And, at last check as part of an attempt at an rsnapshot based backup system, it hangs on open files. No it doesn't. A lot of people use it as the transport for backups in backuppc and while it may skip files that the OS has locked, it doesn't hang when using rsync in daemon mode. I had to do it my original way, which was to export the filesystem via CIFS, mount it and do the backups on the relevant rsnapshot server, because the hanging rsync issue was deadly. There was an old (and long-standing) bug when using rsync under cygwin sshd that would hang more or less at random. It is fixed in current versions. But even in the older version you could issue the rsync command on the windows side and use ssh with a linux/unix version under sshd on the remote side. If you require encryption, rsync traffic can be encrypted using SSH or stunnel (see stunnel.org). If your server runs Linux, SSH is probably the easier solution. With a Windows server, stunnel might be the better option since running an SSH server on Windows requires cygwin. There are some commercial SSH servers and toolkits as well. If you need both rsync and SSH services on the same windows server, CygWin is the way to go. If you don't need encryption, you can just run rsync as a standalone daemon (use double-colons in the rsync command for that mode). If you do need encryption you might use OpenVPN to set up tunnels with the staging server - which might also be useful for VNC or other control access too. Or with the current 1.7.x version, cygwin sshd should work the way you expect. I think that using a high-quality sync tool such as rsync is definitely a better solution to the problem you're trying to solve. I'm mystified about using export on his core server. Do a checkout and svn update to a something like SRCDIR on the core server, to avoid the this file is locked issue, and use rsync -av --exclude=.svn /SRCDIR/ REMOTEHOST:/TARGETDIR/ syntax to push only that updated code. Rsync has the -C option for exactly this purpose - to exclude files that are normally cvs or svn metadata and cruft left over from compiles. But look at the list of the built in excludes to make sure it won't skip anything you need. Rsync is also better than most means of copying into a live system because it will construct a new copy of existing files under a temporary name and rename it only when complete. That way, running programs never see inconsistent files and they aren't left in an inconsistent state if the transfer is interrupted. -- Les Mikesell lesmikes...@gmail.com
Committing different dirs to one external repo
I've been using svn on and off for a while, and have recently started using it at work after finally managing to migrate from SourceSafe. We have what might appear to be a slightly peculiar code hierarchy, and it's true that it was largely begat from using multiple SourceSafe databases, overlaid on top of one another, but it's what we have and isn't changing any time soon. A simplistic cut-down view of what we have is: # CORE is common code shared amongst projects, in one repo. CORE-REPO/ Source/ Include/ CORE/ CORE include files CORE/ CORE sub-directories of code etc.../ # An individual project, using CORE, in its own repo PROJ-REPO/ Source/ Include/ PROJ/ PROJ include files PROJ/ PROJ sub-directories of code etc.../ (yes, there's actually trunk+branches+tags at the real top, a plethora of other subdirs, but you get the gist hopefully). Then the PROJ root has svn:externals set such that it pulls in the (versioned) Include/CORE and Source/CORE bits that it wants, ending up with a combined build area: PROJ-BUILD/ Source/ Include/ CORE/ CORE include files PROJ/ PROJ include files CORE/ CORE sub-directories of code PROJ/ PROJ sub-directories of code etc.../ And it all works a treat (even, in fact, with a third layer in between, in much the same way). Now to the question. On occasion, someone working on PROJ is going to want to commit fixes (required by PROJ and impl. tested in a PROJ build area) to CORE. Fine, this works too. But sometimes, we are going to have (have had) fixes in Source/Include/CORE *and* Source/CORE which go together, and, in an ideal world, would go in in an atomic commit. And I was wondering what people thought was the best way of going about it. So far, we've just taken the hit/risk of doing 2 commits (one from Source/Include/CORE and one from Source/CORE). I considered pulling CORE out elsewhere, exporting the 2 CORE bits to that location, and committing from there, but that's a bit of a faff. I've also just thought of creating as temp. branch in CORE, switching both the PROJ copies to it, committing twice to the branch, and then atomically merging that back to trunk. But that's a similar faff. Although I could probably script that process with a uniquely-generated branch name (and, as I type, I'm thinking that'll be the way to go). I did, of course, just “try it”. From PROJ-BUILD/Source: svn ci Source/Include/CORE Source/CORE .. but svn doesn't like that; it seems to “see” the PROJ svn binding in the common directory, and then complains that the locations' repos. have mismatching UUIDs (the one from PROJ and the one from CORE), eben though both locations in question come from the same repo (CORE). I even tried from *within* one of the dirs, Source/CORE: svn ci . ../Include/CORE .. but got the same UUID error. Which may technically be a svn bug. So, any thoughts? (Excluding the ‘obvious’ re-organise all your build trees!) -- [n...@fnx ~]# rm -f .signature [n...@fnx ~]# ls -l .signature ls: .signature: No such file or directory [n...@fnx ~]# exit
Question about shuffling top level directory
Hi, I have a repository structure like: *repos/ABC/trunk/abc/src* I want to remove the trunk and get the structure to a form like *repos/ABC/abc/src* I know I can use svn move, but I want to keep the same revision number as of now. Is there any smarter way to get rid of the trunk dir and make 'abc' go one level up. -Ameet
Authorization Required
Hello, I'm configuring the subversion with to RAD 6.0 and would like provide the authorization for every user with their same NT login id and password. Whenever they will change the NT password, automatically the subversion password should also change as like that. What are the necessary configurations I need to do for these things? Please help me out to configure my subversion repository to my workspace with complete authentication and authorization. Thanks a lot in advance... Regards, Sunny This message and any attachments (the message) is intended solely for the addressees and is confidential. If you receive this message in error, please delete it and immediately notify the sender. Any use not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval. The internet can not guarantee the integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will) not therefore be liable for the message if modified. Do not print this message unless it is necessary, consider the environment. - Ce message et toutes les pieces jointes (ci-apres le message) sont etablis a l'intention exclusive de ses destinataires et sont confidentiels. Si vous recevez ce message par erreur, merci de le detruire et d'en avertir immediatement l'expediteur. Toute utilisation de ce message non conforme a sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite, sauf autorisation expresse. L'internet ne permettant pas d'assurer l'integrite de ce message, BNP PARIBAS (et ses filiales) decline(nt) toute responsabilite au titre de ce message, dans l'hypothese ou il aurait ete modifie. N'imprimez ce message que si necessaire, pensez a l'environnement.
RE: Authorization Required
Hello, I'm configuring the subversion with to RAD 6.0 and would like provide the authorization for every user with their same NT login id and password. Whenever they will change the NT password, automatically the subversion password should also change as like that. What are the necessary configurations I need to do for these things? Please help me out to configure my subversion repository to my workspace with complete authentication and authorization. Thanks a lot in advance... Regards, Sunny You might want to look at Subversion edge. http://www.open.collab.net/products/subversion/whatsnew.html I think they make setting up LDAP (NT Auth) point and click. I keep planning to try it but haven't got to it yet. BOb
RE: Question about shuffling top level directory
I have a repository structure like: repos/ABC/trunk/abc/src I want to remove the trunk and get the structure to a form like repos/ABC/abc/src I know I can use svn move, but I want to keep the same revision number as of now. Is there any smarter way to get rid of the trunk dir and make 'abc' go one level up. -Ameet You can't change what is in the repository without committing it as a revision. Well... that's not strictly true... you can dump it, use dumpfilter, import it to a new path... but it doesn't seem worth it when a svn mv will do it in a few seconds. BOb
Common authorisation
I am trying to make some common authorisation for all my repositories. This is useful for example to give a particular user or a group of users, svn admins in my case, read-write permissions in all repositories. I thought I could have two AuthzSVNAccessFile in my Location in the Apache confi, but only the second one is considered. I have tried having two files in the AuthzSVNAccessFile but it doesn't. The reason I tried this approach is because I can have more that one authentication file with multiple AuthUserFile, so I thought that maybe I could do the same for authorisation. Anyway, another approach would be to be able to have some kind of #include in the access file themselves. For example myrepo.access: #include common.access [groups] dev = gt, hp [/] @dev = r [/trunk] @dev = rw And common.access: [groups] admins = svn_gt [/] @admind = rw The idea here is user svn_gt will have read-write access to the root of the repository, while gt and hp will only have read access Is this possible? I haven't tried #include because it would be interpreted as a comment. It's just an example, I was simply wondering if such feature is available or not. If that's not possible, does anyone have any suggestion on how I could achieve this? Thanks Giulio Linedata Limited Registered Office: 85 Gracechurch St., London, EC3V 0AA Registered in England and Wales No 3475006 VAT Reg No 710 3140 03
svn: working copy ??? locked
Trying to resolve this issue. I expected to find a 'locked' file somewhere, but one does not exist. Running 'svn cleanup' does not resolve the problem either. Suggestions? -- Until later, Geoffrey I predict future happiness for America if they can prevent the government from wasting the labors of the people under the pretense of taking care of them. - Thomas Jefferson
Re: Getting started with subversion
On Thu, Jul 15, 2010 at 5:16 AM, Cooke, Mark mark.co...@siemens.com wrote: $ svn mkdir svn_repos Why svn mkdir and not just mkdir ~ this is to create a new repo not to add a directory to a repo? That's what I get when I answer emails past midnight after I fell asleep on the couch. -- David Weintraub qazw...@gmail.com
Re: subversion
What platform and binaries? Where did you get these errors? When you started Apache? Why is it asking for your Python HOME directory? It's hard to tell what the issue could be without more information. 2010/7/15 phoebe pho...@sz168.com.cn: Hi: I have some question with subversion: SVN1.6.6, install binary to deploy apache mode, start service, then the error log will appear: Could not find platform independent libraries prefix Could not find platform dependent libraries exec_prefixConsider setting $PYTHONHOME to prefix[:exec_prefix] 'import site' failed; use -v for traceback Could not find platform independent libraries prefix Could not find platform dependent libraries exec_prefixConsider setting $PYTHONHOME to prefix[:exec_prefix] 'import site' failed; use -v for traceback Can it will be ok? Or how to take out this problem? Thanks. 2010-07-15 Phoebe 曾青艳 Tel:86-755-2699 4790 Fax:86-755-26996813 深圳市华软泰科科技有限公司 Shenzhen Chinasoft Information Technology Co.,Ltd 深圳市南山区高新区南区科技南十路深圳航天技术创新研究院D209 Rm.209, Shenzhen Academy of Aeroapace Technology Bldg., Kejinan 10th Rd.,South High-tech Zone,Nanshan Dist.,Shenzhen,China 518057 -- David Weintraub qazw...@gmail.com
svn: timed out waiting for server
Hi all, I am dealing with a situation where a Java application that user Subversion is causing an intermittent problem. Usually it happens with the first user each day. When they launch the application, they get this error. “Caused by: org.tmatesoft.svn.core.SVNExcaption: svn: REPORT request failed on ‘/svn/app/trunk’ Svn: timed out waiting for server” If they close the application and restart, it works fine. Amin _ Hotmail: Free, trusted and rich email service. https://signup.live.com/signup.aspx?id=60969
RE: Getting started with subversion
Let's get through this one step at a time: First of all, if you are trying to use Subversion just to version your own designs and files, you are probably better off with TimeMachine. It versions your files and is very simple to use. All you need is a $100 USB hard drive to connect to your Mac. Remember that it isn't if your hard drive will fail, it is when, so the $100 investment is your guarantee that you won't lose your valuable work. Just to clarify, TimeMachine doesn't really version your file. It does a back up every hour of any files that have changed. So, if you change the file 4 times in one hour you can't go back to any of those revisions... just the last one TM backed up each hour. You can also use Dropbox (http://dropbox.com) which is free for 2Gb of space (which is quite a bit more than you realize). Dropbox versions your files, and has some great collaboration features that allow to share files with other users. Now this is true. They save revisions for 30 days. If you have a pro-account you can add Pack-Rat for $40 a year and they will save all revisions forever. from the dropbox help: Dropbox saves a history of all deleted and previous versions of files for 30 days for all Dropbox accounts by default. If you have the Pack-Rat add-on, Dropbox saves those files for as long as you have the Pack-Rat add-on. With Pack-Rat, you never have to worry about losing an old version of a file. BOb
RE: working copy ??? locked
Trying to resolve this issue. I expected to find a 'locked' file somewhere, but one does not exist. Running 'svn cleanup' does not resolve the problem either. Suggestions? -- Until later, Geoffrey I'm pretty sure lock info is stored in the repository. http://svnbook.red-bean.com/nightly/en/svn-book.html#svn.advanced.locking BOb
Re: svn: working copy ??? locked
Andy Levy wrote: On Thu, Jul 15, 2010 at 11:13, Geoffrey li...@serioustechnology.com wrote: Trying to resolve this issue. I expected to find a 'locked' file somewhere, but one does not exist. Running 'svn cleanup' does not resolve the problem either. Suggestions? You need to provide more detail. What version of Subversion? Operating System? If Windows, what antivirus? Subversion: 1.4.2 OS: Red Hat Enterprise 5.3 -- Until later, Geoffrey I predict future happiness for America if they can prevent the government from wasting the labors of the people under the pretense of taking care of them. - Thomas Jefferson
Re: Getting started with subversion
On Thu, Jul 15, 2010 at 12:29, Bob Archer bob.arc...@amsi.com wrote: Let's get through this one step at a time: First of all, if you are trying to use Subversion just to version your own designs and files, you are probably better off with TimeMachine. It versions your files and is very simple to use. All you need is a $100 USB hard drive to connect to your Mac. Remember that it isn't if your hard drive will fail, it is when, so the $100 investment is your guarantee that you won't lose your valuable work. Just to clarify, TimeMachine doesn't really version your file. It does a back up every hour of any files that have changed. So, if you change the file 4 times in one hour you can't go back to any of those revisions... just the last one TM backed up each hour. Also, at the end of each week (I think - it kind of depends on how much space you have. Regardless, it's some set time period), those hourlies get deleted and you only have a snapshot of the end of each day. Then just the end of each week. And when you're out of space entirely, the weeklies start getting deleted, oldest first. You do not have an eternal, complete history of each file with TM. That said, I think TM is a great backup system for the average user; it's saved me a couple times, and I really wish there was something comparable for my XP system I have to use for work.
RE: Getting started with subversion
On Thu, Jul 15, 2010 at 12:29, Bob Archer bob.arc...@amsi.com wrote: Let's get through this one step at a time: First of all, if you are trying to use Subversion just to version your own designs and files, you are probably better off with TimeMachine. It versions your files and is very simple to use. All you need is a $100 USB hard drive to connect to your Mac. Remember that it isn't if your hard drive will fail, it is when, so the $100 investment is your guarantee that you won't lose your valuable work. Just to clarify, TimeMachine doesn't really version your file. It does a back up every hour of any files that have changed. So, if you change the file 4 times in one hour you can't go back to any of those revisions... just the last one TM backed up each hour. Also, at the end of each week (I think - it kind of depends on how much space you have. Regardless, it's some set time period), those hourlies get deleted and you only have a snapshot of the end of each day. Then just the end of each week. And when you're out of space entirely, the weeklies start getting deleted, oldest first. You do not have an eternal, complete history of each file with TM. Yes, to be fully technical it does an hourly, daily, weekly, monthly. It deletes oldest data first if it runs out of room. It uses links to good effect. From a MacWorld article: Time Machine keeps all of the day's backups for 24 hours, but then it begins to delete older versions to save space. You can count on it to keep the first backup of any given day for an entire month. Even after a month, it preserves the first backup of each week until your disk is nearly full. Only at that point does the program begin purging files from your oldest weekly backups. The net result is that you see your files as they appeared at many points in the past, though not all points in the past. My point was that is doesn't version/backup each change. So, that shouldn't be expectecd. That said, I think TM is a great backup system for the average user; it's saved me a couple times, and I really wish there was something comparable for my XP system I have to use for work. I think something like this comes as a client to Windows home server although it is a daily backup and I'm not sure if you can go back in time. I'm sure there are 3rd party backup systems that work like TimeMachine for Windows. If not, maybe I will write one using svn 1.7 source code as a base, sell it an become filthy rich! BOb
RE: working copy ??? locked
On Thu, Jul 15, 2010 at 12:37, Bob Archer bob.arc...@amsi.com wrote: Trying to resolve this issue. I expected to find a 'locked' file somewhere, but one does not exist. Running 'svn cleanup' does not resolve the problem either. Suggestions? -- Until later, Geoffrey I'm pretty sure lock info is stored in the repository. http://svnbook.red-bean.com/nightly/en/svn- book.html#svn.advanced.locking Working copy locked is not the same as locking a file to prevent someone else from committing a change to it. http://svnbook.red-bean.com/nightly/en/svn.tour.cleanup.html Ah.. I missed that... my bad. As the church lady would say... never mind. BOb
svn del: access denied
i have been using svn for about a week now and want to restructure my repository a little bit. I tried deleting a folder and I get access denied. I use tortise svn on windows 7 32bit and svn on my gentoo box. Both get access denied and I have been unable to find any logs or more information i can create and modify files and create folders but i can not move, rename, or delete anything what can i do to debug this? here is some information i think to be relevant i am using subversion 1.6.11 on a Gentoo 2.6.31-r6 kernel. ## svnserve.conf ### Visit http://subversion.tigris.org/ for more information. [general] anon-access = none auth-access = write password-db = passwd authz-db = authz realm = Rededog's Version Control System #EOF# ## authz # irrelevant users omitted for brevity [aliases] koglinjg = /C=WA/ST=Washington/L=Redmond/O=/OU=/CN=Joel Koglin [/] koglinjg = rw #EOF# Thanks, Joel Koglin
Merging with differing checkout and update depths v.1.5.1
Hello, I've come across an issue in v1.5.1 and was wondering whether it was expected behavior or a bug. The sequence is as follows (pathnames have been changed for simplicity). * Create a branch from trunk: svn copy svn://some.repo.com/repo/trunk svn://some.repo.com/repo/branches/mybranch/trunk * Make a change to trunk in several places: svn co svn://some.repo.com/repo/trunk trunk vi trunk/file1.txt # make some changes vi trunk/subdir1/subdir2/file2.txt # make some more changes cd trunk; svn commit -m changes to trunk; cd .. * Checkout branch using --depth and update subdir1 with --set-depth: svn co svn://some.repo.com/repo/branches/mybranch/trunk mybranch --depth immediates cd mybranch svn update subdir1 --set-depth infinity svn merge --dry-run -r1:HEAD svn://some.repo.com/repo/trunk --- Merging r1 through r3 into '.': Ufile1.txt Now, at this point, it seems merge does not traverse the modified depth. I would have expected subdir1/subdir2/file2.txt to be updated as well (as the update, commit and status commands all traverse to the modified depth). In order to get the changes on subdir1, I need to cd there and call merge again: cd mybranch/subdir1 svn merge --dry-run -r1:HEAD svn://some.repo.com/repo/trunk/subdir1 --- Merging r1 through r3 into 'subdir2': Ufile2.txt This was performed on Ubuntu 8.04 server on an x86_64 arch running svnserve v1.5.1 and an svn v1.5.1 client on the same machine. Regards, Can
Re: Question about shuffling top level directory
On 7/15/2010 9:54 AM, Bob Archer wrote: I have a repository structure like: repos/ABC/trunk/abc/src I want to remove the trunk and get the structure to a form like repos/ABC/abc/src I know I can use svn move, but I want to keep the same revision number as of now. Is there any smarter way to get rid of the trunk dir and make 'abc' go one level up. -Ameet You can't change what is in the repository without committing it as a revision. Well... that's not strictly true... you can dump it, use dumpfilter, import it to a new path... but it doesn't seem worth it when a svn mv will do it in a few seconds. Also, making a change but not changing the revision number doesn't make any sense in the context of a revision control system. It's there to make sure you can get back both what you have now and the next thing you do to it. And if you want to think of revision numbers as something to keep, you probably should be doing copies into a tags directory instead of doing away with the trunk. -- Les Mikesell lesmikes...@gmail.com
Access control client error messages very poor?
Hello all, I've just had a look through the mailing lists and the issue tracker for this topic, and not found it discussed before. So, I'll start in? Is the current behaviour on performing SVN activities (with Neon RA) that violate access controls known to be bad? Environment is: Client SVN: 1.6.9 with ra_neon Server SVN: Either of 1.6.12 or 1.5.6 If a directory in a repository is open for read for a particular user, but closed for write, the following is the error message given to the user. It's hardly friendly, is it!? svn: Commit failed (details follow): svn: Server sent unexpected return value (403 Forbidden) in response to CHECKOUT request for '/svn/sources/!svn/ver/43/Read/Only/Area/tags' svn: Your commit message was left in a temporary file: svn:'svn-commit.tmp' To me, the worst part of this is the Server sent _unexpected_ return value. Why is Forbidden considered unexpected!? ra_neon is talking to a mod_dav_svn server, which allows access to the repository to be restricted - what's unexpected about that access being denied? Equally, if a user tries to check out an area of the repository they don't have read access to, they get: svn: Server sent unexpected return value (403 Forbidden) in response to OPTIONS request for 'http://svn.example.com/svn/svntest1/Private/Area' Again, Forbidden is unexpected. Has no-one else reported this? Is it being worked on - anything? Cheers, John. -- John Beranek To generalise is to be an idiot. http://redux.org.uk/ -- William Blake
Re: subversion
You've neglected to state the operating system and how you've installed the software. Perhaps you've failed to install some important dependencies when you installed the binaries? Please let us know the operating system and how you've obtained and installed the software. Also, Subverison 1.6.12 is available and I'd recommend you update to and install that. 2010/7/15 phoebe pho...@sz168.com.cn: Hi: I have some question with subversion: SVN1.6.6, install binary to deploy apache mode, start service, then the error log will appear: Could not find platform independent libraries prefix Could not find platform dependent libraries exec_prefixConsider setting $PYTHONHOME to prefix[:exec_prefix] 'import site' failed; use -v for traceback Could not find platform independent libraries prefix Could not find platform dependent libraries exec_prefixConsider setting $PYTHONHOME to prefix[:exec_prefix] 'import site' failed; use -v for traceback Can it will be ok? Or how to take out this problem? Thanks. 2010-07-15 Phoebe 曾青艳 Tel:86-755-2699 4790 Fax:86-755-26996813 深圳市华软泰科科技有限公司 Shenzhen Chinasoft Information Technology Co.,Ltd 深圳市南山区高新区南区科技南十路深圳航天技术创新研究院D209 Rm.209, Shenzhen Academy of Aeroapace Technology Bldg., Kejinan 10th Rd.,South High-tech Zone,Nanshan Dist.,Shenzhen,China 518057
Re: how to contribute feature of unknown popularity
Thank you very much for the replies. About export failing, it happened to me so often, I thought everyone would know the details. It occurs when Windows will not allow svn.exe export to write to the file, for any reason. The most common reason in my case was that the file was in use, e.g. a DLL loaded in memory. Locking of a DLL is a Windows limitation and they probably think it is by design. Another thing that locks files is the readonly attribute (which okay normally would not be there but I did run into it). I have only tested the CollabNet svn.exe (command line) in this regard. The whole thing is completely reproducible so if you want more info on that, let me know. RSync, why not. Good question. Because it seemed completely overwhelming to learn another whole way of doing things, when I was just getting my head around moving 15 years of work from 2 other version control systems on into Subversion. Because I am only starting to run Linux servers and did not want to put RSync there without knowing enough how to admin it. Because when I read the info on using RSync on Windows, it seemed to be yet another product that did not really run on Windows, easily, simply (could be wrong about that... ), and I really dislike the idea of simulating Linux on Windows, not least because the instructions always assume linux know-how and if I had linux know-how, I'd already be running it on Linux. (End rant... just explaining why I was so turned off RSync). Another reason was that the files were already *in* Subversion repositories and it seemed natural to want to take them back out of there. Does RSync automatically work against an existing repository or would that involve having another copy of the files? Maybe R stands for Repository. Obviously I don't know anything about RSync other than it sync's something to something. Last reason I thought that the spirit of CollabNet was inviting people to collaborate, and here I really thought I had something to contribute. And I say that because, before launching into all this, I read quite a few forum posts from other people over the years who also were wanting to use svn export as lazy-man's sync. It seemed so close to being exactly that, okay if we leave aside bitmaps, all it needed was the idea of selective export and voila, it was a sync. It really does not seem to be as bizarre as selective export of files containing java fragments. As to the proposed solution of exporting everything to a temporary location and then copying selectively (with rsync or otherwise), I ruled that out because it needlessly duplicated all the files -- waste of disk space, processing time and effort. I did in fact do that (with xcopy) during the weeks before Paul coded the skip feature. Here is a link to the modified source: http://greenbreen.com/svn_mod_source/which implements the --skipfilesmatchingsize feature. -Ann At 11:43 AM 7/15/2010, Stefan Sperling wrote: On Thu, Jul 15, 2010 at 07:27:57AM -0400, Nico Kadel-Garcia wrote: On Thu, Jul 15, 2010 at 6:34 AM, Stefan Sperling s...@elego.de wrote: Why don't you use rsync, which was designed to solve exactly this problem? And, at last check as part of an attempt at an rsnapshot based backup system, it hangs on open files. That is a Windows problem. Windows cannot handle deletions of files that are open. The rsync windows ports should have special logic to deal with this. If they don't, that needs to be fixed. (Or even better, Windows should be fixed...) I think that using a high-quality sync tool such as rsync is definitely a better solution to the problem you're trying to solve. I'm mystified about using export on his core server. Do a checkout and svn update to a something like SRCDIR on the core server, to avoid the this file is locked issue, and use rsync -av --exclude=.svn /SRCDIR/ REMOTEHOST:/TARGETDIR/ syntax to push only that updated code. What is the this file is locked issue? There is no difference between checkout and export, except that export does not create the .svn directories. Stefan
