Bug#688772: gnome Depends network-manager-gnome

[Jeremy Bicha]

On 12 October 2012 07:31, Ian Jackson <ijackson at chiark.greenend.org.uk> wrote:
> Don Armstrong writes ("Bug#688772: gnome Depends network-manager-gnome"):
>> 1) we decide that failures of NM to detect basic ifupdown
>> configurations and avoid overriding them are bugs, possibly of RC
>> severity
>>
>> 2) given the gnome maintainer's desire to have NM installed by default
>> from the gnome metapackage
>>
>> allowing gnome to Depends: nm | wicd; would deal with the most
>> concerning form of breakage for me.
>>
>> Does this work for anyone else?
>
> Why do you think the gnome metapackage depending on, rather than
> recommending, wicd, is a good idea ?  I don't really see the logical
> connection between any of the goals (whether the TC's or the GNOME
> maintainers') and your proposal.
>
> For example, consider the position of someone who has deliberately
> removed n-m in squeeze, and is using ifupdown or running ifconfig by
> hand or whatever, and upgrades to wheezy.  This still gives them n-m
> back.  That's not respecting their previous choice to remove it.

The point I took away from Chris' post is that wicd does not integrate
with GNOME Shell at all. There is only one networking solution that is
supported with GNOME 3.

Not to put more ideas in Ian's head about packaging decisions to
overrule, but nobody objects to gnome-core depending on gdm, which
also starts by default after installation unless you explicitly
disable it, and conflicts with several other display managers that are
part of Debian.

I consider a usable UI for setting up mobile networking (to include
WiFi) to be a fundamental piece of any desktop, especially GNOME.

I support Don's proposal to consider bugs where NM does not work right
with basic ifupdown configs to be RC-severity.

Jeremy