I am interested in understanding the history behind the (archived) Cassandra snap (snapcrafters/cassandra).
Why was it archived? Any pointers to threads/bugs that I could go through to understand what happened to it (and if it would be possibly to pick it up from where it stopped) would be much appreciated!
Was it related to https://bugs.launchpad.net/launchpad-buildd/+bug/1702130 ?
If so, and in case the issue was about using maven-ant-tasks to resolve the dependencies, would this be a good time to being this snap back, given maven-ant-tasks was replaced upstream at https://github.com/apache/cassandra/commit/cf39d031279620eb5684ad384dff72f7325104cd ?
If memory serves, we archived it because it didn’t work. I vaguely recall Evan worked on it initially, but it was very much in the early days of snapcraft, and didn’t get a lot of love. If someone wanted to maintain it then we could un-archive it and re-publish a new version.
I maintained a cassandra part in the edgexfoundry snap for a while, but we had lots of problems with folks trying to build the snap behind corporate proxies at the time, so we switched to just downloading the pre-built tarballs and using those in the snap instead, and then eventually we actually switched to postgresql when system-usernames was supported inside snaps.
I based my work on the cassandra snap that @popey mentioned, so I think it could be revived if someone wanted to do the work to port the snapcraft.yaml to not use meson-ant-tasks (I don’t even recall how to it was built tbh). You can see the bit where we just downloaded the tarball here: https://github.com/edgexfoundry/edgex-go/blob/edinburgh/snap/snapcraft.yaml#L725-L762 and the bit where we last built cassandra from source here: https://github.com/edgexfoundry/edgex-go/pull/1319/commits/f4e033b6dff31e72f5d71aa6167fc9ebcbe5eac7
Thanks for the pointers.
I was able to successfully trigger a new build for cassandra 4.0-rc1 on cassandra-test : Snap packages : Athos Ribeiro based on the former (archived) snap.
I will perform some final adjustments to that snap so we can proceed to re-publish those. Since my final goal with this snap is to embed it into a new Cassandra OCI image (Cassandra snap and OCI image status - Server - Ubuntu Community Hub) , we would like to maintain the repository under the server team launchpad namespace if this is not a problem
I have an initial snap ready at https://launchpad.net/~athos-ribeiro/+snap/cassandra-test.
Ideally, I would like to maintain it in a launchpad repository under the server team namespace, as mentioned before.
Are there any special steps required for un-archiving and re-publishing a snap? What would the next steps look like here?
Hi @popey, what would the next steps on un-archinving the snap be?
Sorry @athos I no longer work at Canonical on snaps. I’d recommend pinging @Igor
Cassandra upstream finally released 4.0.0 a few weeks ago.
To complete our work on publishing a Cassandra OCI, we published the Cassandra snap 4.0.0, which is now publicly available.
We now ship Cassandra OCIs in
https://hub.docker.com/r/ubuntu/cassandra and https://gallery.ecr.aws/ubuntu/cassandra
Let me know if you have any questions or concerns regarding the new snap or OCI images.