Login | Register
My pages Projects Community openCollabNet

Discussions > users > How to use fsvs?

fsvs
Discussion topic

Hide all messages in topic

All messages in topic

Re: How to use fsvs?

Author pmarek
Full name P.Marek
Date 2006-07-09 06:18:33 PDT
Message Sorry for not answering for such a long time -- I was (and still am) a bit out
of order.

In case that this is still not working I'll dump my 0.02 euro into the mix:
--- Start ---

#!/bin/bash

set -x

# Set some paths
fsvs=`pwd`/../fsvs-1​.0.7/src/fsvs
repospath=`pwd`/repos
reposurl=file://$repospath
spool=/var/spool/fsvs
targetdir=./dir
ignore=skipme

# Clean up from last run
rm -rf $repospath
rm -rf $spool
rm -rf $targetdir

# Create the dirs
mkdir $targetdir
touch $targetdir/file
mkdir $targetdir/$ignore
touch $targetdir/$ignore/file

# Now I want to version $dir, but how?

svnadmin create $repospath
mkdir $spool
# goto the target path - most other operations use the current directory
# to differentiate between multiple "checkouts"
cd $targetdir
# set the repository to use
$fsvs init $reposurl

# I don't get any difference from including this section or not. why?
$fsvs ignore ./$ignore

# initial status
echo "Initial status:"
$fsvs st

# first commit
echo "Initial commit."
$fsvs ci -m 'Commit-Test'

# status after commit
echo "Status after commit:"
$fsvs st
--- End ---

Please try this and tell me any problems.


Regards,

Phil

Re: How to use fsvs?

Author Gunter Ohrner <G dot Ohrner at post dot rwth-aachen dot de>
Full name Gunter Ohrner <G dot Ohrner at post dot rwth-aachen dot de>
Date 2006-06-28 14:05:38 PDT
Message Am Mittwoch, 28. Juni 2006 18:51 schrieb Peter Valdemar Morch:
> > That's wrong: $spool is managed by fsvs ONLY, it's used for internal
> Oh, but if I comment out "svn co $repos $spool" I get
>
> An error occurred: No such file or directory (2)
> in waa__init: stat() of waa-path '/var/spool/fsvs' failed. Does your
> local storage area exist?
> Version trunk:329
>
> As I wrote, I also did try mkdir /var/spool/fsvs
> it still didn't work.

This co is still wrong, mkdir-ing the directory is the way to go. What's
the error message if you replace the svn co by mkdir?

> > You probably mean "svn co $repos /dir", I guess?
> NO!!! Remember, that I eventually want to keep track of /etc. I don't
> want any .svn directories in /etc!!! I sure hope that is possible?
> And I DEFINITELY don't want to create an emtpy /etc (for obvious
> reasons)

Sorry, I obviously was inattentive while reading your original mail. There
is no point of chaching out or exporting anything from your repository in
any case as you just created it - it just cannot contain any data.

There's no need to invoke svn at all.

> > That's wrong, you must "fsvs init $spool", not $repos.

That's nonsense, of course, the "fsvs init $repos" you used is correct.

> fsvs init /var/spool/fsvs
> Are you sure about that?

No, that's just plain wrong. I don't know what I was thinking about when I
suggested that.

However, a mistake you did was calling "fsvs init" in a directory other
that the directory which should be managed. You need to cd to / to
manage /dir and /skipme.

See the attached script, a modified version of yours. As I'm not testing
things as root and thus can't reate directories in system directories
as "/", I made all tests relative to the current directory.

> What I'm looking for is a complete example of how to keep track of /etc.

See the attached file.

Greetings,

  Gunter

--
+-+-+-+-+-+-+-+-+-+-​+-+-+-+-+-+-+-+-+-+-​+-+-+-+-+-+-+-+-+-+-​+-+-+-+-+-+-+
Thunder rolled. ... It rolled a six. -- (Terry Pratchett, Guards!
Guards!)
+-+-+-+-+-+-+-+-+-+-​+-+-+-+-+-+-+-+-+-+-​+-+-+-+-+-+-+-+-+-+-​+-+-+-+-+-+-+
+ PGP-verschlüsselte Mails bevorzugt! +
+-+-+-+-+-+-+-+-+-+-​+-+-+-+-+-+-+-+-+-+-​+-+-+-+-+-+-+-+-+-+-​+-+-+-+-+-+-+
Attachments

Re: How to use fsvs?

Author Peter Valdemar Morch <swp5jhu02 at sneakemail dot com>
Full name Peter Valdemar Morch <swp5jhu02 at sneakemail dot com>
Date 2006-06-28 09:51:50 PDT
Message Hi there,

Thanks for your quick answer, but uhm...

Gunter Ohrner G.Ohrner-at-post.rwth-aachen.de |Lists| wrote:
> That's wrong: $spool is managed by fsvs ONLY, it's used for internal data.

Oh, but if I comment out "svn co $repos $spool" I get

An error occurred: No such file or directory (2)
   in waa__init: stat() of waa-path '/var/spool/fsvs' failed. Does your
local storage area exist?
Version trunk:329

As I wrote, I also did try mkdir /var/spool/fsvs
it still didn't work.

> You probably mean "svn co $repos /dir", I guess?
NO!!! Remember, that I eventually want to keep track of /etc. I don't
want any .svn directories in /etc!!! I sure hope that is possible?
And I DEFINITELY don't want to create an emtpy /etc (for obvious reasons)

