Request for classic confinement for Blueprint Compiler

store-requests
#1

Request for the classic confinement and publisher vetting for the snap blueprint-compiler and its upstream publisher respectively. Kindly do this asap. The transfer took almost a week. Please. :pray: :pray:

Request for classic confinement for snap Blueprint Compiler
#2

Adding the previous request for classic confinement for this snap for context here!

#3

@soumyaDghosh I have added a comment to the existing thread

1 Like
#4

Thanks for your comment. Hope things can be done sooner. For everyone eles’s information,

This snap blueprint-compiler is published from upstream, i.e jwestman, and will be served to the store from this repo

Thanks, Soumyadeep Ghosh, Collaborator

#5

@jwestman, @soumyaDghosh,

This thread (and others) has been a bit convoluted, so I’ll lay it out here: @soumyaDghosh is asking @advocacy to vet @jwestman so that the blueprint compiler snap can be granted classic confinement (which has otherwise been approved here).

For your benefit @Igor, jwestman is the upstream developer, noting we haven’t heard from James yet.

#6

I thought it will not be necessary. I have asked him to make his comment if he agrees with this or not. Also, to verify you can look into the github account, from which the snap will be published. Thanks.

#7

It is necessary. The upstream developer needs to be involved in this process. Once we can vet James, we can then move on to the vetting process for this snap.

1 Like
#8

Hello! I’m the upstream developer. What do I need to do for the vetting process?

1 Like
#9

pinging @Igor for the next process

#10

Hello James, can you dm me, I will need some info from you please.

#11

I don’t think I can, when I go to my Messages tab I don’t see a New Message button.

#12

@Igor any updates on this?

#13

@jwestman I’ve contacted you for some additional details, thank you!

#14

+1 from me, @jwestman has approved the publishing by the third-party dev @soumyaDghosh .

1 Like
#15

For context, this is the repo

http://github.com/jwestman/blueprint-compiler-snap

And I will be maintaining it

#16

@Igor any news on when can we have it? We need it here now

https://github.com/NickvisionApps/Tagger/actions/runs/6864637479/job/18666866574

If it will be done soon, we can use it as a snap

#17

The Store team will make the changes based on the vetting. They are usually quite busy with requests, so it can take them a little while to action all of the forum posts.

1 Like
#18

@Igor any updates? More upstreams are now shifting to the latest blueprint-compiler. Why are these requests stuck for so long. I mean, there is not even any estimation/update. And building blueprint compiler from source, for all of these snaps, it really takes a lot!

#19

Just tagging in @alexmurray and @emitorino to see if this one got lost somehow. The original request for classic was approved here a while ago, and Igor has done vetting now so it should be good to go afaict.

Thanks for your patience @soumyaDghosh. As Igor says, the review team have many requests to get to amongst other work.

1 Like
#20

Granting use of classic. This is now live.

Thank you for your patience. Plug/slot definitions will need to be removed from the snapcraft.yaml when using classic confinement.