Migrations with Subversion
Hi! Im administrating a subversion server 1.4.2 version and Tortoise Version 1.5.4 and Im thinking to migrate to 1.6.9 in a x86_64 machine. Could I have any problem? Its important for me to avoid any conflict. Thank you very much!
RE: [Help] Choose Subversion for Java Application
> > On Mar 28, 2010, at 22:43, Moch Firman N wrote: > > > > Thanks. I have not yet installed any package of subversion, > > please in advise which version should I install with free > > license of course ? > > > You should install the latest version of Subversion, > currently 1.6.9, and familiarize yourself with the license > under which it is released to see if it adequately satisfies > your definition of "free". > It depends how you want to use it. Read chapters 1 and 6 of the subversion red book (http://svnbook.red-bean.com/nightly/en/index.html) and try to decide if you want/need apache or just a local svnserve install. Then go get the appropriate binaries: http://subversion.apache.org/packages.html#windows The easiest way for apache is to go for the collabnet server install that will install a complete apache server setup for you. If you want more control / just svnserve then you might have to settle for 1.6.6 as there is no current maintainer for the 1.6.9 windows binaries (unless you want to build your own). As for client access, try TortoiseSVN for your windows clients, it rocks. ~ Mark C
Re: Migrations with Subversion
2010/3/29 Juan Jesús Cremades Monserrat : > Hi! > > > > I’m administrating a subversion server 1.4.2 version and Tortoise Version > 1.5.4 and I’m thinking to migrate to 1.6.9 in a x86_64 machine. > > > > Could I have any problem? It’s important for me to avoid any conflict. Thank > you very much! See http://svnbook.red-bean.com/nightly/en/svn.reposadmin.maint.html#svn.reposadmin.maint.migrate
Re: [Help] Choose Subversion for Java Application
Cooke, Mark wrote: On Mar 28, 2010, at 22:43, Moch Firman N wrote: Thanks. I have not yet installed any package of subversion, please in advise which version should I install with free license of course ? You should install the latest version of Subversion, currently 1.6.9, and familiarize yourself with the license under which it is released to see if it adequately satisfies your definition of "free". It depends how you want to use it. Read chapters 1 and 6 of the subversion red book (http://svnbook.red-bean.com/nightly/en/index.html) and try to decide if you want/need apache or just a local svnserve install. Then go get the appropriate binaries: http://subversion.apache.org/packages.html#windows The easiest way for apache is to go for the collabnet server install that will install a complete apache server setup for you. If you want more control / just svnserve then you might have to settle for 1.6.6 as there is no current maintainer for the 1.6.9 windows binaries (unless you want to build your own). As for client access, try TortoiseSVN for your windows clients, it rocks. For java you are probably going to be running eclipse so you'd want the subclipse plugin. On the server side the easiest choice will depend on the platform. The major linux versions will have packages as part of the distribution that can be installed with their native package manager. -- Les Mikesell lesmikes...@gmail.com
Problem creating new repo
For 4 hours I have tried to solve this problem but seems like very few had it before. I just installed subversion on a QNAP T410, NAS, which completed all fine however it went wrong when I tried to create the first repository. I use the command: svnadmin create repo_path But in a few moments it just says "Illegal instruction" - which I really can't figure out what means... I tried to delete the directory, make it again and create again, but every time the samme... About half the files are missing and I really can't figure out why... Is there any way to get som more debugging information than just "Illegal instruction"? Anyone knowing how to solve this problem? If you need any more information please ask. -Silwing
Default module for WebDaV?
Hello, In SVN's proposal to join Apache we had a discussion about default module for WebDav protocol: http://old.nabble.com/-PROPOSAL--VOTE--Subversion-to26203843.html where it was said that trunk code was switched to use Serf as the default DAV RA implementation. Will Serf become a default DAV RA implementation in upcoming 1.7 release? Best Regards, Burilo Igor Subversive Team
Re: Problem creating new repo
On Mon, Mar 29, 2010 at 03:08:21PM +0100, Randi Hillerøe wrote: > I just installed subversion on a QNAP T410, NAS, which completed all fine > however it went wrong when I tried to create the first repository. > > I use the command: svnadmin create repo_path > But in a few moments it just says "Illegal instruction" - which I really > can't figure out what means... That's really all it says? No other error messages? > Is there any way to get som more debugging information than just "Illegal > instruction"? Do you have strace or similar available on this machine? Can you build a debug version of Subversion? tyler
Re: Problem creating new repo
On Monday 29 Mar 2010, Randi Hillerøe wrote: > For 4 hours I have tried to solve this problem but seems like very few had > it before. > > I just installed subversion on a QNAP T410, NAS, which completed all fine > however it went wrong when I tried to create the first repository. > > I use the command: svnadmin create repo_path > But in a few moments it just says "Illegal instruction" - which I really > can't figure out what means... > > I tried to delete the directory, make it again and create again, but every > time the samme... About half the files are missing and I really can't > figure out why... > > Is there any way to get som more debugging information than just "Illegal > instruction"? > > Anyone knowing how to solve this problem? > > If you need any more information please ask. > > -Silwing The illegal instruction error sounds like the binary isn't quite compatible with the processor in the nas. I'd suggest trying a different source for the binaries or compiling them yourself. The latter would be better as you can tweak the compiler flags to deal with the illegal op but getting the compiler in the first place might be tricky. I don't recall seeing it the last time I looked at the packages available on ipkg nor could I find a compatible cross compiler environment. Sorry :/ I've got a T109-II, I'll give it a shot tonight myself and see if I also have the problem but without a compiler environment I don't see how it might be fixed. Campbell -- __ Sword Ciboodle is the trading name of ciboodle Limited (a company registered in Scotland with registered number SC143434 and whose registered office is at India of Inchinnan, Renfrewshire, UK, PA4 9LH) which is part of the Sword Group of companies. This email (and any attachments) is intended for the named recipient(s) and is private and confidential. If it is not for you, please inform us and then delete it. If you are not the intended recipient(s), the use, disclosure, copying or distribution of any information contained within this email is prohibited. Messages to and from us may be monitored. If the content is not about the business of the Sword Group then the message is neither from nor sanctioned by us. Internet communications are not secure. You should scan this message and any attachments for viruses. Under no circumstances do we accept liability for any loss or damage which may result from your receipt of this email or any attachment. __
command line to remove a property
So, Any of you command line gurus able to give me a command line that will delete the svn:mime-type property from any file with a .sql extension in my project folder? I'm on windows but do have msysgit installed so grep and some other unix commands are available. BOb
svn copy not updating Last Changed Rev
I noticed that when you svn copy a directory (like for branching and tagging) the 'Last Changed Rev' in svn info only moves forward on the root of the copy and not every file. The most recent revision in svn log will show up as the copy revision though. Shouldn't the 'Last Changed Rev' on a path always be the same as the most recent revision shown in svn log for the same path? I noticed this on svn 1.4.2, but it shows up in 1.6.9 as well. Here is an example from svn 1.6.9 operating with a local repository, but I originally noticed this on svn 1.4.2 with the svn+ssh protocol. $ svn copy -m "test branch" file:///tmp/svn-repo/trunk file:///tmp/svn-repo/branches/mine Committed revision 5. SVN info on the root of the copy shows the expected information: $ svn info file:///tmp/svn-repo/branches/mine Path: mine URL: file:///tmp/svn-repo/branches/mine Repository Root: file:///tmp/svn-repo Repository UUID: f5a3ca28-02f1-438b-b454-8e94791581c1 Revision: 5 Node Kind: directory Last Changed Author: jadevree Last Changed Rev: 5 Last Changed Date: 2010-03-29 13:43:06 -0400 (Mon, 29 Mar 2010) But SVN info on the file that got copied with the branch is wrong: $ svn info file:///tmp/svn-repo/branches/mine/file Path: file Name: file URL: file:///tmp/svn-repo/branches/mine/file Repository Root: file:///tmp/svn-repo Repository UUID: f5a3ca28-02f1-438b-b454-8e94791581c1 Revision: 5 Node Kind: file Last Changed Author: jadevree Last Changed Rev: 2 Last Changed Date: 2010-03-29 13:40:30 -0400 (Mon, 29 Mar 2010) SVN log shows revision 5 as the most recent: $ svn log file:///tmp/svn-repo/branches/mine/file r5 | jadevree | 2010-03-29 13:43:06 -0400 (Mon, 29 Mar 2010) | 1 line test branch r2 | jadevree | 2010-03-29 13:40:30 -0400 (Mon, 29 Mar 2010) | 1 line foo Interestingly enough, this doesn't happen if you do a local copy + commit instead of a server side copy. Having peeked at the fsfs revision files, it seems the two types of copies are represented quite a bit differently internally. $ svn copy trunk branches/bar A branches/bar $ svn commit -m "bar" Adding branches/bar Adding branches/bar/file Committed revision 3. $ svn info file:///tmp/svn-repo/branches/bar/file Path: file Name: file URL: file:///tmp/svn-repo/branches/bar/file Repository Root: file:///tmp/svn-repo Repository UUID: f5a3ca28-02f1-438b-b454-8e94791581c1 Revision: 3 Node Kind: file Last Changed Author: jadevree Last Changed Rev: 3 Last Changed Date: 2010-03-29 13:40:53 -0400 (Mon, 29 Mar 2010) -- Jon "lib64 is a wart on history and should never have been there." -Tollef Fog Heen
RE: svn copy not updating Last Changed Rev
Why would you expect the last changed rev of a file to change just because you coppied it to another path? You didn't actually change that file right? BOb > -Original Message- > From: Jon DeVree [mailto:jadev...@mtu.edu] > Sent: Monday, March 29, 2010 1:56 PM > To: users@subversion.apache.org > Subject: svn copy not updating Last Changed Rev > > I noticed that when you svn copy a directory (like for branching and > tagging) the 'Last Changed Rev' in svn info only moves forward on the > root of the copy and not every file. The most recent revision in svn log > will show up as the copy revision though. Shouldn't the 'Last Changed > Rev' on a path always be the same as the most recent revision shown in > svn log for the same path? > > I noticed this on svn 1.4.2, but it shows up in 1.6.9 as well. > Here is an example from svn 1.6.9 operating with a local repository, but > I originally noticed this on svn 1.4.2 with the svn+ssh protocol. > > $ svn copy -m "test branch" file:///tmp/svn-repo/trunk > file:///tmp/svn-repo/branches/mine > > Committed revision 5. > > SVN info on the root of the copy shows the expected information: > > $ svn info file:///tmp/svn-repo/branches/mine > Path: mine > URL: file:///tmp/svn-repo/branches/mine > Repository Root: file:///tmp/svn-repo > Repository UUID: f5a3ca28-02f1-438b-b454-8e94791581c1 > Revision: 5 > Node Kind: directory > Last Changed Author: jadevree > Last Changed Rev: 5 > Last Changed Date: 2010-03-29 13:43:06 -0400 (Mon, 29 Mar 2010) > > But SVN info on the file that got copied with the branch is wrong: > > $ svn info file:///tmp/svn-repo/branches/mine/file > Path: file > Name: file > URL: file:///tmp/svn-repo/branches/mine/file > Repository Root: file:///tmp/svn-repo > Repository UUID: f5a3ca28-02f1-438b-b454-8e94791581c1 > Revision: 5 > Node Kind: file > Last Changed Author: jadevree > Last Changed Rev: 2 > Last Changed Date: 2010-03-29 13:40:30 -0400 (Mon, 29 Mar 2010) > > SVN log shows revision 5 as the most recent: > > $ svn log file:///tmp/svn-repo/branches/mine/file > > r5 | jadevree | 2010-03-29 13:43:06 -0400 (Mon, 29 Mar 2010) | 1 line > > test branch > > r2 | jadevree | 2010-03-29 13:40:30 -0400 (Mon, 29 Mar 2010) | 1 line > > foo > > > > Interestingly enough, this doesn't happen if you do a local copy + > commit instead of a server side copy. Having peeked at the fsfs revision > files, it seems the two types of copies are represented quite a bit > differently internally. > > $ svn copy trunk branches/bar > A branches/bar > $ svn commit -m "bar" > Adding branches/bar > Adding branches/bar/file > > Committed revision 3. > $ svn info file:///tmp/svn-repo/branches/bar/file > Path: file > Name: file > URL: file:///tmp/svn-repo/branches/bar/file > Repository Root: file:///tmp/svn-repo > Repository UUID: f5a3ca28-02f1-438b-b454-8e94791581c1 > Revision: 3 > Node Kind: file > Last Changed Author: jadevree > Last Changed Rev: 3 > Last Changed Date: 2010-03-29 13:40:53 -0400 (Mon, 29 Mar 2010) > > -- > Jon > "lib64 is a wart on history and should never have been there." > -Tollef Fog Heen
Can checkout and commit but NOT diff or display logs for files or dirs
Hi, I set up a repo on my computer. I run the daemon with the following options: >svnserve.exe -d -r d:\svndata I can then check out and commit to the repo using "svn co svn://localhost/project/trunk project" , BUT I can not do any diff or show logs. But if I instead checkout the repo using "svn co file:///d:/svndata/project/trunk project" everything works perfectly. I have tried to run in listen-once mode with logging to a log file. And I get this line when trying to diff the file readme.txt from the current revision(10) to revision 8. 1736 2010-03-29T17:41:31.690740Z 127.0.0.1 - svndata open 2 cap=(edit-pipeline svndiff1 absent-entries depth mergeinfo log-revprops) /project/trunk/readme.txt SVN/1.6.6%20(r40053) - 1736 2010-03-29T17:41:31.690740Z 127.0.0.1 - svndata get-locations /project/trunk/readme@10 (8) I am running Windows Vista 64 bit and Subversion 1.6.6. The svnserve.exe is added to the firewall exceptions list. Anyone got any ideas of what is going wrong here? I have ran out of fresh ideas... Best regards, Björn
Re: command line to remove a property
On Mon, Mar 29, 2010 at 13:49, Bob Archer wrote: > So, > > > > Any of you command line gurus able to give me a command line that will > delete the svn:mime-type property from any file with a .sql extension in my > project folder? I'm on windows but do have msysgit installed so grep and > some other unix commands are available. Right from the standard Command Prompt: svn propdel svn:mime-type *.sql This won't recurse through subdirectories though; you might have to wrap it in a script to process each subdirectory.
Re: svn copy not updating Last Changed Rev
On Mon, Mar 29, 2010 at 14:02:06 -0400, Bob Archer wrote: > Why would you expect the last changed rev of a file to change just > because you coppied it to another path? You didn't actually change > that file right? First, the value changes if you use svn copy locally and commit the results. So I would expect the behavior of using svn copy using two URLs to have the same behavior. Second, the revision shows up in the log for that file. So there is an inconsistency here. Either the file was changed and the log is correct, or nothing changed and the log shouldn't really be there either. Finally, you could just as easily argue that branches/mine/ is a copy of trunk/ and did not actually change either. So why would that have an updated revision number but nothing else does? I should add that I only showed this on a file, but it actually happens to both files and directories beneath the root of the copy operation. -- Jon "lib64 is a wart on history and should never have been there." -Tollef Fog Heen
Re: command line to remove a property
This will take care of the recursion: for /R %f in (*.sql) do svn propdel svn:mime-type "%f" -- Stein
RE: command line to remove a property
> This will take care of the recursion: > > for /R %f in (*.sql) do svn propdel svn:mime-type "%f" > > -- > Stein Brilliant... thanks. This seems to do the trick. BOb
RE: command line to remove a property
> -Original Message- > From: Stein Somers [mailto:ssom...@opnet.com] > Sent: maandag 29 maart 2010 21:06 > To: users@subversion.apache.org > Subject: Re: command line to remove a property > > This will take care of the recursion: > > for /R %f in (*.sql) do svn propdel svn:mime-type "%f" $ svn propdel -R svn:mime-type . should work as well. Bert
RE: ignore local change
Thanks Bob and David, it's helpful. I'll look whether I can customize diff command. Regards, Ben Kim On Thu, 25 Mar 2010, Bob Archer wrote: BTW: TortoiseSVN does implement the "ignore change list" idea. Although, I would rather go with checking in a template and then using build scripts or deploy scripts to create the correctly named file populating and tokens in the file that need to be customized. BOb There's no way to do this easily: Ignoring is only for non-subversion files. For example, if every time I do a build, a directory called "build" is created, I can create an ignore, so that this directory won't show up on "svn status', but if a file is changed and is part of the Subversion repository, ignore won't work. What you can do is create a changelist and use that when you do commands like svn status and svn diff. (BTW, I think you meant "svn diff" in your original post. All "svn status" would do is list that the file was modified). Unfortunately, you have to keep manually maintaining your changelists and remember to use the --cl parameter when you do things like "svn status", "svn info", and of course, "svn commit". Just as aside: I like the way Perforce handles changelists. In Perforce you have the concept of a default changelist. All files that are changed are placed in the default changelist unless you specify otherwise. When you do any workspace command like a diff or commit, and you don't specify a changelist, Perforce automatically operates only on the default changelist. That makes it easy to make a change in a file, and then toss it into an "ignore" changelist. Doing a diff or status will ignore the "ignore" changelist unless you specify otherwise in the workspace command. And, most importantly, when you do a commit, and you don't specify a changelist, only the files in your default changelist are committed and not the ones in your "ignore" changelist. The only issue is that developers sometimes forget about their "ignore" changelist and never revert the changes or commit them. That can allow a build to succeed on a developer's machine, but fail when the build server attempts to do the build. On Thu, Mar 25, 2010 at 12:54 PM, Ben Kim wrote: Dear list, version: subversion 1.6.6 on cygwin, FC12 and also tortoise svn. I have some local changes that I want to keep, and wish they did not show up in svn status. For example, on production mail = "#users_real_email#" on dev machine mail = "#fake_email_for_debugging#" I want subversion to ignore this difference when I do "svn status" locally. < mail = "#users_real_email#" --- mail = "#fake_email_for_debugging#" But if there are other changes except for this, I want them to show upon "svn status". There is a need to change the file from time to time, so I don't want to put the whole file in svn:ignore list. Is there a feature in subversion or subversion-perl that allows me to let subversion "ignore" only certain differences within a file? Thanks. Ben Kim -- David Weintraub qazw...@gmail.com
Building for Win32 - tests fail
Hi
I now started building subversion 1.6.9 for Win32, starting from the
vc6-build.bat.in template.
Everything looks fine when building (after a very few tweaks) and
running the test using file:// and svn:// protocol looks good (for both
fsfs and bdb-backend).
But when running against http:// I get
22 tests SKIPPED
25 tests XFAILED
74 tests FAILED (list below)
1 tests XPASSED
Searching for some of them didn't give me any clues.
My environment:
WindowsXP MCE, fully updated (except IE7 and IE8) using WindowsUpdate.
Visual C++ 6 with SP 3
PlatformSDK February 2003 (latest for VC++6)
Python 2.6.5
ActivePerl 5.10.1.1007
Apache 2.2.15
Anybody got some ideas?
/David
FAIL: basic_tests.py 42: basic relative url target using current dir
FAIL: basic_tests.py 43: basic relative url target using other targets
FAIL: commit_tests.py 39: set revision props during remote mkdir
FAIL: commit_tests.py 40: set revision props during remote delete
FAIL: commit_tests.py 41: set revision props during commit
FAIL: commit_tests.py 42: set revision props during import
FAIL: commit_tests.py 43: set revision props during repos-to-repos copy
FAIL: commit_tests.py 44: set revision props during wc-to-repos copy
FAIL: commit_tests.py 45: set revision props during repos-to-repos move
FAIL: commit_tests.py 46: set revision props during remote property edit
FAIL: commit_tests.py 47: set multiple revision props during remote mkdir
FAIL: commit_tests.py 48: set revprop without value ('') during remote
mkdir
FAIL: commit_tests.py 49: set revprop without '=' during remote mkdir
FAIL: log_tests.py 5: 'svn log -r COMMITTED' of dynamic/local WC rev
FAIL: log_tests.py 19: test 'svn log -g' a path added before merge
FAIL: log_tests.py 24: test revprop retrieval
FAIL: merge_authz_tests.py 1: skipped paths get overriding mergeinfo
FAIL: stat_tests.py 17: status output in XML format
FAIL: stat_tests.py 21: status -v -N -u from different current directories
FAIL: stat_tests.py 24: run 'status -u' variations w/ incoming propchanges
FAIL: stat_tests.py 25: run 'status -uv' w/ incoming propchanges
FAIL: stat_tests.py 31: status with tree conflicts
FAIL: trans_tests.py 1: commit new files with keywords active from birth
FAIL: blame_tests.py 4: blame output in XML format
FAIL: blame_tests.py 6: blame targets with peg-revisions
FAIL: blame_tests.py 8: ignore whitespace when blaming
FAIL: blame_tests.py 9: ignore eol styles when blaming
FAIL: blame_tests.py 10: test 'svn blame -g'
FAIL: blame_tests.py 11: don't look for merged files out of range
FAIL: blame_tests.py 12: blame target not in HEAD with peg-revisions
FAIL: blame_tests.py 14: blame -g output with inserted lines
FAIL: lock_tests.py 1: lock a file and verify that it's locked
FAIL: lock_tests.py 2: commit a file and keep lock
FAIL: lock_tests.py 3: commit a file and release lock
FAIL: lock_tests.py 4: commit a locked file with a prop change
FAIL: lock_tests.py 5: lock a file and verify lock breaking behavior
FAIL: lock_tests.py 6: lock a file and verify lock stealing behavior
FAIL: lock_tests.py 7: examine the fields of a lockfile for correctness
FAIL: lock_tests.py 8: verify behavior when a lock in a wc is defunct
FAIL: lock_tests.py 10: verify svn:needs-lock behavior with defunct lock
FAIL: lock_tests.py 11: verify lock removal on a deleted path
FAIL: lock_tests.py 12: lock and unlock some files
FAIL: lock_tests.py 13: verify removal of a directory with locks inside
FAIL: lock_tests.py 14: verify status of lock in working copy
FAIL: lock_tests.py 15: verify status of stolen lock
FAIL: lock_tests.py 16: verify status of broken lock
FAIL: lock_tests.py 18: lock an out-of-date file and ensure failure
FAIL: lock_tests.py 19: update handles svn:needs-lock correctly
FAIL: lock_tests.py 20: verify svn:needs-lock behavior with revert
FAIL: lock_tests.py 21: examine the fields of a lock from a URL
FAIL: lock_tests.py 22: lock/unlock several files in one go
FAIL: lock_tests.py 23: lock/unlock switched files
FAIL: lock_tests.py 24: lock and unlock a file with an URI-unsafe name
FAIL: lock_tests.py 27: commit file with xml-unsafe name and release lock
FAIL: lock_tests.py 28: verify info p...@x or path -rY return repos lock
FAIL: lock_tests.py 29: (un)lock set of files, one already (un)locked
FAIL: lock_tests.py 30: show correct lock info on moved path
FAIL: lock_tests.py 31: ls locked path needing URL encoding
FAIL: lock_tests.py 33: verify recursive info shows lock info
FAIL: lock_tests.py 35: lock a file using a comment with xml special chars
FAIL: svnsync_tests.py 14: verify that unreadable content is not synced
FAIL: svnsync_tests.py 15: verify that copies from unreadable dirs work
FAIL: svnsync_tests.py 16: verify copies with mods from unreadable dirs
FAIL: svnsync_tests.py 17: verify copies with mods from unreadable dirs
+copy
FAIL: authz_tests.py 3: broken authz files cause errors
FAIL: authz_tests.py 4: test authz f
Re: svn copy not updating Last Changed Rev
Jon DeVree wrote on Mon, 29 Mar 2010 at 14:19 -0400: > On Mon, Mar 29, 2010 at 14:02:06 -0400, Bob Archer wrote: > > Why would you expect the last changed rev of a file to change just > > because you coppied it to another path? You didn't actually change > > that file right? > > First, the value changes if you use svn copy locally and commit the > results. So I would expect the behavior of using svn copy using two URLs > to have the same behavior. I don't see any difference: [[[ % svn up At revision 1. % svnversion 1 % svn cp -q iota iota2 % svn ci -q -m "r2: add iota2" % svn cp -q ^/trunk/iota ^/trunk/iota3 -m "r3: add iota3" % svn up -q % svn info iota2 iota3 | grep "Last Changed Rev" Last Changed Rev: 2 Last Changed Rev: 3 % ]]] In both cases, the "Last Changed Rev" is the revision of the copy. > I should add that I only showed this on a file, but it actually happens > to both files and directories beneath the root of the copy operation. Hmmm.
Re: Problem creating new repo
Keep replies on list if you want help. On Mon, Mar 29, 2010 at 07:32:46PM +0100, Randi Hillerøe wrote: > No other error message... I've searched a lot to find some way to get just a > bit more info, but I didn't find anything :S strace, isn't that some linux > stuff? Or is it possible to install on windows too? Yes, strace is a Linux tool. Presumably a similar tool exists for whatever OS you're running (this NAS you're using runs Windows? curious.) tyler > 2010/3/29 Tyler Roscoe > > > On Mon, Mar 29, 2010 at 03:08:21PM +0100, Randi Hillerře wrote: > > > I just installed subversion on a QNAP T410, NAS, which completed all fine > > > however it went wrong when I tried to create the first repository. > > > > > > I use the command: svnadmin create repo_path > > > But in a few moments it just says "Illegal instruction" - which I really > > > can't figure out what means... > > > > That's really all it says? No other error messages? > > > > > Is there any way to get som more debugging information than just "Illegal > > > instruction"? > > > > Do you have strace or similar available on this machine? Can you build a > > debug version of Subversion? > > > > tyler > >
Re: Problem creating new repo
On Mar 29, 2010, at 15:55, Tyler Roscoe wrote: > On Mon, Mar 29, 2010 at 07:32:46PM +0100, Randi Hillerøe wrote: >> No other error message... I've searched a lot to find some way to get just a >> bit more info, but I didn't find anything :S strace, isn't that some linux >> stuff? Or is it possible to install on windows too? > > Yes, strace is a Linux tool. Presumably a similar tool exists for > whatever OS you're running (this NAS you're using runs Windows? > curious.) According to the manufacturer, the QNAP TS-410 Turbo NAS runs an embedded Linux operating system. http://www.qnap.com/pro_detail_software.asp?p_id=134 QNAP uses a package manager called QPKG. If it's not already installed, you could see if strace is available via QPKG. http://www.qnap.com/QPKG.asp
Re: svn copy not updating Last Changed Rev
On Mon, Mar 29, 2010 at 23:53:43 +0300, Daniel Shahaf wrote: > [[[ > % svn up > At revision 1. > > % svnversion > 1 > > % svn cp -q iota iota2 > > % svn ci -q -m "r2: add iota2" > > % svn cp -q ^/trunk/iota ^/trunk/iota3 -m "r3: add iota3" > > % svn up -q > > % svn info iota2 iota3 | grep "Last Changed Rev" > Last Changed Rev: 2 > Last Changed Rev: 3 > Try it with a directory that includes files and subdirectories and you'll be able to reproduce it. The actual directory used as the root of the copy operation has the correct Last Changed Rev, as I noted already: > SVN info on the root of the copy shows the expected information: > > $ svn info file:///tmp/svn-repo/branches/mine > Last Changed Author: jadevree > Last Changed Rev: 5 > Last Changed Date: 2010-03-29 13:43:06 -0400 (Mon, 29 Mar 2010) It is the files and subdirectories of this that are wrong: > But SVN info on the file that got copied with the branch is wrong: > > $ svn info file:///tmp/svn-repo/branches/mine/file > Last Changed Author: jadevree > Last Changed Rev: 2 > Last Changed Date: 2010-03-29 13:40:30 -0400 (Mon, 29 Mar 2010) And this is inconsistent with what svn log reports as the last change: > $ svn log file:///tmp/svn-repo/branches/mine/file > > r5 | jadevree | 2010-03-29 13:43:06 -0400 (Mon, 29 Mar 2010) | 1 line > > test branch > > r2 | jadevree | 2010-03-29 13:40:30 -0400 (Mon, 29 Mar 2010) | 1 line > > foo > -- Jon "lib64 is a wart on history and should never have been there." -Tollef Fog Heen
RE: svn copy not updating Last Changed Rev
> On Mon, Mar 29, 2010 at 23:53:43 +0300, Daniel Shahaf wrote: > > [[[ > > % svn up > > At revision 1. > > > > % svnversion > > 1 > > > > % svn cp -q iota iota2 > > > > % svn ci -q -m "r2: add iota2" > > > > % svn cp -q ^/trunk/iota ^/trunk/iota3 -m "r3: add iota3" > > > > % svn up -q > > > > % svn info iota2 iota3 | grep "Last Changed Rev" > > Last Changed Rev: 2 > > Last Changed Rev: 3 > > > > Try it with a directory that includes files and subdirectories and > you'll be able to reproduce it. The actual directory used as the root of > the copy operation has the correct Last Changed Rev, as I noted already: > > > SVN info on the root of the copy shows the expected information: > > > > $ svn info file:///tmp/svn-repo/branches/mine > > Last Changed Author: jadevree > > Last Changed Rev: 5 > > Last Changed Date: 2010-03-29 13:43:06 -0400 (Mon, 29 Mar 2010) > > It is the files and subdirectories of this that are wrong: > > > But SVN info on the file that got copied with the branch is wrong: > > > > $ svn info file:///tmp/svn-repo/branches/mine/file > > Last Changed Author: jadevree > > Last Changed Rev: 2 > > Last Changed Date: 2010-03-29 13:40:30 -0400 (Mon, 29 Mar 2010) > > And this is inconsistent with what svn log reports as the last change: > > > $ svn log file:///tmp/svn-repo/branches/mine/file > > > > r5 | jadevree | 2010-03-29 13:43:06 -0400 (Mon, 29 Mar 2010) | 1 line > > > > test branch > > > > r2 | jadevree | 2010-03-29 13:40:30 -0400 (Mon, 29 Mar 2010) | 1 line > > > > foo > > > You don't show what your pwd is when you do these commands. but I think the default range is 1:BASE if you are in a working copy. Does the log change if you use: svn log -r HEAD :///tmp/svn-repo/branches/mine/fil BOb
Re: Can checkout and commit but NOT diff or display logs for files or dirs
2010/3/29 Björn Blissing : > Hi, > > I set up a repo on my computer. I run the daemon with the following options: > >>svnserve.exe -d -r d:\svndata > > I can then check out and commit to the repo using "svn co > svn://localhost/project/trunk project" , BUT I can not do any diff or show > logs. > But if I instead checkout the repo using "svn co > file:///d:/svndata/project/trunk project" everything works perfectly. > > I have tried to run in listen-once mode with logging to a log file. And I get > this line when trying to diff the file readme.txt from the current > revision(10) to revision 8. > > 1736 2010-03-29T17:41:31.690740Z 127.0.0.1 - svndata open 2 > cap=(edit-pipeline svndiff1 absent-entries depth mergeinfo log-revprops) > /project/trunk/readme.txt SVN/1.6.6%20(r40053) - > 1736 2010-03-29T17:41:31.690740Z 127.0.0.1 - svndata get-locations > /project/trunk/readme@10 (8) > > I am running Windows Vista 64 bit and Subversion 1.6.6. The svnserve.exe is > added to the firewall exceptions list. > > Anyone got any ideas of what is going wrong here? I have ran out of fresh > ideas... What's the exact command that you're running for diff or log? And what's the error message (if any) that you get from your svn client? -- Johan
Re: svn copy not updating Last Changed Rev
On Mon, Mar 29, 2010 at 18:15:19 -0400, Bob Archer wrote: > You don't show what your pwd is when you do these commands. but I think the > default range is 1:BASE if you are in a working copy. Does the log change if > you use: > > svn log -r HEAD :///tmp/svn-repo/branches/mine/fil > Good question, I was using the repository URLs just to be sure of cases like this, but apparently that isn't enough. I have gone back and confirmed that this occurs even when I'm outside of a working copy. In fact, it occured to me that this should be visible on any public subversion repository that used a server side svn copy operation. Even the repository of svn itself: Here is the most recent log entry for the build subdirectory of subversion in the 1.6.9 tag: svn log --stop-on-copy http://svn.apache.org/repos/asf/subversion/tags/1.6.9/build r901401 | hwright | 2010-01-20 17:08:30 -0500 (Wed, 20 Jan 2010) | 1 line Tag 1.6.9 release with svn_version.h matching tarball. But if you request svn info on the same URL it shows a different revision as the most recent change: $ svn info http://svn.apache.org/repos/asf/subversion/tags/1.6.9/build | grep ^Last Last Changed Author: hwright Last Changed Rev: 884204 Last Changed Date: 2009-11-25 12:23:50 -0500 (Wed, 25 Nov 2009) -- Jon "lib64 is a wart on history and should never have been there." -Tollef Fog Heen
Re: Junior developers
On Wed, Feb 24, 2010 at 3:10 AM, Alan Barrett wrote: > On Wed, 17 Feb 2010, dcz wrote: >> Here is what I'm trying to do : some user (let's call them junior >> developer) should require their commit to be authorized by other >> (senior developer) before they would actually be committed. > > You could require the junior developer to put a line like this > in the log message: > > Approved by: > > Then you could have a pre-commit hook that rejects commits from junior > developers, unless that line is present in the log message. If the > junior developer lies about whether the code has been approved, then > you have a non-technical problem to solve outside svn. You could also > extend this by requiring the log message to contain a reference number > to an external database that tracks code reviews and approvals. > > --apb (Alan Barrett) > I know this is old but I wanted to chime in (actually found this thread while searching for references to Review Board). While my use case is slightly different (we want approvals for all commits, not just from a specific type of user), if you're capable of doing some coding, this is a solvable problem. Here's the method I'm working on: Developer: 1) Checks out repository and makes changes. 2) When changes are ready for review, generate a changelist. a) A changelist ID (integer) is generated in an SQL database. b) The changelist ID is used to create a local SVN client changelist, with that ID as the name. c) A custom SVN revprop is set with the changelist ID. 3) User emails out the diff, to a reviewer, and a conversation commences. Reviewer(s): 4) When the review has been approved (including any changes requesting during the review), the reviewer marks the change as approved. a) The changelist ID, in the database, has an is_approved boolean and this is set True. b) An e-mail is sent to the developer, informing them that their change has been approved. Developer: 5) Developer commits their changelist. a) Pre-commit script checks the changelist ID revprop and verifies that is_approved and active are both True. (active gets set false, after a successful commit, so that changelist IDs don't get reused). b) Post commit script grabs the commit revision and emails out a commit notice, with revision information, to the reviewer(s) and sets the active boolean, in our DB, to False. While this is a somewhat complex procedure, it's really simple to implement if you have some coding skills. Since my last employer was a junkie for Python, I did all of this using pysvn (http://pysvn.tigris.org/). I'd just give out the code (and may still, if I can get permission to OSS it) but, for now, it's the intellectual property of my current employer. I attempted a couple other methods but this one worked the best, with the fewest race conditions. The best part though is that it's an easy sell. This method is based on what I recall of Google's code review methods, from 2004-2006 (implemented without having ever seen their actual code... so it could definitely be better). Beyond the normal SVN subcommands, I had implement these: abandon -If the change is decided to be bad, abandon it completely. approve -Allow a reviewer to simply run "custom_svn approve --cl ". change -Generate a changelist, and changelist config, based on current workspace modifications. client -We want people to be able to manage repos independently, for various reasons. This could be left out. mail -A developer only has to run "custom_svn mail --cl " to send out a request for review. I'm starting work on getting this to talk to Review Board now (thus the search). I also had to hijack and slightly reimplement commit, so that we can run "custom_svn commit --cl " and work my magic. If you really only want to require review and approvals for junior developers, that wouldn't be that hard to add. You could have a user list and have the pre-commit script only trigger when a user is/isn't in a list. If I were to do it, I would probably maintain LDAP groups, based on language, for people who you trust to not need a review. Again, using Google as a reference, having a group (like python-trusted) that people are added to, once they past some sort of coding/style test, and skipping the hard verification test would probably be ideal. Wow that was long... Again, I know this is a month old but I wanted to toss my thoughts into the ring. If I am able to OSS this, or parts of it, I'll make an announcement here and/or on the pvsvn list (after I make sure it's not against the rules). If someone wants to chat more about my implementation, I'm perfectly willing to talk non specifics and help where I can. -- --tucker
Re: Problem creating new repo
Oh sry for hitting the wrong answer button... I'm not that used to mailing lists... I'll look for strace somewhere.. There is both QPKG which has a web interface for installing and the IPKG which I can use through SSH. 2010/3/29 Ryan Schmidt > > On Mar 29, 2010, at 15:55, Tyler Roscoe wrote: > > > On Mon, Mar 29, 2010 at 07:32:46PM +0100, Randi Hillerøe wrote: > >> No other error message... I've searched a lot to find some way to get > just a > >> bit more info, but I didn't find anything :S strace, isn't that some > linux > >> stuff? Or is it possible to install on windows too? > > > > Yes, strace is a Linux tool. Presumably a similar tool exists for > > whatever OS you're running (this NAS you're using runs Windows? > > curious.) > > According to the manufacturer, the QNAP TS-410 Turbo NAS runs an embedded > Linux operating system. > > http://www.qnap.com/pro_detail_software.asp?p_id=134 > > QNAP uses a package manager called QPKG. If it's not already installed, you > could see if strace is available via QPKG. > > http://www.qnap.com/QPKG.asp > > >
