Philipp Marek wrote:
Hello Thomas!

On Tuesday 05 August 2008 Thomas Harold wrote:
Originally, we ignored /var/vmail (the entirety).

./var/vmail/

Then I added (to the end):
And that's the problem - the ignore patterns are used *in order*, and the first match terminates the search.
So you'll have to move them to the front:
        fsvs ignore dump > file
        vi file
        fsvs ignore load < file

Thank you.  Mmm... I now have the ordering of:

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

Which seems like FSVS should ignore everything under /var/vmail/ except for the sievescripts directory and any files below that point that are named ".dovecot.sieve".

But fsvs status doesn't show updates when I sit in the root folder (root of my working copy, where I always do my commands from):

# fsvs status /
n...       dir  .
# fsvs status /var/
# fsvs status /var/vmail/
N...       dir  ./var/vmail/sievescripts
n...       dir  ./var/vmail
#

So a fsvs ci -m "comment" from the root won't do anything unless I:

# fsvs ci -m "snapshot" /var/vmail/
Committing to file:///var/svn/sys-fw1-pri-cfg
n...       dir  ./var/vmail
N...       dir  ./var/vmail/sievescripts
committed revision      367 on 2008-08-06T23:48:53.176164Z as root
#

But it's still not grabbing the files inside of the sievescripts folder. Or looking for .dovecot.sieve files under the /var/vmail tree. The ".dovecot.sieve" folders are located two levels below /var/vmail:

/var/vmail/domain/username/.dovecot.sieve

Maybe I'm not understanding the USAGE file where you have patterns with spaces in them like: './ ** / *.bak'.

Also tried:

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

If I create a test file in /var/, it immediately picks it up:

 fsvs status
n...       dir  .
N...         5  ./var/test
.mC.       dir  ./var
#

Creating a test file in /var/vmail/ results in:

# fsvs status
n...       dir  .
.m..       dir  ./var/vmail
.m..       dir  ./var
#

Which is as expected. Moving the test file under /var/vmail/sievescripts then causes fsvs to see that there are actually things under /var/vmail/sievescripts that need to be versioned and results in a lot of new "N..." lines. It's like fsvs got itself "unstuck" and suddenly found the files as I changed things in /var/vmail/ itself.

Still can't get it to look in folders below /var/vmail/ or find those .dovecot.sieve files:

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

And a "find /var/vmail -name .dovecot.sieve" pulls up 8 files under /var/vmail.

I've also tried: "fsvs status -C -C" which took a while to run, but still didn't pickup on the ".dovecot.sieve" files in the individual mail folders. And running it solely on the /var/vmail/ tree results in:

# fsvs status -C -C -v /var/vmail/
.....       dir  ./var/vmail
.....      5276  ./var/vmail/sievescripts/survey-sortingrulesc
.....        48  ./var/vmail/sievescripts/survey-BASEc
.....        58  ./var/vmail/sievescripts/survey-BASE
.....       179  ./var/vmail/sievescripts/Makefile
.....      3501  ./var/vmail/sievescripts/survey-sortingrules.old
.....       dir  ./var/vmail/sievescripts
.....      4842  ./var/vmail/sievescripts/survey-sortingrules
#

Hmm, I just looked at the version - it's only 1.1.6 (been misreading that as 1.1.16).

No luck, even with fsvs-1.1.16:1690, it's still not seeing the dovecot sieve files inside of individual user folders.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to