This should help with situations like https://github.com/raspberrypi/rpi-eeprom/issues/336 where the user runs rpi-update to get the "beta firmware", but then (accidentally?) runs apt-get update && apt-get upgrade which then updates raspberrypi-bootloader which overwrites the new "beta firrmware" with the older "stable firmware". If the user realises their mistake and tries running rpi-update again, they'll just get told "Your firmware is already up to date.".
This PR updates that message to tell the user how to "force" an rpi-update. (perhaps there's a "better" way of doing this, but this seemed like the simplest option?)
This should help with situations like https://github.com/raspberrypi/rpi-eeprom/issues/336 where the user runs
rpi-updateto get the "beta firmware", but then (accidentally?) runsapt-get update && apt-get upgradewhich then updatesraspberrypi-bootloaderwhich overwrites the new "beta firrmware" with the older "stable firmware". If the user realises their mistake and tries runningrpi-updateagain, they'll just get told "Your firmware is already up to date.".This PR updates that message to tell the user how to "force" an rpi-update. (perhaps there's a "better" way of doing this, but this seemed like the simplest option?)