Login | Register
My pages Projects Community openCollabNet

Discussions > users > Re: [ANNOUNCE] FSVS 1.2.1 released

fsvs
Discussion topic

Hide all messages in topic

All messages in topic

Re: [ANNOUNCE] FSVS 1.2.1 released

Author pmarek
Full name P.Marek
Date 2009-11-04 06:19:04 PST
Message Hello Gunnar!

> So ignoring mtime globally is my only option, at least I know its possible. Do
> you think this can become a match pattern so that it can be used together with
> "dironly" in a global scope affecting all dirs?
No, you're misunderstanding me.

"dironly" and match patterns are used only for new files, that are not yet known in the
repository.

The filter specifies what to look for in *known* files.

>> Maybe ...
>> The symlinks are there just for informational purposes, and so they might stay.
>> If there's only a sqlite database, it's not that easy to see which working copy this
>> is.
>> Maybe I should put a "README" or something like that in there? But that's not so
>> easily
>> used by scripts ...
>
> Just asking because we had problems with the _base symlink when debian packages
> take use of the "find" command. This still happens with "base-files" causing an
> endless loop.
You can just remove them ... FSVS doesn't use them.

>>> I get a segfault with "fsvs unversion", bugreport is on its way...
>> Fine ;-/, please tell me.
>
> This happens when using the "fsvs add" and performing unversion. I have to
> figure out the exact scenario.
Thank you!


Regards,

Phil


--
Versioning your /etc, /home or even your whole installation?
             Try fsvs (fsvs.tigris.org)!

Re: [ANNOUNCE] FSVS 1.2.1 released

Author tekknokra
Full name Gunnar Thielebein
Date 2009-11-04 01:47:33 PST
Message Hi Phil,

Philipp Marek wrote:
> Hello Gunnar!
>
>> thanks for this new release. I am just evaluating the upgrade path from 1.1.16
>> to 1.2.1. Some questions about the handling:
>>
>> On playing with the examples of grouping patterns i noticed a small typo:
>> http://doc.fsvs-soft​ware.org/doxygen-gif​/index.html
> Yes, thank you. I'll fix that.
>
>> Fix is to put a trailing comma after each modifier. Seems this gets default now.
> There's a conversion script for the ignore/grouping patterns; you don't have to do that
> by hand.
>
>
>> Regarding introduction of groups and modifiers. Is it now possible to explicitly
>> discard check of the mtime of directories? I use fsvs in a cron job for
>> monitoring and I get notifications when someone with owner privileges open files
>> within directories, because this causes an update of directories mtime timestamp.

> Well, the open itself shouldn't modify the mtime of the directory ... but the creation
> of a temporary file will.

Ah, so this happens when I use vim and a swapfile is created. I missed that fact.

>
> You could try using the filter option "text,owner,mode,gro​up,new,deleted" ... that's
> simply everything but mtime.
> You won't see files with *only* mtime changed, too - but that might be ok, as they
> should be given as soon as the data changes.

So ignoring mtime globally is my only option, at least I know its possible. Do
you think this can become a match pattern so that it can be used together with
"dironly" in a global scope affecting all dirs?

