Automated builds producing broken images #13

New issue

Open

opened 2026-06-23 10:16:59 +00:00 by irl · 1 comment

irl commented

2026-06-23 10:16:59 +00:00

Owner

when I unpack both tarballs, I get two files that look very similar:

-rw-r--r--@ 1 ...  staff  3250585600 Jun 18 10:05 raspi4_butter_main_v0.0.1_180626.img
-rw-r--r--@ 1 ...  staff  3250585600 Jun 21 08:00 raspi4_butter_main_v0.0.1_210626.img

when I unpack both tarballs, I get two files that look very similar: ``` -rw-r--r--@ 1 ... staff 3250585600 Jun 18 10:05 raspi4_butter_main_v0.0.1_180626.img -rw-r--r--@ 1 ... staff 3250585600 Jun 21 08:00 raspi4_butter_main_v0.0.1_210626.img ```

acute was assigned by irl

2026-06-23 10:16:59 +00:00

acute commented

2026-06-23 12:05:06 +00:00

Owner

Yhe _main_v0.0.1 symlinks were ones that I created manually (and point to 180626 build), the symlinks added by my script have nicer names and correctly point to the latest build (in this case the 210626 build).

I've removed my manual symlinks and I expect the remaining latest_ symlinks to update every Monday when a new build is created.

If you meant 'broken images' to mean something different let me know.

Yhe *_main_v0.0.1* symlinks were ones that I created manually (and point to 180626 build), the symlinks added by my script have nicer names and correctly point to the latest build (in this case the 210626 build). I've removed my manual symlinks and I expect the remaining latest_ symlinks to update every Monday when a new build is created. If you meant 'broken images' to mean something different let me know.