[yocto] do_roots braking after a SRCREV update for non master branch

Burton, Ross ross.burton at intel.com
Thu Jan 18 06:51:40 PST 2018


I'd check (using oe-pkgdata-util and/or buildhistory-diff) that the new
package is building the same files and packages as the old one.  If PN
wasn't being generated, that would explain why the provides isn't working.

Ross

On 18 January 2018 at 14:46, Alan Martinovic <alan.martinovic at senic.com>
wrote:

> Hi,
> I've updated my recipe to use a review from a non master branch:
>
> Old version [python3-senichub_git.bb]:
>
>     inherit setuptools3
>
>     PROVIDES += "python3-senic-hub"
>     RPROVIDES_${PN} += "python3-senic-hub"
>
>     S = "${WORKDIR}/git"
>     SRC_URI = "git://github.com/getsenic/senic-hub.git;"
>     SRCREV = "01fd5bd8725add5e73d3cc35a169f0dc837daefa"
>     PV = "git-${SRCPV}"
>
>     RDEPENDS_${PN} = "python3-nuimo python3-lightify"
>
> New version [python3-senichub_git.bb]:
>
>     inherit setuptools3
>
>     PROVIDES += "python3-senic-hub"
>     RPROVIDES_${PN} += "python3-senic-hub"
>
>     S = "${WORKDIR}/git"
>     SRC_URI = "git://github.com/getsenic/senic-hub.git;branch=improve-
> logging;"
>     SRCREV = "ad6c082a8a990291c6128f54ea0c0d185081704e"
>     PV = "git-${SRCPV}"
>
>     RDEPENDS_${PN} = "python3-nuimo python3-lightify"
>
>
> So the only changes is the SRCREV, and a specific
> branch in the SRC_URI.
> The package alone builds successfully.
> But when building the image it fails on the do_rootfs:
>
>     opkg_prepare_url_for_install: Couldn't find anything to satisfy
> 'python3-senic-hub'.
>
> I can't really make the causes of it. There are some legacy
> naming inconsistencies with a dash, but there is an explicit
> PROVIDES and RPROVIDES in both recipes, one fails the
> other passes.
>
> Any ideas?
> --
> _______________________________________________
> yocto mailing list
> yocto at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20180118/b5f48790/attachment.html>


More information about the yocto mailing list