On Sun, Apr 16, 2023, 01:37 Csepp wrote:
>
> Théo Maxime Tyburn writes:
>
> > Csepp writes:
> >
> >> Théo Maxime Tyburn writes:
> >>
> >>> ```
> >>> checking for OpenEXR >= 1.0.6... no
> >>> [...]
> >>> Delegate library configuration:
> >>> OpenEXR --with-openexr=yes no
>
Théo Maxime Tyburn writes:
> Csepp writes:
>
>> Théo Maxime Tyburn writes:
>>
>>> ```
>>> checking for OpenEXR >= 1.0.6... no
>>> [...]
>>> Delegate library configuration:
>>> OpenEXR --with-openexr=yes no
>>> ```
>>
>> If we are going by semver, then 1.0.6 is incompatible
Hello,
Am Sat, Apr 15, 2023 at 06:25:52PM + schrieb Kaelyn:
> I tried to update the package definition to be able to build from git but it
> became a much bigger rabbit hole than I have the energy for at the moment. I
> also tried to cherry-pick the commit from the merge request without
Csepp writes:
> Théo Maxime Tyburn writes:
>
>> ```
>> checking for OpenEXR >= 1.0.6... no
>> [...]
>> Delegate library configuration:
>> OpenEXR --with-openexr=yes no
>> ```
>
> If we are going by semver, then 1.0.6 is incompatible with 3.x. Maybe
> it expects an older
Am Sat, Apr 15, 2023 at 01:20:07PM +0200 schrieb Andreas Enge:
> The recent master/staging merge apparently broke python-pytest even on
> x86_64, see message below, which should be sorted out first.
With pytest repaired, your patch builds numpy successfully on both x86
architectures. Pushed,
Am Sat, Apr 15, 2023 at 09:59:00PM +0200 schrieb Andreas Enge:
> I will try to revert the commit that updates pytest and apply yours instead
> to see if this is the safer route.
It was, in this way I get a working python-numpy on x86_64 and i686.
I think we should be rather conservative now. The
Am Sat, Apr 15, 2023 at 09:52:50PM +0200 schrieb Andreas Enge:
> when looking at the powerpc machines at
>https://ci.guix.gnu.org/workers
> one sees that only one slot out of two is used on guixp9, and nothing
> at all on sjd-p9.
It is definitely a thing with cuirass. When I manually start a
Hello Josselin,
Am Sat, Apr 15, 2023 at 04:08:18PM +0200 schrieb Josselin Poiret:
> This should also fix it without bumping python-pytest to a new version (since
> it
> has so many dependents, don't want to introduce new breakage now).
in the meantime Maxim updated pytest to the latest version,
Hello,
when looking at the powerpc machines at
https://ci.guix.gnu.org/workers
one sees that only one slot out of two is used on guixp9, and nothing
at all on sjd-p9.
Could someone with knowledge how cuirass is set up on berlin have a look,
please? In the meantime, I will just connect
--- Original Message ---
On Saturday, April 15th, 2023 at 4:37 PM, Kaelyn
wrote:
>
>
> Hi,
>
> --- Original Message ---
> On Saturday, April 15th, 2023 at 10:43 AM, Andreas Enge andr...@enge.fr wrote:
>
> > Am Fri, Apr 14, 2023 at 08:51:18PM -0400 schrieb Maxim Cournoyer:
>
Hi,
--- Original Message ---
On Saturday, April 15th, 2023 at 10:43 AM, Andreas Enge wrote:
>
> Am Fri, Apr 14, 2023 at 08:51:18PM -0400 schrieb Maxim Cournoyer:
>
> > None, but are there wget uptsream reports about the problem?
>
>
> I do not see anything at
>
--- Original Message ---
On Saturday, April 15th, 2023 at 2:08 PM, Josselin Poiret
wrote:
>
> * gnu/packages/patches/pytest-fix-unstrable-exception-test.patch: Add new
> patch from upstream.
> * gnu/packages/check.scm (python-pytest): Use it.
> * gnu/local.mk (dist_patch_DATA):
* gnu/packages/patches/pytest-fix-unstrable-exception-test.patch: Add new
patch from upstream.
* gnu/packages/check.scm (python-pytest): Use it.
* gnu/local.mk (dist_patch_DATA): Register it.
---
Hey Andreas and Kaelyn,
This should also fix it without bumping python-pytest to a new version (since
Hey!
The bordeaux build farm and substitute server has been operating for
around 2 years now, and during that time the storage for the nars has
changed a few times.
At first they were stored on bayfront, but when it was low on space
there was a switch to storing them on a different machine
Am Sat, Apr 15, 2023 at 01:20:07PM +0200 schrieb Andreas Enge:
> The recent master/staging merge apparently broke python-pytest even on
> x86_64, see message below, which should be sorted out first.
I tried to update to the more recent versions 7.2.2 and 7.3.1, but the
recipe does not work out of
Am Fri, Apr 14, 2023 at 08:05:46PM + schrieb Kaelyn:
> I just sent in https://issues.guix.gnu.org/62843 to disable the two tests for
> i686 and armhf (disabling TestKind.test_all for armhf might not be needed,
> but the Gentoo package definition suggests the huge array test will fail for
>
Am Fri, Apr 14, 2023 at 08:51:18PM -0400 schrieb Maxim Cournoyer:
> None, but are there wget uptsream reports about the problem?
I do not see anything at
https://gitlab.com/gnuwget/wget
Andreas
Hello Lars,
Am Fri, Apr 14, 2023 at 08:40:32PM +0200 schrieb Lars-Dominik Braun:
> do you have a log file indicating where exactly it failed?
here is one:
http://localhost:8081/build/804101/log/raw
There is consistently this timeout after printing the lines
=> galois_raytrace(normal)
Am Fri, Apr 14, 2023 at 03:29:01PM -0400 schrieb Maxim Cournoyer:
> The staging branch has been merged to master.
Thanks and congratulations!
> Should we remove the branch from Cuirass and Guix, knowing that teams
> is the way going forward?
Definitely! I will go ahead and do so. If we want a
Am Sat, Apr 15, 2023 at 09:59:20AM +0200 schrieb Josselin Poiret:
> Good question. My personal opinion on this is that fixes for
> dependencies that impact multiple packages could be reviewed on the spot
> while leaf packages could wait until later.
I feel more adventurous. Since anyway we are
Hi John,
John Kehayias writes:
> Question on procedure: are we going to be posting every patch to guix-patches
> and waiting
> for QA to build? Or only for not trivial (whatever that means) patches? I
> guess I'm asking
> if this will be a sort of sprint weekend and larger changes/cleanup in
21 matches
Mail list logo
