fix(kyber): use ubuntu as default username - #1517
Conversation
|
You do not have enough credits to review this pull request. Please purchase more credits to continue. |
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
Disabled knowledge base sources:
📝 WalkthroughSummary by CodeRabbit
WalkthroughThe username configuration for the kyber host is updated from "shunkakinoki" to "ubuntu" across two related Nix files. The change affects both the main flake configuration and the kyber module's default parameter value. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
Poem
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
…lt user Latitude.sh provisions Ubuntu images with the `ubuntu` system user. The kyber host config was using `shunkakinoki` which caused Home Manager activation to fail with `USER is "ubuntu", expected "shunkakinoki"`.
Mesa DescriptionTL;DRFixed Kyber host configuration to use What changed?
Description generated by Mesa. Update settings |
Summary
ubuntuas the default system usershunkakinoki, causing Home Manager activation to fail:USER is "ubuntu", expected "shunkakinoki"flake.nixandnamed-hosts/kyber/default.nixto useubuntuTest plan
make build && make switchsucceeds on kyber withoutUSERoverrideSummary by cubic
Set kyber’s default username to
ubuntuto match Latitude.sh images and fix Home Manager activation failures.flake.nixandnamed-hosts/kyber/default.nixto setusername = "ubuntu".Written for commit 8fd2d35. Summary will update on new commits.