← Back to issue list

Poor message when failing to specify a valid version

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1665003
Type
issue
State
open
Author
~facundo
Labels
store ui
Created
Updated
Closed
—

Current evaluation

Legacy snapcraft CLI showed a confusing error ('register ... before trying to release or choose an existing revision') when releasing a snap without a registered version. Reported ~9.5 years ago; no maintainer response; the current craft-based codebase no longer contains that message.

Suggested action: close stale

Reason: The issue is 3484 days old with zero comments and no maintainer interaction, and it targets the legacy pre-rewrite CLI. A grep of the current craft-based codebase finds no occurrence of the quoted message ('before trying to release' / 'choose an existing revision'), so the specific wording no longer exists in the project. The related Launchpad bug 1664704 confirms the same misleading 'register' error was a known legacy-CLI problem from the same era.

Impact: 20 Quick Win: 17.0 Staleness: 95 Complexity: 15 Confidence: 70 Support Request: 10

Issue body

I registered a snap in the store, then I push it (releasing to edge), ended OK, then I want to release in stable and it tells me I need to *register* it again... The message was: "Sorry, try `snapcraft register foobar40` before trying to release or choose an existing revision." Which I read as: register before I do any of two actions: release, or choose a revision :) It should indicate you need to 'register before releasing' or 'choose an existing revision'. Thanks!

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.8-27b
Impact: 20
Quick Win: 17.0
Staleness: 95
Complexity: 15
Confidence: 70
Support Request: 10
close stale Legacy snapcraft CLI showed a confusing error ('register ... before trying to release or choose an existing revision') when releasing a snap without a registered version. Reported ~9.5 years ago; no maintainer response; the current craft-based codebase no longer contains that message.
qwen/qwen3.6-35b-a3b
Staleness: 95
Complexity: 15
Confidence: 90
Support Request: 10
close stale Reported confusing CLI error message for snap release registration. Issue has been inactive for over 9 years with no maintainer response or updates.
qwen/qwen3.6-35b-a3b
Staleness: 98
Complexity: 15
Confidence: 90
Support Request: 10
close stale Confusing CLI error message when releasing a snap to stable. No maintainer activity or comments for over nine years. Likely irrelevant to current snapcraft versions and release workflows.
qwen3.6-35b-a3b-mtp-q6
Staleness: 98
Complexity: 10
Confidence: 85
Support Request: 5
close stale External contributor reports a confusing CLI error message when releasing a snap to stable. The issue requests clearer wording to distinguish between registering a new snap versus choosing an existing revision. It has been inactive for over 9 years.
qwen3.6-35b-a3b-mtp-q6
Staleness: 100
Complexity: 10
Confidence: 95
Support Request: 10
close stale Confusing CLI error when releasing a snap to stable without prior registration. The wording ambiguously implies registering before choosing an existing revision. Issue remains open, unassigned, and inactive with no comments.

Update history

No update history recorded yet.

Related work

  • Related To: snapcraft (launchpad)#1664704 (confidence 75%)

    Launchpad bug 1664704 reports the same misleading 'snapcraft register' error from snapcraft release in the legacy CLI era; both predate the craft-based rewrite.

Related issues

Issue Project State Summary Similarity
#1664704 snapcraft release gives misleading error when revision does not exist snapcraft (launchpad) open snapcraft release shows misleading error suggesting 'snapcraft register' when the real problem is a non-existent revision. Filed 2016, 0 comments, no maintainer interaction; legacy CLI since replaced by craft-based rewrite.
81%
#1604810 try to snapcraft release an unexisting revision shows the wrong error snapcraft (launchpad) open Misleading error when running snapcraft release with a non-existent revision: it suggests 'snapcraft register' instead of saying the revision is invalid. Filed by maintainer elopio in 2016, labelled bitesize, 0 comments, no activity for ~9.5 years; the legacy CLI has since been replaced by the craft-based rewrite.
79%
#1999038 "snapcraft release" chokes given an invalid revision value snapcraft (launchpad) open Issue about confusing error when 'snapcraft release' receives invalid revision. Stale for 1366 days with no maintainer response. The release command appears to have been removed or deprecated.
77%
#2059787 inaccurate error output in snapcraft release if given invalid revision snapcraft (launchpad) open Bug report: snapcraft release shows misleading 'No such command release' error when given an invalid revision. Untriaged, 888 days old with no maintainer interaction.
72%