<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.comp.sysutils.backup.fsvs.general">
    <title>gmane.comp.sysutils.backup.fsvs.general</title>
    <link>http://blog.gmane.org/gmane.comp.sysutils.backup.fsvs.general</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/540"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/527"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/502"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/490"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/476"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/462"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/459"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/451"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/450"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/437"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/428"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/423"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/420"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/417"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/414"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/406"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/405"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/401"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/398"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/397"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/540">
    <title>fsvs use case</title>
    <link>http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/540</link>
    <description>Ladies and Gentlemen,
We have a unique challenge that we're trying to address using fsvs.  We have
a lot of servers out "in the wild" as it were, and instead of using some
sort of package management system to upgrade the OS and our own software, we
want to use fsvs.

The idea is that we can make updates on our own master server, check them
into fsvs/subversion, and then have each of the "in the wild" servers update
from fsvs/subversion.  This seems like a great idea, but we've had a bit of
difficulty when trying to actually get these updates to work.

In our testing environment, we'll make some changes and then commit them
fine, but when we try to do an update, we will often (but not always) get
something like the following:

dev-01 / # fsvs update -r 19
Updating svn+ssh://user&lt; at &gt;svnserver//home/user/svn/osrepo to revision
19.
The entry ./etc/fsvs has changed locally

