Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix command line arguments for duplicity 2.1 #2301

Merged
merged 3 commits into from
Sep 2, 2023

Commits on Aug 30, 2023

  1. Fix how the value is being passed for the gpg-options parameter

    Duplicity v2.1.0 backups are failing with the error:
    "... --gpg-options expected one argument".
    
    The issue is that duplicity v2.1.0 began using the argparse Python
    library and the parse_known_args function. This function
    interprets the argument being passed, "--cipher-algo=AES256",
    as an argument name (because of the leading '-') and not as an
    argument value. Because of that it exits with an error and
    reports that the --gpg-options arg is missing its value.
    
    Adding an extra set of quotes around this string causes
    parse_known_args to interpret the string as an argument
    value.
    darrsand committed Aug 30, 2023
    Configuration menu
    Copy the full SHA
    c034b0f View commit details
    Browse the repository at this point in the history

Commits on Sep 2, 2023

  1. Move source and target positional arguments to the end, required for …

    …Duplicity 2.1.0
    
    (Modified by JT.)
    jvolkenant authored and JoshData committed Sep 2, 2023
    Configuration menu
    Copy the full SHA
    7be687e View commit details
    Browse the repository at this point in the history
  2. Add a new backup.py command to print the duplicity command to the con…

    …sole to help debugging
    JoshData committed Sep 2, 2023
    Configuration menu
    Copy the full SHA
    08defb1 View commit details
    Browse the repository at this point in the history