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]>

This commit is contained in:

ekklesia

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

co-authored by

Claude Opus 5

parent b8688d00a7

commit fe08363534

3 changed files with 15 additions and 2 deletions

VERSION

+1 -1

View File

@@ -1 +1 @@
 .2.4
 .2.5