Hola Javier Fernández-Sanguino Peña <jfs@debian.org> el Fri, 12 Nov 2010 23:36:40 +0100 escribiste: > On Mon, Nov 08, 2010 at 10:55:07PM +0100, Gonzalo Pérez de Olaguer Córdoba wrote: > > The same have happened to me with VPN software: the upgrade stops the VPN > > daemon and leaves the system unconnected while other packages are being > > upgraded. Then, if some other package breaks, the upgrade stops with the > > remote connection stopped: system isolated. > > Which VPN software were you using (openvpn?) we might want to document this > use case and warn sysadmins in the Release Notes. I'm using the tinc package. The problem is inherent to any service required during the upgrade process (in my case tinc and approx). I think it should be documented in any package this situation may happen, and it will also be a good idea to explain it a bit in the release notes. About tinc: The version of tinc in lenny has a debconf question that asks whether you want to retart or not the daemon during upgrades, and explicitly explains this situation. But it seems the new version in squeeze has removed this question, and the situation is not explained anywhere. Looking at the maintainer scripts it seems it restarts the daemon inconditionaly, now. I think this should be considered a bug. Do you want me to report it? I don't see it reported in the current bug's page (both archived and unarchived). I have no idea why they have removed this debconf question. Best regards, Gonzalo. -- Gonzalo Pérez de Olaguer Córdoba <gpoc@iies.es> --- www.gpoc.es PGP key 2861C704 --- F206 5671 6789 425D 111C 1302 214F 1934 2861 C704
Attachment:
signature.asc
Description: PGP signature