Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backport "timedate: handle gracefully if RTC lost time because of power loss" (v254) #445

Closed

Conversation

chombourger
Copy link

Apparently some RTC drivers return EINVAL in that case when we try to read it. Handle that reasonably gracefully.

Fixes: #31854
(cherry picked from commit 5c81de9)

@chombourger
Copy link
Author

chombourger commented Sep 26, 2024

Not sure if this is the proper way to ask for a specific patch to be backported/integrated into a -stable release
One of our embedded device uses a 3rd party RTC driver that return EINVAL and this fix is exactly what we would need to handle this case gracefully

@yuwata
Copy link
Member

yuwata commented Jan 24, 2025

Sorry for late review. LGTM. But let's first backport this to v255.
#470

Apparently some RTC drivers return EINVAL in that case when we try to
read it. Handle that reasonably gracefully.

Fixes: #31854
(cherry picked from commit 5c81de9)
(cherry picked from commit b858433)
@yuwata yuwata force-pushed the backport-5c81de98fc branch from 7c4007b to 54060ae Compare March 5, 2025 13:19
Copy link

We were not able to find or create Copr project packit/systemd-systemd-stable-445 specified in the config with the following error:

Cannot create a new Copr project (owner=packit project=systemd-systemd-stable-445 chroots=[]): chroots: '[]' is not a valid choice for this field..

Unless the HTTP status code above is >= 500, please check your configuration for:

  1. typos in owner and project name (groups need to be prefixed with @)
  2. whether the project name doesn't contain not allowed characters (only letters, digits, underscores, dashes and dots must be used)
  3. whether the project itself exists (Packit creates projects only in its own namespace)
  4. whether Packit is allowed to build in your Copr project
  5. whether your Copr project/group is not private

@yuwata
Copy link
Member

yuwata commented Mar 5, 2025

#470 is merged. Rebased.

@bluca
Copy link
Member

bluca commented Mar 5, 2025

I'll handle this in the other PR

@bluca bluca closed this Mar 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants