← Back to team overview

desktop-packages team mailing list archive

[Bug 510625] Re: Bad parsing of GnuPG output, expecting english output, which doesn't work if locales different than english.

 

** Changed in: duplicity
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/510625

Title:
  Bad parsing of GnuPG output, expecting english output, which doesn't
  work if locales different than english.

Status in Duplicity - Bandwidth Efficient Encrypted Backup:
  Confirmed
Status in duplicity package in Ubuntu:
  Confirmed
Status in duplicity package in Debian:
  Confirmed

Bug description:
  this is a forward/extract of debian bug #565398, which lives over
  there: http://bugs.debian.org/565398

  summary: when using gpg and --encrypt-key, and only if LANG is set to de_AT
  and LC_CTYPE is set to de_AT (or POSIX or C, but not iso-8859-1 or utf-8), 
  then incremental backups fail completely. somehow or other duplicity 
  mis-interprets gnupg output and errors out: i assume it would be 
  the 8-bit nature of certain phrases like "Schlüssel" (german for "key") 
  which causes the mess, but i can't identify the code in question.

  reproducible: always. needs only an empty backup dir (source), an empty
  target dir (target), a gpg key and locale de_AT available.

  duplicity --encrypt-key KEYID source file://target
   works fine, creates a (minuscule) full backup
   running it again, with LANG unset (or to something purely 7bit like en_US)
   works perfect again, no problems.

  but running it with LANG=de_AT and LC_CTYPE=de_AT causes duplicity to attempt
  some gnupg decryption (of what? the cache and archive are in sync), and 
  it dies with a gpg failure (with the gpg message being the german equivalent
  of "encryption failed: bad passphrase", not surprising as no passphrase was
  given, nor should one be necessary).

  i'm attaching the relevant -v9 logs, first of the successful full run,
  then of a failed inc run (LANG and LC_CTYPE=de_AT) and then of the 
  successful inc run (LANG="", LC_CTYPE=de_AT). no changes were made to
  the source dir between runs.

  regards,
  az

To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/510625/+subscriptions