How to use --include-filelist-stdin or --exclude-filelist-stdin

On 09.02.2015 13:01, Aaron Whitehouse wrote:
> New question #261866 on Duplicity:
> https://answers.launchpad.net/duplicity/+question/261866
>
> Can somebody please give me a working example of how to use --include-filelist-stdin or --exclude-filelist-stdin?
>
> I'm trying to rejig the selection code to make all filelists globbing (as discussed on the mailing list) and don't want to break anything, but I'm struggling to make test cases using --include-filelist-stdin and --exclude-filelist-stdin that currently work (it isn't a feature that I have used before).
>
> Major bonus marks if somebody can give it to me as python code that I can drop into the functional tests, but any pointers would be appreciated!
>

maybe?
http://stackoverflow.com/questions/16672132/executing-shell-command-in-python-with-file-as-stdin

..ede/duply.net

Sorry I wasn't clear, Ede.

My main issue is that I don't know how to use the --include-filelist-stdin and --exclude-filelist-stdin options normally. Do people normally pipe a list to the command, or run the command and then send a list of files over stdin?

Apologies if this is a stupid question, but it isn't a use-case I'm familiar with and my various guesses have failed.

If I can figure that out, I can hopefully sort out how to automate that behaviour into a test case.

On 09.02.2015 13:31, Aaron Whitehouse wrote:
> Question #261866 on Duplicity changed:
> https://answers.launchpad.net/duplicity/+question/261866
>
> Status: Answered => Open
>
> Aaron Whitehouse is still having a problem:
> Sorry I wasn't clear, Ede.
>
> My main issue is that I don't know how to use the --include-filelist-
> stdin and --exclude-filelist-stdin options normally. Do people normally
> pipe a list to the command, or run the command and then send a list of
> files over stdin?
>
> Apologies if this is a stupid question, but it isn't a use-case I'm
> familiar with and my various guesses have failed.
>
> If I can figure that out, I can hopefully sort out how to automate that
> behaviour into a test case.
>

never used it myself, but as the description reads on the manpage it'd be something like

cat filelist.txt | duplicity /src file://target

..ede

Thanks Edgar, that's helpful.

Using that as a starting point, it looks as though it is:
cat exclude.txt | duplicity --exclude-filelist-stdin $SOURCEDIR file://$TARGETDIR

or
cat exclude.txt | duplicity --include-filelist-stdin $SOURCEDIR file://$TARGETDIR

But it would still be helpful if there is somebody out there who does actually use it who could please confirm. It seems unlikely that is the main way people are using it, as if it was they could just use --include-filelist etc rather than "cat"ing the file.

Kenneth has suggested on the list that we should drop the options, which seems sensible.

It can be changed back if it's not fixed. I must have thought it was.

On Wed, Jun 29, 2016 at 5:32 PM, Aaron Whitehouse <
<email address hidden>> wrote:

> Bug #1423367 status changed in Duplicity:
>
> Fix Committed => Fix Released
>
> https://bugs.launchpad.net/duplicity/+bug/1423367
> "--include-filelist-stdin and --exclude-filelist-stdin should be
> deprecated and ultimately removed"
>
> This bug is linked to #261866.
> How to use --include-filelist-stdin or --exclude-filelist-stdin
> https://answers.launchpad.net/duplicity/+question/261866
>
> --
> You received this question notification because your team duplicity-team
> is an answer contact for Duplicity.
>
> _______________________________________________
> Mailing list: https://launchpad.net/~duplicity-team
> Post to : <email address hidden>
> Unsubscribe : https://launchpad.net/~duplicity-team
> More help : https://help.launchpad.net/ListHelp
>