Hello Plamen!
> Looks like the problems gone. Take a look (sorry, it is long):
Good for you. Yes, I'll have to take a look at that ... but that'll take some
time.
> # fsvs commit -m 'autoupdate: virtualbox (from virtualbox web repository)'
> Committing to file://localhost/media/backup/backup/fsvs/trunk/base
> d... dir sys
> .m.. dir proc
>
> An error occurred: Transaction is out of date (160028)
> in ci___set_props: function: Out of date: '/trunk/base/proc' in
> transaction '218-1'
That means that the repository has a newer version of this entry (/proc) than
FSVS
reports as being locally.
Do you work on this repository from another WC too?
Next time you could try "fsvs update".
> # fsvs sync-repos | tail -n 200
>
> An error occurred: Invalid argument (22)
> in ops__string_to_dev: 'ELF' is not parseable as a special description
That's the same problem as before, in the other thread.
> # ls -l /etc/fsvs
> drwxr-xr-x 2 root root 4096 2009-05-28 20:48
> 6666cd76f96956469e7be39d750cc7d9
> drwxr-xr-x 2 root root 4096 2009-06-01 18:41
> d73ade42b8f359af27c04e3a32c3f10f
>
> # ls -l /var/spool/fsvs/
> drwxr-xr-x 258 root root 4096 2009-06-01 21:28 6666
> drwxr-xr-x 3 root root 4096 2009-06-01 18:41 d73a
>
> ### Why 2 dirs but one URL. Few days back it was one directory
> 6666cd76f96956469e7be39d750cc7d9 and '6666'
Because you had a second working copy ... look at the symlinks
/etc/fsvs/*/_base to see
the base paths.
> I decide to try to NOT ignore /dev/pts. It created problems in past,
> wanted to check how it is now. I know, you said - ignore /dev
> completely, but I want this history, plus I want to see permission changes.
>
> Anyway, as I see it, some file create problem (/dev/pts), but the next
> file is affected (/dev/ptmx). After 'delete, commit, commit' /dev/ptmx
> (commit again because it is not ignored - first is deleted, then it is
> added as new), then the problem gone.
Good luck!
> The problem in my previous email, could be (maybe) because when I run
> 'fsvs commit' I decided to check something. So I interrupt it with ctrl+C.
>
> For the record, I often have similar problems. But if I use fsvs
> carefully, it works fine. If I use ctrl+C or if the process (commit) is
> interrupted because of error, then I do not know what to expect next.
> For me, this is a weak area.
Hmmm, normally subversion should do atomic commits - and if you don't interrupt
FSVS
right in the split-second part where the commit has happened but the local WC
data has
not, it shouldn't be a problem.
Do you use that repository from another working copy, too?
Regards,
Phil
--
Versioning your /etc, /home or even your whole installation?
Try fsvs (fsvs.tigris.org)!
------------------------------------------------------
http://fsvs.tigris.org/ds/viewMessage.do?dsForumId=3928&dsMessageId=2358668
To unsubscribe from this discussion, e-mail:
[[email protected]].
