snap: update for core24

[soumyaDghosh]

No description provided.

[GeopJr]

Thanks for this PR!

FWIW, this action and snap are only for ci artifacts and development builds. The release snap config lives at https://github.com/GeopJr/tuba-snap/ (you don't have to open a PR there, I'll pick the changes from here!)

[soumyaDghosh]

Thanks for this PR!

FWIW, this action and snap are only for ci artifacts and development builds. The release snap config lives at https://github.com/GeopJr/tuba-snap/ (you don't have to open a PR there, I'll pick the changes from here!)

You cannot directly build this in the snapcraft.io website builder. Because gnome extension still experimental.

[GeopJr]

:/ disappointing

[soumyaDghosh]

:/ disappointing

Actually the extensions are getting a major overhaul on the graphics side, with new graphics drivers. So, it's taking this long.

canonical/snapcraft#4744

[soumyaDghosh]

You can get the login cradentials via this command,

snapcraft export-login --snaps=tuba \
  --acls package_access,package_release \
  SNAP_STORE_STABLE

Then set that in an environment variable named STORE_LOGIN

[GeopJr]

I'll do so when I get on my snap environment! Thanks!

I have one more question though, if it compiles with -Ddevel=true, how do I make 'stable' builds from here? If I promote the edge one, it will be treated as devel and the action is not aware of repo releases. That's one of the reasons I split it into devel snap config and release snap config in a different repo.

[soumyaDghosh]

I'll do so when I get on my snap environment! Thanks!

I have one more question though, if it compiles with -Ddevel=true, how do I make 'stable' builds from here? If I promote the edge one, it will be treated as devel and the action is not aware of repo releases. That's one of the reasons I split it into devel snap config and release snap config in a different repo.

Okay, so even more conditioning! Ummmm... For now I removed the devel using sed, but I think better you could do is replicate this in the snap manifests repo. And remove things from here which you don't need anymore.

[GeopJr]

Here's an idea: How about I unlink the tuba-snap repo from the snapcraft runners and we instead add an action there with (workflow_dispatch so I can trigger it manually) to build and publish snaps?

That way, the action on this repo can stay as devel and the action on tuba-snap will always be release only

[GeopJr]

Merging, thanks!

I don't know if/when I'll set up action publishing on the tuba-snap repo.

[soumyaDghosh]

Hi gnome+core24 now on stable

[GeopJr]

Thanks for letting me know!

Can I drop SNAPCRAFT_ENABLE_EXPERIMENTAL_EXTENSIONS?

[soumyaDghosh]

No Sorry, my bad, not yet. It's not yet stable. I hope in the next release of snapcraft, it'll be. And yes, you can drop it once stable