Login | Register
My pages Projects Community openCollabNet

Discussions > users > Re: FSVS 1.0.3 released

fsvs
Discussion topic

2020-03-13: This site is going to be decommissioned and shut down very soon. Please copy and archive any data you wish to keep ASAP

Hide all messages in topic

All messages in topic

Re: FSVS 1.0.3 released

Author mucci at perspectives dot qc dot ca
Full name mucci at perspectives dot qc dot ca
Date 2006-01-19 07:40:49 PST
Message Hi Phil
> I'm using gcc 4.0.3 (prerelease) (debian 4.0.2-7); which are you using?
> Because it doesn't seem to understand __nonnull() or __attribute_pure__.
>
# gcc -v
Reading specs from /usr/lib/gcc-lib/i38​6-redhat-linux/3.2.2​/specs
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man
--infodir=/usr/share/info --enable-shared --enable-threads=posix
--disable-checking --with-system-zlib --enable-__cxa_atexit
--host=i386-redhat-linux
Thread model: posix
gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5)

> My pcre-library is libpcre3 6.4-1.1; which are you using, as don't have
> PCRE_NO_AUTO_CAPTURE?
>
pcre-3.9-10

> The inclusion of "-idirafter /usr/include/pcre/" is no problem; but not
> using PCRE_NO_AUTO_CAPTURE has the possible problem of leaking memory, if
> an ignore pattern has () in it ...
>
As I said my friend simply find a (hacky?) way to make it work...
> I believe I need someone with autoconf/automake or similar experience ...
>
Good idea! But sadly I can't help...

If you have any other question, please do not hesitate!

Ben

Re: FSVS 1.0.3 released

Author pmarek
Full name P.Marek
Date 2006-01-18 22:25:05 PST
Message Hello Benjamin!


Please let's verify some things.


I'm using gcc 4.0.3 (prerelease) (debian 4.0.2-7); which are you using?
Because it doesn't seem to understand __nonnull() or __attribute_pure__.

My pcre-library is libpcre3 6.4-1.1; which are you using, as don't have
PCRE_NO_AUTO_CAPTURE?

The inclusion of "-idirafter /usr/include/pcre/" is no problem; but not
using PCRE_NO_AUTO_CAPTURE has the possible problem of leaking memory, if
an ignore pattern has () in it ...


I believe I need someone with autoconf/automake or similar experience ...



Regards,

Phil

Re: FSVS 1.0.3 released

Author pmarek
Full name P.Marek
Date 2006-01-17 22:52:29 PST
Message > Hi Phil,
>
> As I've said in my previous email... Attached the make error log and
> patch proposed by my friend to make it work under my system.
>
> Hope this will help you!
Thank you, I'll have a look at that tonight.


>> ~~~~~~~~~~~~~~~~~~~~​~~~~~~~~~~~~~~~
>> On make run-tests
>> ~~~~~~~~~~~~~~~~~~~~​~~~~~~~~~~~~~~~
>> I have to run run-tests as root because otherwise:
The tests test the ability to re-create devices, and this needs root
priviledges.
Perhaps there should be a flag for the tests to skip the root-only parts.


>> ~~~~~~~~~~~~~~~~~~~~​~~~~~~~~~~~~~~~~~~~~​~~~~~~~~~
>> I get the following when I commit one of my user home directory:
>> ~~~~~~~~~~~~~~~~~~~~​~~~~~~~~~~~~~~~~~~~~​~~~~~~~~~
>>
>> $ fsvs commit -m "First import" -v
...
>> An error occured at 13:19:20.953: No such file or directory (2)
>> in ac__commit_dir [commit.c:354]: ac__ci_set_props: ac__ci_set_props
>> in ac__commit_dir [commit.c:339]: ac__commit_dir: ac__commit_dir
>> in ac__commit_dir [commit.c:339]: ac__commit_dir: ac__commit_dir
>> in ac__commit_dir [commit.c:339]: ac__commit_dir: ac__commit_dir
>> in ac__commit_uninit [commit.c:424]: ac__commit_dir: ac__commit_dir
>> in ac__commit_uninit [commit.c:427]: ac__commit_dir
>> in main [fsvs.c:425]
>> Version fsvs-1.0.3:69
>>
>> The file:
>> $ ls -l ./.cpan/build/Templa​te-Toolkit-2.10/Make​file.PL
>> -rw-r--r-- 1 253 253 35053 Apr 29 2003
>> ./.cpan/build/Templa​te-Toolkit-2.10/Make​file.PL
I'll have a look at that.

