E Shattow <[email protected]> writes: > The resulting release artifact tarball uploaded [1] has this problem. > > $ tar Jtvf bl-spacemit-k3-20260902.tar.xz > drwxr-xr-x runner/runner 0 2026-09-02 22:56 bl-spacemit-k3-20260902/ > -rw-r----- runner/runner 16384 2026-09-02 22:56 > bl-spacemit-k3-20260902/u-boot-env-default.bin > -rw-r--r-- runner/runner 270615 2026-09-02 22:56 > bl-spacemit-k3-20260902/fw_dynamic.itb > -rw-r--r-- runner/runner 80 2026-09-02 22:56 > bl-spacemit-k3-20260902/bootinfo_spinor.bin > -rw-r--r-- runner/runner 1587668 2026-09-02 22:56 > bl-spacemit-k3-20260902/u-boot.itb > -rw-r--r-- runner/runner 546087 2026-09-02 22:56 > bl-spacemit-k3-20260902/esos_rt24.itb > -rw-r--r-- runner/runner 966 2026-09-02 22:56 > bl-spacemit-k3-20260902/partition_4M.json > -rw-r--r-- runner/runner 464864 2026-09-02 22:56 > bl-spacemit-k3-20260902/FSBL.bin > -rwxr-xr-x runner/runner 525 2026-09-02 22:56 > bl-spacemit-k3-20260902/flash.sh > > Note the slight drift where the size column does not have enough leading > padding on the first few lines of output. Extracting and re-creating > this file then follows with normal output.
FYI, I think your mail client wrapped these. It confused me for a minute or two. Maybe you can attach it as a file? Collin
