svndumpfilter help
I have a new problem. Not a problem with the software I think this is sysadmin/user error. I've read the docs and examples on how to use svnadmin dump and svndumpfilter. I'm familiar with dumps and loads. But I have a new task appointed to me. I have a directory structure that looks like this: svn://x.x.x.x/mainproject/branch/this_new_stuff Developers want to take /this_new_stuff as a dump, and create a new repo so it'll look like this: svn://x.x.x.x/this_new_stuff So far so good, I'll try svndumpfilter. So I do: svnadmin dump mainproject > mainproject.dump svndumpfilter include this_new_stuff > new_stuff_only.dmp svnadmin create new_stuff cd new_stuff svnadmin load . < ../new_stuff_only.dmp ... ... lots of messages that it is loading ... it's going good, I'm getting stoked it is working ... ... whew, it's a lot, almost done done. Now I then go to my PC and do a tortoise browse svn://x.x.x.x/this_new_stuff And it is EMPTY. I look at the logs on tortoise and I can sell all the developer logs with the check-ins I've looked into new_stuff_only.dmp and see a lot of stuff I've tried "dump-empty-revs and renumber-revs and preserve-revprops". The first 2 gives me that error inside the dump file that says something like "empty this is just for padding or something like that' Then I finally used "preserve-revprops" and I didn't get that error and the logs show up with the developer check-ins. Am I missing something? Maybe another step? All my googling just refers to svnadmin dump and svndumpfilter. I'm googling thins like "subversion dump folder into new repo" and I'm getting svndumpfilter as the way to do it. TIA! -- eric
svn crash log
Please find log and dmp files attached as directed in the console output. "Please send the log file to users@subversion.apache.org to help us analyze and solve this problem." The information contained in this email message and its attachments is intended only for the private and confidential use of the recipient(s) named above, unless the sender expressly agrees otherwise. Transmission of email over the Internet is not a secure communications medium. If you are requesting or have requested the transmittal of personal data, as defined in applicable privacy laws by means of email or in an attachment to email, you must select a more secure alternate means of transmittal that supports your obligations to protect such personal data. If the reader of this message is not the intended recipient and/or you have received this email in error, you must take no action based on the information in this email and you are hereby notified that any dissemination, misuse or copying or disclosure of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by email and delete the original message. svn-crash-log20160203154435.dmp Description: svn-crash-log20160203154435.dmp svn-crash-log20160203154435.log Description: svn-crash-log20160203154435.log
Re: svn crash log
Hi John, Please find log and dmp files attached as directed in the console output. “Please send the log file to users@subversion.apache.org to help us analyze and solve this problem.” The information contained in this email message and its attachments is intended only for the private and confidential use of the recipient(s) named above, unless the sender expressly agrees otherwise. Transmission of email over the Internet is not a secure communications medium. If you are requesting or have requested the transmittal of personal data, as defined in applicable privacy laws by means of email or in an attachment to email, you must select a more secure alternate means of transmittal that supports your obligations to protect such personal data. If the reader of this message is not the intended recipient and/or you have received this email in error, you must take no action based on the information in this email and you are hereby notified that any dissemination, misuse or copying or disclosure of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by email and delete the original message. I checked out the dump you got and would ask you to test the issue with the latest SilkSVN 1.8 version (1.8.15) to see whether the issue was resolved. Regards, Stefan
