gmane.comp.sysutils.backup.fsvs.general

Re: Is fsvs 1.1.16 compatible with RHEL 4?

Philipp Marek — 2008-10-06T16:21:16

Hello Farzad! On Monday 06 October 2008 Farzad FARID wrote: No, subversion 1.1 is too old; FSVS needs at least 1.4. But for this situation there's an easy workaround: use FSVS' chroot-helper. See here for details: http://fsvs-software.org/doc/doxygen-gif/group__howto__chroot.html I got it working on Suse 7.3 (from 2001 or something like that) with a 2.4.21 kernel by using a debian sarge base install (with debootstrap) (because of the 2.4 kernel, which modern glibc doesn't wants), and the 1.4.2 package from sarge-backports (http://packages.debian.org/sarge-backports/subversion). I don't know your machine x86, 32/64bit - if you trust me, I could provide you with a chroot tar of my 32bit x86, so you only need to compile the tiny chroot-wrapper program on RHEL4. Hope that helps - at least it's exactly the situation I wrote the wrapper for ;-) Regards, Phil

Is fsvs 1.1.16 compatible with RHEL 4?

Farzad FARID — 2008-10-06T15:12:54

Hi, I am embarassed because I tested fsvs on Debian, but my customer's target distribution is Red Hat Entreprise Linux 4, and by default fsvs can't compile on it... I know it's old but it's my customer's production platform ;) The configure script depends on the "apr-1" library version, RHEL4 only provides "apr-0", and there is a missing "svn_ra_initialize" symbol in "svn_ra-1". Here are the package versions provided by RHEL4: apr-0.9.4-24.5 apr-util-devel-0.9.4-21 apr-devel-0.9.4-24.5 apr-util-0.9.4-21 subversion-1.1.4-2.ent subversion-devel-1.1.4-2.ent Is there a way to compile fsvs on RHEL4 anyway? Regards,

Re: Can fsvs automatically find the repository to use for a commit with multiple URLs?

Farzad FARID — 2008-10-06T14:55:06

Hi, On Friday 03 October 2008 19:45:23 Philipp Marek wrote: OK, my customer is interested by the solution, I have to show him a working proof of concept :) For the moment, I think that using the URL priority to select the default commit destination for new files is the most natural solution. Plus, of course, the auto-selection of the destination for existing files, based on the associated URLs and the priority if the file is in more than one repository. Regards,

Re: Can fsvs automatically find the repository to use for a commit with multiple URLs?

Plamen Marinov — 2008-10-05T20:27:52

Maybe "fsvs status" to print "will be added" to first (defult) URL. If I use "fsvs add" to URL_XYZ, then add it to URL_XYZ. If you do it with patterns, then you must remove "auto add every new file" and you have again to use patterns. kind regards.

Re: Files listed as "changed" after aborted fsvs up

Philipp Marek — 2008-10-05T17:06:30

Well, after an update or commit the new entries file is written - but that should only happen *after* the other data has been handled. What does a "status -C -C -C" say? Maybe the size hasn't changed, and the timestamp gets re-read wrong. That's surely better. ... Yes ... FSVS uses $FSVS_WAA and $FSVS_CONF for temporary files, which get moved to their destination if they could be written completely. Please wait a few days ... I'm just a small bit away from a new release, and I've changed some internal handling for update/commit etc., so that it's cleaner. Maybe that's already solved, too. Regards, Phil

Re: Can fsvs automatically find the repository to use for a commit with multiple URLs?

Philipp Marek — 2008-10-05T16:59:20

Hello Maurice, On Sunday 05 October 2008 Maurice van der Pot wrote: Well, that's an idea ... but having an option to change this default would be necessary, though. Part of the problem is that even if there are not properties given explicitly there's a well-defined order for FSVS - which, again, might not match the users' assumptions. Regards, Phil

Re: Can fsvs automatically find the repository to use for a commitwith multiple URLs?

Maurice van der Pot — 2008-10-05T15:48:02

I had assumed this would be to the URL with the highest priority? Maurice.

Re: Files listed as "changed" after aborted fsvs up

Maurice van der Pot — 2008-10-05T15:46:14

