Monday, 2016-08-15

*** nighty <nighty!> has quit IRC00:00
*** clopez <clopez!> has quit IRC00:03
*** clopez <clopez!> has joined #yocto00:10
*** Biliogadafr <Biliogadafr!> has quit IRC00:12
*** nighty <nighty!> has joined #yocto00:33
*** dmiess_ <dmiess_!> has joined #yocto00:45
*** bananadev <bananadev!~onlyester@> has joined #yocto02:16
*** bananadev <bananadev!~onlyester@> has quit IRC02:23
*** slidercrank <slidercrank!~slidercra@unaffiliated/slidercrank> has quit IRC02:24
*** blueness <blueness!~blueness@gentoo/developer/blueness> has quit IRC02:29
*** Nilesh_ <Nilesh_!uid116340@gateway/web/> has joined #yocto02:38
*** ntl <ntl!> has quit IRC02:52
*** ntl <ntl!> has joined #yocto03:06
*** slidercrank <slidercrank!~slidercra@unaffiliated/slidercrank> has joined #yocto03:49
*** clopez <clopez!> has quit IRC04:07
*** clopez <clopez!> has joined #yocto04:21
*** AndersD <AndersD!> has joined #yocto05:09
khemwhats TERM set to05:12
khemusually its a problem with virtual terminals05:13
khemdoes it work with screen ?05:13
*** slidercrank <slidercrank!~slidercra@unaffiliated/slidercrank> has quit IRC05:15
*** AndersD <AndersD!> has quit IRC05:24
*** AndersD <AndersD!> has joined #yocto05:25
*** visaev <visaev!~visaev@> has joined #yocto05:45
*** sujith_h <sujith_h!~toaster@> has joined #yocto05:48
*** hatter <hatter!~hatter@> has joined #yocto05:53
*** AndersD <AndersD!> has quit IRC05:54
*** AndersD <AndersD!> has joined #yocto05:55
*** gtristan <gtristan!~tristanva@> has quit IRC06:01
*** AndersD <AndersD!> has quit IRC06:01
*** AndersD <AndersD!> has joined #yocto06:02
*** AndersD <AndersD!> has quit IRC06:06
*** AndersD <AndersD!> has joined #yocto06:07
*** AndersD <AndersD!> has quit IRC06:26
*** AndersD <AndersD!> has joined #yocto06:37
*** joshuagl <joshuagl!~joshuagl@> has joined #yocto07:01
*** gtristan <gtristan!~tristanva@> has joined #yocto07:02
*** blueness <blueness!~blueness@gentoo/developer/blueness> has joined #yocto07:07
*** aragua <aragua!> has joined #yocto07:09
*** fl0v0 <fl0v0!> has joined #yocto07:13
*** blueness <blueness!~blueness@gentoo/developer/blueness> has quit IRC07:15
*** rajm <rajm!> has joined #yocto07:16
*** CTtpollard <CTtpollard!> has joined #yocto07:19
*** LocutusOfBorg <LocutusOfBorg!~Gianfranc@ubuntu/member/locutusofborg> has joined #yocto07:20
*** blueness <blueness!~blueness@gentoo/developer/blueness> has joined #yocto07:22
*** hatter <hatter!~hatter@> has quit IRC07:27
*** Anticom <Anticom!~timo.m@> has joined #yocto07:35
*** iskander <iskander!~iskander@> has quit IRC07:39
*** dreyna <dreyna!> has quit IRC07:40
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has joined #yocto07:40
CTtpollardis it possible to do_install_append_$machine ?07:41
*** iskander <iskander!~iskander@> has joined #yocto07:43
*** iskander <iskander!~iskander@> has quit IRC07:55
*** iskander <iskander!~iskander@> has joined #yocto07:59
CTtpollardalso, it's possible to use sed in do_install commands right?08:06
*** joseppc <joseppc!~josep@linaro/joseppc> has joined #yocto08:07
*** ftonello <ftonello!~felipe@> has quit IRC08:09
CTtpollardseds claiming the file doe not exist at the given path in the sysroot, but it does08:13
*** Crofton <Crofton!~Crofton@> has joined #yocto08:16
*** Crofton <Crofton!~Crofton@> has quit IRC08:23
*** joseppc <joseppc!~josep@linaro/joseppc> has quit IRC08:25
*** joseppc <joseppc!~josep@linaro/joseppc> has joined #yocto08:37
*** Ulfalizer <Ulfalizer!~ulf@> has joined #yocto08:46
*** iskander <iskander!~iskander@> has quit IRC08:57
*** iskander <iskander!~iskander@> has joined #yocto09:01
*** seezer <seezer!quassel@quassel/developer/seezer> has quit IRC09:03
jubriskander: `echo $TERM`, then maybe `export TERM=linux` or `export TERM=xterm`09:04
*** seezer <seezer!seezer@quassel/developer/seezer> has joined #yocto09:14
*** belen <belen!Adium@nat/intel/x-dovdopponbtqwbqv> has joined #yocto09:17
*** rburton <rburton!> has joined #yocto09:29
*** seezer <seezer!seezer@quassel/developer/seezer> has quit IRC09:40
*** Anticom <Anticom!~timo.m@> has quit IRC09:41
*** Anticom <Anticom!~timo.m@> has joined #yocto09:41
*** seezer <seezer!seezer@quassel/developer/seezer> has joined #yocto09:46
*** nighty <nighty!> has quit IRC10:04
*** maxin <maxin!~maxin@2001:998:22:0:657c:8573:13c2:de73> has joined #yocto10:14
*** JaMa <JaMa!> has joined #yocto10:15
*** maxin <maxin!~maxin@2001:998:22:0:657c:8573:13c2:de73> has quit IRC10:22
*** maxin <maxin!> has joined #yocto10:26
*** anselmolsm <anselmolsm!~anselmols@> has joined #yocto10:46
*** Snert <Snert!> has quit IRC10:54
*** Snert <Snert!> has joined #yocto10:55
*** nighty <nighty!> has joined #yocto11:00
*** maxin <maxin!> has quit IRC11:05
*** joseppc <joseppc!~josep@linaro/joseppc> has quit IRC11:18
*** jku <jku!~jku@> has joined #yocto11:26
*** jku is now known as Guest7386711:26
*** maxin <maxin!~maxin@2001:998:22:0:657c:8573:13c2:de73> has joined #yocto11:27
*** maxin <maxin!~maxin@2001:998:22:0:657c:8573:13c2:de73> has quit IRC11:33
*** maxin <maxin!> has joined #yocto11:34
*** caiortp <caiortp!~inatel@> has joined #yocto11:38
*** simonl <simonl!uid6729@gateway/web/> has joined #yocto11:39
*** berton <berton!~fabio@> has joined #yocto11:49
*** istarilucky <istarilucky!~rlucca@> has joined #yocto11:58
visaevjubr, it is still not working12:02
visaevtried both12:02
visaevmake: *** No rule to make target `menuconfig'.  Stop.12:03
visaevCommand failed.12:03
visaevPress any key to continue...12:03
*** gtristan <gtristan!~tristanva@> has quit IRC12:05
*** zeddii_home <zeddii_home!> has joined #yocto12:07
*** Guest73867 <Guest73867!~jku@> has quit IRC12:10
*** gtristan <gtristan!~tristanva@> has joined #yocto12:21
*** ionte <ionte!> has joined #yocto12:28
*** challinan <challinan!> has joined #yocto12:29
*** CTtpollard <CTtpollard!> has quit IRC12:32
*** CTtpollard <CTtpollard!> has joined #yocto12:34
*** CTtpollard <CTtpollard!> has quit IRC12:37
*** CTtpollard <CTtpollard!> has joined #yocto12:38
*** CTtpollard <CTtpollard!> has quit IRC12:42
*** joseppc <joseppc!~josep@linaro/joseppc> has joined #yocto12:44
*** gtristan <gtristan!~tristanva@> has quit IRC12:48
*** CTtpollard <CTtpollard!> has joined #yocto12:50
*** radzy <radzy!> has quit IRC12:50
*** radzy <radzy!> has joined #yocto12:51
*** boucman_work <boucman_work!> has quit IRC13:05
*** rcw <rcw!~rwoolley@> has joined #yocto13:14
*** igor2 <igor2!~igor@> has joined #yocto13:15
*** challinan <challinan!> has quit IRC13:25
*** challinan <challinan!> has joined #yocto13:28
*** tobias_ <tobias_!> has joined #yocto13:36
tobias_anyone have some experience with HP ProDesk 600 G2 mini ? i cant get it to boot. It runs the installer but after its done and reboots it prints "efi: requested map not found"13:38
*** armpit <armpit!~akuster@2601:202:4001:9ea0:94d9:eae7:71b3:4646> has quit IRC13:40
*** Nilesh_ <Nilesh_!uid116340@gateway/web/> has quit IRC13:47
*** caiortp <caiortp!~inatel@> has quit IRC13:48
*** armpit <armpit!~akuster@2601:202:4001:9ea0:94d9:eae7:71b3:4646> has joined #yocto13:53
*** caiortp <caiortp!~inatel@> has joined #yocto13:54
*** paulg <paulg!~paulg@> has joined #yocto13:54
*** AndersD <AndersD!> has quit IRC13:59
*** tomz_ <tomz_!~tomz@> has joined #yocto14:08
*** billr <billr!~wcrandle@> has joined #yocto14:09
*** tobias_ <tobias_!> has quit IRC14:14
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has quit IRC14:15
*** blueness <blueness!~blueness@gentoo/developer/blueness> has quit IRC14:25
*** blueness__ <blueness__!> has quit IRC14:26
*** indie_ <indie_!~indie@> has joined #yocto14:26
*** blueness__ <blueness__!> has joined #yocto14:31
*** sveinse <sveinse!> has joined #yocto14:32
sveinseAre there any benefits from letting multiple yocto trees, versions and machines use the same sstate cache? E.g. building for ARM vs Intel. Or one build building for jethro while another is building krogoth.14:36
kergothyes. particularly in the former case. many 'native' recipes are built, which target the build machine. those are teh same between MACHINEs14:37
CTtpollard+1, althought may not be quite as usual across different releases, but certainly targets14:39
sveinseHow do you share sstate across multiple users? I mean, do you allow all users to contribute to the common sstate? Or do you only generate it from a controlled build, like a build server?14:40
sveinseDo you allow it grow indefinitely?14:40
*** anselmolsm <anselmolsm!~anselmols@> has quit IRC14:41
sveinseNFS is the only scheme that can be used that provides a two-way update of the remote sstate cache?14:41
*** anselmolsm <anselmolsm!~anselmols@> has joined #yocto14:43
*** ntl <ntl!> has quit IRC14:44
kergothsveinse: that's really up to you14:45
*** anselmolsm <anselmolsm!~anselmols@> has quit IRC14:45
kergothwe control our sstate size by removing files based on access time. i.e. nothing has used the file in over a week, gone14:45
*** maxin <maxin!> has quit IRC14:48
sveinsekergoth: Ah, that's a pretty smart way of managing it. (Yet this is the first time in years I've heard a use case for atime)14:49
*** anselmolsm <anselmolsm!~anselmols@> has joined #yocto14:50
kergoth:) yeah, i've used it both for yocto downloads and sstate, and it's about the only time i've used it too14:51
sveinsehow do you share to the users?14:51
kergoththat depends14:52
kergothat my company, we update our sstate on an internal server from our automated builds with rsync and share that via http, and have a cron job on that server for the atime cleanup14:52
kergothsame with downloads14:52
rburtonnote that sstate over NFS is good at exposing bad NFS servers14:52
kergothhah, indeed14:52
sveinseMany of our devs are remote, so VPN is being used, with NFS begin tricky at best. So I think we'll settle at http.14:55
sveinseTo my understanding that will build up a local sstate cache with what has been downloaded and what has been generated locally, right? So I could make a script that rsync back from the user's local sstate to the server sstate cache, and thus providing to the sstate pool?14:56
rburtonor do a nightly automated build to populate the cache14:56
*** lamego <lamego!~jose@> has joined #yocto14:56
sveinserburton: yeah, for those builds that are "mainline". However, like now, where I'm experimenting with new BSPs and Yocto version. At the start of this conversation it was said that there are advantages to share sstate caches across such changes. And there are multiple devs working on these experiments, so sharing is a great way of doing this14:58
sveinse(But we might consider multiple sstate caches for the different development stages)14:59
*** visaev <visaev!~visaev@> has quit IRC15:02
sveinse(this is going to be interesting: Storing sstate cache on a NTFS fs... Windows runs into corners when ':' are encountered)15:04
rburtonnot sure we support sstate on ntfs15:05
rburtoncan you even create a file with : in on ntfs?15:05
*** Nilesh_ <Nilesh_!uid116340@gateway/web/> has joined #yocto15:05
rburtonkhem: <— thoughts?15:06
sveinserburton: I'm out of disk space -- again -- and I'm syncing sstate-cache to a small USB3 drive I have with NTFS. It seems ubuntu's fusefs is happy with it. Let's see how it goes15:07
dl9pfHow do I workaround (INSANE_SKIP):   QA Issue: failed sanity test (workdir) in path [....]sysroot-destdir/usr/lib [la]15:09
rburtondfrey: well one fix is to delete the .la files as they're pointless and cause problems like this.15:10
*** sgw_ <sgw_!sgw_@nat/intel/x-ulecfkvfpcbhbbbe> has joined #yocto15:10
kergothwe just rsync from our automated builds to populate the cache for engineers to use, and don't share sstate for changes not in mainline, here. sstate can bloat up awfully fast with every little local change you're making.15:10
nishahello! is there any way I can have a recipe point to a local git repo rather than a remote one?15:11
kergothnisha: either use externalsrc or a file: url. i.e. git:///some/local/path;protocol=file15:11
dl9pfrburton: roger that, I'll add that to the recipe. Now how can I workaround it for the build with INSANE_SKIP ?15:11
kergoththat'll pass file:///some/local/path to the git-clone15:11
nishakergoth, thanks! I'll try that15:12
rburtondl9pf: well if you delete the file it can't trigger the sanity check15:12
rburtonyou want to fix it as otherwise you've a way of breaking future builds15:12
rburton(which is why the check exists)15:12
dl9pfrburton: yes the fix will be done (rm .la) - for the moment I need to build to proceed, so I can find the other failing stuff15:13
sveinserburton: Just unplugged my NTFS drive with sstate cache and plugged it into windows. It seems to be intact. That is I see the files, but I can't read them.15:14
rburtondl9pf: INSANE_SKIP_(package) += "workdir" iirc.  but if you're editing the recipe then just throw in a rm15:14
sveinseI had a suspicion that that would happen. NTFS is a fairly agnostic file system in this respect. Its windows GUI which is croaking on "invalid" filenames15:15
rburtonsveinse: ah interesting15:15
sveinseNTFS even have symlinks. Windows don't use it, themselves thou15:15
dl9pfrburton: tnx. I'll have to poke the recipe maintainer.15:15
*** ntl <ntl!> has joined #yocto15:16
*** paulg <paulg!~paulg@> has quit IRC15:18
nishakergoth, I get an error: Failed to fetch URL git:///path/to/local/repo;protocol=file15:18
kergothinsufficient information. check the do_fetch log file15:18
*** radzy <radzy!> has quit IRC15:19
nishahmm...not sure why it is doing this: DEBUG: For url git:///home/nisha/work/cascadia/dlt-daemon;protocol=file returning
nishaso it's looking for a tarball?15:22
*** radzy <radzy!> has joined #yocto15:23
*** dreyna <dreyna!> has joined #yocto15:23
*** Crofton <Crofton!~Crofton@> has joined #yocto15:28
*** sameo <sameo!~samuel@> has joined #yocto15:34
*** vmesons <vmesons!> has joined #yocto15:37
*** vmeson <vmeson!> has quit IRC15:38
sveinseI keep getting "fatal: Not a git repository (or any parent up to mount point /home)" multiple times while building an image. How can I track down which recipe generate this?15:41
*** sameo <sameo!~samuel@> has quit IRC15:44
*** sameo <sameo!~samuel@> has joined #yocto15:44
*** benjamirc <benjamirc!~besquive@> has joined #yocto15:45
*** paulg <paulg!~paulg@> has joined #yocto15:46
*** rajm <rajm!> has quit IRC15:48
rburtonsveinse: i've seen older pulseaudio releases do that but we patch that out of them now15:51
rburtonyou could enable kernel auditing and get a trace of file access for /home/.git/15:52
*** aehs29 <aehs29!~aehernan@> has joined #yocto15:56
billrsvense: I've seen that before when the git repo bb is trying to access is not on the same filesystem as the build directory. E.g., it's symlinked to someplace else or it's on a bin-mount fs.15:57
*** Crofton <Crofton!~Crofton@> has quit IRC15:58
*** AgentElrond <AgentElrond!> has joined #yocto15:58
*** Crofton <Crofton!~Crofton@> has joined #yocto15:59
*** fl0v0 <fl0v0!> has quit IRC16:04
*** joshuagl <joshuagl!~joshuagl@> has quit IRC16:06
sveinserburton: Good idea -- My knowledge of kernel tracing is limited, but we can assume that is's the git executable accessing .git, can't we? And the parent process to git is bitbake isn't it?16:06
*** Crofton <Crofton!~Crofton@> has quit IRC16:08
rburtonits quite possibly a trying to determine if its in a git clone to mark the version, or something16:09
jubrsveinse: BB_NUMBER_THREADS = '1' with a `bitbake $image-recipe | cat -` will give you nice sequential output - it skips the fancy rendering16:14
rburtonyou could grep the cooker log to see if the message ended up in there, and if it did work out what tasks were active at the time16:17
kergothcat - is redundant, fyi, cat reads from stdin and writes to stdout  by default16:21
kergothjust | cat will do16:21
* jubr could pretend he borked his copy-paste of `| cat -n` -- but he won't :)16:25
jubrtnx for the tip!16:26
*** maxin <maxin!> has joined #yocto16:26
*** Anticom <Anticom!~timo.m@> has quit IRC16:26
AgentElrondI'm having a Yocto problem on Debian.  I'm fairly new to Yocto so I'm ignorant of many things, but I've been told that there are "virtual" names in some places for packages, of the form "virtual/whatever"16:31
AgentElrondFor some reason, the Yocto build I'm attempting, with Debian package generation, is generating a DEBIAN/control file that still includes the full "virtual/whatever" in the package name.16:32
AgentElrondBecause '/' is an invalid character for a package name, this fails the build immediately16:32
AgentElrondAny ideas what I might be missing would be appreciated!16:32
AgentElrondThis is Yocto-2.0.1 for reference.16:33
jubrAgentElrond: I recall you doing a `bitbake -c menuconfig virtual/kernel`, can you try if using the real recipe would help? Probably something like `linux-$machine`16:42
AgentElrondjubr:  I haven't used menuconfig or any "virtual/whatever" in the command-line.  I have just used "bitbake overall-package-whatever"16:44
*** maxin <maxin!> has quit IRC16:49
*** moto-timo <moto-timo!~ttorling@> has joined #yocto16:51
*** moto-timo <moto-timo!~ttorling@fsf/member/moto-timo> has joined #yocto16:51
AgentElrondThis is similar to what I'm seeing:
rburtonAgentElrond: i think that was a bug in the recipes, virtual/ shouldn't be used in target packages.  meta-oe had some fixes for that.16:56
AgentElrondThis is even closer to what I see.
AgentElrondRPROVIDES specifically seems to be the line that causes issues with virtual/ for do_package_write_deb16:57
rburtonbasically recipes shouldn't be using /  in target names as dpkg doesn't like them16:58
rburtonunfortuntately nobody actually tests with dpkg16:58
rburtonbecause 99% of people use rpm or opkg, which don't object as much16:58
rburtonso my recommendation is "use opkg or rpm", followed by fix the recipes to not use virtual/ in target package names16:59
rburtonas build-time PROVIDES/DEPENDS its fine16:59
AgentElrondNoted :)16:59
kergothdefinitely stop using / in package names anyway16:59
AgentElrondWould fixing the RPROVIDES line be a likely solution, or is it going to be more trouble than it's worth?16:59
rburtonits *the* fix17:00
AgentElrondThanks again, sorry about the spam17:00
*** igor2 <igor2!~igor@> has quit IRC17:00
*** igor2 <igor2!~igor@> has joined #yocto17:01
stwcxrburton: Does PROVIDES solves RDEPENDS needs?17:01
*** joseppc <joseppc!~josep@linaro/joseppc> has quit IRC17:02
stwcxPackage A RDEPENDS on virtual/foo.  Package B PROVIDES virtual/foo?17:02
kergothprovides/depends are build time, rprovides/rdepends are run time. two en tirely different namespaces17:02
stwcxSo how do you solve the RDEPENDS without using a slash?17:03
*** jkridner|playdoh <jkridner|playdoh!> has joined #yocto17:03
*** istarilucky1 <istarilucky1!~rlucca@> has joined #yocto17:03
sveinseyocto has some notable differences from Debian package building17:04
AgentElrondstwcx:  Perhaps a package RDEPENDS on a name without a slash, e.g. YOUR_PREFIX_package?17:05
*** istarilucky <istarilucky!~rlucca@> has quit IRC17:05
stwcxAgentElrond: The point of virtual is to be able to abstract a concept though.  A package can need virtual/foo and multiple packages can satisify virtual/foo in their own wa.17:06
kergotheither use VIRTUAL-RUNTIME, which is a way of selecting runtime packages using build time variables rather than selection at the package manager level, or use rprovides/rdepends without a /17:07
*** gtristan <gtristan!~tristanva@> has joined #yocto17:07
kergothvirtual/ is just a convention anyway, your virtaul package name can be anything17:07
kergothcall it 'blah' for all we care17:07
stwcxvirtual/ssl is an example on some systems because openssl and libressl both provide the same functionality.17:07
kergothso call it virtual-ssl and move on17:07
stwcxkergoth: With that in mind, is there any reason for them to not be virtual-foo ?17:07
stwcx;)  Ok.17:07
kergothagain, the name can be anything the package manager supports17:07
kergothvirtual/ is a convention, that's all17:07
kergothand a convention only for build time at that17:08
stwcxkergoth: I wasn't sure if Yocto has anything special for virtual/.  I do see that in a few .py files when I do a grep.17:08
kergoththere are a couple bits primarily to strip off or add back the prefix, when our bbclasses mangle the name17:08
kergothso e.g. it ends up virtual/nativesdk-foo, not nativesdk-virtual/foo17:08
kergothminor stuff17:08
kergothcan't think of much else off the top of my head, but maybe there's other bits. hopefully not17:09
*** dmoseley <dmoseley!> has joined #yocto17:10
stwcxkergoth: There is a little bit of stuff in lib/bb/ and lib/bb/ looks the most interesting.17:10
stwcxLooks like it creates a special log file of those virtual lookups.17:10
kergothsounds questionable, it should be able to identify cases where multiple recipes provide the same thing and use that, but i could be missing something17:11
* kergoth shrugs17:11
*** Guest2569 <Guest2569!500fd832@gateway/web/freenode/ip.> has quit IRC17:13
*** paulg <paulg!~paulg@> has quit IRC17:13
*** aehs29 <aehs29!~aehernan@> has left #yocto17:30
*** paulg <paulg!~paulg@> has joined #yocto17:36
*** belen <belen!Adium@nat/intel/x-dovdopponbtqwbqv> has quit IRC17:46
sveinseHow do I resolve a dependency loop? I got a large printout of two identified loops, but I have to admit I have problems seeing where the loop is17:53
kergothgood question, everybody has that problem :)17:53
kergoththe info is better than nothing, but it's still a lot of troubleshooting and manual digging into the recipes mentioned17:53
sveinseThat is, I do know where it comes from: I added a dependency on qtbase from avahi.17:54
kergothokay, so remove that and then dig into the dependency graph to see why qtbase depends on avahi.17:54
kergothbitbake -u depexp -g qtbase may be of use, or bb whatdepends avahi qtbsae if you have bb, or a number of other options17:55
sveinseI added a PACKAGECONFIG --enable-qt5 to avahi.17:55
kergoththey'll at least show the dependency graph, if not the *why*17:55
kergothright, so obviously if that introduces a cycle, then we know qt must need avahi as well as avahi needing qt. so again, dig into the former17:55
sveinsekergoth: wasn't there a dot that could show the deps?17:55
kergoththat's what bitbake -g is17:56
kergoth-u depexp gives an x11 gui to that info17:56
sveinseah, right17:56
kergothbut bitbake -g and examining the .dot files or using graph-tool woudl be an option too17:56
kergothfrom a quick check with whatdepends, it's pulseaudio. qtbase wants both pulseaudio and libnss-mdns, both of which result in pulseaudio being built, and pulseaudio wants avahi.17:59
sveinseyes, I just found the same thing: qtbase wants pulseaudio, which wants avahi. So when I setup avahi to depend on qt5base....18:01
*** willeponken <willeponken!> has quit IRC18:02
sveinseThere is no way round this I suppose other than building the package twice? Make a new recipe avahi-qt5 which only packages libavai-qt5?18:02
sveinsehmm, then you run a real risk of packages being out of sync...18:03
kergothunless you don't want pulseaudio and can disable that in qtbase, yeah, i think that's about the only way, unless you arrange for special tasks to subvert the cycle18:03
sveinseNo, we don't use pulseaudio. So that might be the approach. Thanks18:04
*** dmiess__ <dmiess__!d0517801@gateway/web/freenode/ip.> has joined #yocto18:05
* sveinse thinks fiddling in qt5 recipes is always a lot of fun18:05
dmiess__Hi, I'm trying to get sshd running on a small image I'm creating but I'm running into some trouble. It seems that the start script isn't running because there is no file /etc/init.d/functions18:07
dmiess__I've added the server to my image with the following line: IMAGE_FEATURES += "debug-tweaks ssh-server-openssh"18:07
*** anselmolsm <anselmolsm!~anselmols@> has quit IRC18:12
*** jkridner|playdoh <jkridner|playdoh!> has quit IRC18:12
*** anselmolsm <anselmolsm!~anselmols@> has joined #yocto18:12
*** aehs29 <aehs29!~aehernan@> has joined #yocto18:12
*** pohly <pohly!> has joined #yocto18:16
*** nisha <nisha!~nisha@> has quit IRC18:20
*** jkridner|playdoh <jkridner|playdoh!> has joined #yocto18:21
*** jkridner|work <jkridner|work!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto18:25
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC18:29
*** aehs29 <aehs29!~aehernan@> has quit IRC18:32
*** tyler-baker <tyler-baker!tyler-bake@gateway/shell/linaro/x-wewmwzqrbtbwqlek> has quit IRC18:38
*** tyler-baker <tyler-baker!tyler-bake@linaro/tyler-baker> has joined #yocto18:38
*** aehs29 <aehs29!~aehernan@> has joined #yocto18:43
sveinseWow. DISTRO_FEATURES_BACKFILL_CONSIDERED has to be yoctos most nonintuitive variable, IMHO.18:44
kergoththe concept is actually pretty simple. backfilled features are appended regardless of what you set DISTRO_FEATURES to. considered backfilled features are those you've explicitly decided you want disabled anyway.18:45
kergothbut the variable naming is perhaps not ideal18:45
kergothbackfill is needed to let the core change the default distro features even when external distros set (rather than add/remove) DISTRO_FEATURES in their distro .conf18:46
sveinseBut I use this to /remove/ functionality (pulseaudio in my case). So please explain BACKFILL? My lingual interpretation of "backFILL" and consider, suggests adding something, doesn't it?18:47
kergothi just told you18:48
kergothDISTRO_FEATURES_BACKFILL are items added to DISTRO_FEATURES behind the scenes18:48
kergothit *is* adding something18:48
kergoththe _CONSIDERED part says you considered those items and want them not backfilled. as i said, that variable naming is likely not ideal. DISTRO_FEATURES_BACKFILL is named appropriately, but DISTRO_FEATURES_BACKFILL_CONSIDERED Is less than intuitive18:48
sveinseokay. I'm not going to make this my fight anyways, I was just curious. Perhaps DISTRO_FEATURES_BACKFILL_OMIT or some other negative/subtractive statement would have been better. EOD for my part :D18:51
kergothi'm agreeing with you. i said 2-3 times, the _CONSIDERED variable is likely named badly :P18:51
sveinseyes, I got that XD18:52
kergothnot the first time our variable naming wasn't ideal18:52
kergothsadly we're stuck with it unless we provide compatibility along the way18:54
sveinseI find the obsession about using 'tmp' really fun18:54
*** istarilucky1 <istarilucky1!~rlucca@> has quit IRC18:55
kergothover the years plenty of folks had moved the output of the build out of tmpdir, but once sstate was added that become not really possible due to how sstate packaging works (paths are all relative to the same root)18:55
kergothwould be nice to add support for that again by adding an intermediate path for the sstate archival18:55
*** istarilucky <istarilucky!~rlucca@> has joined #yocto18:55
kergothworth noting that you can trivially rename it to something else, if you want. it's not an obession, it's a default directory name. TMPDIR = "${TOPDIR}/foo" for example18:56
kergothhaving everything we do relative to $PWD was a key design consideration when we started the project -- we needed to stay self contained to avoid mucking with the user's system18:56
*** paulg <paulg!~paulg@> has quit IRC18:57
sveinsethat's fair enough, it just seems... odd18:57
kergothhow so? the vast majority of what ends up there is temporary, it's just intermediate artifacts of the build process.18:57
sveinseAnd you have more than one tmp. each recipe has its own tmp and a work. So you'll end up typing tmp a lot when doing development18:58
*** dmoseley <dmoseley!> has quit IRC19:00
sveinsewell, tmp/deploy/images is an output, not a temporary directory. But perhaps the thinking is that you have a build management system that fetches the artefacts from tmp/, moves it elsewhere and deletes the tmp dir19:00
sveinseI haven't got any problems with this, I just raised my eyebrows a few times when getting used to this. I guess all build systems has its own things and quirks19:02
*** Biliogadafr <Biliogadafr!> has joined #yocto19:03
*** rcwoolley_ <rcwoolley_!~rwoolley@> has joined #yocto19:08
*** dmoseley <dmoseley!> has joined #yocto19:09
*** rcw <rcw!~rwoolley@> has quit IRC19:11
*** Girafferson <Girafferson!~Giraffers@2601:281:8500:95b0:5249:f3c:d4e2:30a9> has joined #yocto19:14
*** paulg <paulg!~paulg@> has joined #yocto19:31
sveinseIs it possible to exclude recipes from builds? We have a meta layer which provides recipes for our application and images. Depending on which BSP we use, different image recipes must be used. Unfortunately unreferenced recipes still fail on require, so we cannot collect all of them into one layer when a globbed BBFILES path is used in layer.conf19:35
*** maxin <maxin!> has joined #yocto19:41
*** Crofton <Crofton!~Crofton@> has joined #yocto19:44
kergothsveinse: you can break up your repo so some appends are only used if the corresponding layer is included in teh configuration.19:48
*** Girafferson <Girafferson!~Giraffers@2601:281:8500:95b0:5249:f3c:d4e2:30a9> has left #yocto19:48
*** pohly <pohly!> has quit IRC19:48
kergothsveinse: add or equivalent (other layers do this too), then move your appends into a subdir based on the layer name (as used in BBFILE_COLLECTIONS, not the path on disk. i.e. 'openembedded-layer' not 'meta-oe')19:49
*** rubdos <rubdos!> has joined #yocto19:51
*** nillerbrun <nillerbrun!> has quit IRC19:53
*** Crofton <Crofton!~Crofton@> has quit IRC19:54
*** jkridner|playdoh <jkridner|playdoh!> has quit IRC19:59
*** jkridner <jkridner!> has joined #yocto20:01
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto20:01
*** maxin <maxin!> has quit IRC20:04
*** pohly <pohly!~pohly@> has joined #yocto20:04
*** aehs29 <aehs29!~aehernan@> has quit IRC20:05
*** aehs29 <aehs29!aehernan@nat/intel/x-rgmqyslawqwasisi> has joined #yocto20:05
*** nisha <nisha!~nisha@> has joined #yocto20:06
*** istarilucky <istarilucky!~rlucca@> has quit IRC20:10
*** Girafferson <Girafferson!~Giraffers@2601:281:8500:95b0:5249:f3c:d4e2:30a9> has joined #yocto20:10
*** grma <grma!~gruberm@> has quit IRC20:10
*** aehs29 <aehs29!aehernan@nat/intel/x-rgmqyslawqwasisi> has quit IRC20:12
*** aehs29 <aehs29!aehernan@nat/intel/x-umfpqmovaofwcruf> has joined #yocto20:13
*** Artox <Artox!~Artox@> has quit IRC20:14
*** gtristan <gtristan!~tristanva@> has quit IRC20:16
*** willeponken <willeponken!> has joined #yocto20:20
*** dmoseley <dmoseley!> has quit IRC20:23
AgentElrondHmm.  I'm guessing if I rename part of the path above the yocto build, the build will be invalidated or fail?20:25
AgentElronde.g. once a build has already finished, if I rename the directory to yocto_bob instead of yocto_default?20:26
*** milindur <milindur!0592f853@gateway/web/freenode/ip.> has joined #yocto20:26
GiraffersonI'm assuming all you'd need to do is source ae-init-build-env again20:27
AgentElrondI was afraid absolute paths would get baked into dependencies / caches / scripts / whatever20:28
AgentElrondPerhaps my fears were groundless20:28
*** milindur is now known as milindur_20:30
kergothAgentElrond: you'll need to wipe tmp20:30
*** rcwoolley_ <rcwoolley_!~rwoolley@> has quit IRC20:30
*** milindur_ is now known as milindur20:30
AgentElrondkergoth:  Thanks, that's what I was afraid of.  The tmp directory is some 3+ hours of building and 11+ GB of data.20:32
kergothif your sstate is outside of tmp, rebuilding from sstate is trivial20:32
kergothdoesn't take long at all20:32
AgentElrondWell, my system might be very slow to compile20:33
AgentElrondBut I'll bear that in mind20:33
kergothsstate is prebuilt binaries, the whole point of sstate is to *not* compile.20:33
kergothbuilds from sstate == extracting some tarballs20:33
AgentElrondThank you for yet again correcting my ignorance20:34
AgentElrondI'm TRYING to educate myself on some things via google and hands-on experience, but I still spam the IRC channel more than is necessary20:35
kergoththere's a lot to pick up, quite a learning curve. worthwhile, but still a lot of complexity to pick up20:35
*** slidercrank <slidercrank!~slidercra@unaffiliated/slidercrank> has joined #yocto20:36
*** milindur <milindur!0592f853@gateway/web/freenode/ip.> has quit IRC20:37
*** blueness <blueness!~blueness@gentoo/developer/blueness> has joined #yocto20:39
*** milindur <milindur!> has joined #yocto20:43
*** dmiess__ <dmiess__!d0517801@gateway/web/freenode/ip.> has quit IRC20:45
*** pohly <pohly!~pohly@> has quit IRC20:52
*** AgentElrond <AgentElrond!> has quit IRC20:53
*** milindur <milindur!> has quit IRC20:53
*** milindur <milindur!> has joined #yocto20:53
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC20:54
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto20:54
*** milindur <milindur!> has quit IRC20:54
*** milindur <milindur!> has joined #yocto20:54
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC20:55
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto20:55
*** paulg <paulg!~paulg@> has quit IRC20:59
*** milindur <milindur!> has quit IRC20:59
*** jkridner_ <jkridner_!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto21:00
*** Artox <Artox!~Artox@> has joined #yocto21:01
*** jkridner|work <jkridner|work!~jkridner@pdpc/supporter/active/jkridner> has quit IRC21:01
*** fledermaus <fledermaus!~vivek@> has joined #yocto21:04
*** jkridner|playdoh <jkridner|playdoh!> has joined #yocto21:05
*** jkridner_ <jkridner_!~jkridner@pdpc/supporter/active/jkridner> has quit IRC21:06
*** jkridner_ <jkridner_!> has joined #yocto21:06
*** jkridner|work <jkridner|work!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto21:07
*** caiortp <caiortp!~inatel@> has quit IRC21:07
*** milindur <milindur!> has joined #yocto21:08
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC21:09
*** jkridner|playdoh <jkridner|playdoh!> has quit IRC21:10
*** istarilucky <istarilucky!~rlucca@> has joined #yocto21:12
*** JaMa <JaMa!> has quit IRC21:14
*** berton <berton!~fabio@> has quit IRC21:17
*** jkridner_ <jkridner_!> has quit IRC21:20
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto21:21
*** nighty <nighty!> has quit IRC21:24
*** anselmolsm <anselmolsm!~anselmols@> has quit IRC21:30
*** Nilesh_ <Nilesh_!uid116340@gateway/web/> has quit IRC21:47
*** rubdos <rubdos!> has quit IRC21:48
*** jkridner_ <jkridner_!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto21:52
*** jkridner|playdoh <jkridner|playdoh!~jkridner@2601:409:8500:9430:6d7b:dba9:6c3e:1fda> has joined #yocto21:53
*** jkridner|work <jkridner|work!~jkridner@pdpc/supporter/active/jkridner> has quit IRC21:54
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC21:54
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto21:54
*** jkridner_ <jkridner_!~jkridner@pdpc/supporter/active/jkridner> has quit IRC21:57
*** bfederau <bfederau!> has quit IRC22:01
*** fmeerkoetter <fmeerkoetter!> has quit IRC22:01
*** fmeerkoetter <fmeerkoetter!> has joined #yocto22:01
*** bfederau <bfederau!> has joined #yocto22:01
*** LocutusOfBorg <LocutusOfBorg!~Gianfranc@ubuntu/member/locutusofborg> has quit IRC22:01
*** paulg <paulg!> has joined #yocto22:03
-YoctoAutoBuilder- build #875 of nightly-ppc-lsb is complete: Success [build successful] Build details are at
*** LocutusOfBorg <LocutusOfBorg!~Gianfranc@ubuntu/member/locutusofborg> has joined #yocto22:05
*** Biliogadafr <Biliogadafr!> has quit IRC22:08
*** blueness <blueness!~blueness@gentoo/developer/blueness> has quit IRC22:21
*** blueness <blueness!~blueness@gentoo/developer/blueness> has joined #yocto22:22
*** jkridner|playdoh <jkridner|playdoh!~jkridner@2601:409:8500:9430:6d7b:dba9:6c3e:1fda> has quit IRC22:27
*** jkridner|playdoh <jkridner|playdoh!~jkridner@2601:409:8500:9430:d07a:3c1d:4764:ab92> has joined #yocto22:28
*** nighty <nighty!> has joined #yocto22:33
*** benjamirc <benjamirc!~besquive@> has quit IRC22:35
*** lamego <lamego!~jose@> has quit IRC22:39
*** istarilucky <istarilucky!~rlucca@> has left #yocto22:39
*** igor2 <igor2!~igor@> has quit IRC22:40
*** LocutusOfBorg <LocutusOfBorg!~Gianfranc@ubuntu/member/locutusofborg> has quit IRC22:46
*** ntl <ntl!> has quit IRC22:55
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC22:57
*** nighty- <nighty-!> has quit IRC22:59
*** jkridner|playdoh <jkridner|playdoh!~jkridner@2601:409:8500:9430:d07a:3c1d:4764:ab92> has quit IRC23:02
*** jkridner <jkridner!~jkridner@2601:409:8500:9430:d07a:3c1d:4764:ab92> has joined #yocto23:02
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto23:02
-YoctoAutoBuilder- build #890 of nightly-x86-lsb is complete: Success [build successful] Build details are at
*** fledermaus <fledermaus!~vivek@> has quit IRC23:06
*** blueness <blueness!~blueness@gentoo/developer/blueness> has quit IRC23:25
*** blueness <blueness!~blueness@gentoo/developer/blueness> has joined #yocto23:27
*** paulg <paulg!> has quit IRC23:29
*** nighty <nighty!> has quit IRC23:31
-YoctoAutoBuilder- build #902 of nightly-x86 is complete: Failure [failed BuildImages Running Sanity Tests] Build details are at

Generated by 2.11.0 by Marius Gedminas - find it at!