From c9ea0c619dd356c95cad511742ae1e19e571b37b Mon Sep 17 00:00:00 2001 From: Richard Purdie Date: Wed, 30 Sep 2015 14:42:07 +0100 Subject: lib/oe/package_manager: Handle empty package list in opkg case If you build buildtools-tarball with opkg as the package manager, it passes in an empty target packages list and fails. This allows the code to cope with an empty package list (in sync with the rpm backend). (From OE-Core rev: b460afb12bb16a4b56d800c953c5f5c7da0bff84) Signed-off-by: Richard Purdie --- meta/lib/oe/package_manager.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'meta/lib/oe/package_manager.py') diff --git a/meta/lib/oe/package_manager.py b/meta/lib/oe/package_manager.py index c51e88be58..630b957ba9 100644 --- a/meta/lib/oe/package_manager.py +++ b/meta/lib/oe/package_manager.py @@ -1512,7 +1512,7 @@ class OpkgPM(PackageManager): self.deploy_dir_unlock() def install(self, pkgs, attempt_only=False): - if attempt_only and len(pkgs) == 0: + if not pkgs: return cmd = "%s %s install %s" % (self.opkg_cmd, self.opkg_args, ' '.join(pkgs)) -- cgit v1.2.3-54-g00ecf