Closed mrankine closed 4 years ago
I'm surprised by that - the code at least appears to be checking that the result is a bash script. It's under investigation.
Thanks.
This was on a fresh Raspbian image (2020-02-13 buster lite) and I'd just run apt update && apt dist-upgrade
.
If the version in apt repo is older than 22 Jul 2019 it won't contain the sanity check https://github.com/Hexxeh/rpi-update/commit/a0c5de1e32194ed14818c93e183ca6cbb076059a
@XECDesign how old is rpi-update in apt?
For me, apt reports the latest rpi-update version is 20140705
.
That's very old. I believe the issue is resolve in code from here, but apt needs an update.
Great, thanks! Do I need to file an issue somewhere else to get apt updated?
Let’s wait for a response from @XECDesign - he can get it updated.
Sorry, it's getting harder to spot mentions in all the github emails. Updated rpi-update package should show up in the repo within an hour.
Great, I can see the repo is now on version 20200409
which contains a0c5de1e32194ed14818c93e183ca6cbb076059a.
Thanks! Closing.
Running
sudo rpi-update
results in a brokenrpi-update
script, when GitHub is responding with 500/503 errors.For me at the moment, https://raw.githubusercontent.com/Hexxeh/rpi-update/master/rpi-update responds
500: Internal Server Error
. This is a general GitHub problem, not specific to rpi-update.The problem is that the script does not detect the 500 code, and overwrites itself with this error response. So it will remain broken, even when GitHub is up again. Suggestion: it should only overwrite itself if the HTTP response is 200.
(As a workaround to download a valid script again, use
apt install --reinstall rpi-update
.)Log: