Just a wild guess, but could your corporate proxy, which is kind of visible in the provided logs, intervene with this - to me it seems to be some MITM box. Do you have any chance to try it without tha

#yocto #kernel

Hi all, I have a few oeqa test cases, which always should run last in a test suite (log and file collectors for instance). Due to the ordering of the test case discovery I had to name all those tests

Hi all, I have a bunch of custom testcases (oeqa/runtime/cases) which are interacting with "d" from the build host - basically fetching some info while executing the test, e.g. foo = self.tc.td['MY_CU

I would recommend that you go for a systemd drop-in file [1]. That would be something like a small snippet placed to /etc/systemd/system/dbus-org.bluez.service/override.conf In that file place somethi

Thanks Tim, for taking this discussion. I'm really glad to see that upstream finally recognizes our use case. Unfortunately as that looks pretty "beta" to me so I will keep on with the tiring process

Just add RDEPENDS_${PN] += "python3-json" to the recipe that creates the package, that contains the mentioned python script. Alternatively add IMAGE_INSTALL += "python3-json" to the image the script i

The service is deployed with standard systemd package, which doesn't have that set as far as I see it (no SYSTEMD_AUTO_ENABLE_${PN} in the latest recipe revision) I think, after browsing through the c

Hi, I would recommend that you go for a systemd drop-in file [1]. That would be something like a small snippet placed to /etc/systemd/system/avahi-daemon.service.d/override.conf In that file place som

"github.com[0: 140.82.114.4]: errno=Connection timed out" indicates either a temporary issue with github (unlikely) or with your network setup. Already tried a different network path from your dev-mac

#yocto

Thanks to both of you - seems like I missed out on BB_LOGCONFIG, but it's exactly what I was looking for. Regards Konrad

Hi all, when running bitbake in CI I would like to add an additional log handler to used python logging to catch *ALL* (task warnings, dangling append, qa issues, a.s.o.), instead of manually grepping

Did you had a look at https://github.com/kraj/meta-openwrt/blob/master/recipes-networking/ipset/ipset_6.38.bb yet? That pretty much looks like the one you were looking for, but for an older version, r

Hi Armin, that sounds good. Please keep me in the loop. BTW did you/the project create any kind of roadmap, just out of interest? BR Konrad

Hi, is this just a demo, or are there plans to broaden the scope of this layer? To me it would make perfectly sense to have more of these features (besides sudo, openssh and root-pwd) and I'm willing

I think some RDEPENDS entries are missing, by looking at https://github.com/googleapis/oauth2client/blob/master/setup.py install_requires = [ 'httplib2>=0.9.1', 'pyasn1>=0.1.7', 'pyasn1-modules>=0.0.5

I assume you tried to compile on the target using the resulting image, if that's the case the package isn't installed. By using 'oe-pkgdata-util find-path */libc.a' in your build workspace, you could

#sdk #yocto #linux

I assume that you have ssh access to the device and your rootfs is writeable - in that case you could use "devtool deploy-target". Typical workflow would be something like this - devtool modify python

Hi Mikeal, To me it seems like the makefile has no support for DESTDIR builtin - which is the mechanism poky relies on. I've seen this projects offers a cmake file as well, maybe you have more luck wi

I would say a `DEPENDS += "sed"` in the recipe should fix things - btw sumo is kind of ancient already, ever considered updating to a newer version of poky?

Hi, I guess https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#new-recipe-post-installation-scripts is what you looking for. Best Konrad