unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] Update gd and php
Date: Fri, 20 Jan 2017 22:25:40 +0100	[thread overview]
Message-ID: <87pojhmnjf.fsf@gnu.org> (raw)
In-Reply-To: <20170120173002.GA29902@jasmine> (Leo Famulari's message of "Fri, 20 Jan 2017 12:30:02 -0500")

Leo Famulari <leo@famulari.name> skribis:

> On Fri, Jan 20, 2017 at 05:12:46PM +0100, julien lepiller wrote:
>> How do you make php use gd-2.2.4, then? It needs to be updated too because
>> the security issues with gd are still present in our current php package.
>
> It seems that gd-for-php gets replaced by gd-2.2.4 now:
>
> $ ./pre-inst-env guix build -e '(@@ (gnu packages php) gd-for-php)'
> /gnu/store/xg2r8hk5axfq7xk1aj9ql5ncgkpnh0vk-gd-2.2.4
>
> But, building PHP with --dry-run implies that gd@2.2.3 will be used.
>
> I think that we need to set (replacement #f) in gd-for-php, so that PHP
> is built with gd@2.2.3, which will then be grafted to refer to gd-2.2.4
> in the built output of PHP.
>
> I'm a little unsure. Does anyone have advice?

If gd-for-php has #f as its replacement, then nothing will be grafted to
replace it.

Or am I missing something?

Ludo’.

  reply	other threads:[~2017-01-20 21:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-19 21:19 [PATCH] Update gd and php Julien Lepiller
2017-01-20  5:53 ` Leo Famulari
2017-01-20 15:33   ` Leo Famulari
2017-01-20 16:12     ` julien lepiller
2017-01-20 17:30       ` Leo Famulari
2017-01-20 21:25         ` Ludovic Courtès [this message]
2017-01-21  1:22           ` Leo Famulari
2017-01-26 10:15             ` Ludovic Courtès
2017-01-27 19:43               ` Leo Famulari
2017-01-27 23:04                 ` 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

  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=87pojhmnjf.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 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).