01:15.24 | *** join/#oe zenlinux_ (~sgarman@2001:470:e962:b01:cbc:3f20:2bbc:3691) |
01:18.38 | *** join/#oe dos11 (~dos@unaffiliated/dos1) |
01:19.08 | *** join/#oe dos11 (~dos@unaffiliated/dos1) |
01:50.07 | *** join/#oe rogue2 (~pompomJui@41.0.38.138) |
01:52.37 | *** join/#oe nitink1 (nitink@nat/intel/x-fslenapmpbkvhlbu) |
01:57.12 | *** join/#oe sr105|aw` (~sr105@65349hfc19.tampabay.res.rr.com) |
02:00.13 | *** join/#oe stefan__ (~chatzilla@bas2-montreal29-1279583504.dsl.bell.ca) |
02:30.53 | *** join/#oe s3v3n62mm2 (~s3v3n62mm@p5DDC1125.dip0.t-ipconnect.de) |
02:37.38 | *** join/#oe Vutral (~ss@mirbsd/special/Vutral) |
02:56.52 | *** join/#oe hillct (~hillct@cpe-071-070-219-043.nc.res.rr.com) |
03:03.29 | *** join/#oe Vutral (~ss@mirbsd/special/Vutral) |
03:09.32 | *** join/#oe jkridner (~jkridner@c-98-250-189-79.hsd1.mi.comcast.net) |
03:09.33 | *** join/#oe jkridner (~jkridner@pdpc/supporter/active/jkridner) |
03:10.40 | *** join/#oe jkridner (~jkridner@c-98-250-189-79.hsd1.mi.comcast.net) |
03:10.40 | *** join/#oe jkridner (~jkridner@pdpc/supporter/active/jkridner) |
03:22.26 | *** join/#oe pompomJuice (~pompomJui@41.0.38.138) |
03:29.01 | *** join/#oe Vutral (~ss@mirbsd/special/Vutral) |
03:34.32 | *** join/#oe NvrBst (~NvrBst@gateway/tor-sasl/nvrbst) |
04:01.47 | *** join/#oe KNERD (~KNERD@24.175.253.226) |
04:07.06 | *** join/#oe Vutral (~ss@mirbsd/special/Vutral) |
04:17.41 | *** join/#oe crxz0193 (~crxz0193@203.247.149.152) |
04:21.34 | *** join/#oe Leatherface- (~leatherfa@2001:470:dd7d:0:949d:e099:8f4:e3b5) |
04:32.43 | *** join/#oe rereadit (~rereadit@c-24-3-21-28.hsd1.pa.comcast.net) |
05:20.48 | *** join/#oe jkridner (~jkridner@pdpc/supporter/active/jkridner) |
05:22.44 | *** join/#oe nitink (~nitink@134.134.139.74) |
06:23.26 | *** join/#oe Vutral (~ss@mirbsd/special/Vutral) |
06:49.54 | *** join/#oe ant_work (~ant__@host54-128-static.10-188-b.business.telecomitalia.it) |
06:53.20 | *** join/#oe woglinde (~henning@fb-n15-11.unbelievable-machine.net) |
06:53.56 | *** join/#oe rob_w (~bob@unaffiliated/rob-w/x-1112029) |
06:58.43 | *** join/#oe bluelightning (~paul@pdpc/supporter/professional/bluelightning) |
06:59.50 | *** join/#oe diego_r (~diego@host77-246-static.10-188-b.business.telecomitalia.it) |
07:07.20 | *** join/#oe florian_kc (~fuchs@Maemo/community/contributor/florian) |
07:09.59 | *** join/#oe eballetbo (~eballetbo@43.Red-2-139-180.staticIP.rima-tde.net) |
07:32.08 | bluelightning | morning all |
07:34.05 | *** join/#oe tbr_ (dm8tbr@cl-790.ham-01.de.sixxs.net) |
07:37.49 | mckoan | gm bluelightning |
07:40.06 | *** join/#oe sr105|away (~sr105@65349hfc19.tampabay.res.rr.com) |
07:41.20 | *** join/#oe diego_ (~diego@host65-246-static.10-188-b.business.telecomitalia.it) |
07:44.29 | *** join/#oe kroon (~kroon@193.15.174.198) |
07:49.03 | *** join/#oe tasslehoff (~Tasslehof@77.40.182.98) |
07:49.19 | bluelightning | morning mckoan |
07:49.32 | koen | hey mckoan & bluelightning |
07:49.39 | bluelightning | hi koen |
07:57.57 | *** join/#oe stefan_schmidt (~stefan@123.143.183.198) |
08:05.17 | pompomJuice | aargh bluelightning help me... |
08:05.27 | bluelightning | pompomJuice: what's up? |
08:05.29 | pompomJuice | apk_base_postinst_chrome() { |
08:05.41 | pompomJuice | I dont see the script in the ipk |
08:05.43 | pompomJuice | it wont go |
08:05.56 | pompomJuice | recipy is chrome_38.7.bb |
08:06.35 | pompomJuice | is something like this legal? |
08:06.36 | pompomJuice | pk_base_postinst_${PN}() { |
08:07.10 | bluelightning | shouldn't it be pkg_postinst_${PN} () { ? |
08:07.15 | pompomJuice | amagad |
08:07.18 | pompomJuice | ok lets see |
08:08.34 | pompomJuice | still not there |
08:08.56 | pompomJuice | inside the IPK there is this debian folder that is supposed to get the script |
08:09.01 | bluelightning | well, that is the correct syntax |
08:09.02 | pompomJuice | it works for other packages |
08:09.22 | pompomJuice | in my system so it's just this one.. no other level I must pull that you can think of? |
08:12.13 | *** join/#oe Vutral (~ss@mirbsd/special/Vutral) |
08:13.30 | bluelightning | pompomJuice: I just tried it here - I added pkg_postinst_${PN} to a recipe that I'd already built, built it again, and unpacked the ipk - the postinst file is there inside control.tar.gz within the ipk |
08:13.52 | pompomJuice | I did not notice the pkg_ |
08:13.54 | pompomJuice | let me try again |
08:14.01 | pompomJuice | the start differs |
08:14.11 | bluelightning | right, that would stop it from working... |
08:14.53 | *** join/#oe tbr_ (dm8tbr@cl-790.ham-01.de.sixxs.net) |
08:15.26 | pompomJuice | it works! |
08:15.27 | pompomJuice | amagad |
08:15.30 | pompomJuice | thanks |
08:16.09 | bluelightning | np |
08:16.20 | pompomJuice | i was cloning some other recipies, there was an anonymous python hack that does this -> d.setVar("pkg_postinst_%s" % pkg, d.getVar("apk_base_postinst", True) % apk) |
08:16.23 | pompomJuice | and it works! |
08:16.36 | pompomJuice | so no idea by apk_base_postinst works there... |
08:16.37 | pompomJuice | bizarre |
08:17.09 | bluelightning | I don't think it does, that code is reading apk_base_postinst and setting pkg_postinst_<packagename> from it |
08:17.10 | pompomJuice | I wrote a system that installs APKs through opkg :) |
08:17.25 | pompomJuice | amagad |
08:17.35 | pompomJuice | oops |
08:17.40 | pompomJuice | take it slow |
08:18.37 | pompomJuice | did not see that the first part was not the same |
08:18.43 | pompomJuice | not easy |
08:19.44 | bluelightning | I'm happy to take suggestions on how we can document this better |
08:20.36 | pompomJuice | maybe start by explaining in some document how bitbake->oe->angstrom->layers relate |
08:20.47 | pompomJuice | im so lost sometimes |
08:21.10 | pompomJuice | but the documentation is good, just you dont get time to read it |
08:21.15 | bluelightning | there is a "Post-Installation Scripts" section in the development manual (under the new "Writing a New Recipe" section) |
08:21.16 | pompomJuice | shit must be finished today |
08:21.30 | pompomJuice | let me check |
08:21.35 | pompomJuice | my main issue is the following |
08:21.39 | pompomJuice | all the documentation is split |
08:21.44 | pompomJuice | I want one document |
08:21.48 | pompomJuice | the macdaddy of documents |
08:21.51 | bluelightning | aha, then you are in luck :) |
08:21.55 | pompomJuice | where I can do a keyword search |
08:21.56 | bluelightning | check out the "mega manual" |
08:22.02 | pompomJuice | awesome |
08:22.19 | bluelightning | equally though I don't mind answering questions here, even if they are in the manual |
08:22.42 | pompomJuice | thats just pure lazyness then |
08:22.49 | pompomJuice | please give me a link to this manual |
08:22.54 | bluelightning | I'm not just going to say "RTFM" although I may point to sections of the manual if they explain some aspect in greater detail than I feel like typing ;) |
08:23.00 | bluelightning | one sec |
08:23.25 | bluelightning | http://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html |
08:23.34 | pompomJuice | awesome thanks |
08:23.45 | bluelightning | that's the 1.6 manual (the current release) |
08:23.50 | bluelightning | the 1.5 manual is here: http://www.yoctoproject.org/docs/1.5/mega-manual/mega-manual.html |
08:24.03 | pompomJuice | omg its huge |
08:24.06 | pompomJuice | lol |
08:24.12 | pompomJuice | I don't feel bad anymore |
08:24.12 | bluelightning | it does say "mega" ;) |
08:24.29 | pompomJuice | no wonder im so lost |
08:25.36 | bluelightning | I don't think we expect people to read the entire thing |
08:25.49 | pompomJuice | yea it's not always neccesary |
08:26.09 | pompomJuice | if the sources are able to be built by autotools it's a no brainer |
08:26.15 | pompomJuice | the recipies are delf explanitory |
08:26.18 | pompomJuice | self* |
08:27.57 | pompomJuice | this is going to be awesome |
08:28.29 | bluelightning | I hope that the new "Writing a New Recipe" section will be helpful... it's not in the 1.5 manual, it's new in the 1.6 version (but equally applicable to older versions) |
08:28.46 | pompomJuice | awesome |
08:29.14 | pompomJuice | im gonna check it out def, since the only oother writing a new recipy in the interwebs is so old |
08:29.32 | pompomJuice | maybe include some templates |
08:29.33 | pompomJuice | like |
08:29.37 | pompomJuice | autotool template |
08:29.41 | pompomJuice | cmake |
08:29.45 | pompomJuice | etc |
08:30.11 | pompomJuice | and one that shows different maneuvers like the ipk post install... |
08:30.17 | *** join/#oe ccube (ccube@nx.ccube.de) |
08:30.46 | *** join/#oe anarsoul|2 (~anarsoul@178.124.194.242) |
08:35.32 | pompomJuice | maybe I have a legit question now |
08:35.42 | bluelightning | sure, fire away |
08:35.52 | pompomJuice | I am busy adapting a recipy... |
08:36.02 | pompomJuice | in this recipy we have these post insttall scripts |
08:36.27 | pompomJuice | and one of the scripts contained: |
08:36.28 | pompomJuice | apk_base_postinst() { |
08:36.28 | pompomJuice | #!/bin/sh |
08:36.28 | pompomJuice | APK="%s" |
08:36.34 | pompomJuice | that %s |
08:36.36 | pompomJuice | what is that? |
08:36.39 | pompomJuice | how does that work? |
08:36.44 | pompomJuice | it makes no sense to me |
08:36.57 | pompomJuice | aah wait |
08:37.22 | pompomJuice | its a placeholder for the python line that inserts it |
08:37.26 | pompomJuice | sorry man |
08:37.28 | pompomJuice | plastic programming |
08:37.30 | bluelightning | right |
08:37.32 | bluelightning | no worries :) |
08:37.34 | pompomJuice | I solved it now |
08:37.58 | pompomJuice | so my question becomes |
08:38.48 | *** join/#oe JaMa (~martin@ip-89-176-104-3.net.upcbroadband.cz) |
08:39.34 | pompomJuice | can I insert bitbake variables into those scripts... |
08:39.41 | pompomJuice | testing it now... |
08:39.47 | pompomJuice | the manual does not say |
08:40.03 | bluelightning | you can yes, just ${VARIABLENAME} |
08:40.25 | pompomJuice | since it seems that the reason why the previous guy went with the anonymous python is that he could not inject bitbake variables into his post install script |
08:40.30 | pompomJuice | aweome |
08:42.06 | pompomJuice | whoever invented bitbake is genius... this thing has no end |
08:44.03 | bluelightning | it's very flexible for sure |
08:44.28 | pompomJuice | very, the things we have automated in our image is insane |
08:44.30 | bluelightning | of course that does lead to a bit of a learning curve, but it's powerful once you get to grips with it |
08:44.35 | pompomJuice | we have a very unconventional image |
08:44.42 | pompomJuice | and we are using bitbake on all levels |
08:45.23 | pompomJuice | bitbake just sorts out all our problems |
08:46.43 | *** join/#oe ao2 (~ao2@2001:1418:117::1) |
08:47.52 | bencoh | are you actually packaging android stuff using bitbake ? |
08:47.58 | bencoh | (just being curious) |
08:50.58 | pompomJuice | yes |
08:51.07 | pompomJuice | the dudes before me did something strange |
08:51.18 | pompomJuice | they installed android ontop of linux |
08:51.36 | pompomJuice | instead of just adroid with gimped linux |
08:51.43 | pompomJuice | so we have a device |
08:51.55 | pompomJuice | with full angstom capability... but runs android |
08:52.10 | pompomJuice | things like systemd |
08:52.11 | pompomJuice | etc |
08:52.29 | pompomJuice | makes it then a very powerfull device that can easily be augmented will all kinds of trickery |
08:53.12 | pompomJuice | our android is in a jail |
08:53.29 | pompomJuice | pretty cool |
08:53.45 | pompomJuice | the android we use is rowboat, since it's a ti chip |
08:54.56 | bencoh | so you have an androidish kernel ? |
08:54.58 | pompomJuice | therefor the recipies I am writing now enables you to opkg install android apps |
08:55.05 | pompomJuice | yes the kernel is the bugger |
08:55.10 | pompomJuice | when they started this |
08:55.16 | pompomJuice | t4 years ago |
08:55.31 | pompomJuice | ti did not have a android kernel, so they took one and patched it |
08:55.37 | pompomJuice | locking the kernel in place |
08:55.43 | pompomJuice | that number is 2.6.37 |
08:55.45 | pompomJuice | pretty annoying |
08:55.58 | pompomJuice | so that means I can only take systemd to 204.. shit like that |
08:56.43 | pompomJuice | I could try find a new kernel that does support linux, and re-apply the patches... but how do you motivate that to the upper management. They don't see the value in keeping versions up to date |
08:57.36 | pompomJuice | the other tricky part was getting the to SGX 530 gl driver module into the kernel |
08:57.43 | pompomJuice | and getting android to use it |
08:59.44 | pompomJuice | you get werid issues |
08:59.45 | pompomJuice | like |
08:59.52 | pompomJuice | the other day I went from linaro 4.7 4.8 |
08:59.58 | pompomJuice | bam kernel brick |
09:00.04 | pompomJuice | then solved by patching memset |
09:00.09 | pompomJuice | bam sgx driver brick |
09:00.40 | pompomJuice | memcpy from syslink no good anymore |
09:00.56 | *** join/#oe dany (~Thunderbi@sestofw01.enea.se) |
09:01.09 | pompomJuice | things like that |
09:01.45 | *** join/#oe Vutral (~ss@mirbsd/special/Vutral) |
09:04.27 | pompomJuice | uugh I have another issue |
09:04.50 | pompomJuice | I wronte this mini recipy android-utils that contain 2 !#/bin/sh scripts |
09:04.53 | pompomJuice | wrote* |
09:05.05 | pompomJuice | the ipk contains the scripts at /usr/bin |
09:05.19 | pompomJuice | and the device says it is installed |
09:05.24 | pompomJuice | but the files are not there |
09:05.36 | pompomJuice | should I take special precaution in recipy for script targets? |
09:06.07 | bluelightning | pompomJuice: no, no special handling should be needed |
09:06.16 | pompomJuice | mmm ok thanks. |
09:06.29 | bluelightning | what does the package manager list when you ask it to list files within that package? |
09:06.40 | pompomJuice | checking |
09:08.16 | pompomJuice | strrange |
09:08.36 | pompomJuice | ./usr/bin/adb |
09:08.36 | pompomJuice | ./usr/bin/aapt |
09:08.43 | pompomJuice | now I am confused |
09:09.18 | pompomJuice | omg |
09:09.42 | pompomJuice | another package adds PACKAGES += "android-utils" in another package |
09:09.47 | pompomJuice | its a duplicatge |
09:09.55 | pompomJuice | bizarre |
09:10.18 | pompomJuice | my package name exists... thats why... |
09:10.21 | pompomJuice | ok let me fix it |
09:10.37 | bluelightning | ah right |
09:11.00 | bluelightning | though that should have triggered a warning, unless it happened that only one of the recipes actually got built |
09:12.01 | pompomJuice | yea |
09:12.07 | pompomJuice | was only building the one |
09:12.20 | pompomJuice | interesting though |
09:12.49 | pompomJuice | I have that recipy as DEPENDS="android-utils" in my chrome recipy... and it built my new one before it built the chrome recipy |
09:12.55 | pompomJuice | so I thoguht it worked |
09:31.33 | *** join/#oe Vutral (~ss@mirbsd/special/Vutral) |
09:40.18 | *** join/#oe NvrBst (~NvrBst@gateway/tor-sasl/nvrbst) |
09:41.45 | *** join/#oe dany (~Thunderbi@sestofw01.enea.se) |
09:48.38 | pompomJuice | RDEPENDS_${PN} = "android-install-utils" |
09:48.44 | pompomJuice | does not seem to work |
09:48.48 | pompomJuice | :/ |
09:49.18 | bluelightning | is android-install-utils a valid package name? |
09:49.38 | pompomJuice | its recipy is android-install-utils_0.1.bb |
09:49.56 | pompomJuice | that version number is purely fictitious |
09:50.06 | bluelightning | ok, and that recipe produces a normal main package that is non-empty? |
09:50.11 | pompomJuice | yes |
09:50.17 | bluelightning | what fails then? |
09:50.20 | koen | does android-install-utils_0.1.bb generate a 'android-install-utils'? |
09:50.20 | pompomJuice | my other rdepends works |
09:50.21 | pompomJuice | well |
09:50.30 | pompomJuice | it's like the dependency is not there |
09:50.39 | bencoh | ? |
09:50.50 | pompomJuice | even though the chrome ipk contains in it's info a line: |
09:51.03 | bluelightning | can you be more specific? |
09:51.17 | pompomJuice | Depends: android-install-utils |
09:51.29 | pompomJuice | that is inside the chrome.ipk's info file |
09:51.43 | bencoh | what's wrong then ? |
09:51.59 | pompomJuice | but when I do opkg install chrome it does not pull the android-install-utils first... |
09:51.59 | koen | and you don't have anything RPROVIDE'ing or RREPLACES'ing android-install-utils ? |
09:52.11 | pompomJuice | let me check that one too |
09:52.26 | koen | grep android-install-utils /var/lib/opkg -rn |
09:53.24 | pompomJuice | does not seem like it |
09:53.35 | pompomJuice | let me double check this |
09:53.40 | pompomJuice | since other rdepends in our system works |
09:53.51 | *** join/#oe ensc|w (~ensc@fedora/ensc) |
09:54.18 | pompomJuice | yea |
09:54.28 | pompomJuice | opkg uinstall chrome |
09:54.35 | pompomJuice | opkg uninstall android-install-utils |
09:54.42 | pompomJuice | opkg install chrome |
09:54.50 | pompomJuice | worked |
09:54.59 | pompomJuice | sorry |
09:55.36 | bluelightning | sounds like the chrome package didn't get upgraded on the target to include the new dependency |
09:55.45 | pompomJuice | yea |
09:55.52 | pompomJuice | I made a weird discovery |
09:56.03 | pompomJuice | you can install something for the first time by saying opkg upgrade chrome |
09:56.08 | pompomJuice | it was habit |
09:56.33 | pompomJuice | when it started downloading the chrome ipk I ctrl-C it thinking the deps dont work |
09:56.38 | pompomJuice | but it downloads the dep second |
09:56.40 | pompomJuice | amagd |
09:56.43 | bluelightning | upgrade will work after that, but the version number has to change or it'll think nothing has tobe done |
09:56.49 | pompomJuice | I see |
09:56.59 | bencoh | install --reinstall |
09:57.06 | bencoh | hm, --force-reinstall |
09:57.18 | pompomJuice | yea that one |
09:57.53 | pompomJuice | and it works |
09:57.55 | pompomJuice | everything works |
09:57.58 | bencoh | :) |
09:58.29 | pompomJuice | sorry for going for the cheap route by asking questions here I was under time pressure it's easier to come plastic program here |
09:58.30 | pompomJuice | thanks all |
09:58.38 | pompomJuice | it works |
09:58.41 | pompomJuice | boss man is happy |
09:58.46 | pompomJuice | I can relax again |
09:58.50 | bencoh | now you can play around with OE ;) |
09:58.57 | pompomJuice | yea |
09:59.28 | pompomJuice | one interesting I notice though |
09:59.45 | pompomJuice | my pkg_postinst script contains echo "some status" to give some feedback |
09:59.56 | pompomJuice | the feedback is printed twice, but I am sure the script only runs once |
10:00.05 | pompomJuice | unless my dupcheck wored |
10:00.10 | pompomJuice | worked* |
10:00.12 | pompomJuice | anyway |
10:02.23 | pompomJuice | yea the script executed only once otherwise my dupcheck echoes would have printed.. |
10:13.29 | pompomJuice | koen legend btwe |
10:13.41 | pompomJuice | everyone in this office knows the name |
10:13.47 | pompomJuice | fyi |
10:13.49 | pompomJuice | ;) |
10:21.03 | *** join/#oe KNERD|2 (~KNERD@24.175.253.226) |
10:53.42 | woglinde | ah nice the google-pdf plugin |
10:53.50 | woglinde | now we can make it run under arm too |
10:54.00 | woglinde | for chrome/ium of course |
10:54.55 | *** join/#oe dany (~Thunderbi@sestofw01.enea.se) |
11:41.54 | *** join/#oe dany (~Thunderbi@sestofw01.enea.se) |
11:45.36 | pompomJuice | I was wondering, these pkg_postinst that you can add... how are those handled when you create the image? Those scripts of mine need to be deferred, they cant be switched since some of the post install commands are adb shell commands to the android system. Those won't work on image generation... is there something built in for this? |
11:46.41 | koen | pompomJuice: if it can't run safely, there usually is a -z $D check present to abort if opkg -o /path/to/root is used |
11:46.58 | koen | for some postinsts OE will try to run them under qemu or another wrapper |
11:47.11 | koen | e.g. gtk-pixbuf and icon cache postinsts |
11:47.25 | pompomJuice | yea I see my script is switching on $D like you said |
11:47.53 | pompomJuice | ok so am I to assume that those scripts are run and they fail? Or what? |
11:47.58 | koen | postinsts are just shellscripts opkg will run with some extra vars set (like $D) |
11:48.14 | pompomJuice | are they run when the image is generated |
11:48.15 | pompomJuice | ? |
11:48.17 | pompomJuice | surely |
11:48.30 | pompomJuice | what happens if they fail or "hang"? |
11:48.36 | pompomJuice | ok wait |
11:48.39 | pompomJuice | they are switching on 4D |
11:48.43 | pompomJuice | $D |
11:48.46 | pompomJuice | so they wont hang |
11:48.48 | pompomJuice | nm |
11:48.51 | bluelightning | if they fail they are postponed until first boot |
11:48.58 | pompomJuice | aah |
11:49.11 | pompomJuice | that could come in handy |
11:49.17 | pompomJuice | exactly what I need |
11:49.21 | pompomJuice | top top |
11:49.23 | pompomJuice | will test it now |
11:49.43 | koen | iirc 1.5 introduced the qemu and wrapper stuff |
11:49.56 | pompomJuice | So this one IPK installs a android keyboard APK, that needs a post install command adb ime enable command that can only run on the meter |
11:50.14 | pompomJuice | interesting... that qemu move |
11:50.36 | pompomJuice | must you have a qemu configuration ready? |
11:50.37 | bluelightning | if you want the script to be postponed when $D is set you must "exit 1" in that case so that it appears to fail |
11:50.51 | pompomJuice | thanks bluelightning |
11:50.57 | pompomJuice | testing that now |
12:07.20 | *** join/#oe ldnunes (~ldnunes_@177.194.208.225) |
12:16.58 | *** join/#oe athoik (5c768d30@gateway/web/freenode/ip.92.118.141.48) |
12:19.23 | athoik | hello, anyone knows if binary patch (GIT binary patch) is applied on bitbakes? I have a patch witch contains images and text, but only text is applied (using SRC_URI += ...) |
12:22.12 | *** join/#oe kristoffer (~kristoffe@c-e882e253.171-2-64736c10.cust.bredbandsbolaget.se) |
12:22.31 | bluelightning | athoik: it won't be normally, no |
12:22.47 | bluelightning | athoik: you may be able to get it to apply if you set PATCHTOOL = "git" within the recipe |
12:23.27 | koen | and if that fails, add the binaries to SRC_URI and overwrite the originals in do_configure_prepend |
12:23.37 | koen | do_unpack is python, right? |
12:24.11 | bluelightning | yep |
12:24.52 | athoik | bluelightning: thanks i will test first PATCHTOOL = "git" if that doesn't succed i was thinking to include photos in files and copy then manualy :) |
12:30.14 | athoik | bluelightning: PATCHTOOL = "git" did the trick! really\ thanks a lot! |
12:30.43 | *** join/#oe adelcast (~adelcast@130.164.62.249) |
12:32.45 | bluelightning | athoik: np |
12:33.04 | *** join/#oe g1zer0 (~g1zer0@adsl-ull-86-11.48-151.net24.it) |
12:34.49 | *** join/#oe belen (~Adium@192.198.151.44) |
12:36.41 | *** join/#oe stefan__ (~chatzilla@modemcable149.221-203-24.mc.videotron.ca) |
12:46.24 | *** join/#oe dany (~Thunderbi@sestofw01.enea.se) |
13:06.29 | *** join/#oe kristoffer (~kristoffe@c-e882e253.171-2-64736c10.cust.bredbandsbolaget.se) |
13:16.51 | *** join/#oe hillct (~hillct@cpe-071-070-219-043.nc.res.rr.com) |
13:24.56 | *** join/#oe Noor (~quassel@110.93.212.98) |
13:28.09 | *** join/#oe gizero (~g1zer0@adsl-ull-86-11.48-151.net24.it) |
13:35.38 | *** join/#oe cr3pe (~Cr3pe@146.187.3.109.rev.sfr.net) |
13:36.39 | *** part/#oe cr3pe (~Cr3pe@146.187.3.109.rev.sfr.net) |
13:46.49 | *** join/#oe challinan (~chris@173-10-226-189-BusName-WestFlorida.hfc.comcastbusiness.net) |
14:17.46 | *** join/#oe woglinde (~henning@fb-n15-11.unbelievable-machine.net) |
14:24.08 | *** join/#oe belen (Adium@nat/intel/x-reuaeqcpcyenuepx) |
14:30.37 | *** join/#oe sr105|away (~sr105@65349hfc19.tampabay.res.rr.com) |
14:41.11 | *** join/#oe kscherer (~kscherer@128.224.252.2) |
14:58.03 | *** join/#oe adelcast (~adelcast@130.164.62.249) |
15:02.03 | *** join/#oe Jafura (~Jean-Fran@ptr-178-50-71-191.dyn.mobistar.be) |
15:07.54 | *** join/#oe ant_work (~ant__@host54-128-static.10-188-b.business.telecomitalia.it) |
15:58.54 | *** join/#oe jkridner (~jkridner@c-98-250-189-79.hsd1.mi.comcast.net) |
15:58.54 | *** join/#oe jkridner (~jkridner@pdpc/supporter/active/jkridner) |
16:01.29 | Crofton|work | How can I track a patch as it goes through the oe-core sausage making machine? |
16:01.46 | *** join/#oe woglinde (~henning@fb-n15-11.unbelievable-machine.net) |
16:06.05 | *** join/#oe g1zer0 (~g1zer0@adsl-ull-86-11.48-151.net24.it) |
16:11.11 | *** join/#oe lumag (~lumag@nat-min.mentorg.com) |
16:21.30 | bluelightning | Crofton|work: sorry, what's the context? |
16:21.51 | Crofton|work | I sent a patch in, trying to figure out how I can follow its path into oe-core master |
16:22.05 | Crofton|work | so I know when to ask it go into diane |
16:22.16 | bluelightning | daisy? dora? dylan? |
16:22.24 | Crofton|work | daisy |
16:22.33 | Crofton|work | to many d words |
16:22.51 | bluelightning | I guess that's what patchwork is supposed to help with, unfortunately it's not very good at marking merged patches for OE-Core |
16:23.56 | *** join/#oe g1zer0 (~g1zer0@adsl-ull-86-11.48-151.net24.it) |
16:27.11 | Crofton|work | I need to make sure it doesn't fall on the floor, since I have a meta-oe patch that depends on it |
16:30.13 | *** join/#oe lumag (~lumag@nat-min.mentorg.com) |
16:34.20 | *** join/#oe tgall_foo (~tgall@24-159-198-82.static.roch.mn.charter.com) |
16:34.27 | *** join/#oe tgall_foo (~tgall@linaro/tgall-foo) |
16:34.31 | bluelightning | beyond patchwork and the mailing list we don't really have anything |
16:36.38 | kergoth | set up a cron job to update a clone and git log —grep= it for your commit periodically? ;) |
16:37.07 | bluelightning | well, we do have the oe-commits list as well, that's probably easier than that ;) |
16:40.45 | kergoth | sets up git url aliases to redirect oe-core -> openembedded-core and meta-oe -> meta-openembedded for the github repos |
16:58.41 | *** join/#oe s3v3n62mm (~s3v3n62mm@p5DDC1125.dip0.t-ipconnect.de) |
16:59.50 | *** join/#oe sr105|away (~sr105@65349hfc19.tampabay.res.rr.com) |
17:10.23 | *** join/#oe tgall_foo (~tgall@70.35.96.184) |
17:10.24 | *** join/#oe tgall_foo (~tgall@linaro/tgall-foo) |
17:13.41 | *** join/#oe g1zer0 (~g1zer0@adsl-ull-86-11.48-151.net24.it) |
17:22.18 | *** join/#oe Shawn286 (~Shawn@unaffiliated/shawn156) |
17:43.43 | *** join/#oe blilly1 (~blilly1@c-50-170-54-92.hsd1.wa.comcast.net) |
18:03.22 | *** join/#oe john3213 (john3213@static-72-66-66-50.washdc.fios.verizon.net) |
18:05.15 | *** join/#oe rob_w (~rob@unaffiliated/rob-w/x-1112029) |
18:07.33 | *** join/#oe fusman (~fahad@39.55.22.85) |
18:08.25 | *** part/#oe john3213 (john3213@static-72-66-66-50.washdc.fios.verizon.net) |
18:16.38 | *** join/#oe hillct (~hillct@cpe-071-070-219-043.nc.res.rr.com) |
19:01.44 | *** join/#oe kgilmer (~kgilmer@ip-64-134-223-6.public.wayport.net) |
19:15.14 | *** join/#oe kroon (~kroon@89-253-118-72.customers.ownit.se) |
19:31.53 | *** join/#oe hillct (~hillct@cpe-071-070-219-043.nc.res.rr.com) |
19:37.05 | *** join/#oe Shawn286 (~Shawn@unaffiliated/shawn156) |
19:43.32 | *** join/#oe eFfeM (~frans@c73189.upc-c.chello.nl) |
19:45.14 | *** join/#oe woglinde (~henning@g225019247.adsl.alicedsl.de) |
19:49.20 | *** join/#oe anarsoul (~anarsoul@80.249.95.37) |
19:57.33 | *** join/#oe phdeswer (~phdeswer@a88-112-199-213.elisa-laajakaista.fi) |
20:01.56 | bluelightning | hmm so it seems the layer index wasn't updating properly for the master branch since the server was moved |
20:02.12 | bluelightning | mainly because I forgot to switch it to use the proper branch of bitbake |
20:02.25 | bluelightning | I've now fixed it and reloaded all of the data |
20:04.21 | *** join/#oe uwe_ (~uwe_@dslb-088-064-062-090.pools.arcor-ip.net) |
20:06.47 | *** join/#oe hillct (~hillct@cpe-071-070-219-043.nc.res.rr.com) |
20:11.37 | *** join/#oe uwe_mobile (~uwe@static.88-198-8-117.clients.your-server.de) |
20:32.18 | *** join/#oe florian (~fuchs@sign-4d094779.pool.mediaWays.net) |
20:32.18 | *** join/#oe florian (~fuchs@Maemo/community/contributor/florian) |
20:45.47 | *** join/#oe nschle85 (~kvirc@188-192-114-39-dynip.superkabel.de) |
20:55.35 | *** join/#oe blindvt (~brf@91-119-222-98.dynamic.xdsl-line.inode.at) |
21:28.11 | *** join/#oe hillct (~hillct@cpe-071-070-219-043.nc.res.rr.com) |
21:38.47 | *** join/#oe stefan___ (~chatzilla@bas2-montreal29-1279583504.dsl.bell.ca) |
21:59.17 | *** join/#oe ant_home (~andrea@host53-12-dynamic.21-79-r.retail.telecomitalia.it) |
21:59.27 | *** join/#oe zenlinux (zenlinux@2600:3c00::f03c:91ff:fedb:c91) |
22:45.24 | *** join/#oe hillct (~hillct@cpe-071-070-219-043.nc.res.rr.com) |
23:25.45 | *** join/#oe darknighte (~darknight@pdpc/supporter/professional/darknighte) |