Closes #534. There was an issue in how we were building the snap image of qaul.net from within CircleCI.
Before this PR, it was built from the Doker snapcore/snapcraft image - which is not maintained at all and is quite obsolete by this point. This caused a compatibility issue with the glibc version available in the image vs. what our packages expect.
Solution
Build the snap image from a machine executor, instead of a docker executor, gives us a bit more control over the environment.
I also made so that new releases will be uploaded to the candidate channel instead of the stable one. This way, we don't replace a known working release with a new one prior to testing.
To install a qaul version from the candidate channel, run:
snap install --candidate qaul
If you already have it installed, you can refresh instead:
snap refresh --candidate qaul
Once you're ready to promote a candidate into the stable channel, you can do so via the Snapcraft UI, or by running the following command:
Description
Closes #534. There was an issue in how we were building the snap image of qaul.net from within CircleCI. Before this PR, it was built from the Doker snapcore/snapcraft image - which is not maintained at all and is quite obsolete by this point. This caused a compatibility issue with the glibc version available in the image vs. what our packages expect.
Solution
Build the snap image from a machine executor, instead of a docker executor, gives us a bit more control over the environment.
I also made so that new releases will be uploaded to the
candidatechannel instead of thestableone. This way, we don't replace a known working release with a new one prior to testing.To install a qaul version from the
candidatechannel, run:If you already have it installed, you can refresh instead:
Once you're ready to promote a candidate into the
stablechannel, you can do so via the Snapcraft UI, or by running the following command: