IRC log for #oe on 20170327

00:23.24*** join/#oe infobot (ibot@rikers.org)
00:23.24*** topic/#oe is OpenEmbedded Developer Lounge | Web: http://openembedded.org | Repositories: http://git.openembedded.org/ | Primary Repo Mirrors: https://github.com/openembedded | This is not a distro or machine support channel
01:18.46*** join/#oe snowkidind (~textual@216-15-40-124.c3-0.gth-ubr1.lnh-gth.md.cable.rcn.com)
01:26.04*** join/#oe theRealGent (~theRealGe@unaffiliated/therealgent)
02:14.41*** join/#oe Nilesh_ (uid116340@gateway/web/irccloud.com/x-kafbcdzdzccpsivj)
03:16.32*** join/#oe Jackie (~quassel@106.120.101.38)
05:01.02*** join/#oe Bunio_FH (~bunio@clj-165.netdrive.pl)
06:14.14*** join/#oe AndersD (~anders@194-237-220-218.customer.telia.com)
06:14.51*** join/#oe rob_w (~bob@93.104.205.194)
06:14.51*** join/#oe rob_w (~bob@unaffiliated/rob-w/x-1112029)
06:24.31*** join/#oe frsc (~frsc@80.149.173.67)
06:28.45*** join/#oe eduardas_m (~eduardas@213.197.143.19)
06:54.44*** join/#oe morphis (~morphis@pD9ED609A.dip0.t-ipconnect.de)
07:00.48*** join/#oe JaMa (~martin@217.30.68.212)
07:03.19*** join/#oe jbrianceau_away (uid10952@gateway/web/irccloud.com/x-tibcmkmdokymbaht)
07:03.51*** join/#oe ant_work (~ant__@host180-233-dynamic.45-213-r.retail.telecomitalia.it)
07:20.56*** join/#oe florian_kc (~fuchs@Maemo/community/contributor/florian)
07:29.48*** join/#oe jku (~jku@192.198.151.45)
07:46.32*** join/#oe mr_science (~sarnold@gentoo/developer/nerdboy)
07:47.22*** join/#oe nerdboy (~sarnold@gatekeeper.gentoogeek.org)
07:47.22*** join/#oe nerdboy (~sarnold@gentoo/developer/nerdboy)
07:55.14*** join/#oe eduardas (~eduardas@213.197.143.19)
08:06.20*** join/#oe eduardas_m (~eduardas@213.197.143.19)
08:07.11*** join/#oe ao2 (~ao2@2001:1418:100:22::2)
08:12.58*** join/#oe eduardas_m (~eduardas@213.197.143.19)
08:21.25*** join/#oe maxin (maxin@nat/intel/x-psikkuhsfxbuawqo)
08:30.21*** join/#oe ilial (~ilial@185.23.60.4)
08:38.56*** join/#oe robert_ (~lyang1@106.120.101.38)
08:48.01*** join/#oe joshuagl (~joshuagl@192.198.151.45)
09:02.27*** join/#oe t0mmy (~tprrt@217.114.201.133)
10:00.52*** join/#oe troulouliou_div2 (~troulouli@unaffiliated/troulouliou-div2/x-0271439)
10:10.03*** join/#oe qt-x (~Thunderbi@217.10.196.2)
10:10.59*** join/#oe rburton (~Adium@home.burtonini.com)
10:37.28*** join/#oe qt-x (~Thunderbi@217.10.196.2)
10:43.30*** join/#oe ecloud (quassel@nat/qt/x-wcosdsbkdduygtpl)
11:21.13*** join/#oe jku (~jku@192.198.151.45)
11:24.49quiteI have trouble adding a new recipe and doing devtool-modify on the same. Getting the "compiling from external source tree [correct path]" message, but compiling is still done down in tmp/work/{machine}/...
11:26.16quiteLooking in run.do_compile I see `cd '/the/tmp/work/machine/pkg-path'; do_compile`
11:34.28*** part/#oe quite (quite@gyro.lublin.se)
11:36.17*** join/#oe berton (~berton@189.114.111.135)
11:51.18*** join/#oe ldnunes (~ldnunes_@189.114.111.135)
11:51.40*** join/#oe caiortp (~inatel@131.221.240.226)
12:11.32*** join/#oe bradfa (~andrew@clr-vpn01.kodakalaris.com)
12:47.26*** join/#oe marka (~masselst@135-23-92-83.cpe.pppoe.ca)
13:05.19*** join/#oe eduardas_m (~eduardas@213.197.143.19)
13:15.32mario-goulartIs there any valid reason for a recipe for the target to depend on bison (not bison-native)?
13:20.15mago1mario-goulart: only if the recipe requires the target bison to build
13:21.05mago1mario-goulart: (assuming you're not talking about RDEPENDS)
13:21.27mario-goulartmago1: I'm actually talking about DEPENDS.
13:22.38rburtondoubt it then
13:23.01rburtonbison itself build depends on bison-native, so it would solve the "i need bison to build" problem
13:23.05rburtonalbeit wrongly
13:23.12rburtonand only if building from scratch
13:23.18mario-goulartindeed
13:23.53mario-goulartI'd say the same for flex, but I think flex actually ships a library.
13:50.39*** join/#oe Paprika_007 (~Paprika_0@87.237.27.158)
14:00.00otaviorburton: hello
14:00.12otaviorburton: did you put u-boot in MUT for test?
14:00.41otaviorburton: I would also try to fit mesa upgrade for release; it is just bug fixes and would be good to have in
14:02.11rburtonyeah they're in next for testing
14:03.03*** join/#oe madisox (~madison@12.30.244.5)
14:04.14Crofton|workMarex, ^^^
14:08.39otavioMarex: 2017.03 release, it is
14:13.19Marexwhat ?
14:14.36MarexCrofton|work: what is otavio talking about ?
14:15.16Crofton|workhe sent in patches for 2017.03
14:16.33Marexwell gee, thanks for CCing me
14:16.35Marexlink ?
14:17.14MarexCrofton|work: that's for poky 2.3 or next one ?
14:18.34Crofton|workI'm not sure, just wanted to make sure you knew there were patches around
14:21.15MarexCrofton|work: I might as well submit my patch too finally ^_^'
14:21.23Marexshould've done that a while ago
14:23.31*** join/#oe cbrake (~Thunderbi@66.219.186.219)
14:26.52*** join/#oe vmeson (~rmacleod@24-212-231-150.cable.teksavvy.com)
14:27.17otavio:-)
14:27.56Crofton|workWell, you brok eth elast release as I recall
14:28.23Crofton|workso timing and making sure what is in release really works is up to u-boot user community
14:28.47otavioCrofton|work: who, me?
14:29.31Crofton|workand the other people using u-boot in OE :)
14:29.49Crofton|workand making your don't break autobuilder and tests
14:30.25Crofton|workpersonally, I think I will be OK with the update :)
14:32.55otavioCrofton|work: I am not following you
14:33.40otavioCrofton|work: Updating U-Boot is a problem if the BSP uses the OE-Core recipe and applies patches on it. If it does, I think it is wrong twice. It should send those patches upstream or use a fork
14:33.49Crofton|workotavio, we had a conversation with marex a while back about whether the next release would have 2017.01 or 2017.03
14:34.28otavioCrofton|work: as being one of most active people on u-boot recipe I would have been included on this conversation I believe
14:34.33Crofton|worksince .03 was fairly late in the release cycle, Marex sent in .01
14:35.50otavioWell it is not fairly late being used by few reference bsp only
14:36.31Crofton|workI think braoder use than that
14:37.06otavioI use it in many boards and as I apply patches I keep a fork
14:37.24otaviobut the original recipe, I don't think so
14:38.31Marexand the fork depends on the abysmal state of u-boot bbclass ... we've been there
14:38.43Marexis kinda getting annoyed, bbl
14:40.51*** join/#oe florian_ (~fuchs@77.9.78.241)
14:54.13*** join/#oe florian_kc (~fuchs@Maemo/community/contributor/florian)
15:13.26*** join/#oe willdye (~willdye@h152.133.190.173.dynamic.ip.windstream.net)
15:36.57*** join/#oe hrw (~hrw@redhat/hrw)
15:45.54*** join/#oe Paprika_007 (~Paprika_0@145.108.69.130)
16:17.48adelcastRP: do you remember who was last week reporting an opkg solver issue? I still believe opkg is behaving correctly, but I am somewhat on the lookout for issues because libsolv does make opkg more strictly adhere to debian guidelines (some recipes may rely on opkg not following debian that strictly)
16:18.06adelcastI want to make sure I follow up, just in case
16:21.33RPadelcast: I'd have to look through the logs, I don't remember offhand
16:21.42RPadelcast: thanks for looking into it though!
16:22.48paulbarkerotavio: meta-raspberrypi uses the u-boot recipe from oe-core. We don't currently apply any patches but I'll need to do some re-testing if we upgrade u-boot this late in the cycle.
16:23.05paulbarkerthe last few upstream u-boot releases have changed things for rpi quite a bit
16:23.17rburtonand this is why i'm always cautious about u-boot upgrades
16:23.24adelcastRP: no worries, I'll dig in the logs....do ping me if you hear of anyone else having issues with the switch
16:23.24rburtonespecially weeks away from the release
16:26.09RPpaulbarker: that is a good data point thanks. That kind of thing is hard to test too
16:26.35*** join/#oe stephano (~stephano@134.134.139.70)
16:26.45paulbarkerusing oe-core recipes and applying patches in a bbappend is pretty much my way of working when I need to tweak something for a BSP
16:28.48paulbarkerRP: Thankfully with rpi, u-boot is on an SD card so it's easy to take out and re-flash if I break it. It does need a bit of manual testing though
16:29.43paulbarkerI'm not looking forward to the meta-arduino u-boot upgrade I have planned. In that case it's a soldered down flash with no recovery mechanism if you break u-boot
16:32.09*** join/#oe jku (~jku@2001:14ba:1fe:f400:4e8d:79ff:fef2:49ba)
16:34.04*** join/#oe eFfeM (~frans@dhcp-089-099-139-063.chello.nl)
16:36.01RPpaulbarker: ouch, definitely one you need to get right :/
16:36.58*** join/#oe t0mmy (~tprrt@ram31-1-82-234-79-177.fbx.proxad.net)
16:43.23*** join/#oe ash_charles (~acharles@2607:fad8:4:6:c8a6:17d:5ad6:1157)
16:52.06otaviopaulbarker: if you believe it would be breaking anything might be better to have a specific recipe with the validated branch pinned.
16:52.19otaviopaulbarker: but of course using the recipe if possible, is nice
16:54.09paulbarkerotavio: on the master branch, I want to find out if the new release is broken. I want it to explode in my face so I can fix it. I just maybe don't want that to happen in the last few weeks before a release
17:00.17paulbarkerpersonally I'd say let's update u-boot at the start of the yocto 2.4 cycle
17:05.45*** join/#oe florian (~fuchs@Maemo/community/contributor/florian)
17:06.00paulbarker(my only concern is meta-raspberrypi here. for meta-arduino I just use whatever is already flashed into the board at this stage and I'm not taking on that scary upgrade for a while yet)
17:25.31*** join/#oe Varti (~varthall@dynamic-adsl-78-12-165-150.clienti.tiscali.it)
17:33.18*** join/#oe jkridner (~jkridner@pdpc/supporter/active/jkridner)
17:41.11*** join/#oe Bunio_FH (~bunio@clj-165.netdrive.pl)
19:06.47*** join/#oe bluelightning (~paul@pdpc/supporter/professional/bluelightning)
19:22.35*** join/#oe ChrisD1_Away (~ChrisD@dsl-217-155-59-206.zen.co.uk)
19:24.42*** join/#oe marka (~masselst@135-23-92-83.cpe.pppoe.ca)
20:50.39*** join/#oe ant_home (~ant__@95.236.249.99)
20:52.41*** join/#oe ao2 (~ao2@2001:1418:100:22::2)
21:01.00*** join/#oe otavio_ (~otavio@debian/developer/otavio)
21:28.51*** join/#oe stephano (~stephano@134.134.139.82)
21:33.21*** join/#oe moto-timo (~ttorling@134.134.139.77)
21:33.21*** join/#oe moto-timo (~ttorling@fsf/member/moto-timo)
21:52.27*** join/#oe sgw_ (sgw_@nat/intel/x-pohfndqbqdypahcy)
21:58.40*** join/#oe Paprika_007 (~Paprika_0@a83-163-237-65.adsl.xs4all.nl)
22:01.00*** join/#oe phdeswer_ (~phdeswer@91-159-55-220.elisa-laajakaista.fi)
22:12.34*** join/#oe georgem_home (uid210681@gateway/web/irccloud.com/x-isbywyderzttwepp)
22:34.50*** join/#oe stephano (~stephano@134.134.139.83)
22:52.03RPotavio_, paulbarker: FWIW I'm thinking of not upgrading uboot at this point, its too late

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.