| *** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has joined #yocto | 00:03 | |
| *** manuel_ <manuel_!~manuel@c-24-61-40-209.hsd1.ma.comcast.net> has quit IRC | 00:07 | |
| *** manuel_ <manuel_!~manuel@c-24-61-40-209.hsd1.ma.comcast.net> has joined #yocto | 00:09 | |
| *** smferris <smferris!~smferris@192.95.10.156> has quit IRC | 00:10 | |
| *** HyP3r <HyP3r!~HyP3r@andreas-fendt.de> has quit IRC | 00:11 | |
| *** seebs <seebs!~seebs@2601:196:4901:ec80:f1d1:b4ad:12e2:4c03> has joined #yocto | 00:18 | |
| *** smferris <smferris!~smferris@192.95.10.156> has joined #yocto | 00:21 | |
| *** bbarr <bbarr!~bbarr@38.140.133.170> has quit IRC | 00:23 | |
| *** tripzero <tripzero!~tripzero@134.134.139.76> has quit IRC | 00:26 | |
| *** tripzero <tripzero!~tripzero@134.134.137.75> has joined #yocto | 00:27 | |
| *** dreyna <dreyna!~dreyna@rrcs-74-87-90-2.west.biz.rr.com> has quit IRC | 00:36 | |
| *** dreyna <dreyna!~dreyna@rrcs-74-87-90-2.west.biz.rr.com> has joined #yocto | 00:37 | |
| *** manuel_ <manuel_!~manuel@c-24-61-40-209.hsd1.ma.comcast.net> has quit IRC | 00:41 | |
| *** dreyna <dreyna!~dreyna@rrcs-74-87-90-2.west.biz.rr.com> has quit IRC | 00:50 | |
| *** manuel_ <manuel_!~manuel@c-24-61-40-209.hsd1.ma.comcast.net> has joined #yocto | 00:50 | |
| *** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has quit IRC | 01:09 | |
| *** manuel_ <manuel_!~manuel@c-24-61-40-209.hsd1.ma.comcast.net> has quit IRC | 01:10 | |
| *** t0mmy <t0mmy!~tprrt@ram31-1-82-234-79-177.fbx.proxad.net> has joined #yocto | 01:12 | |
| *** morphis__ <morphis__!~morphis@pD9ED6288.dip0.t-ipconnect.de> has joined #yocto | 01:14 | |
| *** manuel_ <manuel_!~manuel@c-24-61-40-209.hsd1.ma.comcast.net> has joined #yocto | 01:16 | |
| -YoctoAutoBuilder- build #946 of nightly-multilib is complete: Failure [failed BuildImages_5 Running Sanity Tests_4 BuildImages_6 Running SDK Sanity Tests] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-multilib/builds/946 | 01:18 | |
| *** morphis_ <morphis_!~morphis@pD9ED6678.dip0.t-ipconnect.de> has quit IRC | 01:18 | |
| *** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto | 01:22 | |
| *** fenrig_ <fenrig_!5ee32de5@gateway/web/freenode/ip.94.227.45.229> has joined #yocto | 01:26 | |
| fenrig_ | Hi, how do i enable systemd services to run at boot from within yocto | 01:26 |
|---|---|---|
| fenrig_ | and how do I add journalctl to the image? | 01:26 |
| *** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC | 01:27 | |
| Ulfalizer | fenrig_: http://www.yoctoproject.org/docs/2.2/ref-manual/ref-manual.html#var-SYSTEMD_AUTO_ENABLE | 01:31 |
| bluelightning | that's of course assuming you have already switched over from sysvinit to systemd | 01:31 |
| fenrig_ | how do I do this from the image.bb file | 01:32 |
| bluelightning | you cannot | 01:32 |
| fenrig_ | yeah i switched to systemd already | 01:32 |
| bluelightning | it must be done at the configuration level or in the recipe installing the service | 01:32 |
| fenrig_ | though I am missing systemctl and journalctl from my image | 01:33 |
| bluelightning | the default is to enable the service though so if you find one that's not enabled either the recipe is disabling it or something is broken | 01:33 |
| fenrig_ | i probably should grep for it then | 01:36 |
| bluelightning | it sounds a bit odd that systemctl and journalctl aren't there | 01:38 |
| fenrig_ | its odd | 01:38 |
| fenrig_ | but i have some messages from systemd-udevd | 01:39 |
| fenrig_ | and I have systemd files in my sysroot | 01:39 |
| bluelightning | that doesn't mean much, since that's a separate program | 01:39 |
| bluelightning | I suspect you're still running sysvinit in the image | 01:40 |
| fenrig_ | I did had to switch | 01:40 |
| fenrig_ | I did this in the local.conf | 01:40 |
| *** manuel_ <manuel_!~manuel@c-24-61-40-209.hsd1.ma.comcast.net> has quit IRC | 01:40 | |
| bluelightning | what exactly did you put in there? | 01:41 |
| fenrig_ | VIRTUAL_RUNTIME_init_manager = "systemd" | 01:41 |
| fenrig_ | and | 01:41 |
| fenrig_ | DISTRO_FEATURES = "ext2 opengl usbhost ${DISTRO_FEATURES_LIBC} pulseaudio systemd" | 01:41 |
| fenrig_ | this is the correct way? | 01:42 |
| fenrig_ | Im building for the raspberry pi | 01:43 |
| *** manuel_ <manuel_!~manuel@c-24-61-40-209.hsd1.ma.comcast.net> has joined #yocto | 01:46 | |
| *** Nilesh_ <Nilesh_!uid116340@gateway/web/irccloud.com/x-ofihylyhqrzuihiu> has joined #yocto | 01:48 | |
| *** manuel__ <manuel__!~manuel@c-24-61-40-209.hsd1.ma.comcast.net> has joined #yocto | 01:48 | |
| *** blueness <blueness!~blueness@gentoo/developer/blueness> has quit IRC | 01:48 | |
| bluelightning | fenrig_: confusingly it's VIRTUAL-RUNTIME not VIRTUAL_RUNTIME | 01:50 |
| bluelightning | if you have the latter in your config that may explain why it's not working | 01:50 |
| *** manuel_ <manuel_!~manuel@c-24-61-40-209.hsd1.ma.comcast.net> has quit IRC | 01:51 | |
| *** manuel__ is now known as manuel_ | 01:51 | |
| fenrig_ | okay lets rebuild | 01:51 |
| fenrig_ | so "inherit systemd" makes the service enabled for boot | 01:52 |
| fenrig_ | unless there is a | 01:52 |
| fenrig_ | SYSTEMD_AUTO_ENABLE = "disable" | 01:52 |
| Ulfalizer | fenrig_: behind the scenes, a post-installation script is added to the package. when the package is installed, 'systemctl enable <service>' is run if SYSTEMD_AUTO_ENABLE is "enable". | 02:01 |
| Ulfalizer | search for systemd_postinst in systemd.bbclass to see it | 02:01 |
| Ulfalizer | the underlying mechanism is pkg_postinst. you'll find that in the reference manual. | 02:02 |
| Ulfalizer | not directly relevant, but it helps me to understand how it's implemented | 02:02 |
| Ulfalizer | urr... *in the development manual | 02:02 |
| Ulfalizer | fenrig_: http://www.yoctoproject.org/docs/2.2/ref-manual/ref-manual.html#var-PROVIDES has a note on VIRTUAL-RUNTIME btw | 02:06 |
| *** blueness <blueness!~blueness@gentoo/developer/blueness> has joined #yocto | 02:09 | |
| *** manuel_ <manuel_!~manuel@c-24-61-40-209.hsd1.ma.comcast.net> has quit IRC | 02:10 | |
| *** manuel_ <manuel_!~manuel@c-24-61-40-209.hsd1.ma.comcast.net> has joined #yocto | 02:17 | |
| *** fenrig_ <fenrig_!5ee32de5@gateway/web/freenode/ip.94.227.45.229> has quit IRC | 02:34 | |
| *** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto | 03:26 | |
| *** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC | 03:31 | |
| *** manuel_ <manuel_!~manuel@c-24-61-40-209.hsd1.ma.comcast.net> has quit IRC | 03:32 | |
| *** manuel_ <manuel_!~manuel@c-24-61-40-209.hsd1.ma.comcast.net> has joined #yocto | 03:47 | |
| *** AndersD <AndersD!~anders@h83-209-191-235.cust.se.alltele.net> has joined #yocto | 04:06 | |
| *** slidercrank <slidercrank!~slidercra@unaffiliated/slidercrank> has quit IRC | 04:11 | |
| *** manuel_ <manuel_!~manuel@c-24-61-40-209.hsd1.ma.comcast.net> has quit IRC | 04:15 | |
| *** dreyna <dreyna!~dreyna@rrcs-74-87-90-2.west.biz.rr.com> has joined #yocto | 04:23 | |
| *** gtristan <gtristan!~tristanva@114.207.54.40> has joined #yocto | 04:36 | |
| *** sujith_h <sujith_h!~toaster@kde/developers/sujithh> has joined #yocto | 04:43 | |
| *** AndersD <AndersD!~anders@h83-209-191-235.cust.se.alltele.net> has quit IRC | 04:51 | |
| *** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has joined #yocto | 04:57 | |
| *** dreyna <dreyna!~dreyna@rrcs-74-87-90-2.west.biz.rr.com> has quit IRC | 05:02 | |
| -YoctoAutoBuilder- build #1018 of nightly is complete: Failure [failed] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly/builds/1018 | 05:03 | |
| *** optimus_ <optimus_!~optimus@189.181.129.194> has joined #yocto | 05:06 | |
| *** agust <agust!~agust@p4FCB58BB.dip0.t-ipconnect.de> has joined #yocto | 05:39 | |
| *** rperier <rperier!~quassel@ubuntu/member/rperier> has quit IRC | 06:03 | |
| *** pohly <pohly!~pohly@p5DE8FF1A.dip0.t-ipconnect.de> has joined #yocto | 06:04 | |
| *** jku <jku!jku@nat/intel/x-jcceasihviubqzxs> has joined #yocto | 06:05 | |
| *** rperier <rperier!~quassel@2001:41d0:52:100::44a> has joined #yocto | 06:06 | |
| *** AndersD <AndersD!~anders@213-64-218-130-no126.business.telia.com> has joined #yocto | 06:10 | |
| *** milindur <milindur!~milindur@deimos.ca-soft.de> has quit IRC | 06:10 | |
| *** jubr <jubr!57ed1b9e@gateway/web/freenode/ip.87.237.27.158> has quit IRC | 06:11 | |
| *** mario-goulart <mario-goulart!~user@email.parenteses.org> has joined #yocto | 06:15 | |
| *** mario-go` <mario-go`!~user@email.parenteses.org> has quit IRC | 06:16 | |
| *** frsc <frsc!~frsc@dslb-178-002-210-000.178.002.pools.vodafone-ip.de> has joined #yocto | 06:17 | |
| *** TobSnyder <TobSnyder!~schneider@ip9234b0ae.dynamic.kabel-deutschland.de> has joined #yocto | 06:19 | |
| *** behanw <behanw!uid110099@gateway/web/irccloud.com/x-hwrzvkhgiwbhfulc> has quit IRC | 06:19 | |
| *** milindur <milindur!~milindur@deimos.ca-soft.de> has joined #yocto | 06:20 | |
| *** rob_w <rob_w!~bob@93.104.205.194> has joined #yocto | 06:32 | |
| *** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has joined #yocto | 06:32 | |
| *** optimus_ <optimus_!~optimus@189.181.129.194> has quit IRC | 06:39 | |
| *** hatter <hatter!~hatter@h-90-120.a137.corp.bahnhof.se> has joined #yocto | 06:39 | |
| *** t0mmy <t0mmy!~tprrt@ram31-1-82-234-79-177.fbx.proxad.net> has quit IRC | 06:41 | |
| *** jonver <jonver!~jonver___@dd577603a.access.telenet.be> has joined #yocto | 06:52 | |
| *** boucman_work <boucman_work!~boucman@193.56.60.161> has joined #yocto | 06:53 | |
| *** eduardas_m <eduardas_m!~eduardas_@213.197.143.19> has joined #yocto | 06:53 | |
| *** fl0v0 <fl0v0!~fvo@pD9F6B9DE.dip0.t-ipconnect.de> has joined #yocto | 06:58 | |
| *** blueness <blueness!~blueness@gentoo/developer/blueness> has quit IRC | 07:04 | |
| *** Anticom <Anticom!~quassel@217.6.33.234> has joined #yocto | 07:05 | |
| *** t0mmy <t0mmy!~tprrt@217.114.201.133> has joined #yocto | 07:07 | |
| *** blueness <blueness!~blueness@gentoo/developer/blueness> has joined #yocto | 07:11 | |
| *** AndersD <AndersD!~anders@213-64-218-130-no126.business.telia.com> has quit IRC | 07:11 | |
| *** jonver <jonver!~jonver___@dd577603a.access.telenet.be> has left #yocto | 07:12 | |
| *** jonver <jonver!~jonver___@dD577603A.access.telenet.be> has joined #yocto | 07:13 | |
| *** jonver <jonver!~jonver___@dD577603A.access.telenet.be> has quit IRC | 07:14 | |
| *** jonver <jonver!~jonver___@dd577603a.access.telenet.be> has joined #yocto | 07:16 | |
| *** toanju <toanju!~toanju@185.27.182.30> has joined #yocto | 07:16 | |
| *** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has quit IRC | 07:16 | |
| *** florian <florian!~fuchs@Maemo/community/contributor/florian> has joined #yocto | 07:20 | |
| *** robertmarshall <robertmarshall!~robertmar@82-70-136-246.dsl.in-addr.zen.co.uk> has joined #yocto | 07:20 | |
| *** AndersD <AndersD!~anders@213-64-218-130-no126.business.telia.com> has joined #yocto | 07:26 | |
| *** ecdhe_ <ecdhe_!~ecdhe@173-22-126-166.client.mchsi.com> has joined #yocto | 07:30 | |
| *** toscalix_ <toscalix_!~toscalix@80.91.70.192> has joined #yocto | 07:31 | |
| *** mckoan|away is now known as mckoan | 07:32 | |
| *** obsrwr_ <obsrwr_!~otp-amois@89.121.200.102> has joined #yocto | 07:32 | |
| mckoan | good morning | 07:33 |
| *** joshuagl <joshuagl!~joshuagl@192.198.151.44> has joined #yocto | 07:41 | |
| *** frsc <frsc!~frsc@dslb-178-002-210-000.178.002.pools.vodafone-ip.de> has quit IRC | 07:44 | |
| *** ecdhe <ecdhe!~ecdhe@173-22-126-166.client.mchsi.com> has quit IRC | 07:48 | |
| *** ecdhe <ecdhe!~ecdhe@unaffiliated/ecdhe> has joined #yocto | 07:48 | |
| *** ecdhe <ecdhe!~ecdhe@173-22-126-166.client.mchsi.com> has joined #yocto | 07:49 | |
| *** ecdhe <ecdhe!~ecdhe@unaffiliated/ecdhe> has joined #yocto | 07:49 | |
| *** LocutusOfBorg <LocutusOfBorg!~Gianfranc@2.238.240.162> has joined #yocto | 07:50 | |
| *** LocutusOfBorg <LocutusOfBorg!~Gianfranc@ubuntu/member/locutusofborg> has joined #yocto | 07:50 | |
| *** zeenix <zeenix!~zeenix@83.218.80.242> has joined #yocto | 07:55 | |
| *** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto | 08:00 | |
| *** seezer <seezer!quassel@quassel/developer/seezer> has quit IRC | 08:03 | |
| *** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC | 08:04 | |
| *** sameo <sameo!~samuel@192.55.55.41> has joined #yocto | 08:04 | |
| *** shagu <shagu!~eric@p5B2E8337.dip0.t-ipconnect.de> has joined #yocto | 08:06 | |
| *** frsc <frsc!~frsc@dslb-178-002-210-000.178.002.pools.vodafone-ip.de> has joined #yocto | 08:07 | |
| *** grma <grma!~gruberm@80.93.38.128> has joined #yocto | 08:07 | |
| *** jku <jku!jku@nat/intel/x-jcceasihviubqzxs> has quit IRC | 08:22 | |
| *** mortderire <mortderire!~rkinsell@192.198.151.45> has joined #yocto | 08:24 | |
| *** jku <jku!~jku@2001:998:22:0:4e8d:79ff:fef2:49ba> has joined #yocto | 08:24 | |
| *** maxin <maxin!~maxin@37-219-81-187.nat.bb.dnainternet.fi> has joined #yocto | 08:26 | |
| *** toanju <toanju!~toanju@185.27.182.30> has quit IRC | 08:34 | |
| *** mortderire <mortderire!~rkinsell@192.198.151.45> has quit IRC | 08:36 | |
| *** toanju <toanju!~toanju@185.27.182.30> has joined #yocto | 08:38 | |
| *** falk0n <falk0n!~falk0n@a109-49-61-108.cpe.netcabo.pt> has joined #yocto | 08:48 | |
| *** sla <sla!c2fb77c5@gateway/web/freenode/ip.194.251.119.197> has joined #yocto | 08:52 | |
| sla | hello guys, some question: lets say i have 4 targets (machines) in conf/, few tasks for building artifacts in classes/, and while executing bitbake my-image I want to build 4 targets at once. how can I achieve that? thanks for any tips | 08:56 |
| *** seezer <seezer!quassel@quassel/developer/seezer> has joined #yocto | 08:59 | |
| *** JaMa <JaMa!~martin@ip-89-176-104-169.net.upcbroadband.cz> has joined #yocto | 09:02 | |
| *** belen <belen!~Adium@134.134.137.71> has joined #yocto | 09:09 | |
| *** toanju <toanju!~toanju@185.27.182.30> has quit IRC | 09:25 | |
| *** toanju <toanju!~toanju@185.27.182.30> has joined #yocto | 09:25 | |
| *** mortderire <mortderire!~rkinsell@192.198.151.45> has joined #yocto | 09:49 | |
| mckoan | sla: you can't, but you can concatenate bitbake commands using && | 09:55 |
| mckoan | sla: and specifying MACHINE=xxx on the commandline before each bitbake | 09:55 |
| *** mortderire1 <mortderire1!~rkinsell@192.198.151.45> has joined #yocto | 10:07 | |
| *** mortderire <mortderire!~rkinsell@192.198.151.45> has quit IRC | 10:09 | |
| *** toscalix_ <toscalix_!~toscalix@80.91.70.192> has quit IRC | 10:16 | |
| *** toscalix_ <toscalix_!~toscalix@80.91.70.192> has joined #yocto | 10:18 | |
| *** toscalix <toscalix!~toscalix@80.91.70.192> has joined #yocto | 10:24 | |
| *** toscalix_ <toscalix_!~toscalix@80.91.70.192> has quit IRC | 10:26 | |
| *** mortderire1 <mortderire1!~rkinsell@192.198.151.45> has quit IRC | 10:31 | |
| *** jku <jku!~jku@2001:998:22:0:4e8d:79ff:fef2:49ba> has quit IRC | 10:31 | |
| *** mortderire <mortderire!~rkinsell@192.198.151.45> has joined #yocto | 10:31 | |
| *** jku <jku!~jku@2001:998:22:0:4e8d:79ff:fef2:49ba> has joined #yocto | 10:32 | |
| *** jku <jku!~jku@2001:998:22:0:4e8d:79ff:fef2:49ba> has quit IRC | 10:35 | |
| *** jku <jku!~jku@2001:998:22:0:4e8d:79ff:fef2:49ba> has joined #yocto | 10:35 | |
| *** Biliogadafr <Biliogadafr!~pin@62.214.49.206> has joined #yocto | 10:37 | |
| *** obsrwr_ <obsrwr_!~otp-amois@89.121.200.102> has quit IRC | 10:44 | |
| *** mortderire <mortderire!~rkinsell@192.198.151.45> has quit IRC | 10:46 | |
| *** toscalix <toscalix!~toscalix@80.91.70.192> has quit IRC | 10:48 | |
| *** toscalix <toscalix!~toscalix@80.91.70.192> has joined #yocto | 10:59 | |
| *** redengin <redengin!~redengin@c-67-160-25-22.hsd1.wa.comcast.net> has quit IRC | 11:00 | |
| *** redengin <redengin!~redengin@c-67-160-25-22.hsd1.wa.comcast.net> has joined #yocto | 11:00 | |
| *** mortderire <mortderire!~rkinsell@192.198.151.44> has joined #yocto | 11:08 | |
| *** mortderire1 <mortderire1!~rkinsell@192.198.151.45> has joined #yocto | 11:10 | |
| *** mortderire <mortderire!~rkinsell@192.198.151.44> has quit IRC | 11:13 | |
| *** mago_ <mago_!~mago@88.131.56.168> has quit IRC | 11:14 | |
| *** mortderire <mortderire!~rkinsell@192.198.151.45> has joined #yocto | 11:16 | |
| *** shagu <shagu!~eric@p5B2E8337.dip0.t-ipconnect.de> has quit IRC | 11:22 | |
| *** Net147 <Net147!~Net147@unaffiliated/net147> has quit IRC | 11:24 | |
| *** nighty <nighty!~nighty@d246113.ppp.asahi-net.or.jp> has quit IRC | 11:26 | |
| *** belen <belen!~Adium@134.134.137.71> has quit IRC | 11:31 | |
| *** Net147 <Net147!~Net147@unaffiliated/net147> has joined #yocto | 11:41 | |
| *** Net147 <Net147!~Net147@unaffiliated/net147> has quit IRC | 11:44 | |
| *** Net147 <Net147!~Net147@unaffiliated/net147> has joined #yocto | 11:47 | |
| *** maxin <maxin!~maxin@37-219-81-187.nat.bb.dnainternet.fi> has quit IRC | 11:48 | |
| aratiu | I have a recipe which adds a new user via useradd but another recipe which depends on it fails because the user does not exist, when I go to the target sysroot I can't find the user in /etc/passwd. Can something overwrite the file in the sysroot (I don't do it intentionally)? | 11:50 |
| *** falk0n <falk0n!~falk0n@a109-49-61-108.cpe.netcabo.pt> has quit IRC | 11:51 | |
| *** falk0n <falk0n!~falk0n@a109-49-61-108.cpe.netcabo.pt> has joined #yocto | 11:53 | |
| *** present <present!c2336e7b@gateway/web/freenode/ip.194.51.110.123> has joined #yocto | 11:53 | |
| *** qt-x <qt-x!~Thunderbi@217.10.196.2> has quit IRC | 11:56 | |
| *** gtristan <gtristan!~tristanva@114.207.54.40> has quit IRC | 11:57 | |
| *** istarilucky <istarilucky!~rlucca@189.112.127.225> has joined #yocto | 11:58 | |
| *** qt-x <qt-x!~Thunderbi@217.10.196.2> has joined #yocto | 11:59 | |
| *** seebs <seebs!~seebs@2601:196:4901:ec80:f1d1:b4ad:12e2:4c03> has quit IRC | 12:02 | |
| *** seebs <seebs!~seebs@c-24-91-64-163.hsd1.ma.comcast.net> has joined #yocto | 12:03 | |
| *** phatina <phatina!~phatina@82-119-96-90.static.chello.sk> has joined #yocto | 12:03 | |
| *** maxin <maxin!~maxin@2001:998:22:0:844f:dfe2:9cc2:a409> has joined #yocto | 12:04 | |
| *** marka_home <marka_home!~marka@135-23-92-83.cpe.pppoe.ca> has joined #yocto | 12:15 | |
| *** gtristan <gtristan!~tristanva@110.11.179.37> has joined #yocto | 12:16 | |
| *** seebs <seebs!~seebs@c-24-91-64-163.hsd1.ma.comcast.net> has quit IRC | 12:16 | |
| *** seebs <seebs!~seebs@c-24-91-64-163.hsd1.ma.comcast.net> has joined #yocto | 12:17 | |
| *** berton <berton!~fabio@177.100.227.233> has joined #yocto | 12:21 | |
| *** caiortp <caiortp!~inatel@131.221.240.204> has joined #yocto | 12:22 | |
| *** t0mmy <t0mmy!~tprrt@217.114.201.133> has quit IRC | 12:25 | |
| jku | armpit: had a look at the Xorg failure on your krogoth-next nightly-musl: khem fixed this in master , oe-core rev e279c9a30f | 12:26 |
| *** dmoseley <dmoseley!~dmoseley@6532158hfc157.tampabay.res.rr.com> has quit IRC | 12:26 | |
| *** seebs <seebs!~seebs@c-24-91-64-163.hsd1.ma.comcast.net> has quit IRC | 12:29 | |
| *** t0mmy <t0mmy!~tprrt@217.114.201.133> has joined #yocto | 12:31 | |
| *** seebs <seebs!~seebs@c-24-91-64-163.hsd1.ma.comcast.net> has joined #yocto | 12:31 | |
| *** mago_ <mago_!~mago@88.131.56.168> has joined #yocto | 12:34 | |
| *** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC | 12:35 | |
| jku | aratiu: can you share the recipe? | 12:36 |
| *** seebs <seebs!~seebs@c-24-91-64-163.hsd1.ma.comcast.net> has quit IRC | 12:39 | |
| *** csanchezdll <csanchezdll!~user@galileo.kdpof.com> has joined #yocto | 12:41 | |
| *** oob <oob!~paulg@OTWAON23-3096772825.sdsl.bell.ca> has joined #yocto | 12:41 | |
| *** Nilesh_ <Nilesh_!uid116340@gateway/web/irccloud.com/x-ofihylyhqrzuihiu> has quit IRC | 12:47 | |
| *** belen <belen!~Adium@134.134.137.71> has joined #yocto | 12:53 | |
| *** nighty <nighty!~nighty@s229123.ppp.asahi-net.or.jp> has joined #yocto | 12:54 | |
| *** jku <jku!~jku@2001:998:22:0:4e8d:79ff:fef2:49ba> has quit IRC | 13:00 | |
| *** ziggo <ziggo!~ziggo@217.89.178.116> has quit IRC | 13:01 | |
| *** jku <jku!jku@nat/intel/x-clwqveboaudaxcod> has joined #yocto | 13:02 | |
| *** igor3 <igor3!~igor@177.159.144.73> has joined #yocto | 13:02 | |
| *** Anticom <Anticom!~quassel@217.6.33.234> has quit IRC | 13:03 | |
| *** 7YUAB2SWX <7YUAB2SWX!~quassel@217.6.33.234> has joined #yocto | 13:04 | |
| *** jku <jku!jku@nat/intel/x-clwqveboaudaxcod> has quit IRC | 13:04 | |
| *** fl0v0 <fl0v0!~fvo@pD9F6B9DE.dip0.t-ipconnect.de> has quit IRC | 13:05 | |
| *** fl0v0 <fl0v0!~fvo@pD9F6B9DE.dip0.t-ipconnect.de> has joined #yocto | 13:05 | |
| *** 7YUAB2SWX is now known as Anticom | 13:06 | |
| *** LocutusOfBorg <LocutusOfBorg!~Gianfranc@ubuntu/member/locutusofborg> has quit IRC | 13:07 | |
| melonipoika | Hi | 13:09 |
| melonipoika | has anyone seen this waring when building pulseaudio? 'WARNING: /home/josealar/poky/meta/recipes-multimedia/pulseaudio/pulseaudio_8.0.bb: Getting checksum for pulseaudio SRC_URI entry : file not found except in DL_DIR' | 13:10 |
| melonipoika | (krogoth branch) | 13:10 |
| melonipoika | I don't know how to debug what is the file that is not found... | 13:11 |
| rburton | well, is there a SRC_URI entry that doesn't exist alongside the recipe | 13:12 |
| *** vmeson <vmeson!~rmacleod@24-212-184-107.cable.teksavvy.com> has quit IRC | 13:13 | |
| melonipoika | no, all are there | 13:13 |
| rburton | then do you have a layer that appends pulseaudio? | 13:14 |
| rburton | (bitbake pulseaudio -e | less and search for SRC_URI to check) | 13:14 |
| rburton | huh | 13:15 |
| melonipoika | thanks | 13:15 |
| rburton | the message is "Getting checksum for %s SRC_URI entry %s: file not found except in DL_DIR" | 13:15 |
| rburton | so the entry is "" | 13:15 |
| rburton | bad whitespace causing problems? | 13:15 |
| *** eduardas_m <eduardas_m!~eduardas_@213.197.143.19> has quit IRC | 13:18 | |
| melonipoika | oh, yes we are appending it in our layer... | 13:18 |
| *** maxin <maxin!~maxin@2001:998:22:0:844f:dfe2:9cc2:a409> has quit IRC | 13:19 | |
| melonipoika | and we have four SRC_URI entries that don't exist... | 13:20 |
| *** Phlogistique <Phlogistique!~phlogisti@195.154.54.216> has quit IRC | 13:22 | |
| melonipoika | that was it, thanks rburton! | 13:26 |
| melonipoika | btw when looking into this I found this in the pulseaduio .inc file | 13:26 |
| melonipoika | LIC_FILES_CHKSUM = "file://GPL;md5=4325afd396febcb659c36b49533135d4 \ | 13:26 |
| melonipoika | shouldn't this be LIC_FILES_CHKSUM = "file://${COMMON_LICENSE_DIR}/GPL-2.0;md5=801f80980d171dd6425610833a22dbe6 ? | 13:27 |
| rburton | no | 13:27 |
| melonipoika | oh | 13:27 |
| rburton | that is relative to ${S} and refers to the GPL file in the tarball | 13:27 |
| melonipoika | i see | 13:27 |
| rburton | LIC_FILES_CHKSUM is designed to detect license changes *in the source itself* | 13:27 |
| rburton | so there's no point to pointing it at a file that isn't in the source | 13:27 |
| melonipoika | makes sense | 13:28 |
| rburton | it should be pointing at LICENSE as that is where the terms are, it's a fair assumption that "GPL is going to be the GPL | 13:28 |
| rburton | but if LICENSE changes then we need to be warned | 13:28 |
| *** Nilesh_ <Nilesh_!uid116340@gateway/web/irccloud.com/x-kzcsxzgojxilpimq> has joined #yocto | 13:29 | |
| * rburton adds | 13:29 | |
| *** manuel_ <manuel_!~manuel@c-24-61-40-209.hsd1.ma.comcast.net> has joined #yocto | 13:31 | |
| JaMa | rburton: thanks for cmake cleanups! | 13:32 |
| *** igor3 <igor3!~igor@177.159.144.73> has quit IRC | 13:32 | |
| rburton | JaMa: i hate cmake | 13:33 |
| rburton | JaMa: those patches took about a day of fiddling and testing. | 13:33 |
| rburton | JaMa: that said, buildstats-diff is AWESOME and now queued for oe-core | 13:33 |
| *** ntl <ntl!~nathanl@99-127-51-4.lightspeed.austtx.sbcglobal.net> has joined #yocto | 13:34 | |
| *** igor3 <igor3!~igor@189.112.127.225> has joined #yocto | 13:35 | |
| *** challinan <challinan!~chris@173-10-226-189-BusName-WestFlorida.hfc.comcastbusiness.net> has quit IRC | 13:36 | |
| JaMa | rburton: that's why there was bugzilla report for that, sorry that in the end it fall on you to handle | 13:38 |
| *** maxin <maxin!~maxin@37-219-81-187.nat.bb.dnainternet.fi> has joined #yocto | 13:40 | |
| joshuagl | don't listen to rburton, he loves hacking around buildsystems | 13:42 |
| rburton | it doesn't help my case if i say i have the start of a meson recipe does it | 13:43 |
| *** Phlogistique <Phlogistique!~phlogisti@195.154.54.216> has joined #yocto | 13:43 | |
| joshuagl | it absolutely does not | 13:43 |
| *** fenrig <fenrig!5ee32de5@gateway/web/freenode/ip.94.227.45.229> has joined #yocto | 13:44 | |
| joshuagl | in fact I almost asked you how it was going so as to prove the point :-) | 13:44 |
| fenrig | Hi, is it possible ffmpeg isnt building with mp3 support? I'm having a double free with mpd playing a mp3 stream using ffmpeg | 13:44 |
| fenrig | and apparently gst-ffmpeg is blacklisted | 13:45 |
| *** behanw <behanw!uid110099@gateway/web/irccloud.com/x-ibeiogkweepczzzp> has joined #yocto | 13:55 | |
| *** madisox <madisox!~madison@12.30.244.5> has joined #yocto | 13:56 | |
| *** slidercrank <slidercrank!~slidercra@unaffiliated/slidercrank> has joined #yocto | 13:56 | |
| *** AndersD <AndersD!~anders@213-64-218-130-no126.business.telia.com> has quit IRC | 14:02 | |
| *** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has quit IRC | 14:07 | |
| *** fenrig <fenrig!5ee32de5@gateway/web/freenode/ip.94.227.45.229> has quit IRC | 14:20 | |
| *** manuel_ <manuel_!~manuel@c-24-61-40-209.hsd1.ma.comcast.net> has quit IRC | 14:20 | |
| *** mckoan is now known as mckoan|away | 14:23 | |
| *** manuel_ <manuel_!~manuel@c-24-61-40-209.hsd1.ma.comcast.net> has joined #yocto | 14:23 | |
| *** manuel_ <manuel_!~manuel@c-24-61-40-209.hsd1.ma.comcast.net> has quit IRC | 14:27 | |
| RP | rburton: I'm not convinced about the build-appliance fix btw :/ | 14:30 |
| *** alexlarsson <alexlarsson!~alexl@213-66-155-112-no94.tbcn.telia.com> has joined #yocto | 14:30 | |
| RP | rburton: its defeating the artefact manifest the deploy_dir changes were meant to help | 14:30 |
| alexlarsson | Who would i do an:Ä | 14:31 |
| alexlarsson | RDEPENDS_${PN} += | 14:31 |
| alexlarsson | but only for certain arches? | 14:31 |
| alexlarsson | I.e. I want to add libasan-staticdev | 14:31 |
| alexlarsson | but its not there on arm | 14:31 |
| *** caiortp <caiortp!~inatel@131.221.240.204> has quit IRC | 14:32 | |
| *** manuel_ <manuel_!~manuel@c-24-61-40-209.hsd1.ma.comcast.net> has joined #yocto | 14:36 | |
| *** LocutusOfBorg <LocutusOfBorg!~Gianfranc@37.180.75.6> has joined #yocto | 14:37 | |
| *** LocutusOfBorg <LocutusOfBorg!~Gianfranc@ubuntu/member/locutusofborg> has joined #yocto | 14:37 | |
| alexlarsson | Do i use RDEPENDS_${PN}_append_x86-64 ? | 14:39 |
| rburton | alexlarsson: that looks like it would work | 14:41 |
| *** Anticom <Anticom!~quassel@217.6.33.234> has quit IRC | 14:42 | |
| alexlarsson | rburton: cool | 14:42 |
| alexlarsson | this whole parsing-variable-names thing scares me to no end | 14:43 |
| *** manuel_ <manuel_!~manuel@c-24-61-40-209.hsd1.ma.comcast.net> has quit IRC | 14:43 | |
| alexlarsson | Who defines what are valid prefixes? and what about ordering, conflicts, etc | 14:43 |
| * alexlarsson shudders | 14:43 | |
| rburton | mwhahaha | 14:45 |
| alexlarsson | I guess i don't really want to know... | 14:45 |
| *** alimon1 <alimon1!~alimon@134.134.139.76> has quit IRC | 14:45 | |
| alexlarsson | what would _x86-64_append do? | 14:46 |
| rburton | nothing | 14:46 |
| rburton | ordering is wrong | 14:46 |
| alexlarsson | What about a package called "append"? | 14:46 |
| *** manuel_ <manuel_!~manuel@c-24-61-40-209.hsd1.ma.comcast.net> has joined #yocto | 14:46 | |
| rburton | well in this case the logic actually looks for a variable called "RDEPENDS_" + pkg | 14:46 |
| rburton | so don't call a package append | 14:47 |
| alexlarsson | little bobby drop tables... | 14:47 |
| *** yahya93 <yahya93!c525ed02@gateway/web/freenode/ip.197.37.237.2> has joined #yocto | 14:48 | |
| *** alimon1 <alimon1!~alimon@134.134.137.75> has joined #yocto | 14:50 | |
| *** alimon1 <alimon1!~alimon@134.134.137.75> has left #yocto | 14:50 | |
| rburton | alexlarsson: yeah… | 14:50 |
| *** alimon1 <alimon1!alimon@nat/intel/x-nwjwjpcdvkdcxylj> has joined #yocto | 14:50 | |
| yahya93 | hello , I have a question in Toaster. I used Toaster to make an rpi-hwup-image for raspberrypi 2 , but it didn't generate the sdimg file , does anybody know how to do that using Toaster ? | 14:51 |
| *** simonl <simonl!uid6729@gateway/web/irccloud.com/x-llhlfscjzzqjipxc> has joined #yocto | 14:51 | |
| belen | yahya93: you would need to add the image type to the IMAGE_FSTYPES variable. If you are using the master branch, you can do so from toaster. | 14:53 |
| yahya93 | belen: thanks for your answer, but the sdimg is not listed in the IMAGE_FSTYPES | 14:55 |
| present | yahya93: There use to be bug report/feature request about that | 14:56 |
| present | yahya93: And you can directly edit the proper file which is using Toaster to add sdimg in it | 14:57 |
| belen | yahya93: present is correct. The bug is fixed, but only in master, not in the last stable release | 14:58 |
| yahya93 | when I creat a new project , I don't find master listed in the options, only Jethro and Krogoth | 14:58 |
| yahya93 | belen: when I creat a new project , I don't find master listed in the options, only Jethro and Krogoth | 14:59 |
| *** present <present!c2336e7b@gateway/web/freenode/ip.194.51.110.123> has quit IRC | 14:59 | |
| belen | yahya93: yes, that's because you are using the Yocto Project krogoth release. When I say master, I mean the Yocto Project development branch | 15:00 |
| *** manuel_ <manuel_!~manuel@c-24-61-40-209.hsd1.ma.comcast.net> has quit IRC | 15:00 | |
| belen | yahya93: a possible workaround is to edit the poky/bitbake/lib/toaster/orm/models.py file. That file contains a list of image types: you can add sdimg to that list, and you will then able to select it from the toaster web ui | 15:02 |
| belen | yahya93: I think the proper name is rpi-sdimg, but I am not 100% sure | 15:03 |
| *** jonver <jonver!~jonver___@dd577603a.access.telenet.be> has quit IRC | 15:04 | |
| *** alexlarsson <alexlarsson!~alexl@213-66-155-112-no94.tbcn.telia.com> has left #yocto | 15:04 | |
| michaelw1 | yahya93: ( http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/bitbake/lib/toaster/orm/models.py?h=krogoth#n645 ) | 15:05 |
| *** TobSnyder <TobSnyder!~schneider@ip9234b0ae.dynamic.kabel-deutschland.de> has quit IRC | 15:06 | |
| *** toanju <toanju!~toanju@185.27.182.30> has quit IRC | 15:07 | |
| yahya93 | belen & michaelwl: That was great help! thank you very much | 15:08 |
| *** florian <florian!~fuchs@Maemo/community/contributor/florian> has quit IRC | 15:08 | |
| *** jonver <jonver!~jonver___@dD577603A.access.telenet.be> has joined #yocto | 15:09 | |
| *** qt-x <qt-x!~Thunderbi@217.10.196.2> has quit IRC | 15:10 | |
| belen | yahya93: no worries. Any other questions, let us know | 15:14 |
| *** jonver <jonver!~jonver___@dD577603A.access.telenet.be> has quit IRC | 15:20 | |
| *** manuel_ <manuel_!~manuel@209.6.175.242> has joined #yocto | 15:24 | |
| *** zeenix <zeenix!~zeenix@83.218.80.242> has quit IRC | 15:28 | |
| *** maxin <maxin!~maxin@37-219-81-187.nat.bb.dnainternet.fi> has quit IRC | 15:32 | |
| *** gtristan <gtristan!~tristanva@110.11.179.37> has quit IRC | 15:32 | |
| *** oob <oob!~paulg@OTWAON23-3096772825.sdsl.bell.ca> has quit IRC | 15:32 | |
| *** manuel_ <manuel_!~manuel@209.6.175.242> has quit IRC | 15:34 | |
| *** manuel_ <manuel_!~manuel@209.6.175.242> has joined #yocto | 15:34 | |
| *** morphis_ <morphis_!~morphis@pD9ED643F.dip0.t-ipconnect.de> has joined #yocto | 15:35 | |
| *** morphis__ <morphis__!~morphis@pD9ED6288.dip0.t-ipconnect.de> has quit IRC | 15:38 | |
| *** vmeson <vmeson!~rmacleod@24-212-184-107.cable.teksavvy.com> has joined #yocto | 15:43 | |
| *** robertmarshall <robertmarshall!~robertmar@82-70-136-246.dsl.in-addr.zen.co.uk> has quit IRC | 15:48 | |
| *** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has joined #yocto | 15:48 | |
| *** ntl <ntl!~nathanl@99-127-51-4.lightspeed.austtx.sbcglobal.net> has quit IRC | 15:49 | |
| *** LocutusOfBorg <LocutusOfBorg!~Gianfranc@ubuntu/member/locutusofborg> has quit IRC | 15:57 | |
| *** aehs29 <aehs29!~aehernan@134.134.137.73> has joined #yocto | 15:59 | |
| *** belen <belen!~Adium@134.134.137.71> has quit IRC | 16:02 | |
| *** yahya93 <yahya93!c525ed02@gateway/web/freenode/ip.197.37.237.2> has quit IRC | 16:12 | |
| *** yahya93 <yahya93!c525ed02@gateway/web/freenode/ip.197.37.237.2> has joined #yocto | 16:13 | |
| *** ntl <ntl!~nathanl@cpe-24-242-74-130.austin.res.rr.com> has joined #yocto | 16:14 | |
| *** maxin <maxin!~maxin@37-219-81-187.nat.bb.dnainternet.fi> has joined #yocto | 16:22 | |
| *** tobiash <tobiash!~quassel@212.118.206.70> has quit IRC | 16:22 | |
| *** belen <belen!Adium@nat/intel/x-fuqpznoakrsejytq> has joined #yocto | 16:22 | |
| *** tobiash <tobiash!~quassel@212.118.206.70> has joined #yocto | 16:23 | |
| *** fl0v0 <fl0v0!~fvo@pD9F6B9DE.dip0.t-ipconnect.de> has quit IRC | 16:24 | |
| *** belen <belen!Adium@nat/intel/x-fuqpznoakrsejytq> has quit IRC | 16:31 | |
| *** belen <belen!~Adium@134.134.137.71> has joined #yocto | 16:35 | |
| *** caiortp <caiortp!~inatel@131.221.240.204> has joined #yocto | 16:36 | |
| *** belen <belen!~Adium@134.134.137.71> has quit IRC | 16:42 | |
| *** tobiash <tobiash!~quassel@212.118.206.70> has quit IRC | 16:44 | |
| *** boucman_work <boucman_work!~boucman@193.56.60.161> has quit IRC | 16:44 | |
| *** tobiash <tobiash!~quassel@212.118.206.70> has joined #yocto | 16:45 | |
| *** egavinc <egavinc!~egavinc@43.red-2-139-180.staticip.rima-tde.net> has quit IRC | 16:49 | |
| *** gtristan <gtristan!~tristanva@110.11.179.37> has joined #yocto | 16:52 | |
| *** Biliogadafr <Biliogadafr!~pin@62.214.49.206> has quit IRC | 16:53 | |
| *** maxin <maxin!~maxin@37-219-81-187.nat.bb.dnainternet.fi> has left #yocto | 16:53 | |
| *** mortderire <mortderire!~rkinsell@192.198.151.45> has quit IRC | 16:54 | |
| *** Nilesh_ <Nilesh_!uid116340@gateway/web/irccloud.com/x-kzcsxzgojxilpimq> has quit IRC | 16:57 | |
| *** frsc <frsc!~frsc@dslb-178-002-210-000.178.002.pools.vodafone-ip.de> has quit IRC | 17:00 | |
| *** t0mmy <t0mmy!~tprrt@217.114.201.133> has quit IRC | 17:03 | |
| *** darwish_ <darwish_!~darwish@46.101.16.85> has quit IRC | 17:03 | |
| *** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto | 17:09 | |
| -YoctoAutoBuilder- build #326 of nightly-checkuri is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-checkuri/builds/326 | 17:13 | |
| -YoctoAutoBuilder- build #278 of nightly-no-x11 is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-no-x11/builds/278 | 17:15 | |
| *** falk0n <falk0n!~falk0n@a109-49-61-108.cpe.netcabo.pt> has quit IRC | 17:18 | |
| *** toscalix <toscalix!~toscalix@80.91.70.192> has quit IRC | 17:20 | |
| *** dreyna <dreyna!~dreyna@rrcs-74-87-90-2.west.biz.rr.com> has joined #yocto | 17:24 | |
| *** obsrwr_home <obsrwr_home!~obsrwr@188.24.242.116> has joined #yocto | 17:25 | |
| khem | kergoth: precisely, yes its for older gcc | 17:27 |
| *** dmoseley <dmoseley!~dmoseley@6532158hfc157.tampabay.res.rr.com> has joined #yocto | 17:27 | |
| khem | kergoth: or for arches where libatomic in gcc does not _yet_ support | 17:27 |
| khem | when you go back in versions then the support for atomics came in in pieces | 17:28 |
| *** alimon1 <alimon1!alimon@nat/intel/x-nwjwjpcdvkdcxylj> has quit IRC | 17:33 | |
| *** dv_ <dv_!~quassel@62.178.118.86> has quit IRC | 17:46 | |
| *** dv_ <dv_!~quassel@62.178.118.86> has joined #yocto | 17:46 | |
| *** aehs29 <aehs29!~aehernan@134.134.137.73> has left #yocto | 17:48 | |
| *** morphis_ <morphis_!~morphis@pD9ED643F.dip0.t-ipconnect.de> has quit IRC | 17:49 | |
| neverpanic | Is there an official Yocto project leadership? Or some people working full time on Yocto? kergoth, rburton maybe? | 17:50 |
| neverpanic | Or is there a mail address to send offers for the project? | 17:50 |
| armpit | neverpanic, see https://www.yoctoproject.org/about | 17:57 |
| neverpanic | armpit: Thanks, that answers my question | 18:02 |
| armpit | np | 18:02 |
| *** _markfeatherston <_markfeatherston!~mark@wsip-174-79-58-228.ph.ph.cox.net> has left #yocto | 18:02 | |
| *** joseppc <joseppc!~josep@c-8ae4e455.010-118-73746f7.cust.bredbandsbolaget.se> has joined #yocto | 18:15 | |
| *** joseppc <joseppc!~josep@linaro/joseppc> has joined #yocto | 18:15 | |
| *** challinan <challinan!~chris@173-10-226-189-BusName-WestFlorida.hfc.comcastbusiness.net> has joined #yocto | 18:18 | |
| *** Phlogistique <Phlogistique!~phlogisti@195.154.54.216> has quit IRC | 18:19 | |
| *** hatter <hatter!~hatter@h-90-120.a137.corp.bahnhof.se> has quit IRC | 18:19 | |
| otavio | Is someone using Docker to run KVM instances? We use it as a set of our test infrastructure and we are having problems to run multiple docker instances with KVM in parallel | 18:19 |
| *** dmoseley <dmoseley!~dmoseley@6532158hfc157.tampabay.res.rr.com> has quit IRC | 18:26 | |
| *** aehs29 <aehs29!aehernan@nat/intel/x-mftufgvgjifckjkp> has joined #yocto | 18:35 | |
| lukma1 | Dear all, | 18:40 |
| lukma1 | Please correct me if I'm wrong | 18:40 |
| *** t0mmy <t0mmy!~tprrt@ram31-1-82-234-79-177.fbx.proxad.net> has joined #yocto | 18:40 | |
| lukma1 | Is it doable to create my own core-image-XXXXXX image to be layer on top of for example core-image-minimal ? | 18:41 |
| *** arkver <arkver!~arkver@host81-135-82-73.range81-135.btcentralplus.com> has joined #yocto | 18:47 | |
| *** hatter <hatter!~hatter@c-5eeaaa50-74736162.cust.telenor.se> has joined #yocto | 18:49 | |
| *** dmoseley <dmoseley!~dmoseley@6532158hfc157.tampabay.res.rr.com> has joined #yocto | 18:49 | |
| *** alimon1 <alimon1!~alimon@134.134.139.74> has joined #yocto | 18:53 | |
| *** ntl <ntl!~nathanl@cpe-24-242-74-130.austin.res.rr.com> has quit IRC | 19:01 | |
| *** marka <marka!~marka@128.224.252.2> has joined #yocto | 19:01 | |
| *** hatter <hatter!~hatter@c-5eeaaa50-74736162.cust.telenor.se> has quit IRC | 19:03 | |
| jmesmon | lukma1: you could create a core-image-minimal_%.bbappend and append to vars in there, though I'm not sure that's really recommended practice. | 19:04 |
| *** obsrwr_home <obsrwr_home!~obsrwr@188.24.242.116> has quit IRC | 19:11 | |
| *** t0mmy <t0mmy!~tprrt@ram31-1-82-234-79-177.fbx.proxad.net> has quit IRC | 19:12 | |
| *** JaMa <JaMa!~martin@ip-89-176-104-169.net.upcbroadband.cz> has quit IRC | 19:15 | |
| *** kad <kad!~kad@unaffiliated/kad> has quit IRC | 19:15 | |
| *** ntl <ntl!~nathanl@cpe-24-242-74-130.austin.res.rr.com> has joined #yocto | 19:16 | |
| *** kad <kad!~kad@unaffiliated/kad> has joined #yocto | 19:17 | |
| kergoth | lukma1: what do you mean by layer? if you just want to use that as a starting point, your best bet is to just copy it to your own image. and core-image- isn't really appropriate naming anymore in that case | 19:25 |
| *** blueness <blueness!~blueness@gentoo/developer/blueness> has quit IRC | 19:25 | |
| *** poucelyne <poucelyne!~poucelyne@ip-62-235-25-109.dial.scarlet.be> has joined #yocto | 19:26 | |
| *** poucelyne <poucelyne!~poucelyne@ip-62-235-25-109.dial.scarlet.be> has left #yocto | 19:26 | |
| *** bluelightning <bluelightning!~paul@85.219.69.111.dynamic.snap.net.nz> has joined #yocto | 19:33 | |
| *** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto | 19:33 | |
| *** dreyna <dreyna!~dreyna@rrcs-74-87-90-2.west.biz.rr.com> has quit IRC | 19:37 | |
| *** yahya93 <yahya93!c525ed02@gateway/web/freenode/ip.197.37.237.2> has quit IRC | 19:42 | |
| *** aehs29 <aehs29!aehernan@nat/intel/x-mftufgvgjifckjkp> has left #yocto | 19:49 | |
| -YoctoAutoBuilder- build #573 of nightly-mips64 is complete: Failure [failed Running Sanity Tests] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-mips64/builds/573 | 19:54 | |
| rburton | you can do that | 19:55 |
| rburton | lukma1: easier to just copy core-image-minimal and then modify it as you want | 19:55 |
| *** Crofton <Crofton!~Crofton@66-87-84-216.pools.spcsdns.net> has joined #yocto | 19:57 | |
| rburton | just *how* evil is something like this in a recipe : ${B}/*-libtool --mode install install $b ${D}${bindir} | 20:00 |
| fray_ | should work as long as the shell properly processes the wild card -and- only matches one instance | 20:01 |
| fray_ | problem is if there are multiple matches it can fail | 20:01 |
| rburton | yeah | 20:01 |
| rburton | well its out-of-tree autotools | 20:01 |
| rburton | and i'm now getting gnu hash errors so obviously i do need to patch this makefile after all | 20:02 |
| *** mortderire <mortderire!~rkinsell@192.198.151.45> has joined #yocto | 20:02 | |
| fray_ | BTW I'm trying to avoid producing a backtrace in an event handler in case of a specific failure.. last week RP mentioned that he though it was a simple 'raise' exception (which I'm forgetting which exception) that will cause the system to clean up an exit, but no backtrace.. | 20:02 |
| fray_ | Anyone know what is needed? | 20:02 |
| fray_ | (bb.fatal prints an exception, which causes the actual error message to be obscured) | 20:02 |
| rburton | started looking at someone elses autotools and now i want to drink | 20:04 |
| rburton | conveniently its beerbods night | 20:05 |
| rburton | "we don't need automake" | 20:05 |
| rburton | fails to pass ldflags | 20:05 |
| rburton | missing install targets | 20:05 |
| fray_ | that is relatively normal.. there is a reason why people use the auto* tools.. | 20:05 |
| fray_ | even though they do often get in the way | 20:05 |
| kergoth | fray_: I don't think there's any way to avoid a traceback in all cases fro an event handler, i ran into this too. i was trying to exit out with an error from TaskStarted to prevent the ability to build in a certain case, but no exception really seemed to do the job, given what exceptions were handled where in the code | 20:05 |
| *** khem <khem!~khem@unaffiliated/khem> has quit IRC | 20:05 | |
| kergoth | we need to catch more from event.fire() at various places in the code | 20:06 |
| *** fray_ is now known as fray | 20:06 | |
| rburton | 300 line makefile.in, 80% of which is boilerplate that automake does | 20:06 |
| kergoth | FuncFailed -> traceback, bb.fatal -> traceback.. | 20:06 |
| * kergoth shrugs | 20:06 | |
| fray | kergoth that is pretty much what I'm trying to do.. | 20:06 |
| kergoth | rburton: ugh. reinventing the wheel badly.. | 20:07 |
| fray | I can see the event handler is parsing "SystemExit".. but that doesn't seem like necessarily a good thing to raise | 20:07 |
| kergoth | fray: also if you use the wrong one from the wrong event, you can end up exiting the main build process without proper cleanup | 20:07 |
| kergoth | fray: bb.fatal generates SystemExit. | 20:07 |
| fray | exactly | 20:07 |
| fray | Ahh didn't realize it did that.. | 20:07 |
| kergoth | bb.fatal runs sys.exit which raises SystemExit | 20:07 |
| fray | try: | 20:07 |
| fray | ret = handler(event) | 20:07 |
| fray | except (bb.parse.SkipRecipe, bb.BBHandledException): | 20:07 |
| fray | except SystemExit as exc: | 20:07 |
| fray | ... | 20:08 |
| fray | so I was expecting BBHandledException to "work".. but it doesn | 20:08 |
| fray | 't | 20:08 |
| kergoth | at least, bb.fatal used to. maybe it raises handledexception now, would ahve to double check the code | 20:08 |
| kergoth | at any rate, sys.exit() raises SystemExit, so you don't usually have to raise it explicitly | 20:08 |
| fray | fatal calls sys.exit(1) | 20:09 |
| kergoth | ah, okay, figued | 20:09 |
| kergoth | the problem is, even if the code in bb.event.fire catches errors, prints them,a dn raises handledexception, we'd still need to catch handledexception from every call to event.fire(), which we don't do, afaik | 20:09 |
| *** seebs <seebs!~seebs@home.seebs.net> has joined #yocto | 20:09 | |
| kergoth | need to add try/catch blocks to every fire() call either way | 20:10 |
| fray | ya, I wasn't expecting bb.fatal to produce a trace | 20:10 |
| fray | well, I clearly have the backtrace for the event handler.. ;) | 20:10 |
| kergoth | :) | 20:10 |
| fray | problem is I don't understand what to do if I do catch the BBHandledException.... | 20:10 |
| bluelightning | we need a test for that apparently, because it sounds like it's regressed... | 20:10 |
| fray | (I'm looking for an example).. | 20:10 |
| kergoth | fray: i think it depends where the event is fired from | 20:10 |
| fray | I'm also not finding where the backtrace is actually fired | 20:11 |
| kergoth | i.e. cooker would want to initiate a shutdown | 20:11 |
| fray | seems like the place the backtrace is fired from is where the BBHandledException should be caught | 20:11 |
| kergoth | whereas a build running a function probably wants a FuncFailed to indicate the function failure to the runqueue | 20:11 |
| kergoth | so as always with exception handling, the answer is it depends on context :) | 20:11 |
| fray | the comments on BBHandledException is that anything that inherits it has already given the user enough information to fix the problem -- so not to print a backtrace. .:) | 20:12 |
| fray | obviously not working | 20:12 |
| kergoth | right, but it still has to appropriately handle the failure in some cases | 20:12 |
| kergoth | otherwise you'd just be ignoring the event handler failure, which is wrong | 20:12 |
| *** khem <khem!~khem@unaffiliated/khem> has joined #yocto | 20:12 | |
| kergoth | the fact that a message has been printed is great, but we still need to shut down the build | 20:12 |
| kergoth | so depends on what it means by handled, i guess :) | 20:12 |
| kergoth | afaik that message usually indicates 'an error has been printed, silently take whatever action is appropriate' | 20:13 |
| kergoth | erm, s/that message/that exception/ | 20:13 |
| * kergoth isn't a fan of BBHandledException, it was a massively brute force answer, when we should really have handled more on a case by case basis.. but bitbake is huge, so can understand why that route was taken | 20:14 | |
| fray | problem is something along the lines broke.. this "used to work" AFAIK.. | 20:14 |
| fray | maybe it still does in some cases, but I can't figure out where the actual backtrace is being dumped.. if I could, I could avoid it in the BBHANdledException, and but still do the rest of whatever the cleanup is | 20:14 |
| fray | last part I get in the backtrace is: | 20:15 |
| fray | File "/home/mhatle/git/oss/oe-core/bitbake/lib/bb/cookerdata.py", line 271, in CookerDataBuilder.parseBaseConfiguration(): | 20:15 |
| fray | 20:15 | |
| fray | > bb.event.fire(bb.event.ConfigParsed(), self.data) | 20:15 |
| fray | so it's one level 'above' that.. whatever caught the fault in the base config processing | 20:16 |
| kergoth | fire() does result in handlers being run, the only question is whether they run in the server or the ui, afaik | 20:16 |
| kergoth | would have to double check event.py | 20:17 |
| kergoth | hmm | 20:18 |
| *** khem <khem!~khem@unaffiliated/khem> has quit IRC | 20:18 | |
| fray | found the parse block in the parseBaseConfiguration | 20:18 |
| kergoth | it sure would be nice to break up some of bitbake's functionality to reduce the tight binding between the components and modules. i.e. split out fetch into a separate standalone package or cli tool, make the runqueue generation emit scripts + metadata so you culd use make or ninja to actually run the tasks, etc | 20:19 |
| fray | the three except blocks in the parseBaseConfiguration, all eventually raise bb.BBHandledException | 20:20 |
| fray | so why the hell is it doing a traceback | 20:20 |
| *** darknighte <darknighte!~darknight@pdpc/supporter/professional/darknighte> has quit IRC | 20:21 | |
| fray | is python itself doing the traceback? | 20:21 |
| *** khem <khem!~khem@unaffiliated/khem> has joined #yocto | 20:21 | |
| fray | I'm not seeing any try / exception blocks around tinfoil and it's BBCooker, which is what eventually runs the parseBaseConfiguration | 20:22 |
| Ulfalizer | fray: python itself prints tracebacks for uncaught exceptions | 20:23 |
| fray | I'm looking at knotty and such.. and I don't see any BBHandledExceptions code either | 20:23 |
| Ulfalizer | that's why you get "Traceback (most recent call last):" if you type "cduishciusdh" into the interactive interpreter :P | 20:23 |
| -YoctoAutoBuilder- build #929 of nightly-mips is complete: Failure [failed Running Sanity Tests] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-mips/builds/929 | 20:24 | |
| fray | so should hte UI be the one handling the exception to finish the shutdown? (I don't understand this part of bitbake) | 20:25 |
| *** mortderire <mortderire!~rkinsell@192.198.151.45> has quit IRC | 20:27 | |
| *** khem <khem!~khem@unaffiliated/khem> has quit IRC | 20:28 | |
| kergoth | fray: yes, an uncaught exception gets a traceback, as Ulfalizer says | 20:34 |
| *** marka <marka!~marka@128.224.252.2> has quit IRC | 20:34 | |
| fray | I added a catch in the event fire function, and suddenly the logger went away, so I saw all fo the 'debug' messages.. | 20:34 |
| fray | really odd | 20:34 |
| *** grma <grma!~gruberm@80.93.38.128> has quit IRC | 20:35 | |
| fray | wait.. no it worked this time.. | 20:36 |
| fray | I must have broken my environment.. :P | 20:36 |
| *** khem <khem!~khem@unaffiliated/khem> has joined #yocto | 20:37 | |
| *** khem <khem!~khem@unaffiliated/khem> has quit IRC | 20:43 | |
| *** caiortp <caiortp!~inatel@131.221.240.204> has quit IRC | 20:43 | |
| fray | AH-HA! I figured it out! | 20:44 |
| fray | the block in cookerdata.py was not explicitly handling bb.BBHandledException.. | 20:44 |
| fray | so it was getting caught by the 'except Exception:' block what was doing logger.exception("Error parsing configuration files") | 20:45 |
| fray | and logger.exception was producing a backtrace | 20:45 |
| kergoth | ah. that explains that one event, anyway :) | 20:45 |
| kergoth | almost none of the event.fire()s actually catch exceptions of any kind :( | 20:45 |
| fray | after that it worked fine.. I think I have a fairly simple fix | 20:45 |
| kergoth | nice | 20:45 |
| fray | - except bb.data_smart.ExpansionError as e: | 20:46 |
| fray | + except (bb.data_smart.ExpansionError, bb.BBHandledException) as e: | 20:46 |
| fray | that look 'reasonable'.. | 20:46 |
| fray | logger.error(str(e)) | 20:46 |
| fray | raise bb.BBHandledException | 20:46 |
| fray | (reset of it).. not sure if it makes sense to unconditionally print the 'e'.. since some instances of BBHandledException won't have an 'e' | 20:46 |
| kergoth | you shouldn't print a BBHandledException at all, by defintiion its error has already been printed | 20:47 |
| fray | ok.. I found some examples where people were doing 'BBHandledException('some message here')' which was confusing me | 20:47 |
| fray | easy enough, the line above: | 20:47 |
| fray | except SyntaxError: | 20:47 |
| fray | raise bb.BBHandledException | 20:47 |
| fray | can just be extneded to include BBHandledException | 20:47 |
| kergoth | are those really raising BBHandledException, not BBHandledException()? | 20:47 |
| kergoth | raising an exception class instead of an object is a bit odd | 20:47 |
| fray | thats what it says | 20:48 |
| fray | what I have now: | 20:48 |
| fray | - except SyntaxError: | 20:48 |
| fray | + except (SyntaxError, bb.BBHandledException): | 20:48 |
| fray | raise bb.BBHandledException | 20:48 |
| fray | except bb.data_smart.ExpansionError as e: | 20:48 |
| fray | logger.error(str(e)) | 20:48 |
| fray | that is cookerdata.py BTW | 20:48 |
| kergoth | raising a new BBHandledException instead of the one we already have is a little odd, though admittedly minor | 20:49 |
| kergoth | except bb.BBHandledException: raise; might be slightly cleaner, though at the cost of more lines of code | 20:49 |
| kergoth | debatable. | 20:49 |
| fray | I have to raise instead of letting it fall through.. but ya.. laternative is ... | 20:49 |
| fray | you beat me to it, but I don't see any real advantage in this code.. | 20:49 |
| kergoth | agreed, particularly since the class isn't carrying any information, it's not even an object half the time | 20:49 |
| kergoth | :) | 20:49 |
| fray | I don't see any real examples either way in the bitbake code...... | 20:49 |
| fray | I'll send up a change to the bitbake-devel | 20:51 |
| Ulfalizer | 'raise Foo' is the same as 'raise Foo()' if Foo is a class btw. you're only allowed to raise stuff that inherits from BaseException, so raising a class object wouldn't make sense anyway, making it unambiguous. | 20:54 |
| fray | DAMNIT.. I think I just sent crap to the mailing list.. | 20:54 |
| fray | drat | 20:54 |
| Ulfalizer | fray: git format-patch... --subject-prefix="PATH v2" ... ;) | 20:55 |
| Ulfalizer | could add a --cover-letter that explains what you changed since v1 too | 20:55 |
| fray | no.. it didn't send the commit ID I pasted.. it sent the commit ids of all of the patches AFTER the one I wanted (which are still in progress) | 20:55 |
| fray | :P | 20:55 |
| fray | at some point the git send-email changed behavior and no longer works like git log, git show, etc.. | 20:56 |
| kergoth | Ulfalizer: BBHandledException does inherit from BaseException, so really don't see your point there | 20:56 |
| kergoth | fray: also, bb.fatal() raises BBHandledException in current bitbake, but bb.msg.fatal() does a sys.exit | 20:56 |
| * kergoth rolls eyes | 20:56 | |
| Ulfalizer | kergoth: i meant at the language level. 'raise Foo()' can be shortened to 'raise Foo'. | 20:57 |
| fray | there we go.. the RIGHT patch sent this time | 20:57 |
| kergoth | Ulfalizer: interesting, didn't realize that. i like the () for consistency, but didn't realize raise would instantiate for us. cool | 20:58 |
| kergoth | "It must be either a subclass or an instance of BaseException. If it is a class, the exception instance will be obtained when needed by instantiating the class with no arguments." | 20:58 |
| *** paulg <paulg!~paulg@198-84-239-75.cpe.teksavvy.com> has quit IRC | 20:58 | |
| Ulfalizer | yep | 20:58 |
| fray | ahh.. with that patch, you are right.. bb.fatal works again.. no more backtrace! | 20:58 |
| fray | sweet | 20:58 |
| kergoth | fray: thanks for the inspiration, i realized i can fix my use case pretty trivially too. i needed to be able to fail from TaskStarted, so just had to move event.fire() into the try/except and add a clause for BBHandledException :) | 20:59 |
| * kergoth will send a patch too | 20:59 | |
| fray | I know some of this worked in the past (w/o dumping backtraces) so I'm guessing some code was changed around which triggered the faults (or maybe even python3 differences) | 21:00 |
| kergoth | clearly missing test cases, as bluelightning pointed out :\ | 21:01 |
| fray | this is an issue, I'm not sure how to implement a test case.. :| | 21:02 |
| bluelightning | that was an unsubtle hint btw ;) | 21:02 |
| fray | pretty easy.. run an event handler, run a bb.fatal(...) inside of it.. but do we have an existing event handler tests? | 21:02 |
| bluelightning | not that I know of | 21:02 |
| fray | (I don't see any, but maybe I'm not looking in the right place) | 21:02 |
| *** pohly <pohly!~pohly@p5DE8FF1A.dip0.t-ipconnect.de> has quit IRC | 21:03 | |
| bluelightning | unusually this is one you could probably do in the bitbake tests comfortably | 21:03 |
| fray | so if someone figures out the right way to implement event handler tests, I'm happy to add one | 21:03 |
| fray | I'm honestly now sure how to implement it.. the other tests all run functions inside bitbake.. | 21:03 |
| fray | I don't think that is what we want in this case | 21:04 |
| bluelightning | right, yeah, you won't have access to both sides | 21:04 |
| bluelightning | probably easier as an oe-selftest test then | 21:04 |
| bluelightning | meta/lib/oeqa/selftest/ | 21:04 |
| fray | we'd need a small layer or something to implement the 'fatal' event handler.. again, not sure how to do that in the oe self-tests.. but overall, I think you are right it would be easier in that environment | 21:06 |
| fray | I think | 21:06 |
| bluelightning | meta-selftest exists for that kind of thing (oe-selftest requires it to be in your config when running) | 21:06 |
| kergoth | problem is you have to cover all the codepaths for event.fire() in bitbake. we cant' fire them ourselves, it's not being cought in the bitbake code that's the problem | 21:06 |
| kergoth | so i.e. bitbake -p would be insufficient depending on which event handler is fatal'ing | 21:06 |
| kergoth | I wonder if we should test the runqueue task events, too | 21:06 |
| fray | kergoth, I think (over time) we could built up a reasonable set of event handlers and such to capture many of the cases.. | 21:06 |
| kergoth | those catch nothing, but any event could error out in the metadata | 21:07 |
| * kergoth tried erroring out from the runqueue task started event which immediately exited the bitbake server process, not pretty :) | 21:07 | |
| bluelightning | some events don't make it to the task handlers, that's true | 21:07 |
| bluelightning | er | 21:07 |
| fray | I've only ever done this stuff on events that run on 'early' | 21:07 |
| bluelightning | handlers defined in the metadata, that is | 21:07 |
| bluelightning | "class handlers", that's the term I meant to use | 21:08 |
| *** Tenhi_ <Tenhi_!~tenhi@static.177.80.201.138.clients.your-server.de> has joined #yocto | 21:11 | |
| * kergoth scratches head | 21:13 | |
| kergoth | if i bb.fatal() in a TaskStarted handler, should I fire TaskFailed? technically the task never ran... though I guess if TaskStarted fired at all, one should fail to ensure the mirrored events line up, even though not all TaskStarted event handlers ran.. | 21:14 |
| *** Crofton <Crofton!~Crofton@66-87-84-216.pools.spcsdns.net> has quit IRC | 21:14 | |
| kergoth | i wonder if it should continue to run the other event handlers when one of them fails, and collects the various errors/exceptions and shows them all, otherwise which event handlers run is highly dependent upon event registration order.. though maybe that's okay.. | 21:15 |
| kergoth | certain parts of bitbake really hurt my head | 21:16 |
| *** Tenhi_ <Tenhi_!~tenhi@static.177.80.201.138.clients.your-server.de> has quit IRC | 21:16 | |
| -YoctoAutoBuilder- build #257 of nightly-musl is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-musl/builds/257 | 21:17 | |
| fray | I'm not sure.. and I know eventually if the tasks and the controller are on different machines this is even more complicated | 21:18 |
| *** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has quit IRC | 21:18 | |
| *** blueness <blueness!~blueness@gentoo/developer/blueness> has joined #yocto | 21:21 | |
| *** lukma1 <lukma1!~lukma@109.241.15.61> has quit IRC | 21:21 | |
| kergoth | among other things, i think we should, one of these days, adopt oe-lite's change which added addtask-style dependencies / ordering control to event handling | 21:22 |
| *** dreyna <dreyna!~dreyna@rrcs-74-87-90-2.west.biz.rr.com> has joined #yocto | 21:23 | |
| fray | kergoth, did you see the LAYERRECOMMEND patch that was sent? | 21:25 |
| kergoth | yep. i'm a fan of the feature, haven't had a chance to review the code, though | 21:25 |
| fray | From the oe-arch conversation nobody really cared, and most were surprised there was auto priority stuff in bitbake -- but I think it should be fine | 21:25 |
| * kergoth nods | 21:25 | |
| fray | it's more or less a copy of the existing dependency checking, but stripped of 'errors'.. debugging was added.. and any miss deps are just excluded | 21:25 |
| kergoth | yeah | 21:25 |
| fray | actually turned out easier then I thought it would be.. | 21:26 |
| kergoth | for what its worth it has my ack for 2.3, i want to see it merged eventually | 21:26 |
| fray | we're currently working on adding a 'recommends' flag to the layer index as well (for the layerDependency) data structure | 21:26 |
| kergoth | nice | 21:26 |
| fray | what we want it for is primarily our 'download layers'.. We've got special layers that are just the cached download components for a given layer, like oe-core or meta-oe, or meta-networking, etc.. we'd like those to be 'recommended' depedencies so toaster and others can optionally pull them down from our servers | 21:27 |
| fray | user can basically choose to pull down everything right now -- or not do it and take the download hit 'later' | 21:27 |
| fray | (now also facilitates off-line building) | 21:27 |
| fray | but I expect over time, we can do other recommended layers and filtering w/ bbmask and such if a collection is available or not | 21:29 |
| *** arkver <arkver!~arkver@host81-135-82-73.range81-135.btcentralplus.com> has quit IRC | 21:32 | |
| *** agust <agust!~agust@p4FCB58BB.dip0.t-ipconnect.de> has quit IRC | 21:33 | |
| *** lukma1 <lukma1!~lukma@109.241.15.61> has joined #yocto | 21:34 | |
| *** a1cypher <a1cypher!~mroy@mail.krausglobal.com> has joined #yocto | 21:36 | |
| kergoth | ah, interesting. hadn't thought about using layers for downloads | 21:36 |
| kergoth | we do a lot of 'inherit this class only if this layer is available' in our distro | 21:36 |
| *** dmoseley <dmoseley!~dmoseley@6532158hfc157.tampabay.res.rr.com> has quit IRC | 21:36 | |
| kergoth | (and similar) | 21:36 |
| fray | downloads as layers make it easy to keep pieces 'connected' at least | 21:37 |
| *** ntl <ntl!~nathanl@cpe-24-242-74-130.austin.res.rr.com> has quit IRC | 21:37 | |
| fray | you can also automate this by adjusting the DL_DIR to include the layer name in the generated path.. ;) | 21:37 |
| fray | then do a bitbake -c fetchall universe -k | 21:37 |
| a1cypher | Hey. Trying to add avahi to my image. I added "avahi" to my IMAGE_INSTALL_append list but now I get "avahi not found in the base feeds" when I try to bitbake the image | 21:38 |
| fray | about 90% of the stuff is already in the right place for you at the end | 21:38 |
| a1cypher | avahi definitely builds and I can see the binaries in the work folder | 21:38 |
| fray | avahi is not the anem of a generated package.. you will need to look at the recipe, or the package output and figure out what the name of the -package- produced is | 21:38 |
| fray | recipe and package names are not always the same | 21:38 |
| bluelightning | a1cypher: I think you want avahi-daemon instead | 21:39 |
| Ulfalizer | a1cypher: http://www.yoctoproject.org/docs/2.2/ref-manual/ref-manual.html#viewing-package-information-with-oe-pkgdata-util might be helpful | 21:39 |
| fray | (the 'PACKAGES' variable in the recipes helps determine the names.. and I think he's right.. avahi-daemon is likely what you want) | 21:39 |
| Ulfalizer | i've updated the DEPENDS and RDEPENDS glossary entries in the 2.2 reference manual to try to clear up recipe vs. package confusion too | 21:40 |
| bluelightning | I think perhaps the issue is the recipe lies and says it produces an ${PN} package, if it didn't do that at least you would get an error earlier | 21:40 |
| a1cypher | if I do bitbake -e avahi | grep ^PACKAGES= I get "PACKAGES="libavahi-gobject avahi-daemon libavahi-common libavahi-core libavahi-client avahi-dnsconfd libavahi-glib libavahi-ui avahi-autoipd avahi-utils avahi-dbg avahi-staticdev avahi-dev avahi-doc avahi-locale avahi" | 21:40 |
| a1cypher | I thought since "avahi" was at the end there that If I chose that one I would get them all | 21:40 |
| fray | bluelightning it is.. certainly one of the complaints I've had from customers.. why is it in the list, if it's not provided | 21:40 |
| fray | :/ | 21:40 |
| bluelightning | a1cypher: right, it claims it will produce that package, it either should produce it or not claim that it does | 21:40 |
| fray | a1cypher that is how a few things were implemented, but not everything.. | 21:41 |
| *** mortderire <mortderire!~rkinsell@192.198.151.45> has joined #yocto | 21:41 | |
| bluelightning | more of a frustration than an outright bug, but IMO we should correct it | 21:41 |
| a1cypher | ok, so I'll try just including the specific ones that I want and see if that helps | 21:41 |
| fray | might be a cleanup worth exploring in YP 2.3, a test that exposing things not produced, then someone can go in and cleanup the PACKAGES.. (there will always be SOME package entries that are dynamic... but most are not) | 21:41 |
| *** ant_home <ant_home!~ant__@host113-211-dynamic.54-79-r.retail.telecomitalia.it> has joined #yocto | 21:42 | |
| a1cypher | also the specific error message is like 10 screens of red text with no linebreaks. | 21:42 |
| bluelightning | a1cypher: yuck - can you pastebin that? | 21:43 |
| a1cypher | sure | 21:43 |
| *** joshuagl <joshuagl!~joshuagl@192.198.151.44> has quit IRC | 21:43 | |
| -YoctoAutoBuilder- build #947 of nightly-multilib is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-multilib/builds/947 | 21:44 | |
| a1cypher | http://pastebin.com/EibjpVP4 | 21:44 |
| bluelightning | I believe you can thank fray for that message ;) | 21:45 |
| bluelightning | I've always thought it was pretty hideous myself | 21:45 |
| *** smurray <smurray!sid98062@gateway/web/irccloud.com/x-iienehqdeeqfmaio> has quit IRC | 21:45 | |
| fray | confused.. the error you care about is at the very end.. | 21:46 |
| fray | isn't it? | 21:46 |
| *** rob-oi-ma <rob-oi-ma!sid155560@gateway/web/irccloud.com/x-cskkltqpkyikdrhr> has quit IRC | 21:46 | |
| fray | ahh no.. it was reorderd.. | 21:47 |
| bluelightning | fray: "not found in the base feeds (<bleaaaaaargh massive list that's way too long to read>)" | 21:47 |
| fray | no idea why | 21:47 |
| *** flynn378 <flynn378!sid63564@gateway/web/irccloud.com/x-qrayoewgfbnjjmbn> has quit IRC | 21:47 | |
| *** zibri <zibri!~zibri@2a01:7e01::f03c:91ff:febb:9538> has quit IRC | 21:47 | |
| fray | should be hte other way around.. the command being run was (long list).. error was (end) | 21:47 |
| fray | I don't know if that is produced in the code or in smart | 21:47 |
| bluelightning | in our code | 21:47 |
| bluelightning | the utility of that list itself is questionable | 21:47 |
| fray | I suspect thiswas introduced in conversation ot the lib.oe version then | 21:48 |
| fray | the lsit is needed.. it's stupid, but the number of questions I get from customers as "Why is XYZ failing, when I didn't ask for it" (when it's explicitly in the list of packages you asked for) | 21:48 |
| *** zibri <zibri!~zibri@2a01:7e01::f03c:91ff:febb:9538> has joined #yocto | 21:48 | |
| fray | so thus, the list of explicitly asked for packages is there... | 21:48 |
| *** smurray <smurray!sid98062@gateway/web/irccloud.com/x-sqcbyrffroaevzgg> has joined #yocto | 21:49 | |
| fray | but I agree, ordering is backwards.. | 21:49 |
| fray | error should be last | 21:49 |
| fray | the rest is simply diagnostics | 21:49 |
| Ulfalizer | fray: maybe i'm blind, but it doesn't seem to explain what that list is either. it just dumps it out. | 21:49 |
| fray | it's a list of everything user asked for | 21:50 |
| fray | that simple | 21:50 |
| Ulfalizer | don't think that'll be obvious to people | 21:50 |
| fray | last time I made any substantial changes was when this was still shell code.. | 21:50 |
| fray | it used to have text around it to indicate just that | 21:50 |
| fray | a lot of things disappeared when it went to python | 21:50 |
| *** rob-oi-ma <rob-oi-ma!sid155560@gateway/web/irccloud.com/x-tpbokuhxsppqsovs> has joined #yocto | 21:51 | |
| fray | with that said, I don't know if this is in smart or not.. but I don't rmember it being there.. | 21:51 |
| bluelightning | fray: erm, the list is the list of all packages in the feeds, not the list that the user has requested for the image | 21:51 |
| a1cypher | list is fine, but maybe put some line breaks in there so that its one package per line or something | 21:51 |
| fray | bluelighting, then the list has changed | 21:52 |
| Ulfalizer | "This is the set of packages that was requested to be installed into the root filesystem. Note that some of these packages might have been pulled in via dependencies between packages even if they were not explicitly requested." | 21:52 |
| fray | it was originally the list of the items the user asked for | 21:52 |
| Ulfalizer | i'd add something like that. makes it clear. | 21:52 |
| Ulfalizer | if that's what it is | 21:52 |
| bluelightning | someone needs to check the code | 21:52 |
| fray | bb.note("Installing the following packages: %s" % ' '.join(pkgs)) | 21:53 |
| fray | that is the list I was referring to | 21:53 |
| fray | so it si still in the code | 21:53 |
| bluelightning | that's not the list I'm referring to ;) | 21:53 |
| fray | yes, but that is what should have been printed -before- the error message | 21:53 |
| bluelightning | err_msg += " ".join(self.fullpkglist) | 21:54 |
| fray | (which I suspect it is in the log) | 21:54 |
| bluelightning | that's what makes it excessive | 21:54 |
| fray | make it a '=+' instead and you'd at least get the order right | 21:54 |
| bluelightning | why do we need that list though? especially given it's not the list you're referring to | 21:55 |
| fray | ya.. this is all from the original conversion of the shell code to the python code.. | 21:55 |
| fray | I'm saying there are at least two problems here.. | 21:55 |
| bluelightning | by all means write it to a file so you can look at it, if it helps debugging | 21:55 |
| fray | problem 1.. the error message should be last.. | 21:55 |
| fray | =+ would fix that | 21:55 |
| fray | problem 2... there is too much crap there for most people | 21:55 |
| fray | as long as the error message is last, and some qualification of what that list is.. I don't care either way if it's presented or not.. but as is, nobody knows what the list is anymore | 21:56 |
| *** flynn378 <flynn378!sid63564@gateway/web/irccloud.com/x-cadeireaicvzhaoe> has joined #yocto | 21:56 | |
| Ulfalizer | problem 3: it ought to to give more details about what that list is, imo. the explicitly requested packages? all packages? what does the thing after the @ refer to? | 21:56 |
| fray | yes.. I consider that part of 2.. | 21:57 |
| fray | the log itself does list what was being attempted.. | 21:57 |
| fray | it's only on error that is generated.. and it should be generated as "available packages" \n "error message" | 21:57 |
| *** rburton <rburton!~Adium@home.burtonini.com> has quit IRC | 21:57 | |
| fray | littlery should say something about "available packages" | 21:57 |
| fray | - err_msg += " ".join(self.fullpkglist) | 21:58 |
| fray | + err_msg =+ "List of available packages: " + " ".join(self.fullpkglist) | 21:58 |
| fray | there that would be a reasonable simple change.. | 21:58 |
| bluelightning | if we're making a change, we should drop that list | 21:58 |
| *** marka_home <marka_home!~marka@135-23-92-83.cpe.pppoe.ca> has quit IRC | 21:58 | |
| fray | so the question is, do we have a simple way for a user to know what packages are listed in the smart database? if not, we need to dump diagnostics "somewhere" in this type of failure | 21:59 |
| fray | and if it's not in the main log, then at least a message to indicate where it was dumped | 21:59 |
| *** berton <berton!~fabio@177.100.227.233> has quit IRC | 22:00 | |
| *** bfederau <bfederau!~quassel@service.basyskom.com> has quit IRC | 22:01 | |
| *** fmeerkoetter <fmeerkoetter!~quassel@service.basyskom.com> has quit IRC | 22:01 | |
| *** fmeerkoetter <fmeerkoetter!~quassel@service.basyskom.com> has joined #yocto | 22:01 | |
| *** bfederau <bfederau!~quassel@service.basyskom.com> has joined #yocto | 22:01 | |
| * Ulfalizer dislikes the term "base feed" | 22:01 | |
| bluelightning | I'm not sure what that means either, if anything | 22:02 |
| Ulfalizer | "'avahi' not found among the packages that were built" seems much more concrete | 22:02 |
| Ulfalizer | or something like that | 22:02 |
| fray | it could have been built.. and not loaded into the feeds.. | 22:03 |
| fray | - err_msg = '%s not found in the base feeds (%s).\n' % \ | 22:04 |
| fray | + err_msg = '%s not found in the deploy feeds (%s).\n' % \ | 22:04 |
| fray | that better? | 22:04 |
| Ulfalizer | might be guessable that the package also needs to be copied into some common area after it's built though | 22:04 |
| *** mortderire <mortderire!~rkinsell@192.198.151.45> has quit IRC | 22:04 | |
| fray | packages that were built really has no meaning here.. | 22:04 |
| Ulfalizer | and registered | 22:04 |
| fray | deploy is where the stuff ends up once constructed.. the stuff in deploy is used to generate the feeds | 22:04 |
| Ulfalizer | i guess i just dislike the term "feed" :P | 22:05 |
| fray | me looks at others for that.. | 22:05 |
| Ulfalizer | but whatevz | 22:05 |
| fray | feed is not my term | 22:05 |
| fray | I'd call it a package repository myself -- but that is not the OE term for that.. it's a feed.. (and apparently it has been called a feed for a very long time, much longer then the Yocto Project has been around) | 22:07 |
| bluelightning | feed is really the right term here, other issues aside | 22:07 |
| *** mortderire <mortderire!~rkinsell@192.198.151.44> has joined #yocto | 22:07 | |
| Ulfalizer | yeah, i'd go for package repository too | 22:07 |
| fray | other option w/ that part of the message, is just say "%s not found in the feeds (%s).\n" | 22:08 |
| fray | originally it was expected that the user could add additional feeds (outside of the build system) for the image install.. but I don't think that was ever implemented nor will it likely be at this point | 22:08 |
| bluelightning | we probably ought to add a hint for the user as to the cause, which is almost always the scenario that prompted this whole thing (recipe claimed to package somehting and didn't) | 22:08 |
| Ulfalizer | regardless of what the established terminology is, i suspect many of the people that would be helped the most by that message have a very vague idea of what a "feed" is | 22:09 |
| fray | ahh I know why it said 'base' | 22:10 |
| fray | there are two different error message paths: | 22:10 |
| fray | if you select 'lib32-bash', the message is not found in the lib32 feeds (%s)... | 22:11 |
| fray | otherwise it's 'base'.. | 22:11 |
| fray | what else do we call the non-multilib.. thus it was 'base' | 22:11 |
| kergoth | I'd just say 'lib32 feeds' and 'feeds', and know that the lack of lib32 indicates not lib32, but *shrug* | 22:12 |
| *** alimon1 <alimon1!~alimon@134.134.139.74> has quit IRC | 22:13 | |
| Ulfalizer | "'%s' not found in the package feeds (found in %s). Make sure that some recipe builds this package." would give a tiny hint at least | 22:13 |
| Ulfalizer | if references to the manual are okay, there's stuff to link there too | 22:14 |
| Ulfalizer | kergoth: yeah, that seems better | 22:15 |
| Ulfalizer | it's not clear what "base" means (obviously, from earlier discussion :P) | 22:15 |
| fray | http://pastebin.com/gCvfakHV | 22:19 |
| fray | Ugh.. no sorry premature pastebin.. ;) | 22:19 |
| *** a1cypher <a1cypher!~mroy@mail.krausglobal.com> has quit IRC | 22:24 | |
| *** manuel_ <manuel_!~manuel@209.6.175.242> has quit IRC | 22:26 | |
| fray | there we go... | 22:26 |
| fray | http://pastebin.com/Tqd5wb5U | 22:26 |
| fray | that was what I was trying to paste before | 22:26 |
| fray | order is now more logical | 22:26 |
| fray | and if you look at the logs it all still makes sense.. | 22:27 |
| Ulfalizer | "'%s' not found in the package feeds (found in %s). Make sure that some recipe builds this package. Note that a package declared in PACKAGES within a recipe will not get built if it turns out empty (unless ALLOW_EMPTY_<pkg> = "1" is used)." | 22:27 |
| Ulfalizer | how about that version? that also explains what the problem might be (if i've understood it correctly). | 22:27 |
| *** ant_home <ant_home!~ant__@host113-211-dynamic.54-79-r.retail.telecomitalia.it> has quit IRC | 22:32 | |
| *** igor3 <igor3!~igor@189.112.127.225> has quit IRC | 22:33 | |
| Ulfalizer | "'ahavi' not found in the package feeds (qemux86 i586 x86 noarch any all - found in /.../tmp/deploy/rpm). Make sure that..." | 22:35 |
| Ulfalizer | i think that'd help a lot more people diagnose the issue themselves | 22:35 |
| *** dreyna <dreyna!~dreyna@rrcs-74-87-90-2.west.biz.rr.com> has quit IRC | 22:36 | |
| Ulfalizer | fray: opinions? | 22:38 |
| fray | http://pastebin.com/yG2XWeRM | 22:41 |
| Ulfalizer | i'd add a "-" before the "in", to make it clear that it's not part of the list | 22:41 |
| Ulfalizer | and also the rest of the hint :P | 22:42 |
| fray | I'm not sure how i feel about that.. either way | 22:42 |
| fray | http://pastebin.com/KTGX4VkW | 22:43 |
| Ulfalizer | lgtm (sans hint) | 22:44 |
| fray | there sent to the oe-core list.. | 22:47 |
| Ulfalizer | ahhh... didn't notice that you added the hint :) | 22:48 |
| Ulfalizer | sorry | 22:48 |
| Ulfalizer | maybe it could be on the same line | 22:48 |
| Ulfalizer | but too late :P | 22:48 |
| fray | it doesn't look good on one line, you end up with the same jumbled mess as the one line list of all packages | 22:49 |
| Ulfalizer | yeah, it might just be me being blind | 22:49 |
| Ulfalizer | (not for real) | 22:49 |
| fray | it's hit the list.. feel free to ack it | 22:50 |
| fray | damned thunderstorm keeps knocking me offline for 2-10 minutes at a time.. | 22:50 |
| *** nighty <nighty!~nighty@s229123.ppp.asahi-net.or.jp> has quit IRC | 22:51 | |
| *** bbhoss <bbhoss!sid18216@gateway/web/irccloud.com/x-geqsxwcwaxjxufoc> has quit IRC | 22:54 | |
| *** mjl <mjl!sid16781@gateway/web/irccloud.com/x-mpruswktnoegoaaf> has quit IRC | 22:56 | |
| *** khem <khem!~khem@unaffiliated/khem> has joined #yocto | 22:56 | |
| *** bbhoss <bbhoss!sid18216@gateway/web/irccloud.com/x-nyhcuyigzuttqddh> has joined #yocto | 22:58 | |
| *** mjl <mjl!sid16781@gateway/web/irccloud.com/x-zzcwgbkowssdjqqp> has joined #yocto | 22:59 | |
| fray | ha someone asked to have a meeting with me, I said sure.. meeting time comes and all the invite says is "Lets meet".. no dial in info, urls, etc.. ;) | 23:01 |
| fray | "whoops" | 23:01 |
| fray | not sure if the meeting person forgot the info, or if exchange ate it | 23:01 |
| fray | (I really hate exchange) | 23:01 |
| Ulfalizer | sounds nice depending on the meeting | 23:03 |
| *** istarilucky <istarilucky!~rlucca@189.112.127.225> has left #yocto | 23:07 | |
| *** manuel_ <manuel_!~manuel@c-24-61-40-209.hsd1.ma.comcast.net> has joined #yocto | 23:10 | |
| *** sujith_h <sujith_h!~toaster@kde/developers/sujithh> has quit IRC | 23:17 | |
| *** behanw <behanw!uid110099@gateway/web/irccloud.com/x-ibeiogkweepczzzp> has quit IRC | 23:19 | |
| *** sujith_h <sujith_h!~toaster@139.181.35.34> has joined #yocto | 23:20 | |
| Ulfalizer | fray: one more unimportant nit that i feel bad for sending a mail for: lines do not to be escaped with \ within (). | 23:22 |
| Ulfalizer | urr, *newlines | 23:23 |
| fray | I've had hit and miss experiencing not escaping it | 23:23 |
| Ulfalizer | the rule is that newlines don't terminate python statements within braces | 23:24 |
| Ulfalizer | outside braces, newlines need to be escaped though | 23:24 |
| fray | thats what I thought, but I've still had parse issues in the past.. to the point where I always just add the escapes.. | 23:25 |
| Ulfalizer | urr, *brackets :P | 23:25 |
| Ulfalizer | english fail | 23:25 |
| fray | I knew what you meant.. ;) | 23:25 |
| *** sameo <sameo!~samuel@192.55.55.41> has quit IRC | 23:27 | |
| *** sjolley <sjolley!sjolley@nat/intel/x-blhgvsghkjakauuv> has joined #yocto | 23:31 | |
| *** tlab_ <tlab_!~tlab@104.235.20.44> has joined #yocto | 23:32 | |
| *** tlab <tlab!~tlab@104.235.20.44> has quit IRC | 23:35 | |
| -YoctoAutoBuilder- build #924 of nightly-qa-systemd is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-qa-systemd/builds/924 | 23:38 | |
| *** khem <khem!~khem@unaffiliated/khem> has quit IRC | 23:42 | |
| *** khem <khem!~khem@unaffiliated/khem> has joined #yocto | 23:45 | |
| *** manju <manju!95c73efe@gateway/web/freenode/ip.149.199.62.254> has joined #yocto | 23:45 | |
| manju | i am using recipetool to generate bbappend, it always parses the recipe every single time. is there a way to store the parsing of bb file so that the second time it is faster? | 23:48 |
| *** anselmolsm <anselmolsm!~anselmols@192.55.55.37> has quit IRC | 23:50 | |
| *** nighty <nighty!~nighty@d246113.ppp.asahi-net.or.jp> has joined #yocto | 23:50 | |
| *** khem <khem!~khem@unaffiliated/khem> has quit IRC | 23:54 | |
| *** manuel_ <manuel_!~manuel@c-24-61-40-209.hsd1.ma.comcast.net> has quit IRC | 23:55 | |
| *** manuel_ <manuel_!~manuel@c-24-61-40-209.hsd1.ma.comcast.net> has joined #yocto | 23:56 | |
| *** khem <khem!~khem@unaffiliated/khem> has joined #yocto | 23:57 | |
Generated by irclog2html.py 2.11.0 by Marius Gedminas - find it at mg.pov.lt!