charm build - exclude i386 and armhf architectures
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Triaged
|
Low
|
Unassigned |
Bug Description
Hi,
I've just set up a new charm recipe for the autocert charm. When requesting a build, the i386 and armhf builds fail. It isn't just a specific series, but for all:
kinetic - https:/
xenial - https:/
bionic - https:/
jammy - https:/
focal - https:/
Looking at the build logs, for i386, it's failing on the "charmcraft" snap not supporting this architecture:
"""
error: snap "charmcraft" is not available on stable for this architecture
(i386) but exists on other architectures (amd64, arm64, armhf, ppc64el,
s390x).
"""
For armhf:
xenial - https:/
focal - https:/
jammy - https:/
kinetic - https:/
That's failing because of the "charm" snap:
"""
Parts processing error: Error installing snap 'charm' from channel 'latest/stable'.
"""
Can we exclude these two architectures by default to avoid the noisy fail to build emails?
summary: |
- charm build - exclude i386 and armhf + charm build - exclude i386 and armhf architectures |
description: | updated |
tags: | added: buildd-manager |
description: | updated |
tags: |
added: lp-charms removed: buildd-manager |
Changed in launchpad: | |
status: | New → Triaged |
importance: | Undecided → Low |
The "charm" snap has no 3.x release (nor latest/stable) for armhf & i386, so likely they dropped support for this architecture:
https:/ /private- fileshare. canonical. com/~hloeung/ tmp/a5LiVwlxsK. png
See https:/ /snapcraft. io/charm