[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#688772: gnome Depends network-manager-gnome

]] Colin Watson 


> Some types of networking are just so rarely used as anything other than
> a means of getting connectivity in network-poor locations that I would
> have a very hard time arguing that their interruption during upgrades
> could be release-critical.  For instance, if a 3G network interface went
> down during upgrade, or the client end of an IP-over-DNS link, then
> that's ungraceful and could be handled more smoothly, but I don't think
> it's RC.

While I think this position is reasonable, how should this be
communicated to the administrator?  Having to check postinst scripts for
all packages that might interfere with network connectivity isn't really

(I think 3G network interfaces will be more common than you believe, in
particular for embedded setups.  I've personally reconfigured multiple
thousand power meters over 3G links, and if that particular upgrade had
gone awry, the company I did the work for would have incurred a cost in
the millions of NOK, since they'd have to send people to each location
to reinitialise the meters.  This is a bit of an extreme example and not
particularly common, but the impact can be very large.)

Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are

Reply to: