I’m using the review-tools snap to verify snaps locally (built via the remote-build feature) before pushing them to the store. I expected them to pass fine, but I see warnings related to classic confinement, even though my snap already has approval for that (it’s the cmake snap). An example of the relevant output for one of the architectures looks like this:
Uploading cmake_3.17.3_arm64.snap to channel 3.17/edge
Preparing to push 'cmake_3.17.3_arm64.snap'.
After pushing, the resulting snap revision will be released to '3.17/edge' when it passes the Snap Store review.
Running the review tools before pushing this snap to the Snap Store.
Review Tools did not fully pass for this snap.
Specific measures might need to be taken on the Snap Store before this snap can be fully accepted.
- (NEEDS REVIEW) confinement 'classic' not allowed. If your snap needs classic confinement to function, please make a request for this snap to use classic by creating a new topic in the forum using the 'store-requests' category and detail the technical reasons why classic is required. (Refer to https://forum.snapcraft.io/t/process-for-reviewing-classic-confinement-snaps/1460)
Pushing 'cmake_3.17.3_arm64.snap' [===================================================================================================================================================================] 100%
How can I tell the review tools that the snap already has the approval it is says needs to be requested? Note that this isn’t stopping the upload and release from proceeding, but it does make the release process look like there is a problem when there isn’t.