When running koha-remove, if the db for the instance being removed has been previously dropped, koha-remove throws an error and exits. We should add a --force switch so that koha-remove can be made to continue with the cleanup regardless of what errors it encounters. Of course appropriate warnings should be announced.
Yes, we definitely should. This bothers me whenever I'm testing the create/remove scripts.
I just came up against this - very annoying.
Has this already been fixed? The current script seems to already deal with the case of the db not existing.
Are there other cases that need coasting over?
I think the conditions have been generally improved, this probably isn't necessary any more.