Releasing a new snap is blocked by a previous uploading pending manual review
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Snapcraft |
Fix Released
|
Undecided
|
Unassigned | ||
Software Center Agent |
New
|
Undecided
|
Unassigned |
Bug Description
Steps to reproduce:
1) Build a snap that will fail an automated review check. For example build a snap that contains only a shell script, and you'll hit "Could not find compiled binaries for architecture 'amd64' lint-snap-
2) Upload this snap with 'snapcraft push <snap> --release stable'. You'll get an error from snapcraft (I've filed a separate bug about that output not being particularly helpful).
3) Now fix the problem that the automated review tools were complaining about. In this example, include a binary in the snap (add 'stage-packages: wget' or similar).
4) Attempt to upload and release the new snap with: 'snapcraft push <snap> --release stable'
Expected behaviour:
I expect snapcraft to either release the new snap, or give me an error message if it fails review.
Observed behaviour:
What actually happens is that snapcraft gets stuck at the 'Processing' stage. This will continue until the previous release has either been manually accepted or rejected by a store reviewer. However, there's no indication in the snapcraft UI that this is the case.
IMO there's a few issues at play here:
1) The store shouldn't block a later revision from publication on an earlier revision needing manual review. Doing so makes the store less 'self-service' than we'd like, I think.
2) Snapcraft should point the user to the store page, or provide more information about what the current state is, and what it's waiting for.
Both of your expected outcomes involve changes in the store code, so affecting it as well