v0.5.10 — A fresh index before installing what was just built

A regression introduced in v0.5.8, found by v0.5.9's release.

E: Failed to fetch …/libgstreamer-plugins-base1.0-0_1.24.2-1ubuntu0.4_amd64.deb  404  Not Found

Installing the window's .deb pulls GTK from the archive, and the index a runner image ships with is as old as the image. Against a mirror mid-publish, the index names a pool file that is no longer there.

Why it reached us, which is the part that is mine

apt-get update was the first line of "Install the interface's libraries" — a step that went to the binaries job when v0.5.8 split the compiling out of the packaging. The new packages job was left installing against whatever the image had.

Splitting a job takes the things it quietly depended on with it. This was one of them.

CI was unaffected: its check job still refreshes the index early, and the rpm, Arch and tarball checks each run in containers that refresh their own.

What v0.5.8 did while this happened

This was the first time the resilient attach was asked for anything, and it did its job:

• the arm64 half was installable throughout — .deb, .rpm, tarball, checksum and both window rpms were uploaded;
• the release page carried its own notice naming the six missing files;
• the check went red.

Re-running the one failed job completed the release and took the notice off the page again, which is the half of that mechanism nobody had seen work yet.

Before v0.5.8 the same failure threw away a complete arm64 build and published a page with nothing on it. That is what happened to v0.5.7, and is why the fix exists.