Spit out warning codes for iteration warns

Bug #429785 reported by Michael Terry on 2009-09-15
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

When iterating, if duplicity sees a file it can't read or can't stat or is a socket that it will skip, it doesn't currently give a machine-readable code.

Here's a bzr branch that adds that. I also fixed po/update-pot in the process, because I updated the pot file to included changed strings.

Related branches

Larry Gilbert (l2g) on 2009-09-16
Changed in duplicity:
status: New → Fix Committed
Changed in duplicity:
importance: Undecided → Medium
Changed in duplicity:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers