On Wed, 2024-01-17 at 14:46 +0200, Dmitry Baryshkov wrote:
> On Thu, 11 Jan 2024 at 15:15, Alexander Kanavin <alex.kana...@gmail.com>
> wrote:
> >
> > shadow 4.14.x adds a number of libraries it dynamically links with
> > (md, bsd, attr). This causes troubles in setscene tasks where
> > shadow executables are used (such as useradd), as pulling in
> > the needed dynamic libraries needs unpleasant special-casing.
> >
> > Signed-off-by: Alexander Kanavin <a...@linutronix.de>
>
> It seems, this is causing issues with the TuxOE builds. We have been
> observing issues with the TuxOE build environment with the image
> creation choking on the home dirs. Reverting this patch seems to fix
> the problem. The build environment is Ubuntu 20.04 running in a
> container on Ubuntu 22.04.
>
> ERROR: rpb-weston-image-1.0-r0 do_image_tar:
> ExecutionError('/oe/build/tmp-rpb_wayland-glibc/work/qcom_armv8a-linaro-linux/rpb-weston-image/1.0/temp/run.do_image_tar.160075',
> 1, None, None)
> ERROR: Logfile of failure stored in:
> /oe/build/tmp-rpb_wayland-glibc/work/qcom_armv8a-linaro-linux/rpb-weston-image/1.0/temp/log.do_image_tar.160075
> Log data follows:
> > DEBUG: Executing python function set_image_size
> > DEBUG: 1402908.000000 = 1079160 * 1.300000
> > DEBUG: 1402908.000000 = max(1402908.000000, 65536)[1402908.000000] + 0
> > DEBUG: 1402908.000000 = int(1402908.000000)
> > DEBUG: 1404928 = aligned(1402908)
> > DEBUG: returning 1404928
> > DEBUG: Python function set_image_size finished
> > DEBUG: Executing shell function do_image_tar
> > tar: ./home/linaro/.bashrc: Unknown file type; file ignored
> > tar: ./home/linaro/.profile: Unknown file type; file ignored
> > tar: Exiting with failure status due to previous errors
> > WARNING:
> > /oe/build/tmp-rpb_wayland-glibc/work/qcom_armv8a-linaro-linux/rpb-weston-image/1.0/temp/run.do_image_tar.160075:146
> exit 1 from '[ $? -eq 1 ]'
>
The error is coming from tar during archive creation, "Unknown file
type; file ignored". I'm a little confused/concerned about what it is
seeing which it can't handle.
It might also be good to work out if that is tar from the host or tar
from tar-native. Is the host's tar unable to support something we're
relying upon?
If it were me, I'd probably have a look into the tar source code too,
see what might trigger an error like that.
Cheers,
Richard
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#193967):
https://lists.openembedded.org/g/openembedded-core/message/193967
Mute This Topic: https://lists.openembedded.org/mt/103661548/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
