**** BEGIN LOGGING AT Tue May 08 03:00:03 2018
May 08 03:50:49 <yocti> New news from stackoverflow: conditionals in Yocto <https://stackoverflow.com/questions/50225540/conditionals-in-yocto>
May 08 04:06:06 <jynik> It looks like Patchwork demands that patches pertaining to CVEs list "CVE: CVE-yyyy-nnnnn' in the commit message.
May 08 04:07:39 <jynik> I'm looking to update the cve-check class to inspect (backported) patches for this string. Right now, if you're on a release branch (e.g. Rocko) you'll continue to get CVE warnings despite having the patches.
May 08 04:08:04 <jynik> Usually, this is due to the patch not having the CVE in the filename, as is the case when a patch contains multiple fixes.
May 08 04:08:32 <jynik> Just wanted to bounce this idea of folks before I test it out and ship it off to the mailing list.
May 08 04:08:45 <jynik> Any thoughts/feedback welcome. :)
May 08 04:09:14 <jynik> *off folks
May 08 04:24:07 <jynik> Hrm... beb089b indicates this should already be done...
May 08 04:55:12 <jynik> Ah... I see the issue: cve-check.bbclass only handles 1 CVE fix per patch.
May 08 04:55:38 <jynik> </monologue>
May 08 09:52:02 <yocti> New news from stackoverflow: Yocto and rpm repository using https on the google cloud <https://stackoverflow.com/questions/50230447/yocto-and-rpm-repository-using-https-on-the-google-cloud>
May 08 09:52:15 <RP> kanavin: confirmed it was the ca-certs upgrade that broke images
May 08 11:11:54 <malu1> Hi, I've just upgraded from Ubuntu 17.10 to Ubuntu 18.04 and am now getting multiple errors directly related to "build/tmp/sysroots-uninative/x86_64-linux/lib/libc.so.6: version `GLIBC_2.27' not found"
May 08 11:12:21 <malu1> any advice how to fix that ?
May 08 11:13:56 <malu1> fun fact, Ubuntu 18.10 seems to include libc 2.27-3ubuntu1 so it should find it
May 08 11:14:02 <malu1> 18.04*
May 08 11:17:42 <paulbarker> malu1: Which branch of yocto project are you using?
May 08 11:19:09 <malu1> paulbarker: rocko
May 08 11:19:15 <LetoThe2nd> malu1: there has been some fun going on lately with glibc 2.27, with fedora being the first host to break IIRC
May 08 11:19:59 <paulbarker> I'd suggest sticking with previous Ubuntu versions for rocko for now. Fixes probably will get backported as rocko is still in maintenance but the focus is on getting the sumo release out right now
May 08 11:20:45 * LetoThe2nd seconds that.
May 08 11:20:59 <malu1> if I lib dependencies manually using ldd it finds the glibc dependency just fine
May 08 11:21:04 <malu1> +check
May 08 11:21:48 <malu1> yeah, it might be a bit premature jumping to 18.04 but I suspect the only problem is the glibc 2.27 issue
May 08 11:23:39 <malu1> I bet it is the ld host search paths that somehow gets overrided by yocto resuling in it not finding the libc-2.27.so despite it being installed.
May 08 11:27:22 <rburton> malu1: its uninative so its *way* more complicated than that
May 08 11:27:46 <rburton> ubuntu 1804 isn't supported under rocko but file a bug please
May 08 11:27:52 <LetoThe2nd> probably it would be enough to cherry-pick the uninative version from sumo, but thats *PURE* guesswork
May 08 11:28:02 <malu1> rburton: uninative?
May 08 11:29:00 <rburton> malu1: the other solution is to disable uninative
May 08 11:30:26 <malu1> rburton: I'm not sure what uninative is in context of yocto but how do I try disable it?
May 08 11:30:36 <rburton> your distro configuration enables it
May 08 11:30:53 <rburton> i suspect you're using poky instead of your own, so this is a lesson in 'why not to just use poky'
May 08 11:31:13 <rburton> INHERIT_remove = "uninative" will work if you don't want to write your own distro configuration
May 08 11:31:44 <malu1> yes I'm using poky ^^
May 08 11:32:56 <LetoThe2nd> rburton: if you would take care that poky *ALWAYS* breaks catastrophically, then nobody would use it. problem solved.
May 08 11:33:00 <LetoThe2nd> </SCNR>
May 08 11:34:40 <malu1> the INHERIT_remove is that something which can be inserted in local.conf?
May 08 11:34:43 <rburton> yes
May 08 11:35:36 <malu1> ok, i'll try that
May 08 11:36:06 <eduardas_m> hello, it seems something is wrong with IRC logs, https://www.yoctoproject.org/irc/latest.log.html no longer directs me to them
May 08 11:36:30 <eduardas_m> I get directed to the Yocto project wiki instead
May 08 11:36:39 <rburton> halstead: ^ irc logs redirect not working
May 08 12:16:35 <malu1> is uninative some sort of prepackaged stuff? So using INHERIT_remove = "uninative" makes it truly build everything from scratch?
May 08 12:53:29 <malu1> rburton: using INHERIT_remove = "uninative" bypassed my glibc 2.27 issue, thanks.
May 08 13:27:42 <osse> I've added a layer to conf/bblayers.conf and it works (I can build a recipe from it), but bitbake-layers show-layers doesn't list it. am i missing some formalities in layer.conf maybe?
May 08 14:48:15 <steamrunner> Good morning everyone!
May 08 14:50:17 <kergoth> osse: most likely you didn't set BBFILE_COLLECTIONS, BBFILE_PATTERN_<name> and BBFILE_PRIORITY_<name> correctly
May 08 14:50:36 <kergoth> BBPATH+BBFILES will get classes and recipes avaialbe, respectively, but it's not a layer from bitbake's perspective without the rest
May 08 14:53:14 <steamrunner> I'm having an issue with bitbake. I followed https://www.yoctoproject.org/docs/2.4.2/yocto-project-qs/yocto-project-qs.html to install the dependencies for ubuntu 16.04 (updated & upgraded), checked out poky 2.4.2, and when I run "bitbake core-image-minimal" it just hangs without any text output.
May 08 14:53:35 <steamrunner> Left it overnight hoping to see something
May 08 14:55:19 <steamrunner> ctrl-c just gets the output: "Keyboard Interrupt, closing down...", then ~1 min later "Timeout while waiting for a reply from the bitbake server"
May 08 14:56:03 <steamrunner> I did this both on a fresh install of ubuntu 16.04 on a machine and in a vm. same result
May 08 14:57:32 <steamrunner> top -p $(python3) shows Cooker is still running
May 08 14:58:47 <steamrunner> Anyone got a suggestion?
May 08 15:15:23 <halstead> rburton: eduardas_m: IRC display is fixed. Thanks for the report.
May 08 16:23:45 <denix> hey, who broke rocko? armpit?
May 08 16:24:42 <zeddii> not me!
May 08 16:24:51 <zeddii> that's my standard response to anything ;)
May 08 16:38:23 <RP> denix: broke how?
May 08 17:23:32 <yocti> New news from stackoverflow: using xsltproc for a Yocto recipe <https://stackoverflow.com/questions/50238922/using-xsltproc-for-a-yocto-recipe>
May 08 17:28:30 <JPEW> denix: Is it the waf issue on the ML?
May 08 17:36:26 <JPEW> Hmm, I don't seem to be able to fetch from git@push.yoctoproject.org anymore: Permission denied (publickey)
May 08 17:36:59 <rburton> JPEW: don't fetch from push?
May 08 17:37:18 <rburton> use git.yoctoproject.org for fetch
May 08 17:37:25 <rburton> [url "ssh://git@push.yoctoproject.org/"]
May 08 17:37:25 <rburton> 	pushInsteadOf = yocto:
May 08 17:37:26 <rburton> [url "git://git.yoctoproject.org/"]
May 08 17:37:26 <rburton> 	insteadOf = yocto:
May 08 17:37:30 <rburton> is what i have in my gitconfig
May 08 17:38:20 <denix> JPEW: yes, waf
May 08 17:38:26 <JPEW> Right... that is for sure a config error on my end... it must have worked at some point in the past
May 08 17:38:54 <JPEW> denix: Hmm, the change that was revereted didn't seem to touch get_waf_parallel_make()
May 08 17:41:02 <denix> JPEW: good point and I think I found my problem
May 08 17:46:35 <JPEW> Ok, I can fetch, now I can't push to poky-contrib (same error) :)
May 08 17:47:46 <rburton> are you pushing to push.?
May 08 17:50:17 <JPEW> I think so: git@push.yoctoproject.org: Permission denied (publickey).
May 08 18:23:43 <yocti> New news from stackoverflow: How to add LAN and RS232 in yocto <https://stackoverflow.com/questions/49903067/how-to-add-lan-and-rs232-in-yocto>
May 08 18:39:18 <armpit> RP I am killing the rocko build. it pulled in the wrong gplv2 branch
May 08 19:23:56 <yocti> New news from stackoverflow: flashing yocto image to raspberrypi cm3 eMMC <https://stackoverflow.com/questions/50240520/flashing-yocto-image-to-raspberrypi-cm3-emmc>
May 08 20:24:08 <yocti> New news from stackoverflow: Add kernel configuration options using configuration fragments in custom YOCTO layer <https://stackoverflow.com/questions/50040020/add-kernel-configuration-options-using-configuration-fragments-in-custom-yocto-l>
May 08 23:30:03 <armpit> Rp, rocko build finished
May 08 23:54:52 * armpit hmm do I update to Ubuntu 18??
May 08 23:57:14 <rburton> armpit: you'll have to fix uninative in rocko
May 08 23:57:38 <rburton> or did you already backport the new glibc patches from sumo
May 09 00:00:34 <armpit> rburton, I will have to double check. I think I have everything in rocko except the libcrypt changes which are a problem.
May 09 00:01:19 <armpit> rburton, its for morty ; ) to trouble shoot a problem in I saw in Ubunut 17
May 09 00:02:03 <armpit> rburton, why are you awake?
May 09 00:02:20 <rburton> armpit: literally just dropped from our planning meeting
May 09 00:02:34 <rburton> hooray tri-zone meetings, 11pm-1am for me
May 09 00:02:45 <armpit> wow
May 09 00:03:05 <rburton> the guy in penang, 6am-8am
May 09 00:03:50 <rburton> but now, bedtime :)
May 09 00:03:56 <armpit> night
May 09 00:04:08 <rburton> armpit: rocko failed selftest btw
May 09 00:04:17 <armpit> I saw
May 09 00:04:20 <armpit> thanks
**** ENDING LOGGING AT Wed May 09 03:00:04 2018