The thing is that I don't understand the cause of the conflict. The .fsvs directory is not listed when I do fsvs status, the update that follows is aborted because .fsvs has been modified locally and afterwards the fsvs status command still doesn't show .fsvs as having been modified. How is that possible? I'd rather not handle this conflict until I understand where it's coming from. Another thing I'm seeing is that a commit changes the timestamp of the Urls file and the directories that this file is in. It looks like that results in those directories always having changes. griffon26< at >griffon27 ~> ls -ald .fsvs/6666cd76f96956469e7be39d750cc7d9/Urls .fsvs/6666cd76f96956469e7be39d750cc7d9/ .fsvs/ drwx------ 4 griffon26 users 4096 2008-10-05 17:35 .fsvs/ drwx------ 2 griffon26 users 4096 2008-10-05 17:35 .fsvs/6666cd76f96956469e7be39d750cc7d9/ -rwx------ 1 griffon26 users 82 2008-10-05 17:35 .fsvs/6666cd76f96956469e7be39d750cc7d9/Urls griffon26< at >griffon27 ~> fsvs status -v|grep "\.fsvs" ...... 1249 .fsvs/6666cd76f96956469e7be39d750cc7d9/Ign .t.... dir .fsvs/6666cd76f96956469e7be39d750cc7d9 .t.... dir .fsvs griffon26< at >griffon27 ~> date Sun Oct 5 17:38:12 CEST 2008 griffon26< at >griffon27 ~> fsvs commit Committing to svn+ssh://localhost/home/griffon26/repos/fsvsrepo/home-base .m.. dir .fsvs .m.. dir .fsvs/6666cd76f96956469e7be39d750cc7d9 committed revision 24 on 2008-10-05T15:38:19.590787Z as griffon26 griffon26< at >griffon27 ~> ls -ald .fsvs/6666cd76f96956469e7be39d750cc7d9/Urls .fsvs/6666cd76f96956469e7be39d750cc7d9/ .fsvs/ drwx------ 4 griffon26 users 4096 2008-10-05 17:38 .fsvs/ drwx------ 2 griffon26 users 4096 2008-10-05 17:38 .fsvs/6666cd76f96956469e7be39d750cc7d9/ -rwx------ 1 griffon26 users 82 2008-10-05 17:38 .fsvs/6666cd76f96956469e7be39d750cc7d9/Urls griffon26< at >griffon27 ~> fsvs status -v|grep "\.fsvs" ...... 1249 .fsvs/6666cd76f96956469e7be39d750cc7d9/Ign .t.... dir .fsvs/6666cd76f96956469e7be39d750cc7d9 .t.... dir .fsvs griffon26< at >griffon27 ~> strace shows that a temporary Urls file is created and then moved over to Urls, but I guess you know this. Should I send a debug log of any of these commands? Thanks, Maurice.

Re: Can fsvs automatically find the repository to use for a commit with multiple URLs?

Philipp Marek — 2008-10-05T15:41:28

Hello Farzad! On Friday 03 October 2008 Philipp Marek wrote: Another thing just came across my mind (again) - why I originally required this parameter: where should *new* entries, that have no URL associated yet, be committed? Maybe there's some simple answer to that question ... but I think that multi-url commit either has to ignore new files, or needs some specification which URL they should be given to ... that could be with patterns, maybe? Ideas welcome. Regards, Phil

Re: Can fsvs automatically find the repository to use for a commit with multiple URLs?

Philipp Marek — 2008-10-03T17:45:23

Hello Farzad, On Friday 03 October 2008 Farzad FARID wrote: I wanted to add _please_, /please/, *please* keep on using FSVS with multiple URLs; you're one of the few doing that, so you're very valuable for me. There's not enough feedback on multi-URL operation; I don't think that I got everything right. Please keep on telling me what works and what doesn't. Thank you. Regards, Phil

Re: Can fsvs automatically find the repository to use for a commit with multiple URLs?

Philipp Marek — 2008-10-03T16:25:58

Hello Farzad! On Friday 03 October 2008 Farzad FARID wrote: ... ... ... It knows where the current file is from; but not where you want it. I have on my TODO some kind of multi-commit - where each changed entry gets committed to the URL it belongs to. But this is not yet done. I thought that I *require* that a repository is given, because changes could easily be overlooked and committed against the wrong repository. (As currently only a single repository is possible.) You can use the "commit_to" option in the config, if you (normally) commit against a specific repository. That error I could work around - but I'm not sure whether that's correct, as it would silently put the file where it wasn't before - and the user possibly doesn't want it. But maybe you're right, and I should just give more rope, so that users can shoot themselves in the foot ... I'm aware that this is not really an answer to your questions; but patches are welcome ;-) Regards, Phil

