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

[2.12.0] Backport "Remove systemd-resolved, explicitly install systemd-hwe-hwdb on noble" #7472

Merged
merged 2 commits into from
Mar 12, 2025

Conversation

legoktm
Copy link
Member

@legoktm legoktm commented Mar 11, 2025

Status

Ready for review

Description of Changes

Backport of #7466.

Testing

legoktm added 2 commits March 11, 2025 14:51
We don't use systemd-resolved and during the focal -> noble migration,
it gets dropped since it was split out to a separate package.

Now that we can remove it entirely, let's have noble installs absent the
package instead of merely stopping the systemd unit.

Fixes #7464.

(cherry picked from commit 7bdd2af)
This package is installed on fresh systems, but not on upgrades because
it was split out of the systemd package. Set the dependency ourselves to
make sure it's always pulled in.

Currently none of these udev rules apply to expected SecureDrop
hardware, but it's good to futureproof ourselves just in case.

(cherry picked from commit 52106d9)
@legoktm legoktm requested a review from a team as a code owner March 11, 2025 18:52
@rocodes rocodes self-assigned this Mar 11, 2025
Copy link
Contributor

@rocodes rocodes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • visual review; correct base branch
  • only relevant commits

Approving pending CI

@cfm cfm merged commit 57eae5a into release/2.12.0 Mar 12, 2025
44 checks passed
@cfm cfm added this to the SecureDrop 2.12.0 milestone Mar 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

3 participants