starting new job...
→ running command: cd "/etc/byggsteg/job-clone//lambdock/trunk" && git reset --hard && git pull
HEAD is now at ead857b chore: Release v0.8.2
From https://codeberg.org/jjba23/lambdock
ead857b..436163a trunk -> origin/trunk
Updating ead857b..436163a
Fast-forward
NEWS.org | 5 ++++-
README.org | 40 ++++++++++++++++++++++++++++++++++++++++
scheme/lambdock/core.scm | 4 ++++
scheme/lambdock/state.scm | 21 ++++++++++++++++++++-
src/guile_bridge.c | 18 ++++++++++++++++++
src/guile_bridge.h | 6 ++++++
src/lambdock.h | 6 +++++-
src/main.c | 3 ++-
src/ui/dock_item.c | 4 ++++
tests/scheme/lambdock_tests.scm | 12 ++++++++++++
10 files changed, 115 insertions(+), 4 deletions(-)
→ running command: cd /etc/byggsteg/job-clone/lambdock/trunk && uname -a
Linux wolk-jjba 7.2.11-gnu #1 SMP PREEMPT_DYNAMIC 1 x86_64 GNU/Linux
→ running command: cd /etc/byggsteg/job-clone/lambdock/trunk && git log --name-status HEAD^..HEAD
commit 436163aa0b8528cd630aece22535682a2d8fb92e
Author: Josep Bigorra <jjbigorra@gmail.com>
Date: Sun Oct 25 14:59:36 2026 +0100
feat: Make the gap between dock items a setting
The spacing between items was the hard-coded DOCK_BOX_SPACING_PX (8). It is
now `dock-item-spacing` (default 4), read through `get-dock-item-spacing`,
applied when the box is built and on every hot reload, and settable live with
`set-dock-item-spacing!`.
The default follows the OS X dock: in the reference screenshot its icons are
50px wide with ~15px between them, i.e. ~0.3 x the icon size. With 48px icons,
4px of spacing plus the ~10px of button padding/margins the theme contributes
lands at the same ~15px rhythm (the docs explain the arithmetic and give 0/16
as the extremes).
M NEWS.org
M README.org
M scheme/lambdock/core.scm
M scheme/lambdock/state.scm
M src/guile_bridge.c
M src/guile_bridge.h
M src/lambdock.h
M src/main.c
M src/ui/dock_item.c
M tests/scheme/lambdock_tests.scm
→ running command: cd /etc/byggsteg/job-clone/lambdock/trunk && maak test
The Meson build system
Version: 1.9.0
Source dir: /etc/byggsteg/job-clone/lambdock/trunk
Build dir: /etc/byggsteg/job-clone/lambdock/trunk/build
Build type: native build
Project name: lambdock
Project version: 0.8.2
C compiler for the host machine: cc (gcc 14.3.0 "cc (GCC) 14.3.0")
C linker for the host machine: cc ld.bfd 2.44
Host machine cpu family: x86_64
Host machine cpu: x86_64
Compiler for C supports arguments -Wpedantic: YES
Compiler for C supports arguments -Wshadow: YES
Compiler for C supports arguments -Wstrict-prototypes: YES
Compiler for C supports arguments -Wmissing-prototypes: YES
Compiler for C supports arguments -Wredundant-decls: YES
Compiler for C supports arguments -Wimplicit-fallthrough: YES
Compiler for C supports arguments -Wvla: YES
Compiler for C supports arguments -Wundef: YES
Compiler for C supports arguments -Wformat=2: YES
Compiler for C supports arguments -Wformat-security: YES
Compiler for C supports arguments -Werror=implicit-function-declaration: YES
Compiler for C supports arguments -Werror=incompatible-pointer-types: YES
Compiler for C supports arguments -Werror=int-conversion: YES
Compiler for C supports arguments -Wno-overlength-strings: YES
Found pkg-config: YES (/gnu/store/axnyqk5byz282l7ml2da6jv0jwnryy78-profile/bin/pkg-config) 0.29.2
Did not find CMake 'cmake'
Found CMake: NO
Run-time dependency gtk4 found: NO
meson.build:84:10: ERROR: Dependency lookup for gtk4 with method 'pkgconfig' failed: Could not generate cflags for gtk4:
Package liblzma was not found in the pkg-config search path.
Perhaps you should add the directory containing `liblzma.pc'
to the PKG_CONFIG_PATH environment variable
Package 'liblzma', required by 'libtiff-4', not found
A full log can be found at /etc/byggsteg/job-clone/lambdock/trunk/build/meson-logs/meson-log.txt
--------------------------------------------------------------
Maak 0.12.2: the infinitely extensible command runner
Loading tasks from Maak file: /etc/byggsteg/job-clone/lambdock/trunk/maak.scm
Executing Maak tasks: test
--------------------------------------------------------------
=> Running Maak task: test
Build and run the whole test suite headlessly.
The shell wrapper only applies to the first command, so the pipeline is run by
one inner `sh -c' instead of a bare `&&': otherwise `ninja' would execute
outside the Guix environment.
The GTK tests need a display: with none, `gtk_init_check' fails and GLib turns
the resulting GTK warnings into aborts (6 of 7 tests die with SIGTRAP), so the
suite runs on a virtual X server, as in package.nix's checkPhase. `GDK_BACKEND'
and `GTK_A11Y' are pinned because there is no compositor and no a11y bus here.
The build directory is thrown away first: the Byggsteg job clone survives
between jobs, and a tree configured by a different Meson version makes both
`meson setup' and `ninja' fail with 'build data file ... references functions
or classes that don't exist'. Rebuilding from scratch also means the passing
tests are the ones that match the checked out sources.
Execute command:
guix time-machine --channels=channels.scm -- shell -m manifest.scm -- /bin/sh -c 'set -eu; export GTK_A11Y=none GDK_BACKEND=x11; rm -rf build; meson setup build; ninja -C build; xvfb-run -a -s "-screen 0 1024x768x24" meson test -C build --print-errorlogs'
Executing: guix time-machine --channels=channels.scm -- shell -m manifest.scm -- /bin/sh -c 'set -eu; export GTK_A11Y=none GDK_BACKEND=x11; rm -rf build; meson setup build; ninja -C build; xvfb-run -a -s "-screen 0 1024x768x24" meson test -C build --print-errorlogs'
maak: error: command failed (exit code 1): guix time-machine --channels=channels.scm -- shell -m manifest.scm -- /bin/sh -c 'set -eu; export GTK_A11Y=none GDK_BACKEND=x11; rm -rf build; meson setup build; ninja -C build; xvfb-run -a -s "-screen 0 1024x768x24" meson test -C build --print-errorlogs'
hint: Fix the command above, or run `maak --dry-run' to inspect it first.