We've tried with and without the "-r &lt;revision&gt;", and we don't always get
the same file as having changed (though it is usually one of a handful</description>
    <dc:creator>Stuart Lester</dc:creator>
    <dc:date>2008-08-26T17:32:01</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/527">
    <title>full backup with fsvs - trying to revert a revision (and other problems)</title>
    <link>http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/527</link>
    <description>Hi all.


Recently I upgraded VirtualBox from version 1.5.6 to 1.6.4. Then I decide to revert. I decide to use fsvs and I failed.


Here my ignore list:
./media/*/**
./mnt/*/**
./proc/**
./sys/**
Everything else is included: /dev, /var/run, /var/lock


Here my commits log:
------------------------------------------------------------------------
r87 | root | 2008-08-14T08:19:51.031668Z | 1 line
  backup 2008-08-14 aptitude clean
------------------------------------------------------------------------
r86 | root | 2008-08-14T08:18:08.803716Z | 1 line
  backup 2008-08-14 aptitude autoclean
------------------------------------------------------------------------
r85 | root | 2008-08-14T08:13:44.560284Z | 1 line
  update 2008-08-14 VirtualBox (1.6.4)
------------------------------------------------------------------------
r84 | root | 2008-08-11T08:47:45.485636Z | 1 line
  backup 2008-08-11 Thunderbird (email accounts)
------------------------------------------------------------------------


I want to revert rev</description>
    <dc:creator>MMM MMM</dc:creator>
    <dc:date>2008-08-18T12:30:58</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/502">
    <title>fsvs doesn't detect changes</title>
    <link>http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/502</link>
    <description>Hi Philipp and others,

(To refresh your memory) I'm using fsvs to keep files in my homedir under
version management using this:
  export FSVS_SOFTROOT=${HOME}
  export FSVS_CONF=${FSVS_SOFTROOT}/.fsvs
  export FSVS_WAA=${FSVS_CONF}/waa

I have two machines that do this.

Tonight I noticed that the changes to the ignore list are not being
committed. Here's a sample session.
(status is an alias for fsvs -C -f text,owner,group,mode
 commit is an alias for fsvs ci -o empty_commit=no -C -f text,owner,group,mode)

griffon26&lt; at &gt;griffon27 ~&gt; status
.mC.       975  .fluxbox/keys
.mC.      6857  .fluxbox/init
N...        48  .ssh/config
.mC.       dir  .ssh
N...      1180  bin/mailwatch.sh
.mC.       dir  bin
.mC.      1328  .xsession
.mC.      1129  .fsvs/6666cd76f96956469e7be39d750cc7d9/Ign
N...        48  .cvsrc
N...       dir  public_html_shared
.mC.       dir  .
griffon26&lt; at &gt;griffon27 ~&gt; commit
Committing to svn+ssh://localhost/home/griffon26/repos/fsvsrepo/home-base
.mC.       dir  .ssh
N...        48  .ssh/config
.m</description>
    <dc:creator>Maurice van der Pot</dc:creator>
    <dc:date>2008-08-08T21:36:49</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/490">
    <title>Quick ignore / take question (fsvs-1.1.6:900)</title>
    <link>http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/490</link>
    <description>Originally, we ignored /var/vmail (the entirety).

./var/vmail/

Then I added (to the end):

t./var/vmail/sievescripts
t./var/vmail/**/.dovecot.sieve

So now I want to put the /var/vmail/sievescripts folder under version 
control, as well as any ".dovecot.sieve" files below that point.  But 
not anything else.

But an "fsvs status" from the root folder doesn't show those "taken" 
patterns, nor does a "fsvs ci -m 'message'" grab those files.

Not sure what else I needed to do.
</description>
    <dc:creator>Thomas Harold</dc:creator>
    <dc:date>2008-08-05T16:01:03</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/476">
    <title>questions about "unversion" and "ignore"</title>
    <link>http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/476</link>
    <description>Hi all,


I am new to both fsvs and svn. Please, excuse me if my questions are irrelevant or if question are related to svn.



1. About svn repository

case 1: I commit file XYZ; then I unversion and ignore file XYZ.
-&gt; How to completely remove file XYZ from svn repository and save disk space?

case 2: I do daily commits; once in a month I remove all garbage (empty trash, uninstall temp/test software).
-&gt; How to shrink svn repository and remove all daily commits?

Does fsvs handle these cases? (or maybe svndumpfilter is the answer?)

If I am able to shrink my svn repository, then I will not worry about ignore filters.


2. I would like to see examples about ignore filters (I did not check everything in mail archive yet, but found "howto backup" tutorial and "FSVS for sysadmins"). I am linux beginner and can't decide easily. Could I ask for advice:


Are these good ignore filters:
./root/.mozilla/firefox/*/Cache/**
./home/*/.mozilla/firefox/*/Cache/**
./root/.nautilus/metafiles/file**
./home/*/.nautilus/meta</description>
    <dc:creator>MMM MMM</dc:creator>
    <dc:date>2008-07-23T11:01:16</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/462">
    <title>fsvs urls or fsvs initialize results in No such file or directory (2) error</title>
    <link>http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/462</link>
    <description>So I was setting up FSVS 1.1.16 on a new CentOS 5.1 box this week (one 
of the first things that I do as soon as possible before configuration 
starts).  And I encountered the following error:

# fsvs -v urls svn+ssh://svn.example.com/sys-machinename

An error occurred at 14:40:31.865: No such file or directory (2)
   in url__output_list
   in url__work
   in main: action urls failed

...

The fix is to create the "/etc/fsvs" folder

fsvs 1.1.16 was smart enough to remind me to create /var/spool/fsvs, but 
it apparently doesn't give a good error message when the "/etc/fsvs" 
folder does not exist.

Apologies if this is an older error, but I figured I'd write it up for 
the mailing list.  (Also posted on my blog so that Google finds it.)
</description>
    <dc:creator>Thomas Harold</dc:creator>
    <dc:date>2008-07-14T18:51:36</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/459">
    <title>backup replication with fsvs</title>
    <link>http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/459</link>
    <description>hi Team,

I have a question about FSVS, I'd like to know if it is possible to create a
configuration that will let me do a simultaneous backup replication.  Please
help me with some configuration example/examples to get this done.

Thanks a lot for your help.

Carlos Ochoa
</description>
    <dc:creator>Carlos Ochoa</dc:creator>
    <dc:date>2008-07-14T15:15:17</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/451">
    <title>[feature request] ssl client-certificate auth</title>
    <link>http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/451</link>
    <description>I have seen that this feature already exists in the svn client and can 
be controlled via
the following directives in subversion configuration:


The access to the repository should be authenticated in a host-based way.
This would also offer the oppurtinity to evaluate key attributes on 
server side for url rewrite and verify the the origin of the http-request.
We need a password option for avoiding the password request when 
http-auth. I am not sure for now if the svn-client does seperate 
password requests (ssl/http-auth).
For our scenario if the password is stored http-auth should use this 
password. We need http-auth to get the username of the committer.

Userbased authorisation makes no sense in our environment as every 
fsvs-user is also admin and therefore could fake the username / spy 
passwords.
Using ssh for host-based authentication does not offer the flexibility 
of apache2 which we need in this scenario.

Best Regards,
Gunnar Thielebein
</description>
    <dc:creator>Gunnar Thielebein</dc:creator>
    <dc:date>2008-07-07T14:13:20</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/450">
    <title>Questions about ignoring files</title>
    <link>http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/450</link>
    <description/>
    <dc:creator>Maurice van der Pot</dc:creator>
    <dc:date>2008-07-06T22:27:51</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/437">
    <title>FSVS and versioning /etc - a security risk?</title>
    <link>http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/437</link>
    <description>Hello everybody,

I'd like to share a question, and hope to find a simple answer:
How can FSVS avoid showing passwords to unauthorized people?


Me, *personally*, I think -
1) Passwords should be hashed, or similarly unreadable.
   But that's not always possible (eg. when needed for IMAP verification)
