On Wed, Nov 29, 2023 at 01:27:15PM +, jgart wrote:
> Hi Guixers,
>
> Does anyone happen to know why sbcl-py4cl doesn't appear in this output?
>
> guix refresh --list-dependent python-numpy
>
>
(ins)efraim@3900XT ~$ guix refresh -l sbcl-py4cl
A single dependent package:
Hi,
On mer., 29 nov. 2023 at 13:27, "jgart" wrote:
> Does anyone happen to know why sbcl-py4cl doesn't appear in this output?
>
> guix refresh --list-dependent python-numpy
>
> Building the following 1490 packages would ensure 3164 dependent packages are
> rebuilt:
I guess sbcl-py4cl is not
Hey,
I have a RISC-V board that is hooked up to the bordeaux build farm, and
there is another board connected, although there's some issues with the
connection/agent.
1 to 2 boards though isn't enough to get good substitute availability
and build packages for patches and branches though.
Maxim Cournoyer skribis:
> Hi Simon,
>
> Simon Tournier writes:
>
>> Hi,
>>
>> On mer., 22 nov. 2023 at 19:27, Ludovic Courtès wrote:
>>
>>> For long-term storage though, we could choose to keep lzip only (because
>>> it compresses better). Not something we can really do with the current
>>>
Hi Simon,
Simon Tournier writes:
> Hi,
>
> On mer., 22 nov. 2023 at 19:27, Ludovic Courtès wrote:
>
>> For long-term storage though, we could choose to keep lzip only (because
>> it compresses better). Not something we can really do with the current
>> ‘guix publish’ setup though.
>
> It
> > the downside of generating countless macros is that they won't show up
> > in backtraces, and they cannot be found when grep'ping the codebase,
> > and as such make the codebase much less approachable.
>
>
> Reading your words really helped me feel that I'm not alone. You more or
> less
Hi Maxim,
I am late to the party and maybe it is already solved.
On ven., 06 oct. 2023 at 22:13, Maxim Cournoyer
wrote:
> I've narrowed the problem down to #$(this-package-input "subversion");
> the following diff allows the build to start:
[...]
> I'm puzzled as to why this happens. Would
