**** BEGIN LOGGING AT Fri Apr 24 02:59:59 2015 Apr 24 07:42:26 goddmorning guys... i am still tring to compile the meta-qt5-toolchain... now i got a FETCH error on qt5system Apr 24 07:42:31 ERROR: Fetcher failure: Unable to find revision aa651c73bf7bc57c1b6b1bfcfa9afe901884a102 in branch stable even from upstream Apr 24 07:43:10 the recepi generating this error is /meta-qt5/recipes-qt/qt5/qtsystems_git.bb, do_fetch) failed with exit code '1' Apr 24 07:44:19 but this recepy looks really strange.. there is nothing inside! Apr 24 07:44:26 just this 4 lines Apr 24 07:44:30 require qt5-git.inc Apr 24 07:44:30 require ${PN}.inc Apr 24 07:44:30 # qtsystems wasn't released yet, last tag before this SRCREV is 5.0.0-beta1 Apr 24 07:44:30 # qt5-git PV is only to indicate that this recipe is compatible with qt5 5.2.1 Apr 24 07:44:30 SRCREV = "aa651c73bf7bc57c1b6b1bfcfa9afe901884a102" Apr 24 07:44:59 what means that is not been released yet? Apr 24 07:45:39 well it means that this SRCREV was not found in the stable branch ,yet ? Apr 24 07:46:02 ok Apr 24 07:46:13 how can i switch to another branch? Apr 24 07:46:37 in qt3d i had to switch from master to dev Apr 24 07:46:41 i gues inside qt5-git.inc must the be branch settings .. close to SRC_URI Apr 24 07:47:15 is this going to affect also other packages? Apr 24 07:47:17 ok ok Apr 24 07:47:19 i try Apr 24 07:48:47 thanks rob_w Apr 24 07:48:51 np Apr 24 08:48:20 morning all Apr 24 09:06:50 hi bluelightning Apr 24 09:32:27 hi rob_w: now i got this error Apr 24 09:32:45 Collected errors: Apr 24 09:32:45 * satisfy_dependencies_for: Cannot satisfy the following dependencies for packagegroup-qt5-toolchain-target: Apr 24 09:32:45 * qttools-plugins * Apr 24 09:32:45 * opkg_install_cmd: Cannot install package packagegroup-qt5-toolchain-target. Apr 24 09:33:42 together with a huge list of perl-dev: unsatisfied recommendation for Apr 24 09:42:15 qttools-plugins is the package ur missing .. either install it before or actually update your repo which should then make our opkg pull dependencies Apr 24 10:24:52 rob_w: unfortunatly is not working.. i added qttools-plugin in build/local.conf -->IMAGE_INSTALL_append = "qtbase qttools qtbase-fonts qttools-plugins ... " Apr 24 10:25:37 and i tried to rebuild the complete image with bitbake -k angstrom-lxde-image Apr 24 10:26:35 and it fails when when it do_rootfs : * opkg_install_cmd: Cannot install package qttools-plugins. Apr 24 10:26:36 ERROR: Function failed: do_rootfs Apr 24 10:31:15 then qttools-plugins is not set as build dependency ,, try to build it via bitbake qttools-plugin and see what happens Apr 24 10:31:40 I suspect that is not the problem Apr 24 10:32:54 my comments are just from 10000ft high .. guess qt5 has its own caveeggs Apr 24 10:37:24 rob_w: i think you were right Apr 24 10:37:35 it says ERROR: Nothing PROVIDES 'qttools-plugin' Apr 24 10:48:49 * rob_w scores Apr 24 10:49:43 also it could well be a obsolete dependency .. as i said, i am 10000ft above qt5 Apr 24 10:50:06 my primitive mind would force the install and see it works ;-) Apr 24 10:55:09 rob_w: but i already have the option -k Apr 24 10:57:22 is with that that i force the install? Apr 24 11:03:15 try to investigate what qttools-plugin does, where it went and why it is missing .. thats a basic investigation and will bring you closer to the whole package/dependency thing inside oe Apr 24 16:39:56 Is it possible to verify if a flag is enabled on PKGCONFIG (EXTRA_OECONF) ? If it is enabled I want to take an action Apr 24 18:38:19 back in the 'dark ages' of openEmbedded, the mercurial repo used to change on an hourly basis, pulls from the repo were not to be done by the faint-hearted. Stuff that worked, suddenly broke. Apr 24 18:38:31 my question is, how "stable" is 'master'? Apr 24 18:39:24 depends on the point in the release cycle Apr 24 18:39:27 well, yocto 1.8 *just* released, so at the moment master isn't far from the release Apr 24 18:39:30 but yeah, it varies Apr 24 18:39:40 since there was just a release, master sucks now Apr 24 18:39:53 since people are adding lots of stuff Apr 24 18:40:16 in a few months, it ill stabilize as new stuff isn't accepted and we fix bugs :) Apr 24 18:40:48 also, it was a monotone repo :) Apr 24 18:41:00 if you want something recent and stable, best to use fido / 1.8 Apr 24 18:41:05 +1 Apr 24 18:41:45 that reminds me, i should start working through my push/submission backlog now that it's released and join the post-release madness Apr 24 18:41:51 :) Apr 24 18:42:03 yep Apr 24 18:42:26 Moving my product forward, I need to start doing a lot of X programming, probably with Athena. Now, the "fido", isn't that stripped of much of the OE functionality? E.g. if I want it "all" I should bake recipes on OE instead of pokey/Yocto? Apr 24 18:42:29 T0mW: mercurial? do you mean monotone? Apr 24 18:42:43 oh, yeah, forgot the name. heh Apr 24 18:43:00 Poky is oe-core + meta-yocto :) Apr 24 18:43:01 that really doesn't maek a great deal of sense Apr 24 18:43:10 yeah, poky is oe-core+meta-yocto+bitbake Apr 24 18:43:13 and maybe a bsp Apr 24 18:43:19 * Crofton|work has never built poky Apr 24 18:43:21 meta-oe can be added on whether you're using meta-yocto and the poky distro or not Apr 24 18:43:36 T0mW: there is libXaw recipe already, I gave you link in #yocto Apr 24 18:43:44 okay, i really want TOPDIR exported into the devshell environment Apr 24 18:43:53 quite often i want to copy something back to the build directory Apr 24 18:43:57 and i'm always having to do it manually Apr 24 18:46:30 Jama, but that exists in OE (along with other dependant recipes), but not in Yocto Daisy. So, I'm about to pull the trigger on killing off Yocto and moving back into OE (simply due to the breadth of recipes). Apr 24 18:46:47 that really doesn't make any sense Apr 24 18:46:58 again, yocto includes poky, which is just an integration of oe-core, meta-yocto, and bitbake Apr 24 18:47:07 there's no more recipes in poky than in those separate components, or vice versa Apr 24 18:47:16 it sounds like you're comparing two different branches, or something Apr 24 18:47:28 kergoth: right, but its' reduced form of OE. A derivative. Apr 24 18:47:31 wrong Apr 24 18:47:36 what? Apr 24 18:47:47 poky is a repository that includes *precisely* the current content of oe-core, meta-yocto, and bitbake Apr 24 18:47:58 nothing is removed, that's all it is Apr 24 18:48:18 I thought poky was dead and replaced by Yocto? Apr 24 18:48:22 you can go do a build with bitbake and oe-core separately, but you aren't magically getting anything new Apr 24 18:48:33 no, yocto is an umbrella projct which includes poky as its reference distribution and build platform Apr 24 18:48:41 AH! Apr 24 18:49:04 oe-core in oe and oe-core in poky are exactly the same, which is *why* we moved to oe-core in the first place Apr 24 18:49:07 everyone shares the same baseline Apr 24 18:49:08 kergoth: ok, I'm going to pull from poky then and take another look. My mistake. Apr 24 18:49:34 whether you use poky or the individual components is largely a matter of personal preference, and whether you're going to make use of the poky distro or not Apr 24 18:49:41 kergoth: yeah, you wanted a stable releasing which was poky, I thought that the poky was renamed to Yocto. Apr 24 18:50:03 kergoth: cool, thanks ken. Apr 24 18:50:06 you can check out the yocto 1.8 branch of oe-core separately, or the 1.8 branch of poky, the content will be the same Apr 24 18:50:55 which is also true for daisy, so it sounds like you were comparing daisy content to master contnet, or daisy content to oe-classic, which is an apples and oranges comparison Apr 24 18:51:15 ken? Apr 24 18:51:31 Crofton|work: out of curiosity, what setup scripts do you use in your setup, the stock oe-core ones? Apr 24 18:51:46 Maybe, but Yocto does not have the 'recipes-graphics/xorg-lib/libxaw_1.0.10.bb' recipe Apr 24 18:51:59 meta-oe does Apr 24 18:52:04 again Apr 24 18:52:10 you can add meta-oe to a poky setup or a standalone oe setup Apr 24 18:52:13 as i said earlier Apr 24 18:52:16 as long as the branches line up Apr 24 18:52:25 hmm, ok Apr 24 18:52:42 For stable work I use repo Apr 24 18:52:46 which is the whole point of the layering mechanism, you can add arbitrary layers to any oe-core based configuration Apr 24 18:52:47 see http://layers.openembedded.org/layerindex/ Apr 24 18:52:53 and stole a readme from gumstix Apr 24 18:52:56 meta-oe is just another layer Apr 24 18:52:59 Crofton|work: ah, cool Apr 24 18:53:06 sucks for dev Apr 24 18:53:17 for that I jsut assemble stuff by hand Apr 24 18:53:36 but I tell customers to use repo, so I ahve a good idea what they are building Apr 24 18:53:45 and can dupe my setup fairly accurately Apr 24 18:54:15 I use repo for repository management for day to day development, not too bad as long as the manifest in question tracks branches, not specific commits, and once i set up a 'new project' script that automatically runs 'repo start —all projectname' so nothing is ever sitting on a floating checkout Apr 24 19:00:25 can I stay with sysv-init (no systemd) with the fido release? Apr 24 19:01:09 yes Apr 24 19:02:15 i *think* sysvinit is still default for distroless and poky, at least it was last time i checked Apr 24 19:02:18 hm Apr 24 19:02:40 yeah Apr 24 19:03:32 excellent! **** ENDING LOGGING AT Sat Apr 25 02:59:59 2015