Bug#688772: gnome Depends network-manager-gnome

[Michael Biebl]

On 25.10.2012 22:47, Andreas Barth wrote:
> * Jeremy Bicha (jbicha at ubuntu.com) [121025 18:51]:
>> On 25 October 2012 12:17, Don Armstrong <don at debian.org> wrote:
>>> That said, if I'm wrong, and you believe that there is a compromise
>>> which would resolve the concerns raised beyond those already presented
>>> (status quo with/without release notes), now would be the time to
>>> present it.
>>
>> My proposal is to:
>> 1. Add a paragraph to the Release Notes with the one line command
>> people should use if they don't want NetworkManager running:
>> "update-rc.d disable network-manager"
>> 2. And cases where that doesn't work are RC.
> 
> How would that prevent startup of n-m during upgrades from stable to
> next-stable?  (Which could already present issues, especially if the
> system is remote managed)

I've been discussing with jordi today about this issue.

One idea that came up was to check wether wicd is in use (or for that
matter ifupdown), and then show a debconf prompt explaining the
situation, and letting the user chose if he wants to take over network
management by NetworkManager.
It would work similar to how we currently handle multiple installed
display managers, like gdm3 or kdm (btw, gdm3 is currently a hard
depends of gnome-core).
If the users choses no, we could disable the service via update-rc.d
disable, so the invoke-rc.d later on in postinst would not start NM.

This would also help in situations where users install both wicd and
network-manager by accident, which usually doesn't really work well
since e.g. both spawn their own instance of wpa_supplicant.

A more detailed reply will follow soon.

Michael

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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 900 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-gnome-maintainers/attachments/20121026/e16b64f4/attachment.pgp>