Feat/19 installer - #23
Merged
Merged
Conversation
qquais
force-pushed
the
feat/19-installer
branch
from
September 9, 2026 20:32
5139898 to
572a454
Compare
…bles REMOTE_SERIAL_PICO_REPO and REMOTE_SERIAL_PICO_BRANCH override what gets cloned, so a change can be installed on a spare Pi and tested end to end before it is merged. doctor now also names the checked-out branch.
…eck commands dpkg -s exits 0 for a package in "config files" state, so udisks2 that had been removed was never reinstalled and the flasher would fail at mount time. Check the dpkg status text instead, and make doctor verify that git, python3 and udisksctl actually exist. Found by a fresh-install test on the dev Pi.
RajkumarGara
approved these changes
Sep 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Title: One-command Pi install with doctor and status (#19)
Setting up a Pi meant six manual steps from the README, and the old installer
got several of them wrong. Now
sudo remote-serial-pico installdoes all ofthem, is safe to run again, and the service comes back after a reboot.
remote-serial-pico doctorchecks everything and says how to fix what's wrong;statusshows whether it's running and which Picos are connected.Tested on a dev Pi: fresh install, a second run that changed nothing, and a
reboot, after which the service was running by itself. 17 unit tests. Nothing
changes on the office Pi until someone runs it there.