<div dir="ltr"><div dir="ltr"><div>On Tue, 6 Aug 2019 at 14:51, Richard Purdie <<a href="mailto:richard.purdie@linuxfoundation.org">richard.purdie@linuxfoundation.org</a>> wrote:<br></div></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
We now filter the pkgdata to the things a recipe can see in its<br>
dependencies after:<br>
<br>
<a href="http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=99206cb7b41be7a124ea8339bc891077f02128a2" rel="noreferrer" target="_blank">http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=99206cb7b41be7a124ea8339bc891077f02128a2</a><br>
<br>
Does that help? If not, is it because some code isn't using the<br>
filtered copy? Or could we use this technique somewhere else?<br>
<br>
I've not looked at the underlying issues enough to tell which code is<br>
actually triggering it but that kind of approach should help with this<br>
kind of problem and at least make it deterministic...<br></blockquote><div><br></div><div><div>I think the issue might be actually in the QA check where it looks
beyond the recipe's immediate RDEPENDS (and then fails or not depending
on whether those indirect dependencies have been packaged). I need to better understand what happens there so will add some printouts first. The problem does happen with latest master.<br></div><div><br></div><div>Alex<br></div></div></div></div>