diff options
author | OYTIS <anton.gerasimov@here.com> | 2018-10-12 16:58:15 +0200 |
---|---|---|
committer | Patrick Vacek <patrickvacek@gmail.com> | 2018-10-30 13:40:38 +0100 |
commit | c18824081b5d9d01337b3e33f5c78368b7fcf97b (patch) | |
tree | fe616f99e819030bbdff9f84e9c5bc8079058317 | |
parent | 6c3f7564ea6fabdb6b882ef0a6f3d24af46979d0 (diff) | |
download | meta-updater-c18824081b5d9d01337b3e33f5c78368b7fcf97b.tar.gz |
Fix typos/language
-rw-r--r-- | README.adoc | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/README.adoc b/README.adoc index 189a4d8..e14d7bd 100644 --- a/README.adoc +++ b/README.adoc | |||
@@ -178,7 +178,7 @@ Every time you build an image with `SOTA_PACKED_CREDENTIALS` set, a new entry in | |||
178 | 1. Set `GARAGE_TARGET_VERSION` variable in your `local.conf`. | 178 | 1. Set `GARAGE_TARGET_VERSION` variable in your `local.conf`. |
179 | 2. Write a recipe or a bbclass to write the desired version to `${STAGING_DATADIR_NATIVE}/target_version`. An example of such bbclass can be found in `classes/target_version_example.bbclass`. | 179 | 2. Write a recipe or a bbclass to write the desired version to `${STAGING_DATADIR_NATIVE}/target_version`. An example of such bbclass can be found in `classes/target_version_example.bbclass`. |
180 | 180 | ||
181 | Please note that [target name, target version] pairs are expected to be unique in the system. If you build a new target with the same target version as a previously build one, the old package will be overwritten on the update server. It can have unpredictable effect on devices that have this version installed, it is not guaranteed that information will be reported correctly for such devices or that you will be able to update them (we're doing our best though). The easiest way to avoid problems is to make sure that your overriding version is as unique as OSTree commit hash. | 181 | Please note that [target name, target version] pairs are expected to be unique in the system. If you build a new target with the same target version as a previously built one, the old package will be overwritten on the update server. It can have unpredictable effect on devices that have this version installed, and it is not guaranteed that information will be reported correctly for such devices or that you will be able to update them (we're doing our best though). The easiest way to avoid problems is to make sure that your overriding version is as unique as an OSTree commit hash. |
182 | 182 | ||
183 | == QA with oe-selftest | 183 | == QA with oe-selftest |
184 | 184 | ||