Mismatching sha256sum on L5 download server

[dos]

landing is completely broken itself, that one’s expected

[muon]

@irvinewade

So you only have the option of not checking the hash if you bypass the script and do some of the steps manually.

I don’t always bypass the script, but when I do, I check the hash.

Erm, anyway… that’s good that it’s fixed, but I’m not sure I want to reflash a 3rd time for a test right now! I may have to find a way to automate post-flash setup…

[riabenko]

@dos

For the record, I’ve fixed the CI image generation, so you should be able to flash your phones with recent plain image by omitting --stable parameter (until it breaks again at least).

In order to promote the new images to stable and in turn fix the sum mismatch that’s currently present there, someone would have to test them. I’m not going to promote them blindly

Do I understand it correctly that, to help you test the latest image, I should follow the developer doumentation on reflashing but omit the --stable flag, then report here?

[irvinewade]

@riabenko

omit the --stable flag

Correct. That will pick up the daily build - so potentially less stable but should at least have a correct checksum.