This repository has been archived by the owner on Jul 1, 2024. It is now read-only.
Update Bluez to 5.64 #165
Merged
Update Bluez to 5.64 #165
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hi I used to track Ubuntu LTS bluetoothd version on main branch. Honestly I am unsure of the current version as of today. Anyway a branch with the API version is good to go |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This updates bluez to 5.64 and includes the generated files from the new version. As of writing, 5.64 is what Ubuntu 22.04 is using as a core package. This patchset will need a little more tweaking before it is ready as I have not changed the default bluez version away from 5.60 in the Makefile.
@muka, it looks like you have pinned master to 5.60, so for consistency I'm assuming this would go on a new branch ala bluez/5.63?
This should resolve #160, but nothing has changed with the manufacturing data specified in #163, so I'm continuing to run that down.