From: Jan Nieuwenhuizen <janneke@gnu.org>
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org
Subject: Re: 01/01: Merge branch 'staging'
Date: Sat, 09 Feb 2019 18:52:37 +0100 [thread overview]
Message-ID: <87y36ohmsa.fsf@gnu.org> (raw)
In-Reply-To: <87a7j5f1d0.fsf@netris.org> (Mark H. Weaver's message of "Sat, 09 Feb 2019 10:05:36 -0500")
Mark H Weaver writes:
Hi Mark, Ludo',
>> commit 50a93adc05b611836e740c4b55571890f4c6770a
>> Merge: 722ac64 69fb26d
>> Author: Ludovic Courtès <ludo@gnu.org>
>> Date: Sat Feb 9 15:14:59 2019 +0100
>>
>> Merge branch 'staging'
>
> I asked Hydra to evaluate 'master' after this commit, and it failed.
> See below for the evaluator.log output.
I tried to reproduce this, by building ghostscript locally, but failed.
Then I noticed that this string
> srfi/srfi-1.scm:592:17: In procedure map1:
> Throw to key `srfi-34' with args `(#<condition &message [message:
> "ghostscript-CVE-2018-16509.patch: patch not found"] 42fd960>)'.
does not exist in master
--8<---------------cut here---------------start------------->8---
18:51:24 janneke@dundal:~/src/guix/master
$ git show HEAD | head -2
commit 50a93adc05b611836e740c4b55571890f4c6770a
Merge: 722ac64cd7 69fb26d4f5
18:51:52 janneke@dundal:~/src/guix/master
$ git grep ghostscript-CVE-2018-16509.patch
[1]18:51:56 janneke@dundal:~/src/guix/master
--8<---------------cut here---------------end--------------->8---
...what's going on?
janneke
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com
next prev parent reply other threads:[~2019-02-09 17:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190209142647.10191.98883@vcs0.savannah.gnu.org>
[not found] ` <20190209142650.14A42204D2@vcs0.savannah.gnu.org>
2019-02-09 15:05 ` 01/01: Merge branch 'staging' Mark H Weaver
2019-02-09 17:52 ` Jan Nieuwenhuizen [this message]
2019-02-13 22:39 ` Ludovic Courtès
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y36ohmsa.fsf@gnu.org \
--to=janneke@gnu.org \
--cc=guix-devel@gnu.org \
--cc=mhw@netris.org \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.