-
Notifications
You must be signed in to change notification settings - Fork 865
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Restore snap publishing on snapcraft #1551
Comments
@bertrandfalguiere - do you mind adding the appropriate labels to this issue when you get a chance? You can see details of the labeling system here: https://github.com/ipfs/community/blob/master/ISSUE_LABELS.md |
I don't mind, but I think I don't have the right for it? I think this could be I can be assigned too, but I don't think I have the rights either. |
@bertrandfalguiere, I'm sorry about the permissions! Thanks for that list. I added the labels and assigned you. 😊 |
The lowest friction route here seems to be adopting a snapcraft.yml file into this repo, and letting the snapstore build infra build out the snap files for us, and then promote new releases to the stable channel via the snapstore ui. I love full automation, but the periodic build failure from stale credentials will get annoying. |
We are already publishing generic I believe we could go https://snapcraft.io/docs/pre-built-apps route and reuse prebuilt |
@olizilla slayed the snap dragon for go-ipfs in ipfs/kubo#7250 (comment) 🛡🗡🐉! Now it's a matter of time to be able to install ipfs-desktop from the default app store of Ubuntu, right? |
@bertrandfalguiere yes, but it's a low priority for the team (limited bandwidth). If anyone has time to create a PR to try approach from #1551 (comment) I'd be happy to test and review. |
This is a placeholder for me to tackle this.
Snap publishing was removed because of #1547 : it was at the wrong place and it unpolitely interrupted testing.
The text was updated successfully, but these errors were encountered: