Config [[files]] entries for init services used /usr/lib/init.d/ paths,
which get silently overwritten by package staging (Layer 2 over Layer 1).
Per AGENTS.md, config overrides MUST use /etc/init.d/ so the init system's
config_for_dirs() gives them priority over package defaults.
Fixes mini image debug console failure (getty: failed to open TTY
/scheme/fbcon/3: No such file or directory) caused by base package's
31_debug_console.service overwriting minimal.toml's debug scheme override.
The Wayland compositor was commented out, causing the greeter to fail
when trying to launch the UI. With the compositor enabled, the full
greeter flow now works: compositor starts, creates Wayland socket,
greeter UI launches on VT 3, and Qt6 client connects successfully.
Bootloader hardcoded RedoxFS partition offset at 2 MiB, which fails when
efi_partition_size > 1 (redbear-full, redbear-grub use 16 MiB, placing
RedoxFS at LBA 34816 = 17 MiB). Added GPT partition table parser that
scans for Linux filesystem GUID (0FC63DAF) to find the actual offset.
Also removed invalid 'respawn = true' from 31_debug_console.service in
redbear-full.toml — init's service format does not support this field.
Verified: all three ISOs boot in QEMU UEFI and reach login prompt.
5-phase hardening to prevent silent file-layer collisions (the D-Bus
regression class):
Phase 1: lint-config-paths.sh + make lint-config in depends.mk
Phase 2: CollisionTracker in installer (content-hash comparison)
Phase 3: installs manifests in recipe.toml + validate-file-ownership.sh
Phase 4: validate-init-services.sh + make validate in disk.mk
Phase 5: documentation (AGENTS.md, BUILD-SYSTEM-HARDENING-PLAN.md)
Both redbear-mini and redbear-full build and validate clean.
66 declared install paths in base, zero conflicts.
The [users.root] override in redbear-full.toml only set shell, which
replaced (not merged) the base.toml entry that had uid=0 gid=0
password="password". Without explicit uid/gid, the installer assigned
root UID 1000, causing D-Bus to fail looking up user "root" and
"messagebus" — all D-Bus clients (sessiond, polkit, udisks, upower)
timed out and exited.
Verified: D-Bus daemon starts, polkit registers PolicyKit1, sessiond
registers login1, zero timeouts or retries in QEMU boot.
Shell: Changed default shell from ion to zsh for all user accounts
in base.toml, redbear-mini.toml, redbear-full.toml, and greeter config.
zsh 5.9 is already ported and builds (ZSH-PORTING-PLAN — fully implemented).
ion is kept as fallback/alternative.
Cookbook: pkgar staging fallback — when a dependency's target pkgar
doesn't exist, fall back to repo/<target>/<pkg>.pkgar. This fixes the
kf6-kitemviews build failure where libwayland's pkgar was missing from
the target directory.
Finalize all non-artifact changes accumulated from other sessions:
- config updates, recipe changes, source edits, patches
- pkgar/cache artifacts intentionally excluded (build outputs)
This is the maximum achievable scope for this session.
Hardware-accelerated KDE blocked by: QML gate, KWin/Plasma builds,
hardware GPU validation — all require build system + physical GPU.
These packages have recipes but are not yet built.
Commented out with #WIP notes until artifacts exist.
[[files]] in device-services.toml are valid TOML array tables.
config/redbear-full.toml had duplicate [packages] table (lines 26 + 406),
making it syntactically invalid. Moved konsole + kf6-pty into first
[packages] section, removed duplicate table. Single [packages] at l26.
1. local/AGENTS.md: KWin/greeter/KF6 status updated to current truth
2. config/redbear-full.toml: konsole + kf6-pty moved under [packages]
3. docs/05 + BLUETOOTH + VFAT: redbear-kde.toml → redbear-full.toml
4. All remaining fixable Oracle issues from round 9 resolved
1. config/wayland.toml: kwin_wayland_wrapper → redbear-compositor
(redbear-compositor IS the Wayland compositor)
2. docs/README.md: removed stale 2026-04-14 status note
(referenced docs were already deleted)
3. docs/07: redbear-compositor serves as Wayland compositor
(not "provides kwin_wayland binary")
Newly enabled (previously commented as blocked):
kf6-kdeclarative, kf6-kwayland, kf6-kpackage, kf6-kidletime,
kf6-kded6, kf6-kitemmodels, kf6-prison, kglobalacceld
All build successfully and publish pkgar to repo.
Plus kf6-kcmutils + kdecoration from earlier round.
Total KDE packages enabled: 35 (was 26 before sensors/libinput)
Total pkgar in repo: growing with each cook
Remaining blocked: plasma-* (QML gate), kirigami (QML gate),
breeze (compilation), kde-cli-tools (compilation),
kf6-knewstuff (empty package), kwin real binary (QML gate)
Disabled: kdecoration, kf6-kcmutils, kf6-kdeclarative, kf6-kded6,
kf6-kidletime, kf6-kitemmodels, kf6-kpackage, kf6-kwayland,
kf6-prison, kglobalacceld. All commented as 'blocked: no pkgar
artifact in repo'. Config now matches actual repo artifacts:
26 KDE enabled ≈ 29 KDE pkgar (3 are transitive deps).
Step 2: kf6-kio in repo ✅, kde-cli-tools out of scope (commented)
Step 3: Config accurate — blocked packages commented with reasons
Step 4: CONSOLE plan line 6 replaced with scoped verification claim:
'VERIFIED scope is the currently buildable KDE surface on
redbear-full; packages blocked by QML/Sensors/libinput stay
commented out and are not part of this verification claim'
Step 5: Docs synced with config
- hostinfo.cpp not in cmake KIOCORE source list; workerinterface.cpp
called KIO::HostInfo::lookupHost which had no implementation
- Replaced HostInfo::lookupHost call with direct QHostInfo::fromName
in workerinterface.cpp via recipe sed, removed hostinfo.h include
- kf6-kio now publishes 2.4MB pkgar to repo
- Enabled in config. Unblocks kde-cli-tools (kde-cli has its own
separate build error)
- Blocked count: 12 → 11 (kf6-kio now builds)
- config/redbear-full.toml: 22 KF6 + kglobalacceld enabled, kirigami only suppressed
- kf6-knewstuff + kf6-kwallet now enabled (real cmake builds with stub fallback)
- recipe.toml: added redbear-phase6-kde-check to package.files (was in Cargo.toml but not packaged)
Phase 4 KDE Plasma preparation:
kded6: new recipe at local/recipes/kde/kf6-kded6/ building the KDE
daemon from source. Depends on kf6-kconfig, kf6-kcoreaddons,
kf6-kcrash, kf6-kdbusaddons, kf6-kservice — all already built.
Added to redbear-full.toml package list. D-Bus activation file
already existed; removed TODO now that recipe exists.
kirigami: rewrite from stub to real CMake build. qtdeclarative
(Qt6Quick) is now available, so the real Kirigami can be built
instead of installing dummy cmake configs and a static lib placeholder.
Added qtshadertools and qtsvg as additional dependencies.
Convert 14 config files from the legacy init script format (plain-text
commands) to the systemd-style TOML .service format. The init daemon
supports both formats; this eliminates the legacy path entirely so that
all services use the richer, more structured TOML unit format.
Key changes per config:
- base.toml: split 00_base into 00_base.service (tmpdir) + 00_sudo.service
(sudo daemon); remove redundant 00_drivers and 10_net (handled by
existing .service files from the base recipe)
- minimal.toml: split 30_console into 29_activate_console.service +
30_console.service + 31_debug_console.service
- desktop-minimal.toml: convert 20_display and 30_console to .service,
add 29_activate_console and 31_debug_console overrides
- x11.toml: convert 10_dbus, 10_xenv, 20_orbital, 30_console
- redoxer.toml: split 10_net into 10_smolnetd.service + 10_dhcpd.service,
convert 30_redoxer
- redbear-legacy-*.toml: update override references to .service paths
- acid.toml, auto-test.toml, os-test.toml, sys-build.toml: direct conversions
vasilito