Thursday, 2020-04-09

*** pi2 <pi2!> has joined #yocto00:04
*** pi____ <pi____!> has quit IRC00:07
*** maudat <maudat!> has quit IRC00:09
*** pi____ <pi____!> has joined #yocto00:16
*** pi2 <pi2!> has quit IRC00:19
*** vineela <vineela!~vtummala@> has quit IRC00:24
*** vineela <vineela!vtummala@nat/intel/x-gnlebhruceezxwlb> has joined #yocto00:26
*** mischief1 is now known as mischief00:27
*** behanw <behanw!uid110099@gateway/web/> has joined #yocto00:27
*** nerdboy <nerdboy!~sarnold@> has joined #yocto00:32
*** pi2 <pi2!> has joined #yocto00:32
*** nerdboy <nerdboy!~sarnold@> has quit IRC00:32
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has joined #yocto00:32
*** kovalevsky <kovalevsky!~kovalevsk@fedora/kovalevsky> has quit IRC00:34
*** pi____ <pi____!> has quit IRC00:35
*** mauz555 <mauz555!~mauz555@2a01:e0a:56d:9090:dd4:468f:5afc:d70b> has joined #yocto00:36
*** mauz555 <mauz555!~mauz555@2a01:e0a:56d:9090:dd4:468f:5afc:d70b> has quit IRC00:41
*** pi____ <pi____!> has joined #yocto00:43
*** robert_yang <robert_yang!~robert@> has quit IRC00:45
*** robert_yang <robert_yang!~robert@> has joined #yocto00:45
*** meow` <meow`!> has quit IRC00:45
*** pi2 <pi2!> has quit IRC00:47
*** robert_yang <robert_yang!~robert@> has quit IRC00:55
*** robert_yang <robert_yang!~robert@> has joined #yocto00:56
*** pi2 <pi2!> has joined #yocto01:00
alejandrohszeddii: I definitely didnt get the reference01:01
*** pi____ <pi____!> has quit IRC01:03
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has quit IRC01:06
*** pi____ <pi____!> has joined #yocto01:11
*** vineela <vineela!vtummala@nat/intel/x-gnlebhruceezxwlb> has quit IRC01:13
*** pi2 <pi2!> has quit IRC01:14
*** pi2 <pi2!> has joined #yocto01:26
*** nerdboy <nerdboy!~sarnold@> has joined #yocto01:29
*** pi____ <pi____!> has quit IRC01:29
*** nerdboy <nerdboy!~sarnold@> has quit IRC01:29
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has joined #yocto01:29
*** pi____ <pi____!> has joined #yocto01:38
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has quit IRC01:39
*** nerdboy <nerdboy!~sarnold@> has joined #yocto01:40
*** pi2 <pi2!> has quit IRC01:41
*** pi2 <pi2!> has joined #yocto01:54
*** pi____ <pi____!> has quit IRC01:57
*** pi____ <pi____!> has joined #yocto02:06
*** pi2 <pi2!> has quit IRC02:09
*** nerdboy <nerdboy!~sarnold@> has quit IRC02:21
*** pi2 <pi2!> has joined #yocto02:22
*** pi____ <pi____!> has quit IRC02:25
*** ericch <ericch!> has quit IRC02:26
*** pi____ <pi____!> has joined #yocto02:33
*** robert_yang <robert_yang!~robert@> has quit IRC02:33
*** robert_yang <robert_yang!~robert@> has joined #yocto02:34
*** pi2 <pi2!> has quit IRC02:37
zeddiialejandrohs, :D we are a strange bunch up here!02:43
*** pi2 <pi2!> has joined #yocto02:50
*** pi____ <pi____!> has quit IRC02:53
paulgThat damn Phillips dude - wrecking things for Canadians!02:53
paulgcouldn't just stop at contaminating Yocto lists...02:54
*** pi____ <pi____!> has joined #yocto02:56
*** pi2 <pi2!> has quit IRC02:57
*** pi2 <pi2!> has joined #yocto03:01
*** pi____ <pi____!> has quit IRC03:04
*** ssajal <ssajal!> has quit IRC03:12
*** fitzsim <fitzsim!> has quit IRC03:20
*** pi____ <pi____!> has joined #yocto03:33
*** pi2 <pi2!> has quit IRC03:35
*** pi2 <pi2!> has joined #yocto03:48
*** pi____ <pi____!> has quit IRC03:51
*** pi____ <pi____!> has joined #yocto04:00
*** pi2 <pi2!> has quit IRC04:04
*** pi2 <pi2!> has joined #yocto04:16
*** pi____ <pi____!> has quit IRC04:19
*** pi____ <pi____!> has joined #yocto04:28
*** pi2 <pi2!> has quit IRC04:31
*** pi2 <pi2!> has joined #yocto04:32
*** pi____ <pi____!> has quit IRC04:35
*** nerdboy <nerdboy!~sarnold@> has joined #yocto04:41
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has joined #yocto04:41
*** pi____ <pi____!> has joined #yocto04:44
*** pi2 <pi2!> has quit IRC04:47
*** gtristan <gtristan!~tristanva@> has quit IRC04:59
*** pi2 <pi2!> has joined #yocto05:00
*** pi____ <pi____!> has quit IRC05:03
*** cpo <cpo!> has quit IRC05:06
*** pi____ <pi____!> has joined #yocto05:11
*** pi2 <pi2!> has quit IRC05:15
*** cpo <cpo!> has joined #yocto05:17
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC05:19
*** cpo <cpo!> has quit IRC05:22
*** ibinderwolf <ibinderwolf!> has joined #yocto05:23
*** pi2 <pi2!> has joined #yocto05:27
*** pi____ <pi____!> has quit IRC05:30
*** cpo <cpo!> has joined #yocto05:39
*** pi____ <pi____!> has joined #yocto05:39
*** gtristan <gtristan!~tristanva@> has joined #yocto05:40
*** timblechmann <timblechmann!~quassel@> has joined #yocto05:41
*** gtristan <gtristan!~tristanva@> has quit IRC05:42
*** gtristan <gtristan!~tristanva@> has joined #yocto05:42
*** pi2 <pi2!> has quit IRC05:42
*** cpo <cpo!> has quit IRC05:45
*** robert_yang <robert_yang!~robert@> has quit IRC05:47
*** robert_yang <robert_yang!~robert@> has joined #yocto05:47
*** AndersD <AndersD!> has joined #yocto05:49
*** pi2 <pi2!> has joined #yocto05:54
*** cpo <cpo!~cpo@> has joined #yocto05:56
*** pi____ <pi____!> has quit IRC05:58
*** dreyna <dreyna!> has quit IRC05:59
*** dreyna <dreyna!> has joined #yocto05:59
*** pharaon2502 <pharaon2502!> has joined #yocto06:07
*** pi____ <pi____!> has joined #yocto06:07
*** pi2 <pi2!> has quit IRC06:10
*** agust <agust!> has joined #yocto06:10
*** dreyna <dreyna!> has quit IRC06:15
*** pi2 <pi2!> has joined #yocto06:22
*** pi____ <pi____!> has quit IRC06:25
*** guerinoni <guerinoni!> has joined #yocto06:26
*** pohly <pohly!> has joined #yocto06:27
*** pi____ <pi____!> has joined #yocto06:33
*** frsc <frsc!> has joined #yocto06:34
*** timblechmann <timblechmann!~quassel@> has quit IRC06:35
*** dreyna <dreyna!> has joined #yocto06:36
*** robert_yang <robert_yang!~robert@> has quit IRC06:36
*** timblechmann <timblechmann!~quassel@> has joined #yocto06:36
*** robert_yang <robert_yang!~robert@> has joined #yocto06:37
*** pi2 <pi2!> has quit IRC06:37
*** timblechmann <timblechmann!~quassel@> has quit IRC06:45
*** timblechmann <timblechmann!~quassel@2001:e68:5420:af96:a53f:b289:bee:e7b4> has joined #yocto06:47
*** nameclash <nameclash!> has quit IRC06:47
*** pi2 <pi2!> has joined #yocto06:50
*** pi____ <pi____!> has quit IRC06:53
*** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has joined #yocto06:53
*** nameclash <nameclash!> has joined #yocto06:54
*** pi____ <pi____!> has joined #yocto07:01
nameclashgood morning! what is the correct way to install prebuilt binaries into the rootfs without having to deal with auto-detected runtime dependencies?07:02
*** [Sno] <[Sno]!> has quit IRC07:03
*** ebail <ebail!> has joined #yocto07:04
*** pi2 <pi2!> has quit IRC07:04
RobertBerger@nameclash: pebuild packages or just binaries?07:04
nameclashactually it's a directory tree of binaries, cfg etc, so basically a package07:05
*** ebail <ebail!> has quit IRC07:05
RobertBerger@nameclash: hmm but not a .deb .rpm .pkg package?07:06
nameclashit is a 3rd party suite of ui testing tools I built from source07:06
erbonameclash: I'd say to use the bin_package bbclass, and then override RDEPENDS_${PN} to clear it07:06
erbonameclash: If you have the source, why not build it in Yocto though? :)07:07
RobertBerger@nameclash: but this can get tricky ;)07:07
RobertBerger@nameclash: yes exactly, why don't you build it?07:07
nameclashthe project itself is qt based, but they're using their own awesome commercial binary build engine so I had no chance building it from source within yocto07:09
nameclashI tried it but failed miserably07:09
RobertBerger@nameclash: hehe I think I know what stuff you are talking about ;)07:10
nameclashthey're using their own homebrew build system that uses qmake internally and I got stuck somewhere 5 yards before the finish line07:11
nameclashthen I said screw it, just throw in the binaries (can't be that hard, huh?) and then this pesky auto dependency checker got me07:12
RobertBerger@nameclash: if you can bundle it somehow as a package, you could use, as mentioned above, the bin_package class07:12
RobertBerger@nameclash: otherwise you can write your own recipe, which just copies files over where they belong to07:13
nameclashI did that07:13
nameclashbut some of the binaries link againist and bitbake detects that and says I have nothing that provides this07:14
nameclashalthough I have qt-5 in my image07:14
nameclashI dont understand it. but I guess such things may happen if you're not building everything from scratch alltogether07:16
RobertBerger@nameclash: that's a packaging problem07:16
RobertBerger@nameclash: you did not just copy over stuff, I guess, but more in your recipe07:16
*** pi2 <pi2!> has joined #yocto07:17
erboI think the bin_package class handles tarballs as well07:19
erbonameclash: Have you tried just overriding RDEPENDS_${PN} = "" in your recipe?07:19
erboor maybe the autodepenencies are added after reading RDEPENDS?07:20
nameclashfirst, I put those 3rd party sources in a repo and wrote a recipe for it to build it from source. when I got stuck with qmake I gave up and decided to add a tarball with the artifacts I had built by hand and changed the recipe to just untar it in do_install. That gave me a bunch of uid warnings which I didnt like so I unpacked the tarball, put the files in the repo and then just copied them into place in do_install07:20
*** pi____ <pi____!> has quit IRC07:20
RobertBerger@erbo: yes this could be the case.07:21
*** seebs <seebs!~seebs@> has quit IRC07:21
nameclashthat gave me 3 warnings about missing dependencies to, so I INSANE_SKIPPED file-rdeps and that actually made the recipe succeed, but RPM got me on do_rootfs07:21
nameclashthat's the whole story07:22
nameclashI'll try something more now, just came in my mind and then I'll look into the links you sent07:22
nameclashthx guys07:23
nameclashI'll ping back07:23
*** xade <xade!6d58ac23@> has joined #yocto07:23
*** dreyna <dreyna!> has quit IRC07:23
*** xade is now known as xavier_deschuyte07:24
*** dreyna <dreyna!> has joined #yocto07:24
*** [Sno] <[Sno]!> has joined #yocto07:24
xavier_deschuyteHi all, I have an issue with bitbake data store manipulation, here is a minimal example:
*** seebs <seebs!~seebs@> has joined #yocto07:25
*** robert_yang <robert_yang!~robert@> has quit IRC07:26
xavier_deschuytemyfunc task is using setvar and check that it's applied and myfunc2 (another task running after myfunc) is trying to check it. And it's not working, here is the log:
*** robert_yang <robert_yang!~robert@> has joined #yocto07:26
xavier_deschuytemyfunc is "OK" but we see in myfunc2 log that setvar was not correctly applied.07:27
xavier_deschuytemy goal is to modify SUMMARY/DESCRIPTION/PV from git repo files.07:28
xavier_deschuyteAny idea how to fix this?07:28
*** pi____ <pi____!> has joined #yocto07:29
RobertBerger@xavier: Not sure if DESCRIPTION behaves differently from other variables ;)07:30
RobertBergerI would try a non system variable07:30
RobertBergerand I would also try in my task instead of set07:30
RobertBergeror so07:31
RobertBergerdoes this work?07:31
erboI don't think you can modify variables and have it stored between tasks, IIRC07:31
*** pi2 <pi2!> has quit IRC07:32
xavier_deschuyteI tried it with some success with something like this: SUMMARY="${@myfunc(d)}" but it's not "stable"07:32
xavier_deschuyteDepending of the build order/connection speed, sometimes it worked, sometimes not (apparrently bitbake is not expecting variable parsing to take some time)07:33
RobertBergeryou also didn't clearly define what should run first07:33
RobertBergertry _prepend _append07:34
xavier_deschuyteRobertBerger I tried with a non bitbake variable without success: and output
xavier_deschuyteRobertBerger order is defined with addtask isn't it? and it appears to be correctly working and is not the issue here (I can check it with deb package info that is using DESCRIPTION)07:36
RobertBergerwell with before and after07:36
RobertBergerbut that is not precise07:36
RobertBergeryou could try instead of myfunc207:37
RobertBergersorry append07:37
RobertBergerthen the second one will run after the first07:37
*** dreyna <dreyna!> has quit IRC07:37
RobertBergerand take out the second before/after line07:38
erboxavier_deschuyte: I think changes to the datastore is only valid inside the task07:38
xavier_deschuyteRobertBerger even if order issue is not the issue here (you clearly see that myfunc2 is executing after myfunc) so task order is OK. But with your suggestion it's not working neitherrr07:39
xavier_deschuyteerbo : yes that's what I observe here, but that's strange because that's not what the documentation is stating07:39
RobertBergerhehe - let me have a look ;)07:40
*** timblechmann <timblechmann!~quassel@2001:e68:5420:af96:a53f:b289:bee:e7b4> has quit IRC07:42
xavier_deschuyteerbo section 3.5.507:42
*** timblechmann <timblechmann!~quassel@> has joined #yocto07:44
xavier_deschuyteRobertBerger thanks for the help! my goal is to change the DESCRIPTION field of the generated deb. I saw in the package_deb class that it's using getvar.. I assumed that using setvar before would do the trick07:45
*** pi2 <pi2!> has joined #yocto07:45
RobertBergerI am busy right now, but will definitely try to see what's going on on my mission to demystify bitbake ;)07:46
RobertBergerso I am collecting such things and solutions to it07:46
RobertBergerWhy don't you just write DESCRIPTION="das;dkas;ldk" in your recipe?07:46
erboxavier_deschuyte: yeah I recall having troubles finding this info too. And regarding the anonymous function, maybe those can modify but not regular tasks07:46
xavier_deschuyteerbo yes, anonymous is working as described. But then, I am facing issue with the bitbake task scheduler (because I need to access git files, I need to fetch/unpack and it takes time and apparentlty parsing is not supposed to "take time"07:48
*** pi____ <pi____!> has quit IRC07:48
xavier_deschuyteRobertBerger : because basically I want to set description with a git file content07:48
RobertBergerOK an addition issue ;)07:49
*** LocutusOfBorg <LocutusOfBorg!~LocutusOf@ubuntu/member/locutusofborg> has joined #yocto07:50
*** pi____ <pi____!> has joined #yocto07:56
xavier_deschuyteI suppose that python tasks receive a "copy" of the global context. Would be nice to get a way to access global context07:57
*** pi2 <pi2!> has quit IRC08:00
*** mckoan|away is now known as mckoan08:00
xavier_deschuyteOK. By putting logs in a python anonymous function. I understood my issue: each bitbake task trigger a recipe parsing. So I assume my setvar is working but is wiped by the next recipe parsing08:05
*** yann|work <yann|work!> has joined #yocto08:05
paulbarkerxavier_deschuyte: Each task has it's own context. Are you trying to set a value in one task and then get it in another task?08:07
xavier_deschuyteHere is an example: producing
*** yann <yann!> has quit IRC08:07
paulbarkerxavier_deschuyte: It's not technically parsing, more like execution of the code that was already parsed08:08
xavier_deschuytepaulbarker my goal is to set deb package attribute (DESCRIPTION for example). So without modifying bitbake files, only my recipe.08:08
paulbarkerWhat do you mean by "bitbake files"08:09
paulbarkerI'd recommend avoiding package_deb and using either ipk or rpm packages instead as they're much better supported08:10
xavier_deschuytepaulbarker I need to get deb packages (I generate an APT repository)08:11
qschulzCan someone shine a light on the use of LICENSE_EXCLUSION in base.bbclass? It is only used in package.bbclass and the logic is broken for multilib so I'd like to fix it. The easiest is just to axe it but mmmm maybe there's a reason :) ?08:12
xavier_deschuyteand using rpm, ipk or whatever would not fix my issue. I need to set a bitbake variable from a git file08:12
*** pi2 <pi2!> has joined #yocto08:13
paulbarkerxavier_deschuyte: I don't know any way to do that neatly, you may be better off asking in an email to the list08:14
*** pi____ <pi____!> has quit IRC08:16
*** robert_yang <robert_yang!~robert@> has quit IRC08:16
xavier_deschuytepaulbarker I double checked my test and I think your solution could be the correct one "append/prepend".08:17
*** robert_yang <robert_yang!~robert@> has joined #yocto08:17
xavier_deschuyteBut in fact when I said it was not "working" digging into that means it was simply not executed08:17
xavier_deschuyteI simply declare the task this way: `python do_myfunc_append() {`08:17
xavier_deschuytebut it is not executed08:18
*** timemaster5 <timemaster5!> has quit IRC08:18
xavier_deschuytebut I hope that prepend/append are executing without "reparsing" and so context would be the same and it would work08:19
paulbarkerprepend/append fragments are joined together before the code is executed so that should work08:19
xavier_deschuytebut my syntax is not working08:20
paulbarkerLet me check quickly08:20
*** radsquirrel <radsquirrel!> has quit IRC08:21
xavier_deschuyteI used that: `do_myfunc[postfuncs] += "do_myfunc_append"` that did the trick and context is preserved but would be interrested to fix it with append/prepend08:22
paulbarkerWhat's that `BB_DONT_CACHE` doing there?08:22
xavier_deschuytejust a test... I was afraid that bitbake was "caching parsing" of summary or similar08:22
xavier_deschuytebut it's not the issue here08:22
*** pi__ <pi__!> has joined #yocto08:24
*** yann|work <yann|work!> has quit IRC08:27
paulbarkerxavier_deschuyte: Your append should work. Check what appears in `tmp/work/<arch>/<pkg>/<version>/temp/run.do_myfunc`08:27
*** pi2 <pi2!> has quit IRC08:27
*** timblechmann <timblechmann!~quassel@> has quit IRC08:27
*** timblechmann <timblechmann!~quassel@> has joined #yocto08:29
qschulzugh... it seems I can't fix my multilib issue without breaking something else.... Will open a bug then :/08:34
paulbarkerqschulz: 99 little bugs in the code, 99 little bugs in the code. Take one down, patch it around, 117 little bugs in the code08:35
*** kroon <kroon!~kroon@> has joined #yocto08:35
qschulzpaulbarker: but it's kinda of an issue. I fall in a side effect of PACKAGES having lib32- prepended later than LICENSE_EXCLUSION being computed. If I fix that, all packages depending on this side effect will actually break and there are more than the one impacted by the current behavior....08:37
paulbarkerqschulz: ouch08:37
qschulzpaulbarker: yeah you don't say :)08:38
*** yann|work <yann|work!> has joined #yocto08:39
*** timblechmann <timblechmann!~quassel@> has quit IRC08:39
*** pi2 <pi2!> has joined #yocto08:40
*** timblechmann <timblechmann!~quassel@> has joined #yocto08:40
*** AndersD <AndersD!> has quit IRC08:42
*** radsquirrel <radsquirrel!> has joined #yocto08:43
*** pi__ <pi__!> has quit IRC08:44
*** gtristan <gtristan!~tristanva@> has quit IRC08:47
*** T_UNIX <T_UNIX!uid218288@gateway/web/> has joined #yocto08:48
*** pi__ <pi__!> has joined #yocto08:52
*** pi2 <pi2!> has quit IRC08:55
*** timblechmann <timblechmann!~quassel@> has quit IRC08:59
*** timblechmann <timblechmann!~quassel@> has joined #yocto09:01
*** rburton <rburton!~rburton@> has joined #yocto09:01
*** leon-anavi <leon-anavi!~Leon@> has joined #yocto09:08
*** pi2 <pi2!> has joined #yocto09:08
*** robert_yang <robert_yang!~robert@> has quit IRC09:09
*** robert_yang <robert_yang!~robert@> has joined #yocto09:09
*** pi__ <pi__!> has quit IRC09:12
*** florian <florian!~florian_k@Maemo/community/contributor/florian> has joined #yocto09:17
*** pi__ <pi__!> has joined #yocto09:19
*** pi2 <pi2!> has quit IRC09:23
*** timblechmann <timblechmann!~quassel@> has quit IRC09:25
*** timblechmann <timblechmann!~quassel@> has joined #yocto09:27
*** pi2 <pi2!> has joined #yocto09:36
*** goliath <goliath!> has joined #yocto09:37
*** AndersD <AndersD!> has joined #yocto09:38
*** pi__ <pi__!> has quit IRC09:38
*** AndersD_ <AndersD_!> has joined #yocto09:40
*** florian_kc <florian_kc!~florian_k@Maemo/community/contributor/florian> has joined #yocto09:42
*** AndersD <AndersD!> has quit IRC09:43
*** pi__ <pi__!> has joined #yocto09:47
*** robert_yang <robert_yang!~robert@> has quit IRC09:47
*** robert_yang <robert_yang!~robert@> has joined #yocto09:48
*** pi2 <pi2!> has quit IRC09:50
*** timblechmann <timblechmann!~quassel@> has quit IRC09:57
*** timblechmann <timblechmann!~quassel@> has joined #yocto09:58
*** timemaster5 <timemaster5!> has joined #yocto10:00
xavier_deschuytepaulbarker : prepend is not working neither for my specific case because deb package generation uses "execs" so I am trying right now to put a task after the deb build to edit the control file. Not that ugly in the end.10:02
*** pi2 <pi2!> has joined #yocto10:02
*** pi__ <pi__!> has quit IRC10:06
*** timblechmann <timblechmann!~quassel@> has quit IRC10:11
*** bradfa <bradfa!uid297668@gateway/web/> has joined #yocto10:11
*** pi__ <pi__!> has joined #yocto10:15
*** timblechmann <timblechmann!~quassel@> has joined #yocto10:18
*** pi2 <pi2!> has quit IRC10:18
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has quit IRC10:19
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto10:21
*** pi2 <pi2!> has joined #yocto10:30
*** x7777 <x7777!c01922c2@> has joined #yocto10:30
*** pi__ <pi__!> has quit IRC10:33
*** timblechmann <timblechmann!~quassel@> has quit IRC10:34
*** timblechmann <timblechmann!~quassel@> has joined #yocto10:35
x7777Hi guys. Im building poky 3.0.2 with meta-raspberrypi and targetting raspberrypi4-64. Any idea why my TARGET_FPU is empty? Machine raspberrypi4-64 uses tune-cortexa72 from OE. if I understood correctly, cortex-a72 should have vfpv4 support?10:38
qschulzpaulbarker: if you're interested:
yoctiBug 13865: critical, Undecided, ---, unassigned, NEW , mutlilib results in, if package has incompatible license, pulled in rootfs or if package has compatible license, blacklisted from RDEPENDS/rootfs10:42
*** pi__ <pi__!> has joined #yocto10:42
*** pi2 <pi2!> has quit IRC10:45
qschulzHopefully I'm not drowning people in details in this issue, I've been pretty bad lately at explaining things. Let me know if there is some rephrasing to do :)10:47
*** pi2 <pi2!> has joined #yocto10:58
*** pi__ <pi__!> has quit IRC11:01
*** timblechmann <timblechmann!~quassel@> has quit IRC11:10
*** timblechmann <timblechmann!~quassel@> has joined #yocto11:10
*** pi__ <pi__!> has joined #yocto11:10
*** pi2 <pi2!> has quit IRC11:13
RPqschulz: that bug sounds horrible :(11:18
paulbarkerqschulz: Overly detailed bugreports are much better than missing out some details11:18
* RP wishes we could just drop multilibs and imcompaible_license11:18
qschulzRP: yeah, I'm sorry, always me finding out the weird licenses corner cases :/11:19
qschulzRP: honestly, if we can ditch LICENSE_EXCLUSION in base.bbclass without any repercussion, I think it should be possible to handle the packaging blacklist directly in package.bbclass. It's just that I'm not sure there isn't something I'm missing :/11:21
paulbarkerRP, qschulz: The way LICENSE_EXCLUSION is used does look really messy. I'm happy to take that bug and see if I can come up with a better way of doing it. No guarantees I'll get to it for a week or three though11:22
*** pi2 <pi2!> has joined #yocto11:25
*** berton <berton!~berton@> has joined #yocto11:28
*** pi__ <pi__!> has quit IRC11:28
*** comptroller <comptroller!> has quit IRC11:29
*** berton <berton!~berton@> has quit IRC11:36
*** pi__ <pi__!> has joined #yocto11:37
*** berton <berton!~berton@> has joined #yocto11:37
qschulzpaulbarker: wait for the goodies, I forgot to add some info to the bug11:37
*** pi2 <pi2!> has quit IRC11:39
yoctiNew news from stackoverflow: Why would a yocto patch fail under devtool but not during a normal build? <>11:42
*** timblechmann <timblechmann!~quassel@> has quit IRC11:50
*** timblechmann <timblechmann!~quassel@2001:e68:5420:af96:a53f:b289:bee:e7b4> has joined #yocto11:51
*** pi2 <pi2!> has joined #yocto11:53
*** pi__ <pi__!> has quit IRC11:56
*** timblechmann <timblechmann!~quassel@2001:e68:5420:af96:a53f:b289:bee:e7b4> has quit IRC11:59
*** timblechmann <timblechmann!~quassel@> has joined #yocto11:59
*** pi__ <pi__!> has joined #yocto12:04
*** pi2 <pi2!> has quit IRC12:07
*** x7777 <x7777!c01922c2@> has quit IRC12:17
*** gtristan <gtristan!~tristanva@> has joined #yocto12:20
*** pi2 <pi2!> has joined #yocto12:21
*** pi__ <pi__!> has quit IRC12:23
*** kovalevsky <kovalevsky!~kovalevsk@> has joined #yocto12:28
*** kovalevsky <kovalevsky!~kovalevsk@fedora/kovalevsky> has joined #yocto12:28
*** nameclash <nameclash!> has quit IRC12:29
*** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has quit IRC12:31
*** nameclash <nameclash!> has joined #yocto12:32
*** pi__ <pi__!> has joined #yocto12:32
*** pi2 <pi2!> has quit IRC12:35
*** fitzsim <fitzsim!> has joined #yocto12:36
*** Guest5253 <Guest5253!a5e14925@gateway/web/cgi-irc/> has joined #yocto12:49
*** Guest5253 is now known as PatrickE12:49
*** meow` <meow`!> has joined #yocto13:04
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC13:09
*** nhartman1 <nhartman1!> has joined #yocto13:12
nhartman1Has anyone had any luck importing a .wic.vmdk to EC2? Annoyingly, they only allow a select subset of OSs13:17
*** pi__ <pi__!> has quit IRC13:21
*** ericch <ericch!> has joined #yocto13:26
*** kpo__ <kpo__!4e09039d@gateway/web/cgi-irc/> has joined #yocto13:28
*** ecdhe <ecdhe!~quassel@unaffiliated/ecdhe> has quit IRC13:30
*** geheimnis` <geheimnis`!~geheimnis@> has quit IRC13:32
*** geheimnis` <geheimnis`!~geheimnis@> has joined #yocto13:40
*** mrc3 <mrc3!~mrc3@linaro/mrc3> has quit IRC13:42
*** ssajal <ssajal!> has joined #yocto13:52
*** mrc3 <mrc3!~mrc3@linaro/mrc3> has joined #yocto13:55
khemRP: the musl multilib v2 change I sent lets not consider it, its too close to release14:00
khemRP: secondly, the change you are proposing is going to disable a valid usecase ( 64bit kernel + 32bit userspace-only ) which can be built today for musl bitbake lib32-core-image-minimal14:02
khemRP: so I think if you turn this into a parse warning like we have musl+systemd then perhaps that will be idea14:02
*** comptroller <comptroller!> has joined #yocto14:03
*** kroon <kroon!~kroon@> has quit IRC14:05
*** PatrickE <PatrickE!a5e14925@gateway/web/cgi-irc/> has quit IRC14:08
xavier_deschuytepaulbarker : I managed to get my stuff done by creating a new task after deb creation that modify the control file inside it and replace Description. Not the cleanest stuff, but "OK"14:16
*** ecdhe <ecdhe!~quassel@unaffiliated/ecdhe> has joined #yocto14:17
*** mauz555 <mauz555!~mauz555@2a01:e0a:56d:9090:85ad:d670:765f:ee45> has joined #yocto14:22
*** dmoseley <dmoseley!~dmoseley@> has quit IRC14:24
*** armpit <armpit!> has quit IRC14:27
*** T_UNIX <T_UNIX!uid218288@gateway/web/> has quit IRC14:27
*** mauz555 <mauz555!~mauz555@2a01:e0a:56d:9090:85ad:d670:765f:ee45> has quit IRC14:29
*** emrius <emrius!> has joined #yocto14:34
nameclashhow do I properly set up a recipe that uses qmake?14:38
qschulznameclash: inherit qmake should be a good start (I don't know much more :) )14:39
*** AndersD_ <AndersD_!> has quit IRC14:39
nameclashI have TOOLCHAIN_HOST_TASK_append = nativesdk-packagegroup-qt5-toolchain-host which makes qmake and the mkspecs available in the sysroot-native14:40
nameclashIn the recipe I depend on qtbase-native and the recipe's sysroot gets populated with qmake, however when I try to run ${WORKDIR}/recipe-sysroot-native/usr/bin/qt5/qmake in do_configure(), qmake complains not being able to find its specs...14:42
emriusHey, just to confirm: I'm experimenting with a different kernel version. Thus I changed `PREFERRED_PROVIDER_virtual/kernel` and `PREFERRED_VERSION_linux-mainline` and then started rebuild with bitbake. It seems to kick off linux-mainline kernel compilation but only at task 5600 (plus/minus) of 5944. I would have expected that a change of the kernel14:43
emriuswould require a much deeper recompilation of dependencies...14:43
nameclashqschulz I'll look into that, thanks14:43
emriusDo I have to enforce recompilation or something?14:43
qschulzemrius: not really, mostly kernel modules and the image depends on the kernel sources IIRC. Anything that needs header files from the linux kernel are taken from linux-libc-headers14:44
emriusqschulz great! Thanks for the quick reply14:44
rburtonnameclash: TOOLCHAIN_HOST_TASK etc is pointless and meaningless in a normal recipe.  you just want inherit qmake.14:49
rburtonsorry, inherit qmake514:49
nameclashrburton, thanks14:50
rburtonTOOLCHAIN_* are all about controlling what goes into the SDK14:51
rburtonif you can share where you thought that would be the solution then maybe we can ensure the docs are not misleading14:51
nameclashok and that's implicitly handled by inherit qmake5 I guess14:51
rburtonjust read the class: it adds depends and defines configure/compile/install tasks14:51
rburtonif you're talking recipes you are *not* using a SDK14:52
nameclashthat makes sense14:53
nameclashwith that information, and looking into the qmake classes I think I should inherit qmake5_base, not qmake514:54
nameclashthe project that I'm trying to build uses its own configure script to setup the build14:54
nameclashit expects the path to qmake be passed as argument14:55
nameclashso I need to override the tasks defined in qmake514:55
*** lucaceresoli <lucaceresoli!> has joined #yocto15:00
*** dmoseley <dmoseley!~dmoseley@> has joined #yocto15:00
emriusSo, after changing the kernel version bitbake started to compile as expected but ran into a problem. The `package-core-boot` still requires the previous kernel version. Do I have to modify that recipe or is maybe some cache dirty or something else?15:12
emriusThe interested reader may also consult my issue on SO :)
yoctiNew news from stackoverflow: Upgrade yocto linux kernel fails <>15:13
*** mauz555 <mauz555!~mauz555@2a01:e0a:56d:9090:85ad:d670:765f:ee45> has joined #yocto15:14
*** florian_kc <florian_kc!~florian_k@Maemo/community/contributor/florian> has quit IRC15:15
*** rburton <rburton!~rburton@> has quit IRC15:16
*** mauz555 <mauz555!~mauz555@2a01:e0a:56d:9090:85ad:d670:765f:ee45> has quit IRC15:20
*** uhaider <uhaider!sid307926@gateway/web/> has quit IRC15:21
*** ibinderwolf <ibinderwolf!> has quit IRC15:23
qschulzemrius: bitbake packagegroup-core-boot -e | less15:24
qschulzif that works, try to find where kernel-image-4.19.63 is coming from15:25
*** xtron <xtron!> has joined #yocto15:27
emriusqschulz thanks again! I'm on it... but actually it looks fine.15:30
emriusJust to make sure. There are two places a hint on the kernel version 4.19% pops up in the environment.15:31
emriusIt looks about like this:15:31
emrius#   set? /home/marius/mender-qemu-warrior/build/../sources/meta-sunxi/conf/machine/include/     "4.19%"15:31
emriusgrr.... hang on15:32
emriusDo I interprete the questionmark behind set correctly as: "Set the value if it hasn't been set before?15:33
qschulzemrius: yes, ??= is weaker than ?= which is weaker than =15:34
emriusI think the place above where the version also appears basically is the same command:
qschulzemrius: that was not my original question, let me rephrase15:36
emriusqschulz ok, as I thought then. those are the only two places that kernel version appears in `bitbake packagegroup-core-boot -e | less`15:36
qschulzemrius: package-group-boots is requiring kernel-image-15:36
qschulzso it has to come from somewhere15:36
emriusah alright. Now I got it15:36
qschulzwhich variable holds kernel-image that is used in packagegroup-core-boot15:36
emriusthanks. I'll dig into that...15:36
emriusSo, there is `IMAGE_INSTALL=" kernel-image kernel-devicetree  networkmanager networkmanager-nmtui mender"` and `MACHINE_ESSENTIAL_EXTRA_RDEPENDS=" kernel-image kernel-devicetree"` ... *scratching head*15:38
*** armpit <armpit!~armpit@2601:202:4180:a5c0:d419:c81:2767:b4e0> has joined #yocto15:38
RPkhem: I agree, your v2 change can be for 3.2? For 3.1 its probably too late to do anything15:39
emriusmmm... What can I do with that information? Sorry for asking potentilly silly questions... I'm a little lost :/15:40
qschulzemrius: did you actually run bitbake -e packagegroup-core-boot or bitbake -e myimage?15:41
qschulzemrius: I don't know what I'm doing as well, just looking for leads :)15:41
emrius`MACHINE=opi-zero-adxl bitbake packagegroup-core-boot -e | less` that one15:41
qschulzand you have IMAGE_INSTALL there?15:42
emriusqschulz I'm pretty sure you know much better what you are doing than I what I am doing :)15:42
emriusoeehm yes...15:43
emriusno good?15:43
qschulzwait... are you setting your IMAGE_INSTALL in local.conf?15:46
qschulzemrius: where is IMAGE_INSTALL coming from? (read the few lines above the line starting with IMAGE_INSTALL). Most prob not the issue but i'm curious now :)15:48
emriusI define an image the inherits core-image. Its coming in there:
emriusI think I followed one of the live coding sessions from LetoThe2nd there. But I'm not 100% sure anymore... Lots of trying ...15:51
*** dreyna <dreyna!> has joined #yocto15:51
qschulzno, in bitbake -e packagegroup-core-boot | less, I don't have it15:52
emriusOk. That's good to know! At least I know now that it shouldn't be in there15:53
qschulzWell I don't know, that's why I'm asking :)15:54
*** florian <florian!~florian_k@Maemo/community/contributor/florian> has quit IRC15:54
emriusThe problem might just have vanished. Besides the image recipe I had another one (under a different name) with some other features. I just deleted that and the compilation finished... `IMAGE_INSTALL` is still in there btw :)15:56
* qschulz shrugs15:56
emriusProbably something got tainted from there. A little unsatisfying not to understand where it came from. But at least it seems to be cured now.15:56
qschulzcan you give me the lines above IMAGE_INSTALL15:56
emriussure one sec15:57
emriusof the recipe or the environemtn?15:57
qschulzbitbake -e packagegroup-core-boot you said there is an IMAGE_INSTALL in there15:57
emriusyes. Ok15:58
qschulzand FYI, you might want to create your own machine inherit the Allwinner one you're building now where you would set mahcine specific variables instead of in local.conf, for example PREFERRED_PROVIDER_virtual/kernel and PREFERRED_VERSION_linux-mainline :)15:59
*** guerinoni <guerinoni!> has quit IRC15:59
emriusI actually have that. The machine is `MACHINE=opi-zero-adxl`15:59
emriusI just tested in local.conf. Once things work there I usually deploy them elsewhere15:59
qschulzgreat! remove the IMAGE_INSTALL from that machine then :)16:00
qschulzmmmm nevermind, it seems to be in the official example in the docs... Weird16:01
emriusokay. hmm... alright... I figured that was kinda important to have there. But probably I just copy pasted something from somewhere else :/16:01
emriusOk. I probably have it from there when :)16:02
emriusAnyway. I removed it. It compiles just fine. All good :)16:02
qschulzI'd have thought MACHINE_ESSENTIAL_EXTRA_RDEPENDS or something was more the way to go but it seems I've missed something :)16:02
emriusThanks a lot for your time!!! I'll add you on my "people I owe beer when they are in Berlin" list with a second dash (y)16:03
qschulzemrius: the line you had for kernel-image and kernel-devicetree is to install the kernel and the devicetree in the rootfs (most likely in/boot)16:03
emriusah ok16:03
qschulzemrius: my pleasure, I hope it's not crazy in Berlin right now. Take care. Week-end for me. Happy easter for those who're celebrating/having the day off.16:04
emriusWell, it's alright here. I'm just gonna work till end of easter. It's basically the most exiting thing to do at the moment here. Everything is closed.16:04
*** mckoan is now known as mckoan|away16:05
emriusand then continue working...16:05
emriusEnjoy easter and weekend!16:05
*** pharaon2502 <pharaon2502!> has quit IRC16:05
*** khem <khem!~khem@unaffiliated/khem> has quit IRC16:06
emriusBTW: I actually had commented the `IMAGE_INSTALL_append` line in my machine configuration as follows: `# Is the following configuration best placed here?`16:07
emriusThe obvious answer is `No` =D16:07
*** vineela <vineela!vtummala@nat/intel/x-nptvhhlzsogrfdtn> has joined #yocto16:09
nameclashalmost there with the build but qmake still not able to find linux-oe-g++ config16:11
nameclashall relevant paths for qmake seem to be written by qmake5_base to a qmake config file with the path to it exposed as OE_QMAKE_QTCONF_PATH16:12
*** Spock_ncc1701 <Spock_ncc1701!~Spock_ncc@> has joined #yocto16:12
nameclashhowever, I'm not sure how to pass this config file to qmake...16:13
nameclashI've uploaded some additional info on it:16:14
nameclashmy recipe:
nameclashthe bitbake error:
nameclashthe output of the built projects configure script (includes qmake output):
nameclashany pointers on how to pass OE_QMAKE_QTCONF_PATH to qmake highly appreciated16:15
*** emrius <emrius!> has quit IRC16:18
*** khem <khem!~khem@unaffiliated/khem> has joined #yocto16:24
*** ssajal <ssajal!> has quit IRC16:26
*** ssajal <ssajal!> has joined #yocto16:26
*** mamadeus <mamadeus!~mamadeus@> has joined #yocto16:27
*** gtristan <gtristan!~tristanva@> has quit IRC16:28
*** mamadeus_ <mamadeus_!~mamadeus@> has joined #yocto16:29
*** mamadeus <mamadeus!~mamadeus@> has quit IRC16:32
*** locutus_ <locutus_!~LocutusOf@> has joined #yocto16:36
*** LocutusOfBorg <LocutusOfBorg!~LocutusOf@ubuntu/member/locutusofborg> has quit IRC16:38
*** mamadeus__ <mamadeus__!~mamadeus@> has joined #yocto16:42
*** mamadeus_ <mamadeus_!~mamadeus@> has quit IRC16:44
*** frsc <frsc!> has quit IRC16:47
*** frsc <frsc!> has joined #yocto16:50
*** mauz555 <mauz555!~mauz555@2a01:e0a:56d:9090:85ad:d670:765f:ee45> has joined #yocto16:50
*** Bunio_FH <Bunio_FH!> has quit IRC16:51
*** mauz555 <mauz555!~mauz555@2a01:e0a:56d:9090:85ad:d670:765f:ee45> has quit IRC16:52
*** frsc <frsc!> has quit IRC16:54
*** mamadeus_ <mamadeus_!~mamadeus@> has joined #yocto16:54
*** Bunio_FH <Bunio_FH!> has joined #yocto16:56
*** mamadeus__ <mamadeus__!~mamadeus@> has quit IRC16:57
*** rburton <rburton!~rburton@> has joined #yocto16:59
*** gtristan <gtristan!~tristanva@> has joined #yocto16:59
*** mamadeus_ <mamadeus_!~mamadeus@> has quit IRC17:00
*** mauz555 <mauz555!~mauz555@2a01:e0a:56d:9090:85ad:d670:765f:ee45> has joined #yocto17:13
*** Spock_ncc1701 <Spock_ncc1701!~Spock_ncc@> has quit IRC17:14
*** nerdboy <nerdboy!~sarnold@> has joined #yocto17:23
*** sagner <sagner!~ags@2a02:169:3df5::edf> has quit IRC17:25
*** nerdboy_ <nerdboy_!~sarnold@> has joined #yocto17:27
*** nerdboy <nerdboy!~sarnold@> has quit IRC17:27
*** paulg_ <paulg_!> has joined #yocto17:31
*** nerdboy_ <nerdboy_!~sarnold@> has quit IRC17:31
*** nerdboy_ <nerdboy_!~sarnold@> has joined #yocto17:35
*** nerdboy_ <nerdboy_!~sarnold@> has quit IRC17:35
*** nerdboy <nerdboy!~sarnold@> has joined #yocto17:36
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has joined #yocto17:36
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has quit IRC17:46
*** vineela <vineela!vtummala@nat/intel/x-nptvhhlzsogrfdtn> has quit IRC17:49
*** lucaceresoli <lucaceresoli!> has quit IRC17:53
*** xtron <xtron!> has quit IRC17:53
*** leon-anavi <leon-anavi!~Leon@> has quit IRC17:53
*** timblechmann <timblechmann!~quassel@> has quit IRC17:55
*** timblechmann <timblechmann!~quassel@> has joined #yocto17:55
*** locutus_ <locutus_!~LocutusOf@> has quit IRC18:02
*** timblechmann <timblechmann!~quassel@> has quit IRC18:04
*** LocutusOfBorg <LocutusOfBorg!~LocutusOf@ubuntu/member/locutusofborg> has joined #yocto18:04
*** timblechmann <timblechmann!~quassel@> has joined #yocto18:05
*** vineela <vineela!vtummala@nat/intel/x-xqztpbsqetucxsru> has joined #yocto18:11
*** xyzzy42 <xyzzy42!> has joined #yocto18:17
xyzzy42Is it possible to use SYSTEMD_SERVICE_${PN} to enable a service provided by another package?18:18
*** nerdboy <nerdboy!~sarnold@> has joined #yocto18:18
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has joined #yocto18:18
xyzzy42For example, if all users of a package do not necessarily enable to the service in the same way.18:19
*** timemaster5 <timemaster5!> has quit IRC18:36
zeddiixyzzy42. you could hack it into local.conf, but you can always bbappend the recipe in your layer and enable what you want.18:40
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has quit IRC18:40
*** tomjose <tomjose!~tomjose@> has quit IRC18:40
xyzzy42zeddii, so only a recipe which provides the service file is allowed to enable it?18:42
yoctiNew news from stackoverflow: Hardware acceleration RPI4 FFmpeg <>18:43
*** timemaster5 <timemaster5!> has joined #yocto18:43
*** mauz555 <mauz555!~mauz555@2a01:e0a:56d:9090:85ad:d670:765f:ee45> has quit IRC18:45
*** anoo1 <anoo1!~anoo1@> has quit IRC18:47
*** robert_yang <robert_yang!~robert@> has quit IRC18:47
*** robert_yang <robert_yang!~robert@> has joined #yocto18:48
*** anoo1 <anoo1!~anoo1@> has joined #yocto18:49
zeddiixyzzy42, it's a recipe variable like anything else.18:49
zeddiiso correct, you can't cross the boundry to muck in one recipe/package from another.18:50
xyzzy42zeddii, it's not the variable's scope in the recipe, but finding the service file18:50
xyzzy42zeddii, e.g., contains SYSTEMD_SERVICE_foo += "bar.service"18:50
zeddiistill a variable18:51
xyzzy42suppose bar.service is not a file provided by, but by bar.bb18:51
zeddiithen you've got some messed up packaging18:51
zeddiiif you are trying to provide service files for another recipe/packages from another.18:52
xyzzy42but beyond that, it appears it can't be done18:52
xyzzy42building foo will complain that it can't fine bar.service18:53
zeddiiright, because it is looking in its own sysroot for it.18:53
xyzzy42and adding bar to DEPENDS should/will put the bar.service file in the sysroot18:53
*** xtron <xtron!> has joined #yocto18:54
zeddiionly if you deploy it from that dependent recipe (and have it in a installed directory that is deployed). You can find the list of directories that are put into the recipe specific sysroot via DEPENDS in the code itself, or docs. I don't recall them all off the top of my head.18:55
xyzzy42and in the end, what happens is the foo package postinst script will call "systemctl enable bar.service", which will work perfectly well, provided it has the rdepends to ensure bar is installed18:55
*** xtron <xtron!> has quit IRC18:55
*** anoo1 <anoo1!~anoo1@> has quit IRC18:56
xyzzy42I see the file in tmp/work/arch/foo/version/recipe-sysroot/lib/systemd/system/bar.service18:57
xyzzy42so it seems like it is in the sysroot, no?18:57
*** amaury_d <amaury_d!> has quit IRC18:57
*** nerdboy_ <nerdboy_!~sarnold@> has joined #yocto18:57
zeddiiyep, but if you want to package it in that 2nd recipe, you have to copy it, and make sure it is packaged so the ontarget enable will have it.18:58
xyzzy42oh no, I don't want to package it.  Just enable it.18:58
zeddiiwell, the .service file has to end up on the target. I'd not recommend providing it in one package and enabling it in the other.18:59
xyzzy42why not, if the package which enables it depends on the one that provides it (because it uses the service)18:59
xyzzy42the service is a templated service, so the provider of the service is basically saying you can enable this in different ways and it's not my job to figure them out.19:00
zeddiiyou are splitting the logic over multiple recipes, you can do whatever you want, I'm just saying that it might bite you later.19:00
*** timblechmann <timblechmann!~quassel@> has quit IRC19:00
zeddiiyou really should have a distro feature, or similar to control coordinated efforts like that.19:01
zeddiithe yocto mega manual should cover some of this. but again, you can do whatever you want, but expect to have to work around the default way that the build and classes work, since that isn't the normal the case.19:01
zeddiior watch some of LetoThe2nd's youtube things, he goes over some of those concepts IIRC.19:02
*** nerdboy_ <nerdboy_!~sarnold@> has quit IRC19:02
*** timemaster5 <timemaster5!> has quit IRC19:02
xyzzy42what I'd like to be able to do is choose what interfaces a templated service is started on.  Kind of the whole point of templated services is you don't need to know when you create the service what it might get attached to.19:02
*** timblechmann <timblechmann!~quassel@> has joined #yocto19:02
xyzzy42so I'd to be able to have one image that enables interface X, but another image that does not enable it19:03
xyzzy42if I make a debug-mode package, which has the "systemctl enable debug-service@ttyS1.service" postint, then I can include or not include that package in an image19:04
xyzzy42I think this is really the main idea behind templated unit files.  If we knew exactly what bar@.service would be enabled for when we built bar, we'd just hardcode %i in bar.service19:06
xyzzy42but we don't want the restriction, so we create bar@.service which uses %i, and let someone else enable bar@instance.service to provide the value(s).19:07
*** timemaster5 <timemaster5!> has joined #yocto19:09
xyzzy42zeddii, regardless of the should or why, it doesn't appear to be possible, even if the service is in the sysroot, as only services deployed by the recipe are allowed.19:11
*** anoo1 <anoo1!~anoo1@> has joined #yocto19:12
zeddiiright. I can't say that I know the systemd bbclass really well, but right, it will only look in specific directories for the service files. you'd need to modify it, add your own task, or otherwise, augment it to look in that sysroot directory to find and generate the ontarget snippet.19:14
zeddiigotta bolt for coffee. good luck!19:15
*** locutus_ <locutus_!~LocutusOf@> has joined #yocto19:17
*** bradfa <bradfa!uid297668@gateway/web/> has quit IRC19:18
*** anoo1 <anoo1!~anoo1@> has quit IRC19:19
*** LocutusOfBorg <LocutusOfBorg!~LocutusOf@ubuntu/member/locutusofborg> has quit IRC19:19
*** nerdboy_ <nerdboy_!~sarnold@> has joined #yocto19:25
*** nerdboy_ <nerdboy_!~sarnold@> has quit IRC19:26
*** nerdboy <nerdboy!~sarnold@> has joined #yocto19:27
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has joined #yocto19:27
xyzzy42zeddii, occurred to me that "package foo needs service bar" is very common.  There are tons of things which involve multiple services.  But how it's usually done is foo owns foo.service, which Wants/After bar.service19:30
xyzzy42i.e., if foo needs a service, it uses the systemd unit ordering and dependency system to describe this in relation to another service.19:31
*** florian_kc <florian_kc!~florian_k@Maemo/community/contributor/florian> has joined #yocto19:36
*** anoo1 <anoo1!~anoo1@> has joined #yocto19:37
*** lucaceresoli <lucaceresoli!> has joined #yocto19:41
*** anoo1 <anoo1!~anoo1@> has quit IRC19:45
*** pohly <pohly!> has quit IRC19:45
*** timemaster5 <timemaster5!> has quit IRC19:49
*** rburton <rburton!~rburton@> has quit IRC19:50
*** lucaceresoli <lucaceresoli!> has quit IRC19:50
*** anoo1 <anoo1!~anoo1@> has joined #yocto19:50
*** timemaster5 <timemaster5!> has joined #yocto19:54
*** anoo1 <anoo1!~anoo1@> has quit IRC19:59
*** anoo1 <anoo1!~anoo1@> has joined #yocto20:01
*** amaury_d <amaury_d!> has joined #yocto20:04
*** anoo1 <anoo1!~anoo1@> has quit IRC20:13
*** risca_ is now known as risca20:43
*** risca <risca!~quassel@> has quit IRC20:47
*** risca <risca!~quassel@> has joined #yocto20:47
*** timemaster5 <timemaster5!> has quit IRC20:54
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has quit IRC20:57
*** timemaster5 <timemaster5!> has joined #yocto21:00
*** Spock_ncc1701 <Spock_ncc1701!~Spock_ncc@> has joined #yocto21:01
*** florian_kc is now known as florian21:02
*** dreyna_ <dreyna_!~dreyna@2601:646:4201:b1a0:8c36:ca89:cca9:d5ed> has joined #yocto21:03
*** timemaster5 <timemaster5!> has quit IRC21:04
*** timblechmann <timblechmann!~quassel@> has quit IRC21:06
*** timblechmann <timblechmann!~quassel@> has joined #yocto21:08
*** berton <berton!~berton@> has quit IRC21:10
*** falk0n <falk0n!> has joined #yocto21:21
*** nerdboy <nerdboy!~sarnold@> has joined #yocto21:27
*** anoo1 <anoo1!~anoo1@> has joined #yocto21:30
*** timemaster5 <timemaster5!> has joined #yocto21:31
*** nerdboy <nerdboy!~sarnold@> has quit IRC21:31
*** florian <florian!~florian_k@Maemo/community/contributor/florian> has quit IRC21:36
*** florian <florian!~florian_k@Maemo/community/contributor/florian> has joined #yocto21:39
*** timemaster5 <timemaster5!> has quit IRC21:47
*** tomjose <tomjose!~tomjose@> has joined #yocto21:47
yoctiNew news from stackoverflow: Run Raspberry Pi Zero W image in qemu <>22:14
*** timemaster5 <timemaster5!> has joined #yocto22:20
*** timemaster5 <timemaster5!> has quit IRC22:29
*** Bunio_FH <Bunio_FH!> has quit IRC22:31
*** Spock_ncc1701 <Spock_ncc1701!~Spock_ncc@> has quit IRC22:31
* paulg has a pi-zero W that has been around for several years that hasn't seen an electron of use.22:31
paulgfortunately I think it was only like $13 CDN.22:39
*** Bunio_FH <Bunio_FH!> has joined #yocto22:48
*** ssajal <ssajal!> has quit IRC22:57
*** agust <agust!> has quit IRC23:15
*** ericch <ericch!> has quit IRC23:19
*** nameclash <nameclash!> has left #yocto23:29
*** florian <florian!~florian_k@Maemo/community/contributor/florian> has quit IRC23:40
*** vineela <vineela!vtummala@nat/intel/x-xqztpbsqetucxsru> has quit IRC23:50
*** timemaster5 <timemaster5!> has joined #yocto23:52
*** locutus__ <locutus__!~LocutusOf@> has joined #yocto23:59

Generated by 2.17.2 by Marius Gedminas - find it at!