Skip to content
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

snapcraft.yaml: update to work with modern snapcraft #132

Merged
merged 4 commits into from
Feb 7, 2023

Conversation

mvo5
Copy link
Contributor

@mvo5 mvo5 commented Aug 19, 2021

spread is currently not build with snapcraft 5.0 (the default).
This commit fixes this by moving to base: core20.

Note that this also requires moving to go.mod hand hence it includes #129.

spread is currently not build with snapcraft 5.0 (the default).
This commit fixes this by moving to `base: core20`. Note that
this also requires moving to `go.mod`.
@mvo5 mvo5 added the Ready label Sep 9, 2021
@mvo5 mvo5 changed the title snapcraft.yaml: update to work with snapcraft 5.0 snapcraft.yaml: update to work with modern snapcraft Feb 4, 2022
@@ -12,6 +12,7 @@ description: |

confinement: strict
grade: stable
base: core20

apps:
spread:

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

adding an entry for personal-files to be able to easily use the google backend would be nice.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Excellent suggestion, I think this would ideally be a followup?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I addressed this in PR #161 now.

@mvo5 mvo5 mentioned this pull request Feb 6, 2023
Copy link

@sergiusens sergiusens left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would update the version to something relevant (not blocking on it) and consider another PR to move to core22. This works for now.

@mvo5 mvo5 mentioned this pull request Feb 6, 2023
@@ -1,5 +1,5 @@
name: spread
version: 2018.08.21
version: 2020.08.19
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can we use git as version here?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I will do a followup with this change and also the move to core22. This PR got (soft) approval by Gustavo as is so I don't want to add more potentially controversial things just now :)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I addressed the version in #161 - please let me know if that matches what you had in mind and I'm happy to tweak as needed.

@mvo5 mvo5 merged commit 655ee77 into canonical:master Feb 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants