From: ng0 <ng0@we.make.ritual.n0.is>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH][core-updates] gnu: gnupg, libgpg-error updates rebased
Date: Sat, 20 Aug 2016 08:41:42 +0000 [thread overview]
Message-ID: <877fbbg7cp.fsf@we.make.ritual.n0.is> (raw)
In-Reply-To: <87h9ahb5uy.fsf@we.make.ritual.n0.is>
[-- Attachment #1: Type: text/plain, Size: 1157 bytes --]
ng0 <ng0@we.make.ritual.n0.is> writes:
> Leo Famulari <leo@famulari.name> writes:
>
>> On Thu, Aug 18, 2016 at 07:27:14PM +0000, ng0 wrote:
>>> Leo Famulari <leo@famulari.name> writes:
>>>
>>> > On Thu, Aug 18, 2016 at 06:34:24PM +0000, ng0 wrote:
>>> >> GnuPG 2.1.15 has just been released, but please apply this patch, I'll
>>> >> have 2.1.15 ready later and send a separate patch of it based on this one.
>>> >
>>> > I applied your update patch for libgpg-error, but I rewrote the gnupg
>>> > update patch from scratch.
>>> >
>>> > So, no need for a "gnupg: Update to 2.1.15" patch. It's already done.
>>>
>>> I'm not so sure. My build of it failed when the tests happened, which is
>>> why my patch included a fix for that:
>>> https://lists.gnu.org/archive/html/guix-devel/2016-08/msg01276.html
>>
>> Ah, you're right. Can you send a patch for core-updates?
>
> http://lists.gnu.org/archive/html/guix-devel/2016-08/msg01276.html
> includes this already.
Disregard the previous message, this one applies on top of your changes
on core-updates. It has not been run, I'm starting the build now, but it
is the same as the original gnupg update I had.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-gnu-gnupg-Fix-test-failures.patch --]
[-- Type: text/x-patch, Size: 1177 bytes --]
From 3aec89f0444bd1e75f8dfa945e586a79790d254d Mon Sep 17 00:00:00 2001
From: ng0 <ng0@we.make.ritual.n0.is>
Date: Sat, 20 Aug 2016 08:37:22 +0000
Subject: [PATCH] gnu: gnupg: Fix test failures.
* gnu/packages/gnupg.scm (gnupg)[arguments]: Set $HOME before 'check.
---
gnu/packages/gnupg.scm | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/gnu/packages/gnupg.scm b/gnu/packages/gnupg.scm
index 27db5c3..52a9fc5 100644
--- a/gnu/packages/gnupg.scm
+++ b/gnu/packages/gnupg.scm
@@ -247,7 +247,13 @@ compatible to GNU Pth.")
(lambda _
(substitute* (find-files "tests" ".\\.scm$")
(("/usr/bin/env gpgscm")
- (string-append (getcwd) "/tests/gpgscm/gpgscm"))))))))
+ (string-append (getcwd) "/tests/gpgscm/gpgscm")))))
+ (add-before 'check 'set-home
+ ;; Some tests require write access to $HOME, otherwise leading to
+ ;; 'failed to create directory /homeless-shelter/.asy' error.
+ (lambda _
+ (setenv "HOME" "/tmp")
+ #t)))))
(home-page "https://gnupg.org/")
(synopsis "GNU Privacy Guard")
(description
--
2.9.3
[-- Attachment #3: Type: text/plain, Size: 70 bytes --]
--
ng0
For non-prism friendly talk find me on http://www.psyced.org
next prev parent reply other threads:[~2016-08-20 8:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-18 15:33 [PATCH][core-updates] gnu: gnupg, libgpg-error updates rebased ng0
2016-08-18 18:34 ` ng0
2016-08-18 18:54 ` Leo Famulari
2016-08-18 19:27 ` ng0
2016-08-19 4:55 ` Leo Famulari
2016-08-19 7:00 ` ng0
2016-08-20 8:41 ` ng0 [this message]
2016-08-20 9:27 ` ng0
2016-08-21 22:09 ` 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=877fbbg7cp.fsf@we.make.ritual.n0.is \
--to=ng0@we.make.ritual.n0.is \
--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).