Christian Hammers wrote... > Regarding to the "fails to upgrade": as a restart of Quagga potentially > means a loss of Internet connection for the router (and connected subnets) > which is especially ugly if you administrate the server via ssh many people > explicitly requested that Quagga will *not* be upgraded by default which was > the reason I implemented this defaults-to-false debconf question.
I understand your point: The admin should not upgrade without prior
thought. However, even if he has done the proper preparations like
logging in via a serial console, he still cannot upgrade unless he
changes the debconf setting - and back to the prior setting to avoid
shooting his foot the next time. This is a bit of a nuissance.
> So would you suggest to just clarify the wording of the question or
> what else to do?
My suggestion: Check whether quagga is still running and abort the
upgrade only if it does. Print a warning then about probable loss of
connectivity during the upgrade and say that quagga has to be stopped
manually before upgrade to avoid a fatal situation.
Christoph
signature.asc
Description: Digital signature
