]> code.ossystems Code Review - openembedded-core.git/commit
package_manager.py: Explicit complementary fail
authorNiko Mauno <niko.mauno@vaisala.com>
Wed, 28 Feb 2018 16:20:08 +0000 (18:20 +0200)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Thu, 8 Mar 2018 18:36:17 +0000 (10:36 -0800)
commit2502bd591c37bf532d02dc6b37fc1e8b5224fb0a
treea045274269eca1d08fb58dd306349621fc594b15
parent62acf087dca83ff094b1c0300b5752978807ca17
package_manager.py: Explicit complementary fail

When running bitbake -c populate_sdk <image_name>, it is expected that
packages matching SDKIMAGE_INSTALL_COMPLEMENTARY name mask (unless
declared in PACKAGE_EXCLUDE_COMPLEMENTARY) are installed to resulting
SDK. Underlying mechanism issues a package manager install call for set
of complementary packages. However the mechanism doesn't seem to inform
the user all too obviously in case the package manager command behind
install_complementary() method fails -- and since it is combined with
attempt_only=True option, user might end up wondering why several *-dev,
*-dbg packages are missing from resulting SDK.

Improve associated install() method behaviour in affected OpkgPM and
DpkgPM classes so that a problematic state of affairs becomes directly
obvious for bitbake user, resulting in shell output like:

  WARNING: someimage-1.0-r0 do_populate_sdk: Unable to install packages.
  Command '...' returned 1:
  Collected errors:
   * Solver encountered 1 problem(s):
   * Problem 1/1:
   *   - package somepkg-dev-1.0-r0.x86 requires somepkg = 1.0-r0, but
         none of the providers can be installed
   *
   * Solution 1:
   *   - allow deinstallation of someotherpkg-1.1-r1.x86

   *   - do not ask to install a package providing somepkg-dev

   * Solution 2:
   *   - do not ask to install a package providing somepkg-dev

Signed-off-by: Niko Mauno <niko.mauno@vaisala.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
meta/lib/oe/package_manager.py