From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.96.142.65 with SMTP id ru1csp312896qdb; Wed, 2 Apr 2014 18:01:29 -0700 (PDT) X-Received: by 10.60.115.68 with SMTP id jm4mr2868715oeb.45.1396486888385; Wed, 02 Apr 2014 18:01:28 -0700 (PDT) Return-Path: Received: from rubyforge.org ([50.56.192.79]) by mx.google.com with ESMTP id l9si481764oex.195.2014.04.02.18.01.28 for ; Wed, 02 Apr 2014 18:01:28 -0700 (PDT) Received-SPF: pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 50.56.192.79 as permitted sender) client-ip=50.56.192.79; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 50.56.192.79 as permitted sender) smtp.mail=sup-talk-bounces@rubyforge.org; dkim=neutral (body hash did not verify) header.i=@gmail.com Received: from localhost.localdomain (localhost [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id CA8222E192; Thu, 3 Apr 2014 01:01:27 +0000 (UTC) Received: from mail-qc0-f179.google.com (mail-qc0-f179.google.com [209.85.216.179]) by rubyforge.org (Postfix) with ESMTP id 74DBB2E183 for ; Thu, 3 Apr 2014 01:00:27 +0000 (UTC) Received: by mail-qc0-f179.google.com with SMTP id m20so1113379qcx.24 for ; Wed, 02 Apr 2014 18:00:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:content-type; bh=A6rMfkI4xpjEtNpF9YsfjcyxeagyaqNNGFjbSvLJA20=; b=Qb/NhWS0vJzf0DKObhoQLC98nt8tQ//su/PSLG8CBmOZQ20IKO115F3xg0okAeHDp7 k9avM+3EuQ2NA5DzlDhqwcAK37BLmfg1iYCV/zho/H3clRzLE1JoZa4V0zuEnlpFviek yBBZOiRhLpTBo9JrcEW1GlW4Ft+AldeGVV1xlfHUAiMUmOM1uxG/FWv2VLG8l4pqEbCP cWVAkjm5hzhO/r3S126MWhjLOsBtkSIau/vh7K1o5XYxcEibCi0zbeF/YPTmCoHQKBLV pmUFQBw04Hu8IzN2f1HbUWhP5VHcjE4n9Tn9PmtfdbIyfcO9NRo9IZ7jmpb4M7LC2W4M sQZQ== X-Received: by 10.224.60.71 with SMTP id o7mr4272991qah.38.1396486827029; Wed, 02 Apr 2014 18:00:27 -0700 (PDT) MIME-Version: 1.0 Received: by 10.140.40.84 with HTTP; Wed, 2 Apr 2014 18:00:06 -0700 (PDT) In-Reply-To: <1395733057-sup-3470@qwerzila> References: <1395733057-sup-3470@qwerzila> From: James Pearson Date: Wed, 2 Apr 2014 18:00:06 -0700 X-Google-Sender-Auth: oMZqUxF5vnumXpLsohxWuF8O61E Message-ID: To: sup-talk Subject: Re: [sup-talk] Getting GPG working in Sup X-BeenThere: sup-talk@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: User & developer discussion of Sup List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org On Tue, Mar 25, 2014 at 12:44 AM, Gaute Hope wrote: > I'm using 2.0.5. What is the output of `rake test` in sup.git? It runs > through a few gpg-tests as well. After installing 'rr', this gave me the message WARNING: No crypto set up, crypto will not be tested. Reason: ["Environment variable 'GPG_AGENT_INFO' not set, is gpg-agent running?", "If gpg-agent is running, try $ export `cat ~/.gpg-agent-info`"] I hadn't realized that gpg-agent was a required thing. :3 So, I did this: https://github.com/sup-heliotrope/sup/wiki/gpg#using-pinentry-curses-gpg-agent-without-a-new-graphical-window and this: http://www.gnupg.org/documentation/manuals/gnupg/Invoking-GPG_002dAGENT.html and now I think things are hunky-dory. Thanks for the help! _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk