**** BEGIN LOGGING AT Wed Nov 04 02:59:58 2015 Nov 04 08:05:03 good morning Nov 04 08:25:01 whats the most appropriate way of changing the SRC_URI using a .bbappend? SRC_URI contains a 1 git repo + a bunch of patches, i just want to change the SRCREV and URL of the Git repo. My issue is with u-boot-fw-utils recipe (oe-core), it only works if UBOOT_MACHINE is in the upstream U-boot repo. Mine is not. I would like to repoint u-boot-fw-utils to a local repo that contains my UBOOT_MACHINE Nov 04 09:00:51 mornin Nov 04 09:01:31 morning Jin^eLD, all Nov 04 09:20:07 morning all Nov 04 09:20:22 bluelightning: getting ready to invert your mornings yet? :) Nov 04 09:20:33 hi nrossi Nov 04 09:20:47 heh... yeah, not looking forward to that Nov 04 09:21:05 especially as I suspect my daughter will take a while to invert hers :) Nov 04 09:21:35 the jetlag was not good for me :| took a few days to get over it. Nov 04 09:22:19 ah you made it back to .au, I guess it has been a few weeks Nov 04 09:22:36 yep got back last friday Nov 04 09:37:11 morning invertion? Nov 04 09:41:04 LetoThe2nd: sounds like a neologism Nov 04 09:41:07 is that like priority inversion? Nov 04 09:41:29 LetoThe2nd: LOL Nov 04 09:45:32 just wondering! Nov 04 11:27:48 I'm using the upload-packages script to publish ipks, but I have suddenly lost my Packages.gz files. Who makes those? :) Nov 04 11:30:06 tasslehoff: bitbake package-index is one way Nov 04 11:31:32 LetoThe2nd, mckoan: morning inversion is the near 12 hour timzone shift between UK/Europe and Australia/New Zealand ;) Nov 04 11:33:08 bluelightning: thanks, but that doesn't make it over to my angstrom feed. think I have an Angstrom-specific issue :) Nov 04 11:36:13 bluelightning: ah. forgot to run opkg-make-index from opkg-utils Nov 04 11:37:25 nrossi, you home again? Nov 04 11:37:58 Crofton|work: yes i am ;) going through emails and stuff at the moment Nov 04 11:38:18 well, I hope you had a good holiday Nov 04 11:39:52 nrossi: ack, thx Nov 04 11:40:14 I did, saw quite a bit of Ireland and London Nov 04 11:41:47 mckoan: btw 'morning inversion' is not an actual term ;) so neologism does not apply here Nov 04 12:46:16 tasslehoff: not sure what's going on because bitbake package-index runs that itself to create the index... Nov 04 12:47:37 bluelightning: pebkac yet again. I had modified sort.sh from meta-angstrom/contrib. that one created Packages.gz in subfolders. then I replaced sort.sh with a pristine copy that looked for opkg-utils in /home/koen .... Nov 04 12:47:52 so the sorting work, but other stuff failed Nov 04 12:49:07 ah, I see Nov 04 12:55:29 tasslehoff: thanks for reminding me, I have sort.sh updates I need to push this weekend Nov 04 12:56:16 koen: my pleasure :p Nov 04 14:35:44 hmm, lets assume I have two different image recipes in the same layer, can I define a different preferred provider for some package in each image? Nov 04 14:37:57 Jin^eLD: no, PREFERRED_PROVIDER can only be used at the configuration level Nov 04 14:38:20 how could I achieve something like that? the scenario is Nov 04 14:38:26 I need two different busybox configuration for each image Nov 04 14:38:48 one is for a rescue image which will be trimmed down in features, and one for the regular image Nov 04 14:39:14 I created a copy of the busybox recipe, busybox-rescue and defined that it RPROVIDES_${PN} = "busybox" Nov 04 14:39:26 without that some other stuff kept pulling in busybox into the rescue image Nov 04 14:46:37 Jin^eLD: right yes, that's pretty much the only way Nov 04 14:47:01 yeah but you are saying I can not specify a different preferred provider in each image... Nov 04 14:47:14 which kind of means that this RPROVIDES_ statement is useless to me for this scenario? Nov 04 14:47:21 or am I misunderstanding something? Nov 04 14:47:49 my idea was ot have image one use "busybox" as the preferred provider for it and the rescue image to use "busybox-rescue" as the preferred busybox provider Nov 04 14:48:16 but that won't work because you said preferred provdier is not a per-recipe setting Nov 04 14:48:18 ? Nov 04 14:48:36 if you explicitly ask for busybox in the image, you may get away with that depending on the package manager... otherwise you're going to have to remove those other explicit dependencies on busybox Nov 04 14:48:49 er I mean if you explicitly ask for busybox-rescue Nov 04 14:48:55 aha Nov 04 14:49:05 and just ignore the warning "multiple providers for xx are available" Nov 04 14:49:17 ok let me try that Nov 04 14:49:24 thanks Nov 04 14:49:26 hmm Nov 04 14:49:30 I'm not sure about the latter Nov 04 15:14:41 bluelightning: the RPROVIDES approach does not seem to do the trick, it then even pulls in the wrong package into the regular image :( Nov 04 15:15:20 hmm Nov 04 15:16:05 I suspect the dependency on busybox will be from packagegroup-core-boot Nov 04 15:16:24 you could simply remove that from the rescue image and explicility install the packages it contains Nov 04 15:16:37 minus busybox, plus busybox-rescue Nov 04 15:16:54 let me try that.. Nov 04 16:13:38 hi **** BEGIN LOGGING AT Thu Nov 05 00:25:07 2015 **** ENDING LOGGING AT Thu Nov 05 02:59:58 2015