Closed mr-cal closed 1 month ago
Thank you for reporting us your feedback!
The internal ticket has been created: https://warthogs.atlassian.net/browse/CRAFT-3069.
This message was autogenerated
upstream bug: https://bugs.launchpad.net/launchpad/+bug/2072622
This is mostly fixed by the upstream bug but https://github.com/canonical/snapcraft/pull/4994 solves scenarios with the --platform
argument.
Bug Description
Problem 1
Launchpad fails to parse many
platforms
definitions.We need to complete https://github.com/canonical/craft-platforms/issues/5 and sync with the Launchpad team to consume that build planner.
Problem 2
The legacy remote builder would only allow snaps that could build a single artefact on a
build-on
architecture. That is an architecture could only appear once in allbuild-on
entries.The new remote builder doesn't restrict this. This is a problem because Launchpad's API appears not to distinguish between
build-on
andbuild-for
, so it is not clear Snapcraft can request builds.To Reproduce
snapcraft remote-build --platform amd64
Environment
n/a
snapcraft.yaml
Relevant log output
Additional context
No response