It looks like the GitHub action that is supposed to publish this ends up publishing to binary/arm/Packages instead of binary/armhf/Packages
The binaries are built for amd64, i386, arm and arm64. The Debian architectures for these are: amd64, i386, armhf, and arm64, respectively. Only the armhf architecture is affected.
This means that when following the instructions to install teleport-ent and teleport-ent-updater on an armhf Debian variant, the teleport-ent package installs just fine, but the updater package is not found.
Bug details:
Teleport version all through 14.1.1
Recreation steps - If you don't have an armhf device handy, the easiest way to reproduce is on docker desktop with its built-in binfmt compatibility. Run docker run --rm -it --platform linux/armhf debian bash and then step through the install instructions.
Expected behavior:
Current behavior:
It looks like the GitHub action that is supposed to publish this ends up publishing to
binary/arm/Packages
instead ofbinary/armhf/Packages
The binaries are built for
amd64
,i386
,arm
andarm64
. The Debian architectures for these are:amd64
,i386
,armhf
, andarm64
, respectively. Only thearmhf
architecture is affected.This means that when following the instructions to install
teleport-ent
andteleport-ent-updater
on an armhf Debian variant, theteleport-ent
package installs just fine, but the updater package is not found.Bug details:
docker run --rm -it --platform linux/armhf debian bash
and then step through the install instructions.