> That's wrong, you must "fsvs init $spool", not $repos.

But, uhm, USAGE says:
> fsvs init REPOS_URL
> Examples:
> fsvs init http://svn/repos/ins​tallation/machine-1/​trunk

And you suggest "fsvs init $spool" (where $spool="/var/spool/fsvs")
which leads to:
fsvs init /var/spool/fsvs
Are you sure about that? It leads to "An error occurred: Bad URL passed
to RA layer (170000)" later.

So, now, I'm sorry, but I'm still exactly as stuck...

What I'm looking for is a complete example of how to keep track of /etc.

Peter

--
Peter Valdemar Mørch
http://www..........

Re: How to use fsvs?

Author Gunter Ohrner <G dot Ohrner at post dot rwth-aachen dot de>
Full name Gunter Ohrner <G dot Ohrner at post dot rwth-aachen dot de>
Date 2006-06-28 09:25:54 PDT
Message Am Mittwoch, 28. Juni 2006 15:25 schrieb Peter Valdemar Mørch:
> fsvs=`pwd`/src/fsvs
> repospath=`pwd`/repos
> repos=file://$repospath
> spool=/var/spool/fsvs

That's korrect:
> svnadmin create $repospath

That's wrong: $spool is managed by fsvs ONLY, it's used for internal data.
You probably mean "svn co $repos /dir", I guess?
> svn co $repos $spool

That's wrong, you must "fsvs init $spool", not $repos.
> $fsvs init $repos

Greetings,

  Gunter

--
+-+-+-+-+-+-+-+-+-+-​+-+-+-+-+-+-+-+-+-+-​+-+-+-+-+-+-+-+-+-+-​+-+-+-+-+-+-+
Bei hoher Fehlerrate muss die Fehlerkorrektur des CD-Players öfter
interpolieren - und das kann man hören. -- Lass mich raten... Da geht
dann Raeumlichkeit, Abstandstiefe, Klangwaerme und Natuerlichkeit
verloren und die Neutralitaet leidet erheblich. Tipp: Das liegt daran,
dass Du keine sauerstofffreien Lautsprecherkabel verwendest. --
Jens de Vries und Markus Dobel in
<news:20040709162​518 dot A29723 at balu dot kawo​2.rwth-aachen.de>​
+-+-+-+-+-+-+-+-+-+-​+-+-+-+-+-+-+-+-+-+-​+-+-+-+-+-+-+-+-+-+-​+-+-+-+-+-+-+
+ PGP-verschlüsselte Mails bevorzugt! +
+-+-+-+-+-+-+-+-+-+-​+-+-+-+-+-+-+-+-+-+-​+-+-+-+-+-+-+-+-+-+-​+-+-+-+-+-+-+
Attachments

How to use fsvs?

Author =?ISO-8859-1?Q?Peter_Valdemar_M=F8rch?= <swp5jhu02 at sneakemail dot com>
Full name =?ISO-8859-1?Q?Peter_Valdemar_M=F8rch?= <swp5jhu02 at sneakemail dot com>
Date 2006-06-28 06:25:00 PDT
Message Hi,

I'm trying to get started with this, but I haven't succeeded in getting
even basic operations working.

I eventuall want to keep track of /etc in a repository, but am testing
with /dir. Here is the test script I've been using. I get nothing but
errors and segmentation faults... What am I doing wrong?

How do I keep track of /dir and not /skipme?

Peter
(I'm using trunk -r 355 which is identical to the 1.0.11 tag)

#!/bin/bash

set -x

# Set some paths
fsvs=`pwd`/src/fsvs
repospath=`pwd`/repos
repos=file://$repospath
spool=/var/spool/fsvs

# Clean up from last run
rm -rf $repospath
rm -rf $spool
rm -rf /dir
rm -rf /skipme

# Create the dirs
mkdir /dir
touch /dir/file
mkdir /skipme
touch /skipme/file

# Now I want to version $dir, but how?

svnadmin create $repospath
# Or should this be "mkdir $spool"? Haven't a clue...
# I tried both and both don't work.
svn co $repos $spool
$fsvs init $repos

# I don't get any difference from including this section or not. why?
$fsvs ignore t./dir
$fsvs ignore ./*

$fsvs status /dir
# This outputs:
# N... 0 ./file

$fsvs status /skipme
# This outputs:
# N... 0 ./file
# But why? I thought I skipped that!

$fsvs commit -m "Checking in /dir for the first time" /dir
# Prints out:
# An error occurred: No such file or directory (2)
# in waa__load_repos_urls
# Version trunk:329
# But why? Which dir doesn't exist?

$fsvs add /dir
# creates a segmentation fault

$fsvs sync-repos
# Synchronized to revision 0.

$fsvs add /dir
# Now it prints out:
# n..! 0 .//dir
# But what is up with the double "//'?

$fsvs commit -m "Checking in /dir for the first time" /dir
# An error occurred: No such file or directory (2)
# in waa__load_repos_urls
# Version trunk:329

# Hmm...
cd /
$fsvs add dir
# creates a segmentation fault
$fsvs commit -m "Checking in /dir for the first time" dir
# An error occurred: No such file or directory (2)
# in waa__load_repos_urls
# Version trunk:329

--
Peter Valdemar Mørch
http://www.morch.com
Messages per page: