Eine neue MuPiBox NG Alpha ist verfügbar: 0.2.0-alpha.56. Hier findest du die Änderungen und Fehlerbehebungen dieser Version.
Was ist neu?
- Prevents release/runtime synchronization from replacing a working systemd service, timer or socket unit with a truncated or empty file.
- Installs runtime unit files via verified, fully written temporary files and atomic rename rather than truncating the live unit in place. This also protects a box if an update or post-boot synchronization is interrupted.
- Rejects empty or invalid unit payloads and reports an explicit error without overwriting the existing live unit.
- Uses unique temporary filenames for updater state and runtime writes to avoid collisions between concurrent operations.
- Adds regression tests for empty release files and concurrent writes, plus tests of the safe shell installation path.
The fix addresses a serious report following an update from alpha.54 to alpha.55, where zero-byte systemd service files left the backend, Admin interface and media unavailable even though the update was recorded as confirmed. The precise trigger has not yet been reproduced; this release hardens the identified failure paths.
IMPORTANT: We recommend that all alpha.55 installations update to alpha.56. If the Admin interface is already inaccessible, a damaged installation may require restoring its service files from /opt/mupibox-release/current/deploy/ via SSH before it can update. Back up configuration before updating. No library reset or downgrade is required for the reported recovery procedure.