duplicity-talk
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Duplicity-talk] re: exclude/include file syntax


From: S . Isard
Subject: [Duplicity-talk] re: exclude/include file syntax
Date: Mon, 21 Jul 2003 20:13:01 +0100 (BST)

On  30 Jun 2003, Jonas Meurer wrote:

> gives the error:
> Error opening file

> since it doesn't do that if i remove the --include-globbing-filelist and
> --exclude-globbing-filelist options, that seems to be the problem.

I downloaded duplicity-0.4.0 last weekend and hit the same problem.
There's a missing '=' sign in the file commandline.py. (If you have
already installed duplicity, it will be in
$PYTHONLIB/site-packages/duplicity/commandline.py, where $PYTHONLIB is
something like /usr/lib/python2.2, or wherever python is installed on
your machine.)  Here's a patch:

*** commandline.py      2003/07/20 12:22:46     1.1
--- commandline.py      2003/07/20 12:29:17
*************** def parse_cmdline_options(arglist):
*** 42,48 ****
                 ["allow-source-mismatch", "archive-dir=", "cleanup",
                  "current-time=", "collection-status", "encrypt-key=",
                  "exclude=", "exclude-device-files", "exclude-filelist=",
!                 "exclude-globbing-filelist", "exclude-filelist-stdin",
                  "exclude-other-filesystems", "exclude-regexp=",
                  "file-to-restore=", "force", "full", "incremental",
                  "include=", "include-filelist=", "include-filelist-stdin",
--- 42,48 ----
                 ["allow-source-mismatch", "archive-dir=", "cleanup",
                  "current-time=", "collection-status", "encrypt-key=",
                  "exclude=", "exclude-device-files", "exclude-filelist=",
!                 "exclude-globbing-filelist=", "exclude-filelist-stdin",
                  "exclude-other-filesystems", "exclude-regexp=",
                  "file-to-restore=", "force", "full", "incremental",
                  "include=", "include-filelist=", "include-filelist-stdin",

Stephen Isard




reply via email to

[Prev in Thread] Current Thread [Next in Thread]