ndec changed the topic of #yocto to: "Welcome to the Yocto Project | Learn more: https://www.yoctoproject.org | Join us or Speak at Yocto Project Summit (2022.05) May 17 - 19, more: https://yoctoproject.org/summit | Join the community: https://www.yoctoproject.org/community | IRC logs available at https://www.yoctoproject.org/irc/ | Having difficulty on the list or with someone on the list, contact YP community mgr ndec"
jclsn has quit [Ping timeout: 240 seconds]
kp7299[m] has joined #yocto
jclsn has joined #yocto
goliath has quit [Quit: SIGSEGV]
Circuitsoft has joined #yocto
RobertBerger has joined #yocto
rber|res has quit [Ping timeout: 272 seconds]
Tokamak has quit [Read error: Connection reset by peer]
starblue has quit [Ping timeout: 240 seconds]
Tokamak has joined #yocto
starblue has joined #yocto
<rfs613> any gurus still awake? am looking for a way to set CXXFLAGS in a recipe prior to calling ./configure script. I see EXTRA_OECONF but that seems to be for appending arguments like --with-foo
<rfs613> i tried doing 'export CXXFLAGS = ".."' in the recipe, but the native.bbclass is overriding my assignment with ${BUILD_CXXFLAGS}
sakoman has quit [Quit: Leaving.]
jclsn has quit [Quit: Ping timeout (120 seconds)]
jclsn has joined #yocto
locutusofborg_ has joined #yocto
LocutusOfBorg has quit [Ping timeout: 248 seconds]
jclsn has quit [Ping timeout: 256 seconds]
<rfs613> never mind, i managed to kludge something...
jclsn has joined #yocto
sakoman has joined #yocto
jclsn has quit [Ping timeout: 250 seconds]
jclsn has joined #yocto
amitk has joined #yocto
kroon has joined #yocto
<Saur[m]> rfs613: Either add to `BUILD_CXXFLAGS` or use `CXXFLAGS:append`, which is more appropriate depends on the situation.
<kp7299[m]> Hi all, I'm Komal Pal, I'm outreachy aspirant,working for final contribution, looking forward for guidance in this journey
sakoman has quit [Quit: Leaving.]
alessioigor has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
OutBackDingo has quit [Ping timeout: 248 seconds]
geoffhp has quit [Ping timeout: 260 seconds]
alessioigor has quit [Quit: alessioigor]
OutBackDingo has joined #yocto
rfried has quit [Quit: Ping timeout (120 seconds)]
rfried has joined #yocto
Vonter has quit [Quit: WeeChat 3.5]
kranzo has joined #yocto
locutusofborg_ is now known as locutusofborg
locutusofborg has joined #yocto
locutusofborg has quit [Changing host]
willo has quit [*.net *.split]
<kp7299[m]> ross: Hi Ross, if I have not mistaken you as outreachy mentor Ross Burton and if mistaken as I'm new then sorry in prior 😅, I just wanted to ask as per project description I was unable to get about building freebsd, as I was only able to steps for running yocto project in freebsd in internship steps for outreachy
frieder has joined #yocto
rfuentess has joined #yocto
mvlad has joined #yocto
mckoan|away is now known as mckoan
Guest21 has joined #yocto
Schlumpf has joined #yocto
manuel1985 has joined #yocto
gsalazar has joined #yocto
Guest3774 has joined #yocto
camus has joined #yocto
florian has joined #yocto
Guest3774 has quit [Client Quit]
<RP> kp7299[m]: Hi! I think you want rburton and I think he may be on vacation until next week
tnovotny has joined #yocto
<qschulz> amahnui[m]: don't need to stage the differences, the output of diff -u a b just needs to be sent to the docs mailing list so we can review it. It is fine if it's not following the proper git send-mail process, because like you said, there's no git repo for it.
Vonter has joined #yocto
<qschulz> amahnui[m]: just add the content of the diff inside your mail (not as an attachment please) and tell us against which tarball/archive this diff should be applied
<qschulz> amahnui[m]: in the meanwhile, this looks promising, so good job :)
<jclsn> Why is this bug not assigned? https://bugzilla.yoctoproject.org/show_bug.cgi?id=13353
<jclsn> It is three years old...
<qschulz> jclsn: I guess you're volunteering then :)
<jclsn> I suck at Python...
<jclsn> But well, I would love to code for a change
<jclsn> Will see if I can make time in the upcoming sprint
<kp7299[m]> <RP> "kp7299: Hi! I think you want..." <- Ok Thanks for info :) , Actually I'm just starting my contribution for outreachy and regarding the yoctoproject I had already cloned that repo on linux operating system but never on FreeBSD, so in all that sense if I required initial help too, either I'll ping here then
leon-anavi has joined #yocto
<qschulz> kp7299[m]: amahnui[m] is also looking into freebsd stuff as an outreachy aspirant (just for your information)
<qschulz> hello and welcome to the Yocto Project community
* qschulz waves
<LetoThe2nd> yo dudX
<kp7299[m]> <qschulz> "kp7299: amahnui[m] is also..." <- When amanhnui has started , means was at that time when Ross was there, then I hope would have been done with initial steps😅
alicef_ has joined #yocto
<RP> kp7299[m]: if you have yocto specific questions you can ask and we might be able to help. We're not much good with freebsd though
alicef has quit [Remote host closed the connection]
florian has quit [Read error: Connection reset by peer]
florian has joined #yocto
creich_ has quit [Quit: Leaving]
creich has joined #yocto
xmn has quit [Quit: ZZZzzz…]
mihai has joined #yocto
<RP> kanavin: I'm going to leave the revert on kirkstone and we can think about the B&W fallback icons on master when we decide what to do with sato
<kanavin> RP: right, I'm fine with that
creich has quit [Quit: Leaving]
<RP> kanavin: does "utilities-terminal" fix the missing rxvt one with the revert? That might be worth tweaking on kirkstone. I'd forgotten we had all our own desktop files :/
<RP> It is a shame we don't have the svgs for the original sato icon theme
<kanavin> RP: rxvt had a broken icon even with 41.0
<RP> kanavin: I know, I was wondering if we should fix it
<kanavin> RP: you can see it if you run 'runqemu kvm nographic', the warnings about missing icons would printed there mixed in with console login prompt
<RP> kanavin: it just irritates me and I think I see the fix in your patch :)
<kanavin> RP: there's a patch for removing bogus puzzles app too
<kanavin> net-4d82 something
<RP> kanavin: a patch for puzzles where?
<kanavin> RP: sorry a fix inside the patch
<RP> kanavin: oh, right. That should be a separate patch
<RP> kanavin: plan B - I think I might have the old sato icon svgs
<kanavin> RP: right, that'd be much nicer
<kanavin> RP: those symbolic icons are really rudimentary
<RP> kanavin: took a bit of digging but I found them. Just need to work out how to get them into sato-icon-theme
<RP> michaelo[m]: Should I push that transition docs patch?
ardo has quit [Read error: Connection reset by peer]
ardo has joined #yocto
<RP> kanavin: not sure it is a better plan, I think these old icons may be too dated and simplistic. Still trying to work out how to test them
Guest21 has quit [Quit: Client closed]
<qschulz> RP: I can't make sense of the switchers.js on https://docs.yoctoproject.org/2.7/
<qschulz> why does it have 2.7.4 listed in the all_versions?
rfuentess has quit [Remote host closed the connection]
<qschulz> and more importantly, why are they not consistent between versions of the docs, we are supposed to copy it from the master branch into all other branches in yocto-autobuilder-helper..
<RP> qschulz: no, we don't do that anymore, I changed that
<RP> qschulz: 2.7.4 was the last point release in that series
<qschulz> RP: we still do?
<RP> qschulz: we don't
<qschulz> RP: ah, bitbake only :)
<qschulz> ok, so a bug in set_versions.py somewhere trigegrs this behavior :)
<RP> qschulz: which behaviour? We merged a change which shows the latest point release in a series
<qschulz> the version selection shows:
<qschulz> dev, 3.4.3, 3.3.5, 3.1.15, 3.2.4, 3.2.3, 3.2.3
<RP> so the duplication?
<RP> that is a bug
<qschulz> but we still want to show 3.2.4?
<qschulz> even if it's obsolete?
<RP> qschulz: yes, as it is the version you're looking at
<qschulz> no, I'm looking at 3.2.3
<qschulz> so I'd expect 3.2.3 to appear yes
<RP> oh, sorry, I misread. We show the latest in that series as a hint too
<qschulz> but not the duplicate, nor 3.2.4
<RP> 3.2.4 should be there, that was intended
<qschulz> ah
<qschulz> well, I need to scrap the nice commits I just wrote then :(
<qschulz> I anticipated that all-versions would only have supported versions
<qschulz> (the issue right now is that 3.2.4 is not shown as obsolete on the docs)
kranzo has quit [Quit: Client closed]
<RP> qschulz: I'd tried to make this clear in the discussions we had on the docs list :/
<amahnui[m]> kp7299: I could help you set up your freebsd environment if you don't mind. but yocto is not support by freebsd yet.
<RP> qschulz: 3.2.4 should indeed be marked as obsolete
<kp7299[m]> If that is the case, then how we would contribute amahnui as per yoctoproject on freebsd
<qschulz> RP: I don't have the best memory and I deal with too many different projects right now and Yocto is one of the least used ones unfortunately :/ So, sorry if I rediscover things over and over again, it wasn't on purpose :)
starblue has quit [Ping timeout: 248 seconds]
<amahnui[m]> qschulz: I will do that right away, I had a bad network lately
<RP> qschulz: np, I didn't mean it like that, I was just saying I thought we'd agreed it!
<qschulz> RP: oh maybe we did :)
starblue has joined #yocto
<RP> kanavin: https://git.yoctoproject.org/poky-contrib/commit/?h=rpurdie/t222&id=eb3b2a0cfc3fda98447893c7018a771bf9e96de1 kind of works for the icon. Not sure what I think though
<qschulz> kp7299[m]: I haven't read the outreachy intern project but I assume the point is to actually support building Yocto on FreeBSD and we have no support right now
<RP> kanavin: not even sure it is using the svgs there as yet but the base files are there
<amahnui[m]> kp7299: I think freebsd comes in but during the internship period and we just need to be versed with it now and have knowledge on how it functions.
<kanavin> RP: I wonder if it's better to transition to weston, use symbolic icons from adwaita keep sato testing to a minimum (basically one AB job in a-full), and then let it bitrot
<kanavin> which is kind of the patchset I'm going to propose anyway
<kp7299[m]> Ok, means we just need to set up the freebsd for time being and get familiar with yoctoproject as it cant be installed on freebsd for time being...
<amahnui[m]> RP: qschulz ndec : The patch will be going to the docs@lists.yoctoproject.org right?
<ndec> yes.
<amahnui[m]> kp7299: I think so, while contributing too so you can create a final application.
<kp7299[m]> RP: qschulz amahnui So you all three are participating in outreachy?
<kp7299[m]> amahnui[m]: ok, got it
<RP> kp7299[m]: I'm one of the Yocto Project maintainers, qschulz is one of our contributors too, we're not outreachy. I believe amahnui[m] is though
<amahnui[m]> kp7299: just me some other applicants but I don't know their usernames here if they are on irc except @@Gina:libera.chat
<ndec> and btw.. I am one of the outreachy organizer for yocto.. so if i can help with anything let me know. we are very happy to be participating in outreachy and having you here as applicants!
<kp7299[m]> Sure, would ask, but presently the way other projects have repo where issues being visible separately so is here something like that, I was just able to see this: https://git.openembedded.org/ which is way different than Github repo
<ndec> yes, for yocto (and OE) we are using our own infrastructure for git and issue tracking, we are not using github.
Circuitsoft has quit [Quit: Connection closed for inactivity]
<amahnui[m]> I just sent a patch for the changes, Please I would like to request for a review and corrections for it.
florian has quit [Read error: Connection reset by peer]
florian_kc has joined #yocto
<amahnui[m]> * Hi qschulz: RP: ndec: I just
bonalais has joined #yocto
<ndec> amahnui[m]: thanks, I confirm that the patch hit the list, and I received it , well done :)
florian_kc has quit [Read error: Connection reset by peer]
florian__ has joined #yocto
<qschulz> RP: ok, I think I got the docs warning messages for gatesgarth releases and the dropdown menu duplicate fixed
Schlumpf has quit [Quit: Client closed]
<amahnui[m]> ndec: please how do I proceed. Did I do it right?
<RP> qschulz: Just curious what testing you did? (so I don't duplicate)
florian__ is now known as florian
kroon has quit [Quit: Leaving]
codavi has joined #yocto
ar__ has joined #yocto
goliath has joined #yocto
<qschulz> RP: comment the ./set_versions.py in Makefile, then make clean && ./set_versions.py $VERS && make html
<qschulz> I tested 3.0.1, 3.0.4, 3.1.14, 3.2.3, 3.2.4
<qschulz> amahnui[m]: just wait, there'll be reviews by mail in a few days
<qschulz> if not, then after a week or so, you can reply to the mail and say that youre just making sure we haven't forgotten about it
codavi has quit [Ping timeout: 272 seconds]
<amahnui[m]> RP: okay thanks.
<amahnui[m]> I will do just that.
neverpanic has quit [Ping timeout: 260 seconds]
<amahnui[m]> ndec: can I record this a
<amahnui[m]> * record this as a, * a contribution?
<ndec> amahnui[m]: yes, you can . It's a weird one, since it won't show up in the yocto/oe trees directly, but it's a good and important contribution to the docs website :)
neverpanic has joined #yocto
<amahnui[m]> ndec: thanks, I will.
troth has quit [Quit: Leaving.]
gsalazar has quit [Remote host closed the connection]
<amahnui[m]> Also the information on the outreachy portal said that there is a freebsd co mentor, Please I would like to know if I could get in contact with them.
gsalazar has joined #yocto
Schlumpf has joined #yocto
gsalazar has quit [Ping timeout: 248 seconds]
<qschulz> ndec: ^ do you happen to know? RP mentioned rburton but he wasn't so sure (at least that's what I gathered from the phrasing) and rburton happens to be silent (on holiday?) today :)
<RP> I don't know who the comentor is. awafaa might?
troth has joined #yocto
Net147 has quit [Quit: Quit]
Net147 has joined #yocto
Net147 has joined #yocto
Net147 has quit [Changing host]
<RP> amahnui[m]: I just tested your patch and it looks good to me!
<RP> amahnui[m]: the docs build is make using this script: https://git.yoctoproject.org/yocto-autobuilder-helper/tree/scripts/run-docs-build
<RP> amahnui[m]: you can see where it is extracted on line 30. I think we can add this patch to that git repository inside a /docbook-docs/ directory and have it apply inside that script as a next step?
<qschulz> RP: did you test in different responsive design modes too? (ctrl+shit+c and the tablet+phone icon on the top right of the bar that popped up)
<RP> qschulz: no
manuel1985 has quit [Ping timeout: 260 seconds]
manuel1985 has joined #yocto
<ndec> RP: qschulz : amahnui[m] : i don't think there is a comentor.. i will check the website, but i think it's not correct.
<RP> ndec: there was someone on the freebsd side
<ndec> well, then it was not properly requested to the outreachy website.
<qschulz> RP: :sob: why is it so bad (not talking about amahnui[m] work :) )
<RP> qschulz: so bad?
xmn has joined #yocto
<qschulz> RP: Galaxy S10 in portrait mode, it's WAY bigger than the screen width
<RP> qschulz: oh, I didn't dare look. It is old crusty docbook
<qschulz> RP: yeah, I probably shouldn't have looked :)
<RP> amahnui[m]: our choice now is whether to try and patch all the different doc html files or whether we can write a script which would patch them
<RP> amahnui[m]: we could run that script in the docs build at the point I mention
<RP> obviously it is much easier now we know what we need to change things to
tomzy_0 has joined #yocto
sakoman has joined #yocto
<amahnui[m]> RP: if we are to write a script will we use rust or shell?
chep has quit [Quit: ZNC 1.8.2 - https://znc.in]
<RP> amahnui[m]: Definitely not rust. Python would probably be easier than shell
<RP> amahnui[m]: I'll be happy if we just apply the patch in the script to one of the manuals for now, we can incrementally improve from there but I wanted to give you an idea of where this ultimately needs to get to
<amahnui[m]> RP: that means it will recursively add the code to the the .html and .css files in all the versions?
<qschulz> yup
<RP> amahnui[m]: exactly
chep has joined #yocto
<amahnui[m]> I will look for a way to do it.
<amahnui[m]> I'm having issues thinking of how to do so to a file that contains code already.
bonalais has quit [Quit: Connection closed for inactivity]
amitk has quit [Ping timeout: 256 seconds]
bonalais has joined #yocto
<jonmason> does anyone know how to get poky-tiny to start sshd by default? I'm trying to automate the testing (via testimage) and this is stumping me
<RP> jonmason: does poky-tiny have sshd installed?
<RP> jonmason: I think it was always serial only?
<jonmason> RP: yes, I can run it by hand, but its not autostarting
<RP> jonmason: interesting. Probably the minimal init not working then?
<jonmason> yes, I debated switch it out but that is a different PITA :)
<jonmason> I didn't know if there was a trick to it or if it is broken
<qschulz> amahnui[m]: in the end what you need to do in the html is insert a div, so with the appropriate regex it should be possible to find the place where to inject it and then do it (e.g. with sed or awk if you go for shell commands)
<RP> jonmason: I suspect the latter sadly
xmn has quit [Ping timeout: 256 seconds]
<RP> Does anyone know of anything which should be in kirkstone which isn't for an rc2?
<jonmason> RP: all good. As soon as I get this working properly, it'll be part of the nightly meta-arm regression testing
<RP> sakoman? abelloni?
<sakoman> RP: I'm here
<jonmason> RP: qemuarm tiny enablement ;-)
<RP> sakoman: anything I'm missing for kirkstone rc2?
tlwoerner has quit [Read error: Connection reset by peer]
<moto-timo> kanavin: did you stage a python3.11 anywhere?
<RP> jonmason: too late ;-)
<jonmason> lol
<RP> moto-timo: no, we're not talking python 3.11 :)
<sakoman> RP: not that I am aware of
<RP> moto-timo: I know you didn't mean that
<moto-timo> RP: alpha7 for the win!
GNUmoon has quit [Remote host closed the connection]
GNUmoon has joined #yocto
<smurray> RP: a fix for the bluez + systemd issue would be useful, but it seems upstream are still deciding on what they want as a fix
tomzy_0 has quit [Quit: Client closed]
<RP> smurray: right, I think we'd best wait until that is resolved
<RP> it can come in a point release
<smurray> RP: it breaks us in AGL, so we'll have to carry a patch
<RP> smurray: hmm. Is the fix ready though?
<RP> smurray: or are you saying we should wait?
<qschulz> amahnui[m]: if you are ever looking for another HTML/CSS task, having the warning header on the new docs website stick at the top of the viewport would be awesome too. It should be done in this javascript script: https://git.yoctoproject.org/yocto-docs/tree/documentation/sphinx-static/switchers.js.in#n225
<smurray> RP: a single line added to the systemd unit fixes it, the upstream discussion seems to be about the intent of the original breaking change
<RP> smurray: it is far from clear what I should be merging :/
<smurray> RP: at least in my testing here, just adding StateDirectory=bluetooth allows it to start, that's what I'll carry in a systemd drop-in file if there's no change in poky
Schlumpf has quit [Quit: Client closed]
<amahnui[m]> qschulz: thank you I will check it out too.
xmn has joined #yocto
florian has quit [Ping timeout: 250 seconds]
<awafaa> Sorry, I see I was mentioned but can't seem to find where/why (:
<qschulz> awafaa: who's the comentor for freebsd outreachy internship
<qschulz> was the question some thought you could be able to answer
<awafaa> ah, that would be Ed Maste - emaste on EFNet, not sure if he's on Libera.Chat
gsalazar has joined #yocto
<qschulz> amahnui[m]: kp7299[m]: ^
<amahnui[m]> Thank you I will try contacting him there.
GLumen has joined #yocto
florian has joined #yocto
Tokamak has quit [Ping timeout: 256 seconds]
<vvn> hi there -- I use a host tool to package a firmware update, which needs a target file in deploy dir. How do I append foo-native to deploy a target file?
<LetoThe2nd> vvn: its just not foo-native that deploys it, but your firmware update packaging recipe DEPENDS on foo-native and uses it.
<vvn> I see
<RP> smurray: I'm going to hold off that, we can fix in the point release once there is a clear decision
<smurray> RP: okay, you may want to document it being broken for the release notes
<vvn> LetoThe2nd: didn't work, I add to explicitly add do_image_wic[depends] += "foo:do_deploy"
<smurray> RP: I guess the poky-altcfg testing is limited, so it doesn't manage to get tripped up by it?
<RP> smurray: is there a summary you could share with me of the issue and the mitigation? I still don't have it straight in my head
<RP> smurray: it doesn't find the issue, I don't know whether it should or if there is some corner case in testing we should be adding
<LetoThe2nd> vvn: well of course the dependency chain needs to be intact. however you do that, there are variations.
<smurray> RP: bluez fails to start if you have INIT_MANAGER=systemd, as it wants to create a directory and is prevented by the ProtectSystem=full that was added to the unit
<smurray> RP: hence the original suggested patch on the list being to create that directory during packaging
<RP> smurray: I guess we had better do something about this
jaydeep51[m] has quit [Quit: You have been kicked for being idle]
<smurray> RP: I was hoping upstream would merge something we could pull out as a patch, but they're not moving that quickly
<RP> smurray: so I patch bluez to add ConfigurationDirectory=bluetooth +StateDirectory=bluetooth
<smurray> RP: I think the configuration directory happens to already exist, but both would be good to be safe, yes
* RP doesn't even have a build easily available to test :(
<smurray> yeah, I missed it until I started doing more AGL testing of the kirkstone build on h/w
xmn has quit [Quit: xmn]
manuel1985 has quit [Remote host closed the connection]
<smurray> RP: I can cook up a patch and send it as a reply to the thread on oe-core
florian has quit [Ping timeout: 240 seconds]
manuel1985 has joined #yocto
mckoan is now known as mckoan|away
<RP> smurray: I think I have one but I am just guessing :/
<RP> smurray: does that look right?
<smurray> RP: I don't believe you need to remove the Read{Only,Write}Path directives, but I'd need to dig in systemd to see if it honors them when you also specify {Configuration,State}Directory
<smurray> RP: in my testing here I left those alone and just added StateDirectory=bluetooth
<RP> smurray: I was going off comments in that bug
<smurray> RP: yeah, I wasn't sure how definitive some of what's said there is
<smurray> RP: I can test your patch, will take me half-hour - hour to shift gears and get a build to put on a board to check
<RP> smurray: so the version you've tested and know works doesn't have the deletions?
<smurray> RP: effectively, yes, I just added StateDirectory on top with a drop-in here
<RP> smurray: so you didn't add ConfigurationDirectory either? :/
<smurray> RP: right
* RP now doesn't know what to do :(
<RP> I did have rc2 building but cancelled it as I'm sure I'll get complaints if I don't fix this
<RP> I'll get complaints when I get it wrong too
gsalazar has quit [Ping timeout: 240 seconds]
<smurray> RP: yes, it's less than ideal
<RP> smurray: I've posted it, I'll wait on your testing
<smurray> RP: another option would be to temporarily carry a revert of the 442d211 change, but that also seems not great
<RP> smurray: this is probably the best path forwards rather than the revert
nsbdfl has quit [Ping timeout: 256 seconds]
dtometzki has quit [Read error: Connection reset by peer]
dtometzki has joined #yocto
<smurray> RP: I think removing the Read*Paths directives w/o switching to ProtectSystem=strict disables the namespacing anyways, but I'll check that
<RP> smurray: ok, so the patch is wrong
<smurray> RP: I believe it'll work in that bluez will start, but the sandboxing is somewhat lesser
<RP> smurray: right, which isn't ideal
<smurray> RP: I'm getting a build to test, I can try ProtectSystem=strict on top and see if bluez works
<RP> smurray: thanks, much appreciated
nsbdfl has joined #yocto
abelloni has quit [Quit: leaving]
abelloni has joined #yocto
frieder has quit [Remote host closed the connection]
<kp7299[m]> <amahnui[m]> " Hi qschulz: RP: ndec: I just..." <- Hi Just figuring out, what sort of contribution it was, means was unable to get, like beside those things which were given there in the outreachy page, we could contribute to any other platform too supported by yocto project or what it was, just bit confused... As even I'm unable to get that where I could find link for issues ndec for contribution 😅
Tokamak has joined #yocto
<smurray> RP: so your patch works, and then doing s/ProtectSystem=full/ProtectSystem=strict/ on top also works (bluez starts, phone pairs, etc.). I nuked the /var/lib/bluetooth and restarted in between to double-check
Tokamak has quit [Ping timeout: 246 seconds]
<smurray> RP: and that matches what's proposed in https://github.com/bluez/bluez/issues/329#issuecomment-1098777892
jclsn6 has joined #yocto
fitzsim` has joined #yocto
override_ has joined #yocto
marcus__ has joined #yocto
dlan_ has joined #yocto
Tokamak has joined #yocto
Vonter has quit [*.net *.split]
jclsn has quit [*.net *.split]
dlan has quit [*.net *.split]
JPEW has quit [*.net *.split]
vmeson has quit [*.net *.split]
marcus_ has quit [*.net *.split]
tangofoxtrot has quit [*.net *.split]
fray has quit [*.net *.split]
fitzsim has quit [*.net *.split]
override has quit [*.net *.split]
svuorela has quit [*.net *.split]
erbo has quit [*.net *.split]
vquicksilver has quit [*.net *.split]
Tokamak has quit [Ping timeout: 240 seconds]
fitzsim` is now known as fitzsim
<kanavin> moto-timo, no, I usually don't start looking at python until it reaches rc stage, which is september-ish
<kanavin> don't want to shoot fast moving targets
<moto-timo> kanavin: fair enough... I might start with beta1 in may
Vonter has joined #yocto
JPEW has joined #yocto
tangofoxtrot has joined #yocto
svuorela has joined #yocto
vquicksilver has joined #yocto
erbo has joined #yocto
<kanavin> moto-timo, why so early? is there something particularly interesting?
* moto-timo wants the tomllib
florian has joined #yocto
fray has joined #yocto
vmeson has joined #yocto
Tokamak has joined #yocto
bonalais has quit [Quit: Connection closed for inactivity]
tlwoerner has joined #yocto
ardo has quit [Read error: Connection reset by peer]
ardo has joined #yocto
amitk has joined #yocto
zen_coder has joined #yocto
WRL_User has joined #yocto
<WRL_User> Hi, all. First time IRC user, so please be patient if I make a faux pas. I'm open to being steered in the correct direction.
Tokamak has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<WRL_User> I have a question about the meta-java layer from Yocto. At work, we're using Wind River Linux (WRL) 10.18, which is based on Yocto thud. WRL doesn't provide meta-layer, so we're using that directly from Yocto. I'm trying to figure out the best way to get more current versions of OpenJre8 (for runtime) and OpenJDK 8 and iced-tea7 for build time.
<zeddii> vmeson: ^^^^^^^^^^^^^^^
<WRL_User> Does anyone have any suggestions on the best way to include newer versions of java into out product?
<WRL_User> If this isn't the best place/manner to ask, I'll accept advice on a better place and/or manner.
amitk has quit [Ping timeout: 248 seconds]
Tokamak has joined #yocto
geoffhp has joined #yocto
<WRL_User> I just noticed my typo. I should have said "WRL doesn't provide meta-java, so we're using that directly from Yocto"
florian has quit [Ping timeout: 272 seconds]
<smurray> WRL_User: if you're stuck on WRL 10.18, you'll have to try backporting the recipes for newer versions from one of the newer branches in meta-java
<WRL_User> Thanks. I was afraid that was the right answer. I already tried just using a newer version and changing LAYERSERIES_COMPAT, and that didn't work.
<WRL_User> Would you recommend starting from just checking out a newer version, changing the LAYERSERIES_COMPAT, and resolving the errors? Or try merging specific recipe files into what I have?
<smurray> WRL_User: it's hard to say, tbh, there's a lot of moving parts in the JDK/JRE builds AIUI
<WRL_User> Thanks, again. I guess I'll just have to use old-fashioned elbow grease and determination then!
<WRL_User> Or convince my management to pay Wind River to do it for me :-)
<smurray> WRL_User: heh, exactly
<smurray> WRL_User: not that I recommend doing it in general, but you can tweak LAYERSERIES_COMPAT_layer in local.conf to avoid needing a local fork (though a fork might end up needed to tweak other things to work)
Tokamak has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<WRL_User> I'll keep that in mind, smurray. I'll try the old fashioned (more correct?) way for a bit, keeping that as a last resort.
Tokamak has joined #yocto
<vmeson> smurray: zeddii thanks. WRL_User: I agree with smurray and you wrt doing yourself, paying WR services . The other option is a 3rd party Java provider that some have worked with previously: Azul
<amahnui[m]> <kp7299[m]> "Hi Just figuring out, what..." <- For issue tracking , bugzilla is used for the yocto project. bugzilla.yoctoproject.org
<amahnui[m]> https://wiki.yoctoproject.org/wiki/Newcomers is where newcomer issues are found.
<vvn> Is kirkstone officially released?
<vmeson> vvn: no, RC1 had a few issues so RC2 is underway.
Tokamak has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<vvn> vmeson: thank you!
mvlad has quit [Remote host closed the connection]
alejandrohs has quit [Ping timeout: 248 seconds]
alejandrohs has joined #yocto
Tokamak has joined #yocto
<hushmoney> what is this syntax so that i can read about it? YAML_DT_BOARD_FLAGS_ultra96 ?= "{BOARD avnet-ulgra96-rev1}"
<hushmoney> BOARD is a variable the vendors asks me to specify in my local.conf
<vmeson> hushmoney: I could be wrong, but that seems to be something specifc to xilinx: https://lists.yoctoproject.org/g/meta-xilinx/topic/meta_xilinx_tools_patch/84943737?p=,,,20,0,0,0::recentpostdate/sticky,,,20,2,0,84943737,previd=1634663165200341028,nextid=1619105365533374721&previd=1634663165200341028&nextid=1619105365533374721
<hushmoney> it is a xilinx layer yes, thanks. i thought it was a yocto feature i didn't understand. thanks
<RP> smurray: thanks for confirming. I ended up stepping away for food and coming back
<vmeson> hushmoney: that email was about changing the _ to : (the overrides symbol) so the syntax is variable=YAML_DT_BOARD_FLAGS , override=ultra96 but I"m not sure what the intent is.
<smurray> RP: no worries
<RP> smurray: so do we want to update the patch to make it strict?
<hushmoney> vmeson: thanks thats okay. i don't need to understand it if it's something xilinx invented. i just thought if it was a yocto feature i would like to know about it in case i can use it later
* vmeson steps in a pahole and has trouble getting out: news uprevs, native recipes and who knows what else to make bcc happy it seems.
<vmeson> hushmoney: k
<smurray> RP: I'd say so, my reading of the systemd docs suggests it should give the originally desired sandboxing as herbrechtsmeier says in that comment on the github issue
vvn has quit [Quit: WeeChat 3.5]
<RP> smurray: ok. I'll have a second try at the patch.
vvn has joined #yocto
* RP powers up the build machine again
tnovotny has quit [Quit: Leaving]
manuel1985 has quit [Remote host closed the connection]
manuel1985 has joined #yocto
Tokamak has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<amahnui[m]> hi
Tokamak has joined #yocto
bonalais has joined #yocto
<vmeson> amahnui[m]: hello! What's up?
<amahnui[m]> Hi vmeson sorry I was just trying out how the `/` commands work.
leon-anavi has quit [Ping timeout: 250 seconds]
* vmeson nods
leon-anavi has joined #yocto
Tokamak has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
Tokamak has joined #yocto
leon-anavi has quit [Quit: Leaving]
manuel1985 has quit [Remote host closed the connection]
manuel1985 has joined #yocto
manuel1985 has quit [Client Quit]
Tokamak has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
WRL_User has quit [Quit: Client closed]
florian has joined #yocto
florian has quit [Ping timeout: 250 seconds]
tgamblin has quit [Remote host closed the connection]
tgamblin has joined #yocto
tgamblin_ has joined #yocto
tgamblin has quit [Ping timeout: 248 seconds]
bonalais has quit [Quit: Connection closed for inactivity]
<smurray> RP: I think your runqemu autodetect change is perhaps breaking specifying a backend, it seems to not be using the publicvnc option now and doing sdl
<smurray> RP: ah, looking at the logic, I'd guess it's that it doesn't consider publicvnc option, so the autodetect kicks in
dlan_ is now known as dlan
<smurray> RP: I've sent a patch to oe-core
dlan has joined #yocto
dlan has quit [Changing host]
<Saur[m]> RP: To answer your question from the other day if there is anything more that should go into the rc2, I just sent a patch for `shadow`. It solves a problem with useradd & friends spamming the host's syslog. A problem that was supposed to be fixed a month ago, but apparently wasn't. :(