Skip to content

Conversation

@h8d13
Copy link
Contributor

@h8d13 h8d13 commented Dec 29, 2025

Instead of over complex like I tried in #4002

This is a much simpler approach we set the fallback in args.py and make it mandatory in the menu.
Again this to address lots of logs that get PGP verif errors because TZ was not set.

@h8d13 h8d13 requested a review from Torxed as a code owner December 29, 2025 10:57
@Torxed
Copy link
Member

Torxed commented Dec 29, 2025

I'm not sure I understand what the original problem was?
When I'm lazy I usually just stick with the default UTC and it works fine, unless the hardware clock is way off - but that's more an issue of it being off than what time zone I picked?

@h8d13
Copy link
Contributor Author

h8d13 commented Dec 29, 2025

Just because I see of lot of error logs than yeah its hardware clock (which also gets reset on dead CMOS), so i thought making it explicit choice + showing RTC clock originally (previous PR #4002)

@Torxed
Copy link
Member

Torxed commented Dec 29, 2025

hmm, well NTP should make stuff "just work", as it should happen before archinstall starts strapping in packages. And a timezone shouldn't be needed?

@h8d13
Copy link
Contributor Author

h8d13 commented Dec 29, 2025

My thought was that I could be dead (the service, happens sometimes) or disconnected for offline installs with cached files, so time being wrong there would cause pgp errors.

But yeah I do see how it's technically a non-problem for regular usage.

@h8d13 h8d13 closed this Dec 29, 2025
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.

2 participants