IRC log for #oe on 20210211

00:03.05*** join/#oe florian (~florian_k@Maemo/community/contributor/florian)
00:47.07*** join/#oe B0ned1ger2 (~B0ned1ger@82-135-139-249.static.zebra.lt)
04:44.35*** join/#oe davidlt (~davidlt@78-63-27-146.static.zebra.lt)
04:47.11*** join/#oe B0ned1ger (~B0ned1ger@82-135-139-249.static.zebra.lt)
06:25.44*** join/#oe AndersD (~AndersD@h83-209-96-136.cust.a3fiber.se)
06:27.57*** join/#oe AndersD_ (~AndersD@h83-209-96-136.cust.a3fiber.se)
07:19.04*** join/#oe leon-anavi (~Leon@78.130.197.211)
07:38.57*** join/#oe florian (~florian_k@Maemo/community/contributor/florian)
07:39.44*** join/#oe frsc (~frsc@i6DFA8824.versanet.de)
07:42.55*** join/#oe rob_w (~bob@unaffiliated/rob-w/x-1112029)
08:09.58*** join/#oe cpriouzeau (~cpriouzea@165.225.94.93)
08:12.37*** join/#oe ao2 (~ao2@host-95-250-15-64.retail.telecomitalia.it)
08:12.39*** join/#oe JPEW (~JPEW@2605:a601:ac3d:c100:e3e8:d9:3a56:e27d)
08:40.52*** join/#oe vmeson (~rmacleod@198-48-226-187.cpe.pppoe.ca)
08:47.13*** join/#oe B0ned1ger2 (~B0ned1ger@82-135-139-249.static.zebra.lt)
08:56.56*** join/#oe LocutusOfBorg (~locutusof@ubuntu/member/locutusofborg)
09:04.01*** join/#oe eFfeM (~fmeulenbr@a97014.upc-a.chello.nl)
09:12.32*** join/#oe eFfeM (~fmeulenbr@a97014.upc-a.chello.nl)
09:43.10*** join/#oe B0ned1ger (~B0ned1ger@82-135-139-249.static.zebra.lt)
10:29.57*** join/#oe LetoThe2nd (uid453638@gateway/web/irccloud.com/x-qtdxemditucprzrt)
10:38.23*** join/#oe B0ned1ger2 (~B0ned1ger@78-60-213-230.static.zebra.lt)
10:57.15*** join/#oe B0ned1ger (~B0ned1ger@82-135-139-249.static.zebra.lt)
11:09.07*** join/#oe B0ned1ger2 (~B0ned1ger@78-60-213-230.static.zebra.lt)
11:19.43*** join/#oe florian (~florian_k@Maemo/community/contributor/florian)
11:34.27*** join/#oe davidlt (~davidlt@78-63-27-146.static.zebra.lt)
11:35.46*** join/#oe B0ned1ger (~B0ned1ger@82-135-139-249.static.zebra.lt)
12:06.49*** join/#oe eFfeM (~fmeulenbr@a97014.upc-a.chello.nl)
12:37.51*** join/#oe B0ned1ger (~B0ned1ger@82-135-139-249.static.zebra.lt)
12:42.13Crofton|cloudJPEW: any chance you are awake?
12:48.13*** join/#oe tgamblin (~tgamblin@cpe64777de11593-cm64777de11590.cpe.net.cable.rogers.com)
12:50.40*** join/#oe JPEW (~JPEW@2605:a601:ac3d:c100:e3e8:d9:3a56:e27d)
13:04.00*** join/#oe georgem_home (uid210681@gateway/web/irccloud.com/x-nvjxemiwugirtihv)
13:11.25*** join/#oe tgoodwin (~tgoodwin@static-96-234-151-198.bltmmd.fios.verizon.net)
13:16.38*** join/#oe florian (~florian_k@Maemo/community/contributor/florian)
13:39.05*** join/#oe B0ned1ger (~B0ned1ger@82-135-139-249.static.zebra.lt)
13:46.55*** join/#oe comptroller (~comptroll@47-213-222-227.paolcmtc01.res.dyn.suddenlink.net)
13:55.08*** join/#oe hpsy (~hpsy@196.158.133.128)
13:56.17*** join/#oe sakoman (~steve@72.173.249.164)
14:34.36JPEWCrofton|cloud: I am now
14:36.33*** join/#oe vmeson (~rmacleod@198-48-226-187.cpe.pppoe.ca)
14:37.10*** join/#oe RobertBerger (~rber@ppp-2-86-140-5.home.otenet.gr)
14:37.26*** join/#oe B0ned1ger (~B0ned1ger@82-135-139-249.static.zebra.lt)
14:47.54Crofton|cloudheh
14:48.18Crofton|cloudSo I ran pyrex and ran into this
14:48.35Crofton|cloudsetpriv: libcap-ng is too old for "all" caps
14:48.45Crofton|cloudso poking around, you build this in the container
14:49.04Crofton|cloudI suspect I need to update that lib and maybe util-linux and rebuild the container
14:49.18Crofton|cloudhow do I convince pyrex to rebuild the container?
14:49.55JPEWCrofton|cloud: Which container are you using (if you don't know, it's the default)?
14:50.07Crofton|clouddeafult
14:50.15Crofton|cloudpodman on fedora though
14:50.41JPEWCrofton|cloud: That *shouldn't* matter
14:50.49Crofton|cloudof course
14:50.54JPEWYou need a 20.04 container probably?
14:51.00JPEW(the default is 18.04
14:51.14Crofton|cloudprobably default or older :)
14:52.00JPEWCrofton|cloud: You can set the container version in pyrex.ini
14:52.01Crofton|cloudgotta run
14:52.15JPEWWe have all the LTS from 14.04 - 20.04
14:53.15JPEWAck, I can't build new ones as apparently travis says I'm out of credits :(
14:53.52Crofton|cloudback :)
14:54.01Crofton|cloudhmm
14:54.24Crofton|cloudso I am pulling the prebuilt container
14:54.33JPEWBy default, yes
14:54.51JPEWIf you want to build your own try this: https://github.com/garmin/pyrex/blob/master/DEVELOPING.md#building-images-locally
14:55.36Crofton|cloudok
14:55.43Crofton|cloudI need to go hoe, then I will try this
14:55.57Crofton|cloudif it works, I'll send pull request
14:55.58Crofton|cloud:)
14:56.41JPEWThanks!
14:57.02Crofton|cloudHopefulyl this works, I am having the build old releases on new fedora issue
14:57.17JPEWCrofton|cloud: That's what it's designed to do
14:57.20Crofton|cloudand this happens to me a bunch
14:57.53Crofton|cloudback in a bit
15:15.25*** join/#oe armpit (~armpit@2601:202:4180:a5c0:55f8:e3c0:af8d:902c)
15:22.03*** join/#oe hpsy (~hpsy@197.37.224.220)
15:34.59*** join/#oe B0ned1ger2 (~B0ned1ger@78-60-213-230.static.zebra.lt)
15:46.09*** join/#oe B0ned1ger (~B0ned1ger@78-60-213-230.static.zebra.lt)
15:47.52*** join/#oe B0ned1ger2 (~B0ned1ger@82-135-139-249.static.zebra.lt)
15:48.56*** join/#oe cristiano (~cris@pdpc/supporter/active/cristiano)
16:19.50*** join/#oe escanor (uid387784@gateway/web/irccloud.com/x-qhikrnlrvhwooqqu)
16:31.31Crofton|cloudJPEW: still getting this message: setpriv: libcap-ng is too old for "all" caps
16:32.26JPEWOh, sorry.... j/s
16:32.29Crofton|cloudhttps://www.irccloud.com/pastebin/S99clStd/
16:33.35*** join/#oe marex (~marex@83.167.232.23)
16:39.02JPEWCrofton|cloud: Can you send me your pyrex.ini
16:43.36JPEWCrofton|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
16:44.43Crofton|cloudhmm
16:45.48Crofton|cloudwhat do you mean by exit the build env
16:45.54Crofton|cloudI don't think it starts :)
16:46.17JPEWOh, right :)
16:46.41Crofton|cloudthis happens sourcing the init file
16:47.21Crofton|cloudhttps://www.irccloud.com/pastebin/XzpRjP4S/
16:49.07JPEWThat's bizzare that it's doing that for an 18.04 image....
16:52.29Crofton|cloudI wonder if it is interacting with a recent linux kernel on the F33 machine?
16:52.39Crofton|cloudcaps/setpriv is ont  my strength
16:52.53JPEWCrofton|cloud: Possibly, but that seems less likely
16:53.05JPEWCrofton|cloud: Can you send me your pyrex.ini file?
16:54.19JPEWCrofton|cloud: OOps sorry, I see you did
16:55.09Crofton|cloudEverything breaks for me this week
16:57.06*** join/#oe frieder_ (~frsc@i6DFA8824.versanet.de)
16:59.33JPEWtries a build
17:06.17JPEWWell, 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)
17:06.39JPEWHmm.... I need to look at how libcap-ng handles all privledges
17:07.41Crofton|cloudhmmm
17:07.52Crofton|cloudmaybe I should switch to 14.04?
17:08.22JPEWYou should choose the image that works with whatever version of OE you are using (the sanity tested distro)
17:12.49Crofton|cloudso change the 18.04 to 14.04?
17:13.15JPEWCrofton|cloud: Ya
17:14.35Crofton|cloudhttps://www.irccloud.com/pastebin/glNmpOw5/
17:14.42Crofton|cloudlol this is a good sign
17:14.59JPEWHeh, what version of OE are you trying to build?
17:15.04Crofton|cloudOK, need to try this on checlout that is barfing on python being python3 :)
17:15.15Crofton|cloudsumo I think
17:15.27Crofton|cloudsemi random vendorware
17:16.16Crofton|cloudso I will have something that has oe-core bitbake and a few other layers in a directory
17:16.23Crofton|cloudwill this work?
17:16.36Crofton|cloudI point env vars at oe and bitbake
17:16.36JPEWYa, we build sumo with pyrex. j/s
17:16.53Crofton|cloudbut the added layers, they will make it in?
17:19.18JPEWYes. You have to make sure they are bound into the container. By default it will bind in everything under your init script
17:26.13JPEWCrofton|cloud: https://github.com/garmin/pyrex#binding-directories-into-the-container
17:27.21JPEWUbuntu 18.04 is one of the tested distros for sumo, so I would use that
17:33.26JPEWCrofton|cloud: Ah ha! found it
17:34.18JPEWCrofton|cloud: https://github.com/karelzak/util-linux/commit/93de9f687d1640fff963f26b7db474eef3746532
17:34.38JPEWSo, we do need newer setpriv... need them on the newer distros too
17:41.23Crofton|cloudso how do I make 18.04 work?
17:41.43JPEWj/s and I'll send you a patch to try
17:41.52Crofton|cloudcool
17:54.16JPEWCrofton|cloud: https://github.com/garmin/pyrex/pull/54 You should just be able to `git fetch` and see the change on the branch
17:54.51JPEWI'm still running CI tests locally (takes a while), but it looks OK so far. Hopefully that fixes your problem
17:55.33Crofton|cloudok, going to move to the machine where I need this to work and see what happens
18:11.44JPEWCrofton|cloud: Do you have a github username?
18:12.12Crofton|cloudbalister
18:12.15Crofton|cloudboring I know
18:19.02Crofton|cloudthis will be fun ./meta-foo ./meta-bar ./pky at same level :)
18:39.52*** join/#oe ao2 (~ao2@host-95-250-15-64.retail.telecomitalia.it)
19:04.54JPEWCrofton|cloud: Ya, you'll probably want to write a custom init script
19:11.25Crofton|cloudcontainer is still building on the roatting disk
19:11.51JPEWCrofton|cloud: Ya, it takes a while. podman isn't the fastest at building... docker buildkit is *much* better
19:12.22JPEWbuildkit can skip the unused images in the Dockerfile so you only build what you actually need. It also builds in parallel
19:14.24JPEWCrofton|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
19:16.50RobertBergerJPEW/Crofton: Are there somewhere "for dummy" instructions how to use pyrex?
19:17.10Crofton|cloudthe github readme
19:17.33JPEWRobertBerger: Ya, I tried to make the README pretty comprehensive, but if it needs more help let me know: https://github.com/garmin/pyrex
19:21.02RobertBergerThanks!
19:21.24*** join/#oe marka (~marka@198-84-181-245.cpe.teksavvy.com)
19:27.24*** join/#oe vmeson (~rmacleod@198-48-226-187.cpe.pppoe.ca)
19:27.36*** join/#oe hrw (~hrw@redhat/hrw)
19:28.41*** join/#oe florian (~florian_k@Maemo/community/contributor/florian)
19:40.52tlwoernerJPEW: "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"
19:47.43*** join/#oe B0ned1ger (~B0ned1ger@82-135-139-249.static.zebra.lt)
20:00.46JPEWtlwoerner: Err, not sure what you're pointing out there :)
20:01.41tlwoernerJPEW: that sentence (from the README file at https://github.com/garmin/pyrex) sounds strange
20:02.15tlwoernerit _feels_ like it was about to say "these commands are *NOT* supported…"
20:02.34tlwoerner?
20:04.27tlwoerneri'm just wondering if i'm readying that wrong
20:09.41Crofton|cloudJPEW: OK build running. So you need to do something to update the containers so I do not need to build it all the time?
20:11.28JPEWCrofton|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
20:11.48Crofton|cloudcool
20:11.52Crofton|cloudTomorrow?
20:12.03JPEWYa
20:12.06Crofton|cloudok
20:12.13Crofton|cloudjust needed rough timeframe
20:12.54Crofton|cloudhopefully us talking about it gets a few more people to try it
20:13.01JPEWHopefully :)
20:13.32Crofton|clouddefinitely will help me move off the old build machine and let me update it from Fedora-Ancient
20:21.15JPEWtlwoerner: No, it's correct. Those tools are some of the exceptions that are supposed to still work properly
20:22.10JPEWtlwoerner: Pyrex isn't designed to allow to run e.g. vim inside the container and be a complete development environment
20:22.40kergothi imagine trying to get xterm from inside to show up outside would be a pain in the ass anyway :)
20:23.12JPEWkergoth, tlwoerner: Right. Normally no "interactive" stuff. Those are the exceptions to that rule because you can't really do those any other way
20:23.45tlwoernergreat thanks :-)
20:25.47tlwoerneri 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?
20:26.54JPEWtlwoerner: I think the oe-members list would be a good place for that?
20:33.19tlwoernerbetween https://www.openembedded.org/wiki/Mailing_lists and https://www.yoctoproject.org/community/mailing-lists/ i don't see one named oe-members
20:33.37tlwoerneris going senile
20:39.43Crofton|cloudum you are looking on the yp page?
20:40.14Crofton|cloudyp members are corporations, oe members are people
20:41.24tlwoerneri'm looking at both the OE and YP mailing list pages
20:42.17Crofton|cloudhmmm, maybe not public
20:42.36JPEWI don't see it listed on groups.io
20:43.15Crofton|cloudmight be hiding
21:06.26tlwoernerany other nominations? preferably a list people have heard of? ;-)
21:09.40RobertBerger@tlwoerner: I heard you can buy such lists with names and e-mails from shady places ;)
21:11.17tlwoernerlol
21:24.41Crofton|cloudJPEW: OK, so it works great, accept it can't fetch from a server I see via vpn
21:25.51Crofton|cloudpossibly because I brought the env up before the vpn
21:39.37JPEWCrofton|cloud: Possibly. It uses the --net=host option in the container so it *should* see all the same networking as the host
21:39.59Crofton|cloudhow do I restart things?
21:40.59*** join/#oe hrww (~hrw@redhat/hrw)
21:42.46JPEWThe 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
21:42.49JPEWWhats the error?
21:49.11Crofton|cloudHost key verification failed.
21:49.28Crofton|cloudhttps://www.irccloud.com/pastebin/nB2TPei1/
21:49.47Crofton|cloudbut works from command line
21:50.57Crofton|cloudmight should read fetcher docs
21:51.19*** join/#oe hrw (~hrw@redhat/hrw)
21:51.46JPEWAh, you need to bind in your ssh keys
21:51.57JPEWI should add an example for that
21:54.04JPEWin your pyrex.ini add `${env:HOME}/.ssh` to `run:bind`
21:56.28Crofton|cloudagreed
21:57.39Crofton|cloudhttps://www.irccloud.com/pastebin/OS4Wr3Er/
21:57.46Crofton|cloudso look slike that?
21:58.13JPEWYep
21:58.48Crofton|cloudI mis being able to know more than a few things at once :)
21:59.53Crofton|cloudsame problem ....
22:00.01Crofton|cloudHow do I get it to read the ini  file?
22:00.35JPEWexit the shell and re-run `. pyrex-init-build-env`
22:01.02JPEWBut, things in the [run] section *shouldn't* need that
22:01.15Crofton|cloudhmm
22:01.37Crofton|cloudI need to set the vars again
22:02.08JPEWDid you accidently overrwrite the pyrex.ini file?
22:02.22Crofton|cloudno the root path vars
22:11.14*** join/#oe hrww (~hrw@redhat/hrw)
22:18.22JPEWCrofton|cloud: Ok, Pyrex v1.2.0 has just been released, which should have that fix in it
22:21.07Crofton|cloudthanks
22:41.40*** join/#oe smurray (sid98062@gateway/web/irccloud.com/x-xfcyndbwottehwrg)
22:52.51*** join/#oe hrw (~hrw@redhat/hrw)
23:05.21*** join/#oe hrw (~hrw@redhat/hrw)
23:14.40*** join/#oe hrw (~hrw@redhat/hrw)
23:25.35*** join/#oe hrw (~hrw@redhat/hrw)
23:44.06*** join/#oe infobot (ibot@96-86-209-99-static.hfc.comcastbusiness.net)
23:44.06*** topic/#oe is OpenEmbedded Developer Lounge | Web: http://openembedded.org | Repositories: http://git.openembedded.org/ | Primary Repo Mirrors: https://github.com/openembedded | This is not a distro or machine support channel

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.