Date format is inconsistent in the output of `duplicity collection-status`
Bug #652696 reported by
zpcspm
This bug affects 3 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Duplicity |
New
|
Undecided
|
Unassigned | ||
Bug Description
I have a wrapper that parses the output of `duplicity collection-status` to make decisions about running a full or an incremental backup.
Today it failed.
I was assuming that the day of the month is always two digits, so I was counting for:
Fri Oct 01 00:00:05 2010
but I've got
Fri Oct 1 00:00:05 2010
I'm using duplicity 0.6.10
It would be nice to make the date format consistent, unless there's a strong reason against it.
To post a comment you must log in.
Actually, it would be nice to have a parseable "collection-status" output.
I'll allow a programmatic interface with "duplicity collection-status" the unix way :)
Cheers,
Geoff