From: Christopher Baines <mail@cbaines.net>
To: duplicity-talk@nongnu.org
Cc: 31773@debbugs.gnu.org
Subject: bug#31773: ERROR: test_sigchain_fileobj (testing.unit.test_collections.CollectionTest)
Date: Sun, 10 Jun 2018 10:01:47 +0100 [thread overview]
Message-ID: <8736xv6mmc.fsf@cbaines.net> (raw)
In-Reply-To: <874lib6mxh.fsf@cbaines.net>
[-- Attachment #1: Type: text/plain, Size: 2150 bytes --]
Hey,
The Guix package for duplicity is failing to build, and I was wondering
if there is a fix already? I've had a look on Launchpad, but didn't spot
anything.
Here is the error:
======================================================================
ERROR: test_sigchain_fileobj (testing.unit.test_collections.CollectionTest)
Test getting signature chain fileobjs from archive_dir
----------------------------------------------------------------------
Traceback (most recent call last):
File "/tmp/guix-build-duplicity-0.7.17.drv-0/duplicity-0.7.17/testing/unit/test_collections.py", line 188, in test_sigchain_fileobj
self.sigchain_fileobj_check_list(self.sigchain_fileobj_get(None))
File "/tmp/guix-build-duplicity-0.7.17.drv-0/duplicity-0.7.17/testing/unit/test_collections.py", line 180, in sigchain_fileobj_check_list
test_fileobj(0, "Hello, world!")
File "/tmp/guix-build-duplicity-0.7.17.drv-0/duplicity-0.7.17/testing/unit/test_collections.py", line 177, in test_fileobj
fileobjlist[i].close()
File "/tmp/guix-build-duplicity-0.7.17.drv-0/duplicity-0.7.17/duplicity/dup_temp.py", line 227, in close
assert not self.fileobj.close()
File "/tmp/guix-build-duplicity-0.7.17.drv-0/duplicity-0.7.17/duplicity/gpg.py", line 304, in close
self.gpg_failed()
File "/tmp/guix-build-duplicity-0.7.17.drv-0/duplicity-0.7.17/duplicity/gpg.py", line 271, in gpg_failed
raise GPGError(msg)
GPGError: GPG Failed, see log below:
===== Begin GnuPG log =====
gpg: CAST5 encrypted data
gpg: encrypted with 1 passphrase
gpg: WARNING: message was not integrity protected
gpg: Hint: If this message was created before the year 2003 it is
likely that this message is legitimate. This is because back
then integrity protection was not widely used.
gpg: Use the option '--ignore-mdc-error' to decrypt anyway.
gpg: decryption forced to fail!
gpg: WARNING: unsafe permissions on homedir '/tmp/guix-build-duplicity-0.7.17.drv-0/duplicity-0.7.17/testing/gnupg'
===== End GnuPG log =====
----------------------------------------------------------------------
Ran 418 tests in 548.274s
FAILED (errors=1, skipped=3)
Thanks,
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 962 bytes --]
next prev parent reply other threads:[~2018-06-10 9:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-10 8:55 bug#31773: Duplicit fails to build: ERROR: test_sigchain_fileobj (testing.unit.test_collections.CollectionTest) Christopher Baines
2018-06-10 9:01 ` Christopher Baines [this message]
2018-07-21 4:36 ` bug#31773: " Brendan Tildesley
2019-01-29 16:06 ` bug#31773: Duplicit fails to build: " Christopher Baines
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8736xv6mmc.fsf@cbaines.net \
--to=mail@cbaines.net \
--cc=31773@debbugs.gnu.org \
--cc=duplicity-talk@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).