Hi Josselin,
first of all, sorry for the confusion: I'm still learning... and I'm
probably still using bad terminilogy from a Guix/Guile developer POV.
Josselin Poiret writes:
> Giovanni Biscuolo writes:
>
>> Sorry I don't understand the problem, could you expand please?
>>
>> The guix (and da
"guix import" seems to have issues when importing text encoded in some
non-ascii characters (or at least in Chinese).
As an example to reproduce, this is the output generated by "guix import
pypinyin":
```
(package
(name "python-pypinyin")
(version "0.50.0")
(source
(origin
(metho
In the guix/scripts/system.scm file we do not check the value while parsing the
flag:
--8<---cut here---start->8---
(option '("on-error") #t #f
(lambda (opt name arg result)
(alist-cons 'on-error (string->symbol arg)
res
Hello,
I think this can be closed as it was my mistake as some package
installed with pip
installed OpenCV and Python was picking it up by mistake, sorry for the noise.
However, I came up with a patch to propagate python-numpy as it is required by
OpenCV.
--
Jean-Pierre De Jesus DIAZ
Foundation
* gnu/packages/image-processing.scm (opencv): Move python-numpy from
INPUTS to PROPAGATED-INPUTS.
Change-Id: If4f0c8fa0cf41594a2c63f3e9f271987aa730af2
---
gnu/packages/image-processing.scm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gnu/packages/image-processing.scm
b/gnu
This issue was fixed with commit 6b6fb7872486, "gnu: glibc: Build with
'--strip-debug' instead of '--strip-all'."
--
Simon South
si...@simonsouth.net
When starting the ren'py launcher on version Ren'Py 8.2.0.24012702,
currently my guix channel is on commit
5d2302a1959d09e6d5a5f02ac199458095847a82, the program crashes with the
following error:
Full traceback:
File
"/gnu/store/2m851i42kc8i929rfhrn6w545w6a94lz-python-renpy-8.2.0/lib/python3.10/
I am running into this same issue on other cl packages as well.
Sergey,
I believe you intended a related message for the debbugs service, but only sent
the message to my mail address. I am unsure and want to avoid showing
impoliteness, I rephrased your message a bit below. Thank you,
Chris
---
the highlight error goes away after copying th
The linux-libre 6.7.x package contains ... as far as I can tell, no
supported arm64/aarch64 platforms! This is a pretty significant
regression from the linux-libre 6.6.x packaging!
This appears to have been introduced in
95a3aaf7ad37bb0717f2c9e3faf6f636b586d133
Unfortunately it is all too easy to
On 2023-06-24, Alan & Kim Zimmerman wrote:
> I took a look at this, and the problem seems to be that the cwd ends up
> different from before, so all the file operations fail.
>
> It needs (chdir "../nncp-7.5.0") in the 'go-unpack section.
>
> Attached is a patch that does this, if it works via gmai
On 2024-02-07, Vagrant Cascadian wrote:
> On 2023-06-24, Alan & Kim Zimmerman wrote:
>> I took a look at this, and the problem seems to be that the cwd ends up
>> different from before, so all the file operations fail.
>>
>> It needs (chdir "../nncp-7.5.0") in the 'go-unpack section.
>>
>> Attached
Hi Vagrant,
Vagrant Cascadian writes:
> [[PGP Signed Part:Undecided]]
> The linux-libre 6.7.x package contains ... as far as I can tell, no
> supported arm64/aarch64 platforms! This is a pretty significant
> regression from the linux-libre 6.6.x packaging!
I'll generate a new arm/arm64 config
13 matches
Mail list logo