Is Cannonical deprecating non-Launchpad Snaps?

store
1

Hi. I am one of the packagers of GIMP team, being responsible for the official Snap package and others.

We do create our Snap from our GitLab CI using a snapcraft-rocks Docker image, then the resulting .snap is sent directly to Snapcraft servers.

However, seems that such Docker image stoped being maintained. It is not updated anymore and we got months of radio silence on Provide snapcraft-rocks based on core26 · Issue #112 · canonical/snapcraft-rocks · GitHub, which is not good: bugs naturally accumulate on the packages provided by core24 and we would like to use core26.

Now, I noticed that our page on https://snapcraft.io/gimp have a “No build information for this revision” message, which I believe is because there are no Launchpad at all, since we build on our CI as said above. I already reported that potentially discriminatory UX on the website on https://github.com/canonical/snapcraft.io/issues/5876 but I am not hopeful of that being addressed considering the current ambiguous state of Cannonical support for non-Launchpad builds.

So, I ask formally to the employees: is our use case being deprecated?

1 Like
2

Hello! It looks like the banner issue has been fixed, which is great. I’m in communications with the maintainers of the snapcraft-rocks image so hopefully I can have an answer on that soon.

Regarding your question about the non-Launchpad builds, both Launchpad and non-Launchpad builds are supported without the current intention of removing either type of build. Your use case is not deprecated.

2 Likes
3

Hey, sorry the silence on the snapcraft-rocks side made it feel like the project was abandoned. We let these images go stale, but a core26 rock is on our roadmap and we’re committing to keeping them updated going forward.

I’ll keep this thread updated once we have a solid timeline.

3 Likes