From cca5eb8ec3f6ffb54b1085b9b1f8623bc9e6a6bc Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Tue, 28 May 2019 18:26:21 -0700 Subject: ref-manual: New section "Checking Upgrade Status of a Recipe" I added a new section showcasing the "devtool check-upgrade-status" command. Also, added a note in the "Upgrading a Recipe" section" to tell the reader they might want to check on a recipe's upgrade status before upgrading a recipe. (From yocto-docs rev: ca091498a274b9a7a44b0d6d5ee826c1d2bd6a3c) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/ref-manual/ref-devtool-reference.xml | 72 ++++++++++++++++++++++ 1 file changed, 72 insertions(+) (limited to 'documentation') diff --git a/documentation/ref-manual/ref-devtool-reference.xml b/documentation/ref-manual/ref-devtool-reference.xml index a7f5f8e25f..b35aa039b1 100644 --- a/documentation/ref-manual/ref-devtool-reference.xml +++ b/documentation/ref-manual/ref-devtool-reference.xml @@ -427,6 +427,71 @@ + +
+ Checking on the Upgrade Status of a Recipe + + + Upstream recipes change over time. + Consequently, you might find that you need to determine if you + can upgrade a recipe to a newer version. + + + + To check on the upgrade status of a recipe, use the + devtool check-upgrade-status command. + The command displays a table of your current recipe versions, + the latest upstream versions, and any additional information + such as commit hash strings and reasons you might be able to + upgrade a particular recipe. + + + + As with all devtool commands, you can get + help on the individual command: + + $ devtool check-upgrade-status -h + NOTE: Starting bitbake server... + usage: devtool check-upgrade-status [-h] [--all] [recipe [recipe ...]] + + Prints a table of recipes together with versions currently provided by + recipes, and latest upstream versions, when there is a later version available + + arguments: + recipe Name of the recipe to report (omit to report upgrade info for + all recipes) + + options: + -h, --help show this help message and exit + --all, -a Show all recipes, not just recipes needing upgrade + + Following is a partial example table which reports on all the + recipes: + + $ devtool check-upgrade-status + ... + NOTE: acpid 2.0.30 2.0.31 + Ross Burton <ross.burton@intel.com> + NOTE: u-boot-fw-utils 2018.11 2019.01 + Marek Vasut <marek.vasut@gmail.com> + d3689267f92c5956e09cc7d1baa4700141662bff + NOTE: u-boot-tools 2018.11 2019.01 + Marek Vasut <marek.vasut@gmail.com> + d3689267f92c5956e09cc7d1baa4700141662bff + . + . + . + NOTE: base-passwd 3.5.29 3.5.45 + Anuj Mittal <anuj.mittal@intel.com> cannot be updated due to: Version + 3.5.38 requires cdebconf for update-passwd utility + NOTE: busybox 1.29.2 1.30.0 + Andrej Valek <andrej.valek@siemens.com> + NOTE: dbus-test 1.12.10 1.12.12 + Chen Qi <Qi.Chen@windriver.com> + + +
+
Upgrading a Recipe @@ -441,6 +506,13 @@ section of the Yocto Project Development Tasks Manual. This section overviews the devtool upgrade command. + + Before you upgrade a recipe, you can check on its upgrade + status. + See the + "Checking on the Upgrade Status of a Recipe" + for more information. + -- cgit v1.2.3-54-g00ecf