This bug was fixed in the package deja-dup - 35.4-0ubuntu3
---
deja-dup (35.4-0ubuntu3) artful; urgency=medium
* debian/patches/allow-no-packagekit.patch:
- Cherry-pick patch from upstream git that properly fixes our tests
in autopkgtests where packagekit isn't installed.
** Branch linked: lp:~ubuntu-desktop/deja-dup/ubuntu
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/1710309
Title:
Backup does not recognize gpg 2 option and fails
Status in Déjà
** Changed in: deja-dup
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/1710309
Title:
Backup does not recognize gpg 2 option and fails
OK, fixed in deja-dup. We now report GPG errors to user unless they
really do look like a bad password error.
https://git.launchpad.net/deja-
dup/commit/?id=e603ce8ac530f764862af082f689d1fa5062be5f
** Changed in: deja-dup
Status: Invalid => Fix Committed
** Package changed: duplicity
Well the endless loop aspect is probably from how deja dup is driving
duplicity. We treat most fog issues as bad passwords, I believe because
the error messages are a little variable.
So duplicity is likely correctly reporting gpg messages. If it doesn't
catch this case especially, maybe deja dup
duplicity cannot be expected to parse gpg.conf, no, nor to control gnupg
to such an extent. but if duplicity is to call out to gnupg for
encryption services, then duplicity can IMO be expected to recover
gracefully from catastrophic failures on gnupg's behalf to perform, even
when it arguably
This is not something duplicity controls. If gpg is saying that it does
not recognize the trust model supplied in gpg.conf, then the bug could
be that the version of gpg on the system is too old for this trust
model. It is not in duplicity since duplicity has no reason to read
gpg.conf. Perhaps
** No longer affects: deja-dup
** No longer affects: deja-dup (Ubuntu)
--
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/1710309
Title:
Backup does not recognize gpg 2 option and
@Developers: Please note, that the trust-model tofu+pgp is valid for PGP
2. See https://www.gnupg.org/documentation/manuals/gnupg/GPG-
Configuration-Options.html#GPG-Configuration-Options
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Hello Mats,
thanks for your output.
I was able to reproduce your bug and will add reproduction steps based
on these lines of your log:
DUPLICITY: . gpg: unknown trust model `tofu+pgp'
DUPLICITY: . gpg: /home/lynx/.gnupg/gpg.conf:89: invalid option
This indicates, that this might be a problem
10 matches
Mail list logo
