New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
.deb, .rpm, apt, yum, 402 issue #4059
Comments
(It might also be worth providing instructions in your post above for how people can update their apt / yum configs to remove Cloudsmith, so that people stop getting this 402 error every time they do |
Please provide an alternative way to install and update the package as this software is really awesome and would highly recommend it. |
i.e. https://github.com/balena-io/etcher/releases for those people not familiar with GitHub. |
Nope ! in my Ubuntu Focal 20.04 I have package balena-etcher-electron installed. It's no where here in the releases ... I have for the moment edited the lines in /etc/apt/sources.list.d/ $ sudo mv balena-etcher.list balena-etcher.list.bak In order not to block updating from all other repos ... Well installing balena-etcher 1.18.8 (since the package changed name ...) ended up with an error ... Unpacking balena-etcher (1.18.8) ... Although the package still gets installed and seems to work opening up its windows. |
Hey, Cheers. |
Does that mean that the "OSS hosting by cloudsmith" button ought to be removed from https://etcher.balena.io/#download-etcher ? |
Hello,
We're moving out of Cloudsmith as continuing to host the package there would be too costly for us.
We're very thankful for the service and help CloudSmith provided, and would recommend their product for smaller open-source apps and private packages anytime!
At the moment we don't have the bandwidth (pun intended) to set up an alternative repository but might be moving to self-hosted (probably CloudFlare) in the upcoming weeks.
So sorry for the inconvenience and thank you for your patience.
Note that you can always get a .deb and .rpm package in the release section of the GitHub repository.
The text was updated successfully, but these errors were encountered: