`package_upload` is no more enough for uploading?

#1

With snapcraft 4.1.1, snapcraft push exits with non-zero code after a snap is uploaded. I’ve setup macaroon with the following permissions.

snaps:       ['yakshaveinc', 'amend']
channels:    ['stable']
permissions: ['package_upload']
expires:     None

Here is what happens.

$ snapcraft push snapcrafting/yakshaveinc/yakshaveinc_eternal_amd64.snap --release=stable
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 'yakshaveinc_eternal_amd64.snap'.
After uploading, the resulting snap revision will be released to 'stable' when it passes the Snap Store review.
Install the review-tools from the Snap Store for enhanced checks before uploading this snap.
released
Revision 75 of 'yakshaveinc' created.
Pushing 'yakshaveinc_eternal_amd64.snap' [===============================] 100%
Processing...|                                                                 
Could not retrieve information for 'yakshaveinc'.

Recommended resolution:
Ensure the snap name is correct and that you have permissions to access it.

Failed
failed to deploy

https://travis-ci.org/github/yakshaveinc/linux/jobs/714166058#L371

New macaroon caveat breaks snapcraft release process
Call for testing: Snapcraft 4.1.2
#2

This has been previously discovered. The fix is to request an extra permission: `package_upload` is no more enough for uploading?

#3

Self referencing link?

#4

Oops, sorry; copy pasta fail :stuck_out_tongue_winking_eye:

1 Like
#5

We can look into solving this for the next release.
This appears to be related to status, which is now a separate call, and not upload/release per se.

I will discuss options with @natalia on the Snap Store side.