Comment 21 for bug 1170161

Revision history for this message
Kenneth Loafman (kenneth-loafman) wrote : Re: [Bug 1170161] Re: FeatReq: alternate filenames to support S3/Glacier

For LTS versions Ubuntu does not allow anything but fixes. For
enhancements you need to go the the duplicity PPA.

On Thu, Jan 1, 2015 at 6:34 PM, rfkrocktk <email address hidden>
wrote:

> Edit: it seems to have been released as an RPM (as per here:
> https://launchpad.net/duplicity/+milestone/0.6.24), but not as a DEB,
> any reason why?
>
> --
> You received this bug notification because you are subscribed to
> Duplicity.
> https://bugs.launchpad.net/bugs/1170161
>
> Title:
> FeatReq: alternate filenames to support S3/Glacier
>
> Status in Duplicity - Bandwidth Efficient Encrypted Backup:
> Fix Released
>
> Bug description:
> Feature request: be nice when using S3/Glacier to only transition the
> difftars to Glacier, while leaving the manifests and sigtars alone.
> Given the current duplicity naming scheme, and the limitations of the
> Glacier transition rules, this is currently impossible. S3 transition
> rules can distinguish which files to transition to Glacier by matching
> against a file prefix -- a direct string match, not a regexp match. So
> basically you need to be able to tell if it's a manifest, sigtar, or
> difftar by looking at the part before the timestamp. At present
> sigtars can be identified this way, but manifests and difftars and not
> distinguishable by a prefix match.
>
> This feature would also permit a simple workaround for bug 1170113.
>
> Some discussion of this feature request is in this mailing list thread:
>
> http://lists.nongnu.org/archive/html/duplicity-talk/2013-04/msg00052.html
>
> I also note that recent discussion of bug 1039511 has touched on this
> same feature request.
>
> I am attaching a patch to 0.6.21, which patch is completely untested,
> which implements a version of this scheme. This patch introduces a
> switch "--alternate-filenames" which directs duplicity to generate the
> alternate filenames, but with or without the switch it will read both
> old and new filenames. Thus I believe this can work with a mix of old
> and new filenames in a backup chain. Again, the patch is untested.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/duplicity/+bug/1170161/+subscriptions
>