Sunday, 2022-04-24

*** camus <camus!~Instantbi@2409:8a1e:9112:6900:a067:7638:8bbf:a96f> has joined #oe00:40
*** amahnui <amahnui!uid502939@id-502939.tinside.irccloud.com> has quit IRC (Quit: Connection closed for inactivity)01:29
*** rber|res <rber|res!~rber|res@ppp-2-86-142-56.home.otenet.gr> has joined #oe01:32
*** RobertBerger <RobertBerger!~rber|res@ppp-2-86-142-56.home.otenet.gr> has quit IRC (Ping timeout: 256 seconds)01:34
*** darkapex <darkapex!~darkapex@user/darkapex> has quit IRC (Ping timeout: 256 seconds)01:46
*** sakoman <sakoman!~steve@dhcp-72-253-6-214.hawaiiantel.net> has quit IRC (Quit: Leaving.)02:13
*** darkapex <darkapex!~darkapex@user/darkapex> has joined #oe05:29
*** amahnui <amahnui!uid502939@id-502939.tinside.irccloud.com> has joined #oe06:41
*** zeddii <zeddii!~zeddii@173.34.88.218> has quit IRC (Ping timeout: 246 seconds)08:03
*** zeddii <zeddii!~zeddii@173.34.88.218> has joined #oe08:04
*** florian_kc <florian_kc!~florian@dynamic-002-244-157-026.2.244.pool.telefonica.de> has joined #oe08:32
*** florian_kc <florian_kc!~florian@dynamic-002-244-157-026.2.244.pool.telefonica.de> has quit IRC (Ping timeout: 276 seconds)08:45
*** jeroen_ <jeroen_!~jeroen@2001:1c01:3bc5:4e00:e791:efe6:bf00:7133> has joined #oe09:07
*** florian_kc <florian_kc!~florian@dynamic-002-244-157-026.2.244.pool.telefonica.de> has joined #oe10:19
*** florian_kc <florian_kc!~florian@dynamic-002-244-157-026.2.244.pool.telefonica.de> has quit IRC (Ping timeout: 272 seconds)10:48
*** amahnui <amahnui!uid502939@id-502939.tinside.irccloud.com> has quit IRC (Quit: Connection closed for inactivity)11:00
*** florian_kc <florian_kc!~florian@dynamic-002-244-157-026.2.244.pool.telefonica.de> has joined #oe11:11
*** darkapex <darkapex!~darkapex@user/darkapex> has quit IRC (Ping timeout: 276 seconds)12:10
*** rber|res <rber|res!~rber|res@ppp-2-86-142-56.home.otenet.gr> has quit IRC (Remote host closed the connection)13:06
*** amahnui <amahnui!uid502939@id-502939.tinside.irccloud.com> has joined #oe15:20
jeroen_zeddii: do you happen to be around?16:18
*** dl9pf[m] <dl9pf[m]!~dl9pfmatr@2001:470:69fc:105::9a8> has joined #oe16:18
*** sakoman <sakoman!~steve@dhcp-72-253-6-214.hawaiiantel.net> has joined #oe16:26
marexsakoman: kanavin_: hey, so I started looking at the mixin layers again -- https://git.yoctoproject.org/meta-lts-mixins/ -- because that seems like the recommended way to get newer kernel versions of older OE releases, but ...16:34
marexthey layer seems dead16:34
marexdenix: ^16:34
marexwould it make sense to plug it into AUH somehow, so it gets timely updates for example ?16:34
sakomanmarex: to be honest I don't monitor that layer, so I can't say whether it is alive or dead!16:37
marexits dead all right16:37
tlwoernermarex: i don't think it's dead17:08
tlwoerneron jan 14 the 5.10 kernel was updated to 5.10.9117:08
tlwoernerthe latest commits were to the dunfell/go layer on feb 317:08
tlwoernermarex: perhaps a little neglected, but a bit early to call it dead17:09
tlwoernersakoman: zeddii: denix: will 5.15 get a dunfell mixin branch?17:10
jeroen_Am I the only one who really hates autotools, grrr.17:14
jeroen_I am trying to fix this, https://bugzilla.yoctoproject.org/show_bug.cgi?id=14681, as gcc in the SDK fails when gcc plugins are used.17:16
marextlwoerner: that's 21 linux-stable releases behind ... which is like hundreds of fixes that are missing17:16
marexoh, the usual gcc plugins issue, heh17:17
denixtlwoerner: it's impossible to measure demand for mixin layers. unlike kernel, my understanding that kanavin's go and docker layers were special-purpose one-off and won't be updated17:18
jeroen_that is caused by https://github.com/gcc-mirror/gcc/blob/master/gcc/configure#L3212417:18
jeroen_since it ends in https://github.com/gcc-mirror/gcc/blob/master/gcc/configure#L32157, and -rdynamic is not added..17:19
denixmarex: kernel is up-to-date now - there were 7 update commits, 1 RT commit and 6 config fixes. I fell behind updating it, since there's no feedback17:19
marexdenix: the mixin layer isn't great, so I keep linux-stable , mesa , mainline u-boot layer and just keep it up to date17:20
marexhttps://source.denx.de/denx/meta-mainline-common/-/commits/dunfell-3.1 here17:20
marexand I just keep rolling it forward using a script, there are users who need timely updates, so they consume that17:20
jeroen_So I changed that check configure.ac, but for some reason configure isn't update. Which magic command do I need for that?17:21
marexdenix: I would like to switch to something more upstream, but it seems the mixin layer isn't an option , because outdated all the time17:22
denixmarex: unlike your own rolling linux-stable layer where you keep updating it often, mixin layer policy is to only take backports, i.e. zeddii's commits that propagated through other stable branches after some massaging due to different structure...17:26
marexdenix: so the mixin kernel layer would take linux 5.10 (.0) and then take backports from linux-stable which is all backports of stable fixes to linux 5.10 anyway ?17:27
marexmaybe I don't quite understand this policy17:27
denixsure, 3 months delay is my fault. but don't expect rolling updates. zeddii makes updates to 5.10 about once a month or even less - last update was over a month ago - March 2217:28
marexthose updates could be automated with a 10 line script or AUH17:29
marexI think oe-core does that already17:29
denixmarex: backport policy is due to testing - only commits that went into oe-core master are being tested, plus commits that went into stable branches like hardknott, honister, gatesgarth get some testing too17:30
*** amahnui <amahnui!uid502939@id-502939.tinside.irccloud.com> has quit IRC (Quit: Connection closed for inactivity)17:30
marexdenix: but we're not talking about oe-core here, the mixin layers are supposed to provide up-to-date software for older OE releases17:32
marexdenix: does that mean the mixin layers are assembled from commits which are in newer oe-core releases ?17:32
denixmarex: yes, check for yourself - https://git.yoctoproject.org/meta-lts-mixins/log/?h=dunfell/kernel17:34
denixsince mixin layers don't have their own QA17:34
marexI see, I think I will stick to rolling my own then, it runs through multiple CI instances and it is kept up to date with linux-stable and mesa releases17:36
marexwould it make sense to somehow have something more "rolling" more official ?17:36
denixmarex: there's 5.10.112 already, but master has 5.10.109 and hardknott only has 5.10.10717:36
denixyes, if you need the very latest "rolling", right now you have to do it yourself17:37
denixmarex: how about adding dunfell branch to meta-linux-mainline?17:38
marexdenix: what's meta-linux-mainline ?17:38
denixmaybe you can offer paulbarker maintenance help with dunfell branch17:39
denixmarex: https://sr.ht/~pbarker/meta-linux-mainline/17:39
marexdenix: oh, that, I tried talking to paul before, but it got nowhere17:39
marexit seems like there is demand then, everyone is rolling their own thing, none of it is really upstream17:40
denixheh, and everyone is calling it linux-stable_5.10.bb :) I thought you were using meta-linux-mainline at least, but apparently that's completely your own?17:44
denixmarex: what's the demand for the very cutting-edge stable release? I can only see 2 reasons - a timely security fix or you are part of stable development17:48
*** florian_kc <florian_kc!~florian@dynamic-002-244-157-026.2.244.pool.telefonica.de> has quit IRC (Ping timeout: 272 seconds)17:49
marexdenix: no, the layer I use actually predates the one from paul17:55
marexdenix: paul apparently did something similar later17:56
marexalso, the layer from paul is outdated too ...17:56
marexI dont see any reason to use it17:56
denixmarex: yeah, I understand18:01
*** florian_kc <florian_kc!~florian@dynamic-002-244-157-026.2.244.pool.telefonica.de> has joined #oe18:01
marexdenix: and its not just kernel, I also have up to date mesa there, which is needed for various drivers18:02
denixmarex: it all boils down to testing. sure, you can completely rely on kernel stable testing, but we've seen issues and platforms not booting with such updates in yocto QA18:03
marexdenix: well could AUH and the QA help spot such bad updates and report/skip them ?18:07
marexthat could all be automated, right ?18:07
paulbarkermarex: up-to-date url: https://github.com/unnecessary-abstraction/meta-linux-mainline18:14
denixmarex: there are no official builds or tests for dunfell+5.10 at all, since Yocto QA is at the limit with existing builds and releases. ask RP about all the intermittent issues, mosly in ptest or qemu - that's why kirkstone had to be rebuilt and re-tested 3 times...18:15
*** Notgnoshi <Notgnoshi!~quassel@184-83-133-77-dynamic.midco.net> has joined #oe18:26
marexoh well18:32
*** kanavin_ <kanavin_!~Alexander@62.117.23.44> has quit IRC (Remote host closed the connection)18:50
*** kanavin_ <kanavin_!~Alexander@2a02:2454:29b:3b00:d35d:e3cf:58b5:748b> has joined #oe18:50
*** BCMM <BCMM!~BCMM@user/bcmm> has joined #oe19:46
jeroen_for what is worth, autoconf has an -f option, which seem to help..20:03
*** florian_kc <florian_kc!~florian@dynamic-002-244-157-026.2.244.pool.telefonica.de> has quit IRC (Ping timeout: 272 seconds)20:25
*** jeroen_ <jeroen_!~jeroen@2001:1c01:3bc5:4e00:e791:efe6:bf00:7133> has quit IRC (Quit: Konversation terminated!)21:14
*** jeroen_ <jeroen_!~jeroen@2001:1c01:3bc5:4e00:e791:efe6:bf00:7133> has joined #oe21:20
RPmarex: I have wanted to do more cutting edge testing but we struggle to have the people to monitor it21:31
marexRP: with that meta-mainline-common, I just let a couple of CIs chew on it and if something breaks, I just fix it and move on21:32
marexbut all the users I am aware of are arm32 and arm6421:33
RPmarex: I have so many things I need to "just" fix already :/21:33
marexRP: in case of that layer, I am talking about me fixing it21:34
RPmarex: I think I was looking at the discussion from a different direction so I'll not go further :)21:37
* RP wonders why reproducibility builds are still failing on ubuntu1804-ty-3 21:38
jeroen_I pushed https://github.com/victronenergy/openembedded-core/commit/59c3a48d1102d388858452a3b788fdc08291f02c (for dunfell)21:39
jeroen_zeddii: you might like that, since it fixes a bug assigned to you, https://bugzilla.yoctoproject.org/show_bug.cgi?id=1468121:40
marexRP: I guess I might just be willing to keep an eye on those builds, because, well, I already do anyway21:46
marexRP: that's all I'm trying to say21:46
RPmarex: that is handy to know, I'll keep it in mind thanks. I would like to do something like than and I know some others would too21:47
marexRP: indeed22:00
*** amahnui <amahnui!uid502939@id-502939.tinside.irccloud.com> has joined #oe22:10
*** florian_kc <florian_kc!~florian@dynamic-002-244-157-026.2.244.pool.telefonica.de> has joined #oe22:21
*** BCMM <BCMM!~BCMM@user/bcmm> has quit IRC (Ping timeout: 240 seconds)22:45
*** florian_kc <florian_kc!~florian@dynamic-002-244-157-026.2.244.pool.telefonica.de> has quit IRC (Ping timeout: 272 seconds)22:59
*** sgw <sgw!~swold_loc@user/sgw> has joined #oe23:27

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