please consider updating to >=0.7.08

Bug #1669616 reported by Jeff Fredrickson
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
duplicity (Ubuntu)
Fix Released
Critical
Unassigned
Zesty
Won't Fix
Critical
Unassigned
Artful
Fix Released
Critical
Unassigned

Bug Description

There is a bug in duplicity 0.7.06 that causes certain ignored folders to be backed up anyway. This results in deja-dup reporting an error after each backup. According to a bug report on deja-dup, this was fixed in duplicity 0.7.08:

https://bugs.launchpad.net/deja-dup/+bug/1313034

Please consider updating the Ubuntu package to a newer version of duplicity.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in duplicity (Ubuntu):
status: New → Confirmed
Vej (vej)
tags: added: precise trusty vivid xenial yakkety zesty
Revision history for this message
Vej (vej) wrote :

I would like to see 0.7.08 or higher for zesty. But zesty is feature freeze, which forbids the introduction of new changes.

Please see the following excerpt from duplicities changelog for more informations about the changes made since duplicity 0.7.06.

@Jeff: Most of them are bugfixes which would allow for merging into zesty. Nevertheless there are some changes which might need a FreezeException. Please see https://wiki.ubuntu.com/FreezeExceptionProcess for a guideline about this.

The same changes might be forbidden in a Stable Relase Update (SRU), which are the (non security related) updates for released ubuntu versions. This means that it might be necessary to create patches for the remaining bugfixes to ship them in an SRU without inclusion of new features.

One example for things which might be considered a new feature:

* Added acdclibackend.py from Stefan Breunig and Malay Shah
  - renamed from amazoncloudbackend to stress use of acd_cli

Revision history for this message
Kenneth Loafman (kenneth-loafman) wrote : Re: [Bug 1669616] Re: please consider updating to >=0.7.08

So, if we could extract just the bug fixes, how would you want them?
Patch? Merge?

...Ken
Duplicity Maintainer

On Thu, Mar 2, 2017 at 6:42 PM, Vej <email address hidden> wrote:

> I would like to see 0.7.08 or higher for zesty. But zesty is feature
> freeze, which forbids the introduction of new changes.
>
> Please see the following excerpt from duplicities changelog for more
> informations about the changes made since duplicity 0.7.06.
>
> @Jeff: Most of them are bugfixes which would allow for merging into
> zesty. Nevertheless there are some changes which might need a
> FreezeException. Please see
> https://wiki.ubuntu.com/FreezeExceptionProcess for a guideline about
> this.
>
> The same changes might be forbidden in a Stable Relase Update (SRU),
> which are the (non security related) updates for released ubuntu
> versions. This means that it might be necessary to create patches for
> the remaining bugfixes to ship them in an SRU without inclusion of new
> features.
>
> One example for things which might be considered a new feature:
>
> * Added acdclibackend.py from Stefan Breunig and Malay Shah
> - renamed from amazoncloudbackend to stress use of acd_cli
>
>
> ** Attachment added: "The CHANGELOG of duplicity betwwen the versions
> 0.7.06 and 0.7.11"
> https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/
> 1669616/+attachment/4830255/+files/CHANGELOG_duplicity_excerpt.txt
>
> --
> You received this bug notification because you are subscribed to
> duplicity in Ubuntu.
> https://bugs.launchpad.net/bugs/1669616
>
> Title:
> please consider updating to >=0.7.08
>
> Status in duplicity package in Ubuntu:
> Confirmed
>
> Bug description:
> There is a bug in duplicity 0.7.06 that causes certain ignored folders
> to be backed up anyway. This results in deja-dup reporting an error
> after each backup. According to a bug report on deja-dup, this was
> fixed in duplicity 0.7.08:
>
> https://bugs.launchpad.net/deja-dup/+bug/1313034
>
> Please consider updating the Ubuntu package to a newer version of
> duplicity.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/
> 1669616/+subscriptions
>

Revision history for this message
Vej (vej) wrote :

@Ken: I am not a sponsor, so it is not my decision. Some sponsors review debdiffs only, so this would be the safer thing for a SRU.

For zesty I want to try to get a FeatureFreeze Exception first, which would allow a sponsor or core developer to merge the upstream package. I plan to prepare this tomorrow (UTC +1) and file the request on Monday.

Revision history for this message
Vej (vej) wrote :

Will target 0.7.11 for FeatureFreeze Exception to include important fixes like the one for bug #1642813, which seems to close the high priority bug #1290852.

Revision history for this message
Michael Terry (mterry) wrote :

Vej, I think a Feature Freeze Exception (FFe) is going to be a tough sell on this -- I'm happy to upload a fix for bug 1642813 on top of 0.7.6, and then once zesty+1 opens, I can update to latest stable.

Is there any other critical bug fixes to squeeze into zesty?

Revision history for this message
Vej (vej) wrote :

@Michael Thanks for your assessment regarding a FFe. I am not so experienced on that ;). So I will stop working on the FFe and look for important bugfixes instead.

I will work trough all the bugfixes since 0.7.6, subscribe you to the important ones and nominate them for zesty.

Revision history for this message
Michael Terry (mterry) wrote :

@vej thank you for the bug collections. I've prepared an upload to fix bug 1620085, bug 1642813, bug 1089131, bug 1605939, and bug 1538333.

However now I'm fighting with some test failures that have creeped in due to a change in gpg. Working on it.

Revision history for this message
Vej (vej) wrote :

@Michael Thanks for that work.

> However now I'm fighting with some test failures that have creeped in due to a change in gpg. Working on it.

That is strange, because with the full update I prepared for the FFe I had not seen that. Please let me know if I should test or verify something.

Revision history for this message
Michael Terry (mterry) wrote :

@vej, yeah there seem to be several gpg2-related fixes in the 0.7 tree. After xenial, Ubuntu made gpg2 the default gpg, which I'm guessing is the source of this. I'm collecting fixes and re-testing.

Revision history for this message
Michael Terry (mterry) wrote :

OK, fixed the gpg2 issues and now 0.7.06-2ubuntu3 is in zesty. I've opened a task for z+1 and marked the zesty task won't fix. Thanks for the triage work, Vej!

Changed in duplicity (Ubuntu Zesty):
status: Confirmed → Won't Fix
Changed in duplicity (Ubuntu):
importance: Undecided → Critical
Changed in duplicity (Ubuntu Zesty):
importance: Undecided → Critical
tags: added: upgrade-software-version
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package duplicity - 0.7.11-1ubuntu1

---------------
duplicity (0.7.11-1ubuntu1) artful; urgency=low

  * Merge from Debian unstable (LP: #1669616). Remaining changes:
    - Enable tests during build and add a simple dep8 test
    - Drop Recommends for various backends to Suggests
    - d/p/{01-reverify,02-unicode}: Disabled, upstream fixed the issues
    - d/p/skip-some-tests.patch: Skip flaky tests
    - d/p/backport-gpg2.patch: Improve support for gpg2

 -- Michael Terry <email address hidden> Thu, 27 Apr 2017 09:28:22 -0400

Changed in duplicity (Ubuntu Artful):
status: Confirmed → Fix Released
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.