-
Notifications
You must be signed in to change notification settings - Fork 561
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
kernel-uki: drop dbus in initrd #10311
kernel-uki: drop dbus in initrd #10311
Conversation
@jozzsi Change looks good to me. No issue in our initrd |
@jozzsi there seems to be a conflict as another PR that went in also bumped the kernel version. Could you bump the release version to |
Sorry, but this process is too much overhead for me as now it also needs a rebase. Feel free to close this PR or take it over. |
No problem. I can take over the PR. Thank you for the change! |
fa3bcb0
into
microsoft:tvuong/3.0-dev/uki-remove-dbus
Merge Checklist
All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)
*-static
subpackages, etc.) have had theirRelease
tag incremented../cgmanifest.json
,./toolkit/scripts/toolchain/cgmanifest.json
,.github/workflows/cgmanifest.json
)./LICENSES-AND-NOTICES/SPECS/data/licenses.json
,./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md
,./LICENSES-AND-NOTICES/SPECS/LICENSE-EXCEPTIONS.PHOTON
)*.signatures.json
filessudo make go-tidy-all
andsudo make go-test-coverage
passSummary
dbus is known to have limitations and usually only gets included for either networking or bluetooth support.
Please see dracutdevs/dracut#2378 and dracut-ng/dracut-ng#60 .
Does this affect the toolchain?
YES
Test Methodology
@ddstreet @trungams - would you please be able to help testing this change given the concerns ? If dbus indeed can be dropped, than it should be dropped and I can finish up the PR with the rest of the changes.