bug#64981: GTK4 applications broken (missing libGLESv2)

2023-08-18 Thread 宋文武 via Bug reports for GNU Guix
iyzs...@envs.net writes:

> * gnu/packages/gl.scm (libepoxy)[arguments]<#:phases>:
> Hardcode paths to libGLESv1_CM.so.1 and libGLESv2.so.2.

Hello, since we already hardcode paths for libGL, adding libGLES seems
reasonable.

Have test it though, because on my machine (kwin in wayland) it seems
GTK4 applications will use GL renderer instead of GLES.





bug#64981: [PATCH] gnu: libepoxy: Hardcode paths to GLES libraries.

2023-08-18 Thread iyzsong--- via Bug reports for GNU Guix
From: 宋文武 

Fixes .

* gnu/packages/gl.scm (libepoxy)[arguments]<#:phases>:
Hardcode paths to libGLESv1_CM.so.1 and libGLESv2.so.2.
---
 gnu/packages/gl.scm | 10 +++---
 1 file changed, 7 insertions(+), 3 deletions(-)

diff --git a/gnu/packages/gl.scm b/gnu/packages/gl.scm
index b53b42a9ba..f662f0f7da 100644
--- a/gnu/packages/gl.scm
+++ b/gnu/packages/gl.scm
@@ -742,10 +742,14 @@ (define-public libepoxy
   #~(modify-phases %standard-phases
   (add-before 'configure 'patch-paths
 (lambda* (#:key inputs #:allow-other-keys)
-  (let ((mesa (dirname (search-input-file inputs "lib/libGL.so"
+  (let ((mesa-lib
+ (lambda (file)
+   (search-input-file inputs (string-append "lib/" 
file)
 (substitute* (find-files "." "\\.[ch]$")
-  (("libGL.so.1") (string-append mesa "/libGL.so.1"))
-  (("libEGL.so.1") (string-append mesa "/libEGL.so.1")
+  (("libGL.so.1") (mesa-lib "libGL.so.1"))
+  (("libEGL.so.1") (mesa-lib "libEGL.so.1"))
+  (("libGLESv1_CM.so.1") (mesa-lib "libGLESv1_CM.so.1"))
+  (("libGLESv2.so.2") (mesa-lib "libGLESv2.so.2")
 (build-system meson-build-system)
 (native-inputs
  (list pkg-config python))

base-commit: 597af70fd24eb85a85fa8c45008c9cfa241f4d0b
-- 
2.41.0






bug#64736: pipewire doesn't provide libspa-libcamera.so

2023-08-18 Thread 宋文武 via Bug reports for GNU Guix
Alexandre Hannud Abdo  writes:

> Uou, thank you. Let me know if and how I can help. Best, .~´

Hello, it should be fixed now.  Since commit
7d8ce0701e82cf984906980e240bbf67f4988426.

Closing,  thanks.





bug#63308: [BUG] python-pikepdf build broken

2023-08-18 Thread kiasoc5--- via Bug reports for GNU Guix
The build is broken because qpdf in Guix is too old (inferring this from 
https://github.com/pikepdf/pikepdf/issues/497#issuecomment-1646312997)


Therefore a qpdf upgrade would be required, which would involve a patch 
to core-updates.






bug#64557: (no subject)

2023-08-18 Thread Simon Tournier
Hi,

On Mon, 10 Jul 2023 at 15:44, Girish M  wrote:
> guix substitute: warning: while fetching 
> https://ci.guix.gnu.org/nar/zstd/vmq70gpqzdrd4ljbr1l9ap9pjvwn8dv0-perl-term-readkey-2.38:
>  
> server is somewhat slow
> guix substitute: warning: try `--no-substitutes' if the problem persists
> Backtrace:
> In ice-9/boot-9.scm:

[...]

> ./guix/store.scm:1417:15: In procedure loop:
> ERROR:
>    1. :
>    message: "some substitutes for the outputs of derivation 
> `/gnu/store/f74aip8bzq6axicf1ws1v8qcjivhw789-po4a-0.68.drv' failed 
> (usually happens due to networking issues); try `--fallback' to build 
> derivation from source "
>    status: 1
> guix pull: error: You found a bug: the program 
> '/gnu/store/m43d9r0zn4q4ifwd1bgfdm6pgdji4yrg-compute-guix-derivation'
> failed to compute the derivation for Guix (version: 
> "ef0a45c6413a35e0e7ee375cab2c6f7bc468ab5a"; system: "x86_64-linux";
> host version: "fcfdb8f05ed0228ede47e9d2a0de5b05b09dd7be"; pull-version: 1).

What is the bug about?  Could you give some context when that happens?


Cheers,
simon





bug#64571: harfbuzz package has a duplicated definition

2023-08-18 Thread Simon Tournier
Hi,

On Tue, 11 Jul 2023 at 11:15, Jean-Pierre De Jesus Diaz via Bug reports for GNU 
Guix  wrote:

> guix shell harfbuzz
> guix shell: warning: ambiguous package specification `harfbuzz'
> guix shell: warning: choosing harfbuzz@5.3.1 from gnu/packages/gtk.scm:252:2
>
> It may be as simple as removing harfbuzz-5 package definition but I'm not
> sure if that is correct,
> or if this is intended.

Done with commit 728ed83188846453f1319ea425847da8200a55a9 by Chris if I
read correctly.  Closing?

Cheers,
simon





bug#64760: make check fails on 182be30fb1a8b847c30492462ec22c08ec7a9849

2023-08-18 Thread Ludovic Courtès
Hello!

Pushed as 4b1fdd44ed87dc07d23cc9313a8b6b14d0646923!

Ludo’.





bug#64302: Guix derivation cannot be computed during pull

2023-08-18 Thread Ludovic Courtès
Hi,

Andreas Enge  skribis:

> It looks like 1GB of memory is not enough for "guix pull", which is
> not nice. Has this been addressed in later commits? Is there a known
> lower memory limit for using Guix?

This is terrible.  :-/

The culprit here is Guile, specifically its compiler and psyntax.  I
made some improvements to reduce its memory consumption in 3.0, but it’s
definitely not 2x or so unfortunately.  So, to be continued…

Ludo’.