Can you elaborate more on description of this bug and ad logs
Created attachment 3880 [details] nightly-deb errors log
while testing Fedora 26, buildset nightly-deb failed with error: core-image-minimal-1.0r0 dorootfs: Function failed: dorootfs. Full error log attached for more details
Please attach plain logs, not xml ones. The key error here is Index creation command 'cd TOPDIR/tmp/deploy/deb/qemux86; PSEUDO_UNLOAD=1 TOPDIR/tmp/work/qemux86-poky-linux/core-image-sato-sdk/1.0-r0/recipe-sysroot-native/usr/bin/apt-ftparchive packages . > Packages;TOPDIR/tmp/work/qemux86-poky-linux/core-image-sato-sdk/1.0-r0/recipe-sysroot-native/usr/bin/gzip -fc Packages > Packages.gz;PSEUDO_UNLOAD=1 TOPDIR/tmp/work/qemux86-poky-linux/core-image-sato-sdk/1.0-r0/recipe-sysroot-native/usr/bin/apt-ftparchive release . >> Release' failed with return code 1: TOPDIR/tmp/work/qemux86-poky-linux/core-image-sato-sdk/1.0-r0/recipe-sysroot-native/usr/bin/apt-ftparchive: TOPDIR/tmp/sysroots-uninative/x86_64-linux/usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.23' not found (required by TOPDIR/tmp/work/qemux86-poky-linux/core-image-sato-sdk/1.0-r0/recipe-sysroot-native/usr/bin/../lib/libapt-pkg.so.5.0) so looks like a uninative glibc compatibility issue with previous versions.
I suspect the reproducer here would be to build apt-native on a modern distro, then share an sstate feed and reuse that apt-native sstate on an older distro where it would then fail with this symbol error. Sonia: Which distro did this fail on?
(In reply to comment #5) > I suspect the reproducer here would be to build apt-native on a modern > distro, then share an sstate feed and reuse that apt-native sstate on an > older distro where it would then fail with this symbol error. > > Sonia: Which distro did this fail on? Sorry, it was fedora 26, Sonia did mention that. I think if we build in fedora26 we might just see this when rebuilding from sstate. We might be able to upgrade uninative to a newer glibc to resolve this?
Created attachment 3917 [details] just lor error lines. I have updated glibc, also did a full system update and the sstate are already mounted on fedora 26 and still getting error with do_rootfs. Im attaching just the log lines that describe error, to do it more readable.
(In reply to comment #7) > Created attachment 3917 [details] > just lor error lines. > > I have updated glibc, also did a full system update and the sstate are > already mounted on fedora 26 and still getting error with do_rootfs. > > Im attaching just the log lines that describe error, to do it more readable. Which revision of the metadata was this with?
(In reply to comment #8) > (In reply to comment #7) > > Created attachment 3917 [details] > > just lor error lines. > > > > I have updated glibc, also did a full system update and the sstate are > > already mounted on fedora 26 and still getting error with do_rootfs. > > > > Im attaching just the log lines that describe error, to do it more readable. > > Which revision of the metadata was this with? First test i ran was with 6964efddd31c479386d1643c1025bc102710392f and today i ran a newest review bc2e0b2e9b95707d96c840dade12b00e1450ecc3 but error is still there. As reference, below ius the glib-c packages list installed on worker fedora26. in case it helps. glibc.x86_64 2.25-9.fc26 @updates glibc-all-langpacks.x86_64 2.25-9.fc26 @updates glibc-common.x86_64 2.25-9.fc26 @updates glibc-devel.x86_64 2.25-9.fc26 @updates glibc-headers.x86_64 2.25-9.fc26 @updates glibc-langpack-en.x86_64 2.25-9.fc26 @updates
I've no idea no this one, suggest moving to 2.5 or assign to others.
We've not seen this on the autobuilder in recent times.