commit | db3d966a75875914f630ff702a27f6db2bf63326 | [log] [tgz] |
---|---|---|
author | Adriana Kobylak <anoo@us.ibm.com> | Fri Dec 06 14:55:44 2024 -0600 |
committer | Adriana Kobylak <anoo@us.ibm.com> | Mon Dec 09 14:12:34 2024 -0600 |
tree | d979cf4b4f1ecaf9b5f5b8cbf16c151e0d381864 | |
parent | 61c1a8aa917a70bef59f7e72a3f69c778347f03f [diff] |
obmc-flash-bmc: Add new Manager service as default For D-Bus calls that require the service name, use the new Software.Manager service first since that'll be the default, and if the call fails, try with the old code update service name: busctl new || old We could use the mapper API GetObject to figure out the service name, but this would add a 2nd D-Bus call, and the new code update service would be the default so there's no need to make additional calls. In addition the output of GetObject would need to be parsed. And in some instances like the call to busctl tree service, there's not a unique interface under the software/ path to differentiate the service name from other updaters such as the PSU update manager. Tested: Code update with new and old service on a p10bmc system. Change-Id: Ib5c8115006028d7d9341895afab46eb771f8cf33 Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
Phosphor BMC Code Management provides a set of system software management applications. More information can be found at Software Architecture
To build this package, do the following steps:
meson build
ninja -C build
To clean the repository run rm -r build
.