| *** rburton <rburton!~rburton@35.106.2.81.in-addr.arpa> has quit IRC | 01:11 | |
| *** kaspter <kaspter!~Instantbi@115.205.170.215> has joined #yocto | 01:30 | |
| *** vineela <vineela!~vtummala@134.134.139.76> has joined #yocto | 02:52 | |
| *** georgem_home <georgem_home!uid210681@gateway/web/irccloud.com/x-aumceoiuuvjqglge> has quit IRC | 02:59 | |
| *** stew-dw <stew-dw!~stew-dw@207.242.234.14> has quit IRC | 03:55 | |
| *** stew-dw <stew-dw!~stew-dw@207.242.234.14> has joined #yocto | 03:55 | |
| *** vineela <vineela!~vtummala@134.134.139.76> has quit IRC | 04:20 | |
| *** agust <agust!~agust@p508B63E2.dip0.t-ipconnect.de> has joined #yocto | 04:41 | |
| *** comptroller <comptroller!~comptroll@47-213-222-253.paolcmtc01.res.dyn.suddenlink.net> has quit IRC | 04:53 | |
| *** comptroller <comptroller!~comptroll@47-213-222-253.paolcmtc01.res.dyn.suddenlink.net> has joined #yocto | 05:08 | |
| *** AndersD <AndersD!~AndersD@h-98-128-162-82.NA.cust.bahnhof.se> has joined #yocto | 05:43 | |
| *** TobSnyder <TobSnyder!~schneider@ip5f5aa32f.dynamic.kabel-deutschland.de> has joined #yocto | 05:59 | |
| LetoThe2nd | mccc: heya. i should be around all day. and if you are interested, i'll be running the twitch live sessions tonight :) | 06:02 |
|---|---|---|
| mccc | Link? | 06:13 |
| mccc | If it's https://www.twitch.tv/yocto_project it looks like I missed you - I'll try and catch you next time :) | 06:15 |
| *** tprrt <tprrt!~tprrt@217.114.201.133> has joined #yocto | 06:15 | |
| *** frsc <frsc!~frsc@2003:a:e7a:6200:246c:2a8b:f45a:a33d> has joined #yocto | 06:18 | |
| LetoThe2nd | hehe no, this night. in about 8.5 hrs | 06:24 |
| LetoThe2nd | mccc: so, what do you mean exactly by the clouod server topic. like, full linux systems to run inside a vm? or rather containers? | 06:26 |
| *** yann <yann!~yann@lfbn-1-3372-5.w90-127.abo.wanadoo.fr> has quit IRC | 06:34 | |
| *** Bunio_FH <Bunio_FH!~bunio@2a02:a313:4343:f080:9d18:ca0d:49ff:1965> has joined #yocto | 06:43 | |
| *** jmiehe <jmiehe!~Thunderbi@p578c106e.dip0.t-ipconnect.de> has joined #yocto | 06:51 | |
| mccc | Full Linux systems to run inside a VM. I have a service backend right now that uses a couple of VM types and I'm manually administering them. I was evaluating options to automate them and considered Yocto combined with an orchestrator like Terraform or Pulumi. I don't have much container experience, but a full disk image feels like a natural artifact to use to divide the configuration side | 07:04 |
| mccc | from the orchestration side. I saw other recent projects taking this approach, LinuxKit and Packer. I'm using Yocto in the same project to deliver an embedded system so I wanted to consider using it here too. | 07:04 |
| LetoThe2nd | mccc: hmmmm ok. | 07:06 |
| LetoThe2nd | mccc: well the main thing about yocto or rather openembedded to be precise, is to create a custom linux distribution. so if you know beforehand what you will want in that vm image, there nothing that keeps you from creating it. | 07:07 |
| *** sk_tandt <sk_tandt!~sk_tandt@net-5-88-141-17.cust.vodafonedsl.it> has joined #yocto | 07:08 | |
| *** fl0v0 <fl0v0!~fvo@i53870EF0.versanet.de> has joined #yocto | 07:09 | |
| LetoThe2nd | mccc: it just boils down to this. pro side: total control over the generated image. (where some forms of control take littel effort, some take much). contra side: you most likely end up with a linux distribution in your container that is to at least some degree incompatible with what the rest of the word takes for granted. | 07:10 |
| LetoThe2nd | s/word/world/ | 07:11 |
| LetoThe2nd | mccc: so you'd really have to make up your mind on what the image shall bring, what the orchestration should do, etc. | 07:11 |
| LetoThe2nd | mccc: because if in the end you just need a drop-in for a slim ubuntu or alpine base install, then you're almost certainly better off just using those. | 07:12 |
| LetoThe2nd | mccc: best example: an OE-based image does by default not bring a package manager. and no package repositories too, of course. | 07:13 |
| *** florian <florian!~florian_k@Maemo/community/contributor/florian> has joined #yocto | 07:14 | |
| mccc | Okay. Immutable infrastructure seems to be the hot topic, but it seems like most approaches include starting with a popular distribution, running a configuration manager tool on it, capturing the image, and using it. While a configuration manager would use the distribution's package repositories during configuration time to bring down software, with the immutable infrastructure pattern you | 07:15 |
| mccc | wouldn't expect to use those package managers on that image again. Instead, you would start from scratch when it comes time to upgrade. | 07:15 |
| mccc | In that sense the Yocto Layer Index and community recipes end up taking the place of a distribution's package manager - it's the place where I'd bring software down when building an image. | 07:15 |
| mccc | If the software I would end up needing is available in the layer index, I feel like that should be as good as if it were available in a distribution's package manager. | 07:17 |
| LetoThe2nd | mccc: exactly, that the thing one needs to get his head around. the recipes in the layer index are basically the equivalent of a classic package repository | 07:18 |
| LetoThe2nd | mccc: so, if your approach is to generate a full custom image based on that, which then only needs a handful of configuration artifacts deployed through orchestration, then you're good to go | 07:18 |
| *** florian <florian!~florian_k@Maemo/community/contributor/florian> has quit IRC | 07:19 | |
| LetoThe2nd | mccc: for a usecase like this, you'd probably jsut use the generic x86-64 machine, maybe core-image-minimal as the starting point, and then evolve. | 07:20 |
| *** florian <florian!~florian_k@Maemo/community/contributor/florian> has joined #yocto | 07:21 | |
| *** cvasilak <cvasilak!~cvasilak@2a02:587:8118:a100:30e7:ee7e:f260:2b42> has joined #yocto | 07:21 | |
| mccc | That seems to be the point of the immutable infrastructure pattern, but as we've talked about there isn't much online about using Yocto for this. Most guides talk about using a configuration manager like Chef or Jenkins during image build time, and then there are the LinuxKit and Packer projects. | 07:22 |
| *** mckoan|away is now known as mckoan | 07:22 | |
| LetoThe2nd | mccc: the key difference between vm and container is that the former needs the full shbang in terms of init process and all, so you can't strip it down as aggressively as a container image. there, you can literally just define the binary thats going to be run, and let OE figure out its dependencies to go into the image | 07:22 |
| mckoan | good morning | 07:22 |
| mccc | Good morning mckoan :) | 07:24 |
| alessioigor | good morning | 07:24 |
| LetoThe2nd | mccc: if you're using yocto/OE, there is little to additionally document by default in comparison to a standard embedded image. those are "immutable" too by mindset. | 07:25 |
| mccc | LetoThe2nd - that makes sense. Because I don't have much Docker / container experience, I'm trying to make sure I'm not missing anything about containers in the mix here. | 07:25 |
| mccc | Your point about an app designer being able to just define the binary and ignore the operating system makes sense, of course you take a dependency on the container system, but the OS can be swapped out underneith. | 07:26 |
| mccc | In this scenario though as an app designer I take a dependency on Yocto when I define my recipes, | 07:26 |
| mccc | and then as an image creator I do the work of defining the rest of the OS. | 07:27 |
| LetoThe2nd | mccc: building custom containers is where things are really different. because your run of the mill ubuntu container is, well, an ubuntu where a lot of stuff is around but never run - there is no pid 1, basically. this is where yocto/OE shines, you can totally build something that has no init, no bash, no anything | 07:27 |
| mccc | I'm wondering if the extra work of 1) the Yocto learning curve and 2) being responsible for defining the rest of the OS, is what makes writing an app for a container that runs on a regular distribution the more common path. | 07:29 |
| mccc | I really do like that about Yocto though, the massive configurability and the ability to start from nothing and pull in just what's needed. | 07:30 |
| *** yacar_ <yacar_!~yacar@80.214.29.221> has joined #yocto | 07:31 | |
| mccc | I'm also trying to make sure I'm not swimming too far upstream though, since I don't see much online about using Yocto for cloud VM images. | 07:31 |
| *** florian <florian!~florian_k@Maemo/community/contributor/florian> has quit IRC | 07:34 | |
| mccc | It's late here so I'm going to head home, but I really appreciate your discussion about this, thank you. | 07:36 |
| LetoThe2nd | mccc: sorry, phone. | 07:38 |
| *** T_UNIX <T_UNIX!uid218288@gateway/web/irccloud.com/x-jgdaehmumhrmqpge> has joined #yocto | 07:38 | |
| LetoThe2nd | mccc: it depends. my gut feeling is, that it only pays of if you either have super special requirements, or if you are running such a massive amount of vms/containers that the reduced resource consumption pays off. | 07:38 |
| LetoThe2nd | mccc: for the vast majority of cases, i'd probably say that sticking to common practises is more efficient in terms of work output | 07:39 |
| mccc | That makes sense. The other consideration is I'm already using Yocto in the project for embedded so it would at least share the tool. | 07:40 |
| LetoThe2nd | mccc: it would only share the knowledge. | 07:41 |
| mccc | :) thanks again so much for the discussion. Have a good night! | 07:45 |
| LetoThe2nd | mccc: you too. | 07:45 |
| *** leitao <leitao!~leitao@2620:10d:c092:200::1:5f17> has joined #yocto | 07:53 | |
| *** florian <florian!~florian_k@Maemo/community/contributor/florian> has joined #yocto | 07:57 | |
| qschulz | Does anyone know on which branch of openembedded-core I should base my patches ebfore sending them upstream? I based it on master-next but it was rejected by the build/test bot :/ | 07:58 |
| *** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has joined #yocto | 08:00 | |
| erbo | qschulz: use master | 08:09 |
| *** florian <florian!~florian_k@Maemo/community/contributor/florian> has quit IRC | 08:11 | |
| qschulz | erbo: thx | 08:12 |
| *** AndersD <AndersD!~AndersD@h-98-128-162-82.NA.cust.bahnhof.se> has quit IRC | 08:37 | |
| LetoThe2nd | ndec: sure, i can mention that too. if i should forget, just remind me and point it out in the chat | 08:37 |
| ndec | LetoThe2nd: sure! | 08:38 |
| *** AndersD <AndersD!~AndersD@h-98-128-162-82.NA.cust.bahnhof.se> has joined #yocto | 08:38 | |
| *** jeanba <jeanba!~jbl@77.243.63.34> has joined #yocto | 08:44 | |
| *** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto | 08:45 | |
| *** jeanba <jeanba!~jbl@77.243.63.34> has left #yocto | 08:49 | |
| *** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC | 08:50 | |
| tprrt | Hello everyone, I have a question about testsdk, is it possible to have the results in JUnit xml format? | 08:54 |
| *** florian <florian!~florian_k@Maemo/community/contributor/florian> has joined #yocto | 08:59 | |
| *** khem <khem!~khem@unaffiliated/khem> has quit IRC | 09:02 | |
| *** khem <khem!~khem@unaffiliated/khem> has joined #yocto | 09:02 | |
| RP | tprrt: we standardised on json as the output format but it should be trivial to convert to that | 09:05 |
| *** awe00 <awe00!~awe00@unaffiliated/awe00> has joined #yocto | 09:06 | |
| *** rburton <rburton!~rburton@35.106.2.81.in-addr.arpa> has joined #yocto | 09:11 | |
| luckywho | I'm trying to inegrate nodejs in image file. IMAGE_INSTALL += "nodejs". BUt getting following error ERROR: nodejs-6.10.0-r0 do_package_qa: QA Issue: /usr/lib/node_modules/npm/scripts/dep-update contained in package nodejs requires /bin/bash, but no providers found in RDEPENDS_nodejs? [file-rdeps] | 09:12 |
| luckywho | ERROR: nodejs-6.10.0-r0 do_package_qa: QA Issue: /usr/lib/node_modules/npm/node_modules/node-gyp/gyp/samples/samples contained in package nodejs requires /usr/bin/python, but no providers found in RDEPENDS_nodejs? [file-rdeps]. | 09:12 |
| tprrt | luckywho: From the nodejs recipe, you should add bash into the RDEPENDS_${PN} to fix the first error. And for the second error, you should add the inheritance to the python bbclass. | 09:14 |
| luckywho | 1. RDEPENDS_${PN} += "bash" | 09:15 |
| *** khem <khem!~khem@unaffiliated/khem> has quit IRC | 09:16 | |
| *** khem <khem!~khem@unaffiliated/khem> has joined #yocto | 09:16 | |
| tprrt | RP: thanks, and where is this json file located? because I only found the file log.do_testsdk. | 09:17 |
| *** yann <yann!~yann@85.118.38.73> has joined #yocto | 09:32 | |
| *** Bunio_FH <Bunio_FH!~bunio@2a02:a313:4343:f080:9d18:ca0d:49ff:1965> has quit IRC | 09:39 | |
| yann | kergoth: (reacting to your answer 4 days ago) so the problem would be a bad interaction between "${SYSROOT_DESTDIR}${base_prefix}/sysroot-providers/" in staging.bbclass and base_prefix = "${STAGING_DIR_NATIVE}" in native.class, which basically means that those 2 classes are mutually incompatible, right ? | 09:40 |
| *** yacar_ <yacar_!~yacar@80.214.29.221> has quit IRC | 09:47 | |
| *** kaspter <kaspter!~Instantbi@115.205.170.215> has quit IRC | 09:52 | |
| *** Bunio_FH <Bunio_FH!~bunio@81-18-201-214.static.chello.pl> has joined #yocto | 09:55 | |
| *** dsangue <dsangue!~Daniel@213.55.184.195> has joined #yocto | 09:57 | |
| *** dsangue <dsangue!~Daniel@213.55.184.195> has left #yocto | 09:58 | |
| *** dsangue <dsangue!~Daniel@213.55.184.195> has joined #yocto | 09:59 | |
| *** dsangue <dsangue!~Daniel@213.55.184.195> has left #yocto | 10:01 | |
| *** dsangue <dsangue!~Daniel@213.55.184.195> has joined #yocto | 10:05 | |
| *** kanavin <kanavin!~kanavin@141.113.67.170> has joined #yocto | 10:18 | |
| *** dsangue <dsangue!~Daniel@213.55.184.195> has quit IRC | 10:18 | |
| luckywho | tprrt: And for the second error, you should add the inheritance to the python bbclass. why? we can add as RDEPENDS_$(PN) += "python"(image filesystem failed at do_makesystem). If i add inherit python. It will look for python.bbclass. I have following python classes. "python3-dir.bbclass python3native.bbclass python-dir.bbclass pythonnative.bbclass". | 10:22 |
| *** prabhakarlad <prabhakarlad!~prabhakar@194.75.40.178> has joined #yocto | 10:30 | |
| *** kuzulis <kuzulis!~kuzulis@37.112.57.60> has joined #yocto | 10:36 | |
| *** kaspter <kaspter!~Instantbi@183.128.187.205> has joined #yocto | 10:36 | |
| *** mckoan is now known as mckoan|away | 10:39 | |
| kuzulis | Hi guys, how to configure the image correctly to use the 4G modems? f.e. I have the HUAWEI E3372 modem. By default it initializes in 'mass storage' mode and has vid/pid 12d1:if01.. So, I need the usb-modeswitch-{data} recipes. So, I have added this recipes to my image as: IMAGE_INSTALL_append = "usb-modeswitch \ usb-modeswitch-data"... But, the usb mode does not switched in a result... and my modem still detected as a 'mass storage'... | 10:41 |
| kuzulis | I looked in /usr/share/usb_modeswitch that there are present a configuration for my modem.. in a file 12d1:1f01.. | 10:42 |
| kuzulis | Ahh.. seems, I need to it manually, like: usb_modeswitch -v 12d1 -p 1f01 -c /usr/share/usb_modeswitch/12d1\:1f01 | 10:45 |
| tprrt | luckywho: Sorry, you should add ${PYTHON_PN} to RDEPENDS_${PN}. | 11:07 |
| tprrt | kuzulis: for this to be automatic, you may need to make a modification in a struct of the kernel: static const struct usb_device_id option_ids[] drivers/usb/serial/option.c. | 11:12 |
| *** yacar_ <yacar_!~yacar@80.214.29.221> has joined #yocto | 11:17 | |
| kuzulis | tprrt: Why if I try to create an udev rule instead? Is it will help? | 11:18 |
| *** JaMa <JaMa!~martin@ip-217-030-068-212.aim-net.cz> has joined #yocto | 11:21 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@194.75.40.178> has quit IRC | 11:22 | |
| *** AndersD <AndersD!~AndersD@h-98-128-162-82.NA.cust.bahnhof.se> has quit IRC | 11:23 | |
| luckywho | tprrt: I have added RDEPENDS_${PN} += "bash ${PYTHON_PN}". I'm getting follwoing error. error: ext4_allocate_best_fit_partial: failed to allocate 2 blocks, out of space? | fs_config_file: /home/poky/build/tmp-glibc/work/linux-gnueabi/machine-image/1.0-r0/rootfs-fsconfig.conf | 11:25 |
| tprrt | kuzulis: it is also a right solution, implement an udev rules calling usb_modeswitch | 11:25 |
| kuzulis | tprrt: ok, many thanks | 11:30 |
| RP | tprrt: TMPDIR/log/oeqa/testresults.json | 11:31 |
| *** prabhakarlad <prabhakarlad!~prabhakar@194.75.40.178> has joined #yocto | 11:32 | |
| kanavin | RP: was pulling hairs trying to reproduce the gtk failure, then realized I was building gtk+ (e.g. 2.x), not gtk+3 :) | 11:34 |
| *** berton <berton!~berton@181.220.86.53> has joined #yocto | 11:42 | |
| RP | kanavin: sorry, I eventually realised it was a resource issue, I think | 12:02 |
| RP | kanavin: we're getting too many hard to track down odd issues atm :( | 12:02 |
| tprrt | RP: Thanks for your help. | 12:08 |
| *** radsquirrel <radsquirrel!~bradleyb@mail.fuzziesquirrel.com> has quit IRC | 12:15 | |
| *** radsquirrel <radsquirrel!~bradleyb@mail.fuzziesquirrel.com> has joined #yocto | 12:16 | |
| *** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has quit IRC | 12:47 | |
| *** diego_r <diego_r!~diego@host57-224-static.7-79-b.business.telecomitalia.it> has joined #yocto | 12:52 | |
| *** cvasilak <cvasilak!~cvasilak@2a02:587:8118:a100:30e7:ee7e:f260:2b42> has quit IRC | 12:55 | |
| *** geissonator <geissonator!~geissonat@45-18-127-186.lightspeed.austtx.sbcglobal.net> has joined #yocto | 13:07 | |
| *** Crofton|road <Crofton|road!~Crofton@38.90.133.135> has quit IRC | 13:22 | |
| yann | removing a couple of extra defs finally leads me to a satisfactory recipe-sysroot-native being deployed to user recipes, but the fact sysroot-destdir/ contains a duplication of the whole directory tree still makes me nervous | 13:31 |
| RP | yann: if you mean for native recipes, that is necessary | 13:38 |
| RP | it looks odd, it isn't when you realise that sysroot-destdir is a sysroot, the files placed there are installed at their final end user paths, prefixed by the DESTDIR | 13:39 |
| yann | hm, but then they aren't ever going to be used at that place, since they're relocated for each recipe using them | 13:41 |
| yann | anyway, a short note in staging.class or native.class documentation would help avoid the confusion, I'd say :) | 13:42 |
| RP | yann: they might not be used at that exact path but they will be used at a location like that and other things will be at paths relative to the path. It does help a lot to install like that | 13:43 |
| RP | yann: patches welcome | 13:43 |
| kanavin | RP: I mean the issue that is specific to the gtk+3 version upgrade | 13:44 |
| RP | kanavin: ah, and you were building gtk+ locally, right... | 13:44 |
| RP | kanavin: sorry, my brain is fried atm :/ | 13:44 |
| kanavin | yes, no problem. once I sort that out, there are a few spare cycles I could use to help | 13:45 |
| *** berton_ <berton_!~berton@181.220.86.53> has joined #yocto | 13:45 | |
| yann | RP: as usual, I'm a bit wary when it comes to documenting a behaviour I just discovered :) | 13:46 |
| kanavin | btw, the lwn discussion under your article is a bit discouraging: people did not fail to notice that a) the failure was not picked up until a kernel developer hit the problem locally; b) the failure made it through the kernel review and testing process into stable kernele releases | 13:46 |
| RP | kanavin: there are certainly problems and things that could have happened better | 13:47 |
| JPEW | Is that public yet? | 13:47 |
| RP | kanavin: equally we could have been totally oblivious to it instead so I'd say we got better | 13:47 |
| RP | JPEW: yes | 13:48 |
| JPEW | Ah, found it | 13:48 |
| RP | JPEW: https://lwn.net/Articles/788626/ | 13:48 |
| JPEW | RP: thanks | 13:48 |
| *** berton <berton!~berton@181.220.86.53> has quit IRC | 13:48 | |
| *** kuzulis <kuzulis!~kuzulis@37.112.57.60> has quit IRC | 13:55 | |
| RP | kanavin: I think it got the idea out there that distro testing like we're doing can help the kernel. Next time we send a bug, just maybe they may pay more attention | 13:55 |
| JPEW | RP: It's a good article | 13:56 |
| JPEW | Hrmm, perl is encoding the absolute path to miniperl in its source... this is not reproducible :( | 13:57 |
| RP | JPEW: thanks :) | 13:58 |
| RP | JPEW: no, that is bad :( | 13:58 |
| kergoth | yann: if native used a normal prefix like / or /usr, it’d be troublesome to do the relocation, as part of that is a sed replacement, and you can’t very well go replacing every instance of “/“. That said, we could probably just as well use a specific placeholder, I think. Wouldn’t buy us much though | 14:03 |
| * kergoth yawns | 14:03 | |
| *** TobSnyder <TobSnyder!~schneider@ip5f5aa32f.dynamic.kabel-deutschland.de> has quit IRC | 14:07 | |
| *** comptroller <comptroller!~comptroll@47-213-222-253.paolcmtc01.res.dyn.suddenlink.net> has quit IRC | 14:13 | |
| *** Crofton|road <Crofton|road!~Crofton@23-25-123-169-static.hfc.comcastbusiness.net> has joined #yocto | 14:16 | |
| *** learningc <learningc!~learningc@121.121.98.115> has joined #yocto | 14:17 | |
| RP | yann: we never used to relocate things and this code does date from then. it works well, we have other things which cause problems... | 14:17 |
| RP | kergoth: how much would we change if we started doing this from scratch today? :) | 14:18 |
| *** comptroller <comptroller!~comptroll@47-213-222-253.paolcmtc01.res.dyn.suddenlink.net> has joined #yocto | 14:26 | |
| *** leitao <leitao!~leitao@2620:10d:c092:200::1:5f17> has quit IRC | 14:29 | |
| *** Bunio_FH <Bunio_FH!~bunio@81-18-201-214.static.chello.pl> has quit IRC | 14:30 | |
| *** leitao <leitao!~leitao@2620:10d:c092:200::1:5f17> has joined #yocto | 14:32 | |
| *** tprrt <tprrt!~tprrt@217.114.201.133> has quit IRC | 14:32 | |
| *** tijko <tijko!~tijko@unaffiliated/tijko> has joined #yocto | 14:36 | |
| *** Dvorkin <Dvorkin!b072cc0c@gateway/web/freenode/ip.176.114.204.12> has joined #yocto | 14:39 | |
| *** dreyna <dreyna!~dreyna@c-24-5-28-247.hsd1.ca.comcast.net> has joined #yocto | 14:56 | |
| *** leitao <leitao!~leitao@2620:10d:c092:200::1:5f17> has quit IRC | 14:57 | |
| *** vineela <vineela!~vtummala@134.134.139.83> has joined #yocto | 14:58 | |
| LetoThe2nd | ndec: no timing glitch today! | 14:59 |
| fray | FYI I'm in the twitch chat, but on a meeting.. so I might be delayed if needed... | 15:00 |
| LetoThe2nd | fray: noted, thanks! | 15:00 |
| *** leitao <leitao!~leitao@2620:10d:c092:200::1:5f17> has joined #yocto | 15:01 | |
| kergoth | RP: heh, indeed. could take a little inspiration from nix's individual checksum-based prefixes, perhaps | 15:04 |
| * kergoth yawns | 15:04 | |
| rburton | joined | 15:04 |
| *** leitao <leitao!~leitao@2620:10d:c092:200::1:5f17> has quit IRC | 15:13 | |
| *** frsc <frsc!~frsc@2003:a:e7a:6200:246c:2a8b:f45a:a33d> has quit IRC | 15:18 | |
| *** wlindauer <wlindauer!c092655a@gateway/web/freenode/ip.192.146.101.90> has joined #yocto | 15:24 | |
| *** leitao <leitao!~leitao@2620:10d:c092:200::1:5f17> has joined #yocto | 15:25 | |
| *** yacar_ <yacar_!~yacar@80.214.29.221> has quit IRC | 15:30 | |
| *** leitao <leitao!~leitao@2620:10d:c092:200::1:5f17> has quit IRC | 15:31 | |
| rburton | RP: not sure the pylint patchtest is doing the right thing | 15:32 |
| moto-timo | rburton: it's running python3 right? | 15:34 |
| *** yacar_ <yacar_!~yacar@80.214.29.221> has joined #yocto | 15:35 | |
| *** WillMiles <WillMiles!~Will@static-209-87-231-80.storm.ca> has joined #yocto | 15:35 | |
| rburton | no idea what the test does, but its erroring in a stupid way | 15:35 |
| moto-timo | I found the code, trying not to look too hard ;) | 15:36 |
| moto-timo | I think linting has grown up a bit since 2016... | 15:37 |
| *** leitao <leitao!~leitao@2620:10d:c092:200::1:5f17> has joined #yocto | 15:41 | |
| RP | rburton: it probably isn't. I thought you meant the one on the autobuilder for a second | 15:42 |
| *** leitao <leitao!~leitao@2620:10d:c092:200::1:5f17> has quit IRC | 15:44 | |
| *** tprrt <tprrt!~tprrt@upc31-1-78-208-110-13.fbx.proxad.net> has joined #yocto | 15:49 | |
| *** leitao <leitao!~leitao@2620:10d:c092:200::1:5f17> has joined #yocto | 15:52 | |
| *** yacar_ <yacar_!~yacar@80.214.29.221> has quit IRC | 15:56 | |
| LetoThe2nd | unbelievable how a fly around you is when you're already trying to explain something and have a beer! | 15:57 |
| LetoThe2nd | *how annoying | 15:57 |
| *** sk_tandt <sk_tandt!~sk_tandt@net-5-88-141-17.cust.vodafonedsl.it> has quit IRC | 15:59 | |
| JPEW | I've always wanted to make a fly tracking laser... | 15:59 |
| *** stephano <stephano!stephano@nat/intel/x-ptekjlztcwioncnu> has joined #yocto | 16:00 | |
| LetoThe2nd | mckoan|away: thanks for the input, BTW | 16:00 |
| RP | LetoThe2nd: sorry I was in the other meeting :( | 16:00 |
| LetoThe2nd | RP: no problem. was a really slow session anyways | 16:00 |
| RP | JPEW: the midges we get in the forests around here would just mob such a device :/ | 16:01 |
| LetoThe2nd | at least here its vacation season | 16:01 |
| RP | LetoThe2nd: what is "vacation"? | 16:01 |
| RP | I shouldn't joke, I am getting better at taking breaks | 16:02 |
| LetoThe2nd | RP: when you have to pay for your drinks yourself, but on the other hand do not have to code while emptying them | 16:02 |
| LetoThe2nd | as opposed to not paying, but having to code while.... | 16:02 |
| LetoThe2nd | RP: glad to hear, seriously | 16:02 |
| LetoThe2nd | hope i didn't talk too much nonsense, but neither you nor fray nor kergoth screamed! :) | 16:03 |
| RP | LetoThe2nd: working from home doesn't quite work like that :) | 16:03 |
| RP | LetoThe2nd: I wasn't there to scream :( | 16:03 |
| LetoThe2nd | hehe | 16:03 |
| RP | LetoThe2nd: sounds like you had good company though | 16:03 |
| LetoThe2nd | little company, i think. but well see. request #1: "make past stream sessions available" | 16:04 |
| LetoThe2nd | anyways, see you laters. family time now. | 16:04 |
| RP | LetoThe2nd: thanks for doing it! | 16:04 |
| ndec | LetoThe2nd: we are not saying it enough ... but thank you for your work on the live sessions! today's session about packaging was good. it's a difficult thing to understand for new people... it was a good intro. | 16:06 |
| *** tlwoerner <tlwoerner!~Trevor@unaffiliated/tlwoerner> has quit IRC | 16:12 | |
| *** tlwoerner <tlwoerner!~Trevor@unaffiliated/tlwoerner> has joined #yocto | 16:13 | |
| *** awe00 <awe00!~awe00@unaffiliated/awe00> has quit IRC | 16:16 | |
| *** jmiehe <jmiehe!~Thunderbi@p578c106e.dip0.t-ipconnect.de> has quit IRC | 16:20 | |
| *** yann <yann!~yann@85.118.38.73> has quit IRC | 16:21 | |
| *** diego_r <diego_r!~diego@host57-224-static.7-79-b.business.telecomitalia.it> has quit IRC | 16:29 | |
| *** tprrt <tprrt!~tprrt@upc31-1-78-208-110-13.fbx.proxad.net> has quit IRC | 16:35 | |
| *** fl0v0 <fl0v0!~fvo@i53870EF0.versanet.de> has quit IRC | 16:43 | |
| *** tprrt <tprrt!~tprrt@upc31-1-78-208-110-13.fbx.proxad.net> has joined #yocto | 16:47 | |
| *** rubdos <rubdos!~rubdos@2a02:578:859d:701:a846:9858:21a:9451> has quit IRC | 17:15 | |
| *** leitao <leitao!~leitao@2620:10d:c092:200::1:5f17> has quit IRC | 17:17 | |
| *** armpit2 <armpit2!~armpit@2601:202:4180:c33:ac5b:d26e:fac2:f89f> has joined #yocto | 17:19 | |
| *** armpit <armpit!~armpit@2601:202:4180:c33:50d3:300:d9ff:2f1d> has quit IRC | 17:21 | |
| *** armpit2 is now known as armpit | 17:24 | |
| armpit | RP, the opk patches for thud included a testcase. Should I bug it so we might create a OEQA test? | 17:26 |
| *** florian <florian!~florian_k@Maemo/community/contributor/florian> has quit IRC | 17:27 | |
| *** awe00 <awe00!~awe00@unaffiliated/awe00> has joined #yocto | 17:36 | |
| *** T_UNIX <T_UNIX!uid218288@gateway/web/irccloud.com/x-jgdaehmumhrmqpge> has quit IRC | 17:38 | |
| *** yann <yann!~yann@lfbn-1-3372-5.w90-127.abo.wanadoo.fr> has joined #yocto | 17:41 | |
| yann | hm, looks like I sent my doc patch to the wrong list, should have been yocto@yoctoproject.org, right ? Should I just resubmit to proper list ? | 17:42 |
| *** rubdos <rubdos!~rubdos@2a02:578:859d:701:a846:9858:21a:9451> has joined #yocto | 17:43 | |
| RP | armpit: could create a newcommer bug, yes | 17:46 |
| armpit | k | 17:46 |
| RP | armpit: good thinking | 17:46 |
| armpit | it happens once in a while ; ) | 17:46 |
| *** tprrt <tprrt!~tprrt@upc31-1-78-208-110-13.fbx.proxad.net> has quit IRC | 17:49 | |
| *** alessioigor <alessioigor!~alessioig@140.105.207.227> has quit IRC | 17:53 | |
| *** florian <florian!~florian_k@Maemo/community/contributor/florian> has joined #yocto | 18:00 | |
| *** behanw <behanw!uid110099@gateway/web/irccloud.com/x-vqcywzelhgapzsnh> has quit IRC | 18:10 | |
| *** tgraydon <tgraydon!tgraydon@nat/intel/x-bwsuyqnqzwzwyqcw> has joined #yocto | 18:14 | |
| *** learningc <learningc!~learningc@121.121.98.115> has quit IRC | 18:22 | |
| *** agust <agust!~agust@p508B63E2.dip0.t-ipconnect.de> has quit IRC | 18:27 | |
| LetoThe2nd | ndec: no need to, its just the form of deal i can offer. we use yocto/oe in our daily work, but i don't have company money to hand out. so this is what i can do. in a nutshell: you help me in getting my work done, i help you in getting yours done. | 18:30 |
| *** agust <agust!~agust@pD95F1ED1.dip0.t-ipconnect.de> has joined #yocto | 18:37 | |
| stephano | I'm working on a poky-tiny build for a firmware flash part (4MB). Following the basic steps here: https://wiki.yoctoproject.org/wiki/Poky-Tiny | 18:38 |
| stephano | bsp_definition is dropping me into the bb_fatal for "Could not locate BSP definition" | 18:39 |
| stephano | Did I miss a step setting up the defconfig? | 18:39 |
| LetoThe2nd | stephano: whoa. sorry, but that article seems to be quite outdated. | 18:43 |
| LetoThe2nd | stephano: for example eglibc vs. uclibc hasn't been a thing for years. | 18:44 |
| stephano | LetoThe2nd: Yeah, I realize that poky-tiny needs love. It misses Darren. :) | 18:45 |
| stephano | LetoThe2nd: I'm using musl. Just a vanilla poky master clone. | 18:45 |
| LetoThe2nd | stephano: IIRC even poky master, just switching distro to poky-tiny broke just recently, for a missing kernel (some typo thing) | 18:47 |
| LetoThe2nd | stephano: i'd look at your bsp if it refers to some form of DISTRO specifically. | 18:47 |
| stephano | LetoThe2nd: Okay, will do. | 18:48 |
| LetoThe2nd | stephano: respectively, start with qemu, and only add your bsp if that builds and boots | 18:49 |
| *** Striking7 <Striking7!~jon@96-94-100-129-static.hfc.comcastbusiness.net> has quit IRC | 18:52 | |
| stephano | LetoThe2nd: Will do. The BSP might be meta-intel eventually, but honestly, running out of MinnowBoard flash? Who knows what will work. :) | 18:53 |
| *** Striking7 <Striking7!~jon@96-94-100-129-static.hfc.comcastbusiness.net> has joined #yocto | 18:53 | |
| stephano | LetoThe2nd: We just recently freed up 4mb of flash on the Minnow build, so I figured I'd try to cram Yocto in there. :) | 18:53 |
| stephano | You can do it Poky-Tiny!!! | 18:53 |
| LetoThe2nd | stephano: oh, almost nothing is impossible. but 4mb including a kernel on x86 is a very special kind of fun. on ARM, no big deal. | 18:54 |
| stephano | LetoThe2nd: indeed. I will put my thinking cap on. | 18:59 |
| LetoThe2nd | stephano: have fun, then! | 19:00 |
| *** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has quit IRC | 19:09 | |
| *** jsp973 <jsp973!~jimbo973@159.215.35.1> has quit IRC | 19:10 | |
| stephano | LetoThe2nd: 2.7 tag worked great. :) | 19:12 |
| *** georgem <georgem!~georgem@216.21.169.52> has quit IRC | 19:22 | |
| *** Bunio_FH <Bunio_FH!~bunio@clj-165.netdrive.pl> has joined #yocto | 19:36 | |
| rburton | hey stephano welcome back :) | 19:39 |
| rburton | LetoThe2nd: tiny linux kernel? find tom zanussi :) | 19:40 |
| rburton | erm stephano ^^^ | 19:40 |
| stephano | rburton: Tom! Is he still at Intel, or does he work at VMware now... :p | 19:42 |
| stephano | I never left, I was just sucked into a vortex of conferences. | 19:42 |
| rburton | stephano: i think he is still at intel... | 19:45 |
| rburton | but he can tell you how small a kernel can get with minimal effort, even if the knowledge is a few years stale | 19:45 |
| stephano | rburton, Perfect, thanks! I'll send him an AR. :) | 19:46 |
| *** Dvorkin <Dvorkin!b072cc0c@gateway/web/freenode/ip.176.114.204.12> has quit IRC | 19:49 | |
| stephano | Awww, there's even a video... https://youtu.be/rSaU091gcW8 | 19:50 |
| rburton | there we go :) | 19:50 |
| stephano | Queue Andrew Lloyd Webber's Memories... | 19:50 |
| *** blscoe <blscoe!~Jack___@151.95.140.200> has joined #yocto | 19:54 | |
| blscoe | hi | 19:54 |
| *** Bunio_FH <Bunio_FH!~bunio@clj-165.netdrive.pl> has quit IRC | 19:54 | |
| blscoe | anybody | 19:56 |
| blscoe | yocto is the main oe distro ? | 19:56 |
| *** georgem <georgem!~georgem@216.21.169.52> has joined #yocto | 19:57 | |
| *** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto | 19:59 | |
| blscoe | what kernel does it uses ? | 20:01 |
| JPEW | blscoe: Linux kernel... exact version depends on a lot of factors | 20:02 |
| blscoe | by linux kernel | 20:02 |
| blscoe | you dont mean android kernel right ? | 20:03 |
| JPEW | Err, I'm particularly sure if I can differentiate between them :) The kernel you use is going to largely depend on what hardware you are targeting | 20:04 |
| JPEW | (at least in my expirence) | 20:05 |
| blscoe | shit | 20:05 |
| blscoe | ok | 20:05 |
| blscoe | another question | 20:05 |
| blscoe | whats the default root password ? I have an old password that is oelinux1 | 20:06 |
| blscoe | but doesnt work anymore | 20:07 |
| JPEW | I don't actually know... there might not be one (sometimes root is configured to not allow *any* password login) | 20:09 |
| blscoe | i tryed empty password but no... | 20:10 |
| rburton | blscoe: default password is not set, so you can't actually login. if debug-tweaks was set, then it is empty | 20:19 |
| blscoe | I needoh, and how exactly are you supposed to use ther os ? | 20:20 |
| blscoe | oh, and how exactly are you supposed to use the os ? | 20:20 |
| kergoth | set a r oot password, add a user, or enable debug-tweaks. | 20:21 |
| kergoth | hardcoding a password out of the box is a security flaw | 20:21 |
| blscoe | same fore oe core ? | 20:21 |
| blscoe | same for oe core ? | 20:22 |
| *** learningc <learningc!~learningc@121.121.98.115> has joined #yocto | 20:22 | |
| kergoth | i don't understand the question. | 20:22 |
| kergoth | yocto's buildsystem *is* oe-core, along with a few other bits | 20:22 |
| blscoe | ok | 20:23 |
| blscoe | I need the root password for the quectel EC21 / EC25 | 20:23 |
| blscoe | it used to be oelinux1 , but not anymore | 20:24 |
| rburton | ask quectel? | 20:24 |
| rburton | oe is a tool to build distros | 20:24 |
| rburton | just because the quectel ec21 has a default password of oelinux1 doesn't mean anyone else does | 20:25 |
| blscoe | ok. but someone here may know | 20:27 |
| *** dreyna <dreyna!~dreyna@c-24-5-28-247.hsd1.ca.comcast.net> has quit IRC | 20:29 | |
| *** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has quit IRC | 20:53 | |
| *** diego_r <diego_r!~diego@81.29.205.101> has joined #yocto | 20:54 | |
| *** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has joined #yocto | 20:55 | |
| *** WillMiles <WillMiles!~Will@static-209-87-231-80.storm.ca> has quit IRC | 20:58 | |
| psrcode | when using devtool to upgrade a recipe, what is the best way to handle patches that cannot be applied on the upgraded source? | 21:50 |
| *** diego_r <diego_r!~diego@81.29.205.101> has quit IRC | 21:58 | |
| *** berton_ <berton_!~berton@181.220.86.53> has quit IRC | 22:01 | |
| bluelightning_ | psrcode: it should be a typical git rebase conflict resolution operation | 22:06 |
| psrcode | k, I'm mostly interested in discarding part of the patches | 22:07 |
| psrcode | anyway found another way for now that was a bit less convuluted, will revisit devtool next time | 22:07 |
| RP | psrcode: was meaning to ask you about the lttng-modules patch sitting in -next | 22:08 |
| psrcode | what about them? | 22:09 |
| psrcode | the one for 5.1? | 22:09 |
| psrcode | RP: ^ | 22:11 |
| RP | psrcode: yes, those ones. I'd prefer to have a release to switch to rather than patches I guess :) | 22:13 |
| RP | psrcode: so I guess I'm asking if a release is imminent or whether adding that patch makes sense | 22:13 |
| psrcode | RP: hmmmm, yeah when is the next official release on your side? | 22:14 |
| *** rburton <rburton!~rburton@35.106.2.81.in-addr.arpa> has quit IRC | 22:15 | |
| RP | psrcode: we're on our interim milestone releases. M1 just built, M2 is mid july. Main release October | 22:16 |
| RP | psrcode: I just don't like adding and then removing patches. We may want to consider a git version of lttng-modules people could use instead for new kernels? | 22:16 |
| psrcode | we could probably cut a 2.10.10 patch level release that would include all the fixes (let me double check) | 22:16 |
| RP | If you're using bleeding edge kernels, you probably don't mind a git version of lttng-modules to go with it | 22:17 |
| psrcode | following the stable branch of the 2.X release would make sense | 22:17 |
| psrcode | master also | 22:17 |
| psrcode | actually master would be good | 22:18 |
| psrcode | is there a way to configure wich recipe to take based on the kernel? | 22:18 |
| psrcode | version* | 22:18 |
| *** Crofton|road <Crofton|road!~Crofton@23-25-123-169-static.hfc.comcastbusiness.net> has quit IRC | 22:21 | |
| psrcode | yeah after double checking all proposed patches are in the stable 2.10 branch, I'll check with the maintainer if we can cut a release for you | 22:21 |
| psrcode | but do you plane on moving to 5.2 or higher? because otherwise it is an endless chase ... | 22:22 |
| psrcode | plan* | 22:22 |
| RP | psrcode: This is what worries me. I think adding a git recipe for this reason may be the better answer | 22:24 |
| RP | psrcode: it wouldn't be magic but it would just be a single extra PREFERRED_VERSION setting which people can manage | 22:25 |
| RP | psrcode: I can ask the patch submitter to look at that as an alternative | 22:26 |
| psrcode | would be nice to be able to set a preferred version based on the kernel version chosen, anyway Mathieu is currently looking into cutting the release, should take care of the current patchset | 22:26 |
| psrcode | anyway I got to go, but way git recipe get my +1 | 22:27 |
| psrcode | way -> yeah | 22:27 |
| psrcode | especially for lttng-modules | 22:28 |
| yocti | New news from stackoverflow: include tar.bz image in wic image <https://stackoverflow.com/questions/56552370/include-tar-bz-image-in-wic-image> | 22:30 |
| *** georgem_home <georgem_home!uid210681@gateway/web/irccloud.com/x-apqiakxmuormaxrz> has joined #yocto | 22:36 | |
| *** learningc <learningc!~learningc@121.121.98.115> has quit IRC | 22:38 | |
| *** featherlessbiped <featherlessbiped!836ba0d0@gateway/web/freenode/ip.131.107.160.208> has joined #yocto | 22:39 | |
| featherlessbiped | I'm getting an rpm build error | 22:39 |
| featherlessbiped | is there a way to debug the generated buildspec? | 22:40 |
| featherlessbiped | after I run bitbake | 22:40 |
| RP | psrcode: thanks | 22:45 |
| *** stephano <stephano!stephano@nat/intel/x-ptekjlztcwioncnu> has quit IRC | 22:50 | |
| Tartarus | FWIW, I'm updating and testing a build of current vim now. | 22:57 |
| *** agust <agust!~agust@pD95F1ED1.dip0.t-ipconnect.de> has quit IRC | 23:24 | |
| *** JaMa <JaMa!~martin@ip-217-030-068-212.aim-net.cz> has quit IRC | 23:36 | |
| RP | Tartarus: cool :) | 23:38 |
| *** awe00 <awe00!~awe00@unaffiliated/awe00> has quit IRC | 23:46 | |
| *** geissonator <geissonator!~geissonat@45-18-127-186.lightspeed.austtx.sbcglobal.net> has quit IRC | 23:48 | |
Generated by irclog2html.py 2.11.0 by Marius Gedminas - find it at mg.pov.lt!