This repository was archived by the owner on Sep 24, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 0
Update file Testing Process
Peter Law edited this page Mar 8, 2018
·
4 revisions
The Update File is a file named update.tar.xz
, which contain .deb package files which, once plugged into the robot on a USB stick, are automatically installed.
What follows is the process for testing that the update system works:
- Download an older version of
pi-image.img.xz
, preferably from a link in the docs update page, and flash a Pi SD Card with it (see flashing pis). - Download the
update.tar.xz
of the pi-image version you wish to test from the pi-image build CI artifacts page. - Ensure the version of the packages in the pi are older than the ones being installed (either by looking at the version number with
aptitude status robotd
or by checking a functionality doesn't exist) - Plug in the USB Stick with the
update.tar.xz
, if you want to watch the pi handle the installation, you can runjournalctl -fu runusb
before you do this. A POWER BOARD MUST BE PLUGGED IN AND BE ON FOR THIS TO WORK. - After plugging in, the pi should install the update and reboot. Once this has happened, ensure the update has been applied by checking the new version numbers, and that the new functionality has appeared.
Warning: At time of writing (2018-03-08), the update file doesn't support runusb, so once an update is downloaded you will need to extract and remove runusb. If you don't do this, it will break the pi image as it enters a bad state due to breaking while updating.