>> ~~~~~~~~~~~~~~~~~~~~​~~~~~~~~~~~~~~~~~~~~​~~~~~~~~~~~~~~
>> Also with an other directory after initial commit... on svn co or
>> export I get:
>> ~~~~~~~~~~~~~~~~~~~~​~~~~~~~~~~~~~~~~~~~~​~~~~~~~~~~~~~~
>>
>> $ svn export file:///backup/fsvs/test/ /tmp/test/
>> [snip]
>> A /tmp/test/stats-old/failref.png
>> svn: Unsupported special file type 'link:../public_stats'
Yes, I see.
That's because I've got a small incompatibility in fsvs, which will be
corrected with the next release.
(I use "link:", whereas svn uses "link ")


Thank you!


Regards,

Phil

Re: FSVS 1.0.3 released

Author blair
Full name Blair Zajac
Date 2006-01-15 09:35:07 PST
Message Philipp Marek wrote:
> Am Sunday 15 January 2006 05:28 schrieb Blair Zajac:
>
>>Thanks for the announcement, this is the first announcement I've seen,
>>since I don't read the svn users list too often. You may want to post the
>>announcements to the dev list also.
>
> I'm not sure if these would be welcome there.
> But I'll consider that for the next release.

I don't think anybody would mind (being an svn committer myself), and it's
always good to get more developers involved in a project, which will be more
likely if the people on the dev list are aware of fsvs.

>>The goals of the project look pretty good and I could see this being of use
>>in a large installation, managing a common set of /usr, /var, /etc.
>
> Correct, that's its main target - large installations.
>
>>Have you heard of a the rdiff-backup project? You may want to check it out
>>if you haven't, it's goals are similar to yours.
>
> I'll have a look. But quickly reading I don't see something like a versioned
> storage.

Well, it's not versioned in the Subversion sense, but you can recover a backup
as it looked like in a previous backup.

>>I think the one problem with a Subversion backend is that you can never
>>remove older data. In a filesystem based backup, you can trim older
>>backups, say from daily, to monthly after the data ages to 6 months.
>
> "svn obliterate" - svn issue 516, see
> http://subversion.ti​gris.org/issues/show​_bug.cgi?id=516

Let's hope that gets in soon :)

Regards,
Blair

Re: FSVS 1.0.3 released

Author pmarek
Full name P.Marek
Date 2006-01-15 09:18:30 PST
Message Am Sunday 15 January 2006 05:28 schrieb Blair Zajac:
> Thanks for the announcement, this is the first announcement I've seen,
> since I don't read the svn users list too often. You may want to post the
> announcements to the dev list also.
I'm not sure if these would be welcome there.
But I'll consider that for the next release.

> The goals of the project look pretty good and I could see this being of use
> in a large installation, managing a common set of /usr, /var, /etc.
Correct, that's its main target - large installations.

> Have you heard of a the rdiff-backup project? You may want to check it out
> if you haven't, it's goals are similar to yours.
I'll have a look. But quickly reading I don't see something like a versioned
storage.

> http://www.nongnu.or​g/rdiff-backup/
>
> Some of the advantages that rdiff-backup has is that it does only a single
> pass over the data to be backed up, unlike rsync, and it also handles Mac
> OS X resource forks.
Well, fsvs does a complete filesystem lookup (opendir/readdir/lstat,
optionally reading files to determine whether they have changed), and one
pass for committing the files.

> I think the one problem with a Subversion backend is that you can never
> remove older data. In a filesystem based backup, you can trim older
> backups, say from daily, to monthly after the data ages to 6 months.
"svn obliterate" - svn issue 516, see
http://subversion.ti​gris.org/issues/show​_bug.cgi?id=516


Thank you for your answer.


Regards,

Phil

FSVS 1.0.3 released

Author pmarek
Full name P.Marek
Date 2006-01-12 22:11:23 PST
Message Hello everybody,


FSVS 1.0.3 is released.

----- Excerpt from http://fsvs.tigris.org

FSVS stands for “Fast System VerSioning”, “File System VerSioning” or
“Full System VerSioning”. It aims to become a complete backup/restore tool
for all files in a directory tree or whole filesystems, with a subversion
repository as the backend.
You may think of it as some kind of tar or rsync with versioned storage.

----- Excerpt ends


This new release has a lot of bugfixes and a few notable changes:

- A testing framework with result verification.
  This leads to much higher quality, since bugs should be more readily
found. (1)
- A new command for synchronizing with the repository-state
("sync-repos").
  (Documentation soon in fsvs-repository in doc/USAGE, not included in
tar)
- update, commit and sync-repos now print a tab before the revision number,
  to ease parsing from shell-scripts.
- The format for the local storage area has changed again. But this is no
  cause for alarm; simply do "fsvs sync-repos" and a new list will be
  generated from the repository.


Do not hesitate to contact me for questions and problems.


Regards,

Phil



Ad 1: I already found (apart from some bugs in fsvs) a bug in rsync, which
causes it to try to chdir() into a device, so there're spurious test
failures.
Bug is already filed in debian, I'm thinking about using something like
"ls -laR" and "md5sum" as (partial) substitute.
Messages per page: