--- Begin Message ---
Subject: |
gnupg test failure |
Date: |
Sat, 27 Feb 2016 11:55:39 +0100 |
gnupg fails its tests:
...
note: keeping build directory `/tmp/guix-build-gnupg-2.1.11.drv-0'
builder for `/gnu/store/p91ba6zl4d8gr5ixfqxn8ixhrv13kdv9-gnupg-2.1.11.drv'
failed with exit code 1
cannot build derivation
`/gnu/store/ixcbdqm2xvclfnz4d25nv53wnp6x7alh-profile.drv': 1 dependencies
couldn't be built
cannot build derivation
`/gnu/store/904rahmy35wrhsfdb26pcfxyirhbmlnk-system.drv': 1 dependencies
couldn't be built
note: keeping build directory
`/tmp/guix-build-linux-libre-4.4.3-gnu.tar.xz.drv-0'
guix system: error: build failed: build of
`/gnu/store/904rahmy35wrhsfdb26pcfxyirhbmlnk-system.drv' failed
More details:
FAIL: gpgtar.test
Test: gpgtar.test
GNUPGHOME=/tmp/guix-build-gnupg-2.1.11.drv-0/gnupg-2.1.11/tests/openpgp
gpgtar: gpg2: gpg: encrypted with 1024-bit ELG key, ID B27907AA, created
2003-12-31
gpgtar: gpg2: "Test two (no pp) <address@hidden>"
gpgtar: gpg2: gpg: encrypted with 1024-bit ELG key, ID B27907AA, created
2003-12-31
gpgtar: gpg2: "Test two (no pp) <address@hidden>"
gpgtar: gpg2: gpg: encrypted with 1024-bit ELG key, ID B27907AA, created
2003-12-31
gpgtar: gpg2: "Test two (no pp) <address@hidden>"
gpgtar: gpg2: gpg: block_filter 0x00000000006edd10: read error
(size=12276,a->size=12276)
gpgtar: gpg2: gpg: block_filter 0x00000000006ee2e0: read error
(size=13882,a->size=13882)
gpgtar: gpg2: gpg: WARNING: encrypted message has been manipulated!
gpgtar: gpg2: gpg: block_filter: pending bytes!
gpgtar: gpg2: gpg: block_filter: pending bytes!
gpgtar: error running '../../g10/gpg2': exit status 2
--- End Message ---
--- Begin Message ---
Subject: |
Re: bug#22826: gnupg test failure |
Date: |
Mon, 5 Feb 2018 17:46:36 -0500 |
User-agent: |
Mutt/1.9.2 (2017-12-15) |
On Mon, Feb 05, 2018 at 11:14:55PM +0100, Andreas Enge wrote:
> The current release of gnupg after 2.1.11 is 2.2.4, which is available
> on hydra. Can we close this bug?
The GnuPG test suite has seen lots of changes since this bug was filed,
and it seems to pass consistently now, so I'm closing the bug.
signature.asc
Description: PGP signature
--- End Message ---