Genivi Software Manager with RPyC #6
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
added 30 commits
March 1, 2016 10:38
…d of send dbus message
…fecycle_manager.py
… of rpyc versus dbus
…y state 'simulating' to avoid confusion
… If this fails, sota_client exits without performing any actions.
Small fix
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.
We were unable to install the necessary dependencies to be able to run Genivi Software Manager on NGI 1.0. I rewrote the program to work with RPyC instead of dbus for interprocess communication.
I also changed the print calls to output directly to log files. The main rationale behind this is because we can't view the output of the Software Manager components as there is no way to launch a terminal window on the IMC.
Tested on NGI 1.12.5.4.2, we used the RPyC version to successfully install an .rpm on the rig.