[bug#72962] php-8.3.10 build failure

[bug#72962] php-8.3.10 build failure

[Rutherther via Guix-patches via]

Hello everyone,

note that the linked issue solves this only partially.
It fixes gd itself, but then there are still three
failing tests in php.

I suggest this as current workaround locally:
---
(use-modules
 (guix packages)
 (gnu packages gd)
 (gnu packages php))

(define gd-fixed
  (package/inherit gd
    (name "gd-fixed")
    (propagated-inputs
     (package-inputs gd))))

(define php
  (package/inherit php
    (inputs (modify-inputs (package-inputs php)
              (replace "gd" gd-fixed)))))

php

[bug#72962] php-8.3.10 build failure

[guix-patches--- via]

Carlo Zancanaro <carlo@zancanaro.id.au> writes:

> * gnu/packages/php.scm (php)[arguments]: Delete three tests that are known to
> fail.
>

This is my first time composing a patch review — I am not sure if I am
doing it correctly.

I attempted to build php with the following command:
=
guix build php --with-patch=gd=patch-1.txt --with-patch=php=patch-2.txt
=

The text files are files saved by using the “download” option of the web
interface of Guix Issues.  My understanding is that the patch to gd
applies cleanly, but the patch to php does not:

=
source is at 'php-8.3.10'
applying '/gnu/store/f2zxspb49cbcmcla3mbjrikl48kmbf52-patch-2.txt'...
can't find file to patch at input line 13
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|* gnu/packages/php.scm (php)[arguments]: Delete three tests that are known to
|fail.
|
|Change-Id: Ib684328654c75f37111d252fb0f9fb3356daff9a
|---
| gnu/packages/php.scm | 7 +++++++
| 1 file changed, 7 insertions(+)
|
|diff --git a/gnu/packages/php.scm b/gnu/packages/php.scm
|index 8f879dbdca..ce7458d0e5 100644
|--- a/gnu/packages/php.scm
|+++ b/gnu/packages/php.scm
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
patch unexpectedly ends in middle of line
=

Is this helpful?

[bug#72962] php-8.3.10 build failure

[guix-patches--- via]

Carlo Zancanaro <carlo@zancanaro.id.au> writes:

>> I attempted to build php with the following command:
>> =
>> guix build php --with-patch=gd=patch-1.txt --with-patch=php=patch-2.txt
>> =
>
> You should be able to apply them in a fresh clone of the repository with
> "git am $patch-name". To build, you can follow the instructions in the
> manual "(guix) Building from Git". After that, you can build PHP with
> these patches with "./pre-inst-env guix build php".
>

I had a guix clone from previous attempts to patch things, so I
proceeded to apply the patches.  Patch 1 returned a message along the
lines (translation) of "apply: * gnu/packages/gd.scm (gd): Change inputs
to propagated-inputs".  However,
=
LC_ALL=C git am ../Downloads/patch-2.txt
Patch format detection failed.
=

[bug#72962] php-8.3.10 build failure

[guix-patches--- via]

Upon further inspection, I noticed the second patch is missing the
From: <email> header.  I copied it from the first patch and it applied.

The build is now in progress on my slow laptop, so I am sending this
report immediately.

[bug#72962] php-8.3.10 build failure

[guix-patches--- via]

The build completed and passed all the tests.

Is this the right moment to say reviewed-looks-good? Would I do it by
writing the usertag followed by thanks in the beginning of the message?
Or am I confusing concepts?

[bug#72962] php-8.3.10 build failure

[Nathan Dehnel]

ping