[bluetooth.bluez] downgrade to dbus version 0.2.0 #18132
Closed
+4
−5
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
Signed-off-by: Jörg Sautter <[email protected]>
|
No need to rush as long as we have this sorted before the next milestone. Could you in the mean while check if this issue does not occur at 0.2.0 ( i noticed the pom.xml still pointed to 0.1.4) |
|
Superseded by #18146 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
@lsiepel This PR will downgrade to
0.2.0in case anyone does need to have a working bluetooth stack for testing without dropping the compatible changes to the code.See #18124 (comment) for details about what is broken.