2) If /etc is protected, the repository storing /etc must be, too.
   But sometimes that's forgotten, or the history should be viewable by others, too.
3) There's the commit-pipe hook, which can be used to filter out any secret data.
   But that's easily to forget, or to get wrong.


Any ideas? I already thought a bit about that, and could offer making FSVS run as an
ordinary user (or something like that [1]), so that protected files wouldn't get
versioned at all - but that's not ideal, too (as you loose information).


Any ideas? Examples? How do other products solve that?


Regards,

Phil


[1]
The simplest way could be to use a pre-commit-pipe like
   sudo -u nobody cat '$1' 2&gt;/dev/null || true
so that prote</description>
    <dc:creator>Philipp Marek</dc:creator>
    <dc:date>2008-06-16T12:40:58</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/428">
    <title>exitcode of fsvs diff</title>
    <link>http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/428</link>
    <description>Hi Philipp,

I have an issue when trying to use fsvs in a simple shell script which 
should check the diff of an local directory and its head-revision and 
mail the output of diff to admin via a cron-job.

In the  man-pages and this thread 
(http://thread.gmane.org/gmane.comp.sysutils.backup.fsvs.general/211/focus=217) 
I have seen that you for some reason doesnt forward the exitcode of diff 
but that I can use the -W flag to override that behaviour.

When I use this command (and there are modifications in fileset):

if sudo fsvs -Wdiff-status=stop diff /;then echo $?;fi

I still get exitcode 0. Is there some error in usage?
Do you mind of some other way checking for changes?

Regards,
Gunnar
</description>
    <dc:creator>Gunnar Thielebein</dc:creator>
    <dc:date>2008-06-10T15:39:06</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/423">
    <title>issue with username in http(s)-svn commit</title>
    <link>http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/423</link>
    <description>Hi Marek,

We are beginning to rollout fsvs on some of our office debian and ubutu 
servers for getting an audit about configuration changes mostly done by 
our admins.
Currently we are using the packages of debian sid 1.1.14-1. I did a 
backport of the package for an old ubuntu distribution (edgy) because we 
need it for zimbra.

I have an issue when using sudo with fsvs in environments where we don't 
have the svn-client installed. We do a userbased auth before committing 
via an http-url.

The error message is this:

Where it does ask for a password I only hit return.

When we installed svn and did "svn ls" with the same url it asked for 
username and saved the credentials.

I would also like to propose to set a -u or -l parameter for specifying 
the user when committing via fsvs. This would ease the user handling in 
environments where you have different admins working with only one 
(root) account.

Best Regards,
Gunnar
</description>
    <dc:creator>Gunnar Thielebein</dc:creator>
    <dc:date>2008-06-06T15:52:19</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/420">
    <title>Exclude/include patterns guidance</title>
    <link>http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/420</link>
    <description>Hello,

I am interested in backing up /etc/*, /var/cache/* and /var/lib/* to a single 
repository. In this case it is obvious I need to attach my fsvs root to /. 
What is the correct way to achieve this, short from a very long and messy 
ignore list? Or is such usage discouraged altogether?

Thanks

Peter
</description>
    <dc:creator>Peter Rabbitson</dc:creator>
    <dc:date>2008-05-27T13:51:23</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/417">
    <title>fsvs-1.1.15 - install errors</title>
    <link>http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/417</link>
    <description>1) If I haven't created the /etc/fsvs folder, the following command fails

# fsvs -v url file:///var/svn/sys-san-bkp1-cfg

An error occurred at 12:47:30.669: No such file or directory (2)
   in url__output_list
   in url__work
   in main: action urls failed

1b) I didn't test to see what happened when I forget to create 
/var/spool/fsvs (according to the README).  I had already created the 
folder based on the instructions in the README.

2) The README file says to "cd src" prior to running make.  This is 
incorrect, because the makefile has been moved to the root of the fsvs 
extracted folder.  The correct series of steps (at the moment is):

(go to the extracted folder contents)
./configure
make
cp src/fsvs /usr/local/bin/
</description>
    <dc:creator>Thomas Harold</dc:creator>
    <dc:date>2008-05-16T16:53:01</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/414">
    <title>fsvs revert: problems with meta-data and symlinks</title>
    <link>http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/414</link>
    <description>When creating an object that did not exist locally before, `fsvs
revert` does not seem to recreate symlinks and to restore file
meta-data from the repository.

The following steps should be reproduceable with both a vanilla fsvs
1.1.15 and fsvs 1.1.14-1 taken from the Debian repository. First I
created a "source directory" and committed its contents:

| $ mkdir svn test1 test2
| $ svnadmin create svn/
| $ cd test1/
| $ fsvs urls file:///home/paul/fsvs/svn
| $ echo x &gt;blech
| $ ln -s foo bar
| $ ls -l
| total 4
| lrwxrwxrwx 1 paul users 3 May  8 20:53 bar -&gt; foo
| -rw-r--r-- 1 paul users 2 May  8 20:53 blech
| $ fsvs commit -m ""
| Committing to file:///home/paul/fsvs/svn
| N...         2  blech
| N...         3  bar
| committed revision      1 on 2008-05-08T18:54:01.515226Z as paul
| $

Then I tried to clone the two objects ("bar" and "blech") using fsvs:

| $ cd ../test2/
| $ fsvs urls file:///home/paul/fsvs/svn
| $ fsvs sync-repos
| N...         0  bar
| N...         0  blech
| ..C.       dir  .
| sync-rep</description>
    <dc:creator>Paul Hink</dc:creator>
    <dc:date>2008-05-08T19:14:56</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/406">
    <title>Multiple URLs with FSVS</title>
    <link>http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/406</link>
    <description>Hi,

I am really excited to dive into FSVS, yet there is a concept that I don't 
get. What is the use case of multiple URLs? I can not find anything in the 
documentation, and google doesn't seem to help either. From my knowledge of 
subversion (relatively substantial) I see a number of problems:

* Since each URL is a repository on its own right, they can get out of sync if 
someone commits something using classic svn. What happens then?

* When an URL is not available will a scheduled commit go through? Will it 
abort until the entire URL collection is accessible?

Any pointers to documentation and/or explanations are more than welcome.

Peter
</description>
    <dc:creator>Peter Rabbitson</dc:creator>
    <dc:date>2008-04-18T06:10:39</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/405">
    <title>[ALERT] Bug in example setup - passwords not removed from      /etc/shadow</title>
    <link>http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/405</link>
    <description>Hello everybody,

since 1.1.13 the FSVS sources included an "example" directory, with some
scripts in int.

I just found out that I forgot to put the correct script in my subversion
source directories; the example script for removing passwords in
/etc/shadow and /etc/gshadow was wrong, and didn't remove them.

Please see here for a quick download of a fixed version:
http://fsvs.tigris.org/source/browse/fsvs/trunk/fsvs/example/var/lib/fsvs-versioning/scripts/shadow-clean.pl?rev=1612&amp;view=log


Please take all necessary steps:
- Install the fixed script;
and either
- change all passwords on your system or, if that's not possible,
- use svndumpfilter to remove old versions of your shadow
  and gshadow files, or,
- if you can restart versioning /etc, remove the repository, re-create it,
  and use "fsvs sync" to tell FSVS that there's nothing stored.


I've put an message on freshmeat, too.


I apologize for the inconvinience.


Regards,

Phil


</description>
    <dc:creator>Philipp Marek</dc:creator>
    <dc:date>2008-04-18T05:27:41</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/401">
    <title>fsvs configuration bug</title>
    <link>http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/401</link>
    <description>Hi,

I am trying to configure fsvs to manage the configuration of several servers 
in our company.

We have choosen / as configuration path. We are using exactly one url and 
exactly one ignore list.

The ignore list shows this way:

t./boot
t./boot/grub
t./boot/grub/menu.lst
./etc/fsvs
./etc/*passwd*
./etc/*shadow*
./etc/ssh/ssh_host_[dr]sa_key
./etc/ssl/private
t./etc/
t./var
t./var/lib
t./var/lib/dpkg
t./var/lib/dpkg/status
t./var/trac
t./var/trac/*
t./var/trac/*/conf
t./var/trac/*/conf/trac.ini
./**

the svn url is 

http://server/svn/ORGUNIT/DOMAIN/SUBDOMAIN/hostname

Where we are struggling now is when doing some configuration management. 
Lets say we are in /etc/apache2 and have done some changes in 
sites-enable/000-default and want to perform a commit.

fsvs commit -m "changed apache2 config"

fsvs tries to look for configuration of the path which is cwd passwd as 
parameter with fsvs commit and fails with 

"No URLs have been defined for /etc/apache2."

Another thing is if I use 

fsvs status /etc/</description>
    <dc:creator>gunnar_thielebein&lt; at &gt;gmx.net</dc:creator>
    <dc:date>2008-04-16T16:34:34</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/398">
    <title>FSVS bugreports</title>
    <link>http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/398</link>
    <description>Hi,

I am trying out fsvs and I'm beginning to get the feeling of it :)
There are several issues I had to face and I'd like to make some
bugreports. Can I hijack the issue tracker[1] and post my bugreports
there? I see Its not really used. Or should i just post them to this
mailing list?

Keep up the good work :)

Paul Tobias

[1]http://fsvs.tigris.org/servlets/ProjectIssues
</description>
    <dc:creator>Paul Tobias</dc:creator>
    <dc:date>2008-04-15T15:06:41</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/397">
    <title>[ANNOUNCE] FSVS 1.1.14 released</title>
    <link>http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/397</link>
    <description>Hello everybody,


FSVS 1.1.14 is released, with a few new features and some bugfixes.

There are some fixes I wanted to get into this version (diff output
and behaviour, revert to a revision) but didn't make it - I'd need a
few uninterrupted hours to think that through, and that just doesn't
work in the train.

So, to not cause endless delays, I'm releasing 1.1.14 now - and try
really hard to find the time.


New features:
* New option for conflict handling; allows "stop" (historical default),
  "local", "remote", "both" or "merge".
  Uses an external "merge" binary (but can be configured, like "diff").
* New "resolve" action, to mark conflicts as resolved.
* "update" can now be restricted to an arbitrary subset of URLs.
  Please note that that doesn't mean *partly* updating your working
  copy - it just means that if you use 50 URLs you can update a
  single one.


Other small changes:
- Filter option "text" now means removed entries, too.
- "urls dump" can now work verbose to produce more human-readable
 </description>
    <dc:creator>Philipp Marek</dc:creator>
    <dc:date>2008-04-02T12:21:58</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/394">
    <title>Hide "diff -u" output</title>
    <link>http://comments.gmane.org/gmane.comp.sysutils.backup.fsvs.general/394</link>
    <description>And once more: Hello!

As I said, I'm playing with "fsvs diff"... 

This time, I've got a request. I ran:

--($:/Gentoo/Home)-- LC_ALL=C sudo fsvs  diff -r 141 -R .
diff -u ./opt/.keep.r141 ./opt/.keep.local
diff -u ./fsvs-ignore.ohne-binaries.txt.r141 ./fsvs-ignore.ohne-binaries.txt.local
diff -u ./CHROOT.SH.r141 ./CHROOT.SH.local
diff -u ./opt/bin/rar.r141 ./opt/bin/rar.local
diff -u ./opt/bin/unrar.r141 ./opt/bin/unrar.local
diff -u ./README.txt.r141 ./README.txt.local
diff -u ./fsvs-ignore.mit-binaries.txt.r141 ./fsvs-ignore.mit-binaries.txt.local
diff -u ./root/.keep.r141 ./root/.keep.local
diff -u ./root/.lesshst.r141 ./root/.lesshst.local
diff -u ./root/dead.letter.r141 ./root/dead.letter.local
[...]

Because of all the "diff -u ..." lines, the actual changes are not
really visible.

It would be great, if those "diff -u"'s could be hidden.

Cheers,

Michael
</description>
    <dc:creator>Michael Schmarck</dc:creator>
    <dc:date>2008-03-19T10:45:27</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.comp.sysutils.backup.fsvs.general">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.sysutils.backup.fsvs.general</link>
  </textinput>
</rdf:RDF>
