From: Jens Rehsack <sno@...> Add recipe for companion of IBM Software TPM 2.0 - IBM's TPM 2.0 TSS. It's a user space TSS for TPM 2.0. Signed-off-by: Jens Rehsack <sno@...> --- ...efile.a

From: Jens Rehsack <sno@...> Update ibmswtpm2 from 1628 to 1637. Build 1637 Includes: * Increase NV memory size to match PC Client RSA 3072 requirements * Add and fix ACT support * Update Visua

Update ibmswtpm2 from 1628 to 1637. Build 1637 Includes: * Increase NV memory size to match PC Client RSA 3072 requirements * Add and fix ACT support * Update Visual Studio files to 2019. Signed-off-b

The files "installed-package-names.txt" are not available in my setup (IIRC one has to enable that explicitly). You're right. Ages ago - in April 2015 - I added that to my busybox configuration, since

Unfortunately both include coreutils, see attached pn-buildlist (I can send you the recipe-depends and the task-depends, either if you need them). Seems similar to my kind of soon :-)

So far, so good. They way to fix that seems either to check why busybox uses ${base_bindir} nowadays in favor of ${bindir} and fix either busybox or coreutils or attr. What drives me nuts is not only

It's not much what stands there: Downloading file:/home/sno/gpw-community-bsp/mops-yocto-platform/tmp/work/fischer-poky-linux/core-image-minimal-dev/1.0-r0/oe-rootfs-repo/core2-64/libcap-dev_2.25-r0_c

Hi, I got following issue when building an image for live-debugging: ERROR: updatable-app-dev-image-1.0-r0 do_rootfs: Postinstall scriptlets of ['coreutils'] have failed. If the intention is to defer

We didn't figure out how it can easily be done and use a mix of volatile and overlayfs settings to have /etc and /var separated from readonly /. Cheers -- Jens Rehsack - rehsack@...

Hi Michael, That's one of the larger open points in meta-java. I couldn't finish that in my time at Rademacher. If someone wants to sponsor that :-) Meanwhile try to rely on https://github.com/rehsack

IIRC, rrdtool is a good example to do it right. collectd had the same problem as amanda had - wrong perl used ... Maybe vice versa - I'm getting old and forget to remember :D You're welcome. Cheers --

Please compare word wise ... -I/homes/sno/fsl-release-bsp/ornithologen-kann-man-mit-voegeln-eine-freude-machen/tmp/sysroots/x86_64-linux/usr/lib/perl-native/perl/5.22.1/CORE -I/homes/sno/fsl-release-b

I give it a quick shot and got: ../../arm-poky-linux-gnueabi-libtool --tag=CC --mode=compile arm-poky-linux-gnueabi-gcc -march=armv7-a -marm -mthumb-interwork -mfloat-abi=hard -mfpu=neon -mtune=cortex

I did a diff between your 5.20 and poky's 5.22 and realize some fixes applied in 5.22 regarding library path's aren't applied in your copy. Maybe swig relies on wrong library locations and when we kno

I digged a bit through your layer (while my up2date scanner over meta-cpan blocks my build chain :P) and realized that you use perl-5.20.0 as it was in poky. A "simple" downgrade would be more reasona

That's something complete different than "End of regular support, switching to LTS" - so based on missing features, any distribution which doesn't fulfill the required features should be discarded fro

Sure, but are there some serious/expensive maintaining efforts continuing support Debian 7? Or is it an approach to kick Debian from list of supported distributions for (above?) reasons? Since I run s

Are you on poky/master or cherry-picked fe506edd? -- Jens Rehsack - rehsack@...

Yes, we do. All difficulties we'd found are solved in referred initoverlay recipe. Maybe one fine I write a blog post regarding that topic ;) How does that fit into an ro rootfs? It's more stable than

That's what we currently have implemented and running in field for a while with a small difference: 1) We don't use Stefano Babic's software updater, but an own script which deals with initial softwar