build-image: use latest instead of unstable by default
This is actually a question: storage.puri.sm which is used when not using "latest", seems to be offline, so why not make "latest" default and clean up or fix later?
Due to an influx of spam, we have had to impose restrictions on new accounts. Please see this page for instructions on how to get full permissions. Sorry for the inconvenience.
This is actually a question: storage.puri.sm which is used when not using "latest", seems to be offline, so why not make "latest" default and clean up or fix later?