Your message dated Sat, 09 Apr 2011 01:04:23 +0200
with message-id <[email protected]>
and subject line fixed in 0.8.1+
has caused the Debian Bug report #439917,
regarding network-manager should not deactivate networks on uninstall
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
439917: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=439917
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: network-manager
Version: 0.6.4-8+b1
Severity: important

this is related to #432322 I suppose.

When you are removing network-manager, the postrm should
not deactivate your network connections, since the system
administrator has indicated (by removing n-m) that he/she
no longer wishes it to manage the network. Alternatively I
suppose kicking invoke-rc.d networking restart or ifupping
the interfaces n-m /was/ managing would be wise. But as it
stands, removing n-m can drop your machine from the network.

(As it happens, I didn't explicitly ask for n-m to be
removed either, I presume some dependency changed somewhere
and it was marked as automatic by aptitude, so the machine
dropping off the network came as a bit of a surprise).


-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.21-2-686 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages network-manager depends on:
ii  adduser                       3.104      add and remove users and groups
ii  dbus                          1.1.1-3    simple interprocess messaging syst
pn  dhcdbd                        <none>     (no description available)
ii  hal                           0.5.9.1-4  Hardware Abstraction Layer
ii  ifupdown                      0.6.8      high level tools to configure netw
pn  iproute                       <none>     (no description available)
pn  iputils-arping                <none>     (no description available)
ii  libc6                         2.6.1-1+b1 GNU C Library: Shared libraries
ii  libdbus-1-3                   1.1.1-3    simple interprocess messaging syst
ii  libdbus-glib-1-2              0.74-1     simple interprocess messaging syst
ii  libgcrypt11                   1.2.4-2    LGPL Crypto library - runtime libr
ii  libglib2.0-0                  2.14.0-2   The GLib library of C routines
ii  libgpg-error0                 1.4-2      library for common error values an
ii  libhal1                       0.5.9.1-4  Hardware Abstraction Layer - share
ii  libiw29                       29~pre22-1 Wireless tools - library
pn  libnl1-pre6                   <none>     (no description available)
pn  libnm-util0                   <none>     (no description available)
ii  lsb-base                      3.1-24     Linux Standard Base 3.1 init scrip
pn  wpasupplicant                 <none>     (no description available)

Versions of packages network-manager recommends:
pn  network-manager-gnome | netwo <none>     (no description available)


--- End Message ---
--- Begin Message ---
Version: 0.8.3.999-1

Hi,

for ethernet type connections (both dhcp and static ip), NM will no longer tear
down the connection on stop and can seamlessly pick up the connection again on
(re)start.
For wireless connections this is not easily possible, as this relies on
wpasupplicant.



Cheers,
Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---

Reply via email to