Lines Matching refs:upgrade

45        upgrade               Upgrade an existing recipe
49        check-upgrade-status  Report upgradability for multiple (or all) recipes
287 ``devtool add`` or ``devtool upgrade`` commands.
323 .. _devtool-checking-on-the-upgrade-status-of-a-recipe:
329 need to determine if you can upgrade a recipe to a newer version.
331 To check on the upgrade status of a recipe, you can use the
334 picture, use the ``devtool check-upgrade-status`` command, which takes a
340 being able to upgrade it, displayed in a table.
342 This upgrade checking mechanism relies on the optional :term:`UPSTREAM_CHECK_URI`,
366    $ devtool check-upgrade-status -h
368    usage: devtool check-upgrade-status [-h] [--all] [recipe [recipe ...]]
373      recipe      Name of the recipe to report (omit to report upgrade info for all recipes)
377      --all, -a   Show all recipes, not just recipes needing upgrade
393    $ devtool check-upgrade-status
416 overviews the ``devtool upgrade`` command.
418 Before you upgrade a recipe, you can check on its upgrade status. See
419 the ":ref:`devtool-checking-on-the-upgrade-status-of-a-recipe`" section
422 The ``devtool upgrade`` command upgrades an existing recipe to a more
426 upgrade, patches associated with the recipe are rebased or added as
429 When you use the ``devtool upgrade`` command, you must supply the root
433 which you want to upgrade (i.e. the :term:`PV`), the source
434 revision to which you want to upgrade (i.e. the
438 You can read more on the ``devtool upgrade`` workflow in the
439 ":ref:`sdk-manual/extensible:use \`\`devtool upgrade\`\` to create a version of the recipe that sup…
442 how to use ``devtool upgrade`` in the ":ref:`dev-manual/common-tasks:using \`\`devtool upgrade\`\``"