all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Tomáš Čech" <sleep_walker@gnu.org>
To: guix-devel@gnu.org
Subject: Re: Help with Perl security update
Date: Mon, 25 Jul 2016 23:23:37 +0200	[thread overview]
Message-ID: <20160725212337.hd2d75pz5rls2w5r@venom> (raw)
In-Reply-To: <20160725200009.GA1175@jasmine>

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

On Mon, Jul 25, 2016 at 04:00:09PM -0400, Leo Famulari wrote:
>I'm trying to patch our Perl package against CVE-2016-1238 and
>CVE-2016-6185:
>
><https://www.debian.org/security/2016/dsa-3628>
>
>This patch uses a graft to apply new patches which are composed of
>commits from the 'maint-5.22' branch of
><http://perl5.git.perl.org/perl.git>.
>
>Unfortunately, some of the changes related to CVE-2016-1238 don't apply
>to our Perl source code. There are several '.rej' files that look like
>this:
>
>--- dist/PathTools/lib/File/Spec.pm
>+++ dist/PathTools/lib/File/Spec.pm
>@@ -3,7 +3,7 @@ package File::Spec;
> use strict;
> use vars qw(@ISA $VERSION);
>
>-$VERSION = '3.56_01';
>+$VERSION = '3.56_02';
> $VERSION =~ tr/_//;
>
> my %module = (MacOS   => 'Mac',
>
>Any advice?

This looks like we're missing some patches. My guess is that this is
consequence of the fact that upstream is on 5.22.2 already and we're
on 5.22.1. I'm not sure what value to choose here as the result won't
be neither 3.56_01 nor 3.56_02. Maybe add extra suffix?

Or we can just skip bfe2dd1e9c3296bebf3ab9adc2ca48d3eb8d105d and let
the version same. Someone with deeper perl experience should decide.

I just verified that source code in 5.22.2 has the version strings
patch expects (I haven't checked them all).

S_W

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-07-25 21:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-25 20:00 Help with Perl security update Leo Famulari
2016-07-25 21:23 ` Tomáš Čech [this message]
2016-07-29 21: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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160725212337.hd2d75pz5rls2w5r@venom \
    --to=sleep_walker@gnu.org \
    --cc=guix-devel@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 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.