P.Marek wrote: > Hello Peter! Hi Philipp,
> On Friday 19 December 2008 Peter Rabbitson wrote: >> I finally found some time to try and use fsvs on a real machine. I hit a >> roadblock - the first commit does not happen no matter what I do. > Your email was wrapped in some lines, so I have to guess a bit. > > <snip mundane explanation> > > Aha, here's the culprit! > You tell FSVS to use > svn+ssh://[email protected]/space/system/svn_repos/fsvs/trunk/morlock, > but this path doesn't actually exist in the repository! > > FSVS doesn't create intermediate directories *above* the base URL, only > within the working copy. > > You'll need to create that first, eg. by > svn mkdir > svn+ssh://[email protected]/space/system/svn_repos/fsvs/trunk -m1 > svn mkdir > svn+ssh://[email protected]/space/system/svn_repos/fsvs/trunk/morlock -m2 Well this was certainly unexpected. It would be beneficial imho to pepper this around all existing howtos. Instead of what you propose it is better written as: URL="<your new fsvs svn url>" svn mkdir --parents "$URL" -m "Initialize subdirs" fsvs urls "$URL" > Then you could do a "fsvs sync", to get it to know the current repository > revision, and off you go with > fsvs commit > Yep everything worked from this point on. I have a couple of cosmetic questions though 1) What is the difference between fsvs sync and fsvs update? Documentation is vague on this. 2) Could you review the following ignore/take list and tell me if it is sane? This is my first time really using fsvs, I just want to know I am not doing something rather stupid. Also it is a shame fsvs ignore load does not support comments. Currently I have to do: grep -v '^#' fsvs.ign | fsvs ignore load Thank you for the wonderful tool! Peter my fsvs.ign ================ # ignore all backup/special files /**[-.]old /**.lock /**[-~] # we do not need/can not version anything fsvs related /etc/fsvs /var/spool/fsvs # this is sensitive and the auto-encrypt plugin is not quite ready /etc/*shadow* /etc/ssh/*_key /etc/ssl/private # lvm keeps too much history /etc/lvm/cache /etc/lvm/archive # other than that we do want to version everything in /etc t/etc/** # version lost+found to easily spot remnants of ext3 corruption t/**/lost+found # we want to keep every kernel we ever used t/boot/** # and we want to keep the state of the apt system t/var/lib/aptitude/** t/var/lib/dpkg/** # everything else is of no interest at this point /** ------------------------------------------------------ http://fsvs.tigris.org/ds/viewMessage.do?dsForumId=3928&dsMessageId=988040 To unsubscribe from this discussion, e-mail: [[email protected]].
