From: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
To: "Aníbal Limón" <anibal.limon@linux.intel.com>, yocto@yoctoproject.org
Subject: Re: [[PATCH][AUH] 3/3] upgradehelper.py: Disable _order_pkgs_to_upgrade functionality
Date: Tue, 21 Jun 2016 09:08:22 -0500 [thread overview]
Message-ID: <df1ef372-888a-c6c7-bdd4-05035e84bd42@linux.intel.com> (raw)
In-Reply-To: <1466458070-20099-3-git-send-email-anibal.limon@linux.intel.com>
On 06/20/2016 04:27 PM, Aníbal Limón wrote:
> The _order_pkgs_to_upgrade function order a set of packages to
> be upgraded based on bitbake dependency graph, currently _order_pkgs_to_upgrade
> is broken so disable it while fix.
>
> Signed-off-by: Aníbal Limón <anibal.limon@linux.intel.com>
> ---
> upgradehelper.py | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/upgradehelper.py b/upgradehelper.py
> index 386cbcc..239fd88 100755
> --- a/upgradehelper.py
> +++ b/upgradehelper.py
> @@ -500,8 +500,9 @@ class Updater(object):
> return pkgs_to_upgrade_ordered
>
> def run(self, package_list=None):
> - pkgs_to_upgrade = self._order_pkgs_to_upgrade(
> - self._get_packages_to_upgrade(package_list))
> + #pkgs_to_upgrade = self._order_pkgs_to_upgrade(
> + # self._get_packages_to_upgrade(package_list))
are these commented lines intended to be on the patch?
> + pkgs_to_upgrade = self._get_packages_to_upgrade(package_list)
> total_pkgs = len(pkgs_to_upgrade)
>
> pkgs_ctx = {}
prev parent reply other threads:[~2016-06-21 14:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-20 21:27 [[PATCH][AUH] 1/3] Small fixes to use with Python3 Aníbal Limón
2016-06-20 21:27 ` [[PATCH][AUH] 2/3] upgradehelper.py: Move build of gcc runtime after discover packages Aníbal Limón
2016-06-20 21:27 ` [[PATCH][AUH] 3/3] upgradehelper.py: Disable _order_pkgs_to_upgrade functionality Aníbal Limón
2016-06-21 14:08 ` Leonardo Sandoval [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=df1ef372-888a-c6c7-bdd4-05035e84bd42@linux.intel.com \
--to=leonardo.sandoval.gonzalez@linux.intel.com \
--cc=anibal.limon@linux.intel.com \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.