Allow testing an exclude file (output list of files it matches)

Bug #505366 reported by Daniel Hahler
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Duplicity
Confirmed
Medium
Unassigned

Bug Description

I'd like to have an interface/command to list the files that matches a given include/exclude pattern/file.

USE CASE:
I'm facing a problem, where duplicity (0.5.06, Ubuntu Hardy) backs up far too many files, and it appears to be related to my refactoring of excludes in the exclude file, from:
  + /var/lib/vz/private/111/var/lib/mysql/sqldump
  + /var/lib/vz/private/142/var/lib/mysql/sqldump
  /var/lib/vz/private/111/var/lib/mysql/*/
  /var/lib/vz/private/142/var/lib/mysql/*/
to
  + **/var/lib/mysql/sqldump
  **/var/lib/mysql/*/*
  (and adding)
  **/var/lib/mysql/ibdata1
  **/var/lib/mysql/ib_logfile*

It would be very helpful to easily test those patterns to track this down.

Daniel Hahler (blueyed)
description: updated
Revision history for this message
Elifarley Cruz (elifarley) wrote :

This bug is related to bug 884371

Revision history for this message
Elifarley Cruz (elifarley) wrote :

Using relative paths instead of prefixing all lines with "**" would be more reliable (avoiding possible false hits).

See spec use-relative-paths

Revision history for this message
Elifarley Cruz (elifarley) wrote :
Revision history for this message
Aaron Whitehouse (aaron-whitehouse) wrote :

Hi Daniel,

Sorry for the delay in responding. You should be able to achieve what you want by adding --dry-run and -v5 to your duplicity command, e.g.:

duplicity . --dry-run -v5 --include=**.py --exclude=** file:///tmp

I believe that you could even grep out those lines starting with "A " to just see the files that are to be included:

duplicity . --dry-run -v5 --include=**.py --exclude=** file:///tmp | grep "A "

That isn't to say that a specific --list-matching-files command (or similar) would not be helpful.

I have recently made a number of improvements to filelist glob processing and suspect that I have fixed your underlying bug. It would be very helpful if you could please test with the next release (should be released in the coming days) and let me know if you still have a problem.

Changed in duplicity:
status: New → Confirmed
Revision history for this message
Kenneth Loafman (kenneth-loafman) wrote : Update bug:, status confirmed, importance medium

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

 status confirmed
 importance medium
 done
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEExwf+p6/3mDvUSsaGH1G0ZBEHM/EFAmBmHUYACgkQH1G0ZBEH
M/FZXwgAtoyCHNY3F5SlNB4i1TIdLDRyQdWZk/kyrc22eAA//llVNkAN3JXMl1PO
sFE6qZue4GIwJGCIhNEcX1S4D1ur9/rojuAjvB6yxQ8CwOMBY/DU5zrw6gu1OYvp
4NiPZkZAkO4N3RNpeLSQobJh/vcjHT2XDsCRMFYQjMqA7vDiN3LIxF8kSt6iBsQy
kBtcdz0GmS1RUI5j1y77uoaEhx8GZ1N/fRevh+SBCSZFuXkedpbeob2XQqHsJIS8
5l6Ywz4NzUw5krpd6OriMm8MxgmBmdjnQB9C3JoRLgDWsLdfo2VQ4tfBG0xok85N
Z89bHS/SbAqDKzQVXbi5IGAngTkdyQ==
=f1JR
-----END PGP SIGNATURE-----

Changed in duplicity:
importance: Undecided → Medium
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.