While experimenting with the build.snapcraft service I inadvertently built mir-test-tools for s390x which got pushed to latest/edge automatically. That build is unwanted, has incorrect content, and I have no capability for, nor interest in, supporting s390x for this snap.
I’m still seeing this problem too on https://snapcraft.io/certbot. I (temporarily) closed the edge channel, but the i386 architecture is still listed on the snap store page and testing on a i386 machine, the snap can still be installed.
I don’t think this is what you want. That will build on amd64 and set the runs-on to amd64 AND armhf for the same .snap file. It will, in parallel, build on armhf and set the runs-on for THAT snap file to the same amd64 and armhf. So from the two builds this will generate both snap files will be installable onto an incorrect architecture.
oops. I coulda sworn they were statements rather than commands (“it builds” vs. “to build”, respectively). The basis of the way the architectures operate, however, is good - I’ll edit the post to fix builds-on to be the correct build-on.
In the past, I left the channel closed for less than 2 hours and it didn’t seem to help at all. Yesterday, I tried leaving the channel closed for roughly 10 hours which definitely helped but things are still behaving oddly. On a i386 system where we do not want to offer a Certbot snap, I see this:
# sudo snap install --classic certbot
error: snap "certbot" is not available on stable but is available to install on the following
edge snap install --edge certbot
Please be mindful pre-release channels may include features not completely tested or
implemented. Get more information with 'snap info certbot'.
# snap install --edge --classic certbot
error: snap "certbot" is not available on latest/edge but other tracks exist.
Please be mindful that different tracks may include different features. Get more information
with 'snap info certbot'.
# snap info certbot
error: no snap found for "certbot"