ekklesiaandClaude Opus 5 fe08363534 fix: a machine with no ifupdown configuration is not an error ...

The release validator caught it: in a container there is no
/etc/network/interfaces at all, and a missing file was being treated as
a read failure, so --check printed nothing and said nothing was wrong
rather than saying there was nothing to do.

A machine with no ifupdown configuration is the ordinary case for a
fresh install, and the answer is simply that this command has no work.

Co-Authored-By: Claude Opus 5 <[email protected]>

2026-09-21 21:23:30 -05:00

config

fix: the bar keeps its order when an application opens

2026-09-21 19:34:15 -05:00

docs

docs: the Wi-Fi hand-over is a physical check, so write down its steps

2026-09-21 21:11:49 -05:00

lib

fix: the bar keeps its order when an application opens

2026-09-21 19:34:15 -05:00

packaging/debian

feat: give Wonder Ink tabs, and let a device say it has no Wonder Ink

2026-09-19 21:29:17 -05:00

scripts

fix: a machine with no ifupdown configuration is not an error

2026-09-21 21:23:30 -05:00

systemd

fix: the room asks for its output again, not only once at boot

2026-09-20 14:46:46 -05:00

tests

fix: a machine with no ifupdown configuration is not an error

2026-09-21 21:23:30 -05:00

tools

fix: give a Wi-Fi the installer set up to NetworkManager, by hand

2026-09-21 21:11:19 -05:00

.gitignore

chore: ignore Python bytecode

2026-09-01 19:17:19 -05:00

update_canary.sh

feat: one download address per channel that never changes

2026-09-20 21:11:35 -05:00

update_classroom_v2.sh

feat: give every room the broker, one scale, and its own panel back

2026-09-12 19:05:09 -05:00

update_stable.sh

feat: one download address per channel that never changes

2026-09-20 21:11:35 -05:00

VERSION

fix: a machine with no ifupdown configuration is not an error

2026-09-21 21:23:30 -05:00

S

Description

No description provided

113 MiB

Languages

Shell 50.9%

Python 48.1%

JavaScript 1%