From: Chris Marusich <cmmarusich@gmail.com>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: 01/01: gnu: python-pygpgme: Use GnuPG 1 for the test suite.
Date: Sat, 06 Jan 2018 18:19:10 -0800 [thread overview]
Message-ID: <87shbipg0x.fsf@gmail.com> (raw)
In-Reply-To: <20171228040521.GA6001@jasmine.lan> (Leo Famulari's message of "Wed, 27 Dec 2017 23:05:21 -0500")
[-- Attachment #1: Type: text/plain, Size: 669 bytes --]
Leo Famulari <leo@famulari.name> writes:
> On Wed, Dec 27, 2017 at 07:57:17PM -0500, Mark H Weaver wrote:
>> Alas, your most recent changes seem to have now broken qgpgme:
>>
>> https://hydra.gnu.org/eval/109869#tabs-now-fail
>> https://hydra.gnu.org/job/gnu/master/qgpgme-1.9.0.x86_64-linux
>> https://hydra.gnu.org/job/gnu/master/qgpgme-1.9.0.i686-linux
>> https://hydra.gnu.org/job/gnu/master/qgpgme-1.9.0.armhf-linux
>
> Sigh... I didn't even know this package existed. I'll take a look.
I'm not sure how to use Hydra... Is there a place in Hydra one can go
after committing a change to know if it broke a package like this?
--
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2018-01-07 2:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20171220201341.6365.99040@vcs0.savannah.gnu.org>
[not found] ` <20171220201342.95BEC2044F@vcs0.savannah.gnu.org>
2017-12-27 0:11 ` 01/01: gnu: python-pygpgme: Use GnuPG 1 for the test suite Mark H Weaver
2017-12-27 2:04 ` Leo Famulari
2017-12-28 0:57 ` Mark H Weaver
2017-12-28 4:05 ` Leo Famulari
2018-01-07 2:19 ` Chris Marusich [this message]
2018-01-07 12:42 ` Marius Bakke
2018-01-08 2:57 ` Chris Marusich
2018-01-09 4:48 ` Leo Famulari
2017-12-28 4:56 ` Leo Famulari
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=87shbipg0x.fsf@gmail.com \
--to=cmmarusich@gmail.com \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/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).