Can fsvs automatically find the repository to use for a commit with multiple URLs?

Farzad FARID — 2008-10-03T15:14:10

Hi, I setup a test system, using FSVS 1.1.16, with 2 repositories, and one working directory, as follows: WC: /usr/src/FSVS/etc URLs: N:base,P:100,file:///usr/src/FSVS/repos/base/trunk/etc N:local,P:200,file:///usr/src/FSVS/repos/machines/M0379/etc The WC is a copy of my "/etc" directory. Following this howto (http://fsvs- software.org/doc/doxygen-gif/group__howto__master__local.html), I commited some files to the "local" repository, and all the other files to the "base" repository. Now, for example, I modify "/usr/src/FSVS/etc/hostname". If if commit without giving the "commit_to" option, I get an error message: # fsvs commit -m "Touched file" hostname Which URL would you like to commit to? Please choose one (config option "commit_to"). But "hostname" is already in the correct repository: # fsvs info hostname .m.? 16 hostname Type: file URL: file:///usr/src/FSVS/repos/machines/M0379/etc/hostname Status: 0x28 (mtime, likely) Flags: 0x0 (none) Dev: 65024 Inode: 2166935 Mode: 0100644 UID/GID: 0 (root)/0 (root) MTime: Fri Oct 3 16:02:12 2008 CTime: Fri Oct 3 16:02:12 2008 WAA-Path: /var/spool/fsvs/ea/45/33db34f563d21d08b4066d2f4ccf/ Revision: 6 Repos-MD5: 90dc9df7334df5036bd88b3dc3a0055c Size: 16 Moreover, if I set "commit_to=base" in the "config" file, I will get an even worse error message: # fsvs commit -m "Touched file" hostname Committing to file:///usr/src/FSVS/repos/base/trunk/etc .m.. 16 hostname An error occurred: Filesystem has no item (160013) in ci__directory: open_file I thought that FSVS would automatically know where to commit the file, why doesn't this work? Can I use FSVS with 2 URLs without having to use "-o commit_to" and/or with having a conflict if the default "commit_to" is not the one associated with som of the files I want to commit? Shouldn't the priority field play the same role as the default "commit_to" in the config file? Regards,

Re: Is the ignore list versionned?

Philipp Marek — 2008-10-02T16:21:46

