Hello Simon!
On Montag, 16. Juli 2007 Simon Sprünker wrote:
> I ran into a problem using the recursive revert using fsvs 1.1.6 (did
> not try with older versions):
>
> I am versioning / on a machine. I uninstalled htop
but didn't commit, I think?
> and deleted
> /var/spool/fsvs and /etc/fsvs.
Why did you that? To simulate a catastrophic recovery?
> Then I did
>
> [HEAD]vm-one:/# fsvs sync-repos
Yes, that should restore the needed filelist.
> [HEAD]vm-one:/# fsvs revert -R /
> Reverting to revision 5:
> .m.? 0 ./var/lib/apt/lists/lock
> D... 73252 ./usr/bin/htop
> D... 1707 ./usr/share/man/man1/htop.1.gz
>
> Warning [id=chown-other, action=stop]:
> Cannot chown "./usr/share/doc/htop" to 0:0
>
> An error occurred: No such file or directory (2)
> in up__set_meta_data
What does "fsvs st" say, just after the "sync-repos"?
Please try a "fsvs revert -R -C" - the "-C" tells fsvs to check *all*
directories for missing elements. The sync-repos is not perfect yet, in that
it (has to) take the current timestamps ... But there I could verify
something; that's possibly fixed by taking the ctime as a hint only.
> You may ask, why I did the above steps. I did not find anything in docs
> on how to achieve the following use case: You version a machine, it
> breaks, you install a minimial system and update to the latest revision
> in the repository. I thought the above steps simulate this process.
Well, I'd have recommended doing something like
- Booting with a knoppix or similar
- Make fsvs available (will get easier as soon as distributions include it)
- Go to your harddisk-root (here taken as /mnt)
cd /mnt
- Do
fsvs export $URL
that restores your machine (or at least should); optionally use -rREV.
- Call "lilo", "grub-install" or whatever
- Reboot into the machine.
- Now all you have to do is restore the FSVS' filelist:
cd /
fsvs sync-repos
I didn't take the time yet, but there should be a "--chroot" parameter for
commands, that would simply go
fsvs urls --chroot /mnt $URL
fsvs update --chroot /mnt
and restore the file list and other settings in a single step - by knowing
that /mnt will be the new root.
Currently that doesn't work, because the path is taken to distinguish working
copies - and "/mnt" != "/".
Maybe I'll put that into a single command, "fsvs restore" or something like
that.
> My ignores do not cover ./usr/share/doc/htop.
>
> Did I mess up? Is there a better way to do what I want?
Well, you see how it *should* work ... But I have to admit that I didn't try
the catastrophic recovery yet, only simple mess-ups.
Regards,
Phil
--
Versioning your /etc, /home or even your whole installation?
Try fsvs (fsvs.tigris.org)!
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
