IRC log for #oe on 20140523

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.08bluelightningmorning all
07:34.05*** join/#oe tbr_ (dm8tbr@cl-790.ham-01.de.sixxs.net)
07:37.49mckoangm 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.19bluelightningmorning mckoan
07:49.32koenhey mckoan & bluelightning
07:49.39bluelightninghi koen
07:57.57*** join/#oe stefan_schmidt (~stefan@123.143.183.198)
08:05.17pompomJuiceaargh bluelightning help me...
08:05.27bluelightningpompomJuice: what's up?
08:05.29pompomJuiceapk_base_postinst_chrome() {
08:05.41pompomJuiceI dont see the script in the ipk
08:05.43pompomJuiceit wont go
08:05.56pompomJuicerecipy is chrome_38.7.bb
08:06.35pompomJuiceis something like this legal?
08:06.36pompomJuicepk_base_postinst_${PN}() {
08:07.10bluelightningshouldn't it be pkg_postinst_${PN} () {  ?
08:07.15pompomJuiceamagad
08:07.18pompomJuiceok lets see
08:08.34pompomJuicestill not there
08:08.56pompomJuiceinside the IPK there is this debian folder that is supposed to get the script
08:09.01bluelightningwell, that is the correct syntax
08:09.02pompomJuiceit works for other packages
08:09.22pompomJuicein 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.30bluelightningpompomJuice: 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.52pompomJuiceI did not notice the pkg_
08:13.54pompomJuicelet me try again
08:14.01pompomJuicethe start differs
08:14.11bluelightningright, that would stop it from working...
08:14.53*** join/#oe tbr_ (dm8tbr@cl-790.ham-01.de.sixxs.net)
08:15.26pompomJuiceit works!
08:15.27pompomJuiceamagad
08:15.30pompomJuicethanks
08:16.09bluelightningnp
08:16.20pompomJuicei 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.23pompomJuiceand it works!
08:16.36pompomJuiceso no idea by apk_base_postinst works there...
08:16.37pompomJuicebizarre
08:17.09bluelightningI don't think it does, that code is reading apk_base_postinst and setting pkg_postinst_<packagename> from it
08:17.10pompomJuiceI wrote a system that installs APKs through opkg :)
08:17.25pompomJuiceamagad
08:17.35pompomJuiceoops
08:17.40pompomJuicetake it slow
08:18.37pompomJuicedid not see that the first part was not the same
08:18.43pompomJuicenot easy
08:19.44bluelightningI'm happy to take suggestions on how we can document this better
08:20.36pompomJuicemaybe start by explaining in some document how bitbake->oe->angstrom->layers relate
08:20.47pompomJuiceim so lost sometimes
08:21.10pompomJuicebut the documentation is good, just you dont get time to read it
08:21.15bluelightningthere is a "Post-Installation Scripts" section in the development manual (under the new "Writing a New Recipe" section)
08:21.16pompomJuiceshit must be finished today
08:21.30pompomJuicelet me check
08:21.35pompomJuicemy main issue is the following
08:21.39pompomJuiceall the documentation is split
08:21.44pompomJuiceI want one document
08:21.48pompomJuicethe macdaddy of documents
08:21.51bluelightningaha, then you are in luck :)
08:21.55pompomJuicewhere I can do a keyword search
08:21.56bluelightningcheck out the "mega manual"
08:22.02pompomJuiceawesome
08:22.19bluelightningequally though I don't mind answering questions here, even if they are in the manual
08:22.42pompomJuicethats just pure lazyness then
08:22.49pompomJuiceplease give me a link to this manual
08:22.54bluelightningI'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.00bluelightningone sec
08:23.25bluelightninghttp://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html
08:23.34pompomJuiceawesome thanks
08:23.45bluelightningthat's the 1.6 manual (the current release)
08:23.50bluelightningthe 1.5 manual is here: http://www.yoctoproject.org/docs/1.5/mega-manual/mega-manual.html
08:24.03pompomJuiceomg its huge
08:24.06pompomJuicelol
08:24.12pompomJuiceI don't feel bad anymore
08:24.12bluelightningit does say "mega" ;)
08:24.29pompomJuiceno wonder im so lost
08:25.36bluelightningI don't think we expect people to read the entire thing
08:25.49pompomJuiceyea it's not always neccesary
08:26.09pompomJuiceif the sources are able to be built by autotools it's a no brainer
08:26.15pompomJuicethe recipies are delf explanitory
08:26.18pompomJuiceself*
08:27.57pompomJuicethis is going to be awesome
08:28.29bluelightningI 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.46pompomJuiceawesome
08:29.14pompomJuiceim gonna check it out def, since the only oother writing a new recipy in the interwebs is so old
08:29.32pompomJuicemaybe include some templates
08:29.33pompomJuicelike
08:29.37pompomJuiceautotool template
08:29.41pompomJuicecmake
08:29.45pompomJuiceetc
08:30.11pompomJuiceand 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.32pompomJuicemaybe I have a legit question now
08:35.42bluelightningsure, fire away
08:35.52pompomJuiceI am busy adapting a recipy...
08:36.02pompomJuicein this recipy we have these post insttall scripts
08:36.27pompomJuiceand one of the scripts contained:
08:36.28pompomJuiceapk_base_postinst() {
08:36.28pompomJuice#!/bin/sh
08:36.28pompomJuiceAPK="%s"
08:36.34pompomJuicethat %s
08:36.36pompomJuicewhat is that?
08:36.39pompomJuicehow does that work?
08:36.44pompomJuiceit makes no sense to me
08:36.57pompomJuiceaah wait
08:37.22pompomJuiceits a placeholder for the python line that inserts it
08:37.26pompomJuicesorry man
08:37.28pompomJuiceplastic programming
08:37.30bluelightningright
08:37.32bluelightningno worries :)
08:37.34pompomJuiceI solved it now
08:37.58pompomJuiceso my question becomes
08:38.48*** join/#oe JaMa (~martin@ip-89-176-104-3.net.upcbroadband.cz)
08:39.34pompomJuicecan I insert bitbake variables into those scripts...
08:39.41pompomJuicetesting it now...
08:39.47pompomJuicethe manual does not say
08:40.03bluelightningyou can yes, just ${VARIABLENAME}
08:40.25pompomJuicesince 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.30pompomJuiceaweome
08:42.06pompomJuicewhoever invented bitbake is genius... this thing has no end
08:44.03bluelightningit's very flexible for sure
08:44.28pompomJuicevery, the things we have automated in our image is insane
08:44.30bluelightningof course that does lead to a bit of a learning curve, but it's powerful once you get to grips with it
08:44.35pompomJuicewe have a very unconventional image
08:44.42pompomJuiceand we are using bitbake on all levels
08:45.23pompomJuicebitbake just sorts out all our problems
08:46.43*** join/#oe ao2 (~ao2@2001:1418:117::1)
08:47.52bencohare you actually packaging android stuff using bitbake ?
08:47.58bencoh(just being curious)
08:50.58pompomJuiceyes
08:51.07pompomJuicethe dudes before me did something strange
08:51.18pompomJuicethey installed android ontop of linux
08:51.36pompomJuiceinstead of just adroid with gimped linux
08:51.43pompomJuiceso we have a device
08:51.55pompomJuicewith full angstom capability... but runs android
08:52.10pompomJuicethings like systemd
08:52.11pompomJuiceetc
08:52.29pompomJuicemakes it then a very powerfull device that can easily be augmented will all kinds of trickery
08:53.12pompomJuiceour android is in a jail
08:53.29pompomJuicepretty cool
08:53.45pompomJuicethe android we use is rowboat, since it's a ti chip
08:54.56bencohso you have an androidish kernel ?
08:54.58pompomJuicetherefor the recipies I am writing now enables you to opkg install android apps
08:55.05pompomJuiceyes the kernel is the bugger
08:55.10pompomJuicewhen they started this
08:55.16pompomJuicet4 years ago
08:55.31pompomJuiceti did not have a android kernel, so they took one and patched it
08:55.37pompomJuicelocking the kernel in place
08:55.43pompomJuicethat number is 2.6.37
08:55.45pompomJuicepretty annoying
08:55.58pompomJuiceso that means I can only take systemd to 204.. shit like that
08:56.43pompomJuiceI 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.36pompomJuicethe other tricky part was getting the to SGX 530 gl driver module into the kernel
08:57.43pompomJuiceand getting android to use it
08:59.44pompomJuiceyou get werid issues
08:59.45pompomJuicelike
08:59.52pompomJuicethe other day I went from linaro 4.7 4.8
08:59.58pompomJuicebam kernel brick
09:00.04pompomJuicethen solved by patching memset
09:00.09pompomJuicebam sgx driver brick
09:00.40pompomJuicememcpy from syslink no good anymore
09:00.56*** join/#oe dany (~Thunderbi@sestofw01.enea.se)
09:01.09pompomJuicethings like that
09:01.45*** join/#oe Vutral (~ss@mirbsd/special/Vutral)
09:04.27pompomJuiceuugh I have another issue
09:04.50pompomJuiceI wronte this mini recipy android-utils that contain 2 !#/bin/sh scripts
09:04.53pompomJuicewrote*
09:05.05pompomJuicethe ipk contains the scripts at /usr/bin
09:05.19pompomJuiceand the device says it is installed
09:05.24pompomJuicebut the files are not there
09:05.36pompomJuiceshould I take special precaution in recipy for script targets?
09:06.07bluelightningpompomJuice: no, no special handling should be needed
09:06.16pompomJuicemmm ok thanks.
09:06.29bluelightningwhat does the package manager list when you ask it to list files within that package?
09:06.40pompomJuicechecking
09:08.16pompomJuicestrrange
09:08.36pompomJuice./usr/bin/adb
09:08.36pompomJuice./usr/bin/aapt
09:08.43pompomJuicenow I am confused
09:09.18pompomJuiceomg
09:09.42pompomJuiceanother package adds PACKAGES += "android-utils" in another package
09:09.47pompomJuiceits a duplicatge
09:09.55pompomJuicebizarre
09:10.18pompomJuicemy package name exists... thats why...
09:10.21pompomJuiceok let me fix it
09:10.37bluelightningah right
09:11.00bluelightningthough that should have triggered a warning, unless it happened that only one of the recipes actually got built
09:12.01pompomJuiceyea
09:12.07pompomJuicewas only building the one
09:12.20pompomJuiceinteresting though
09:12.49pompomJuiceI 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.55pompomJuiceso 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.38pompomJuiceRDEPENDS_${PN} = "android-install-utils"
09:48.44pompomJuicedoes not seem to work
09:48.48pompomJuice:/
09:49.18bluelightningis android-install-utils a valid package name?
09:49.38pompomJuiceits recipy is android-install-utils_0.1.bb
09:49.56pompomJuicethat version number is purely fictitious
09:50.06bluelightningok, and that recipe produces a normal main package that is non-empty?
09:50.11pompomJuiceyes
09:50.17bluelightningwhat fails then?
09:50.20koendoes android-install-utils_0.1.bb generate a 'android-install-utils'?
09:50.20pompomJuicemy other rdepends works
09:50.21pompomJuicewell
09:50.30pompomJuiceit's like the dependency is not there
09:50.39bencoh?
09:50.50pompomJuiceeven though the chrome ipk contains in it's info a line:
09:51.03bluelightningcan you be more specific?
09:51.17pompomJuiceDepends: android-install-utils
09:51.29pompomJuicethat is inside the chrome.ipk's info file
09:51.43bencohwhat's wrong then ?
09:51.59pompomJuicebut when I do opkg install chrome it does not pull the android-install-utils first...
09:51.59koenand you don't have anything RPROVIDE'ing or RREPLACES'ing android-install-utils ?
09:52.11pompomJuicelet me check that one too
09:52.26koengrep android-install-utils /var/lib/opkg -rn
09:53.24pompomJuicedoes not seem like it
09:53.35pompomJuicelet me double check this
09:53.40pompomJuicesince other rdepends in our system works
09:53.51*** join/#oe ensc|w (~ensc@fedora/ensc)
09:54.18pompomJuiceyea
09:54.28pompomJuiceopkg uinstall chrome
09:54.35pompomJuiceopkg uninstall android-install-utils
09:54.42pompomJuiceopkg install chrome
09:54.50pompomJuiceworked
09:54.59pompomJuicesorry
09:55.36bluelightningsounds like the chrome package didn't get upgraded on the target to include the new dependency
09:55.45pompomJuiceyea
09:55.52pompomJuiceI made a weird discovery
09:56.03pompomJuiceyou can install something for the first time by saying opkg upgrade chrome
09:56.08pompomJuiceit was habit
09:56.33pompomJuicewhen it started downloading the chrome ipk I ctrl-C it thinking the deps dont work
09:56.38pompomJuicebut it downloads the dep second
09:56.40pompomJuiceamagd
09:56.43bluelightningupgrade will work after that, but the version number has to change or it'll think nothing has tobe done
09:56.49pompomJuiceI see
09:56.59bencohinstall --reinstall
09:57.06bencohhm, --force-reinstall
09:57.18pompomJuiceyea that one
09:57.53pompomJuiceand it works
09:57.55pompomJuiceeverything works
09:57.58bencoh:)
09:58.29pompomJuicesorry 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.30pompomJuicethanks all
09:58.38pompomJuiceit works
09:58.41pompomJuiceboss man is happy
09:58.46pompomJuiceI can relax again
09:58.50bencohnow you can play around with OE ;)
09:58.57pompomJuiceyea
09:59.28pompomJuiceone interesting I notice though
09:59.45pompomJuicemy pkg_postinst script contains echo "some status" to give some feedback
09:59.56pompomJuicethe feedback is printed twice, but I am sure the script only runs once
10:00.05pompomJuiceunless my dupcheck wored
10:00.10pompomJuiceworked*
10:00.12pompomJuiceanyway
10:02.23pompomJuiceyea the script executed only once otherwise my dupcheck echoes would have printed..
10:13.29pompomJuicekoen legend btwe
10:13.41pompomJuiceeveryone in this office knows the name
10:13.47pompomJuicefyi
10:13.49pompomJuice;)
10:21.03*** join/#oe KNERD|2 (~KNERD@24.175.253.226)
10:53.42woglindeah nice the google-pdf plugin
10:53.50woglindenow we can make it run under arm too
10:54.00woglindefor 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.36pompomJuiceI 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.41koenpompomJuice: 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.58koenfor some postinsts OE will try to run them under qemu or another wrapper
11:47.11koene.g. gtk-pixbuf and icon cache postinsts
11:47.25pompomJuiceyea I see my script is switching on $D like you said
11:47.53pompomJuiceok so am I to assume that those scripts are run and they fail? Or what?
11:47.58koenpostinsts are just shellscripts opkg will run with some extra vars set (like $D)
11:48.14pompomJuiceare they run when the image is generated
11:48.15pompomJuice?
11:48.17pompomJuicesurely
11:48.30pompomJuicewhat happens if they fail or "hang"?
11:48.36pompomJuiceok wait
11:48.39pompomJuicethey are switching on 4D
11:48.43pompomJuice$D
11:48.46pompomJuiceso they wont hang
11:48.48pompomJuicenm
11:48.51bluelightningif they fail they are postponed until first boot
11:48.58pompomJuiceaah
11:49.11pompomJuicethat could come in handy
11:49.17pompomJuiceexactly what I need
11:49.21pompomJuicetop top
11:49.23pompomJuicewill test it now
11:49.43koeniirc 1.5 introduced the qemu and wrapper stuff
11:49.56pompomJuiceSo 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.14pompomJuiceinteresting... that qemu move
11:50.36pompomJuicemust you have a qemu configuration ready?
11:50.37bluelightningif 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.51pompomJuicethanks bluelightning
11:50.57pompomJuicetesting 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.23athoikhello,  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.31bluelightningathoik: it won't be normally, no
12:22.47bluelightningathoik: you may be able to get it to apply if you set PATCHTOOL = "git" within the recipe
12:23.27koenand if that fails, add the binaries to SRC_URI and overwrite the originals in do_configure_prepend
12:23.37koendo_unpack is python, right?
12:24.11bluelightningyep
12:24.52athoikbluelightning: 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.14athoikbluelightning:  PATCHTOOL = "git" did the trick! really\ thanks a lot!
12:30.43*** join/#oe adelcast (~adelcast@130.164.62.249)
12:32.45bluelightningathoik: 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.29Crofton|workHow 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.30bluelightningCrofton|work: sorry, what's the context?
16:21.51Crofton|workI sent a patch in, trying to figure out how I can follow its path into oe-core master
16:22.05Crofton|workso I know when to ask it go into diane
16:22.16bluelightningdaisy? dora? dylan?
16:22.24Crofton|workdaisy
16:22.33Crofton|workto many d words
16:22.51bluelightningI 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.11Crofton|workI 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.31bluelightningbeyond patchwork and the mailing list we don't really have anything
16:36.38kergothset up a cron job to update a clone and git log —grep= it for your commit periodically? ;)
16:37.07bluelightningwell, we do have the oe-commits list as well, that's probably easier than that ;)
16:40.45kergothsets 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.56bluelightninghmm so it seems the layer index wasn't updating properly for the master branch since the server was moved
20:02.12bluelightningmainly because I forgot to switch it to use the proper branch of bitbake
20:02.25bluelightningI'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)

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.