Skip to content

fix: skip the hostname page when the installer already set one#26

Merged
bketelsen merged 1 commit into
mainfrom
fix/skip-hostname-when-set
Jul 5, 2026
Merged

fix: skip the hostname page when the installer already set one#26
bketelsen merged 1 commit into
mainfrom
fix/skip-hostname-when-set

Conversation

@bketelsen

Copy link
Copy Markdown
Contributor

Summary

The new bootc-installer flow prompts for a hostname (disk step, seeded with a hardware-derived default) and applies it at install time — then first setup asked again. Per tonight's decision, the installer owns the hostname; first setup now only asks when the system still has a never-customized hostname.

Change

  • backend.hostname_is_default(): true only for the never-customized fallbacks (localhost, localhost.localdomain, debian, (none), empty) — snow images ship no /etc/hostname, so an untouched system always reports one of these.
  • window.py: the hostname page is only built/appended when that returns true (both OEM and standard flows). When skipped in the standard flow, the user page inherits no_back_button so back-navigation into the connectivity check stays blocked.

This stays adaptive: nbc-era installs, manual installs, or anything else that leaves localhost still gets the hostname page.

Verification

Gate exercised directly (localhost → ask, installer-style hostname → skip), py_compile clean, no dangling __view_hostname references, meson test run locally.

🤖 Generated with Claude Code

The bootc-installer wizard seeds and applies a hostname at install
time, so first setup asked for it a second time. Snow images ship no
/etc/hostname, so an untouched system reports the kernel/systemd
fallback — only show the hostname page when the current hostname is
one of those defaults (localhost, debian, empty). When the page is
skipped in the non-OEM flow, the user page takes over the
no-back-button role it inherited.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@bketelsen
bketelsen merged commit 682811e into main Jul 5, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant