From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Tanu Kaskinen <tanu.kaskinen@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/3] speex, speexdsp: 1.2rc1 -> 1.2rc2/1.2rc3
Date: Wed, 15 Jul 2015 08:40:21 +0100 [thread overview]
Message-ID: <1436946021.3310.95.camel@linuxfoundation.org> (raw)
In-Reply-To: <1436438943.23019.26.camel@tkkaskin-mobl3.ger.corp.intel.com>
On Thu, 2015-07-09 at 13:49 +0300, Tanu Kaskinen wrote:
> On Thu, 2015-07-09 at 11:11 +0300, Tanu Kaskinen wrote:
> > On Thu, 2015-07-09 at 08:58 +0100, Richard Purdie wrote:
> > > I included these patches on the autobuilder in master-next and saw:
> > >
> > > https://autobuilder.yoctoproject.org/main/builders/nightly-x86-lsb/builds/385/steps/BuildImages_1/logs/stdio
> > >
>
> The libspeexdsp-dev problem is more difficult, and I don't really know
> how to debug it further. The error message was:
>
> error: Can't install pulseaudio-dev-6.0-r0@core2_32: no package provides libspeexdsp-dev
>
> However, "bitbake speexdsp" seems to generate the libspeexdsp-dev
> package just fine (libspeexdsp-dev_1.2rc3-r0_core2-64.ipk appears in the
> deploy directory).
This one is a little crazy to debug. What you need to do is build
something i586 (like qemux86), then build something core2_32 (like
genericx86), then "bitbake core-image-lsb core-image-lsb-sdk -c rootfs"
and hope the -lsb image builds before -lsb-sdk (I hacked runqueue to
ensure that). Then you see this error.
genericx86 is seeing two copies of libspeexdsp-dev, one from the i586
feed and one from the core2_32 feed and somehow they confuse it, perhaps
due to the RCONFLICTS or something.
Obviously this isn't really a bug in the libspeexdsp recipe, its a bug
in smart combined with a second bug where genericx86 shouldn't be seeing
the i586 packages.
I'll continue to try and narrow it down and produce a test case which is
more easily replicable. I'll not block your upgrades on this though,
this needs fixing elsewhere.
Cheers,
Richard
(going quietly insane with the number of AB 'random' failures)
next prev parent reply other threads:[~2015-07-15 7:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-06 15:14 [PATCH 0/3] speex, speexdsp: 1.2rc1 -> 1.2rc2/1.2rc3 Tanu Kaskinen
2015-07-06 15:14 ` [PATCH 1/3] speexdsp: initial recipe Tanu Kaskinen
2015-07-06 15:14 ` [PATCH 2/3] speex: 1.2rc1 -> 1.2rc2 Tanu Kaskinen
2015-07-06 15:14 ` [PATCH 3/3] alsa-plugins, pulseaudio: depend on speexdsp, not speex Tanu Kaskinen
2015-07-07 13:23 ` [PATCH 0/3] speex, speexdsp: 1.2rc1 -> 1.2rc2/1.2rc3 Alexander Kanavin
2015-07-09 7:58 ` Richard Purdie
2015-07-09 8:11 ` Tanu Kaskinen
2015-07-09 10:49 ` Tanu Kaskinen
2015-07-11 22:42 ` Richard Purdie
2015-07-15 7:40 ` Richard Purdie [this message]
2015-07-15 8:25 ` Andre McCurdy
2015-07-22 7:02 ` Richard Purdie
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=1436946021.3310.95.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=tanu.kaskinen@linux.intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox