Re: [Duplicity-team] [Question #192331]: TypeError in dup_time.py with remove-older-than

Mon, 02 Apr 2012 01:55:01 -0700 

Question #192331 on Duplicity changed:
https://answers.launchpad.net/duplicity/+question/192331

    Status: Open => Answered

edso proposed the following answer:

-------- Original Message --------
Subject:        Re: [Duplicity-team] [Question #192331]: TypeError in 
dup_time.py with remove-older-than
Date:   Sun, 1 Apr 2012 11:05:55 -0500
From:   Kenneth Loafman <[email protected]>
To:     [email protected]
CC:     [email protected]


On Sun, Apr 1, 2012 at 10:50 AM, Derek Kozikowski
<[email protected]
<mailto:[email protected]>> wrote:

    New question #192331 on Duplicity:
    https://answers.launchpad.net/duplicity/+question/192331

    Greetings,
    I am attempting to clean out some of my older backups using the duplicity 
remove-older-than command, but I'm getting an exception. Â I am using Ubuntu 
10.04 and duplicity 0.6.18. Â The command and stack trace follow:


    $ sudo duplicity remove-older-than 1Y --force "file:///media/EZ BUS 
DT/MachineName/DuplicityBackups/home_backup"
    Traceback (most recent call last):
    Â File "/usr/local/bin/duplicity", line 1236, in <module>
    Â  Â with_tempdir(main)
    Â File "/usr/local/bin/duplicity", line 1229, in with_tempdir
    Â  Â fn()
    Â File "/usr/local/bin/duplicity", line 1115, in main
    Â  Â action = commandline.ProcessCommandLine(sys.argv[1:])
    Â File "/usr/lib/python2.6/dist-packages/duplicity/commandline.py", line 
975, in ProcessCommandLine
    Â  Â args = parse_cmdline_options(cmdline_list)
    Â File "/usr/lib/python2.6/dist-packages/duplicity/commandline.py", line 
592, in parse_cmdline_options
    Â  Â globals.remove_time = dup_time.genstrtotime(arg)
    Â File "/usr/lib/python2.6/dist-packages/duplicity/dup_time.py", line 278, 
in genstrtotime
    Â  Â return override_curtime - intstringtoseconds(timestr)
    TypeError: unsupported operand type(s) for -: 'NoneType' and 'int'

    I tried replacing 1Y with 365D with the same result. Â Is this
something as silly as the order of my options, or a real bug?

    Thanks!


Did you use '365 D' or '365D'? Â '1 Y' would not work because of the space. Â 
See TIME FORMATS in the man page.

...Ken

-- 
You received this question notification because you are a member of
duplicity-team, which is an answer contact for Duplicity.

_______________________________________________
Mailing list: https://launchpad.net/~duplicity-team
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~duplicity-team
More help   : https://help.launchpad.net/ListHelp

Reply via email to