`snapcraft try` error is outdated
Metadata
Current evaluation
Closed after assignment. Maintainer provided implementation guidance using get_effective_base() for dynamic base detection, with parametrized tests planned for core24 and core26.
Suggested action: —
No scores available.
Issue body
### Check existing issues
- [x] I've verified that this request isn't described by any existing issues.
### Request
Fix the error message for `snapcraft try`, which always displays "core24", even if you are trying it with core26: `Command or feature not implemented: "snapcraft try" is not implemented for core24`
This can be reproduced with the following snapcraft.yaml:
```yaml
name: hello-core26
base: core26
build-base: devel
version: "0.1"
summary: hello
description: hello
grade: devel
confinement: strict
parts:
my-part:
plugin: nil
```
This should include a unit test that uses pytest.mark.paramterize for core24 and core26.
### The problem it solves
A better error message for core26 snaps.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Closed after assignment. Maintainer provided implementation guidance using get_effective_base() for dynamic base detection, with parametrized tests planned for core24 and core26. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed after being assigned to a contributor to fix the outdated error message and add parametrized unit tests. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed after assignment to vedantdaterao. Contributor clarified base resolution logic using get_effective_base() and fixed the outdated error message. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed and assigned to a contributor to fix the hardcoded core24 in the snapcraft try error message by dynamically detecting the actual base. A parametrized unit test was requested. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed after being assigned to a contributor. An internal Jira ticket was created to track the fix for the hardcoded core24 error message in snapcraft try. Implementation pending. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #6193 fix: snapcraft try error shows effective base | snapcraft | merged | Merged fix for #6186 that updates the snapcraft try error message to accurately display the effective base using get_effective_base(). Approved by reviewers and merged with added unit tests for core24 and core26. | |
| #1803776 snapcraft init missing a base | snapcraft (launchpad) | closed | Closed without resolution. The base requirement for snapcraft init was later implemented in subsequent releases, superseding this report. |