**** BEGIN LOGGING AT Mon Oct 12 02:59:59 2015 Oct 12 07:11:17 good morning Oct 12 07:11:53 hm how to copy files to the rootfs during the backing process? Oct 12 07:12:15 i wrote a recipe with the info i found via google Oct 12 07:12:47 i add the recipe to IMAGE_INSTALL_append in local.conf Oct 12 07:13:13 but when just using PROVIDES in the recipe bitbake complains, when building an image, i can't find that recipe Oct 12 07:13:22 and recommends using RPROVIDES Oct 12 07:13:46 using RPROVIDES results in another error: bluetooth_auto_power.bb: Variable RPROVIDES is set as not being package specific, please fix this. [pkgvarcheck] Oct 12 07:20:32 namra: see the last part of the entry for RPROVIDES in the manual: http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#var-RPROVIDES Oct 12 07:21:03 namra: also consider that the namespace when installing items into the image is *packages* not *recipes* Oct 12 07:21:29 namra: PROVIDES is for the build time (recipe) namespace, RPROVIDES is for the runtime (package) namespace Oct 12 07:23:51 it is the case though that most recipes produce a package with the same name as the recipe Oct 12 07:29:21 "A package's own name is implicitly already in its RPROVIDES list." Oct 12 07:29:45 hm but without and explicit RPROVIDES in the recipe bitbake complains not finding anything Oct 12 07:30:15 the structure is as follows: meta-alayer/recipes-core/bluetooth/bluetooth_auto_power.bb Oct 12 07:30:42 IMAGE_INSTALL_append = " bluetooth_auto_power" Oct 12 07:31:09 are darn Oct 12 07:31:24 underscore was to delimite the package version Oct 12 07:31:31 not hyphen Oct 12 07:33:46 thanks bluelightning Oct 12 07:36:57 namra: right, underscores shouldn't be used in the name part Oct 12 07:38:13 still pretty new to bitbake, and it's only the second recipe so far. with a few days in between Oct 12 07:40:35 ok, no worries :) Oct 12 07:40:51 you've seen http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#new-recipe-writing-a-new-recipe I take it ? Oct 12 07:41:49 yes Oct 12 07:42:01 but there's a lot of information to digest Oct 12 07:42:23 started a week ago with yocto (poky) and bitbake Oct 12 07:42:28 sure, and at least from my perspective I'm happy to answer questions already covered by the manual Oct 12 07:42:38 but I may point to the manual to save me typing :) Oct 12 07:43:40 certainly, it's there for a reason ^^ Oct 12 07:53:30 möin Oct 12 09:17:52 hmm, am hacking some stuff and I get a warning: "WARNING: Variable key FILES_${ALTKERNEL_RESCUE_CONFIG}-image ( /var/lib/dss-rescue/*) replaces original key FILES_rescue1-image (/boot/${KERNEL_IMAGETYPE}*)." Oct 12 09:18:03 Tand I can't really figure out why Oct 12 09:18:09 the recipe tries: FILES_${ALTKERNEL_RESCUE_CONFIG}-image_append = " /var/lib/dss-rescue/*" Oct 12 09:18:30 and another class does: FILES_${ALTKERNEL_NAME}-image = "/boot/${KERNEL_IMAGETYPE}*" Oct 12 09:19:04 who is the "original" key? and why is it considered replaced when I am actually _append'ing? Oct 12 09:19:22 the resulting value of the variable is correct though, but I'd still like to understand the warning Oct 12 10:32:51 hi, when i boot core-image-weston , weston is started automatically, but my shell environment isn't set properly. USER and HOME (among others) are just empty. if i kill weston and restart it's better. Oct 12 10:33:11 is that a 'known' issue, or something wrong in my setup? Oct 12 10:33:33 btw, it's a distro less build (without pam). Oct 12 10:34:07 core-image-weston is a bit of a bodge Oct 12 10:35:03 hmm. Oct 12 10:36:10 rburton: so, do you see the same behavior? Oct 12 10:37:11 haven't a core—image-weston to hand but i wouldn't be surprised! Oct 12 10:37:48 i endorse enabling pam+systemd and using a unit to start it :) Oct 12 10:38:01 i am adding coreutils in the image, that's mostly my only change. Oct 12 10:38:25 i have systemd, too.. i was missing pam.. i am rebuilding with pam now actually Oct 12 10:40:02 i want to check if weston-launch would work better. Oct 12 10:43:37 yes, it does Oct 12 11:33:53 hi, is there anyone working on the meta-browser layer in the area? Oct 12 11:43:57 jbrianceau: hi, there was this mail recently : http://lists.openembedded.org/pipermail/openembedded-devel/2015-October/103760.html Oct 12 11:44:51 hi folks, just sent a new version of the rygel patches : http://lists.openembedded.org/pipermail/openembedded-devel/2015-October/103783.html. Hopefully there are fixing everything. Oct 12 11:45:37 Tarnyko: yes, I saw it. I'm a little concerned about the licensing of chromium in meta-brwoser Oct 12 11:48:09 Crofton: https://bugzilla.yoctoproject.org/show_bug.cgi?id=8488 Oct 12 11:54:11 thanks Oct 12 11:55:27 I suspect the problem is adding packages via the variable, so a very general issue Oct 12 11:56:25 Crofton|work: yes, that's the problem. Toaster is not gathering that information at the moment. We will need to expand the current variable scope… or so bluelightning told me Oct 12 12:08:18 rburton: so, with pam weston-launch works fine. i was able to use a regular user, not root. however weston-init is still bogus.. Oct 12 13:18:55 This seems odd: | error: invalid Python installation: unable to open /home/balister/src/oe-core/build/tmp-glibc/sysroots/ettus-e300/usr/lib/python2.7/config/Makefile (No such file or directory) Oct 12 13:20:47 h c'est bizarre parce que moi, j'ai relancé vendredi et c'était bon Oct 12 13:20:52 grr Oct 12 13:21:00 :) Oct 12 13:21:31 I was saying that my meta-atmel builds were ok on friday ;) Oct 12 13:23:16 it sounds much better in french :) Oct 12 13:23:40 sounds the same to me ;-) Oct 12 13:50:42 How would I get python g to put th eMakefile in the sysroot? Oct 12 14:13:49 mckoan: hi ; if I remember correctly, you were looking for RDP clients last time ; just sent the latest patch enabling FreeRDP (http://lists.openembedded.org/pipermail/openembedded-devel/2015-October/103790.html) Oct 12 14:17:08 Tarnyko: thank you so much! Oct 12 14:21:36 abelloni: that's normal in OE Oct 12 14:23:12 and for the record, they are ok today too, only the meta-atmel maintainer fails to build ;) Oct 12 14:23:25 abelloni: we missed an additional topic for advocacy during oedem LOL Oct 12 14:24:05 yeah Oct 12 14:24:17 abelloni: meta-atmel maintainer is weird :-D Oct 12 14:24:40 BTW, there is a french company, giving free yocto/OE trainings that gets the terminology completely wrong Oct 12 14:24:53 I've tried to correct them multiple times, without success Oct 12 14:25:15 and they seem to have a really large audience Oct 12 14:25:45 abelloni: what terminology? Oct 12 14:28:26 they "build the yocto distribution" Oct 12 14:28:37 and yocto linux Oct 12 14:29:14 I build GNU/Linux with Yocto Oct 12 14:30:37 Crofton|work: +1 Oct 12 14:31:08 I build my Linux with make, personally Oct 12 14:31:17 hiis Oct 12 14:31:19 hiss Oct 12 14:31:52 ;d Oct 12 14:32:02 I use set of crazy bash scripts ;d Oct 12 14:34:02 ok figured out my stupidity Oct 12 14:34:09 Crofton|work: dont you build it with OE? Oct 12 14:34:28 (or did OE get swallowed eventually?) Oct 12 14:35:37 bluelightning: continuing in such way I build my Linux with a computer LOL Oct 12 14:41:23 mckoan: :D Oct 12 14:51:59 bencoh, OE has not been swallowed Oct 12 14:52:15 there was another of those "Yocto Linux" press releases though Oct 12 15:19:09 Yocto systemd/GNU/Linux Oct 12 15:19:13 by Intel Oct 12 15:21:09 (... and a bunch of french guys) Oct 12 16:43:15 Anyone got a good answer for this: Oct 12 16:43:17 http://stackoverflow.com/questions/32850160/bitbake-how-to-list-all-recipe-and-append-files-used-in-an-image Oct 12 16:47:15 bitbake-layers show-appends should work for that. it won't show only the bits used in that image, since it shows all appends, but if he just needs to diff before and after, it'd work for that purpose Oct 12 16:47:34 of course to list recipes built for an image there's -g with pn-buildlist, but that doesn't list appends **** ENDING LOGGING AT Tue Oct 13 02:59:59 2015