Tuesday, 2019-10-29

*** Crofton <Crofton!~Crofton@2a01:cb14:cf9:8c00:ab76:fa52:72e7:6617> has quit IRC00:04
*** NU-Slacker <NU-Slacker!~NU-Slacke@> has joined #yocto00:05
*** NU-Slacker <NU-Slacker!~NU-Slacke@> has quit IRC00:10
*** Crofton <Crofton!~Crofton@2a01:cb14:cf9:8c00:ab76:fa52:72e7:6617> has joined #yocto00:12
*** DrAcos-Carazza <DrAcos-Carazza!~Dracos-Ca@ip4d1530cd.dynamic.kabel-deutschland.de> has quit IRC00:12
*** tgamblin <tgamblin!~tgamblin@CPE64777de11593-CM64777de11590.cpe.net.cable.rogers.com> has joined #yocto00:13
*** Dracos-Carazza <Dracos-Carazza!~Dracos-Ca@ip4d1530cd.dynamic.kabel-deutschland.de> has joined #yocto00:13
*** Klanticus <Klanticus!~quassel@> has quit IRC00:20
*** bb_n00b <bb_n00b!d9423c05@> has quit IRC01:06
*** todun_ <todun_!~todun@> has joined #yocto01:12
*** todun <todun!~todun@> has quit IRC01:12
*** todun_ is now known as todun01:12
*** tgamblin <tgamblin!~tgamblin@CPE64777de11593-CM64777de11590.cpe.net.cable.rogers.com> has quit IRC01:19
*** learning1 <learning1!~pi@> has quit IRC01:34
*** learning1 <learning1!~pi@> has joined #yocto01:46
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has quit IRC01:49
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has joined #yocto01:54
*** todun <todun!~todun@> has quit IRC02:02
*** todun <todun!~todun@> has joined #yocto02:03
*** kaspter <kaspter!~Instantbi@> has quit IRC02:56
*** kaspter <kaspter!~Instantbi@> has joined #yocto02:56
*** todun <todun!~todun@> has quit IRC04:14
*** vineela <vineela!~vtummala@> has quit IRC04:17
*** camus <camus!~Instantbi@> has joined #yocto04:29
*** kaspter <kaspter!~Instantbi@> has quit IRC04:31
*** camus is now known as kaspter04:31
*** agust <agust!~agust@p54833695.dip0.t-ipconnect.de> has joined #yocto05:39
*** marka <marka!~marka@198-84-181-245.cpe.teksavvy.com> has quit IRC06:55
*** vineela <vineela!~vtummala@> has joined #yocto07:00
*** kroon <kroon!~kroon@> has joined #yocto07:07
*** florian_kc <florian_kc!~florian_k@Maemo/community/contributor/florian> has joined #yocto07:09
*** yann <yann!~yann@91-170-159-152.subs.proxad.net> has quit IRC07:12
*** frsc <frsc!~frsc@2003:a:e7a:6200:246c:2a8b:f45a:a33d> has joined #yocto07:15
*** leitao <leitao!~leitao@2620:10d:c092:180::1:6a10> has joined #yocto07:15
*** florian_kc <florian_kc!~florian_k@Maemo/community/contributor/florian> has quit IRC07:23
*** armpit <armpit!~armpit@> has quit IRC07:26
*** goliath <goliath!~goliath@alyon-653-1-55-50.w109-212.abo.wanadoo.fr> has joined #yocto07:30
*** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has joined #yocto07:30
*** vineela <vineela!~vtummala@> has quit IRC07:30
*** jmiehe <jmiehe!~Thunderbi@p578c106e.dip0.t-ipconnect.de> has joined #yocto07:49
*** armpit <armpit!~armpit@> has joined #yocto07:52
*** goliath <goliath!~goliath@alyon-653-1-55-50.w109-212.abo.wanadoo.fr> has quit IRC07:56
lpappwhere rburton07:57
*** Bunio_FH <Bunio_FH!~bunio@81-18-201-214.static.chello.pl> has joined #yocto07:58
LetoThe2ndrburtib is here07:59
*** tprrt <tprrt!~tprrt@> has joined #yocto08:00
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has joined #yocto08:04
*** leitao <leitao!~leitao@2620:10d:c092:180::1:6a10> has quit IRC08:05
*** yann <yann!~yann@> has joined #yocto08:07
*** florian_kc <florian_kc!~florian_k@Maemo/community/contributor/florian> has joined #yocto08:22
*** AndersD <AndersD!~AndersD@ftth-94-142-214-250.breedbandarnhem.nl> has joined #yocto08:23
*** TobSnyder <TobSnyder!~schneider@ip5f5aa32f.dynamic.kabel-deutschland.de> has joined #yocto08:35
lpappI am a bit confused by the meaning of $PN08:46
mcfrisklpapp: recipe name, https://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#var-PN08:53
alessioigorI usually use $BPN.08:54
lpappwhy is it not RN?08:54
lpappPN would indicate a package name to me08:54
lpappso, I am getting this: ./tmp/deploy/ipk/polatisnic/kernel-3.2.1-r21_3.2.1-r22_polatisnic.ipk08:56
lpappdid I understand rburton correctly that if I want to get kernel_3.2.1-r22_polatisnic.ipk, I just have to change KERNEL_PACKAGE_NAME?08:56
lpappto say, kernel?08:56
*** leitao <leitao!~leitao@2620:10d:c092:200::1:3c97> has joined #yocto09:00
lpapphah, KERNEL_PACKAGE_NAME was not available in daisy :)09:01
lpappso, yeah, I am looking for the old-fashioned way to set the kernel package names09:02
lpappkernel.bbclass says # kernel-base becomes kernel-${KERNEL_VERSION - just not sure how09:05
*** bluca <bluca!~bluca@2a01:4b00:f419:6f00:7a8e:ed70:5c52:ea3> has joined #yocto09:06
rcrudodoes gitsm implementation of yocto works with https or only ssh?09:10
*** wertigon <wertigon!50fe9a69@1071ob.scansafe.net> has joined #yocto09:12
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has quit IRC09:13
wertigonHow do I add a package to my sdk, and only my sdk?09:13
wertigonThat is, when I type bitbake myimage -c populate_sdk , I get missing package requirements (more specifically, perl).09:14
Croftonwertigon, https://github.com/balister/meta-sdr/blob/master/recipes-images/images/native-sdk.inc09:14
Croftondoes that help?09:14
wertigonCould work, I'll try it and see how it goes09:15
wertigonWill get back to you soon :)09:15
*** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has quit IRC09:16
CroftonWorks for packages that have build time depends that are not run time, so the image won't have the build depends in an sdk built from the image recipe09:17
wertigonWhere do I place it, and how is it included? In my regular images folder or?09:18
*** florian_kc is now known as florian09:20
wertigonI'll give it a shot in my regular images folder09:23
wertigonAnd believe in the magic :D09:24
wertigonMagic failed me T_T09:28
wertigonOk, so I have the native-sdk.inc file, and I assume I need to include it from somewhere09:29
wertigonOr maybe... Ah, of course I just stick it to the base.inc I already have09:29
*** AndersD <AndersD!~AndersD@ftth-94-142-214-250.breedbandarnhem.nl> has quit IRC09:29
wertigonOk, hopefully this will work, might need to include more packages than just native-perl but that's just a compile-add-missing-repeat dance :P09:34
wertigonSorry for being a total new09:34
*** tprrt <tprrt!~tprrt@> has quit IRC09:35
wertigonNope :/09:36
wertigonError: "nothing provides nativesdk-perl needed by native-sdk-autoconf-2.69-r11.x86-65_nativesdk"09:37
*** leitao <leitao!~leitao@2620:10d:c092:200::1:3c97> has quit IRC09:38
wertigonBut I added nativesdk-perl to the SDK_EXTRA_TOOLS var...09:38
wertigonWhy it do this -_-;;09:40
*** mrc3 <mrc3!~mrc3@linaro/mrc3> has quit IRC09:41
*** Crofton <Crofton!~Crofton@2a01:cb14:cf9:8c00:ab76:fa52:72e7:6617> has quit IRC09:43
*** hpsy <hpsy!d9423c05@> has joined #yocto09:45
*** leitao <leitao!~leitao@2620:10d:c092:200::1:3c97> has joined #yocto09:45
*** tprrt <tprrt!~tprrt@> has joined #yocto09:46
*** leitao <leitao!~leitao@2620:10d:c092:200::1:3c97> has quit IRC09:47
*** leitao <leitao!~leitao@2620:10d:c092:200::1:3c97> has joined #yocto09:47
*** tprrt <tprrt!~tprrt@> has quit IRC09:53
wertigonNope, I turned every angle I could find still nothibng09:55
*** armpit <armpit!~armpit@> has quit IRC09:58
xtronbuilding linux-yocto kernel with meta-selinux configured, selinux.cfg is in src_uri but not reflecting/enabled in kernel .config, any idea why??10:05
*** bluca <bluca!~bluca@2a01:4b00:f419:6f00:7a8e:ed70:5c52:ea3> has left #yocto10:06
*** hpsy <hpsy!d9423c05@> has quit IRC10:07
yoctiNew news from stackoverflow: yocto populate_sdk has lots of warnings: package is not installable <https://stackoverflow.com/questions/58605151/yocto-populate-sdk-has-lots-of-warnings-package-is-not-installable>10:08
*** hpsy <hpsy!d9423c05@> has joined #yocto10:08
*** lucaceresoli <lucaceresoli!~lucaceres@> has joined #yocto10:09
*** tprrt <tprrt!~tprrt@> has joined #yocto10:11
*** lucaceresoli <lucaceresoli!~lucaceres@> has quit IRC10:12
*** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto10:13
*** hpsy <hpsy!d9423c05@> has quit IRC10:14
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC10:17
wertigonCrofton: Any ideas? :(10:23
*** amine <amine!~amine@static-176-158-51-218.ftth.abo.bbox.fr> has joined #yocto10:24
*** rburton <rburton!~rburton@> has joined #yocto10:24
*** mrc3 <mrc3!~mrc3@linaro/mrc3> has joined #yocto10:27
*** T_UNIX <T_UNIX!~T_UNIX@> has joined #yocto10:28
rburtonkergoth: you know external toolchains more than me10:39
LetoThe2ndxtron: did you check that you actually enabled meta-selinux functionality as pointed out in its README?10:40
rburtonkergoth: if i'm using an external toolchain, i presume there's no way to put it into images.  e.g. turning on tools-sdk will build its own gcc which is unrelated to the external toolchain10:40
*** georgem <georgem!~georgem@> has quit IRC10:43
*** kroon_ <kroon_!~kroon@> has joined #yocto10:43
*** georgem <georgem!~georgem@> has joined #yocto10:43
xtronLetoThe2nd, yes, required distro_features are appended, preferred providers are set,10:43
*** kroon <kroon!~kroon@> has quit IRC10:43
LetoThe2ndxtron: ok10:43
LetoThe2ndxtron: then the next step is to bitbake -e the kernel and see where its being left out.10:44
xtronin workdir, kernel-meta contains the kernel configs?10:45
LetoThe2ndxtron: why would you go looking there?10:46
xtronLetoThe2nd, then where selinux.cfg will show-up in kernel configs?10:47
LetoThe2ndxtron: bitbake -e and check that it really shows up in SRC_URI or whereever you *expect* it10:48
xtronLetoThe2nd, it's in src_uri file://selinux.cfg10:49
LetoThe2ndxtron: thats what you *EXPECT10:50
xtronLetoThe2nd, so, where should it be?10:52
LetoThe2ndxtron: bitbake -e your kernel target, and search for SRC_URI and its evaluation there.10:52
LetoThe2ndi think i basically said that three times now.10:53
xtronLetoThe2nd, it's the environment value of src_uri10:57
LetoThe2ndxtron: hum, what?11:05
*** T_UNIX <T_UNIX!~T_UNIX@> has quit IRC11:05
*** T_UNIX <T_UNIX!~T_UNIX@> has joined #yocto11:06
*** mrc3 <mrc3!~mrc3@linaro/mrc3> has quit IRC11:07
* alessioigor waves all11:09
alessioigorCould someone review my platch (http://lists.openembedded.org/pipermail/openembedded-core/2019-October/288378.html), please? Thanks in advance!11:09
LetoThe2ndwould rather review platches11:10
xtronLetoThe2nd, I think the custom image need to add packagegroup-core-selinux11:10
*** TobSnyder <TobSnyder!~schneider@ip5f5aa32f.dynamic.kabel-deutschland.de> has quit IRC11:14
wertigonHmm, further investigations; tried building meta-toolchain, same problem; nothing provides nativesdk-perl11:15
rburtonwertigon: i'd start chopping bits away until it works.  ie use qemux86 instead of your machine, nodistro instead of your distro, etc11:22
wertigonrburton: building the image work just fine, it's when I try to build the SDK / toolchain I receive the error11:26
rburtonbecause its nativesdk* which is SDK specific11:27
rburtonso try chopping changes away until it works, to identify what is breaking it11:27
rburtonthe autobuilder builds about 50 SDKs every night, so it works there11:28
*** T_UNIX <T_UNIX!~T_UNIX@> has quit IRC11:28
wertigonNot much to chop away really :/  Hmm, in fact only IMAGE_FEATURES I have is package-management and splash11:28
rburtonwhat MACHINE?11:28
rburtonunless you can replicate the failure with a pure poky and qemux86, you've more to chop out11:29
wertigonThe sitara dev board by TI11:29
rburtonright so lets see if we can blame TI: remove meta-ti, set machine to qemux86, see if it still breaks11:29
*** Klanticus <Klanticus!~quassel@> has joined #yocto11:37
wertigonmeta-ti provides initramfs11:37
*** yann <yann!~yann@> has quit IRC11:37
rburtonmeta-toolchain should be fairly isolated from anything else11:38
*** berton <berton!~berton@> has joined #yocto11:41
wertigonOk, I try now with MACHINE=qemux86 meta-toolchain11:43
wertigonSorry, MACHINE=qemux86 bitbake meta-toolchain11:43
wertigonThis should build everything to compile a a minimal glibc only application if I understand the docs correctly, right?11:45
*** tgamblin <tgamblin!~tgamblin@> has joined #yocto11:50
*** armpit <armpit!~armpit@> has joined #yocto11:52
wertigonBTW, this is thud branch if that makes much difference11:55
wertigonbuilding qemux86 meta-toolchain on my image right now, will try poky after that fails11:59
*** TobSnyder <TobSnyder!~schneider@ip5f5aa32f.dynamic.kabel-deutschland.de> has joined #yocto12:00
wertigonKeep digging that hole, eventually you'll strike gold...12:01
wertigonOr bones...12:01
wertigonOr a portal to another dimension filled with creepy tribbles12:02
rburtonwertigon: meta-toolchain doesn't care for your image12:09
rburtonan image sdk is 'bitbake myimage -c populate_sdk'12:09
rburtonbitbake meta-toolchain is just a bare compiler and supporting pieces12:10
wertigonrburton: Yeah, so it's really strange I get the same error when I bitbake with meta-toolchain is it not...? :)12:23
rburtonnot at all12:23
wertigonAtleast with MACHINE=sitara12:23
rburtonits the same code, but by doing meta-toolchain you remove the influence of the image itself12:23
wertigonTrying MACHINE=qemux86 now12:23
*** tlwoerner <tlwoerner!~Trevor@unaffiliated/tlwoerner> has quit IRC12:30
*** mrc3 <mrc3!~mrc3@linaro/mrc3> has joined #yocto12:47
wertigonnativesdk-clang takes forever to build :P12:51
*** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has quit IRC12:53
*** armpit <armpit!~armpit@> has quit IRC12:53
rburtonyes it does!12:54
*** wertigon <wertigon!50fe9a69@1071ob.scansafe.net> has quit IRC13:05
*** hpsy <hpsy!d9423c05@> has joined #yocto13:08
*** wertigon <wertigon!50fe9a69@1071ob.scansafe.net> has joined #yocto13:14
*** bluca <bluca!~bluca@2a01:4b00:f419:6f00:7a8e:ed70:5c52:ea3> has joined #yocto13:17
rreignierHi! Regarding my question, last night, does someone know how to change the kernel location from /boot partition to '/' partition in order to have several rootfs on the same target for updates use case.13:25
rreignierI have tried to change "KERNEL_IMAGEDEST" but it has no effect.13:25
*** hpsy <hpsy!d9423c05@> has quit IRC13:51
*** tlwoerner <tlwoerner!~Trevor@unaffiliated/tlwoerner> has joined #yocto13:52
*** Crofton <Crofton!~Crofton@> has joined #yocto13:55
*** learningc <learningc!~pi@> has joined #yocto14:00
*** hpsy1 <hpsy1!~hpsy@> has joined #yocto14:01
*** learning1 <learning1!~pi@> has quit IRC14:02
*** kanavin <kanavin!~kanavin@> has joined #yocto14:05
hpsy1Hello, does the SSTATE_MIRRRORS populate the SSTATE_DIR?14:11
*** hpsy1 is now known as hpsy14:13
hpsyHello, does the SSTATE_MIRRRORS populate the SSTATE_DIR?14:14
LetoThe2ndrreignier: by starting at the code, it *might* be a bug, but i'm uncertain14:14
LetoThe2ndhpsy: meaning that?14:14
LetoThe2ndrreignier: unfortunately the guy who could instantly tell is kinda unavailable at the moment14:16
LetoThe2ndrreignier: but if i run into him i'll ask and report, ok?14:17
hpsyI currently define SSTATE_DIR to share SSTATE between different build directories, I am asking if I use SSTATE_MIRRORS will the shared STATE_DIR be updated when a prebuilt is present in the SSTATE_MIRRORS and missing from SSTATE_DIR or will every build workspace grab the prebuilt from my SSTATE_MIRROR?14:18
LetoThe2ndhpsy: the latter. (about 90% sure)14:19
hpsyLetoThe2nd: Thanks :)14:23
*** ericch <ericch!~ericch@50-205-235-218-static.hfc.comcastbusiness.net> has joined #yocto14:24
*** kroon_ <kroon_!~kroon@> has quit IRC14:28
rreignierLethoThe2nd Thanks a lot14:30
rreignierLetoThe2nd Thanks a lot14:31
rreignierBut maybe that is not the right way to do what I want to achieve. One kernel per root fs and and the bootloader on a separated partition14:32
LetoThe2ndrreignier: well it depends on your platform.14:33
LetoThe2ndrreignier: a lot of platforms i know don't have the bootloader visible in the filesystem at all. but i think you mentioned grub, right?14:33
rreignierI am on x86-64 (UpBoard so Atom). But for now, I do the tests on qemux86-6414:34
rreignierYes. From my investigation, Grub seems like the recommended bootloader on x8614:34
LetoThe2ndrreignier: if you have some form of control over where the EFI starts off, then you could even tuck /boot into the rootfs, no separate partition14:35
rreignierBarebox does not seems supproted yet by Yocto (wic) for now14:35
rreignierInteresting, but I still need EFI/BOOT/bootx64.efi on the first partition, Isn't it?14:37
LetoThe2ndrreignier: you'd need some form of efi binary there, right14:37
LetoThe2ndrreignier: but another thing you need to think about is, how will the bootloader decide which rootfs to boot14:38
LetoThe2ndespecially thinking about the update/broken update situation14:38
rreignierI want to use RAUC so it support different bootloader14:38
LetoThe2ndrreignier: but then i'd postpone the kernel packaging until you've got the rauc strategy all sorted out14:39
LetoThe2ndbecause if you now spend a lot of time sorting out stuff, and then it turns out that you don't have a shared /boot for example, all that time is waasted14:40
rreignierYes, it is true that I do not know from which end start the problem...14:41
rreignierSay I want 3 partitions: /boot, /rootA, /rootA.14:41
rreignierAs I understand it, I need Grub on /boot and the kernel installed on /rootA and /rootB14:41
LetoThe2ndthats what you want and think14:42
LetoThe2ndbut i'm not sure that this is what fits rauc14:42
LetoThe2ndyou might want to be able to upgrade grub too, for example14:42
LetoThe2ndand then your setup is bound to break14:42
rreignierI know that it is a limitation of that scheme, I cannot update the bootloader14:43
*** mrc3 <mrc3!~mrc3@linaro/mrc3> has quit IRC14:45
rreignierOk, so the EFI path as described here could be interesting: https://rauc.readthedocs.io/en/latest/integration.html#efi14:46
LetoThe2ndrreignier: i know. thats why i told you to start with really thinking the whole strategy through instead of just making assumptions.14:47
rreignierIs it possible to generate a kernel EFI stub to boot directly from UEFI with Yocto in qemu? I might try that14:47
LetoThe2ndno idea14:48
rreignierBecause from here, it seems that wic only support grub and systemd-boot as bootloader: https://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/scripts/lib/wic/plugins/source/bootimg-efi.py#n2814:50
rreignierI might be OK with systemd-boot14:50
rreignierI will have to figure out how and when to call "efibootmgr" in a recipe14:51
LetoThe2ndlook into it, trhink it through. make an educated decidion instead of geusswork14:52
rreignierI don't even know if it is possible actually14:52
LetoThe2ndanthing is possible, its only software. just the needed effort varies14:52
*** TobSnyder <TobSnyder!~schneider@ip5f5aa32f.dynamic.kabel-deutschland.de> has quit IRC14:52
tlwoerneris it safe to assume the weekly yocto meeting is on hiatus this week?14:53
tlwoernerRP: ^14:53
*** vineela <vineela!~vtummala@> has joined #yocto14:54
yoctiNew news from stackoverflow: how to get ${THISDIR} inside do_unpack_append in .bbappend file <https://stackoverflow.com/questions/58610052/how-to-get-thisdir-inside-do-unpack-append-in-bbappend-file>15:09
*** vineela <vineela!~vtummala@> has quit IRC15:11
JPEWRP: Unfortunately, my patch to grab the offending packages from failed reproducible build test had an error: shutil.SameFileError: '/home/pokybuild/yocto-worker/oe-selftest-ubuntu/build/build-st-56414/reproducibleA/tmp/deploy/deb/./core2-64/perl-doc_5.30.0-r0_amd64.deb' and '/home/pokybuild/yocto-worker/oe-selftest-ubuntu/build/build-st-56414/reproducibleA/tmp/deploy/deb/./core2-64/perl-doc_5.30.0-r0_amd64.deb' are the same file15:14
JPEWI can't quite figure out how that happened: it looks like the save_dir is an empty string, which is weird. I probably have some stupid error somewhere... anyway once I sort it out I'll post another patch.15:16
JPEWI need to fix up the permissions anyway because the tempdir is rwx------ owned by the pokybuild user on the AB node so I can't see inside it.15:17
*** kanavin <kanavin!~kanavin@> has quit IRC15:18
*** litb <litb!~jschaub@pd907fca9.dip0.t-ipconnect.de> has joined #yocto15:30
litbhello folks15:30
*** jmiehe <jmiehe!~Thunderbi@p578c106e.dip0.t-ipconnect.de> has quit IRC15:33
*** WillMiles <WillMiles!~Will@static-209-87-231-80.storm.ca> has joined #yocto15:42
litbI think my life becomes easier if I specify SYSROOT_DIRS="/", because my installer can then just pick the files from recipe-sysroot, instead of having to build an image first and then somehow loop-mounting untaring it to get onto the files15:46
*** litb <litb!~jschaub@pd907fca9.dip0.t-ipconnect.de> has quit IRC15:47
*** litb <litb!~jschaub@pd907fca9.dip0.t-ipconnect.de> has joined #yocto15:50
*** kanavin <kanavin!~kanavin@> has joined #yocto16:07
*** Crofton <Crofton!~Crofton@> has quit IRC16:11
*** bluca <bluca!~bluca@2a01:4b00:f419:6f00:7a8e:ed70:5c52:ea3> has left #yocto16:11
*** yann <yann!~yann@> has joined #yocto16:14
*** florian <florian!~florian_k@Maemo/community/contributor/florian> has quit IRC16:16
*** berton_ <berton_!~berton@> has joined #yocto16:17
*** vineela <vineela!vtummala@nat/intel/x-cdahhtigtgxieqlz> has joined #yocto16:19
*** berton <berton!~berton@> has quit IRC16:20
*** frsc <frsc!~frsc@2003:a:e7a:6200:246c:2a8b:f45a:a33d> has quit IRC16:23
*** berton__ <berton__!~berton@> has joined #yocto16:32
*** berton_ <berton_!~berton@> has quit IRC16:34
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has joined #yocto16:34
yoctiNew news from stackoverflow: How to store pyc files with setuptools3 in bitbake recipe in the same way setuptools does? <https://stackoverflow.com/questions/58611684/how-to-store-pyc-files-with-setuptools3-in-bitbake-recipe-in-the-same-way-setupt>16:39
*** tgamblin <tgamblin!~tgamblin@> has quit IRC16:43
*** smcginnis <smcginnis!~smcginnis@72-50-207-44.fttp.usinternet.com> has joined #yocto16:45
*** Bunio_FH <Bunio_FH!~bunio@81-18-201-214.static.chello.pl> has quit IRC16:49
rburtonlitb: no context there but why are you having to loop-mount images or something?16:51
rburtontotal confusion as to what is going on16:51
*** kanavin <kanavin!~kanavin@> has quit IRC16:53
litbrburton, because my installer needs to collect some files (mostly shared-library .dll files) from the built packages. so I would make my installer-recipe dependent on  some image recipe's do_image_tar , and in the installer's do_compile, I would need to untar the image to access the files16:54
rburtonlitb: you could just grab the files from the packages16:54
litbrburton, I think that's too complicated. I assume there must be a python API to access the image/ folders of given recipes, to grab files from there16:54
litbyeah, exactly16:54
rburtonno, you misunderstand me.  the packages directly.16:54
rburtonnot build an image and then unpack it again16:54
rburtonhow do you build the installer?16:55
rburtonwhy can't it just depend on all the libraries it needs, so they're all in the sysroot16:55
litbah, you mean from the deploy/deb/ folder. I will look into "oe-pkgdata-util find-path" to see how it makes the lookup from path to pkg-name. with that, I could go into the deb-package to pick the wanted file16:55
litbrburton, I assume I will have a recipe that builds the installer file (which is Inno Setup), for which I need to have the correct files present rooted at a given path ${root}16:57
rburtonso either just depending on the pieces to get them in the sysroot might work,  if you need more than the sysroot contains (quite possibly) then easy enough to unpack the packages directly into a staging directory.16:58
litbrburton, ah, I see. I have looked into how the do_rootfs does it. apparently there's a python API to create a root filesystem from a given list of packages.16:59
*** florian_kc <florian_kc!~florian_k@Maemo/community/contributor/florian> has joined #yocto16:59
rburtonan actual rootfs is probably overkill for what you need16:59
rburtonyou don't need a libc for example i presume?17:00
litbah I see, yeah that's overkill17:00
*** chandana73 <chandana73!~ckalluri@> has joined #yocto17:01
*** florian_kc <florian_kc!~florian_k@Maemo/community/contributor/florian> has quit IRC17:04
*** florian_kc <florian_kc!~florian_k@Maemo/community/contributor/florian> has joined #yocto17:06
*** litb <litb!~jschaub@pd907fca9.dip0.t-ipconnect.de> has quit IRC17:07
*** florian_kc <florian_kc!~florian_k@Maemo/community/contributor/florian> has quit IRC17:13
*** tgamblin <tgamblin!~tgamblin@CPE64777de11593-CM64777de11590.cpe.net.cable.rogers.com> has joined #yocto17:16
*** vmeson <vmeson!~rmacleod@24-52-239-53.cable.teksavvy.com> has quit IRC17:56
*** leitao <leitao!~leitao@2620:10d:c092:200::1:3c97> has quit IRC17:56
*** florian_kc <florian_kc!~florian_k@Maemo/community/contributor/florian> has joined #yocto17:59
*** tprrt <tprrt!~tprrt@> has quit IRC18:14
*** dv_ <dv_!~dv@62-178-50-190.cable.dynamic.surfer.at> has quit IRC18:19
*** Crofton <Crofton!~Crofton@2a01:cb14:cf9:8c00:ab76:fa52:72e7:6617> has joined #yocto18:33
*** dv_ <dv_!~dv@> has joined #yocto18:34
JPEWRP: I've updates the jpew/ab-reproducible-test with new patches to fix the problem with capturing the reproducible build results. Please apply them to master-next in place of the previous 218:35
*** vmeson <vmeson!~rmacleod@24-52-239-53.cable.teksavvy.com> has joined #yocto18:37
*** florian_kc is now known as florian19:02
*** leitao <leitao!~leitao@2620:10d:c092:180::1:e483> has joined #yocto19:05
*** apteryx <apteryx!~maxim@dsl-10-148-194.b2b2c.ca> has joined #yocto19:08
apteryxdoes using a python library recipe (e.g., python-pytest) means python itself is pulled as a runtime dependency? I've looked at their recipe, but couldn't figure it out.19:09
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto19:18
rburtonapteryx: the recipe should have RDEPENDS set appropriately19:21
rburtonit will always depend on python3-core but that's just the interpretter and a *very small* subset of the library19:22
*** hpsy <hpsy!~hpsy@> has left #yocto19:35
*** mrc3 <mrc3!~mrc3@linaro/mrc3> has joined #yocto19:40
*** leitao <leitao!~leitao@2620:10d:c092:180::1:e483> has quit IRC19:57
*** leitao <leitao!~leitao@2620:10d:c092:180::1:e483> has joined #yocto19:59
*** volestorm <volestorm!~volestorm@> has quit IRC20:12
*** WillMiles <WillMiles!~Will@static-209-87-231-80.storm.ca> has quit IRC20:26
*** dallas <dallas!~dallas@> has quit IRC20:37
*** zwelch <zwelch!~zwelch@fluffy.superlucidity.net> has quit IRC20:44
*** zwelch <zwelch!~zwelch@fluffy.superlucidity.net> has joined #yocto20:52
*** leitao <leitao!~leitao@2620:10d:c092:180::1:2e3b> has joined #yocto21:06
mischiefhm, shouldn't the kernel class depend on lz4-native for copy_initramfs()?21:08
*** zwelch <zwelch!~zwelch@fluffy.superlucidity.net> has quit IRC21:16
*** berton__ <berton__!~berton@> has quit IRC21:17
*** leitao <leitao!~leitao@2620:10d:c092:180::1:2e3b> has quit IRC21:18
*** zwelch <zwelch!~zwelch@fluffy.superlucidity.net> has joined #yocto21:22
*** kanavin <kanavin!~kanavin@cust-east-parth2-46-193-72-114.wb.wifirst.net> has joined #yocto21:29
*** palate <palate!~palate@unaffiliated/palate> has joined #yocto21:30
*** mrc3 <mrc3!~mrc3@linaro/mrc3> has quit IRC21:38
*** Klanticus <Klanticus!~quassel@> has quit IRC21:51
*** rburton <rburton!~rburton@> has quit IRC22:01
*** Micro23 <Micro23!~Micro23@cD0AA5AC1.dhcp.as2116.net> has joined #yocto22:09
*** BobPungartnik <BobPungartnik!~BobPungar@> has joined #yocto22:10
*** BobPungartnik <BobPungartnik!~BobPungar@> has quit IRC22:10
*** kanavin <kanavin!~kanavin@cust-east-parth2-46-193-72-114.wb.wifirst.net> has quit IRC22:20
*** Micro23 <Micro23!~Micro23@cD0AA5AC1.dhcp.as2116.net> has quit IRC22:26
*** agust <agust!~agust@p54833695.dip0.t-ipconnect.de> has quit IRC22:37
*** florian <florian!~florian_k@Maemo/community/contributor/florian> has quit IRC22:39
*** ericch <ericch!~ericch@50-205-235-218-static.hfc.comcastbusiness.net> has quit IRC22:46
*** ericch <ericch!~ericch@50-205-235-218-static.hfc.comcastbusiness.net> has joined #yocto22:48
*** ericch <ericch!~ericch@50-205-235-218-static.hfc.comcastbusiness.net> has quit IRC22:48
*** davisr__ <davisr__!~davisr@cpe-184-58-235-7.wi.res.rr.com> has quit IRC23:16
*** rburton <rburton!~rburton@> has joined #yocto23:51

Generated by irclog2html.py 2.11.0 by Marius Gedminas - find it at mg.pov.lt!