unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 27263-done@debbugs.gnu.org
Subject: bug#27263: [PATCH 2/2] gnu: perl: Fix CVE-2017-6512 in File::Path.
Date: Wed, 7 Jun 2017 12:17:53 -0400	[thread overview]
Message-ID: <20170607161752.GA5750@jasmine> (raw)
In-Reply-To: <87shjc66z2.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 675 bytes --]

On Wed, Jun 07, 2017 at 01:18:09AM +0200, Ludovic Courtès wrote:
> Leo Famulari <leo@famulari.name> skribis:
> 
> > * gnu/packages/perl.scm (perl)[replacement]: New field.
> > (perl/fixed): New variable.
> > * gnu/packages/patches/perl-file-path-CVE-2017-6512.patch: New file.
> > * gnu/local.mk (dist_patch_DATA): Add it.
> 
> OK too.
> 
> I suppose we’ll have to apply it in core-updates too, right?

And, done as c67d587f94173fd42d65097165afc5c512935646.

I tested that this packaging of Perl 5.26.0 builds on master, then I
"ported" the package to core-updates. I don't have the resources to
build the Perl package on core-updates in a timely manner.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2017-06-07 16:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-06  3:01 bug#27263: Perl CVE-2017-6512 Leo Famulari
2017-06-06  3:04 ` bug#27263: [PATCH 1/2] gnu: perl-file-path: Update to 2.13 Leo Famulari
2017-06-06  3:04   ` bug#27263: [PATCH 2/2] gnu: perl: Fix CVE-2017-6512 in File::Path Leo Famulari
2017-06-06 23:18     ` Ludovic Courtès
2017-06-07 15:40       ` Leo Famulari
2017-06-07 16:17       ` Leo Famulari [this message]
2017-06-08 12:07         ` Ludovic Courtès
2017-06-06 23:16   ` bug#27263: [PATCH 1/2] gnu: perl-file-path: Update to 2.13 Ludovic Courtès
2017-06-06 18:53 ` bug#27263: Perl CVE-2017-6512 Marius Bakke

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=20170607161752.GA5750@jasmine \
    --to=leo@famulari.name \
    --cc=27263-done@debbugs.gnu.org \
    --cc=ludo@gnu.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 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).