>
>
>> Regarding the last example:
>>
>>> m:04:0
>>> t,./etc/
>>> ./**
>> Do I get the same behaviour with this?:
>>
>>> t,m:004:004,./etc/
>>> ./**
>>From a quick look, yes. But I didn't test.
>
>
>> I like the idea to keep the old WAA file hierarchy for now and leave the new for
>> advanced users with the configure option.
>> Regarding the transition of files to sqlite do you plan to also integrate the
>> _base symlinks?
> Maybe ...
> The symlinks are there just for informational purposes, and so they might stay.
> If there's only a sqlite database, it's not that easy to see which working copy this is.
> Maybe I should put a "README" or something like that in there? But that's not so easily
> used by scripts ...

Just asking because we had problems with the _base symlink when debian packages
take use of the "find" command. This still happens with "base-files" causing an
endless loop.
>
>> I get a segfault with "fsvs unversion", bugreport is on its way...
> Fine ;-/, please tell me.

This happens when using the "fsvs add" and performing unversion. I have to
figure out the exact scenario.

>
>> I will then continue now with checking the functionality against ssl secured
>> repository...
> I'll be happy to hear any results!
>
>
> Regards,
>
> Phil
>
>

Rgds,
Gunnar
Attachments

Re: [ANNOUNCE] FSVS 1.2.1 released

Author pmarek
Full name P.Marek
Date 2009-10-30 00:39:59 PDT
Message Hello Gunnar!

> thanks for this new release. I am just evaluating the upgrade path from 1.1.16
> to 1.2.1. Some questions about the handling:
>
> On playing with the examples of grouping patterns i noticed a small typo:
> http://doc.fsvs-soft​ware.org/doxygen-gif​/index.html
Yes, thank you. I'll fix that.

> Fix is to put a trailing comma after each modifier. Seems this gets default now.
There's a conversion script for the ignore/grouping patterns; you don't have to do that
by hand.


> Regarding introduction of groups and modifiers. Is it now possible to explicitly
> discard check of the mtime of directories? I use fsvs in a cron job for
> monitoring and I get notifications when someone with owner privileges open files
> within directories, because this causes an update of directories mtime timestamp.
Well, the open itself shouldn't modify the mtime of the directory ... but the creation
of a temporary file will.

You could try using the filter option "text,owner,mode,gro​up,new,deleted" ... that's
simply everything but mtime.
You won't see files with *only* mtime changed, too - but that might be ok, as they
should be given as soon as the data changes.


> Regarding the last example:
>
>> m:04:0
>> t,./etc/
>> ./**
>
> Do I get the same behaviour with this?:
>
>> t,m:004:004,./etc/
>> ./**
From a quick look, yes. But I didn't test.


> I like the idea to keep the old WAA file hierarchy for now and leave the new for
> advanced users with the configure option.
> Regarding the transition of files to sqlite do you plan to also integrate the
> _base symlinks?
Maybe ...
The symlinks are there just for informational purposes, and so they might stay.
If there's only a sqlite database, it's not that easy to see which working copy this is.
Maybe I should put a "README" or something like that in there? But that's not so easily
used by scripts ...

> I get a segfault with "fsvs unversion", bugreport is on its way...
Fine ;-/, please tell me.

> I will then continue now with checking the functionality against ssl secured
> repository...
I'll be happy to hear any results!


Regards,

Phil


--
Versioning your /etc, /home or even your whole installation?
             Try fsvs (fsvs.tigris.org)!

Re: [ANNOUNCE] FSVS 1.2.1 released

Author tekknokra
Full name Gunnar Thielebein
Date 2009-10-29 12:58:23 PDT
Message Hi Phil,

thanks for this new release. I am just evaluating the upgrade path from 1.1.16
to 1.2.1. Some questions about the handling:

On playing with the examples of grouping patterns i noticed a small typo:
http://doc.fsvs-soft​ware.org/doxygen-gif​/index.html

> t,d,./var/vmail/**
> t./var/vmail/**/.*.sieve
> ./var/vmail/**

puts an error message:

> Pattern "t./var/vmail/**/.*.sieve" ends prematurely

> td./var/vmail/*
> td./var/vmail/*/*
> t./var/vmail/*/*/.*.sieve
> ./var/vmail/**

put message:

> Expected a shell pattern, starting with "./" or "/"!

Fix is to put a trailing comma after each modifier. Seems this gets default now.

Regarding introduction of groups and modifiers. Is it now possible to explicitly
discard check of the mtime of directories? I use fsvs in a cron job for
monitoring and I get notifications when someone with owner privileges open files
within directories, because this causes an update of directories mtime timestamp.

Regarding the last example:

> m:04:0
> t,./etc/
> ./**

Do I get the same behaviour with this?:

> t,m:004:004,./etc/
> ./**

I like the idea to keep the old WAA file hierarchy for now and leave the new for
advanced users with the configure option.
Regarding the transition of files to sqlite do you plan to also integrate the
_base symlinks?

I get a segfault with "fsvs unversion", bugreport is on its way...
I will then continue now with checking the functionality against ssl secured
repository...

Best,
Gunnar

P.Marek wrote:
> Hello everybody,
>
> FSVS 1.2.1 is released.
>
> ...
> Regards,
>
> Phil
>

[ANNOUNCE] FSVS 1.2.1 released

Author pmarek
Full name P.Marek
Date 2009-10-12 22:51:40 PDT
Message Hello everybody,

FSVS 1.2.1 is released.


This is more or less a bugfix release; there are only two new features:
* FSVS now supports arbitrary "svn+" tunnels, like subversion does.
  (Thank you, Jake.)
* "fsvs log -v" for now filters the changed entries list, and shows the
  paths relative to the parameter.

Of course, these could be taken as features, too:
* Additional configure check for Solaris; it does compile (and work?)
  now. Thank you, Mark.
* Compatibility fixes for subversion 1.6.4.
* Better out-of-date messages.
* Documentation updates.
* Make 'ext-tests' work with debian /bin/sh => dash, too.

Other changes are really just bugfixes:
* The secondary URL/revision file doesn't have to exist. Thank you, Mark!
* Fix recursive behaviour of "_build-new-list".
* Fixed "-o verbose=all" output; would be interpreted as "totally
  silent" because of signed compares.
* Fix tempfile being left after FSVS run.
* Bugfix: on commit empty property hashes got created. Thank you, Bogdan.
* Bugfix for selection of entries (filter bit)
* Bugfixes for non-UTF8 locales and update/sync. Thank you, Gunnar.

I want to say "Thank you!" to all people giving feedback, so that the
quality is kept as high as possible.


As usual you can get the sources here
    http://freshmeat.net​/projects/fsvs
and installation help is at
    http://fsvs.tigris.o​rg/install.html

While manual pages are included, you might be interested
in the HTML documentation (with pictures) at
    http://doc.fsvs-software.org/


Please provide feedback; all problems, bugs, questions and "thank-you"s
are welcome at the two mailing lists.


Regards,

Phil

--
Versioning your /etc, /home or even your whole installation?
             Try fsvs (fsvs.tigris.org)!
Messages per page: