Stat errors on locked (but excluded) files

Bug #1089131 reported by Aaron Whitehouse
188
This bug affects 66 people
Affects Status Importance Assigned to Milestone
Duplicity
Fix Released
Medium
Unassigned
duplicity (Ubuntu)
Fix Released
Medium
Unassigned
Zesty
Fix Released
Medium
Unassigned

Bug Description

Each time that I backup using duplicity (duply, actually) I receive errors about files that are locked, even though these files are in my exclude list.

I understand that this is a known bug:
http://lists.gnu.org/archive/html/duplicity-talk/2012-10/msg00020.html
https://answers.launchpad.net/duplicity/+question/169980

I would quite like to get rid of these errors, as they are confusing. Note that, while these are counted in the "Errors" number of the backup statistics, they do not seem to change the return value of duplicity and do not therefore affect the ability to use check_call from another Python script.

Related branches

Changed in duplicity:
assignee: nobody → Aaron Whitehouse (aaron-whitehouse)
description: updated
Revision history for this message
Kenneth Loafman (kenneth-loafman) wrote : Re: [Bug 1089131] Re: Stat errors on locked (but excluded) files

Please mark as "Propose to Merge" when the branch is finished.

On Sun, Jun 12, 2016 at 4:08 PM, Launchpad Bug Tracker <
<email address hidden>> wrote:

> ** Branch linked: lp:~aaron-whitehouse/duplicity/fix_stat_errors
>
> --
> You received this bug notification because you are subscribed to
> Duplicity.
> https://bugs.launchpad.net/bugs/1089131
>
> Title:
> Stat errors on locked (but excluded) files
>
> Status in Duplicity:
> New
>
> Bug description:
> Each time that I backup using duplicity (duply, actually) I receive
> errors about files that are locked, even though these files are in my
> exclude list.
>
> I understand that this is a known bug:
> http://lists.gnu.org/archive/html/duplicity-talk/2012-10/msg00020.html
> https://answers.launchpad.net/duplicity/+question/169980
>
> I would quite like to get rid of these errors, as they are confusing.
> Note that, while these are counted in the "Errors" number of the
> backup statistics, they do not seem to change the return value of
> duplicity and do not therefore affect the ability to use check_call
> from another Python script.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/duplicity/+bug/1089131/+subscriptions
>

Changed in duplicity:
assignee: Aaron Whitehouse (aaron-whitehouse) → nobody
importance: Undecided → Medium
milestone: none → 0.7.08
status: New → Fix Committed
Changed in duplicity:
status: Fix Committed → Fix Released
Vej (vej)
Changed in duplicity (Ubuntu):
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package duplicity - 0.7.06-2ubuntu3

---------------
duplicity (0.7.06-2ubuntu3) zesty; urgency=medium

  * d/p/backport-fix-tags-in-locked-folders.patch:
    - Fix OSError looking for tag in locked folders with exclude-if-present
      (LP: #1620085)
  * d/p/backport-crash-on-restore.patch:
    - Guard a chown call to avoid a stacktrace (LP: #1642813)
  * d/p/backport-ignore-excluded-locked-files.patch:
    - Ignore excluded locked files rather than giving noisy errors
      (LP: #1089131)
  * d/p/backport-downgrade-error.patch:
    - Make locked file messages be warnings not errors, again. This avoids
      confusing deja-dup. (LP: #1605939)
  * d/p/backport-flush-after-write.patch:
    - Flush after writing a temp file, to keep disk in sync (LP: #1538333)
  * d/p/backport-gpg2.patch:
    - Improve support for gpg2 (fixing FTBFS in process)

 -- Michael Terry <email address hidden> Tue, 07 Mar 2017 18:48:01 -0500

Changed in duplicity (Ubuntu Zesty):
status: Triaged → Fix Released
Revision history for this message
Patricio (patriciov) wrote :

Is this updated going to be released for 16.04?

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.