ARM64 binary not longer to be found in Focal's archive.archive.ubuntu.com

[zar3bski]

A pipeline a mine used to work and now fails building ARM64. I post the issue here but I have the feeling that the root cause is a recent change in Ubuntu repositories (related to the release of the next LTS soon to come?).

[package.metadata.cross.build]
pre-build = [
    "apt-get update",
    "dpkg --add-architecture $CROSS_DEB_ARCH",
    "apt-get --assume-yes install libdbus-1-dev:$CROSS_DEB_ARCH pkg-config libc6-dev:$CROSS_DEB_ARCH"
]

cross build --release --target=x86_64-unknown-linux-gnu
cross build --release --target=aarch64-unknown-linux-gnu

It seems like these two packages cannot be found anymore

131.5 E: Unable to locate package libdbus-1-dev:arm64
131.5 E: Unable to locate package libc6-dev:arm64
------
Dockerfile.aarch64-unknown-linux-gnu-custom:5
--------------------
   3 |                     ARG CROSS_DEB_ARCH=
   4 |                     ARG CROSS_CMD
   5 | >>>                 RUN eval "${CROSS_CMD}"
--------------------
ERROR: failed to build: failed to solve: process "/bin/sh -c eval \"${CROSS_CMD}\"" did not complete successfully: exit code: 100
Error: 
   0: could not run container
   1: when building custom image
   2: when pre-building
   3: `docker buildx build --progress auto --label 'org.cross-rs.for-cross-target=aarch64-unknown-linux-gnu' --label 'org.cross-rs.runs-with=x86_64-unknown-linux-gnu' --label 'org.cross-rs.workspace_root=/home/runner/work/aadvice/aadvice' --tag localhost/cross-rs/cross-custom-aadvice:aarch64-unknown-linux-gnu-28d48-pre-build --build-arg 'CROSS_CMD=apt-get update
      dpkg --add-architecture $CROSS_DEB_ARCH
      apt-get --assume-yes install libdbus-1-dev:$CROSS_DEB_ARCH pkg-config libc6-dev:$CROSS_DEB_ARCH' --build-arg 'CROSS_DEB_ARCH=arm64' --file /home/runner/work/aadvice/aadvice/target/aarch64-unknown-linux-gnu/Dockerfile.aarch64-unknown-linux-gnu-custom --output 'type=docker' /home/runner/work/aadvice/aadvice` failed with exit status: 1

I'm no expert in Ubuntu repositories so feel free to correct me but, based on what cross reaches and what it fails to reach

#5 0.362 Hit:1 http://ports.ubuntu.com/ubuntu-ports focal InRelease
#5 0.367 Get:2 http://ports.ubuntu.com/ubuntu-ports focal-updates InRelease [128 kB]
#5 0.422 Get:3 http://ports.ubuntu.com/ubuntu-ports focal-backports InRelease [128 kB]
#5 0.450 Get:4 http://ports.ubuntu.com/ubuntu-ports focal-security InRelease [128 kB]
#5 4.189 Get:5 http://security.archive.ubuntu.com/ubuntu focal-security InRelease [128 kB]
#5 6.013 Get:6 http://security.archive.ubuntu.com/ubuntu focal-security/main amd64 Packages [4432 kB]
#5 29.81 Get:7 http://security.archive.ubuntu.com/ubuntu focal-security/main i386 Packages [1084 kB]
#5 63.52 Err:8 http://archive.archive.ubuntu.com/ubuntu focal InRelease
#5 63.52   Connection failed [IP: 91.189.91.82 80]
#5 125.3 Err:9 http://archive.archive.ubuntu.com/ubuntu focal-updates InRelease
#5 125.3   Connection failed [IP: 91.189.91.82 80]
#5 128.3 Get:10 http://archive.archive.ubuntu.com/ubuntu focal-backports InRelease [128 kB]

an because https://archive.archive.ubuntu.com/ubuntu/dists/focal-updates/InRelease mentions a main/binary-arm64 that does not exist on https://archive.archive.ubuntu.com/ubuntu/dists/focal-updates/main/, the only hypothesis that comes to my mind is that arm64 binaries have been removed from archive.archive.ubuntu.com. By contrast, https://ports.ubuntu.com/dists/focal/main/ contains the relevant folder.

Did anyone recently experience a similar behavior? Before I send a ticket to Canonical and look as a dummy, did I miss something obvious with how Ubuntu repositories are supposed to work? Last but not least, since the next LTS is about to come and that we might expect less and less availability of focal artifacts (which might explain the current issue), do you plan on migrating all the Dockerfiles to Resolute Raccoon at one point and will you need some help?

[Emilgardis]

we're planing to upgrade to 24.04