Login | Register
My pages Projects Community openCollabNet

Discussions > dev > Re: migration script 1.2

fsvs
Discussion topic

Back to topic list

Re: migration script 1.2

Author pmarek
Full name P.Marek
Date 2008-12-08 05:38:30 PST
Message Hello Gunnar!

On Monday 08 December 2008 Gunnar Thielebein wrote:
> some questions about the script.
>
> When looking in /var/spool/fsvs/dd i see a lot of folder labeled with
> 2digixt hexcode that if understand correctly represents dirs in filesystem.
Not exactly.
The WAA names are MD5(path), but with two directory levels - like you write
below.

If it's just in the "dd" folder, then you got lucky :-)

> In /etc/fsvs there is one folder present which is configuration folder
> of the path i am monitoring with fsvs (for me this is root).
> First task is now to move "Urls" out of all pathes e.g. like
> /etc/fsvs/6666cd76f9​6956469e7be39d750cc7​d9/ and into
> /var/spool/66/66/cd7​6f96956469e7be39d750​cc7d9, correct?
No - the next version will have a per-WC prefix in the WAA structure, so it
will be
  /var/spool/6666/66/66/..../
Other files will be like this:
  MD5(/etc/services) = cdd8f7859d9a2306f50d​599fd2a26edf
  /var/spool/6666/cd/d​8/f7859d9a2306f50d59​9fd2a26edf/


> This pathes I
> have here in example are from debian packges dir-structures and may differ.
> Then you want to clean up WAA? I dont understand what you mean with
> cleanup, can you specify?
> Some other comments in org. post.
Older FSVS versions created too many directories in the WAA structure, and
didn't remove them cleanly in all cases.
So there might be empty directory structures which could get cleaned up.

> > Well, then please see whether you get something up and running.
> >
> > Short description:
> > - The $FSVS_WAA has an additional level, that's determined by a few (per
> > default 4) characters of the MD5 of the WC path.
> > I'd suggest just running "fsvs info <wc>" to get the correct paths.
> > Extra points if you're using the $FSVS_CONF/*/_base links to do that
> > for all used WCs on the machine.
>
> I see no other way than the $FSVS_CONF/*/_base approach, please correct me.
I meant to look for the _base links, and get the correct WAA path by looking
at the output of "fsvs info <wc-path>" - that would show whether the binary
was compiled with the default of 4 characters for the WC-distinction in the
WAA area, or maybe some other value.


> > - The URLs file has to be moved to the WAA
> > - And the WAA has either to be cleaned up, or the data moved correctly.
> > Please see that at least the "dir" files is moved; although the
> > properties
>
> Can you specify "dir" file? Where to move?
All of the files in the WAA have to be moved to the "new" specific
WAA-directories, ie. the ones with the WC-path-prefix in them.

Like your example above - the first 4 characters of MD5(/) = 6666, so it would
be
  /var/spool/6666/ + structure in original WAA.

> > would be nice - else a "fsvs sync-repos" run would be necessary to
> > avoid the loss of the properties.
>
> fsvs sync-repo - before we start migration?
> Should all fsvs relevant tasks be done with the new version of fsvs or
> should migration be done in a pre-upgrade step?
> I mean, does the fsvs 1.2.x own the same syntax or should this be used
> for testing script. I am still with 1.1.16 atm.
All operations should be done with the new version.
If we could just move the "dir" file, we wouldn't need the "sync-repos" - then
the user wouldn't loose all local user changes like "add", "prop-set" etc.

> > Maybe looking for all "prop" files in the WAA, and correlating them to
> > the working copy (by getting a list of all known entries by "fsvs st -v")
> > would be best.
> > The "md5s" and "cflct" files would be nice, too, but are not as
> > important.
>
> I cant find "prop" files. In which step did they get created? Where
> should they be moved too?
They get created if the user defines additional, user-specific properties.
Like the fsvs:commit-pipe.


Thank you *very much* for your effort and the time you're putting into this!


Regards,

Phil

--
Versioning your /etc, /home or even your whole installation?
             Try fsvs (fsvs.tigris.org)!

« Previous message in topic | 2 of 17 | Next message in topic »

Messages

Show all messages in topic

migration script 1.2 tekknokra Gunnar Thielebein 2008-12-08 05:10:06 PST
     Re: migration script 1.2 pmarek P.Marek 2008-12-08 05:38:30 PST
     Re: migration script 1.2 pmarek P.Marek 2008-12-10 23:32:20 PST
         Re: migration script 1.2 tekknokra Gunnar Thielebein 2008-12-11 02:34:13 PST
         Re: migration script 1.2 tekknokra Gunnar Thielebein 2008-12-11 10:22:07 PST
             Re: migration script 1.2 pmarek P.Marek 2008-12-12 09:22:31 PST
                 Re: migration script 1.2 pmarek P.Marek 2008-12-12 11:09:11 PST
                     Re: migration script 1.2 pmarek P.Marek 2008-12-12 11:10:20 PST
                     Re: migration script 1.2 tekknokra Gunnar Thielebein 2008-12-13 05:30:29 PST
                         Re: migration script 1.2 pmarek P.Marek 2008-12-13 11:12:16 PST
                             Re: migration script 1.2 tekknokra Gunnar Thielebein 2009-01-08 09:23:04 PST
                                 Re: migration script 1.2 pmarek P.Marek 2009-01-09 09:46:27 PST
                                     Re: migration script 1.2 pmarek P.Marek 2009-02-08 01:05:41 PST
                                         Re: migration script 1.2 tekknokra Gunnar Thielebein 2009-02-08 04:03:36 PST
                                             Re: migration script 1.2 pmarek P.Marek 2009-02-08 05:08:02 PST
                                                 Re: migration script 1.2 tekknokra Gunnar Thielebein 2009-02-09 04:27:56 PST
     Re: migration script 1.2 pmarek P.Marek 2009-02-09 09:25:50 PST
Messages per page: