[Yocto-builds] buildbot failure in Yocto on crownbay

Tom Zanussi tom.zanussi at intel.com
Mon Jun 4 20:58:19 PDT 2012


On Mon, 2012-06-04 at 20:27 -0700, Scott Garman wrote:
> On 06/04/2012 01:28 PM, Tom Zanussi wrote:
> > On Fri, 2012-06-01 at 09:17 -0700, Scott Garman wrote:
> >> On 06/01/2012 09:12 AM, Paul Eggleton wrote:
> >>> On Friday 01 June 2012 00:09:13 elizabeth.flanagan at intel.com wrote:
> >>>> Build status: FAILURE
> >>>>
> >>>> Buildslave for this Build: ab09
> >>>> Complete logs for all build steps:
> >>>> http://autobuilder.yoctoproject.org:8010/builders/crownbay/builds/134 Build
> >>>> Reason: Triggerable(crownbay)
> >>>> Build Source Stamp: [branch denzil] 7552ccd06c6327b5f36ee0cceb432946f8e98d3f
> >>>
> >>> | error: Failed dependencies:
> >>> | 	libusb-0.1-4>= 0.1.3 is needed by gnupg-2.0.18-r1.core2
> >>> NOTE: package core-image-sato-sdk-1.0-r0: task do_rootfs: Failed
> >>>
> >>> Not sure what is going on here but we seem to be getting this a lot with the
> >>> denzil builds. Scott, any ideas?
> >>
> >> I'm planning to run some builds over the weekend, and I'll make sure
> >> core-image-sato-sdk is one of them.
> >>
> >
> > Were you able to see anything?
> >
> > I was unable to reproduce this here, but it seems to be blocking all the
> > meta-intel BSPs on autobuilder...
> 
> I haven't been able to reproduce it building core-image-sato for crownbay.
> 
> However, I have the feeling this is the rpm ordering bug that bit us for 
> the useradd packages that rely on shadow utils and friends being installed.
> 

Is there a workaround for that?

It seems only the autobuilder is seeing this problem, and everyone else
doing their own (from-scratch?) builds is able to get a good build...

Considering that all we need at this point are images for QA to test, is
there something that can be done on autobuilder to get past this and get
some images built?

One thing I noticed is that gnupg depends on libusb, but gnupg doesn't
have libusb in its DEPENDS.  I don't know if thats the source of the
problem, but shouldn't it regardless?

Beth, can you try the following patch on one of the failing builds and
see if it helps?

Tom

----

[PATCH] gnupg: add libusb to DEPENDS

gnupg apparently depends on libusb:

| error: Failed dependencies:
| 	 libusb-0.1-4 >= 0.1.3 is needed by gnupg-2.0.18-r1.core2

So add libusb to gnupg DEPENDS.

Signed-off-by: Tom Zanussi <tom.zanussi at intel.com>
---
 meta/recipes-support/gnupg/gnupg_2.0.18.bb |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/meta/recipes-support/gnupg/gnupg_2.0.18.bb b/meta/recipes-support/gnupg/gnupg_2.0.18.bb
index 3085494..7dfd908 100644
--- a/meta/recipes-support/gnupg/gnupg_2.0.18.bb
+++ b/meta/recipes-support/gnupg/gnupg_2.0.18.bb
@@ -4,8 +4,8 @@ LICENSE = "GPLv3 & LGPLv3"
 LIC_FILES_CHKSUM = "file://COPYING;md5=f27defe1e96c2e1ecd4e0c9be8967949 \
                     file://COPYING.LIB;md5=6a6a8e020838b23406c81b19c1d46df6"
 
-DEPENDS = "pth libassuan libksba zlib bzip2 readline libgcrypt"
-PR = "r1"
+DEPENDS = "pth libassuan libksba zlib bzip2 readline libgcrypt libusb"
+PR = "r2"
 
 inherit autotools gettext
 
-- 
1.7.0.4




> https://bugzilla.yoctoproject.org/show_bug.cgi?id=2349
> 
> Scott
> 





More information about the yocto-builds mailing list