Hello (reply-all I am off-list thanks!)
When listing tarball contents output from tarball created in
ubuntu-latest environment of GitHub CI/CD workflow (Ubuntu 24.04.4 tar
(GNU tar) 1.35) I observe size columns that are drifting one-or-few
characters. Is this intended or explainable behavior? I cannot seem to
reproduce it locally on my Debian 13 Trixie host. The suspect archive is
produced in a GitHub CI/CD workflow on "ubuntu-latest":
> - name: Archive Firmware
> if: github.ref_type == 'tag'
> run: |
> tar -cJf bl-spacemit-k3-${{ github.ref_name }}.tar.xz \
> --transform 's~^\.~bl-spacemit-k3-${{ github.ref_name }}~' \
> -C dist .
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.
Initially I thought this was a problem with tar transform operation, as
that is how I was going to take the collected files in 'dist/' dir and
give them one top directory that is named referencing a GitHub Actions
environment variable. Later changing this to a combination "mv"
operation and simple tarball creation had the same funky contents
listing outcome though.
> - name: Archive Firmware
> if: github.ref_type == 'tag'
> run: |
> tar --version
> mv dist bl-spacemit-k3-${{ github.ref_name }}
> tar -cJf bl-spacemit-k3-${{ github.ref_name }}.tar.xz \
> bl-spacemit-k3-${{ github.ref_name }}
$ tar Jtvf bl-spacemit-k3-20260902.tar.xz
drwxr-xr-x runner/runner 0 2026-09-02 15:31 bl-spacemit-k3-20260902/
-rw-r--r-- runner/runner 545947 2026-09-02 15:31
bl-spacemit-k3-20260902/esos_rt24.itb
-rw-r--r-- runner/runner 966 2026-09-02 15:31
bl-spacemit-k3-20260902/partition_4M.json
-rw-r--r-- runner/runner 80 2026-09-02 15:31
bl-spacemit-k3-20260902/bootinfo_spinor.bin
-rw-r--r-- runner/runner 1587668 2026-09-02 15:31
bl-spacemit-k3-20260902/u-boot.itb
-rw-r--r-- runner/runner 464864 2026-09-02 15:31
bl-spacemit-k3-20260902/FSBL.bin
-rw-r----- runner/runner 16384 2026-09-02 15:31
bl-spacemit-k3-20260902/u-boot-env-default.bin
-rw-r--r-- runner/runner 270615 2026-09-02 15:31
bl-spacemit-k3-20260902/fw_dynamic.itb
-rwxr-xr-x runner/runner 525 2026-09-02 15:31
bl-spacemit-k3-20260902/flash.sh
Link 1:
https://web.archive.org/web/20260902225137/https://freeshell.de/e/riscv64/bl-spacemit-k3-20260902.tar.xz
Best regards,
E Shattow
