Documentation Error for Regex Include

Bug #1813615 reported by Ben Boeck
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Duplicity
Expired
Undecided
Unassigned

Bug Description

Hello,

first, thank you for the great tool.

Checking the duplicity man page I found an error and some unclarities in the "file selection" part which lead to confusion:

----
1) error: this example should be --include-regexp instead of --include:

"So for instance

    --include ’[0-9]{7}(?!foo)’ <--------!

matches any files whose full pathnames contain 7 consecutive digits which aren’t followed by ’foo’. However, it wouldn’t match /home even if /home/ben/1234567 existed."

----
2) typo
"as this is included within /user/local" should be "/usr/local"

----
3) unclear: highlight the difference between --include-filelist and --exclude-filelist. From my understanding they follow the name, so /usr/local will be included when used with --include-filelist whereas excluded in --exclude-filelist, BUT in both cases entries can be included/excluded by prepending the line with +/-.

I recon the reason is to make do with only one parameter --include-filelist or --exclude-filelist for BOTH includes/excludes. This could be highlighted more clearly.

----
4) improvement: Would it be a good idea to include in the examples with multiple includes/excludes in an include/exclude file that the last line would most likely be --exclude '**'?

It is missing here, for example:
" For example, if file "list.txt" contains the lines:

    /usr/local
    - /usr/local/doc
    /usr/local/bin
    + /var
    - /var "

----
5) improvement: for the include/exclude examples, I think it would make sense to not only show the include/exclude file but also the command line. It is missing for above example.

Thank you,
kind regards

Ben

Revision history for this message
Bill Yikes (yik3s) wrote :

This bug relates to:

https://bugs.launchpad.net/duplicity/+bug/1730640

But note neither should be marked as a duplicate though, because both reports have some overlap and some unique issues.

Revision history for this message
Kenneth Loafman (kenneth-loafman) wrote :

Please upgrade to the current version of duplicity, 0.8.18.  This will assure that any bugs fixed since your release are available and may fix your issue.

There are multiple options both stable and daily:
- Source - https://gitlab.com/duplicity/duplicity
- Stable tarball install - https://launchpad.net/duplicity/+download
- Stable duplicity PPA - https://code.launchpad.net/~duplicity-team/+archive/ubuntu/duplicity-release-git
- Latest duplicity PPA - https://code.launchpad.net/~duplicity-team/+archive/ubuntu/duplicity-develop-git
- Stable snap builds - “sudo snap install duplicity —classic"
- Latest snap builds - “sudo snap install duplicity —classic —edge"
- Stable pip3 builds - “sudo pip[23] install duplicity"
- Latest pip3 builds - “sudo pip[23] install --pre duplicity"

Note 1: UNINSTALL duplicity first if it was installed from a different source..  This is due to divergent install locations, especially between repository installs and the other forms.

Note 2: Launchpad PPAs contain builds for Bionic 18.04, Eoan 19.10, Focal 20.04, and Hirsute 20.10.

Note 3: Xenial 16.04 works with Snap and Pip installs, but cannot be built under Launchpad PPAs at the moment.

Changed in duplicity:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Duplicity because there has been no activity for 60 days.]

Changed in duplicity:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.