Wednesday, 2018-05-09

armpitrburton, I will have to double check. I think I have everything in rocko except the libcrypt changes which are a problem.00:00
armpitrburton, its for morty ; ) to trouble shoot a problem in I saw in Ubunut 1700:01
armpitrburton, why are you awake?00:02
rburtonarmpit: literally just dropped from our planning meeting00:02
rburtonhooray tri-zone meetings, 11pm-1am for me00:02
armpitwow00:02
rburtonthe guy in penang, 6am-8am00:03
rburtonbut now, bedtime :)00:03
armpitnight00:03
rburtonarmpit: rocko failed selftest btw00:04
armpitI saw00:04
armpitthanks00:04
*** rburton <rburton!~textual@35.106.2.81.in-addr.arpa> has quit IRC00:04
*** jerdogma <jerdogma!~Adium@99-25-252-153.lightspeed.mdsnwi.sbcglobal.net> has joined #yocto00:15
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC00:28
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto00:28
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC00:29
*** jkridner|pd <jkridner|pd!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto00:29
-YoctoAutoBuilder- build #466 of nightly-musl-x86-64 is complete: Failure [failed BuildImages Running Sanity Tests] Build details are at https://autobuilder.yocto.io/builders/nightly-musl-x86-64/builds/46600:33
*** nathani__ <nathani__!~nathani@mail.validmanufacturing.com> has quit IRC00:39
-YoctoAutoBuilder- build #1018 of nightly-musl is complete: Failure [failed BuildImages Running Sanity Tests] Build details are at https://autobuilder.yocto.io/builders/nightly-musl/builds/101800:40
*** jerdogma <jerdogma!~Adium@99-25-252-153.lightspeed.mdsnwi.sbcglobal.net> has quit IRC00:51
*** martinkelly <martinkelly!~martin@97-113-238-55.tukw.qwest.net> has joined #yocto00:57
-YoctoAutoBuilder- build #982 of build-appliance is complete: Failure [failed BuildImages_1] Build details are at https://autobuilder.yocto.io/builders/build-appliance/builds/98200:57
-YoctoAutoBuilder- build #979 of nightly-rpm-non-rpm is complete: Failure [failed BuildImages Running Sanity Tests] Build details are at https://autobuilder.yocto.io/builders/nightly-rpm-non-rpm/builds/97900:59
*** GrimSleepless <GrimSleepless!~GrimSleep@qubcpq0634w-lp130-04-70-24-196-14.dsl.bell.ca> has quit IRC01:23
*** Ovidiu_WR__ <Ovidiu_WR__!~Ovidiu@89.121.200.102> has quit IRC01:26
*** majuk <majuk!~majuk@174-24-11-32.clsp.qwest.net> has joined #yocto01:32
*** learningc <learningc!~User@228.252.48.60.klj03-home.tm.net.my> has joined #yocto01:35
-YoctoAutoBuilder- build #643 of nightly-packagemanagers is complete: Failure [failed BuildImages Running Sanity Tests BuildImages_1 Running Sanity Tests_1 BuildImages_2 Running Sanity Tests_2] Build details are at https://autobuilder.yocto.io/builders/nightly-packagemanagers/builds/64301:36
*** majuk <majuk!~majuk@174-24-11-32.clsp.qwest.net> has quit IRC01:36
-YoctoAutoBuilder- build #985 of nightly-mips64 is complete: Failure [failed BuildImages Running Sanity Tests Building Toolchain Images Running SDK Sanity Tests Building Toolchain Images_1 Running SDK Sanity Tests_1] Build details are at https://autobuilder.yocto.io/builders/nightly-mips64/builds/98501:37
-YoctoAutoBuilder- build #971 of nightly-arm64 is complete: Failure [failed BuildImages Running Sanity Tests Building Toolchain Images Running SDK Sanity Tests Building Toolchain Images_1] Build details are at https://autobuilder.yocto.io/builders/nightly-arm64/builds/97101:40
-YoctoAutoBuilder- build #1006 of nightly-x86-64-lsb is complete: Failure [failed BuildImages Running Sanity Tests BuildImages_1] Build details are at https://autobuilder.yocto.io/builders/nightly-x86-64-lsb/builds/100601:45
*** ctlnwr <ctlnwr!~catalin@89.121.200.102> has quit IRC01:45
-YoctoAutoBuilder- build #992 of nightly-no-x11 is complete: Failure [failed BuildImages] Build details are at https://autobuilder.yocto.io/builders/nightly-no-x11/builds/99201:46
-YoctoAutoBuilder- build #1008 of nightly-ppc is complete: Failure [failed BuildImages Running Sanity Tests BuildImages_1 Building Toolchain Images Running SDK Sanity Tests Building Toolchain Images_1 BuildImages_2 Running ESDK Sanity Tests] Build details are at https://autobuilder.yocto.io/builders/nightly-ppc/builds/100801:46
*** martinkelly <martinkelly!~martin@97-113-238-55.tukw.qwest.net> has quit IRC01:47
*** dengke <dengke!~dengke@106.120.101.38> has quit IRC02:09
*** dengke <dengke!~dengke@106.120.101.38> has joined #yocto02:11
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has joined #yocto02:16
*** warthog9 <warthog9!warthog9@proxy.monkeyblade.net> has joined #yocto02:26
-YoctoAutoBuilder- build #1010 of nightly-multilib is complete: Failure [failed BuildImages_2 Running Sanity Tests_2 BuildImages_3 Running Sanity Tests_3 BuildImages_4] Build details are at https://autobuilder.yocto.io/builders/nightly-multilib/builds/101002:28
*** morphis__ <morphis__!~morphis@pD9ED6B4B.dip0.t-ipconnect.de> has joined #yocto02:50
*** morphis_ <morphis_!~morphis@pD9ED66B7.dip0.t-ipconnect.de> has quit IRC02:53
*** learningc <learningc!~User@228.252.48.60.klj03-home.tm.net.my> has quit IRC03:05
*** flihp <flihp!~flihp@76.243.124.132> has quit IRC03:17
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has quit IRC03:26
*** anujm <anujm!~anujm@192.198.146.171> has joined #yocto03:26
*** dreyna <dreyna!~dreyna@c-24-5-28-247.hsd1.ca.comcast.net> has quit IRC03:45
*** anujm <anujm!~anujm@192.198.146.171> has quit IRC03:59
*** morphis_ <morphis_!~morphis@pD9ED648A.dip0.t-ipconnect.de> has joined #yocto04:08
*** morphis__ <morphis__!~morphis@pD9ED6B4B.dip0.t-ipconnect.de> has quit IRC04:11
*** kaspter <kaspter!~Instantbi@115.192.223.124> has quit IRC04:13
*** kaspter <kaspter!~Instantbi@115.192.223.124> has joined #yocto04:17
-YoctoAutoBuilder- build #980 of nightly-world is complete: Failure [failed BuildImages] Build details are at https://autobuilder.yocto.io/builders/nightly-world/builds/98004:22
-YoctoAutoBuilder- build #978 of nightly-world-lsb is complete: Failure [failed BuildImages] Build details are at https://autobuilder.yocto.io/builders/nightly-world-lsb/builds/97804:22
-YoctoAutoBuilder- build #994 of nightly-deb-non-deb is complete: Failure [failed BuildImages Running Sanity Tests] Build details are at https://autobuilder.yocto.io/builders/nightly-deb-non-deb/builds/99404:22
-YoctoAutoBuilder- build #1007 of nightly-wic is complete: Failure [failed BuildImages_1 CreateWicImages CreateWicImages_1 CreateWicImages_2 BuildImages_3 CreateWicImages_3 CreateWicImages_4 CreateWicImages_5 BuildImages_7 CreateWicImages_8 CreateWicImages_9 CreateWicImages_10] Build details are at https://autobuilder.yocto.io/builders/nightly-wic/builds/100704:23
-YoctoAutoBuilder- build #1020 of nightly-x86 is complete: Failure [failed BuildImages Running Sanity Tests BuildImages_1 Building Toolchain Images Running SDK Sanity Tests Building Toolchain Images_1 Running SDK Sanity Tests_1 BuildImages_2 Running ESDK Sanity Tests] Build details are at https://autobuilder.yocto.io/builders/nightly-x86/builds/102004:24
-YoctoAutoBuilder- build #1002 of nightly-x86-lsb is complete: Failure [failed BuildImages Running Sanity Tests BuildImages_1] Build details are at https://autobuilder.yocto.io/builders/nightly-x86-lsb/builds/100204:24
-YoctoAutoBuilder- build #1026 of nightly-x86-64 is complete: Failure [failed BuildImages Running Sanity Tests BuildImages_1] Build details are at https://autobuilder.yocto.io/builders/nightly-x86-64/builds/102604:24
-YoctoAutoBuilder- build #994 of nightly-arm-lsb is complete: Failure [failed BuildImages Running Sanity Tests BuildImages_1] Build details are at https://autobuilder.yocto.io/builders/nightly-arm-lsb/builds/99404:24
-YoctoAutoBuilder- build #987 of nightly-mips is complete: Failure [failed BuildImages Running Sanity Tests BuildImages_1 Building Toolchain Images Running SDK Sanity Tests Building Toolchain Images_1 BuildImages_2 Running ESDK Sanity Tests] Build details are at https://autobuilder.yocto.io/builders/nightly-mips/builds/98704:24
-YoctoAutoBuilder- build #994 of nightly-ppc-lsb is complete: Failure [failed BuildImages Running Sanity Tests BuildImages_1] Build details are at https://autobuilder.yocto.io/builders/nightly-ppc-lsb/builds/99404:24
*** kaspter <kaspter!~Instantbi@115.192.223.124> has quit IRC04:38
*** kaspter <kaspter!~Instantbi@115.192.223.124> has joined #yocto04:38
*** blueness <blueness!~blueness@gentoo/developer/blueness> has quit IRC04:42
*** Ovidiu_WR <Ovidiu_WR!~Ovidiu@89.121.200.102> has joined #yocto04:42
*** blueness <blueness!~blueness@gentoo/developer/blueness> has joined #yocto04:51
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has joined #yocto05:01
*** ctlnwr <ctlnwr!~catalin@89.121.200.102> has joined #yocto05:15
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has quit IRC05:19
-YoctoAutoBuilder- build #999 of nightly-qa-extras is complete: Failure [failed BuildImages_2 BuildImages_10 BuildImages_12 BuildImages_13 BuildImages_14] Build details are at https://autobuilder.yocto.io/builders/nightly-qa-extras/builds/99905:20
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has joined #yocto05:20
-YoctoAutoBuilder- build #1058 of nightly-arm is complete: Failure [failed BuildImages Running Sanity Tests Building Toolchain Images BuildImages_1 Building Toolchain Images_1 Building Toolchain Images_2 Running SDK Sanity Tests Building Toolchain Images_3 BuildImages_3 Running ESDK Sanity Tests] Build details are at https://autobuilder.yocto.io/builders/nightly-arm/builds/105805:21
-YoctoAutoBuilder- build #983 of nightly-mips-lsb is complete: Failure [failed BuildImages Running Sanity Tests BuildImages_1] Build details are at https://autobuilder.yocto.io/builders/nightly-mips-lsb/builds/98305:22
-YoctoAutoBuilder- build #1081 of nightly is complete: Failure [failed] Build details are at https://autobuilder.yocto.io/builders/nightly/builds/108105:25
*** learningc <learningc!~User@124.13.85.122> has joined #yocto05:30
*** agust <agust!~agust@p50887D26.dip0.t-ipconnect.de> has joined #yocto05:30
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has quit IRC05:30
*** georgem_home <georgem_home!uid210681@gateway/web/irccloud.com/x-dpfasfghdbmbduvv> has quit IRC05:40
*** mcfrisk <mcfrisk!mcfrisk@kapsi.fi> has quit IRC05:48
*** on1x <on1x!~on1x@trader.teamfxp.co> has quit IRC06:07
*** dv_ <dv_!~dv@62-178-50-190.cable.dynamic.surfer.at> has quit IRC06:11
*** dv_ <dv_!~dv@62-178-50-190.cable.dynamic.surfer.at> has joined #yocto06:26
*** hamis <hamis!~irfan@110.93.212.98> has joined #yocto06:31
*** frieder <frieder!~frieder@mue-88-130-75-214.dsl.tropolys.de> has joined #yocto06:35
LetoThe2ndi did kick off a qemuarm core image minimal build on ec2 micro for the fun of it. 36hrs and counting.06:39
*** Kakounet <Kakounet!~Thunderbi@che44-1-88-163-84-4.fbx.proxad.net> has joined #yocto06:52
*** TobSnyder <TobSnyder!~schneider@ip9234aad3.dynamic.kabel-deutschland.de> has joined #yocto06:56
*** TobSnyder <TobSnyder!~schneider@ip9234aad3.dynamic.kabel-deutschland.de> has joined #yocto06:57
*** fl0v0 <fl0v0!~fvo@mue-88-130-111-254.dsl.tropolys.de> has joined #yocto06:58
*** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has joined #yocto06:59
*** CoRfr- <CoRfr-!~CoRfr@carmd-fwm01.sierrawireless.com> has quit IRC07:06
*** LocutusOfBorg <LocutusOfBorg!LocutusOfB@gateway/shell/panicbnc/x-qenxwanveuscjomt> has quit IRC07:11
*** LocutusOfBorg <LocutusOfBorg!LocutusOfB@gateway/shell/panicbnc/x-tkfbpayrkquilrvp> has joined #yocto07:12
*** sno <sno!~sno@b2b-78-94-80-58.unitymedia.biz> has quit IRC07:17
yoctiNew news from stackoverflow: Yocto 2.4.2 failed to do_package_qa task <https://stackoverflow.com/questions/50247702/yocto-2-4-2-failed-to-do-package-qa-task> || How to check for not equal to values in bb.utils.contains() <https://stackoverflow.com/questions/50247658/how-to-check-for-not-equal-to-values-in-bb-utils-contains> || Yocto build broken when setting a remote rpm repository with https <https://stackoverflow.com/questions/50230447/yocto-build-broken-when-setting-a-remote-rpm-repository-with-https>07:26
*** Bunio_FH <Bunio_FH!~bunio@81-18-201-214.static.chello.pl> has joined #yocto07:26
*** gtristan <gtristan!~tristanva@114.207.54.40> has joined #yocto07:29
*** rajm <rajm!~robertmar@167.98.27.229> has joined #yocto07:29
*** CoRfr <CoRfr!~CoRfr@carmd-fwm01.sierrawireless.com> has joined #yocto07:34
*** mcfrisk <mcfrisk!mcfrisk@kapsi.fi> has joined #yocto07:46
*** nayfe <nayfe!uid259604@gateway/web/irccloud.com/x-qidlhzcffybvncql> has quit IRC07:53
*** rajm <rajm!~robertmar@167.98.27.229> has quit IRC07:59
*** rajm <rajm!~robertmar@167.98.27.229> has joined #yocto07:59
*** kaspter <kaspter!~Instantbi@115.192.223.124> has quit IRC08:05
*** kaspter <kaspter!~Instantbi@115.192.223.124> has joined #yocto08:05
*** sveinse_ <sveinse_!~sveinse@156.92-221-160.customer.lyse.net> has joined #yocto08:09
sveinse_Where I can I find info about the relationship between PV, SRCPV and PKPV ?08:10
*** sveinse_ <sveinse_!~sveinse@156.92-221-160.customer.lyse.net> has quit IRC08:10
*** sveinse <sveinse!~sveinse@156.92-221-160.customer.lyse.net> has joined #yocto08:12
sveinse(lost connection for a sec there if someone replied)08:12
*** LocutusOfBorg <LocutusOfBorg!LocutusOfB@gateway/shell/panicbnc/x-tkfbpayrkquilrvp> has quit IRC08:13
*** LocutusOfBorg <LocutusOfBorg!LocutusOfB@gateway/shell/panicbnc/x-jpbtwkwcidpvytkw> has joined #yocto08:13
*** sno <sno!~sno@p200300C14BE23A0059ABE471EC3692D5.dip0.t-ipconnect.de> has joined #yocto08:16
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has joined #yocto08:23
*** colrack <colrack!~colrack@94.126.8.166> has joined #yocto08:24
*** colrack <colrack!~colrack@94.126.8.166> has quit IRC08:25
*** on1x <on1x!~on1x@trader.teamfxp.co> has joined #yocto08:52
*** varjag <varjag!~user@122.62-97-226.bkkb.no> has joined #yocto09:14
*** jerdogma <jerdogma!~Adium@99-25-252-153.lightspeed.mdsnwi.sbcglobal.net> has joined #yocto09:51
*** kaspter <kaspter!~Instantbi@115.192.223.124> has quit IRC09:53
*** LocutusOfBorg <LocutusOfBorg!LocutusOfB@gateway/shell/panicbnc/x-jpbtwkwcidpvytkw> has quit IRC09:55
*** LocutusOfBorg <LocutusOfBorg!LocutusOfB@gateway/shell/panicbnc/x-olneelradlccjktc> has joined #yocto09:59
*** kaspter <kaspter!~Instantbi@183.158.243.96> has joined #yocto10:03
*** jerdogma <jerdogma!~Adium@99-25-252-153.lightspeed.mdsnwi.sbcglobal.net> has quit IRC10:08
*** Bunio_FH <Bunio_FH!~bunio@81-18-201-214.static.chello.pl> has quit IRC10:12
*** angelo_ts <angelo_ts!~angelo_ts@unaffiliated/angelo-ts/x-4633355> has joined #yocto10:13
*** falk0n <falk0n!~falk0n@a109-49-51-30.cpe.netcabo.pt> has quit IRC10:15
angelo_tshi all, i am on a debian sid, and getting this error10:16
angelo_tsERROR: Task (virtual:native:/home/angelo/git/bounty/lm-toolchain-yocto/poky/meta/recipes-devtools/e2fsprogs/e2fsprogs_1.43.4.bb:do_compile) failed with exit code '1'10:16
angelo_tsmy collegues uses same yocto from our internal git, but they are on stable ubutnu distros and all works10:17
angelo_tsis there a way to fix this without impacting other guys that are on ubuntu stable and properly building ?10:18
*** Bunio_FH <Bunio_FH!~bunio@188.72.108.231> has joined #yocto10:18
osseWhen bitbake starts running it prints out the main build config vars as well as layer versions. Can I get this information in a script-friendly manner?10:26
*** Bunio_FH <Bunio_FH!~bunio@188.72.108.231> has quit IRC10:28
*** nighty- <nighty-!~nighty@kyotolabs.asahinet.com> has quit IRC10:29
*** kaspter <kaspter!~Instantbi@183.158.243.96> has quit IRC10:41
sveinseIs there a way to override the branch field only from local.conf for a recipe's SRC_URI="...;branch=..." ?10:42
sveinseI tried setting BRANCH_pn-recipename="", but for some reason in a task being run after do_unpack before do_patch it is still master10:44
*** Bunio_FH <Bunio_FH!~bunio@81-18-201-214.static.chello.pl> has joined #yocto10:45
*** kaspter <kaspter!~Instantbi@183.158.243.96> has joined #yocto10:46
sveinseI thought BRANCH_pn-* would work, I'm sure it did once. So either that has been removed from Rocko or the taskpoint after do_unpack before do_patch is too early for the repo to be checked out correctly10:46
malu1angelo_ts: I ran into e2fsprogs issues with ubuntu 18.04 host toolchain - solved by upgrading e2fsprogs to latest version available.10:49
angelo_tsmalu1, ok thanks10:49
angelo_tslikely i will have other issues about libc later10:49
malu1angelo_ts: yes, you might run into glibc 2.27 issues as I did10:50
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has quit IRC10:51
angelo_tsmalu1, yep, thats' it10:51
angelo_tswhat you did then ?10:51
malu1angelo_ts: if so you might considering using 'INHERIT_remove = "uninative"' which will make sure everything is built from scratch which solves glibc 2.27 not being detected.10:52
malu1as far as I understand the uninative stuff makes u use a prebuilt toolchain etc. which is not compatible with the latest glibc 2.27 changes.10:53
*** CoRfr- <CoRfr-!~CoRfr@carmd-fwm01.sierrawireless.com> has joined #yocto10:54
*** CoRfr <CoRfr!~CoRfr@carmd-fwm01.sierrawireless.com> has quit IRC10:54
*** kanavin <kanavin!ak@nat/intel/x-hwbgwxzzwvpkjeft> has quit IRC11:01
*** kanavin <kanavin!ak@nat/intel/x-nkkmeaqfmaakttez> has joined #yocto11:02
*** rburton <rburton!~textual@35.106.2.81.in-addr.arpa> has joined #yocto11:12
*** falk0n <falk0n!~falk0n@a109-49-51-30.cpe.netcabo.pt> has joined #yocto11:14
*** LocutusOfBorg <LocutusOfBorg!LocutusOfB@gateway/shell/panicbnc/x-olneelradlccjktc> has quit IRC11:17
*** LocutusOfBorg <LocutusOfBorg!LocutusOfB@gateway/shell/panicbnc/x-ebqcqbbjxgnvuria> has joined #yocto11:17
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC11:23
yoctiNew news from stackoverflow: If the same code is built at different folders using arm-poky-linux-gnueabi-gcc, the resulting binary will have different contents <https://stackoverflow.com/questions/50174593/if-the-same-code-is-built-at-different-folders-using-arm-poky-linux-gnueabi-gcc>11:27
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has joined #yocto11:31
*** malu1 is now known as malu11:33
*** _william_ <_william_!~william@LFbn-1-9177-74.w86-238.abo.wanadoo.fr> has quit IRC11:34
*** _william_ <_william_!~william@LFbn-1-9177-74.w86-238.abo.wanadoo.fr> has joined #yocto11:35
rburtonRP: did you already pick anuj's gst updates into next? (the v4 and v2 sent at 5am)11:40
RPrburton: yes11:42
rburtoncool11:42
*** Bunio_FH <Bunio_FH!~bunio@81-18-201-214.static.chello.pl> has quit IRC11:45
*** Bunio_FH <Bunio_FH!~bunio@2a02:a313:433c:cd00:219a:555a:f717:80f0> has joined #yocto11:47
rburtonargh looked at the wget fetcher again and now i want to rewrite it all in Requests11:52
*** gtristan <gtristan!~tristanva@114.207.54.40> has quit IRC11:54
*** Ramose <Ramose!c05e2222@gateway/web/freenode/ip.192.94.34.34> has quit IRC11:56
-YoctoAutoBuilder- build #980 of nightly-rpm-non-rpm is complete: Success [build successful] Build details are at https://autobuilder.yocto.io/builders/nightly-rpm-non-rpm/builds/98011:56
*** LocutusOfBorg <LocutusOfBorg!LocutusOfB@gateway/shell/panicbnc/x-ebqcqbbjxgnvuria> has quit IRC11:57
*** LocutusOfBorg <LocutusOfBorg!LocutusOfB@gateway/shell/panicbnc/x-xrgjzrfydjnolgpe> has joined #yocto11:58
*** vmesons <vmesons!~rmacleod@192-0-133-4.cpe.teksavvy.com> has quit IRC12:02
*** gabrbedd <gabrbedd!~beddingfi@li680-65.members.linode.com> has quit IRC12:03
-YoctoAutoBuilder- build #995 of nightly-deb-non-deb is complete: Success [build successful] Build details are at https://autobuilder.yocto.io/builders/nightly-deb-non-deb/builds/99512:10
-YoctoAutoBuilder- build #983 of build-appliance is complete: Success [build successful] Build details are at https://autobuilder.yocto.io/builders/build-appliance/builds/98312:15
RPrburton: the wget fetcher used to be so simple too :(12:18
angelo_tsmalu, many thanks12:18
angelo_tsso what you suggest as best way of working: INHERIT_remove = "uninative"   or   yocto in a container ?12:18
LetoThe2ndangelo_ts: certainly the container way. building a moving target on a moving host is very prone to break things, and not using uninative is a bandaid for this particular breakage only.12:19
angelo_tsLetoThe2nd, thanks. There was around a guide for yocto into container =?12:21
-YoctoAutoBuilder- build #1007 of nightly-x86-64-lsb is complete: Success [build successful] Build details are at https://autobuilder.yocto.io/builders/nightly-x86-64-lsb/builds/100712:21
-YoctoAutoBuilder- build #644 of nightly-packagemanagers is complete: Success [build successful] Build details are at https://autobuilder.yocto.io/builders/nightly-packagemanagers/builds/64412:21
maluangelo_ts: I'm not the right guy to answer that as I'm not sure what the full consequence is of not using uninative.12:22
LetoThe2ndangelo_ts: depends on your usage in the end. but a rather simple usecase is to just have fixed ubuntu version with all needed stuff installed, a user account, mount the work directory inside.12:22
RPrburton: hmm, failure in clutter-gst now :(12:23
rburtonRP: yeah just testing an upgrade for that now12:24
*** gtristan <gtristan!~tristanva@110.11.179.89> has joined #yocto12:25
rburtonRP: the qemu failure is most annoying, i wonder what caused that12:26
-YoctoAutoBuilder- build #1008 of nightly-wic is complete: Success [build successful] Build details are at https://autobuilder.yocto.io/builders/nightly-wic/builds/100812:28
*** LocutusOfBorg <LocutusOfBorg!LocutusOfB@gateway/shell/panicbnc/x-xrgjzrfydjnolgpe> has quit IRC12:30
*** LocutusOfBorg <LocutusOfBorg!LocutusOfB@gateway/shell/panicbnc/x-fnohferhrqdzjuim> has joined #yocto12:31
*** kanavin <kanavin!ak@nat/intel/x-nkkmeaqfmaakttez> has quit IRC12:33
RPrburton: qemu upgrade?12:34
*** kanavin <kanavin!ak@nat/intel/x-rsmbnrnzcwasxwtt> has joined #yocto12:34
rburtonoh yeah that would be it ;)12:34
*** vmesons <vmesons!~rmacleod@128.224.252.2> has joined #yocto12:35
rburtonoh right i turned on llvmpipe, that explains why mesa is taking an age to build12:37
*** jkridner|pd <jkridner|pd!~jkridner@pdpc/supporter/active/jkridner> has quit IRC12:40
-YoctoAutoBuilder- build #1027 of nightly-x86-64 is complete: Success [build successful] Build details are at https://autobuilder.yocto.io/builders/nightly-x86-64/builds/102712:46
*** zarzar <zarzar!~zarzar@184.75.233.58> has joined #yocto12:53
rburtonRP: clutter upgrade on the list13:04
*** vmesons <vmesons!~rmacleod@128.224.252.2> has quit IRC13:05
*** falk0n_ <falk0n_!~falk0n@a109-49-51-30.cpe.netcabo.pt> has joined #yocto13:06
*** falk0n <falk0n!~falk0n@a109-49-51-30.cpe.netcabo.pt> has quit IRC13:07
RPrburton: that fixes that failure?13:07
rburtonyeah13:08
*** morphis_ <morphis_!~morphis@pD9ED648A.dip0.t-ipconnect.de> has quit IRC13:08
RPrburton: safe to pull that, drop the qemu upgrade and merge or needs another run?13:10
rburtoni'd be happier with another run tbh13:12
rburtoni'll have a quick look at what changed in qemu13:12
JaMawhat is the "qemu failure"?13:20
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto13:20
JaMaI've noticed that you reverted the earlier CVE patch before doing the upgrade, I have v2 which removed the patch together with the upgrade, but that should end-up the same13:20
rburtonJaMa: yeah that was meant to be squashed in before merge13:20
rburtoni think we need to explicitly disable sdl in the no-x builds as that is now depending on x keysyms13:21
*** falk0n_ <falk0n_!~falk0n@a109-49-51-30.cpe.netcabo.pt> has quit IRC13:21
JaMaso qemu fails to build for you?13:22
rburtonif you remove x11 distro feature, yes13:22
JaMahere I'm building it with spice/virgl/gtk3 enabled, so I might see different issue13:22
JaMatarget qemu or nativesdk or native?13:23
RPJaMa: target13:23
*** falk0n <falk0n!~falk0n@a109-49-51-30.cpe.netcabo.pt> has joined #yocto13:23
rburtontarget, https://autobuilder.yocto.io/builders/nightly-no-x11/builds/993/steps/BuildImages/logs/stdio13:23
*** TobSnyder <TobSnyder!~schneider@ip9234aad3.dynamic.kabel-deutschland.de> has quit IRC13:24
JaMaI'll trigger the build to see if I can reproduce here with no-x11 distro13:24
JaMaheh qemu was skipped: Recipe is blacklisted: depends on blacklisted libsdl13:25
JaMaconf/distro/include/webos-recipe-blacklist-world.inc:PNBLACKLIST[libglu] ?= "broken: we don't build libGL with mesa: cannot find -lGL"13:26
JaMaconf/distro/include/webos-recipe-blacklist-world.inc:PNBLACKLIST[libsdl] ?= "depends on broken libglu"13:26
rburtonheh13:28
rburtonlibglu should build against mesa-gl just fine13:29
JaMaI've added these long time ago (definitely before dylan was released) and they wasn't revisited since then (except very few cases when someone actually needed something blacklisted)13:32
JaMabut libsdl2 is better anyway, because it supports accelerated gl13:33
-YoctoAutoBuilder- build #995 of nightly-ppc-lsb is complete: Success [build successful] Build details are at https://autobuilder.yocto.io/builders/nightly-ppc-lsb/builds/99513:33
*** marka <marka!~masselst@128.224.252.2> has joined #yocto13:33
*** hamis <hamis!~irfan@110.93.212.98> has quit IRC13:38
-YoctoAutoBuilder- build #986 of nightly-mips64 is complete: Success [build successful] Build details are at https://autobuilder.yocto.io/builders/nightly-mips64/builds/98613:41
-YoctoAutoBuilder- build #1021 of nightly-x86 is complete: Success [build successful] Build details are at https://autobuilder.yocto.io/builders/nightly-x86/builds/102113:54
*** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has quit IRC13:58
-YoctoAutoBuilder- build #995 of nightly-arm-lsb is complete: Success [build successful] Build details are at https://autobuilder.yocto.io/builders/nightly-arm-lsb/builds/99514:05
*** morphis <morphis!~morphis@pD9ED648A.dip0.t-ipconnect.de> has joined #yocto14:05
*** vmeson <vmeson!~rmacleod@128.224.252.2> has joined #yocto14:07
*** varjag <varjag!~user@122.62-97-226.bkkb.no> has quit IRC14:10
-YoctoAutoBuilder- build #1011 of nightly-multilib is complete: Success [build successful] Build details are at https://autobuilder.yocto.io/builders/nightly-multilib/builds/101114:22
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC14:22
-YoctoAutoBuilder- build #984 of nightly-mips-lsb is complete: Success [build successful] Build details are at https://autobuilder.yocto.io/builders/nightly-mips-lsb/builds/98414:25
-YoctoAutoBuilder- build #972 of nightly-arm64 is complete: Success [build successful] Build details are at https://autobuilder.yocto.io/builders/nightly-arm64/builds/97214:28
*** dlan <dlan!~dennis@gentoo/developer/dlan> has quit IRC14:29
*** dlan <dlan!~dennis@gentoo/developer/dlan> has joined #yocto14:30
*** majuk <majuk!~majuk@174-24-11-32.clsp.qwest.net> has joined #yocto14:31
*** rsalveti is now known as rsalveti__14:32
*** rsalveti__ is now known as rsalveti14:33
-YoctoAutoBuilder- build #1000 of nightly-qa-extras is complete: Success [build successful] Build details are at https://autobuilder.yocto.io/builders/nightly-qa-extras/builds/100014:41
u1106_I reorganized my local SRC_MIRROR and now 1 do_fetch task fails. The src file in question looks good to me in the reorganized mirror. The do_fetch log does not really tell from where it tried to get the file. Can the logging level of the fetcher class be increased?14:44
*** AbleBacon <AbleBacon!~AbleBacon@unaffiliated/ablebacon> has joined #yocto14:44
*** majuk <majuk!~majuk@174-24-11-32.clsp.qwest.net> has quit IRC14:48
-YoctoAutoBuilder- build #1059 of nightly-arm is complete: Success [build successful] Build details are at https://autobuilder.yocto.io/builders/nightly-arm/builds/105914:49
*** majuk <majuk!~majuk@174-24-11-32.clsp.qwest.net> has joined #yocto14:51
*** vmeson <vmeson!~rmacleod@128.224.252.2> has quit IRC14:52
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has quit IRC14:54
*** psadro <psadro!~Thunderbi@2620:0:ed0:800a:6683:415a:bf63:3223> has quit IRC15:03
RPu1106_: you could try running the task as bitbake <target> -c fetch -DDDv15:04
*** lfa <lfa!~lfa@217.19.35.51> has quit IRC15:07
-YoctoAutoBuilder- build #1009 of nightly-ppc is complete: Success [build successful] Build details are at https://autobuilder.yocto.io/builders/nightly-ppc/builds/100915:11
*** vmeson <vmeson!~rmacleod@128.224.252.2> has joined #yocto15:16
*** pohly <pohly!~pohly@p54849CF1.dip0.t-ipconnect.de> has quit IRC15:18
*** rajm <rajm!~robertmar@167.98.27.229> has quit IRC15:21
*** Bunio_FH <Bunio_FH!~bunio@2a02:a313:433c:cd00:219a:555a:f717:80f0> has quit IRC15:24
*** Kakounet <Kakounet!~Thunderbi@che44-1-88-163-84-4.fbx.proxad.net> has quit IRC15:28
rburtonJaMa: looks like the qemu upgrade makes the assumption that sdl == x11, so we need to guard the sdl packageconfig with x11 DISTRO_FEATURE checks.  also change to libsdl2 at the same time?15:34
JaMarburton: there are more changes needed to make libsdl2 really usable, see: http://git.openembedded.org/openembedded-core-contrib/log/?h=jansa/qemu15:36
rburtonok fine by me15:36
rburtonlibsdl 1.x is dead isn't it?15:37
*** morphis <morphis!~morphis@pD9ED648A.dip0.t-ipconnect.de> has quit IRC15:37
rburtonJaMa: replied on list15:38
JaMaok, will send v2 after reproducing this15:39
rburtoni can replicate just by removing x11 from distro features15:40
rburtonso should be easy enough15:40
u1106_RP: I don't see that that gives me any more information. There is a lots of additional information concerning all the steps before it does the do_fetch. But I don't think that is relevant to my problem. The information inside tmp/work/foo/bar/temp/log.do_fetch.12345 does not get any more detailed :(15:41
kergothdo_fetch's log should show every mirror url being checked, as well as info about the url processing done by PREMIRRORS15:43
RPu1106_: I agree with kergoth, the fetch logs usually are pretty verbose :/15:44
kergothi usually find the 'returning ..' messages that show what substitutions were applied in mirror processing to be helpful when diagnosing mirror issues15:45
kergothmake sur ethe pathsss are correct15:45
u1106_hmm, I don't see that. Will compare with a sucessful do_fetch15:45
-YoctoAutoBuilder- build #1003 of nightly-x86-lsb is complete: Success [build successful] Build details are at https://autobuilder.yocto.io/builders/nightly-x86-lsb/builds/100315:47
tlwoernerrburton: ping?15:50
rburtontlwoerner: wot15:50
tlwoernerwrt the github.com/${PN}/archive issue15:50
tlwoernerswitching to github.com/${PN}/releases is considered okay?15:50
rburtongenerally not as thats the same url15:50
rburtonthe acceptable fixes are 1) git fetch 2) maintainer-uploaded tarball15:51
*** morphis <morphis!~morphis@pD9ED648A.dip0.t-ipconnect.de> has joined #yocto15:51
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has joined #yocto15:51
rburtonnote that the actual tarball links in /releases/ are typically actually /archive/15:51
rburtonunless its a maintainer uploaded tarball, which is fine15:52
tlwoernerhttp://git.openembedded.org/openembedded-core/commit/?id=9c668f9ff989a34e615e2ecc051dadbfe24a5bb415:52
rburtonyes, see https://github.com/logrotate/logrotate/releases15:52
rburtonlogrotate-3.14.0.tar.gz is a maintainer-uploaded tarball15:52
rburton"Source code" is a /archive/ tarball15:52
rburtoncompare with https://github.com/madler/pigz/releases which doesn't have maintainer-uploaded tarballs15:53
tlwoernerah, okay15:53
rburtonthe tarball URL for the uploaded tarballs is eg https://github.com/logrotate/logrotate/releases/download/3.14.0/logrotate-3.14.0.tar.gz15:55
rburtonnote the lack of /archive/15:55
*** WillMiles <WillMiles!~Will@static-209-87-231-80.storm.ca> has joined #yocto15:56
yoctiNew news from stackoverflow: In devtool command line tool is finish subcommand removed or replaced? <https://stackoverflow.com/questions/50257348/in-devtool-command-line-tool-is-finish-subcommand-removed-or-replaced>15:57
tlwoernerrburton: i was hoping to find an example in oe-core of switching from github archive to git, it looks like all the cleanups that were done, were all able to switch to developer-generated tarballs15:59
rburtontlwoerner: switching to git is trivial, just change the src_uri and set S=WORKDIR/git16:00
tlwoernerrburton: and i'll need a SRCREV?16:00
tlwoernerdo i need to change the name of the recipe from ${PN}_${PV}.bb to ${PN}_git.bb ?16:01
rburtonyeah, set it to the sha of the tag16:01
rburtonno need to rename if it continues to be based on releases16:01
tlwoernerok, thanks :-)16:02
rburtonimho, _git recipes should be reserved for recipes which track arbitrary commits, not releases16:02
rburtonthe version is still valid, even if it does fetch over git instead of tarball16:02
*** WillMiles <WillMiles!~Will@static-209-87-231-80.storm.ca> has quit IRC16:03
*** WillMiles <WillMiles!~Will@static-209-87-231-80.storm.ca> has joined #yocto16:03
*** fl0v0 <fl0v0!~fvo@mue-88-130-111-254.dsl.tropolys.de> has quit IRC16:04
JaMaFWIW: I prefer _git.bb and PV set inside, that way setting SRCREV_pn-foo somewhere won't produce so confusing results16:05
rburtonFIGHT!16:05
JaMawe have recipes-connectivity/connman/connman_1.33.bbappend which sets PV to 1.12+git which annoys me every time16:07
JaMait's only slightly better than duplicating whole recipe in our layer with _git.bb name or using require recipes-connectivity/connman/connman_1.33.bb inside of connman_git.bb which sets 1.12+git16:08
JaMabut I realize that in this case the connman_1.33.bb isn't even fetching from git.. :016:09
tlwoernerwouldn't that be a bug (i.e. the recipe name is 1.33 but inside it sets PV to 1.12)?16:09
JaMarecipe name matches with what the recipe fetches, but our bbappend changes it to fetch something else from our forked connman16:09
tlwoernerobviously connman is the exception, not the rule, but in any case i think changing the name to _git.bb makes more sense since with future version bumps only the SRCREV inside the recipe needs changing, not the SRCREV plus recipe name16:12
*** welhm <welhm!~welhm@zimbra.welvaarts.com> has quit IRC16:13
-YoctoAutoBuilder- build #988 of nightly-mips is complete: Success [build successful] Build details are at https://autobuilder.yocto.io/builders/nightly-mips/builds/98816:21
-YoctoAutoBuilder- build #1082 of nightly is complete: Success [build successful] Build details are at https://autobuilder.yocto.io/builders/nightly/builds/108216:24
*** martinkelly <martinkelly!~martin@97-113-238-55.tukw.qwest.net> has joined #yocto16:25
u1106_RP: kergoth: Right. For a recipe with a working do_fetch I get a lot of information in log.do_fetch16:25
u1106_E.g the "returning" line mentioned by kergoth16:25
u1106_> DEBUG: For url http://downloads.yoctoproject.org/mirror/sources/git2_github.com.file.file.git.tar.gz returning file:///usr/local/share/src_mirror/git2_github.com.file.file.git.tar.gz16:25
u1106_But for the failing one I get really no info where it tries to search https://pastebin.com/X6D83t1516:25
yoctiNew news from stackoverflow: Yocto build succeeds, but warning about missing RDEPENDS <https://stackoverflow.com/questions/50257995/yocto-build-succeeds-but-warning-about-missing-rdepends>16:28
*** marka <marka!~masselst@128.224.252.2> has quit IRC16:28
u1106_I have also straced both task. For the suceeding one it does a couple of lstat() calls on my local src mirror and then 2 stat() calls on /usr/local/share/src_mirror/git2_github.com.file.file.git.tar.gz and the the symlink to downloads16:30
RPu1106_: that looks very like the recipe in question has a "floating" SRCREV, it therefore has to look at the repo to see what the current revision is16:33
u1106_in the failing case it does only the lstat() calls on the source mirror, but never tries to stat() /usr/local/share/src_mirror/git2_github.com.IntelRealSense.librealsense.git.tar.gz , which I guess should should be the file it needs. Nor on anything else16:33
RPu1106_: when it can't do that, it fails16:33
u1106_RP: that could be. I guess this package has never been built offline before here16:34
RPu1106_: we try and educate people not to have floating revisions but in the connected world we live in, its hard for people to understand why :/16:34
RPu1106_: it could also be a "name" it has to resolve and that has to be done against the canonical upstream since it can change16:35
moto-tim1lmbench is failing to build because it can't find rpc/rpc.h any ideas what changed in the last 24 hours that would break that?16:35
RPmoto-tim1: the glibc changes from khem?16:35
u1106_so I guess I do a bbappend and force it to known good version?16:35
moto-tim1RP: that was my first guess16:35
RPmoto-tim1: we dropped large chunks of the rpc stack from glibc16:35
RP(in keeping with what upstream are doing)16:36
RPu1106_: you can probably even do it from a config, but ye16:36
RPyes16:36
moto-tim1RP: ok. well, lmbench is probably in need of an update then :)16:36
RPmoto-tim1: a depends on one of the new recipes may be enough (or may not)16:37
moto-tim1RP: right. just got that from the commit log :)16:40
* moto-tim1 thanks khem for breadcrumbs16:41
*** ausjke <ausjke!~xxiao@104.200.25.19> has joined #yocto16:48
tlwoernerrburton: it seems to be a convention that when switching a recipe from a tarball to git that one updates the PV to include git? e.g. PV = "8.40-1+git${SRCPV}"16:48
tlwoerneror is that more often the convention when the sha is between releases?16:48
rburtonconvention is a strong word :)16:48
rburtonif the sha is the tag then i prefer just eg PV=8.4016:48
tlwoerneri.e. the default16:48
rburtonthe fact that it comes via a git clone is a detail that doesn't matter16:48
ausjkeintel is backing out from iot, wind-river,... so many things in embedded(which is not a surprise), will that eventually impact yocto somehow16:49
rburtonausjke: if you know what the future holds for wind river then i think you know more than wind river does...16:49
tlwoernerausjke: the fact is things will change, the question is whether those changes will be good or bad16:50
tlwoernerausjke: but even if things might be bad initially, good things often have a way of righting themselves :-)16:50
ausjkehope for the best, i guess16:50
* ausjke is trying to hard to figure out intel's success in embedded field for the last 2 decades...sad16:51
tlwoernerausjke: in the beginning, there weren't a lot of people using OE, so it was good having someone with money driving it16:52
tlwoerneri'm hoping (and somewhat optimistic) that the project has reached and passed the tipping point where there is enough involvement that it can continue without that strong backing16:53
Croftontlwoerner, it reached the tipping point before Intel showed up :)16:59
u1106_RP: when specifying a SRCREV I end up with: ERROR: librealsense2-2.10.0-r0 do_fetch: Fetcher failure: Conflicting revisions (bc56b2dcfcf844e39ae2a9c953eaeb35b0706ae4 from SRCREV and v2.10.0 from the url) found, please specify one valid value17:00
u1106_The URI is git://github.com/IntelRealSense/librealsense.git;tag=v${PV}17:00
*** Jefro <Jefro!~josiermi@134.134.139.72> has joined #yocto17:00
kergothconsidering we started OE in 2002, I think that's a safe statement to make, yes :)17:00
*** brrm <brrm!~brrm@HSI-KBW-46-223-101-70.hsi.kabel-badenwuerttemberg.de> has quit IRC17:00
tlwoernerCrofton: but they pay many of the gurus who really drive the project today, if those gurus go out and get jobs that have nothing to do with OE, it might be hard for the community to find those sorts of contributors17:00
tlwoernerfor a little while, anyway :-)17:01
u1106_can a tag not working in offline build??? I do have the tag on my mirror, but that should be irrelevant. From strace I know that it does not even access the mirror17:01
kergothI doubt most of the oe experts are going to drop oe work unless there's no other choice, as deep expertise in anything is valuable17:01
frayfor an SCM, you can use a tag, but you need a local (on your disk) mirror for that repository..17:01
frayit's a known limitation17:01
kergothi know i wouldn't, at least for the day job, unless i had to17:01
fraykergoth, finding an employer has it's ups and downs, even for 'experts'..  it's amazing how many people want me to move to work for them..  (And these are only tangentally related to OE)17:02
frayin the end everyone is replacable.. the catch is -how- long and -how- expensive17:03
kergoththat's true, i do shovel a lot of recruiter mails into a label in gmail on a fairly regular basis17:03
rburtontlwoerner: 'many' is a bit of a stretch.  'some'17:03
kergothbut still, i expect most tend to stay where their years of expertise have led them, unless they're particularly bored17:03
*** brrm <brrm!~brrm@HSI-KBW-46-223-101-70.hsi.kabel-badenwuerttemberg.de> has joined #yocto17:03
Croftonkergoth, ++17:03
kergothcourse there's that old quote saying if you're the expert in your team, you should find a new team, so you don't stagnate..17:04
kergothbut *shrug* :)17:04
frayI find that a bit of a BS statement myself..17:04
RPu1106_: you cannot use a tag, no17:04
kergothagreed17:04
Croftonlol true :)17:04
frayjust because you are an expert doesn't mean you stagnate..  but it's up to YOU to figure out where to keep looking17:04
RPu1106_: it has to be "resolved" to a commit and you need the upstream repo for that17:04
kergothand you can gain deeper and wider knowledge even just mentoring and teaching once your'e in a ssenior role17:05
frayRP/u1106_ which is why a local copy of the upstream repo can 'solve' the issue..  but may not really be what you want17:05
*** gtristan <gtristan!~tristanva@110.11.179.89> has quit IRC17:05
kergothplus can branch off into other internal projects and lead other teams to expand17:05
fraymy personal goal is to work myself out of the job I'm currently doing..17:05
fraythat doesn't stop me from being an 'expert' in what I'm currently doing.. but it does continue to make me useful..17:05
zeddiimy personal goal is to retire ;)17:06
CroftonTell your bosses people got to eat17:06
tlwoernerfray: the chimney thing?17:06
fray(note, I don't really consider myself an expert in a lot of things others might -- but someone who is smart enough to figure out what is needed when it's needed..)17:06
fraytlwoerner :)17:06
kergothI need to start doing some side work, cause i'm definitely not learning as much as i used to17:06
kergothgetting rusty in some areas17:06
fray(for those w/o the chimney reference: http://kernel.crashing.org/fray/chimney/)17:06
fraywhat I spent part of my last two weekends on..17:06
frayso I can not only 'build' software, but I can remove brick..17:07
fraysee I DO do hardware!17:07
tlwoernerkergoth: switching OE from python to rust? (i.e. getting rusty...)17:07
kergothha17:07
fray(lol and the 0333 picture, the wall is straight -- welcome to picture stitching -- makes it look fish-eye)17:07
zeddiifray. what's the terrible upstream latency on that server.17:07
zeddiitsk. tsk.17:08
zeddii3rd world country or something.17:08
fraysorry, my DSL only has a 2-5MB/s upload.. :P17:08
fraythe pictures are 'kinda big'17:08
tlwoernerzeddii: says the guy from the country with the worst internet of all developed countries...17:08
zeddiishhhh.17:08
kergothi don't want to retire, i'd rather just gradually reduce the # of hours per work of work, do a ssemi-retirement thing17:08
frayoccasionally they add additional string across the border....17:09
fraykergoth, my goal (which I won't meet) is to retire in my early 50's..  then in 203x, come back and fix the UNIX time problem for 4x my normal rates.. ;)17:09
zeddiifray. stop all the gambling and drugs. you'll retire faster.17:10
fraylol, I thought gambling (stock market) was how you retired faster17:10
* tlwoerner wants to be a lumberjack17:11
tlwoerneri'm a lumberjack and i'm okay, i sleep all night and i work all day..17:11
frayand ya, my 'drug' (caffine and alcohol) habit can get expensive.. don't drink much -- but I like expensive Scotch.. :|17:11
kergothha, haven't heard the lumberjack song in ages17:12
fraytlwoerner I've given up on lumberjack -- but may have to restart..  I can't get anyone to call me back about the trees on my property..17:12
u1106_RP: fray: Sorry, don't understand why relsoving a tag would need network connection. I can do it locally in my git2/... directory17:12
u1106_$ git rev-parse refs/tags/v2.1017:12
u1106_bc56b2dcfcf844e39ae2a9c953eaeb35b0706ae417:12
fraydamnit I'll PAY you to take them down safely.. but NO... you wouldn't want ot call me back17:12
zeddiitlwoerner. funny. I have a friend that is actually a lumberjack. that dude has some serious heavy equipment!17:12
tlwoernernetflix canada just added a bunch of monty python17:12
zeddiijust stick with trailer park boys ;) :D17:13
frayu1106_ bitbake fetcher -always- goes out and resolves tags from a remote location.. tags can 'change', so it needs to make sure the upstream has not changed17:13
frayif you create a local mirror of the upstream, it will still go out to the mirror (which happens to be on your disk) ... but then you are responsible for updating your mirror async of the build system17:13
*** morphis <morphis!~morphis@pD9ED648A.dip0.t-ipconnect.de> has quit IRC17:14
fraychanging from a tag to a commit ID, means that it's not non-changing -- and if the commit is on the local system there is no reason to go look at the upstream17:14
u1106_you are right, they *could* change. Although I would call that very bad practice17:14
tlwoernerhttps://plus.google.com/+TrevorWoerner/posts/2Kb9nDizNue17:14
frayu1106_ tags change all the time, for better or worse..17:14
tlwoernerzeddii: have you tried any of their drinks?17:15
fraywhen I have restrictions for internet access, I use a local mirror of the remote git repositories -- and tell bitbake to use my mirror..17:15
u1106_ok, I see the point and I will find a workaround. Thanks for your help everybody17:15
frayworkaround is 'easy', but it does mean you have to manage it17:15
fray(linux-yocto is one that I do this with..)17:16
*** sno <sno!~sno@p200300C14BE23A0059ABE471EC3692D5.dip0.t-ipconnect.de> has quit IRC17:16
frayI create a layer that has a git directory and local mirrors of the contents..)17:16
zeddiitlwoerner. not yet, but that's my retirement plan on the east coast! :D17:16
frayPREMIRRORS_prepend = " \17:16
fray     git://git.yoctoproject.org/linux-yocto-4.12.git git://${LAYERDIR}/git/linux-yocto-4.12.git;protocol=file \n \17:16
fray     git://git.yoctoproject.org/yocto-kernel-cache git://${LAYERDIR}/git/yocto-kernel-cache.git;protocol=file \n \17:16
fray"17:16
tlwoernerzeddii: http://www.lcbo.com/lcbo/product/liquormen-s-dirty-ol-cad-whisky-trailer-park-boys/480442 is surprisingly good!17:17
fraytlwoerner I had no idea anyone would 'train a novice' in this..17:17
frayI'm just used to 'grab the chain saw.. don't be an idiot'17:17
zeddiilooks good!17:18
frayJoe MacDonald is the one who finally found me a Scotch I liked.. I still don't like Bourbon or 'Tennesse Wiskey'17:18
tlwoernerfray: nah, that's old skool, turns out there's a whole bunch of interesting, new, techniques17:18
frayproblem with the one jjm found me was it's $150 a bottle.. :P17:18
fraytlwoerner my issue isn't the cutting down.. it's all of the work of taking care of it once it's down..17:19
u1106_so the point is that the mirror needs to contain a true git repo. Not such tar tarball that I once copied from downloads? (Even if that tarball contains a git repo). Or what exactly makes the fetcher happy to *not* trying the network?17:19
fray(but the one tree near my house is hollow inside, and I'd be more likely to hit the house without appropriate machinery.. which is why I need a professional -- if they're around, there there are other trees I'd like them to remove..17:19
frayu1106_ yes17:19
frayjust close the original repository with git clone .... --bare --mirror17:19
kergothu1106_: set SRCREV to a commit id, don't usse ;tag=, and it won't need to contact the remote17:19
fraybut like I said, you are on your own for keeping it in sync with the upstream though17:20
*** georgem <georgem!~georgem@216.21.169.52> has quit IRC17:20
fraybut what RP/kergoth said.. move to commit id's and you don't have this issue any longer17:20
fray(I have things I need to track tags and branches on..  thus the mirroring strategy)17:20
tlwoernerfray: just like with tree falling, the branches are a pain ;-)17:21
frayexactly17:22
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has quit IRC17:22
tlwoernerfray: the course was basically a two-day, hands-on expansion of https://www.youtube.com/watch?v=7FRKU4RmeD017:23
*** georgem <georgem!~georgem@216.21.169.52> has joined #yocto17:23
frayone thing (for tree falling) I don't have but should buy are the kevlar chaps..  I'm always worried the saw will skip and I'll severe a leg.. ;P17:24
tlwoerneryep, i've seen that happen, and i've got myself a pair17:24
frayI've got my MontaVista Hard Hat Linux - Hard Hat (yes it's actually a real hardhat w/ a log on it)...  face shield, gloves, etc...17:24
u1106_kergoth: fray: so I ended up with setting the SRC_URI in a bbappend, to get rid of the tag set by the upstream recipe. Ugly maintenance issue, but do_fetch is happy now17:25
frayyes.. that works.. in a few cases, I've had to write some anonymous python to rewrite the existing SRC_URI... but it's all doable17:26
u1106_Ok, thanks everbody17:26
fray(if you know others will be doing bbappens on the SRC_URI -- just replacing it with your own value can cause problems.. thus the anon python chunk to do it 'inline')..17:26
frayI'd consider that an 'advanced' usecase though17:26
kergothyeah that's what i was going to suggest, d.setVar('SRC_URI', d.getVar('SRC_URI', expand=False).replace(';tag=foo')) or whatever in anonymous python17:27
fraykergoth, exactly.. annoying but owrks17:27
fray(actually going back and checking, I wasn't able to do it in an anon sectionf or some reason -- in this case -- but had to do it via a handler in RecipePreFinalise.. :P  something to do with processing order if I remember right...17:28
kergothhuh, wonder whyt hat is. woudln't expect PV/SRCPV to process before anonfuncs run17:29
fraythats what it was!17:30
u1106_so is the replace('tag'...) any safer the just setting a complete new SRC_URI. I mean if the upstream recipe / tag / sha1 changes I need to make a manual update anyway, don't I?17:30
fraybecause it used a tag.. the PV/SRCPV was processed BEFORE the anon python.. so it was still contacting the remote.. :P17:31
frayso I had to move it to a prefinalize handler.. ;P17:31
kergothah, interesting17:31
frayI seem to also recall it had something to do with the hash values changing after the anon python as well.. (due to the PV/SRCPV)17:31
kergothi kind of wish we had the ability to run arbitrary little blocks of code as pre/post expansion hooks on particular variables. sort of doable by using inline python that returns the empty string, but..17:32
u1106_could I make a "selftest" into my bbappend so that the build fails if the checksum of the upstream recipe changes or if the PV changes? Because then I should never miss my manual maintenance in the bbappend17:35
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has joined #yocto17:35
u1106_well actually for the changed PV I don't need to test, Whenever it changes my append will no longer be appended and do_fetch will fail again if they still use the tag in the SRC_URI17:37
*** toanju <toanju!~toanju@x5ce5820e.dyn.telefonica.de> has joined #yocto17:37
*** scottrif <scottrif!~scottrif@47-40-108-60.dhcp.knwc.wa.charter.com> has joined #yocto17:44
*** frieder <frieder!~frieder@mue-88-130-75-214.dsl.tropolys.de> has quit IRC17:52
kergothyou can do whatever you want in anonymous python. so yeah, you could easily extract the tag from the uri and if it changes error out indicating you need to adjust SRCREV to match17:53
kergothi've actually done that before17:53
*** marka <marka!~masselst@128.224.252.2> has joined #yocto17:56
kergothhttp://blogs.msdn.microsoft.com/commandline/?p=299517:58
*** dreyna <dreyna!~dreyna@c-24-5-28-247.hsd1.ca.comcast.net> has joined #yocto17:58
*** JaMa <JaMa!~martin@217.30.68.212> has quit IRC18:03
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has quit IRC18:11
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has joined #yocto18:12
*** adelcast <adelcast!~adelcast@130.164.62.135> has left #yocto18:14
*** majuk <majuk!~majuk@174-24-11-32.clsp.qwest.net> has quit IRC18:14
*** majuk <majuk!~majuk@174-24-11-32.clsp.qwest.net> has joined #yocto18:15
*** moto-tim1 <moto-tim1!~ttorling@134.134.139.75> has quit IRC18:17
*** moto-timo <moto-timo!~ttorling@134.134.139.75> has joined #yocto18:17
*** moto-timo <moto-timo!~ttorling@134.134.139.75> has quit IRC18:17
*** moto-timo <moto-timo!~ttorling@fsf/member/moto-timo> has joined #yocto18:17
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has quit IRC18:17
*** majuk_ <majuk_!~majuk@174-24-11-32.clsp.qwest.net> has joined #yocto18:18
*** majuk <majuk!~majuk@174-24-11-32.clsp.qwest.net> has quit IRC18:20
*** majuk_ <majuk_!~majuk@174-24-11-32.clsp.qwest.net> has quit IRC18:22
OutBackDingowhats with the yocvto rpi 3 builds latly18:23
*** CoRfr- <CoRfr-!~CoRfr@carmd-fwm01.sierrawireless.com> has quit IRC18:25
*** rcw <rcw!~rcw@65-110-208-159.cpe.pppoe.ca> has joined #yocto18:28
*** scottrif <scottrif!~scottrif@47-40-108-60.dhcp.knwc.wa.charter.com> has quit IRC18:45
*** u1106_ is now known as u110618:46
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has joined #yocto18:52
khemmoto-timo: you might want to look into https://github.com/kraj/meta-openembedded/commits/kraj/master if you are trying latest glibc rework18:53
khemhttps://github.com/kraj/meta-openembedded/commit/25cba67d6f8338df06d43d94c3882892b8c9ef6518:53
khemis what you are looking for18:54
moto-timokhem: RP was right that lmbench needs DEPENDS on rpcsvc-proto. does that only apply for glibc (not libc-musl)??18:55
moto-timokhem: so it should be DEPENDS_append_glibc = " rpcsvc-proto" ?18:56
yoctiNew news from stackoverflow: Can't connect to free wifi network with iwconfig in Linux embedded [closed] <https://stackoverflow.com/questions/50173011/cant-connect-to-free-wifi-network-with-iwconfig-in-linux-embedded>18:58
*** CoRfr- <CoRfr-!~CoRfr@carmd-fwm01.sierrawireless.com> has joined #yocto18:59
moto-timokhem: nevermind, I just looked at your commit. thank you19:00
rburtonkhem: btw the mdadm gcc8 fix breaks with gcc<819:00
khemmoto-timo: I planned to submit a pull to oe-devel after these changes were merged which I sent just now19:00
khemrburton: I can guess19:01
khemthat warning is sort of new in gcc819:01
moto-timokhem: thank you. I really appreciate the hard work.19:02
khemyw19:02
khemmoto-timo: now you can see glibc becoming more like musl19:02
khemget rid of cruft even if it is  painful... some competition is always good I guess19:03
*** gtristan <gtristan!~tristanva@110.11.179.89> has joined #yocto19:05
khemonce gcc8 lands I plan to review and drop more patches from gcc/glibc which we are carrying out of tree19:05
moto-timo\o/19:06
khemand drop crypt once the patch on discussions on ml ends and it lands in upstream glibc19:06
khemrburton: I think we probably can use pragmas19:06
*** Jefro <Jefro!~josiermi@134.134.139.72> has quit IRC19:10
rburtonfun also got a race in mesa19:18
khemrburton: runtime race ?19:22
*** tasslehoff <tasslehoff!~aronning@80.77.101.233> has quit IRC19:23
*** King_InuYasha <King_InuYasha!~King_InuY@fedora/ngompa> has joined #yocto19:24
*** phatina <phatina!~phatina@92-52-40-226.dynamic.orange.sk> has joined #yocto19:25
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has quit IRC19:27
*** tasslehoff <tasslehoff!~aronning@80.77.101.233> has joined #yocto19:28
*** King_InuYasha <King_InuYasha!~King_InuY@fedora/ngompa> has quit IRC19:30
rburtonyeah19:36
khemrburton: we should enable llvmpipe backend for x86 I have been using it for sometime19:36
rburtonyeah i've turned it on here19:37
rburtonwanted to see how much of a difference it made to qemux86-64 actually19:37
khemhttps://github.com/kraj/openembedded-core/commit/bd5b222a07e66809c7f113cdab9311d36362696219:37
*** psadro <psadro!~Thunderbi@2620:0:ed0:800a:b034:cb87:2094:f197> has joined #yocto19:44
*** sno <sno!~sno@b2b-78-94-80-58.unitymedia.biz> has joined #yocto19:46
jynikrburton: I see you're the recipe maintainer for cve-check-tool. Was going to email a patch to the oecore list for cve-check.bbclass. Are you the maintainer for that as well?19:49
rburtonjynik: i guess.  fwiw i consider it broken beyond help19:50
jynikrburton: Oh! Why's that?19:50
rburtonbecause the entire concept of actually trusting the mitre database is doomed19:50
rburtonfeel free to mail the list though19:51
rburtonideally with a patch ;)19:51
jynikI see. Yeah, I'm trying to put together some guidelines for folks to better utilize some Yocto/OE features and was going to include a recommendation that they use cve-check.19:51
jynikSo would you say that presenting that with the caveat that it should be only used to supplement one's monitoring of advisories, and not be the sole source of information, is reasonable?19:52
rburtonyes thats fine19:53
rburtoni have A Plan for the future that doesn't involve cve-check19:53
armpit"A" plan19:53
jynikFantastic... will keep an eye out and update my paper accordingly. :)19:54
RPjynik: its better than nothing but in suing it, we learnt what we really should be doing...19:56
RPer, using :)19:56
rburtonjynik: specifically the database has sufficient gaps and mismatches that you can't rely on it, but you can use it to double-check your own expectations19:57
armpitRP, let me know when you want me to start taking on stable/sumo-next19:59
*** christner <christner!~dchristne@70-91-95-105-washington.dc.hfc.comcastbusiness.net> has joined #yocto19:59
RParmpit: go for it!19:59
RParmpit: just bare in mind its not released yet19:59
*** stephano <stephano!~stephano@134.134.139.83> has joined #yocto20:00
tlwoernerrburton: interesting... sometimes a github.com/<project>/archive is a developer-released tarball (which kinda sucks)20:00
armpitRP, yep. is the AB setup to do sumo builds ie autofill in parts?20:00
tlwoernerrburton: the tarball links from /releases/ point to /archive/ URIs: https://github.com/cisco/libsrtp/releases20:01
*** kaspter <kaspter!~Instantbi@183.158.243.96> has quit IRC20:05
*** jmk <jmk!~julien@62.151.197.58> has quit IRC20:05
*** kaspter <kaspter!~Instantbi@183.158.243.96> has joined #yocto20:05
*** bluelightning <bluelightning!~paul@118.148.68.78> has joined #yocto20:07
*** bluelightning <bluelightning!~paul@118.148.68.78> has quit IRC20:07
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto20:07
RParmpit: not sure20:08
*** scottrif <scottrif!~scottrif@47-40-108-60.dhcp.knwc.wa.charter.com> has joined #yocto20:08
* armpit good time for me to learn ; )20:09
RParmpit: basically, no, that is missing20:11
RParmpit: adding autofill to the new buildbot codebase might be a better use of time20:12
*** WillMiles <WillMiles!~Will@static-209-87-231-80.storm.ca> has quit IRC20:12
*** vmeson <vmeson!~rmacleod@128.224.252.2> has quit IRC20:17
*** jmk <jmk!~julien@109.201.133.30> has joined #yocto20:19
khemrburton: sent a v2 along with some more fixes20:25
armpitkhem, a v8 has more power20:31
khemarmpit: but more money for repairing20:32
RParmpit: some good v6s around now...20:37
*** Jefro <Jefro!josiermi@nat/intel/x-rtfrzdscdqxwzpay> has joined #yocto20:40
khemRP: yeah I think v6 is right mix of money/power20:40
armpitnot if you need to run from the police20:43
rburtontlwoerner: yes, those are autogenerated tarballs-from-tags20:47
rburtontlwoerner: when it says "Source Code", that's github giving you a git-archive20:47
rburtonkhem: was the only changed patch mdadm?20:48
tlwoernerrburton: so how does one differentiate between developer release tarballs on github (i.e. the "okay" ones) and the auto-generated github tarballs (i.e. the ones that should be fixed)?20:50
rburtontlwoerner: anything with /archive/ is autogenerated20:50
tlwoernerrburton: even though it comes from /releases/ ? e.g. https://github.com/cisco/libsrtp/releases and https://github.com/cisco/openh264/releases20:51
*** gtristan <gtristan!~tristanva@110.11.179.89> has quit IRC20:51
rburtonthe open264 page, release 1.7.0 has a lot of *maintainer provided* tarballs (the libopenh264-1.7.0.* files) and then the github-generated /archive/ links (Source code)20:52
rburtonthe maintainer provided ones are good20:52
tlwoernerrburton: okay, excellent. thanks for the clarification :-)20:53
rburtontlwoerner: https://github.com/rossburton/meta-ross/blob/master/classes/insanitier.bbclass#L93 :)20:54
rburtonshould get around to putting that in core...20:54
tlwoernerrburton: yes :-) if i'm not mistaken, devtool will complain, but not bitbake itself20:55
rburtonright21:04
rburtonat least devtool does21:04
*** phatina <phatina!~phatina@92-52-40-226.dynamic.orange.sk> has quit IRC21:04
rburtonand as my own builds have that class in, oe-core itself is clean21:04
*** marka <marka!~masselst@128.224.252.2> has quit IRC21:13
*** Willy-- <Willy--!~william@156.34.168.128> has joined #yocto21:24
*** gabrbedd <gabrbedd!~beddingfi@li680-65.members.linode.com> has joined #yocto21:26
-YoctoAutoBuilder- build #994 of nightly-no-x11 is complete: Success [build successful] Build details are at https://autobuilder.yocto.io/builders/nightly-no-x11/builds/99421:27
*** toanju <toanju!~toanju@x5ce5820e.dyn.telefonica.de> has quit IRC21:29
-YoctoAutoBuilder- build #981 of nightly-rpm-non-rpm is complete: Failure [failed Running Sanity Tests] Build details are at https://autobuilder.yocto.io/builders/nightly-rpm-non-rpm/builds/98121:38
*** Jefro <Jefro!josiermi@nat/intel/x-rtfrzdscdqxwzpay> has quit IRC21:42
*** Jefro <Jefro!josiermi@nat/intel/x-ocohylzcgmbkwdme> has joined #yocto21:42
*** rcw <rcw!~rcw@65-110-208-159.cpe.pppoe.ca> has quit IRC21:43
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has joined #yocto21:43
*** rcw <rcw!~rcw@65-110-208-159.cpe.pppoe.ca> has joined #yocto21:43
*** Jefro <Jefro!josiermi@nat/intel/x-ocohylzcgmbkwdme> has quit IRC21:45
jynikrburton: My apologies if I inadvertantly spammed you a patch twice. Forgot to click the link to activate my list subscription.21:46
*** Jefro <Jefro!~josiermi@134.134.139.73> has joined #yocto21:47
-YoctoAutoBuilder- build #990 of nightly-x32 is complete: Failure [failed Running Sanity Tests_1] Build details are at https://autobuilder.yocto.io/builders/nightly-x32/builds/99021:51
-YoctoAutoBuilder- build #645 of nightly-packagemanagers is complete: Failure [failed Running Sanity Tests] Build details are at https://autobuilder.yocto.io/builders/nightly-packagemanagers/builds/64522:01
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has quit IRC22:02
*** martinkelly <martinkelly!~martin@97-113-238-55.tukw.qwest.net> has quit IRC22:06
*** Jefro <Jefro!~josiermi@134.134.139.73> has quit IRC22:12
rburtonjynik: you did, no worries22:12
*** Jefro <Jefro!~josiermi@134.134.139.73> has joined #yocto22:12
rburtonafternoon Jefro22:13
*** Jefro <Jefro!~josiermi@134.134.139.73> has quit IRC22:15
*** Jefro <Jefro!~josiermi@134.134.139.73> has joined #yocto22:17
*** nemunaire <nemunaire!~nemunaire@ra.nemunai.re> has quit IRC22:20
*** dev1990 <dev1990!~dev@dynamic-78-8-43-125.ssp.dialog.net.pl> has quit IRC22:20
*** rburton <rburton!~textual@35.106.2.81.in-addr.arpa> has quit IRC22:26
tlwoernercan the git fetcher check out a tag?22:27
tlwoernerthis is odd... if i clone https://github.com/cisco/openh264.git manually and checkout a180c9d4d6f1a4830ca9eed9d159d54996bd63cb it works, that's tag v1.7.022:28
tlwoernerbut if i ask bitbake to clone and checkout that sha, it can't find it22:30
neverpanicSee the tag parameter in https://www.yoctoproject.org/docs/current/bitbake-user-manual/bitbake-user-manual.html#git-fetcher22:30
neverpanicIt is common to just set branch=master and SRCREV to the sha1 of the tag, though22:31
*** nemunaire <nemunaire!~nemunaire@2a01:e35:8bb7:3c60::2> has joined #yocto22:32
*** scottrif <scottrif!~scottrif@47-40-108-60.dhcp.knwc.wa.charter.com> has left #yocto22:34
kergothtlwoerner: i'd suggest comparing the tag hash to the commit hash the tag points to, in the case where the tag is annotated22:34
tlwoernerneverpanic: ah, thanks22:34
kergothi.e. git show —pretty=fuller sometag22:34
kergothbut yes, definitely avoid ;tag=22:34
-YoctoAutoBuilder- build #1028 of nightly-x86-64 is complete: Failure [failed Running Sanity Tests] Build details are at https://autobuilder.yocto.io/builders/nightly-x86-64/builds/102822:35
tlwoernerthe sha of the tag doesn't appear from master, if i'm on master, do a "git log", and search for the sha, it isn't found22:35
neverpanicmaybe the tag wasn't made on master?22:35
neverpanicThat would explain why the fetch fails for you with branch=master22:36
neverpanicTry with nobranch=1; if that works, the branch is the problem22:36
tlwoernernobranch=1 worked22:36
*** AbleBacon <AbleBacon!~AbleBacon@unaffiliated/ablebacon> has quit IRC22:37
tlwoernerthe tag doesn't appear on any branch22:37
tlwoerner$ git branch --contains a180c9d4d6f1a4830ca9eed9d159d54996bd63cb22:37
tlwoerner* (HEAD detached at a180c9d4)22:38
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has joined #yocto22:38
tlwoernercheck it out:  https://github.com/cisco/openh264.git22:38
tlwoernerhttps://github.com/cisco/openh264/releases22:38
neverpanicGitHub's web interfaces says the tag is on the openh264v1.7 branch22:38
tlwoernerneverpanic: if the tag is on a branch, github will tell you that22:38
tlwoerneroh well, thankfully nobranch=1 works :-)22:39
neverpanichttps://github.com/cisco/openh264/commit/a180c9d4d6f1a4830ca9eed9d159d54996bd63cb has the branch annotation set to openh264v1.722:39
-YoctoAutoBuilder- build #982 of nightly-world is complete: Success [build successful] Build details are at https://autobuilder.yocto.io/builders/nightly-world/builds/98222:39
*** agust <agust!~agust@p50887D26.dip0.t-ipconnect.de> has quit IRC22:40
tlwoernerneverpanic: weird, now that i've checked out that branch, then returned to master, then tried the --contains command again, it now gives me the right answer ... :-S22:42
tlwoerneroh well, thanks :-D22:43
-YoctoAutoBuilder- build #1008 of nightly-x86-64-lsb is complete: Failure [failed Running Sanity Tests] Build details are at https://autobuilder.yocto.io/builders/nightly-x86-64-lsb/builds/100822:49
*** Jefro <Jefro!~josiermi@134.134.139.73> has quit IRC22:58
*** Jefro <Jefro!josiermi@nat/intel/x-kwnylwciljnvsucw> has joined #yocto22:58
*** Jefro <Jefro!josiermi@nat/intel/x-kwnylwciljnvsucw> has quit IRC23:02
-YoctoAutoBuilder- build #1004 of nightly-x86-lsb is complete: Failure [failed Running Sanity Tests] Build details are at https://autobuilder.yocto.io/builders/nightly-x86-lsb/builds/100423:11
*** majuk <majuk!~majuk@174-24-11-32.clsp.qwest.net> has joined #yocto23:12
*** Son_Goku <Son_Goku!~King_InuY@fedora/ngompa> has quit IRC23:14
*** martinkelly <martinkelly!~martin@205.175.119.193> has joined #yocto23:24
-YoctoAutoBuilder- build #996 of nightly-ppc-lsb is complete: Failure [failed Running Sanity Tests] Build details are at https://autobuilder.yocto.io/builders/nightly-ppc-lsb/builds/99623:25
*** nighty-- <nighty--!~nighty@s229123.ppp.asahi-net.or.jp> has quit IRC23:35
-YoctoAutoBuilder- build #1012 of nightly-multilib is complete: Failure [failed Running Sanity Tests_2] Build details are at https://autobuilder.yocto.io/builders/nightly-multilib/builds/101223:37

Generated by irclog2html.py 2.11.0 by Marius Gedminas - find it at mg.pov.lt!