| commit | 24a8d83d68af09e4b59882481a61e9206bfac556 | [log] [tgz] | 
|---|---|---|
| author | Adriana Kobylak <anoo@us.ibm.com> | Wed Jun 10 08:29:36 2020 -0500 | 
| committer | Adriana Kobylak <anoo@us.ibm.com> | Wed Jun 10 10:38:28 2020 -0500 | 
| tree | b9875a6030969705effad8e4415d47542cf5df45 | |
| parent | 58aa75083162fa5662673511b43d423baeecf52f [diff] | 
item_updater: Use relative path to append OS_RELEASE_FILE
The path append behavior changed between std::experimental and
std::filesystem where appending an absolute path replaces the path
instead of appending, therefore need to use .relative_path().
This was causing the item updater to recreate the d-bus objects with
version OS_RELEASE_FILE instead of MEDIA_DIR/rofs-x/OS_RELEASE_FILE
marking the 2 versions of the system functional and with the same
version string.
Fixes openbmc/phosphor-bmc-code-mgmt#5
Tested: Verified with debug logs that the path was just OS_RELEASE_FILE
        without this change, and it was MEDIA_DIR/rofs-x/OS_RELEASE_FILE
        after this change, the version strings were correct, and only 1
        functional BMC association was created.
Change-Id: I2f81942d7fbb24e839e8f712cd2d84a80b7cd125
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 buildninja -C buildTo clean the repository run rm -r build.