From: "Aníbal Limón" <anibal.limon@linux.intel.com>
To: yocto@yoctoproject.org
Cc: paul.eggleton@linux.intel.com
Subject: [PATCH 08/10][auh] upgradehelper.py: Remove unused references to Buildhistory class
Date: Wed, 29 Jul 2015 15:50:51 -0500 [thread overview]
Message-ID: <1438203053-7909-9-git-send-email-anibal.limon@linux.intel.com> (raw)
In-Reply-To: <1438203053-7909-1-git-send-email-anibal.limon@linux.intel.com>
Buildhistory class isn't implemented so removed related code.
Signed-off-by: Aníbal Limón <anibal.limon@linux.intel.com>
---
upgradehelper.py | 11 +----------
1 file changed, 1 insertion(+), 10 deletions(-)
diff --git a/upgradehelper.py b/upgradehelper.py
index 7bc8eed..a31d041 100755
--- a/upgradehelper.py
+++ b/upgradehelper.py
@@ -43,7 +43,7 @@ from datetime import date
import shutil
from errors import *
from git import Git
-from bitbake import Bitbake, BuildHistory
+from bitbake import Bitbake
from emailhandler import Email
from statistics import Statistics
from recipe import Recipe
@@ -135,7 +135,6 @@ class Updater(object):
os.mkdir(self.uh_work_dir)
self.bb = Bitbake(get_build_dir())
- self.buildhistory = BuildHistory(get_build_dir())
self.git = None
self.author_email = settings.get('from', 'uh@not.set')
self.author = "Upgrade Helper <%s>" % self.author_email
@@ -266,14 +265,6 @@ class Updater(object):
I(" %s: compiling for %s ..." % (self.pn, machine))
self.recipe.compile(machine)
- def _review(self):
- # Check build_history
- if not self.skip_compilation:
- I(" %s: Checking buildhistory ..." % self.pn)
- self.buildhistory.set_work_dir(self.workdir)
- if self.buildhistory.diff(len(self.machines)):
- I(" %s: Wrote buildhistory-diff output ..." % self.pn)
-
def _check_upstream_versions(self, packages=[("universe", None, None)]):
I(" Fetching upstream version(s) ...")
--
1.9.1
next prev parent reply other threads:[~2015-07-29 20:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-29 20:50 [PATCH 00/10][auh] Add support for buildhistory and minor fixes Aníbal Limón
2015-07-29 20:50 ` [PATCH 01/10][auh] upgradehelper.py: Only run with one recipe or all Aníbal Limón
2015-07-31 13:48 ` Paul Eggleton
2015-07-29 20:50 ` [PATCH 02/10][auh] upgradehelper.py: Validate if upgrade is needed Aníbal Limón
2015-07-29 20:50 ` [PATCH 03/10][auh] upgradehelper.py: Only send emails when patch file exist Aníbal Limón
2015-07-29 20:50 ` [PATCH 04/10][auh] bitbake.py: Improve performance on env() call Aníbal Limón
2015-07-29 20:50 ` [PATCH 05/10][auh] upgradehelper.py: Add own step for loading environment Aníbal Limón
2015-07-31 13:48 ` Paul Eggleton
2015-07-29 20:50 ` [PATCH 06/10][auh] upgradehelper.py: UniverseUpdate don't abort if recipe checkpkg fails Aníbal Limón
2015-07-29 20:50 ` [PATCH 07/10][auh] bitbake.py: Rename bitbake_log.txt to bitbake_error_log Aníbal Limón
2015-07-29 20:50 ` Aníbal Limón [this message]
2015-07-29 20:50 ` [PATCH 09/10][auh] upgradehelper.py: Move upstream versioning code to UniverseUpdater Aníbal Limón
2015-07-29 20:50 ` [PATCH 10/10][auh] upgradehelper: Add support for generate buildhistory recipe diff's Aníbal Limón
2015-07-31 15:29 ` Paul Eggleton
2015-07-31 15:39 ` Aníbal Limón
2015-07-31 16:10 ` Paul Eggleton
2015-07-31 16:19 ` Aníbal Limón
2015-07-31 16:21 ` Paul Eggleton
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=1438203053-7909-9-git-send-email-anibal.limon@linux.intel.com \
--to=anibal.limon@linux.intel.com \
--cc=paul.eggleton@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.