use systemd inhibitors
Open
Nobody has claimed this yet.
triaged
- Dominant language
- Rust
- Stars
- 196
- Forks
- 55
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 14
Description
From discussion on fedora-devel list; we should definitely use systemd inhibitors when we're in the process of doing an update.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the linked systemd inhibitors documentation and tracing bootupd's update flow to identify when an update is in progress. Done means bootupd uses a systemd inhibitor during that process, with behavior verified against the project's existing checks or tests if available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100