similar to: incorrect exclude list with -C

Hi! This problem gave me quite a headache tonight... I more or less have this source directory: hop@krautesel:/var/tmp$ ls -laR from/ from/: total 12 drwxrwxr-x 3 hop hop 4096 Feb 8 03:34 . drwxrwxrwt 6 root root 4096 Feb 8 03:34 .. drwxrwxr-x 2 hop hop 4096 Feb 8 03:18 CVS -rw-rw-r-- 1 hop hop 0 Feb 8

On behalf of the development team of R (www.R-project.org), I would like to report the following problem with recent versions of rsync. First, some background info. The R Development Core Team uses CVS for maintainins its source code archive. Additionally, there is a mechanism for "mirroring" some important (so-called recommended) extension packages from a CRAN (Comprehensive R

As mentioned on the rsync home page, the --files-from=FILE option in rsync version 2.6.0 is a useful option that allows one to "specify a list of files to transfer, and can be much more efficient than a recursive descent using include/exclude statements (if you know in advance what files you want to transfer)". However, --files-from does not help one implement the --rsync-exclude=FILE

I have added regular expression support using a POSIX implementation. The patch (against 2.5.5) is attached. The implementation is simple and follows the same mechanism that is implemented for normal searches. I added these command line arguments: --rexclude=PATTERN exclude files matching regexp PATTERN --rexclude-from=FILE exclude regexp patterns listed in FILE --rinclude=PATTERN

This is a patch to add an --rsync-exclude option to rsync-2.5.6cvs. File names in .rsync- (or .rsync+) are excluded (or included) from the file lists associated with the current directory and all of its subdirectories. This has advantages over --cvs-exclude for backing up large file systems since the .cvsignore files only apply to the current directory: unless the .cvsignore restrictions apply

Hi guys, I recently stumbled across what I think is an rsync bug. The problem was I was trying to rsync from one CVS checkout, to another, and was using rsync -Cavz to do the job. In this CVS module, there happens to be two sub-directories with the names of "core" and "tags" respectively, which were ignored, since these names matched the default CVS ignore list. When rsync

It would be nice if the CVS source had a .cvsignore file in the main dir with the following items: ssh scp sshd ssh-add ssh-keygen ssh-keyscan ssh-agent sftp-server sftp configure config.h.in config.h config.status Makefile ssh_prng_cmds *.out Plus a .cvsignore file in openbsd-compat that ignored "Makefile". ..wayne..

anyone who can help me understand- one of my developers reimported openssh snapshot from 0722 into cvs. he sent me the following email about an error he believes is in the snapshot i'm not a cvs-knowledgeable person, so i'm not all that clear on this, but should *.in files be in .cvsignore? i tried checking a later snapshot, but 0722 seems to be the latest one. .cvsignore is dated jun

I'm tracking some custom OpenSSH changes (based on 4.3p2) in a local CVS repository and have run into a few problems... mainly (I believe) because of the .cvsignore files. Keep in mind the main idea here is to commit the OpenSSH source without changes, tag, then add my custom changes and add a new tag. I can probably fix these by making local modes, but I'm just wondering if there

I have some rsync defined as a server on one of my production systems and use to to sync out various configuration files for services running on the box (dhcpd, dns named.conf files & the like). Both ends are Compaq Alpha/Tru64 5.1 systems running rsync 2.5.5. I'm having a fit trying to include certain files in specific subdirectories under the main path; one such example is below:

I think I'll start with the simple stuff, just to be safe. :-) Here are some cvsignore updates, and a fix for the inter-project dependencies in the MSVC *.dsw file. Cheers, Eric -------------- next part -------------- A non-text attachment was scrubbed... Name: vp32-cvs-ignore-patch.diff Type: application/octet-stream Size: 1524 bytes Desc: vp32-cvs-ignore-patch.diff Url :

I have noticed that the contents of per-directory .cvsignore files apply outside their subtrees when using --cvs-exclude in rsync 2.6.0. In the results below, notice how dir1/.cvsignore is applying to a file in dir2. There is no ~/.cvsignore, and the CVSIGNORE variable is unset. % ls -AFR .: dir1/ dir2/ ./dir1: .cvsignore file1 ./dir2: file2.foo % cat dir1/.cvsignore *.foo % /usr/bin/rsync

Building PowerPC.td register information header with tblgen Included from PowerPC.td:22: Parsing PowerPCInstrInfo.td:53: Variable not defined: 'GPRC'! make[3]: *** [PowerPCGenRegisterInfo.h.inc] Error 1 make[3]: Leaving directory `/pool/tmp/ssrc/llvm/lib/Target/PowerPC' maybe I just have to "make clean" and/or ./configure BTW, would it be nice to put Depend, Release and

Some of the debug messages that rsync outputs (when verbose >= 2) can occur on both sides of the connection. This makes it hard to know which program is saying what. Some debug messages deal with this by outputting a "[PID]" string at the start of the message. Unfortunately, the startup message that tells us which pid is which is only output when verbose >= 3, so there's a

Hi: Just did my first svn checkout. Pretty painless. I noticed that icecast and each of its dependent modules (except m4) has a .cvsignore file. Am I right in thinking these are redundant now? Geoff. --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a message to

Rails make it easy to start a new application. At the same time, import a new project into Subversion is not that simple -- there are quite few files that should be ignored. I used to manually remove added log files and tmp/cache, tmp/sessions, tmp/sockets files after the import and then go through the painful process of setting svn:ignore properties. There is an easier way -- simply

I'm using a simple client/server backup pull model rsync -a --delete -e ssh --exclude-from=$exclude path/$client.exclude \ ${client}-rsync:/ $path/$client but can't seem to find the right 'exclude' combination to fetch certain directories but not their contents. Unfortunately this was found during a recent major restore where the excluded directories had to be manually

Here a bug report about "!" not working properly in 2.6.4 and above, paraphrased... > Ok, see attachment. I've tested it right now between two hosts > running rsync 2.6.3-2 and 2.6.6-1. It works in the forward direction, > backwards it gives > > '!' rule has trailing characters: ! > rsync error: syntax or usage error (code 1) at

https://bugzilla.samba.org/show_bug.cgi?id=1873 wayned@samba.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- Additional Comments From wayned@samba.org 2004-10-05 17:19

> I like the idea of your rsync-exclude.patch and have thought > about hacking it in myself. However as you already have done the work > may I make a small suggestion...... can the name of the exclude file > (your .rsync) be specified in the flags.... e.g. > > rsync --rsync-exclude=.snapshot -axvH /here /there > > In this way different invocations (e.g. system and