Package: duplicity Version: 3.0.4-1+b1 Severity: important X-Debbugs-Cc: [email protected]
Hello, There is a regression with the latest duplicity update: the application refuse an email adress as gpg identifier: LANG=C duplicity --encrypt-key [email protected] CommandLineError: Encrypt key should be an 8, 16, or 40 character hex string, like 'AA0E73D2'. Received '[email protected]' length=16 instead. Enter 'duplicity --help' for help screen. This is not what the behavior defined in the manual: --encrypt-key key-id When backing up, encrypt to the given public key, instead of using symmetric (traditional) encryption. Can be specified multiple times. The key-id can be given in any of the formats supported by GnuPG; see gpg(1), section "HOW TO SPECIFY A USER ID" for details. and this also breaks a backup workflow if the configuration was using an email adress previously. -- System Information: Debian Release: 13.1 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'oldstable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.12.43+deb13-amd64 (SMP w/32 CPU threads; PREEMPT) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages duplicity depends on: ii gnupg 2.4.7-21 ii libc6 2.41-12 ii librsync2t64 2.3.4-1.1+b1 ii python3 3.13.5-1 ii python3-fasteners 0.18-2 ii python3-httplib2 0.22.0-1 ii python3-lxml 5.4.0-1 ii python3-paramiko 3.5.1-3 ii python3-pexpect 4.9-3 ii python3-pkg-resources 78.1.1-0.1 ii python3-psutil 7.0.0-2 ii python3-requests 2.32.3+dfsg-5 Versions of packages duplicity recommends: ii python3-oauthlib 3.2.2-3 ii python3-urllib3 2.3.0-3 ii rsync 3.4.1+ds1-5 Versions of packages duplicity suggests: pn lftp <none> pn ncftp <none> pn par2 <none> pn python3-boto3 <none> ii python3-pip 25.1.1+dfsg-1 pn python3-swiftclient <none> pn tahoe-lafs <none> -- no debconf information
