From: ludo@gnu.org (Ludovic Courtès)
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: ed: Replace with 1.14.1 [fixes security issues].
Date: Fri, 13 Jan 2017 14:07:31 +0100 [thread overview]
Message-ID: <87r347rtv0.fsf@gnu.org> (raw)
In-Reply-To: <20170112221723.GA20450@jasmine> (Leo Famulari's message of "Thu, 12 Jan 2017 17:17:23 -0500")
Leo Famulari <leo@famulari.name> skribis:
> On Thu, Jan 12, 2017 at 10:56:51PM +0100, Marius Bakke wrote:
>> Leo Famulari <leo@famulari.name> writes:
>>
>> > On Thu, Jan 12, 2017 at 09:13:53PM +0100, Marius Bakke wrote:
>> >> * gnu/packages/ed.scm (ed-1.14.1): New variable.
>> >> (ed)[replacement]: New field.
>> >
>> > Can you add a comment with a link to the bug report?
>> >
>> > https://lists.gnu.org/archive/html/bug-ed/2017-01/msg00000.html
>>
>> Good find. I wonder, was this issue only present in the unreleased
>> 1.14.0? I can't reproduce it with the current Guix version.
>
> Good catch; I can only reproduce it with 1.14, and the ed maintainer
> points out that it was introduced in 1.14.
>
>> I'll wait and see what the response on oss-sec is. Maybe we can just
>> push the update to core-updates.
>
> I think it's fine for core-updates.
With 200 dependent packages, it could even go to ‘master’.
https://lists.gnu.org/archive/html/guix-devel/2016-10/msg00933.html
Ludo’.
next prev parent reply other threads:[~2017-01-13 13:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-12 20:13 [PATCH] gnu: ed: Replace with 1.14.1 [fixes security issues] Marius Bakke
2017-01-12 20:53 ` John Darrington
2017-01-12 20:58 ` Marius Bakke
2017-01-12 21:50 ` Leo Famulari
2017-01-12 21:56 ` Marius Bakke
2017-01-12 22:17 ` Leo Famulari
2017-01-12 22:30 ` Marius Bakke
2017-01-13 13:07 ` Ludovic Courtès [this message]
2017-01-13 13:20 ` Marius Bakke
2017-01-13 17:44 ` Mark H Weaver
2017-01-14 17:50 ` 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=87r347rtv0.fsf@gnu.org \
--to=ludo@gnu.org \
--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 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.