Hi Leo, Last month, you pushed this commit to master:
> commit e6f63412c9abe6a3b4ddf0ce39735d1e2a65491d > Author: Leo Famulari <l...@famulari.name> > Date: Wed Dec 20 03:20:09 2017 -0500 > > gnu: python-pygpgme: Use GnuPG 1 for the test suite. > > * gnu/packages/gnupg.scm (python-pygpgme, python2-pygpgme)[inputs]: Use > gnupg-1 > and make it a native-input. and you modified gpgme in the immediately following commit: > commit 0e06bec250f34dbab378b2c1e937af75db900bcc > Author: Leo Famulari <l...@famulari.name> > Date: Wed Dec 20 03:20:01 2017 -0500 > > gnu: gpgme: Build with the latest GnuPG. > > * gnu/packages/gnupg.scm (gpgme)[inputs]: Use the latest gnupg package. > [arguments]: Keep a reference to the gnupg package used for build. Clearly you were aware that python-pygpgme needed adjustment to continue building, and I appreciate your attention to detail here, but something seems to have gone wrong. Since these commits, Hydra has failed to build python-pygpgme and python2-pygpgme on all hydra-supported systems: https://hydra.gnu.org/eval/109862#tabs-now-fail https://hydra.gnu.org/job/gnu/master/python-pygpgme-0.3.x86_64-linux https://hydra.gnu.org/job/gnu/master/python-pygpgme-0.3.i686-linux https://hydra.gnu.org/job/gnu/master/python-pygpgme-0.3.armhf-linux https://hydra.gnu.org/job/gnu/master/python2-pygpgme-0.3.x86_64-linux https://hydra.gnu.org/job/gnu/master/python2-pygpgme-0.3.i686-linux https://hydra.gnu.org/job/gnu/master/python2-pygpgme-0.3.armhf-linux I can reproduce the failure on my local GuixSD system as well. Could you take a look? Mark
