history and status error message for a snap not pushed is not good
Metadata
Current evaluation
Confirmed fixed: `snapcraft history` was rewritten/renamed to `list-revisions` in canonical/snapcraft#1160, returning an empty revision table for unpushed snaps; the broken `status` case was filed separately as bug #1695241 (fixed in snapcore/snapcraft#3134).
Resolution: closed resolved
Reason: elopio closed the bug on 2017-06-02 after confirming `snapcraft list-revisions` now prints an empty revision table for an unpushed snap, a result of the history command rewrite/rename merged in canonical/snapcraft#1160. The residual `status` regression was split out into Launchpad bug #1695241, later fixed by snapcore/snapcraft#3134.
Evaluated by: mr-cal-bot
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Confirmed fixed: `snapcraft history` was rewritten/renamed to `list-revisions` in canonical/snapcraft#1160, returning an empty revision table for unpushed snaps; the broken `status` case was filed separately as bug #1695241 (fixed in snapcore/snapcraft#3134). | |
| stealth/space-bunny-alpha | — | closed resolved | History was fixed via the list-revisions rename in canonical/snapcraft#1160; unpushed snaps now return an empty revision table. The separate status failure moved to Launchpad bug #1695241. | |
| stealth/space-bunny-alpha | — | closed stale | The request to improve history and status errors for registered, unpushed snaps was abandoned without an implementation. | |
| qwen/qwen3.6-35b-a3b | — | — | Abandoned and closed without implementation. The requested user-friendly error message for unpushed snaps remains unresolved. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed and abandoned due to inactivity. The requested UX improvements for unpushed snap error messages were not implemented. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. The suggested improvements to error messaging for unpushed snaps were never implemented. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without resolution. The report flagged unhelpful error messages for unpushed snaps, recommending clearer naming and actionable guidance. Likely abandoned due to prolonged inactivity. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Related To:
snapcraft (launchpad)#1695241
(confidence 95%)
Follow-up bug filed by elopio from the closing comment for the still-broken `snapcraft status` output; fixed via snapcore/snapcraft#3134.
-
Likely Fixed By:
snapcore/snapcraft#1160
(confidence 88%)
Merged rewrite/rename of `snapcraft history` to `list-revisions`, which removed the 'Snap not found' error for unpushed snaps.
-
Related To:
snapcore/snapcraft#3134
(confidence 70%)
Merged fix adding a clear message for `snapcraft status` on unreleased snaps (resolves #1695241).
-
Related To:
snapcraft (launchpad)#1629339
(confidence 55%)
Original ticket that introduced the `history` and `status` commands whose error text this bug complained about.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1629339 Add `snapcraft history` and `snapcraft status` | snapcraft (launchpad) | closed | Ticket tracked PR #843; reviewers split it into snapcore/snapcraft#844 (history, 3f3db6dbe) and #845 (status, 0286940d4), both merged, with follow-ups in #863. `history` was later renamed `list-revisions` in #1160. | |
| #843 Add `snapcraft history` and `snapcraft status`. | snapcraft | closed | Combined history/status PR #843 was split into merged PR #844 (3f3db6dbe) for history and PR #845 (0286940d4) for status. |