ValueError: No revision information for 1
Metadata
Current evaluation
Open report of a Store channel-map race that makes snapcraft upload --release fail after the revision was created; maintainers confirmed it and users reproduced it through Snapcraft 5.0.
Suggested action: keep open
Reason: Maintainer @sergiusens identified a Store channel-map race and stated that Snapcraft needed a warning workaround. Later reports affected non-initial revisions, Brand Stores, and Snapcraft 5.0, including a reliable grade:devel reproducer, so this remains a recurring false failure that can break CI despite successful publishing.
Evaluated by: mr-cal-bot
Impact:
52
Quick Win:
18
Complexity:
55
Confidence:
82
Actionability:
79
Issue body
Registered a name, got that approved by store team (3 letters long) and then tried to push all architectures in a loop. First one "failed" (but actually succeeded).
$ for f in dog_v0.1.0_*.snap; do snapcraft push $f --release=candidate; done
DEPRECATED: The 'push' set of commands have been replaced with 'upload'.
See http://snapcraft.io/docs/deprecation-notices/dn11 for more information.
Preparing to upload 'dog_v0.1.0_amd64.snap'.
After uploading, the resulting snap revision will be released to 'candidate' when it passes the Snap Store review.
Install the review-tools from the Snap Store for enhanced checks before uploading this snap.
Pushing 'dog_v0.1.0_amd64.snap' [=================================================================================================================================================================================================] 100%
Processing...|
Ready to release!
Revision 1 of 'dog' created.
Sorry, an error occurred in Snapcraft:
No revision information for 1
We would appreciate it if you anonymously reported this issue.
No other data than the traceback and the version of snapcraft in use will be sent.
Would you like to send this error data? (Yes/No/Always/View) [no]: v
Traceback (most recent call last):
File "/snap/snapcraft/5737/bin/snapcraft", line 33, in <module>
sys.exit(load_entry_point('snapcraft==4.4.1', 'console_scripts', 'snapcraft')())
File "/snap/snapcraft/5737/lib/python3.6/site-packages/click/core.py", line 829, in __call__
return self.main(*args, **kwargs)
File "/snap/snapcraft/5737/lib/python3.6/site-packages/click/core.py", line 782, in main
rv = self.invoke(ctx)
File "/snap/snapcraft/5737/lib/python3.6/site-packages/click/core.py", line 1259, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File "/snap/snapcraft/5737/lib/python3.6/site-packages/click/core.py", line 1066, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "/snap/snapcraft/5737/lib/python3.6/site-packages/click/core.py", line 610, in invoke
return callback(*args, **kwargs)
File "/snap/snapcraft/5737/lib/python3.6/site-packages/snapcraft/cli/store.py", line 198, in upload
snap_revision
File "/snap/snapcraft/5737/lib/python3.6/site-packages/snapcraft/storeapi/v2/channel_map.py", line 332, in get_revision
raise ValueError(f"No revision information for {revision_number!r}")
ValueError: No revision information for 1
We would appreciate it if you anonymously reported this issue.
No other data than the traceback and the version of snapcraft in use will be sent.
Would you like to send this error data? (Yes/No/Always/View) [no]: y
Thank you, sent.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
52
Quick Win:
18
Complexity:
55
Confidence:
82
Actionability:
79
|
keep open | Open report of a Store channel-map race that makes snapcraft upload --release fail after the revision was created; maintainers confirmed it and users reproduced it through Snapcraft 5.0. | |
| stealth/space-bunny-alpha |
Impact:
58
Quick Win:
25
Complexity:
49
Confidence:
87
Actionability:
84
|
keep open | Snapcraft can create and release a revision, then exit with 'No revision information'; maintainers identified an eventual-consistency race, but graceful handling remains unimplemented. | |
| stealth/space-bunny-alpha |
Impact:
44
Quick Win:
17
Complexity:
48
Confidence:
84
Actionability:
76
|
needs triage | Snapcraft 4.4.1 creates and schedules revision 1 for release, then reports ValueError in get_revision. The current upload path does not use that lookup, but no resolution is documented. | |
| qwen/qwen3.8-27b |
Impact:
25
Quick Win:
14
Staleness:
92
Complexity:
45
Confidence:
70
Support Request:
10
|
close stale | snapcraft 4.4.1 'push' (deprecated) crashed with 'ValueError: No revision information for 1' after a successful upload/release, likely a store channel-map race. Open ~5.8 years, zero comments, no labels or maintainer response. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
10
Confidence:
95
Support Request:
5
|
close stale | Bug report for Snapcraft showing a ValueError during upload. Issue has been inactive for over 4 years with no maintainer response or labels. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
25
Confidence:
90
Support Request:
5
|
close stale | Snapcraft 4.4.1 crashes with ValueError after successfully pushing a snap revision due to missing local state lookup. Issue is over 5 years old with no maintainer response. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
20
Confidence:
90
Support Request:
10
|
close stale | Reports a ValueError when looping snapcraft push commands. The issue is over 5 years old, uses a deprecated command and outdated snapcraft version, and has zero maintainer interaction or comments. |
Update history
| Date | Change |
|---|---|
| created |
Related issues
No related issues found above the similarity threshold.