gnu: linux-libre 6.12: Update to 6.12.17.
* gnu/packages/linux.scm (linux-libre-6.12-version): Update to 6.12.17.
(linux-libre-6.12-pristine-source, deblob-scripts-6.12): Update hashes.
Change-Id: I91ff54d2d604a7bf48e8b616cdd07f512dbce6a6
gnu: linux-libre: Update to 6.13.5.
* gnu/packages/linux.scm (linux-libre-6.13-version): Update to 6.13.5.
(linux-libre-6.13-pristine-source, deblob-scripts-6.13): Update hashes.
Change-Id: I7c9551603432394a7c845dba4e10ef7cc444f630
gnu: python-cfn-lint: Skip 2 more tests.
* gnu/packages/python-web.scm (python-cfn-lint) [arguments]
<test-flags>: Skip 2 more shaky tests.
Change-Id: Ib60bee902584e0d1fa36ea9f2a90fb62dd7b7c4c
gnu: godot: Update to 4.4.
* gnu/packages/game-development.scm (godot): Update to 4.4.
[source]: Update snippet to preserve jolt_physics and manifold.
[arguments]<#:phases>: Update scons-use-env phase to match upstream changes.
Change-Id: I7b4bd9557aeb24f2256ded3883ca7676b4a62a32
gnu: guix: Update to 1.4.0-34.5058b40.
* gnu/packages/package-management.scm (guix): Update to 1.4.0-34.5058b40.
Change-Id: I307c6aee6dd3486802fd608de40b02320b1360d8
gnu: swaynotificationcenter: Update to 0.10.1.
* gnu/packages/wm.scm (swaynotificationcenter): Update to 0.10.1.
[native-inputs]: Add sassc.
[inputs]: Add granite-6.
Change-Id: I395c7c6c7297dc310ff88e0c40b5294b963290f8
tests: publish: Constrain guix-publish thread use.
On systems with more than 64 processors. Otherwise starting so many threads
during the test will trip resource limits and lead to a spurious failure with
SIGABRT.
I'm seeing this on a 128 core system running Guix, and limiting to just 64
processors seems sufficient.
* tests/publish.scm: Call setaffinity when the current processor count exceeds
64.
Change-Id: Id4c6d7dcc9ae8dd8dafa2587def98f538061425c
publish: Call (current-processor-count) later.
So that this is evaluated when the main part of the script runs.
I'm looking at this to allow using setaffinity in the publish tests.
* guix/scripts/publish.scm (%default-options): Remove workers default.
(guix-publish): Move the default to here.
Change-Id: I83cd0d048f2641291b5bd8a932b479b23dd92d29
gnu: vulkan-volk: renamed from volk to avoid confusion with another volk package..
* gnu/packages/vulkan.scm (vulkan-volk): Renamed from volk.
(vulkan-tools)[native-inputs]: Reference to volk changed to vulkan-volk.
Change-Id: I8f5e93b753e714d990a837ab914156e5e46d6e46
Signed-off-by: Nicolas Goaziou <mail@nicolasgoaziou.fr>
gnu: trealla: Update to 2.64.3.
* gnu/packages/prolog.scm (trealla): Update to 2.64.3.
Change-Id: Iba818c9402a16be0b285671dfd5b234184adb011
build-system: asdf: Don't search and replace inputs when unnecessary.
If the new-name matches the original name, just use the original package.
This avoids situations where there are several packages matching the name and
the behaviour will be inconsistent, occasionally picking different packages.
Since there are multiple glibc packages currently, I'm seeing this behaviour
with cl-posix-mqueue and ecl-cl-posix-mqueue, occasionally they'll use the
hurd glibc variant.
* guix/build-system/asdf.scm (package-with-build-system): Use the original
input packages unless the new-name differs.
Change-Id: I08a1f3ad1290689b5497d31950ada4dc0bfa3a3a
gnu: go-github-com-hodgesds-perf-utils: Skip more tests on arm.
I see these failing when built on Honeycomb build machines:
=== RUN TestDataTLB
utils_test.go:234: no such file or directory
--- FAIL: TestDataTLB (0.00s)
=== RUN TestInstructionTLB
utils_test.go:246: no such file or directory
--- FAIL: TestInstructionTLB (0.00s)
It could be something with the system configuration but just disable the tests
for now. This is working towards getting the prometheus-node-exporter package
building again on aarch64-linux.
Note that there's even more test failures when trying to build with qemu
binfmt emulation.
* gnu/packages/golang-xyz.scm (go-github-com-hodgesds-perf-utils)[arguments]:
Skip a couple more tests on arm.
Change-Id: Ib5bc41679d825a1a727e240e7fffeb336f82db6d
gnu: linux-libre-arm64-honeycomb: Switch to lts version.
Plus enable more modules, some that I added when playing around with enabling
the SFP+ ports, and others that seem to be required for vsockets (to have
parity with x86_64-linux, e.g. #76352).
* gnu/packages/linux.scm (linux-libre-arm64-honeycomb): Update to
linux-libre-lts-version and enable more modules.
Change-Id: I50689c5420d25a6e83bf0c0d6a64ef02019826ed
gnu: python-trimesh: Skip tests requiring network.
* gnu/packages/python-science (python-trimesh)[arguments]<#:test-flags>: Skip
network tests.
Change-Id: I82389eca3baf14322875daa9aa33f74a1066c8e3
Signed-off-by: Guillaume Le Vaillant <glv@posteo.net>
gnu: chirp: Update to 0.4-3.1219bee.
* gnu/packages/radio.scm (chirp): Update to 0.4-3.1219bee.
Change-Id: I7eead6dd10f0acf0669929b9324930c596f912f8
gnu: Add r-grandr.
* gnu/packages/cran.scm (r-grandr): New variable.
Change-Id: Ib11e4ba8db31ffe176c1e6ae753125a88d850299
gnu: Add r-lfc.
* gnu/packages/cran.scm (r-lfc): New variable.
Change-Id: I71a31ebfd21bda11a5d068b0b3b79fdc50dcb469
gnu: ksoloti-runtime: Update to 1.1.0.
* gnu/packages/axoloti.scm (ksoloti-runtime): Update to 1.1.0.
[arguments]: Adjust phases 'patch-paths, 'build, and 'install.
[inputs]: Remove chibios; a patched and reduced variant is bundled; update
cross-toolchain to 9-2020-q2-update.
[native-inputs]: Remove unzip.
(ksoloti-patcher)[arguments]: Adjust launcher script in 'install phase.
[inputs]: Replace openjdk11 with openjdk17; updgrade cross-toolchain to 9-2020-q2-update.
Change-Id: I0433467badc3d00cf1d16e1d141ece09e926c4d8
gnu: java-flatlaf: Update to 3.5.4.
* gnu/packages/java-graphics.scm (java-flatlaf): Update to 3.5.4.
Change-Id: I87645c695ee3c87a64f08d30f199badafb1d4c1b
gnu: Add GCC arm-none-eabi toolchain 9-2020-q2-update.
* gnu/packages/embedded.scm: (make-gcc-arm-none-eabi-9-2020-q2-update,
make-newlib-arm-none-eabi-9-2020-q2-update,
make-newlib-nano-arm-none-eabi-9-2020-q2-update,
make-arm-none-eabi-toolchain-9-2020-q2-update): New procedures.
Change-Id: Iffb1554bbf38382dadaac7ad8059330f37a54a5c