**** BEGIN LOGGING AT Thu Feb 11 02:59:57 2021 Feb 11 12:42:13 JPEW: any chance you are awake? Feb 11 14:34:36 Crofton|cloud: I am now Feb 11 14:47:53 heh Feb 11 14:48:18 So I ran pyrex and ran into this Feb 11 14:48:35 setpriv: libcap-ng is too old for "all" caps Feb 11 14:48:45 so poking around, you build this in the container Feb 11 14:49:04 I suspect I need to update that lib and maybe util-linux and rebuild the container Feb 11 14:49:18 how do I convince pyrex to rebuild the container? Feb 11 14:49:55 Crofton|cloud: Which container are you using (if you don't know, it's the default)? Feb 11 14:50:07 deafult Feb 11 14:50:15 podman on fedora though Feb 11 14:50:41 Crofton|cloud: That *shouldn't* matter Feb 11 14:50:49 of course Feb 11 14:50:54 You need a 20.04 container probably? Feb 11 14:50:59 (the default is 18.04 Feb 11 14:51:14 probably default or older :) Feb 11 14:52:00 Crofton|cloud: You can set the container version in pyrex.ini Feb 11 14:52:01 gotta run Feb 11 14:52:15 We have all the LTS from 14.04 - 20.04 Feb 11 14:53:15 Ack, I can't build new ones as apparently travis says I'm out of credits :( Feb 11 14:53:52 back :) Feb 11 14:54:01 hmm Feb 11 14:54:24 so I am pulling the prebuilt container Feb 11 14:54:33 By default, yes Feb 11 14:54:51 If you want to build your own try this: https://github.com/garmin/pyrex/blob/master/DEVELOPING.md#building-images-locally Feb 11 14:55:36 ok Feb 11 14:55:43 I need to go hoe, then I will try this Feb 11 14:55:57 if it works, I'll send pull request Feb 11 14:55:58 :) Feb 11 14:56:41 Thanks! Feb 11 14:57:02 Hopefulyl this works, I am having the build old releases on new fedora issue Feb 11 14:57:17 Crofton|cloud: That's what it's designed to do Feb 11 14:57:20 and this happens to me a bunch Feb 11 14:57:53 back in a bit Feb 11 16:31:31 JPEW: still getting this message: setpriv: libcap-ng is too old for "all" caps Feb 11 16:32:26 Oh, sorry.... j/s Feb 11 16:32:29 https://www.irccloud.com/pastebin/S99clStd/ Feb 11 16:39:02 Crofton|cloud: Can you send me your pyrex.ini Feb 11 16:43:36 Crofton|cloud: Also, FYI if you change things in the pyrex.ini file, you need to exit and reinitialize the build environment. It won't see the changes unless you do that Feb 11 16:44:43 hmm Feb 11 16:45:48 what do you mean by exit the build env Feb 11 16:45:54 I don't think it starts :) Feb 11 16:46:17 Oh, right :) Feb 11 16:46:41 this happens sourcing the init file Feb 11 16:47:21 https://www.irccloud.com/pastebin/XzpRjP4S/ Feb 11 16:49:07 That's bizzare that it's doing that for an 18.04 image.... Feb 11 16:52:29 I wonder if it is interacting with a recent linux kernel on the F33 machine? Feb 11 16:52:39 caps/setpriv is ont my strength Feb 11 16:52:53 Crofton|cloud: Possibly, but that seems less likely Feb 11 16:53:05 Crofton|cloud: Can you send me your pyrex.ini file? Feb 11 16:54:19 Crofton|cloud: OOps sorry, I see you did Feb 11 16:55:09 Everything breaks for me this week Feb 11 16:59:33 * JPEW tries a build Feb 11 17:06:17 Well, for one thing I know why your patch doesn't work.... the locally compiled setpriv/libcap-ng only apply to 14.04 (not 18.04) Feb 11 17:06:39 Hmm.... I need to look at how libcap-ng handles all privledges Feb 11 17:07:41 hmmm Feb 11 17:07:52 maybe I should switch to 14.04? Feb 11 17:08:22 You should choose the image that works with whatever version of OE you are using (the sanity tested distro) Feb 11 17:12:49 so change the 18.04 to 14.04? Feb 11 17:13:15 Crofton|cloud: Ya Feb 11 17:14:35 https://www.irccloud.com/pastebin/glNmpOw5/ Feb 11 17:14:42 lol this is a good sign Feb 11 17:14:59 Heh, what version of OE are you trying to build? Feb 11 17:15:04 OK, need to try this on checlout that is barfing on python being python3 :) Feb 11 17:15:15 sumo I think Feb 11 17:15:27 semi random vendorware Feb 11 17:16:16 so I will have something that has oe-core bitbake and a few other layers in a directory Feb 11 17:16:23 will this work? Feb 11 17:16:36 I point env vars at oe and bitbake Feb 11 17:16:36 Ya, we build sumo with pyrex. j/s Feb 11 17:16:53 but the added layers, they will make it in? Feb 11 17:19:18 Yes. You have to make sure they are bound into the container. By default it will bind in everything under your init script Feb 11 17:26:13 Crofton|cloud: https://github.com/garmin/pyrex#binding-directories-into-the-container Feb 11 17:27:21 Ubuntu 18.04 is one of the tested distros for sumo, so I would use that Feb 11 17:33:26 Crofton|cloud: Ah ha! found it Feb 11 17:34:18 Crofton|cloud: https://github.com/karelzak/util-linux/commit/93de9f687d1640fff963f26b7db474eef3746532 Feb 11 17:34:38 So, we do need newer setpriv... need them on the newer distros too Feb 11 17:41:23 so how do I make 18.04 work? Feb 11 17:41:43 j/s and I'll send you a patch to try Feb 11 17:41:52 cool Feb 11 17:54:16 Crofton|cloud: https://github.com/garmin/pyrex/pull/54 You should just be able to `git fetch` and see the change on the branch Feb 11 17:54:50 I'm still running CI tests locally (takes a while), but it looks OK so far. Hopefully that fixes your problem Feb 11 17:55:33 ok, going to move to the machine where I need this to work and see what happens Feb 11 18:11:44 Crofton|cloud: Do you have a github username? Feb 11 18:12:12 balister Feb 11 18:12:15 boring I know Feb 11 18:19:02 this will be fun ./meta-foo ./meta-bar ./pky at same level :) Feb 11 19:04:54 Crofton|cloud: Ya, you'll probably want to write a custom init script Feb 11 19:11:25 container is still building on the roatting disk Feb 11 19:11:51 Crofton|cloud: Ya, it takes a while. podman isn't the fastest at building... docker buildkit is *much* better Feb 11 19:12:22 buildkit can skip the unused images in the Dockerfile so you only build what you actually need. It also builds in parallel Feb 11 19:14:24 Crofton|cloud: In our CI jobs we actually build the images in docker, then export them to podman for the podman tests, otherwise the CI jobs take to long Feb 11 19:16:50 JPEW/Crofton: Are there somewhere "for dummy" instructions how to use pyrex? Feb 11 19:17:10 the github readme Feb 11 19:17:33 RobertBerger: Ya, I tried to make the README pretty comprehensive, but if it needs more help let me know: https://github.com/garmin/pyrex Feb 11 19:21:02 Thanks! Feb 11 19:40:52 JPEW: "For example … commands that run in OE_TERMINAL are all supported since there is no other way to easily run them outside the bitbake environment" Feb 11 20:00:46 tlwoerner: Err, not sure what you're pointing out there :) Feb 11 20:01:41 JPEW: that sentence (from the README file at https://github.com/garmin/pyrex) sounds strange Feb 11 20:02:15 it _feels_ like it was about to say "these commands are *NOT* supported…" Feb 11 20:02:34 ? Feb 11 20:04:27 i'm just wondering if i'm readying that wrong Feb 11 20:09:41 JPEW: OK build running. So you need to do something to update the containers so I do not need to build it all the time? Feb 11 20:11:28 Crofton|cloud: Ya, I'll publish images. It's going to take a little longer since I have to do it manually instead of letting TravisCI do it Feb 11 20:11:48 cool Feb 11 20:11:52 Tomorrow? Feb 11 20:12:03 Ya Feb 11 20:12:06 ok Feb 11 20:12:13 just needed rough timeframe Feb 11 20:12:54 hopefully us talking about it gets a few more people to try it Feb 11 20:13:01 Hopefully :) Feb 11 20:13:32 definitely will help me move off the old build machine and let me update it from Fedora-Ancient Feb 11 20:21:15 tlwoerner: No, it's correct. Those tools are some of the exceptions that are supposed to still work properly Feb 11 20:22:10 tlwoerner: Pyrex isn't designed to allow to run e.g. vim inside the container and be a complete development environment Feb 11 20:22:40 i imagine trying to get xterm from inside to show up outside would be a pain in the ass anyway :) Feb 11 20:23:12 kergoth, tlwoerner: Right. Normally no "interactive" stuff. Those are the exceptions to that rule because you can't really do those any other way Feb 11 20:23:44 great thanks :-) Feb 11 20:25:47 i know we're all dying from email overload, but would it make sense to create a separate mailing list for event planning? i.e. to gather together the people who would be interested in planning an event without LF? Feb 11 20:26:54 tlwoerner: I think the oe-members list would be a good place for that? Feb 11 20:33:19 between https://www.openembedded.org/wiki/Mailing_lists and https://www.yoctoproject.org/community/mailing-lists/ i don't see one named oe-members Feb 11 20:33:37 * tlwoerner is going senile Feb 11 20:39:43 um you are looking on the yp page? Feb 11 20:40:14 yp members are corporations, oe members are people Feb 11 20:41:24 i'm looking at both the OE and YP mailing list pages Feb 11 20:42:17 hmmm, maybe not public Feb 11 20:42:36 I don't see it listed on groups.io Feb 11 20:43:15 might be hiding Feb 11 21:06:26 any other nominations? preferably a list people have heard of? ;-) Feb 11 21:09:40 @tlwoerner: I heard you can buy such lists with names and e-mails from shady places ;) Feb 11 21:11:17 lol Feb 11 21:24:41 JPEW: OK, so it works great, accept it can't fetch from a server I see via vpn Feb 11 21:25:51 possibly because I brought the env up before the vpn Feb 11 21:39:37 Crofton|cloud: Possibly. It uses the --net=host option in the container so it *should* see all the same networking as the host Feb 11 21:39:59 how do I restart things? Feb 11 21:42:46 The container is transient, so it "restarts" every time you run a command... so it actually shouldn't really need a "restart" just run the next command Feb 11 21:42:49 Whats the error? Feb 11 21:49:11 Host key verification failed. Feb 11 21:49:28 https://www.irccloud.com/pastebin/nB2TPei1/ Feb 11 21:49:47 but works from command line Feb 11 21:50:57 might should read fetcher docs Feb 11 21:51:46 Ah, you need to bind in your ssh keys Feb 11 21:51:57 I should add an example for that Feb 11 21:54:04 in your pyrex.ini add `${env:HOME}/.ssh` to `run:bind` Feb 11 21:56:28 agreed Feb 11 21:57:39 https://www.irccloud.com/pastebin/OS4Wr3Er/ Feb 11 21:57:46 so look slike that? Feb 11 21:58:13 Yep Feb 11 21:58:48 I mis being able to know more than a few things at once :) Feb 11 21:59:53 same problem .... Feb 11 22:00:01 How do I get it to read the ini file? Feb 11 22:00:35 exit the shell and re-run `. pyrex-init-build-env` Feb 11 22:01:02 But, things in the [run] section *shouldn't* need that Feb 11 22:01:15 hmm Feb 11 22:01:37 I need to set the vars again Feb 11 22:02:08 Did you accidently overrwrite the pyrex.ini file? Feb 11 22:02:22 no the root path vars Feb 11 22:18:22 Crofton|cloud: Ok, Pyrex v1.2.0 has just been released, which should have that fix in it Feb 11 22:21:07 thanks **** ENDING LOGGING AT Fri Feb 12 02:59:56 2021