summaryrefslogtreecommitdiff
path: root/meta-openembedded/meta-python/recipes-devtools/python/python-m2crypto
diff options
context:
space:
mode:
authorAlexander Filippov <a.filippov@yadro.com>2018-11-23 16:04:49 +0300
committerBrad Bishop <bradleyb@fuzziesquirrel.com>2018-11-28 17:45:18 +0300
commit2f714db14e994f0bb4cd412e1dd4526c2c517e25 (patch)
treec48234da48ad494fbe7dabed3c97a8a4462ba93d /meta-openembedded/meta-python/recipes-devtools/python/python-m2crypto
parent01f149c02c90389f51f2c4eaf5519f9bf2aa57d0 (diff)
downloadopenbmc-2f714db14e994f0bb4cd412e1dd4526c2c517e25.tar.xz
Fix the starting of phosphor-hwmon
After the commit 7ead6495b6d6782dd89951e8bfb26131f35863ec the phosphor-hwmon failed to start with errors like this: ``` /lib/systemd/system/xyz.openbmc_project.Hwmon@.service:8: Failed to resolve unit specifiers on %f: Invalid argument ``` It happens when the instance name begins with `/` character which causes this error when used specifier `%f`. Besides the specifier `%I` looks less buggy and more appropriate in this case, because it's the only part of path and will be completed inside the `phosphor-hwmon-readd`. This commit fixes the starting of the phosphor-hwmon. Partially resolves: openbmc/openbmc#3435 (From meta-phosphor rev: a87fb2d1eb682ed0f04e0f269966b9ae4aafbb1e) Change-Id: Ia8185f047f23bdcd9141d7edea47ad50e6f7fe07 Signed-off-by: Alexander Filippov <a.filippov@yadro.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Diffstat (limited to 'meta-openembedded/meta-python/recipes-devtools/python/python-m2crypto')
0 files changed, 0 insertions, 0 deletions