Right. Not directly. The long explanation: FSVS can't use such simple things as a per-directory "svn:ignore" property - that wouldn't scale. So it uses a simple file in /etc/fsvs/*/Ign. If you're keeping your /etc versioned (with FSVS), you'll have the ignore list versioned, too - automatically; and that's what most people (at least, those that I know) do. If you don't want to keep your /etc versioned, but need the ignore list too, there are a couple of ways: 1) Use a script to copy it regularly into your working copy. 2) Put your $FSVS_CONF into the working copy. 3) Use some (dummy) file in your working copy, and put a commit-pipe like "cat /etc/fsvs/..../Ign" in it; that'll transparently use the data, but won't check that it's changed automatically (because the timestamp on the dummy file won't be changed if you change the ignore patterns). I'm planning to export some environment variables for use in such scripts, so that the path needn't be hardcoded. I hope one of these solutions is enough for you; if not, we can try to find another. Regards, Phil

Re: Modifying an existing URL breaks fsvs?

Philipp Marek — 2008-10-02T16:15:00

Hello Farzad, On Thursday 02 October 2008 Farzad FARID wrote: ... ... The problem is that FSVS stores the current revision your WC is at (BASE in subversion-speak) along with the URL. If you dump that URL, and load it (or another) again, FSVS won't know which revision it is at locally - and use rev0. When you're trying to commit, FSVS tells the repository that it has changes against rev0 - but the repository answers "That's out of date! Somebody else committed 200 revisions in the mean time!". That's why. To get it working again, you'll have to tell FSVS which revision the WC is at; and the easiest way to do that is to run "fsvs sync-repos". That'll fetch the HEAD revision from the repository, and assume that the WC is at that revision; so you should be fine. Alternatively, you could give a revision parameter to that command ("-rX") - but that's normally not necessary. Regards, Phil

Re: fsvs st always shows (.) but commit for this entry not possible

Philipp Marek — 2008-10-02T16:09:59

If I understand you correctly - "." is the WC base. This is the internal name. If you don't want that, don't call sudo fsvs st but eg. sudo fsvs st $PWD then it'll show the full name. Or, alternately, you could use the "path" option - on the command line, as environment variable, or in a config file: http://fsvs-software.org/doc/doxygen-gif/group__options.html#o_opt_path I hope that answers your question; I'm not sure whether I understand it correctly. Regards, Phil

Is the ignore list versionned?

Farzad FARID — 2008-10-02T16:06:04

Hi, Apparently the ignore list is not versionned. When I checkout a copy of a repository, I get an empty ignore list. Will this feature be added to fsvs? Regards,

Modifying an existing URL breaks fsvs?

Farzad FARID — 2008-10-02T14:14:41

Hi, I'm testing fsvs 1.1.16 on a Debian system, using the official Debian package. I created one repository, file:///usr/local/fsvs-repository, and committed "/etc" to it. BTW I know I should have created a subfolder on SVN first, but it was my first test install. The corresponding fsvs URL is: # fsvs urls N:,P:0,file:///usr/local/fsvs-repository I played with fsvs a bit and got it working correctly. By reading the manpage (which by the way does not completely describe the URL format, I opened an issue for this), I understood that I could give a name to the URL. So I ran the following command: (echo 'N:main,file:///usr/local/fsvs-repository') | fsvs urls load But it apparently broke fsvs! After the modification, I tried to make a commit: # fsvs commit -m 'Mise à jour de VMware' vmware rc5.d thnuclnt vmware-vix cups xdg init.d rc2.d rc3.d Committing to file:///usr/local/fsvs-repository .m.. dir init.d .mC. 10785 init.d/vmware An error occurred: Transaction is out of date (160028) in ci__directory: open_file "fsvs status" says there are modified files in the repository, but I think I never modified the SVN repos directly... Not knowing if the "transaction" mentionned here has any link with the SVN transaction, I ran "svnadmin lstxns /usr/local/fsvs-repository" but it didn't output anything. I ran "fsvs update" anyway: # fsvs update Updating file:///usr/local/fsvs-repository to revision 6. .mC. 498 fstab .mC. 277 network/interfaces .mC. 3726 network/if-up.d/mountnfs .mC. 261 network/if-up.d/avahi-daemon .mC. 32 network/if-up.d/wpasupplicant [... many more lines ...] .mC. 4546 init.d/dbus .mC. 1773 init.d/dirmngr .mC. 4521 init.d/hwclock.sh The entry ./init.d/vmware has changed locally But it doesn't modify anything. and "fsvs commit" still doesn't work. I tried undoing my urls change by running: (echo 'N:,file:///usr/local/fsvs-repository') | fsvs urls load But nothing changes. I have the same error messages. Can someone help me and tell me what went wrong? And how can I fix the repository without destroying and recreating it, which would make me loose the log history? Regards,

Re: fsvs st always shows (.) but commit for this entry not possible

Gunnar Thielebein — 2008-10-02T13:10:12

bit unclear. I mean to see the foldername instead of (.).

Re: fsvs st always shows (.) but commit for this entry not possible

Gunnar Thielebein — 2008-10-02T12:39:41

Would it be possible to always add the foldername instead of (.) ? Thanks, i'll try that.

Re: exitcode of fsvs diff

Philipp Marek — 2008-10-01T16:10:39

Hello Gunnar! On Tuesday 30 September 2008 Gunnar Thielebein wrote: Maybe; I think it works as expected. The documentation says The return code is 0 for successfull and 2 for an error. 1 is returned if the option "Stopping status reports as soon as changes are found" is used, and changes are found; ... A normal "status" should never return an error - unless there's been one :-) If you use the option, you'll get an exit code *if* changes are found. Better now? Or how can I improve the documentation, so that it's clearer? Regards, Phil

Re: fsvs st always shows (.) but commit for this entry not possible

Philipp Marek — 2008-10-01T15:57:52

Hello Gunnar! On Wednesday 01 October 2008 Gunnar Thielebein wrote: An unversion of "." is ... evil ;-) I'll try to get that impossible. And BTW, such local changes can be undone by "revert" - you just have to be careful to include an additional "-N", so that entries in "." are not reverted. Or, you could try using "add" (which is kind-of reverse of "unversion") - but I just see that this is not yet documented in http://fsvs-software.org/doc/doxygen-gif/group__howto__entry__statii.html Regards, Phil