**** BEGIN LOGGING AT Wed Apr 27 02:59:58 2016 Apr 27 08:15:00 bluelightning: hi Apr 27 09:39:37 hi Noor Apr 27 09:50:28 bluelightning: I was looking at the bug assigned to you Apr 27 09:54:22 bluelightning: https://bugzilla.yoctoproject.org/show_bug.cgi?id=5546 Apr 27 10:35:19 Noor: right, yes... the answer is possibly, but it's not a straightforward fix Apr 27 10:35:53 bluelightning: ok Apr 27 11:10:51 bluelightning, more esdk fun Apr 27 11:10:53 Parsing recipes...WARNING: /home/balister/sdks-ext/layers/meta-swupdate/recipes-extended/images/bbb-swu-image.bb: Unable to get checksum for bbb-swu-image SRC_URI entry sw-description: file could not be found Apr 27 11:11:19 now, I didn't build the sdk for this image and the sdk build (and image build) work Apr 27 11:11:28 but I recall seeing a warning about this Apr 27 11:11:34 seems to convert to an error Apr 27 11:19:20 Crofton|work: not sure, but why do you have an invalid SRC_URI entry, shouldn't you just fix that? Apr 27 11:21:42 that warning triggers also on valid SRC_URI entries Apr 27 11:22:40 e.g. SRC_URI = "file://foo.conf" COMPATIBLE_MACHINE="bar" -> recipedir/bar/foo.conf and then building for MACHINE!=bar Apr 27 11:26:54 bluelightning, sure, but I am curious why the builds work and esdk install fails Apr 27 11:28:01 as koen notes, this is one of those things that crops up on strange places Apr 27 12:48:29 bluelightning, https://github.com/sbabic/meta-swupdate/blob/master/recipes-extended/images/bbb-swu-image.bb Apr 27 15:47:58 Does OE dynamically construct the URI for pypi modules? Apr 27 15:48:25 I see a md5sum and sha256sum, but no URI Apr 27 15:51:17 Ooh, found my answer - yes it does. Apr 27 15:53:26 MWelchUK, glad to be of assistance Apr 27 15:57:25 Had a failure fetching python3-lxml, the constructed link is indeed broken. Wondering whether this is an isolated issue or whether pypi has changed how it stores it's downloads as the link from the website to the source is completely different. Apr 27 16:11:17 Nope - it seems pypi.class is comming up with https://pypi.python.org/packages/source/p/python3-lxml/python3-lxml-3.6.0.tar.gz rather than https://pypi.python.org/packages/source/l/lxml/lxml-3.6.0.tar.gz for meta-openembedded/meta-python/recipes-devtools/python/python3-lxml_3.6.0.bb. Apr 27 16:12:37 MWelchUK: iirc pypi.bbclass is private to your layer Apr 27 16:12:54 joshuagl: It's in meta-openembedded/meta-python/classes/pypi.bbclass Apr 27 16:13:43 MWelchUK: aha Apr 27 16:14:26 MWelchUK: do you have a different version of pypi.bbclass than the link you posted? Apr 27 16:14:45 Not as far as I know Apr 27 16:14:52 * MWelchUK goes to look in greater detail Apr 27 16:15:27 reading the code PYPI_PACKAGE should be set to the BPN (python3-lxml) with the python3 prefix removed Apr 27 16:15:52 unless the recipe which inherits pypi.bbclass is setting PYPI_PACKAGE to something else Apr 27 16:15:56 joshuagl: Nuts, it's like you had insider information ;-) Apr 27 16:16:19 I couldn't possible divulge that Apr 27 16:20:20 joshuagl: Thanks :-) Apr 27 16:25:24 np Apr 27 20:03:26 khem, ping Apr 27 22:52:06 armpit: pongg Apr 27 22:57:52 khem, do you know if you backport this busybox patch Apr 27 22:57:59 https://git.busybox.net/busybox/commit/?id=4ab372d49a6e82b0bf097dedb96d26330c5f2d5f Apr 27 22:59:12 yes we need it on master and krogoth Apr 27 22:59:50 k, I will send a patch Apr 27 23:00:03 thanks Apr 28 00:48:03 sent **** ENDING LOGGING AT Thu Apr 28 02:59:58 2016