The software updater has an init() method that, among other things, claims to be for the purpose of making sure everything works fine before it indicates to a previous software updater that started it that the new one is now taking over so the old software updater can exit. However, the part of the code in init() that does the runthrough of an update is wrapped in a try/except that pass's on all exceptions, so this could never cause the newly-started software updater to exit.
I'll probably remove the code related to calling do_rsync() from the init() method rather than change the code to cause the software updater to exit if the rsync fails. There could be an argument for making it exit, but I think if we wanted to do that we'd want to be careful about the types of exceptions that cause it to exit.
The software updater has an init() method that, among other things, claims to be for the purpose of making sure everything works fine before it indicates to a previous software updater that started it that the new one is now taking over so the old software updater can exit. However, the part of the code in init() that does the runthrough of an update is wrapped in a try/except that pass's on all exceptions, so this could never cause the newly-started software updater to exit.
I'll probably remove the code related to calling do_rsync() from the init() method rather than change the code to cause the software updater to exit if the rsync fails. There could be an argument for making it exit, but I think if we wanted to do that we'd want to be careful about the types of exceptions that cause it to exit.