On Wed, Apr 18, 2018 at 2:41 PM, Martin Siegumfeldt <m...@gomspace.com> wrote:
> Hi,
>
> I am having a number of recipes residing in two versions, some (development
> versions) being down-prioritized using:
>
> DEFAULT_PREFERENCE = "-1"
>
>
> The source code is hosted at a private git repository, and the git version is
> selected using 'AUTOREV'. The extensible SDK renders successfully, however
> the installation (by third party) fails:
>
> Traceback (most recent call last):
> File "/home/martin/gomspace_sdk/layers/poky/bitbake/lib/bb/data_smart.py",
> line 412, in DataSmart.expandWithRefs(s='dev+git${SRCPV}', varname='PV'):
> try:
> > s = __expand_var_regexp__.sub(varparse.var_sub, s)
> try:
> File "/home/martin/gomspace_sdk/layers/poky/bitbake/lib/bb/data_smart.py",
> line 111, in VariableParse.var_sub(match=<_sre.SRE_Match object; span=(7,
> 15), match='${SRCPV}'>):
> else:
> > var = self.d.getVarFlag(key, "_content")
> self.references.add(key)
> File "/home/martin/gomspace_sdk/layers/poky/bitbake/lib/bb/data_smart.py",
> line 794, in DataSmart.getVarFlag(var='SRCPV', flag='_content', expand=True,
> noweakdefault=False, parsing=False):
> cachename = var + "[" + flag + "]"
> > value = self.expand(value, cachename)
>
> File "/home/martin/gomspace_sdk/layers/poky/bitbake/lib/bb/data_smart.py",
> line 436, in DataSmart.expand(s='${@bb.fetch2.get_srcrev(d)}',
> varname='SRCPV'):
> def expand(self, s, varname = None):
> > return self.expandWithRefs(s, varname).value
>
> File "/home/martin/gomspace_sdk/layers/poky/bitbake/lib/bb/data_smart.py",
> line 426, in DataSmart.expandWithRefs(s='${@bb.fetch2.get_srcrev(d)}',
> varname='SRCPV'):
> except Exception as exc:
> > raise ExpansionError(varname, s, exc) from exc
>
> bb.data_smart.ExpansionError: Failure expanding variable SRCPV, expression
> was ${@bb.fetch2.get_srcrev(d)} which triggered exception FetchError: Fetcher
> failure: Fetch command export GIT_SSL_CAINFO="/home
> /martin/gomspace_sdk/buildtools/sysroots/x86_64-gomspacesdk-linux/etc/ssl/certs/ca-certificates.crt";
> export
> PATH="/home/martin/gomspace_sdk/tmp/work/aarch64-gomspace-linux/libgsisl/fetcheravoidrecurse-r0
> /recipe-sysroot-native/usr/bin/python-native:/home/martin/gomspace_sdk/layers/poky/scripts:/home/martin/gomspace_sdk/tmp/work/aarch64-gomspace-linux/libgsisl/fetcheravoidrecurse-r0/recipe-sysroot-native/u
> sr/bin/aarch64-gomspace-linux:/home/martin/gomspace_sdk/tmp/work/aarch64-gomspace-linux/libgsisl/fetcheravoidrecurse-r0/recipe-sysroot/usr/bin/crossscripts:/home/martin/gomspace_sdk/tmp/work/aarch64-gomsp
> ace-linux/libgsisl/fetcheravoidrecurse-r0/recipe-sysroot-native/usr/sbin:/home/martin/gomspace_sdk/tmp/work/aarch64-gomspace-linux/libgsisl/fetcheravoidrecurse-r0/recipe-sysroot-native/usr/bin:/home/marti
> n/gomspace_sdk/tmp/work/aarch64-gomspace-linux/libgsisl/fetcheravoidrecurse-r0/recipe-sysroot-native/sbin:/home/martin/gomspace_sdk/tmp/work/aarch64-gomspace-linux/libgsisl/fetcheravoidrecurse-r0/recipe-s
> ysroot-native/bin:/home/martin/gomspace_sdk/layers/poky/bitbake/bin:/home/martin/gomspace_sdk/tmp/hosttools";
> export HOME="/home/martin"; git -c core.fsyncobjectfiles=0 ls-remote
> ssh://g...@github.com/GomS
> pace/libisl failed with exit code 128, output:
> Host key verification failed.
> fatal: Could not read from remote repository.
>
>
> Please make sure you have the correct access rights
> and the repository exists.
>
> It is not the intention that third party will ever need access to the
> development version, and I don't see why the version information is fetched
> given the reduced priority. Have I encountered an 'undocumented bug' or is
> there an alternate approach to achieve this?
eSDK and recipes doing AUTOREV are known to not play well (yet). There
is a bug open to address it at
https://bugzilla.yoctoproject.org/show_bug.cgi?id=11350
>
> Thanks,
> Martin
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
--
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
