Duplicity 0.6.24 doesn't show statistics after backup

Bug #1373327 reported by sander eikelenboom
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Duplicity
New
Undecided
Unassigned

Bug Description

After upgrading duplicity on my debian systems i noticed that the backup statistics that were printed after a backup by default are not there anymore. The commandline with which duplicity is invoked hasn't changed.

Upgrade to 0.6.24 (backport package Debian wheezy)

Before it used to print:
-----------[Incremental]------------
Local and Remote metadata are synchronized, no sync needed.
Last full backup date: Sun Sep 21 01:30:18 2014
--------------[ Backup Statistics ]--------------
StartTime 1411515020.44 (Wed Sep 24 01:30:20 2014)
EndTime 1411515020.49 (Wed Sep 24 01:30:20 2014)
ElapsedTime 0.05 (0.05 seconds)
SourceFiles 1
SourceFileSize 4096 (4.00 KB)
NewFiles 0
NewFileSize 0 (0 bytes)
DeletedFiles 0
ChangedFiles 0
ChangedFileSize 0 (0 bytes)
ChangedDeltaSize 0 (0 bytes)
DeltaEntries 0
RawDeltaSize 0 (0 bytes)
TotalDestinationSizeChange 103 (103 bytes)
Errors 0
-------------------------------------------------

After it only prints:
-----------[Incremental]------------
Local and Remote metadata are synchronized, no sync needed.
Last full backup date: Sun Sep 21 01:30:18 2014

The manpage still says:
       --no-print-statistics
              By default duplicity will print statistics about the current session after a successful backup. This switch disables that behavior.

So i would expect them to be still printed by default :)

description: updated
summary: - Duplicity 0.24 doesn't show statistics after backup
+ Duplicity 0.6.24 doesn't show statistics after backup
Revision history for this message
Kenneth Loafman (kenneth-loafman) wrote : Re: [Bug 1373327] [NEW] Duplicity 0.6.24 doesn't show statistics after backup
Download full text (5.7 KiB)

A couple of things:

1) When you first installed duplicity was it from .deb or from a tarball?
If it came from a tarball, you'll need to manually remove the tarball
version and reinstall the .deb upgrade you just did. They install to
different locations and the problem may be mixed sources.

2) If that does not fix the problem, check
/usr/shared/pyshared/duplicity/globals.py around line 118. print_globals
should be True.

On Wed, Sep 24, 2014 at 4:30 AM, sander eikelenboom <
<email address hidden>> wrote:

> Public bug reported:
>
> After upgrading duplicity on my debian systems i noticed that the backup
> statistics that were printed after a backup by default are not there
> anymore. The commandline with which duplicity is invoked hasn't changed.
>
> Upgrade to 0.6.24 (backport package Debian wheezy)
>
> Before it used to print:
> -----------[Incremental]------------
> Local and Remote metadata are synchronized, no sync needed.
> Last full backup date: Sun Sep 21 01:30:18 2014
> --------------[ Backup Statistics ]--------------
> StartTime 1411515020.44 (Wed Sep 24 01:30:20 2014)
> EndTime 1411515020.49 (Wed Sep 24 01:30:20 2014)
> ElapsedTime 0.05 (0.05 seconds)
> SourceFiles 1
> SourceFileSize 4096 (4.00 KB)
> NewFiles 0
> NewFileSize 0 (0 bytes)
> DeletedFiles 0
> ChangedFiles 0
> ChangedFileSize 0 (0 bytes)
> ChangedDeltaSize 0 (0 bytes)
> DeltaEntries 0
> RawDeltaSize 0 (0 bytes)
> TotalDestinationSizeChange 103 (103 bytes)
> Errors 0
> -------------------------------------------------
>
> After it only prints:
> -----------[Incremental]------------
> Local and Remote metadata are synchronized, no sync needed.
> Last full backup date: Sun Sep 21 01:30:18 2014
>
> The manpage still says:
> --no-print-statistics
> By default duplicity will print statistics about the current
> session after a successful backup. This switch disables that behavior.
>
> So i would expect them to be still printed by default :)
>
> ** Affects: duplicity
> Importance: Undecided
> Status: New
>
> ** Description changed:
>
> After upgrading duplicity on my debian systems i noticed that the backup
> statistics that were printed after a backup by default are not there
> anymore. The commandline with which duplicity is invoked hasn't changed.
>
> - Upgrade to 0.24 (backport package Debian wheezy)
> + Upgrade to 0.6.24 (backport package Debian wheezy)
>
> Before it used to print:
> -----------[Incremental]------------
> Local and Remote metadata are synchronized, no sync needed.
> Last full backup date: Sun Sep 21 01:30:18 2014
> --------------[ Backup Statistics ]--------------
> StartTime 1411515020.44 (Wed Sep 24 01:30:20 2014)
> EndTime 1411515020.49 (Wed Sep 24 01:30:20 2014)
> ElapsedTime 0.05 (0.05 seconds)
> SourceFiles 1
> SourceFileSize 4096 (4.00 KB)
> NewFiles 0
> NewFileSize 0 (0 bytes)
> DeletedFiles 0
> ChangedFiles 0
> ChangedFileSize 0 (0 bytes)
> ChangedDeltaSize 0 (0 bytes)
> DeltaEntries 0
> RawDeltaSize 0 (0 bytes)
> TotalDestinationSizeChange 103 (103 bytes)
> Errors 0
> -------------------------------------------------
>
> After it only prints:
> ----...

