When uploading v0.1.0, I received the following failure: “human review required due to ‘allow-installation’ constraint (bool) declaration-snap-v2_plugs_installation (landscape-conf, system-files)”.
This request has been added to the queue for review by the @reviewers team.
Hello @spencerrunde!
This is a +1(#voteFor) from me for granting auto-connection read access to /etc/landscape with the system-files interface due to the snap’s clear ownership.
Hey folks!
@spencerrunde is it planned to transfer this snap under the Canonical account?
Hi @jslarraz , I hadn’t realized that is an option. We certainly could–it will be a required component of Landscape in the future.
How would we go about that process?
If it will be required by Landscape, I think publishing under the Canonical account will be the right thing. Also it will remove any possible friction with this request.
I know there are some minimum requirements, such as adding the proper metadata and having one revision published to the –stable channel, before the transfer can be done, but I’m not very familiar with the process. I would suggest opening a [transfer-ownership](transfer-ownership - snapcraft.io) request and ask the store folks about the concrete requirements.
The only other thing is that the interface name should be etc-launchpad rather than landscape-conf as per the usual naming convention.
Sounds good, thanks for the info! We are still beta testing this, so I’d prefer to wait until we can properly publish something into stable before transferring ownership.
I’ll rename the interface and then upload; is there anything else that prevents approval here?
I’ve updated the interface name in revision 3 of the snap; this is pending manual review now.
Thanks!
If landscape-outbox is going to be officially supported, I think it makes sense to grant the requested auto-connection (#voteFor)
+2 for, 0 against granting landscape-outbox read access to /etc/landscape via the auto-connection of a system-files interface. Publisher is vetted. This is now live.
1 Like
