Wednesday, 2021-09-22

*** dev1990 <dev1990!~dev@78.10.71.240> has quit IRC (Quit: Konversation terminated!)00:07
*** Tokamak <Tokamak!~Tokamak@172.58.190.196> has quit IRC (Read error: Connection reset by peer)00:22
*** Tokamak <Tokamak!~Tokamak@172.58.190.196> has joined #yocto00:27
*** LocutusOfBorg <LocutusOfBorg!~locutusof@93-50-192-18.ip153.fastwebnet.it> has joined #yocto00:31
*** qschulz <qschulz!~weechat@ns326003.ip-37-187-106.eu> has quit IRC (Read error: Connection reset by peer)00:32
*** qschulz <qschulz!~weechat@ns326003.ip-37-187-106.eu> has joined #yocto00:34
*** LocutusOfBorg <LocutusOfBorg!~locutusof@93-50-192-18.ip153.fastwebnet.it> has quit IRC (Ping timeout: 264 seconds)00:36
*** gioyik <gioyik!~gioyik@gateway/tor-sasl/gioyik> has quit IRC (Ping timeout: 276 seconds)00:36
*** BobPungartnik <BobPungartnik!~Pung@187.113.151.66> has quit IRC (Remote host closed the connection)00:37
*** BobPungartnik <BobPungartnik!~Pung@187.113.151.66> has joined #yocto00:37
*** LocutusOfBorg <LocutusOfBorg!~locutusof@93-50-192-18.ip153.fastwebnet.it> has joined #yocto00:43
*** Tokamak <Tokamak!~Tokamak@172.58.190.196> has quit IRC (Read error: Connection reset by peer)00:46
*** Tokamak <Tokamak!~Tokamak@172.58.190.196> has joined #yocto00:51
*** LocutusOfBorg <LocutusOfBorg!~locutusof@93-50-192-18.ip153.fastwebnet.it> has quit IRC (Ping timeout: 264 seconds)00:52
*** jwillikers <jwillikers!~jwilliker@ics141-1.icsincorporated.com> has quit IRC (Remote host closed the connection)01:07
*** Tokamak <Tokamak!~Tokamak@172.58.190.196> has quit IRC (Ping timeout: 252 seconds)01:34
*** gioyik <gioyik!~gioyik@gateway/tor-sasl/gioyik> has joined #yocto01:35
*** Tokamak <Tokamak!~Tokamak@172.58.190.196> has joined #yocto01:38
*** gioyik <gioyik!~gioyik@gateway/tor-sasl/gioyik> has quit IRC (Ping timeout: 276 seconds)01:44
*** camus <camus!~Instantbi@58.246.136.202> has joined #yocto01:51
*** arlen <arlen!~arlen@50-32-89-83.adr01.dlls.pa.frontiernet.net> has quit IRC (Ping timeout: 252 seconds)01:59
*** arlen_ <arlen_!~arlen@50-32-89-83.adr01.dlls.pa.frontiernet.net> has joined #yocto01:59
*** LocutusOfBorg <LocutusOfBorg!~locutusof@93-50-192-18.ip153.fastwebnet.it> has joined #yocto02:00
*** whuang0389 <whuang0389!~whuang038@cpeac202ebbe763-cmac202ebbe760.cpe.net.fido.ca> has joined #yocto02:03
*** LocutusOfBorg <LocutusOfBorg!~locutusof@93-50-192-18.ip153.fastwebnet.it> has quit IRC (Ping timeout: 252 seconds)02:13
*** sakoman <sakoman!~steve@172.243.4.16> has quit IRC (Quit: Leaving.)02:25
*** gioyik <gioyik!~gioyik@gateway/tor-sasl/gioyik> has joined #yocto02:28
*** gioyik <gioyik!~gioyik@gateway/tor-sasl/gioyik> has quit IRC (Ping timeout: 276 seconds)02:33
*** vd <vd!~vd@bras-base-mtrlpq2848w-grc-41-70-53-240-121.dsl.bell.ca> has quit IRC (Quit: Client closed)02:34
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed)02:37
*** whuang0389 <whuang0389!~whuang038@cpeac202ebbe763-cmac202ebbe760.cpe.net.fido.ca> has quit IRC (Quit: Client closed)02:38
*** vd <vd!~vd@bras-base-mtrlpq2848w-grc-41-70-53-240-121.dsl.bell.ca> has joined #yocto02:50
*** alejandrohs <alejandrohs!~alejandro@cpe-70-112-59-126.austin.res.rr.com> has joined #yocto02:52
*** alejandrohs <alejandrohs!~alejandro@cpe-70-112-59-126.austin.res.rr.com> has quit IRC (Client Quit)02:52
*** gioyik <gioyik!~gioyik@gateway/tor-sasl/gioyik> has joined #yocto02:53
*** camus <camus!~Instantbi@58.246.136.202> has quit IRC (Ping timeout: 252 seconds)02:54
*** camus <camus!~Instantbi@58.246.136.202> has joined #yocto02:54
*** sakoman <sakoman!~steve@172.243.4.16> has joined #yocto02:55
*** gioyik <gioyik!~gioyik@gateway/tor-sasl/gioyik> has quit IRC (Ping timeout: 276 seconds)02:59
*** LocutusOfBorg <LocutusOfBorg!~locutusof@93-50-192-18.ip153.fastwebnet.it> has joined #yocto03:08
*** LocutusOfBorg <LocutusOfBorg!~locutusof@93-50-192-18.ip153.fastwebnet.it> has quit IRC (Ping timeout: 264 seconds)03:13
*** alejandrohs <alejandrohs!~alejandro@user/alejandrohs> has joined #yocto03:20
*** gioyik <gioyik!~gioyik@gateway/tor-sasl/gioyik> has joined #yocto03:35
*** gioyik <gioyik!~gioyik@gateway/tor-sasl/gioyik> has quit IRC (Ping timeout: 276 seconds)03:40
*** camus1 <camus1!~Instantbi@58.246.136.202> has joined #yocto03:56
*** camus <camus!~Instantbi@58.246.136.202> has quit IRC (Read error: Connection reset by peer)03:56
*** camus1 is now known as camus03:56
*** ThomasD13 <ThomasD13!~thomasd13@DSL01.212.114.255.148.ip-pool.NEFkom.net> has joined #yocto04:18
*** goliath <goliath!~goliath@user/goliath> has joined #yocto04:24
*** amitk <amitk!~amit@103.208.71.23> has joined #yocto04:31
*** sakoman <sakoman!~steve@172.243.4.16> has quit IRC (Quit: Leaving.)04:39
*** vd <vd!~vd@bras-base-mtrlpq2848w-grc-41-70-53-240-121.dsl.bell.ca> has quit IRC (Quit: Client closed)04:52
*** gioyik <gioyik!~gioyik@gateway/tor-sasl/gioyik> has joined #yocto04:52
*** LocutusOfBorg <LocutusOfBorg!~locutusof@93-50-192-18.ip153.fastwebnet.it> has joined #yocto05:04
*** LocutusOfBorg <LocutusOfBorg!~locutusof@93-50-192-18.ip153.fastwebnet.it> has quit IRC (Ping timeout: 252 seconds)05:09
*** LocutusOfBorg <LocutusOfBorg!~locutusof@93-50-192-18.ip153.fastwebnet.it> has joined #yocto05:11
*** kanavin_ <kanavin_!~Alexander@82.119.0.16> has quit IRC (Remote host closed the connection)05:12
*** kanavin_ <kanavin_!~Alexander@2a02:2454:29b:3b00:d35d:e3cf:58b5:748b> has joined #yocto05:13
*** Wouter01008 <Wouter01008!~Wouter010@entry.nbg.netvos.nl> has joined #yocto05:17
*** Wouter0100 <Wouter0100!~Wouter010@entry.nbg.netvos.nl> has quit IRC (Ping timeout: 252 seconds)05:19
*** Wouter01008 is now known as Wouter010005:19
*** BobPungartnik <BobPungartnik!~Pung@187.113.151.66> has quit IRC (Remote host closed the connection)05:27
*** BobPungartnik <BobPungartnik!~Pung@187.113.151.66> has joined #yocto05:27
*** LocutusOfBorg <LocutusOfBorg!~locutusof@93-50-192-18.ip153.fastwebnet.it> has quit IRC (Quit: ZNC 1.8.2+deb1+bionic2 - https://znc.in)05:53
*** LocutusOfBorg <LocutusOfBorg!~locutusof@93-50-192-18.ip153.fastwebnet.it> has joined #yocto05:54
*** LocutusOfBorg <LocutusOfBorg!~locutusof@93-50-192-18.ip153.fastwebnet.it> has quit IRC (Client Quit)05:58
*** ant__ <ant__!~ant@host-79-24-62-179.retail.telecomitalia.it> has quit IRC (Ping timeout: 252 seconds)06:14
*** arlen <arlen!~arlen@50-32-89-83.adr01.dlls.pa.frontiernet.net> has joined #yocto06:19
*** arlen_ <arlen_!~arlen@50-32-89-83.adr01.dlls.pa.frontiernet.net> has quit IRC (Ping timeout: 246 seconds)06:19
*** frieder <frieder!~frieder@mue-88-130-78-063.dsl.tropolys.de> has joined #yocto06:38
JosefHolzmayr[m]yo dudX06:44
*** rfuentess <rfuentess!~rfuentess@2a01:598:89f3:ce86:9d55:9141:7545:426> has joined #yocto06:46
*** roussinm <roussinm!~mroussin@bras-base-qubcpq1306w-grc-07-184-145-217-104.dsl.bell.ca> has quit IRC (Quit: WeeChat 3.3-dev)06:52
*** zpfvo <zpfvo!~fvo@89.244.127.221> has joined #yocto06:58
*** mckoan|away is now known as mckoan07:06
mckoangood morning07:06
*** gioyik <gioyik!~gioyik@gateway/tor-sasl/gioyik> has quit IRC (Quit: WeeChat 3.1)07:12
*** tnovotny <tnovotny!~tnovotny@ip4-83-240-26-162.cust.nbox.cz> has joined #yocto07:22
ThomasD13Hi07:22
ThomasD13I have a linux app, which is build by a docker image. Does yocto support docker images?07:23
JosefHolzmayr[m]ThomasD13: please define "support"07:24
ThomasD13In terms of writing a recipe, which will execute that docker image and retreive somehow the output of it and packages that07:24
JosefHolzmayr[m]ThomasD13: you can hack it up and it will cause you pain.07:24
ThomasD13pain?07:25
JosefHolzmayr[m]ThomasD13: you either want to be able to build the application directly in the recipe, e.g. the yocto way, or create some form of ci/cd-ish build pipeline. everything else is just a road to terror.07:25
JosefHolzmayr[m]ThomasD13: yes. pain.07:25
ThomasD13Hmm.. this docker image is used to build the application via gitlab ci/cd, because it's kinda complex. So all the dependency/knowledge of how to build this application is within that image.07:27
ThomasD13At the first glance, I thought it could be a good idea, to reuse this container. So that yocto use that container to build that specific application07:28
JosefHolzmayr[m]think about it. the yocto-style build process goes to great lengths to ensure reproducibilty. to cache downloads. to provide a correct sstate. any recipe that brings a "hey lets just pull this container, no idea what it does, pulls itself, reproduces, or whatever" is effectively disabling all that.07:28
JosefHolzmayr[m]so if you totally and absolutely are conviced that the application can only be built in the container, then you effectively need a build pipeline. 1) container builds thing 2) yocto recipe packages built thing as a ready made artifact.07:29
JosefHolzmayr[m]this way, yocto ensures it stays sane itself. given the same artifact, it ensures reproducibilty. everything else is somebody elses problem, then.07:30
ThomasD13Hmm ok. I think I'm not able to rewrite that application bulid process in a yocto-style recipe.. :/07:30
JosefHolzmayr[m]then have fun pipelining.07:30
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #yocto07:31
ThomasD13So I assume I enter new territory? There aren't any public classes/recipes which are doing similar?07:32
JosefHolzmayr[m]huh?07:32
ThomasD13Doing "pipelining" with yocto07:32
JosefHolzmayr[m]ThomasD13: au contraire, the yocto side of things has been in the manual for many, many years: https://www.yoctoproject.org/docs/latest/dev-manual/dev-manual.html#packaging-externally-produced-binaries07:33
JosefHolzmayr[m]ThomasD13: and the rest, well thats you CI/CD pipeline and infrastructure. its just outside our scope.07:34
ThomasD13thank you very much josef :)07:34
JosefHolzmayr[m]have fun.07:35
ThomasD13I won't ;)07:35
*** fbre <fbre!~fbre@145.253.222.69> has joined #yocto07:36
ThomasD13Next time, I beg my boss to not use TI chips07:36
JosefHolzmayr[m]don't blame TI, blame those created the build processes and bsps that gave you the headaches.07:38
JosefHolzmayr[m]*who07:38
*** dev1990 <dev1990!~dev@78.10.71.240> has joined #yocto07:38
rburtonI can't see why you can't just call docker from inside a do_compile, assuming that your build user has permission to use docker.07:40
*** meego <meego!~meego@2001:41d0:fe7e:c800:8146:bbc:806a:1a67> has joined #yocto07:40
rburtonit's madness, obviously07:40
rburtonits quite possibly trivial to reproduce the build, and the docker is just to bring the build dependencies and cross-compilers in a single blob07:41
rburtonhave a look at the dockerfile and see what it does07:41
JosefHolzmayr[m]"you can hack it up and it will cause you pain." :)07:44
JosefHolzmayr[m]i still am convinced this holds true. i never said it can't be done.07:44
JosefHolzmayr[m]because if the docker container would be just pulling in dep and toolchains, then... but in my experience, they hardly ever do "just that", and often not in a static manner.07:45
JosefHolzmayr[m]so lots of variations, it all depends on the particular situation.07:46
ThomasD13Hmm.. building that application (for R5) is quite complex. There are many software packages as dependencies (sysbios/freetos, xdc, specific buildtools, network libs, and so on) and some glue scripts influenced by many ENV variables which produces in the end functional app.07:47
JosefHolzmayr[m]extra brownie points for the container using a proprietary toolchain or tooling that needs a license key being passed in and checking tis validity online.07:48
ThomasD13All this is done in a reproducible way in that docker image. Well I have to see which way go..07:49
ThomasD13Huh? what license key?07:49
JosefHolzmayr[m]like said, have fun.07:49
JosefHolzmayr[m](that was an example for fun things that can happen)07:49
qschulzalso you're going to have a hard time if the dependencies are patched by the distro used in the container and/or more recent/older releases08:03
*** davidinux <davidinux!~davidinux@217.138.219.36> has quit IRC (Ping timeout: 265 seconds)08:25
*** davidinux <davidinux!~davidinux@217.138.219.36> has joined #yocto08:29
*** camus <camus!~Instantbi@58.246.136.202> has quit IRC (Ping timeout: 265 seconds)08:29
*** camus <camus!~Instantbi@58.246.136.202> has joined #yocto08:29
RPkanavin_: librsvg recipe looks good, if a little worrying and hard to understand the "magic". You do like a challenge :)08:31
kanavin_RP: I like showing off too ;)08:31
kanavin_RP: I tried to add comments to the 'magic' bits08:31
kanavin_RP: I hope we won't see more of this autotools on top of cargo things08:32
RPkanavin_: the comments definitely help. I hope we don't see more of that kind of thing but who knows...08:32
RPkanavin_: reminds me a lot of how things used to be with gcc08:32
kanavin_RP: I'd like to throw the whole patchset on the AB again, but would like to do it on top of your task optimizations08:34
kanavin_I think those are not quite ready?08:34
RPkanavin_: actually, master-next isn't too bad now. There was one selftest that failed in the last test and I've put a "fix" for that and am retesting.08:35
RPkanavin_: The only downside is that fix is a total rebuild which is in progress atm, no sstate reuse08:35
* RP had to revert the native part of the siteinfo change which makes me sad08:36
*** FredO3 <FredO3!~willy562@bras-base-crnypq0201w-grc-08-216-209-60-169.dsl.bell.ca> has joined #yocto08:36
*** FredO2 <FredO2!~willy562@bras-base-crnypq0201w-grc-08-216-209-60-169.dsl.bell.ca> has quit IRC (Read error: Connection reset by peer)08:37
*** mattsm <mattsm!~mattsm@104-181-154-57.lightspeed.austtx.sbcglobal.net> has quit IRC (Quit: Ping timeout (120 seconds))08:37
*** mattsm <mattsm!~mattsm@104-181-154-57.lightspeed.austtx.sbcglobal.net> has joined #yocto08:37
*** Belsirk <Belsirk!~rfuentess@tmo-099-4.customers.d1-online.com> has joined #yocto08:39
kanavin_RP: as written in the commit, none of us understands the rust toolchain, or its consumers very well, so as we bring in more consumers, patterns for better solutions will emerge08:39
kanavin_e.g. consolidating and improving the hacks from individual recipes like librsvg08:40
RPkanavin_: definitely. gcc sysroot support was kind of a result of that :)08:40
*** rfuentess <rfuentess!~rfuentess@2a01:598:89f3:ce86:9d55:9141:7545:426> has quit IRC (Ping timeout: 246 seconds)08:41
kanavin_RP: one thing I'd like to do differently this time is take a hint from meson, and try to avoid relying on environment variables08:43
kanavin_they're ephemeral and it's hard to say what was there and what wasn't when things don't work - much better to have a config file on disk, and a log with command line switches to get the picture08:44
*** zyga-mbp <zyga-mbp!~zyga@31.0.173.147> has quit IRC (Quit: Textual IRC Client: www.textualapp.com)08:45
RPkanavin_: right, environment variables do tend to be problematic after a while. I still mean to go and try and reduce the number we have exported08:47
*** zyga-mbp <zyga-mbp!~zyga@31.0.173.147> has joined #yocto08:47
RP(to be clear, I did clean it up a lot but we're down to the harder ones - tricky to know where they are used)08:53
*** florian <florian!~florian@port-217-146-132-69.static.as20676.net> has joined #yocto09:01
*** arlen <arlen!~arlen@50-32-89-83.adr01.dlls.pa.frontiernet.net> has quit IRC (Ping timeout: 264 seconds)09:12
*** pgowda <pgowda!uid516182@id-516182.ilkley.irccloud.com> has joined #yocto09:16
*** LocutusOfBorg <LocutusOfBorg!~locutusof@2001:b07:5d32:c012:a8fe:ff5c:20ac:66d2> has joined #yocto09:21
*** m4ho <m4ho!~m4ho@81.20.119.6> has quit IRC (Read error: Connection reset by peer)09:32
*** m4ho <m4ho!~m4ho@81.20.119.6> has joined #yocto09:47
*** Belsirk <Belsirk!~rfuentess@tmo-099-4.customers.d1-online.com> has quit IRC (Remote host closed the connection)09:56
*** retoatwork <retoatwork!~retoatwor@85.195.220.82> has quit IRC (Ping timeout: 265 seconds)10:11
*** Tokamak <Tokamak!~Tokamak@172.58.190.196> has quit IRC (Read error: Connection reset by peer)10:30
*** mckoan is now known as mckoan|away10:31
*** Tokamak <Tokamak!~Tokamak@172.58.190.196> has joined #yocto10:36
*** Alban[m] <Alban[m]!~albeugaen@2001:470:69fc:105::34b4> has joined #yocto10:36
*** locutusofborg_ <locutusofborg_!~locutusof@93-50-192-18.ip153.fastwebnet.it> has joined #yocto10:36
*** LocutusOfBorg <LocutusOfBorg!~locutusof@2001:b07:5d32:c012:a8fe:ff5c:20ac:66d2> has quit IRC (Ping timeout: 246 seconds)10:37
*** jwillikers <jwillikers!~jwilliker@ics141-1.icsincorporated.com> has joined #yocto10:39
Alban[m]Hi! I'm thinking about setting up an internal layer index to automate the fetching of depend layers in my projects. I found layerindex-web but the README says that it has no REST API, so for me that sounds like it could not be used with bitbake-layers layerindex-fetch. Is there an implementation of this API available somewhere else?10:48
*** BobPungartnik <BobPungartnik!~Pung@187.113.151.66> has quit IRC (Quit: Leaving)11:17
*** GillesM <GillesM!~gilles@89.55.119.78.rev.sfr.net> has joined #yocto11:17
*** locutusofborg_ is now known as locutusofborg11:36
*** xmn <xmn!~xmn@cpe-72-225-198-203.nyc.res.rr.com> has quit IRC (Ping timeout: 265 seconds)11:54
*** arlen <arlen!~arlen@50-32-89-83.adr01.dlls.pa.frontiernet.net> has joined #yocto12:10
*** BCMM <BCMM!~BCMM@user/bcmm> has joined #yocto12:16
dwagenkHello. I know this is nor a lawyers chat, but I'd be interested if my take on INITRAMFS_IMAGE_BUNDLE is consensus or if there are different takes on this: Bundling the initramfs does NOT make the kernel+initramfs a derivative work in the sense of GPLv2. Thus the initramfs may contain proprietary (GPL incompatible) programms.12:58
JosefHolzmayr[m]dwagenk: from the kernel.org docs: External initramfs images:... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/2f5944843e76210aff6380c6f713698e391f8dac)13:03
JosefHolzmayr[m]based on this information one might conclude that your interpretation of bundling is wrong.13:04
*** camus <camus!~Instantbi@58.246.136.202> has quit IRC (Ping timeout: 252 seconds)13:08
*** camus <camus!~Instantbi@58.246.136.202> has joined #yocto13:09
dwagenkthyoctojester: thanks for that hint! That looks pretty clear. Maybe we should add a hint about this to the yocto docs, since the implications of setting INITRAMFS_IMAGE_BUNDLE are easy to overlook. I know the documentation is pretty clear about who's obligation it is to ensure license compliance, but this feels like a trap. Especially since step 2 in https://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#building-an-initramfs-image13:13
dwagenkrecommends bundling due to technical reasons.13:13
JosefHolzmayr[m]dwagenk: patches welcome!13:13
JosefHolzmayr[m]also, michaelo13:14
dwagenktheyoctojester: I'll prepare something13:14
JosefHolzmayr[m]perfect, thanks!13:15
*** meego <meego!~meego@2001:41d0:fe7e:c800:8146:bbc:806a:1a67> has quit IRC (Remote host closed the connection)13:27
*** meego <meego!~meego@2001:41d0:fe7e:c800:f1f7:2235:eaba:b1d> has joined #yocto13:27
*** ThomasD13 <ThomasD13!~thomasd13@DSL01.212.114.255.148.ip-pool.NEFkom.net> has quit IRC (Ping timeout: 264 seconds)13:27
tlwoernerRP: are you attending the plumbers conference?13:44
tlwoernerRP: in 15 minutes there's a "GCC steering committee Q&A (glibc, binutils, gdb)"13:45
tlwoernermight be a good opportunity to ask about glibc symbols (?)13:46
tlwoernerRP: today there's also the "Tracing Microconference" which might provide an opportunity to think about pseudo (?)13:46
tlwoerneri have started doing some research into pseudo/fakeroot things, but probably not enough yet13:47
*** meego_ <meego_!~meego@2001:41d0:fe7e:c800:8146:bbc:806a:1a67> has joined #yocto14:03
*** FredO3 is now known as FredO14:03
*** meego <meego!~meego@2001:41d0:fe7e:c800:f1f7:2235:eaba:b1d> has quit IRC (Ping timeout: 246 seconds)14:05
*** jwillikers <jwillikers!~jwilliker@ics141-1.icsincorporated.com> has quit IRC (Remote host closed the connection)14:10
JPEWmoto-timo: You might be interested in my zuul escapades. I finally have it connected to my GitHub repo and building PRs: https://zuul.wattissoftware.com/t/wattissoftware-zuul/status14:16
*** sakoman <sakoman!~steve@172.243.4.16> has joined #yocto14:16
*** argonautx <argonautx!~argonautx@gw.hyperstone.de> has joined #yocto14:17
moto-timoJPEW: interesting14:18
*** vd <vd!~vd@bras-base-mtrlpq2848w-grc-41-70-53-240-121.dsl.bell.ca> has joined #yocto14:20
moto-timoJPEW: what features/factors made you choose zuul?14:21
JPEWmoto-timo: A bunch of reasons: 1) it's a complete CI solution (Tekton isn't *quite* there, and I don't think it's really intended to be)14:22
moto-timoJPEW: agreed, Tekton was designed to be the backend for a full soution, such as Jenkins-X14:23
JPEW2) It fully runs in K8s (see zuul-operator). It can actually still use a bunch of different worker nodes though. I only have it using K8s pods for building, but it can connect to Openstack nodes, AWS, GCE, etc.14:23
JPEWand you can mix and match pretty easily14:24
moto-timoah14:24
JPEW3) It's really flexible. You define what pipelines you want and what they do, then the individual project say what jobs they want in each pipeline14:25
JPEWSo... the recommended setup is to have a "check" pipeline that runs on every new change and does the basic sanity checks14:26
JPEWThen have a "gate" pipeline that runs you full CI and automated testing after a code review; when that passes Zuul submits the change for you14:26
JPEW(it also does speculative merging for stacked "gate" changes, so it can handle a lot of changes at once)14:27
moto-timoah, that's like the gerrit workflow we were using for the "Living on Master" ELCE talk14:28
JPEW4) Zuul is run by openstack, so gerrit is a first class citizen (not important here, but we use gerrit at work)14:28
moto-timoI was aware of openstack/gerrit14:28
JPEWIt's really nice to mark a PR/commit as "ready-to-merge" and know it will go through a full CI and merge after it passes.... kinda fire-and-forget :)14:30
moto-timolike openstack, zuul has some awkward naming, but that' just lack of familiarity I suppose14:30
JPEWYa, it took me a while to grok all the nomeclature.... also it's all written in Python so I can actually hack on it14:31
moto-timothat is indeed nice...  we had very light human touch automation for a rolling-release14:31
moto-timoPython is a huge plus, obviously14:31
moto-timoYou're running this on one of your home servers I assume?14:32
JPEWYa. I will say that it is very confusing on how to get a system stood up at first because they've broken down the entire thing into a bunch of very small and dedicated components.... so you have to run a scheduler, executor, merger, web-server, nodepool, etc independently (zuul-operator helps a lot with this though)14:32
JPEWUa14:32
JPEWYa on my home servers14:32
moto-timothat's very openstack of them ;)14:33
JPEWYa, it makes sense after you see why they did it... but still confusing :)14:34
moto-timoOf course the dashboard project I did also had many small components/microservices...14:34
moto-timowhich grew organically over time and the whole team knew what they all were. LOL14:35
smurrayheh14:35
JPEWmoto-timo: I think I've fully bought into the "operator" concept with K8s14:35
moto-timoJPEW: when it works, it is better than Helm14:36
*** pidge <pidge!~pidge@194.110.145.166> has joined #yocto14:40
RPtlwoerner: sorry, I'm not at plumbers, no :(14:41
* moto-timo is at plumbers14:41
rburtonyou can be "at" plumbers for free, its live on youtube14:42
moto-timoindeed14:42
RPrburton: ah, well, I also didn't see this until now :/14:44
rburtonyou can also rewind the live streams to watch at your leisure14:44
RPrburton: right, but that wasn't quite what tlwoerner was suggesting14:45
*** mrnuke <mrnuke!~mrnuke@2601:2c1:8501:182d::c66> has joined #yocto14:46
rburtonah right yeah asking a question means registering, sorry14:46
mrnukeHi, I'm trying to use the arm esdk installer from downloads.yoctoproject.org. but when I run the shell script to install it, it takes forever.14:47
mrnukeAnd I keep getting "WARNING: Error contacting Hash Equivalence Server typhoon.yocto.io:8686: [Errno 110] Connect call failed ('35.233.185.178', 8686)"14:47
RPmrnuke: we were just discussing that. It has been fixed recently but won't be in the last point releases14:48
*** DanielWalls[m] <DanielWalls[m]!~dwallsmat@2001:470:69fc:105::ff37> has joined #yocto14:48
RPmrnuke: 3.4 M3 should be ok14:48
mrnukeRP: thanks. I'll give that a try then!14:56
*** tnovotny <tnovotny!~tnovotny@ip4-83-240-26-162.cust.nbox.cz> has quit IRC (Quit: Leaving)14:59
JosefHolzmayr[m]moto-timo: JPEW funny reading you muse about that when I'm just getting into gitlab ci/cd ;-)15:05
JPEWJosefHolzmayr[m]: Ya, gitlab CI seems good also (no personal experience). I wanted something that A) I could selfhost and B) wasn't tied to any particular git provider15:07
*** frieder <frieder!~frieder@mue-88-130-78-063.dsl.tropolys.de> has quit IRC (Remote host closed the connection)15:07
JosefHolzmayr[m]funny, my objective is explictly to not-selfhost :)15:08
*** manuel1985 <manuel1985!~manuel198@62.99.131.178> has joined #yocto15:09
JPEWSure! for non-yocto builds I use github actions (gitlab equivalent works just a well). Too much extra infra needed for fast Yocto builds (sstate, hashequiv, etc.)15:09
qschulzJPEW: you can self-host everything from GitLab I'm pretty sure?15:09
moto-timokhem has some GitHub actions for you-distro15:09
*** camus1 <camus1!~Instantbi@58.246.136.202> has joined #yocto15:10
moto-timos/you/yoe/15:10
JPEWqschulz: Yes, you can. I only want to self-host the CI not the code (maybe gitlab supports that, would have to look)15:10
JPEWqschulz: I know you can attach k8s runners to gitlab and have it do the builds locally15:11
*** camus <camus!~Instantbi@58.246.136.202> has quit IRC (Ping timeout: 265 seconds)15:11
*** camus1 is now known as camus15:11
moto-timoI self-hosted gitlab ci runner, using public gitlab repos15:11
JPEW^^ like that :)15:11
moto-timoBut I got bogged down with running testimage (qemu running in a docker container)15:12
moto-timoAnd then I switched to podman15:12
moto-timoStill haven’t gotten the k8s gitlab ci runner functional yet15:13
qschulzthough they explicitly say in the docs that you probably shouldn't run your own gitlab ci runner on a public repo. But that drastically limits the interest of it :p15:13
RPJPEW: would systemd-analyze show up potential races?15:13
* RP is pondering that issue again15:13
JPEWRP: No, but it might tell us why systemd is tearing down all the networking when systemd-timesyncd is stopped15:14
JPEWs/stopped/disabled15:14
RPJPEW: Googling the error suggests dbus somehow disconnected logind :/15:14
JPEWHmm....15:14
RPnothing I could find about why though15:15
JPEWPerhaps one or the other doesn't like the discontiguous jump in time15:15
RPJPEW: something like that seems likely15:15
JPEWMaybe is't not the service, maybe it's when the test changes the time15:15
RPJPEW: right, it's a question of how to debug it15:25
*** pgowda <pgowda!uid516182@id-516182.ilkley.irccloud.com> has quit IRC (Quit: Connection closed for inactivity)15:30
*** florian <florian!~florian@port-217-146-132-69.static.as20676.net> has quit IRC (Quit: Ex-Chat)15:34
*** ccf <ccf!~ccf@user/ccf> has joined #yocto15:37
ccfAhoj, how to execute a shell-function from within a python-function?15:38
qschulzccf: bb.build.exec_func15:42
qschulzthough you can use [postfunc] and [prefunc] flags for your python task15:42
*** fbre <fbre!~fbre@145.253.222.69> has quit IRC (Quit: fbre)15:51
*** arlen <arlen!~arlen@50-32-89-83.adr01.dlls.pa.frontiernet.net> has quit IRC (Ping timeout: 246 seconds)15:52
*** arlen_ <arlen_!~arlen@50-32-89-83.adr01.dlls.pa.frontiernet.net> has joined #yocto15:52
*** BCMM <BCMM!~BCMM@user/bcmm> has quit IRC (Remote host closed the connection)15:55
*** kiran <kiran!~kiran@2607:fea8:5a80:ea0:f467:f52:2f71:a5fa> has joined #yocto15:58
sgwMorning Folks, is anyone else seeing a new ImportWarning16:02
sgw/usr/lib/python3.6/importlib/_bootstrap.py:219: ImportWarning: can't resolve package from __spec__ or __package__, falling back on __name__ and __path__16:02
sgw  return f(*args, **kwds)16:02
*** lucaceresoli <lucaceresoli!~ceresoli@tech.aim-sportline.com> has quit IRC (Quit: Leaving)16:09
mrnukenew question. I'm trying to build a docker image (for gitlab-CI) with an arm toolchain, and mesa, libdrm and boost packages. I do 'devtool sdk-install -s boost libdrm, mesa' within the docker build. The resulting image is 17GB in size. Is there a way to cleanup bloat ?16:10
*** kiran <kiran!~kiran@2607:fea8:5a80:ea0:f467:f52:2f71:a5fa> has quit IRC (Ping timeout: 260 seconds)16:24
vdHow can I figure out which recipe a binary comes from? (e.g. "resizepart")16:25
rburtonoe-pkgdata-util find-path /usr/bin/resizepart16:26
*** zpfvo <zpfvo!~fvo@89.244.127.221> has quit IRC (Remote host closed the connection)16:28
vdrburton: "Unable to find pkgdata directory" do I need to run something first?16:28
rburtonyou need to build something16:28
rburtoncan't tell you what package contains a file if there is nothing packaged16:29
rburtonutil-linux, fwiw16:29
rburton(bitbake recipes don't have to list exactly what is in each package, so you can't know from just the metadata)16:31
Tokamakrandom question.  I'm finding it rather undesirable that yocto clobbers the kernel version.h's build date as shown by "uname -v".  Does anyone know if there is a way to disable this clobbering for the kernel class?16:33
*** vd <vd!~vd@bras-base-mtrlpq2848w-grc-41-70-53-240-121.dsl.bell.ca> has quit IRC (Quit: Client closed)16:33
*** vd <vd!~vd@bras-base-mtrlpq2848w-grc-41-70-53-240-121.dsl.bell.ca> has joined #yocto16:34
Tokamaksorry, correction.  version.h's source revision date, not build date.16:34
rburtonturn off reproducible builds16:34
zeddii+116:34
*** ant__ <ant__!~ant@host-79-24-62-179.retail.telecomitalia.it> has joined #yocto16:34
Tokamaki had thought about that, but its somewhat desirable to have a consistent date at the filesystem level.  is there a way to disable reproducible builds just for the kernel?16:35
rburtonsure, disable reproducible builds for just the kernel16:39
rburtonBUILD_REPRODUCIBLE_BINARIES=016:40
*** pidge <pidge!~pidge@194.110.145.166> has quit IRC (Quit: Client closed)16:45
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed)16:45
*** pidge <pidge!~pidge@194.110.145.166> has joined #yocto16:45
Tokamakforgive me as i'm still not comfortable with yocto variable scoping / masking.  but do i need to mask that variable by PN somehow?  or if i set it to 0 just in linux-xlnx (for example), it will stay scoped to that package?16:48
rburtonin the recipe, use it as-is.  or in your local.conf or distro conf you could do BUILD_REPRODUCIBLE_BINARIES_pn-linux-xlnx = "0"16:49
Tokamakok, so recipes have some scoping, sometimes.  :P   thanks!  will give it a go!16:50
rburtonrecipes have 100% scoping16:50
rburtonset a variable inside them and it won't leak out into other recipes16:51
*** camus <camus!~Instantbi@58.246.136.202> has quit IRC (Remote host closed the connection)16:55
Tokamakgood to know, thanks again rburton16:56
*** camus <camus!~Instantbi@58.246.136.202> has joined #yocto17:02
vmesonsgw: have you or tgamblin checked if that happens on other ubu-18.04 systems? I'm doing a build on ubu-21.04 and it seems fine. Did your bisect finish?17:03
*** meego_ <meego_!~meego@2001:41d0:fe7e:c800:8146:bbc:806a:1a67> has quit IRC (Remote host closed the connection)17:08
RPsgw: yes, I see that on my 1804 system17:09
*** meego <meego!~meego@2001:41d0:fe7e:c800:8146:bbc:806a:1a67> has joined #yocto17:09
RPsgw: annoying. It is from the warnings change from alexk17:09
sgwRP: I should have said I have a 20.04 system, so it's there also.17:09
RPsgw: sorry, mine is 20.04! :)17:10
sgwvmeson: Yeah, it was alex's change to enable warnings17:10
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #yocto17:10
sgwNot sure why the create_spdx is failing now also, digging into that.17:13
*** meego <meego!~meego@2001:41d0:fe7e:c800:8146:bbc:806a:1a67> has quit IRC (Ping timeout: 268 seconds)17:14
*** GillesM <GillesM!~gilles@89.55.119.78.rev.sfr.net> has quit IRC (Quit: Leaving)17:23
zeddiiRP: round two of my 5.14 bump seems to be green (fixed systemtap). I can send a rfc unified series (I'll skip the OE/yocto split) and maybe we can get it into more testing.17:25
RPzeddii: sounds good, I can pull into master-next too17:26
RPsgw: we could do with adding tests for that on the AB17:26
*** argonautx <argonautx!~argonautx@gw.hyperstone.de> has quit IRC (Ping timeout: 252 seconds)17:27
*** leon-anavi <leon-anavi!~Leon@78.130.197.211> has joined #yocto17:27
*** kiran <kiran!~kiran@2607:fea8:5a80:ea0:9c07:a384:b31:4305> has joined #yocto17:30
*** manuel_ <manuel_!~manuel198@62.99.131.178> has joined #yocto17:32
*** meego <meego!~meego@2a01:e0a:1ec:b0e0:11e2:d8ad:b66c:a3ba> has joined #yocto17:33
*** manuel1985 <manuel1985!~manuel198@62.99.131.178> has quit IRC (Ping timeout: 252 seconds)17:35
*** camus1 <camus1!~Instantbi@58.246.136.202> has joined #yocto17:35
*** camus <camus!~Instantbi@58.246.136.202> has quit IRC (Remote host closed the connection)17:35
*** camus1 is now known as camus17:35
*** meego <meego!~meego@2a01:e0a:1ec:b0e0:11e2:d8ad:b66c:a3ba> has quit IRC (Ping timeout: 252 seconds)17:39
*** manuel_ <manuel_!~manuel198@62.99.131.178> has quit IRC (Ping timeout: 265 seconds)17:42
*** camus1 <camus1!~Instantbi@58.246.136.202> has joined #yocto17:42
*** camus <camus!~Instantbi@58.246.136.202> has quit IRC (Ping timeout: 265 seconds)17:42
*** camus1 is now known as camus17:42
*** roussinm <roussinm!~mroussin@bras-base-qubcpq1306w-grc-07-184-145-217-104.dsl.bell.ca> has joined #yocto17:45
*** kanavin_ <kanavin_!~Alexander@2a02:2454:29b:3b00:d35d:e3cf:58b5:748b> has quit IRC (Quit: Leaving)17:46
*** kanavin <kanavin!~Alexander@2a02:2454:29b:3b00:d35d:e3cf:58b5:748b> has joined #yocto17:48
*** Xagen <Xagen!~Xagen@2600:1700:211:7e60:50d6:94f9:5031:e57e> has joined #yocto17:48
*** kanavin <kanavin!~Alexander@2a02:2454:29b:3b00:d35d:e3cf:58b5:748b> has quit IRC (Remote host closed the connection)17:48
*** Xagen_ <Xagen_!~Xagen@2600:1700:211:7e60:50d6:94f9:5031:e57e> has joined #yocto17:49
*** kanavin <kanavin!~Alexander@2a02:2454:29b:3b00:d35d:e3cf:58b5:748b> has joined #yocto17:50
*** Xagen <Xagen!~Xagen@2600:1700:211:7e60:50d6:94f9:5031:e57e> has quit IRC (Ping timeout: 264 seconds)17:52
*** Xagen_ <Xagen_!~Xagen@2600:1700:211:7e60:50d6:94f9:5031:e57e> has quit IRC (Quit: My MacBook has gone to sleep. ZZZzzz…)17:54
*** Xagen <Xagen!~Xagen@99-135-179-142.lightspeed.austtx.sbcglobal.net> has joined #yocto17:55
*** pidge <pidge!~pidge@194.110.145.166> has quit IRC (Quit: Client closed)18:01
*** zyga-mbp <zyga-mbp!~zyga@31.0.173.147> has quit IRC (Quit: My MacBook has gone to sleep. ZZZzzz…)18:02
*** argonautx <argonautx!~argonautx@dynamic-046-114-146-233.46.114.pool.telefonica.de> has joined #yocto18:19
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed)18:26
*** kanavin <kanavin!~Alexander@2a02:2454:29b:3b00:d35d:e3cf:58b5:748b> has quit IRC (Remote host closed the connection)18:41
*** kanavin <kanavin!~Alexander@2a02:2454:29b:3b00:d35d:e3cf:58b5:748b> has joined #yocto18:41
*** behanw <behanw!uid110099@id-110099.uxbridge.irccloud.com> has quit IRC (Quit: Connection closed for inactivity)18:45
*** argonautx <argonautx!~argonautx@dynamic-046-114-146-233.46.114.pool.telefonica.de> has quit IRC (Ping timeout: 260 seconds)19:11
*** florian <florian!~florian@dynamic-002-243-040-220.2.243.pool.telefonica.de> has joined #yocto19:11
*** meego <meego!~meego@2a01:e0a:1ec:b0e0:1037:e83f:ed32:dc8> has joined #yocto19:12
*** camus <camus!~Instantbi@58.246.136.202> has quit IRC (Ping timeout: 265 seconds)19:15
*** camus <camus!~Instantbi@58.246.136.202> has joined #yocto19:15
*** meego <meego!~meego@2a01:e0a:1ec:b0e0:1037:e83f:ed32:dc8> has quit IRC (Ping timeout: 246 seconds)19:18
*** vd <vd!~vd@bras-base-mtrlpq2848w-grc-41-70-53-240-121.dsl.bell.ca> has quit IRC (Quit: Client closed)19:24
*** dkl_ is now known as dkl19:25
*** yates <yates!~user@fv-nc-f7af8b91e1-234237-1.tingfiber.com> has quit IRC (Remote host closed the connection)19:29
*** vd <vd!~vd@bras-base-mtrlpq2848w-grc-41-70-53-240-121.dsl.bell.ca> has joined #yocto19:37
jaskij[m]RP: regarding pg_config, that native build idea has one more hurdle: as of now the postgresql in meta-oe doesn't seem to package it.20:12
jaskij[m]Is there a way to get a dependency's version in a recipe?20:13
RPjaskij[m]: you'd have to write something into the sysroot from the recipe20:16
jaskij[m]Fortunately libpq is in the sysroot with it's pkgconfig20:18
*** arlen <arlen!~arlen@50-32-89-83.adr01.dlls.pa.frontiernet.net> has joined #yocto20:29
*** arlen_ <arlen_!~arlen@50-32-89-83.adr01.dlls.pa.frontiernet.net> has quit IRC (Ping timeout: 264 seconds)20:29
*** goliath <goliath!~goliath@user/goliath> has quit IRC (Quit: SIGSEGV)20:31
*** leon-anavi <leon-anavi!~Leon@78.130.197.211> has quit IRC (Remote host closed the connection)20:32
*** leon-anavi <leon-anavi!~Leon@78.130.197.211> has joined #yocto20:33
*** jsandman <jsandman!~jsandman@95.179.203.88> has quit IRC (Quit: The Lounge - https://thelounge.chat)21:09
*** jsandman <jsandman!~jsandman@95.179.203.88> has joined #yocto21:10
*** meego <meego!~meego@2a01:e0a:1ec:b0e0:bd5c:21da:58f7:9ced> has joined #yocto21:11
*** manuel_ <manuel_!~manuel198@2a02:1748:dd5c:f290:c5b2:fdff:b718:9edf> has joined #yocto21:14
*** meego <meego!~meego@2a01:e0a:1ec:b0e0:bd5c:21da:58f7:9ced> has quit IRC (Ping timeout: 264 seconds)21:19
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #yocto21:22
*** amitk_ <amitk_!~amit@103.208.69.121> has joined #yocto21:23
*** amitk <amitk!~amit@103.208.71.23> has quit IRC (Ping timeout: 264 seconds)21:25
*** camus1 <camus1!~Instantbi@58.246.136.202> has joined #yocto21:30
*** camus <camus!~Instantbi@58.246.136.202> has quit IRC (Ping timeout: 252 seconds)21:31
*** camus1 is now known as camus21:31
*** ccf <ccf!~ccf@user/ccf> has left #yocto21:46
*** leon-anavi <leon-anavi!~Leon@78.130.197.211> has quit IRC (Quit: Leaving)21:50
*** gsalazar <gsalazar!~gsalazar@194.38.148.130> has quit IRC (Ping timeout: 246 seconds)22:05
*** xmn <xmn!~xmn@cpe-72-225-198-203.nyc.res.rr.com> has joined #yocto22:08
*** jwillikers <jwillikers!~jwilliker@ics141-1.icsincorporated.com> has joined #yocto22:17
*** jwillikers <jwillikers!~jwilliker@ics141-1.icsincorporated.com> has quit IRC (Remote host closed the connection)22:22
*** jwillikers <jwillikers!~jwilliker@ics141-1.icsincorporated.com> has joined #yocto22:29
*** dev1990 <dev1990!~dev@78.10.71.240> has quit IRC (Quit: Konversation terminated!)22:30
*** kiran <kiran!~kiran@2607:fea8:5a80:ea0:9c07:a384:b31:4305> has quit IRC (Ping timeout: 264 seconds)22:30
*** camus <camus!~Instantbi@58.246.136.202> has quit IRC (Ping timeout: 252 seconds)22:46
*** camus <camus!~Instantbi@58.246.136.202> has joined #yocto22:47
*** amitk_ <amitk_!~amit@103.208.69.121> has quit IRC (Ping timeout: 264 seconds)22:55
*** meego <meego!~meego@2a01:e0a:1ec:b0e0:f0fd:b934:580d:bcf3> has joined #yocto23:12
*** meego <meego!~meego@2a01:e0a:1ec:b0e0:f0fd:b934:580d:bcf3> has quit IRC (Ping timeout: 246 seconds)23:19
*** camus <camus!~Instantbi@58.246.136.202> has quit IRC (Ping timeout: 246 seconds)23:24
*** camus <camus!~Instantbi@58.246.136.202> has joined #yocto23:28
*** florian <florian!~florian@dynamic-002-243-040-220.2.243.pool.telefonica.de> has quit IRC (Ping timeout: 252 seconds)23:29
*** camus1 <camus1!~Instantbi@58.246.136.202> has joined #yocto23:32
*** camus <camus!~Instantbi@58.246.136.202> has quit IRC (Ping timeout: 246 seconds)23:32
*** camus1 is now known as camus23:32

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!