Oleksandr ShyshatskyiandClaude Opus 5 9fcfaa43a4 klipper-config links the configs it ships, rather than hoping anvil-core did ...

printer.cfg includes the ff-*.cfg beside it, and those are symlinks that
anvil-link-prog.sh makes from whatever it finds in $MODDIR/config. The only
package calling that script was anvil-core -- which does not own those files,
and which opkg installs first. So an upgrade that ADDS an ff-*.cfg linked the
old set and left the new file with nothing pointing at it, and Klipper refused
to start:

    Include file '/usr/data/config/ff-pa.cfg' does not exist

Seen on a printer, 2026-08-31. The package that ships the files now relinks
them. Re-running the script from two postinsts costs nothing: link_one leaves
a link that is already right alone.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01AVUMfbNuKUWWV32PBcydwb

2026-08-31 12:26:48 +03:00

..

control

klipper-config links the configs it ships, rather than hoping anvil-core did

2026-08-31 12:26:48 +03:00

payload/config

Package numpy, because klippy does not start without it

2026-08-31 13:42:57 +03:00

build.sh

Say what the code does, not what it used to

2026-08-29 18:42:57 +03:00

pkg.conf

moonraker-timelapse ships as a package

2026-08-30 15:47:46 +03:00