On Fri, Mar 03, 2017 at 10:28:55AM +0100, julien lepiller wrote:
> I think they are good now. How could I investigate glib's failure?
I typically investigate hangs by attaching to the guix-daemon as root
with `strace -f -p $(pgrep guix-daemon | head -n1)` to see what it's
doing.
The output is ext
Le 2017-03-02 18:18, Leo Famulari a écrit :
On Thu, Mar 02, 2017 at 05:55:30PM +0100, Marius Bakke wrote:
julien lepiller writes:
> Le 2017-03-01 16:34, julien lepiller a écrit :
>> I've "fixed" the glib failure by disabling a test. Attached are
>> patches I would like to see in core-updates.
On Thu, Mar 02, 2017 at 05:37:07PM +0100, julien lepiller wrote:
> From 10ab0fc95f83dbb291179cbf525d4bef196a827f Mon Sep 17 00:00:00 2001
> From: Julien Lepiller
> Date: Mon, 27 Feb 2017 11:09:11 +0100
> Subject: [PATCH 2/3] gnu: gd: Fix an issue with XBM decoding.
>
> * gnu/packages/patches/gd-p
On Thu, Mar 02, 2017 at 05:55:30PM +0100, Marius Bakke wrote:
> julien lepiller writes:
>
> > Le 2017-03-01 16:34, julien lepiller a écrit :
> >> I've "fixed" the glib failure by disabling a test. Attached are
> >> patches I would like to see in core-updates. If it's too late to add
> >> the patc
julien lepiller writes:
> Le 2017-03-01 16:34, julien lepiller a écrit :
>> I've "fixed" the glib failure by disabling a test. Attached are
>> patches I would like to see in core-updates. If it's too late to add
>> the patch for gd, then I would like to keep gd-for-php. This time I've
>> tested t
Le 2017-03-01 16:34, julien lepiller a écrit :
I've "fixed" the glib failure by disabling a test. Attached are
patches I would like to see in core-updates. If it's too late to add
the patch for gd, then I would like to keep gd-for-php. This time I've
tested them and php works.
A better version
On Wed, Mar 01, 2017 at 04:34:25PM +0100, julien lepiller wrote:
> I've "fixed" the glib failure by disabling a test. Attached are patches I
> would like to see in core-updates. If it's too late to add the patch for gd,
> then I would like to keep gd-for-php. This time I've tested them and php
> wo
On Wed, Mar 01, 2017 at 05:25:46PM +0100, Marius Bakke wrote:
> julien lepiller writes:
>
> > I've "fixed" the glib failure by disabling a test. Attached are patches
> > I would like to see in core-updates. If it's too late to add the patch
> > for gd, then I would like to keep gd-for-php. This
julien lepiller writes:
> I've "fixed" the glib failure by disabling a test. Attached are patches
> I would like to see in core-updates. If it's too late to add the patch
> for gd, then I would like to keep gd-for-php. This time I've tested them
> and php works.
I did not get a substitute for
I've "fixed" the glib failure by disabling a test. Attached are patches
I would like to see in core-updates. If it's too late to add the patch
for gd, then I would like to keep gd-for-php. This time I've tested them
and php works.
From 300af3fb262a31958f26aeac5eef33e376eda604 Mon Sep 17 00:00:00
On Mon, 27 Feb 2017 16:09:58 -0500
Leo Famulari wrote:
> On Mon, Feb 27, 2017 at 11:24:42AM +0100, julien lepiller wrote:
> > I think php-for-gd would break with the new version (it would fail
> > to apply the patches), so I'd like to get rid of it, and use our gd
> > package instead.
>
> Okay
Le 2017-02-26 21:46, Leo Famulari a écrit :
Hi Julien,
Libgd is updated to 2.2.4 on the core-updates branch.
Can you take a look and decide what to do with gd-for-php on that
branch?
I think php-for-gd would break with the new version (it would fail to
apply the patches), so I'd like to get
Hi Julien,
Libgd is updated to 2.2.4 on the core-updates branch.
Can you take a look and decide what to do with gd-for-php on that
branch?
13 matches
Mail list logo
