remote build: platform definitions cannot be parsed by Launchpad
Metadata
Current evaluation
Fixed via an upstream Launchpad bug resolution. PR #4994 merged additional --platform argument handling to resolve remaining parsing scenarios.
Suggested action: —
No scores available.
Issue body
### 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 all `build-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` and `build-for`, so it is not clear Snapcraft can request builds.
### To Reproduce
snapcraft remote-build --platform amd64
### Environment
n/a
### snapcraft.yaml
```shell
name: remote-build-platforms-error
version: "1.0"
summary: test
description: test
confinement: strict
base: core24
platforms:
amd64:
build-on: amd64
arm64:
build-on: amd64
parts:
my-part:
plugin: nil
```
### Relevant log output
```shell
Multiple builds match the current platform.
Recommended resolution: Check the "--platform" and "--build-for" parameters.
```
### Additional context
_No response_
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Fixed via an upstream Launchpad bug resolution. PR #4994 merged additional --platform argument handling to resolve remaining parsing scenarios. | |
| qwen/qwen3.6-35b-a3b | — | — | Resolved by upstream Launchpad bug 2072622. PR 4994 merged to handle --platform argument scenarios, fixing platform definition parsing and remote build conflicts. | |
| qwen/qwen3.6-35b-a3b | — | — | Fixed by upstream Launchpad bug #2072622 and snapcraft PR #4994, resolving platform parsing failures and --platform argument conflicts during remote builds. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Resolved via upstream Launchpad bug fix and snapcraft pull request 4994, which corrects platform definition parsing and handles --platform argument scenarios for remote builds. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Resolved by upstream Launchpad bug #2072622 and merged PR #4994, which fixes platform parsing and handles the --platform argument for remote builds. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #5351 fix(remote): error early for invalid platform usage | snapcraft | merged | Merged a fix that raises an early error when --build-for conflicts with shorthand platform entries, preventing unfriendly Launchpad failures. The change passed CI checks and received approvals, resolving issue #5270. |