Read more...

Revision history for this message
sander eikelenboom (b-linux) wrote :
Download full text (6.5 KiB)

Wednesday, September 24, 2014, 3:07:55 PM, you wrote:

> A couple of things:

> 1) When you first installed duplicity was it from .deb or from a tarball?
> If it came from a tarball, you'll need to manually remove the tarball
> version and reinstall the .deb upgrade you just did. They install to
> different locations and the problem may be mixed sources.

> 2) If that does not fix the problem, check
> /usr/shared/pyshared/duplicity/globals.py around line 118. print_globals
> should be True.

Hi Kenneth,
I just checked:

git:~# locate duplicity/globals.py
/usr/lib/python2.7/dist-packages/duplicity/globals.py
/usr/lib/python2.7/dist-packages/duplicity/globals.pyc
/usr/share/pyshared/duplicity/globals.py

git:~# diff /usr/share/pyshared/duplicity/globals.py /usr/lib/python2.7/dist-packages/duplicity/globals.py
git:~#

So there is no difference and /usr/share/pyshared/duplicity/globals.py has:

# If set, print the statistics after every backup session
print_statistics = True

So it ought to be correct and not a stale file.

--
Sander

> On Wed, Sep 24, 2014 at 4:30 AM, sander eikelenboom <
> <email address hidden>> wrote:

>> Public bug reported:
>>
>> After upgrading duplicity on my debian systems i noticed that the backup
>> statistics that were printed after a backup by default are not there
>> anymore. The commandline with which duplicity is invoked hasn't changed.
>>
>> Upgrade to 0.6.24 (backport package Debian wheezy)
>>
>> Before it used to print:
>> -----------[Incremental]------------
>> Local and Remote metadata are synchronized, no sync needed.
>> Last full backup date: Sun Sep 21 01:30:18 2014
>> --------------[ Backup Statistics ]--------------
>> StartTime 1411515020.44 (Wed Sep 24 01:30:20 2014)
>> EndTime 1411515020.49 (Wed Sep 24 01:30:20 2014)
>> ElapsedTime 0.05 (0.05 seconds)
>> SourceFiles 1
>> SourceFileSize 4096 (4.00 KB)
>> NewFiles 0
>> NewFileSize 0 (0 bytes)
>> DeletedFiles 0
>> ChangedFiles 0
>> ChangedFileSize 0 (0 bytes)
>> ChangedDeltaSize 0 (0 bytes)
>> DeltaEntries 0
>> RawDeltaSize 0 (0 bytes)
>> TotalDestinationSizeChange 103 (103 bytes)
>> Errors 0
>> -------------------------------------------------
>>
>> After it only prints:
>> -----------[Incremental]------------
>> Local and Remote metadata are synchronized, no sync needed.
>> Last full backup date: Sun Sep 21 01:30:18 2014
>>
>> The manpage still says:
>> --no-print-statistics
>> By default duplicity will print statistics about the current
>> session after a successful backup. This switch disables that behavior.
>>
>> So i would expect them to be still printed by default :)
>>
>> ** Affects: duplicity
>> Importance: Undecided
>> Status: New
>>
>> ** Description changed:
>>
>> After upgrading duplicity on my debian systems i noticed that the backup
>> statistics that were printed after a backup by default are not there
>> anymore. The commandline with which duplicity is invoked hasn't changed.
>>
>> - Upgrade to 0.24 (backport package Debian wheezy)
>> + Upgrade to 0.6.24 (backport package Debian wheezy)
>>
>> Before it used to print:
>> -----------[Incremental]------------
>> Local and Remote me...

Read more...

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.