Hi Chris,
I don’t have any idea with regard to the issue that you are getting below. All
the work that we are doing here so far is on CHV (yocto-kernel-3.19.5
standard/base branch).
From your statement below, it looks to me that you are upgrading meta-intel
from Daisy to Fido branch which
Hi ,
I hope this is correct place for my doubts on yocto. If not please
ignore this mail.
I am trying to install node.js on yocto. I added the nodejs recipe and
when i do bitbake an rpm package is generated, but when i try to install it
i see that there are lot of dependency issues and
Hi,
Yes, actually we have some problems checking out layers when the build
starts. But I'm not seeing anything that may be related to imported layers.
The problem that I'm seeing in your logs is actually tracked here:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=7505
So I'm guessing
It looks like I screwed up this patch when I was rewriting some git
history. I'm working up a fix.
Philip
On 06/06/2015 05:37 PM, Philip Tricca wrote:
Signed-off-by: Philip Tricca fl...@twobit.us
---
.../e2fsprogs/misc-xattr-create-xattr-cache.patch | 217
+
The validation for dropping changes needs to be defined only when
interactive mode is true if not this causes to drop the changes
for every failure.
Signed-off-by: Aníbal Limón anibal.li...@linux.intel.com
---
upgradehelper.py | 7 +++
1 file changed, 3 insertions(+), 4 deletions(-)
diff
On Wed, Jun 10, 2015 at 1:01 AM, Sai Prasad B
saiprasa...@pathpartnertech.com wrote:
Hi ,
I hope this is correct place for my doubts on yocto. If not please ignore
this mail.
I am trying to install node.js on yocto. I added the nodejs recipe and
when i do bitbake an rpm package is
[YOCTO #7489]
Signed-off-by: Aníbal Limón anibal.li...@linux.intel.com
---
upgradehelper.py | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/upgradehelper.py b/upgradehelper.py
index 266435d..19753a6 100755
--- a/upgradehelper.py
+++ b/upgradehelper.py
@@ -126,10
Print sentences need to be displayed as information in the logger
this unifies logger facilities.
[YOCTO #7489]
Signed-off-by: Aníbal Limón anibal.li...@linux.intel.com
---
recipe.py| 9 -
upgradehelper.py | 8
2 files changed, 8 insertions(+), 9 deletions(-)
diff
[YOCTO #7489]
Signed-off-by: Aníbal Limón anibal.li...@linux.intel.com
---
upgradehelper.py | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/upgradehelper.py b/upgradehelper.py
index 6af79a0..4a07d7b 100755
--- a/upgradehelper.py
+++ b/upgradehelper.py
@@ -148,10 +148,8
The changes can be found at,
http://git.yoctoproject.org/cgit/cgit.cgi/auto-upgrade-helper/log/?h=alimon/devel
Aníbal Limón (11):
upgradehelper.py: Fix status_msg in pkg_upgrade_handler
upgradehelper.py: Make usage of new upstream detection mechanism
upgradehelper.py: Use settings.from as
When try to upgrade only one recipe is needed to specify the version
also when enable send emails it need to have a maintainer to avoid
exception.
[YOCTO #7489]
Signed-off-by: Aníbal Limón anibal.li...@linux.intel.com
---
upgradehelper.py | 15 ++-
1 file changed, 14 insertions(+),
Change logic to use new values in checkpkg file generated with new
oe.recipeutils.get_recipe_upstream_version and distrodata class.
Remove CSV parsing by hand use csv module and also add debugging when
discard recipes.
[YOCTO #7488]
Signed-off-by: Aníbal Limón anibal.li...@linux.intel.com
---
When is called pkg_upgrade_handler for generate email and save
build history at end sometimes status_msg is undefined.
Signed-off-by: Aníbal Limón anibal.li...@linux.intel.com
---
upgradehelper.py | 16 +---
1 file changed, 9 insertions(+), 7 deletions(-)
diff --git
Use build machines in email to maintainers instead of put that the build
succeed in major arch's, this give to the maintainer non ambiguos info.
[YOCTO #7489]
Signed-off-by: Aníbal Limón anibal.li...@linux.intel.com
---
upgradehelper.py | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
Now send emails almost in all cases this give the maintainer
patches and diff to continue work also if the build isn't
succesful.
[YOCTO #7489]
Signed-off-by: Aníbal Limón anibal.li...@linux.intel.com
---
upgradehelper.py | 19 ++-
1 file changed, 10 insertions(+), 9
When license change it need to be specified into email to maintainers
for review it.
Add get_license_diff_file_name method to recipe class for get it
into email handler and write information about it.
[YOCTO 7186]
Signed-off-by: Aníbal Limón anibal.li...@linux.intel.com
---
recipe.py|
Hi Luke,
Comments below,
Best regards,
alimon
[1] https://autobuilder.yoctoproject.org/
[2] http://git.yoctoproject.org/cgit/cgit.cgi/yocto-autobuilder/
On 10/06/15 14:25, Luke (Lucas) Starrett wrote:
Hi,
I'm trying to understand the feasibility of shared-state across multiple users
in
I'm building for two similar targets and sharing sstate between
them. Actually, I build for target A and use that sstate cache
in my SSTATE_MIRRORS for target B.
If I try to build target B from scratch, i.e. wipe out most
everything from my build tree:
% mv cache sstate-cache tmp old2; rm -fr
Hi,
I'm trying to understand the feasibility of shared-state across multiple users
in a development environment. Does anyone have first-hand experience with
this? Am I asking for trouble?
If this is expected to work, a secondary question would be whether or not
shared-state on a NFS mounted
On Tue, Jun 9, 2015 at 9:34 PM, Brian Hutchinson b.hutch...@gmail.com wrote:
On Tue, Jun 9, 2015 at 9:14 PM, Bruce Ashfield
bruce.ashfi...@windriver.com wrote:
On 2015-06-09 9:12 PM, Brian Hutchinson wrote:
On Tue, May 19, 2015 at 12:42 PM, Brian Hutchinson b.hutch...@gmail.com
wrote:
On
Hi again,
On 06/09/2015 12:21 PM, Peter Bergin wrote:
Hi,
On 06/09/2015 11:28 AM, Burton, Ross wrote:
On 9 June 2015 at 09:27, Peter Bergin
peter.ber...@tritech.semailto:peter.ber...@tritech.se wrote:
The root cause of this is an error during the build of Python3. From
21 matches
Mail list logo
