Hi,
this is a reply to a message from the older bug but it has never
been answered and I believe it's useful to take a proper decision
so I answer in the new bug:
On Tue, 11 Sep 2012, Ian Jackson wrote:
Jeremy Bicha writes (Bug#681834: Call for votes on network-manager, gnome):
I see two
Hi,
On Thu, 25 Oct 2012, Ian Jackson wrote:
Raphael Hertzog writes (Re: Bug#681834: Call for votes on network-manager,
gnome):
Nobody responded to this but while discussing with the GNOME maintainers
I quickly got the answer. NM is a build-time dependency of GNOME Shell
but Debian has
On Vi, 14 sep 12, 21:42:05, Philipp Kern wrote:
And I did not experience network breakage during upgrade bugs recently. I
think
the LAN ports just stick around and I don't do upgrades over wi-fi.
I do, on unstable (mostly). The wireless connection is reset, which,
depending on what else
Ian Jackson ijack...@chiark.greenend.org.uk writes:
Russ Allbery writes (Re: Bug#681834: network-manager, gnome, Recommends vs
Depends):
The options are:
A. Recommends not Depends (overrule maintainers). 3:1 required.
F. Further Discussion.
I vote AF.
Bdale
pgpFnBm8vt7pB.pgp
On Tue, Sep 11, 2012 at 04:10:10PM +0100, Ian Jackson wrote:
The options are:
A. Recommends not Depends (overrule maintainers). 3:1 required.
F. Further Discussion.
I vote AF.
(FWIW I am chiefly persuaded by the upgrade arguments; if not for that
then other solutions such as remove the
On Tue, Sep 11, 2012 at 09:32:32PM -0400, Chris Knadle wrote:
- I experienced breakages on NM on upgrades on several occasions, whereby
I switched to wicd.
But then sadly NM is the only network connection management tool for laptop
users in wheezy that handles IPv6 properly. Hence I turned
* Ian Jackson (ijack...@chiark.greenend.org.uk) [120911 15:10]:
Russ Allbery writes (Re: Bug#681834: network-manager, gnome, Recommends vs
Depends):
Here's what I now have:
I asked for comments and no-one had any. So I hereby call for votes
on the resolution below.
The options are:
]] Chris Knadle
- Furthermore my experience has been that disabling NM via modifying the
init script (i.e. the exit 0 suggestion which came up on [debian-devel],
or making the init script non-executble) only works until NM is upgraded,
whereby the init script is replaced and thus the
Russ Allbery writes (Re: Bug#681834: network-manager, gnome, Recommends vs
Depends):
Here's what I now have:
I asked for comments and no-one had any. So I hereby call for votes
on the resolution below.
The options are:
A. Recommends not Depends (overrule maintainers). 3:1 required.
F.
Ian Jackson writes (Bug#681834: Call for votes on network-manager, gnome):
The options are:
A. Recommends not Depends (overrule maintainers). 3:1 required.
F. Further Discussion.
I vote: A F
Ian.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject
On Tue, 11 Sep 2012, Ian Jackson wrote:
Russ Allbery writes (Re: Bug#681834: network-manager, gnome, Recommends vs
Depends):
Here's what I now have:
I asked for comments and no-one had any. So I hereby call for votes
on the resolution below.
The options are:
A. Recommends not
Ian Jackson ijack...@chiark.greenend.org.uk writes:
I asked for comments and no-one had any. So I hereby call for votes
on the resolution below.
The options are:
A. Recommends not Depends (overrule maintainers). 3:1 required.
F. Further Discussion.
The full resolution text,
I see two things missing from this resolution:
1. GNOME has a stronger dependency on NM than they did when Squeeze
was released. GNOME Shell now has a hard dependency on NM.
The user has to take separate, explicit (and somewhat unusual for the
average user) action to disable network-manager
Jeremy Bicha writes (Bug#681834: Call for votes on network-manager, gnome):
I see two things missing from this resolution:
1. GNOME has a stronger dependency on NM than they did when Squeeze
was released. GNOME Shell now has a hard dependency on NM.
Do you mean
http://packages.debian.org
On Tuesday, September 11, 2012 13:52:47, Jeremy Bicha wrote:
I see two things missing from this resolution:
1. GNOME has a stronger dependency on NM than they did when Squeeze
was released. GNOME Shell now has a hard dependency on NM.
The user has to take separate, explicit (and somewhat
On 11 September 2012 21:32, Chris Knadle chris.kna...@coredump.us wrote:
- There are other network managers than NM.
Of course, but only one is part of GNOME. Nothing else integrates into
GNOME Shell's top bar or System Settings (gnome-control-center). GNOME
2 was different as wicd could
Chris Knadle chris.kna...@coredump.us writes:
- Furthermore my experience has been that disabling NM via modifying the
init script (i.e. the exit 0 suggestion which came up on [debian-devel],
or making the init script non-executble) only works until NM is upgraded,
whereby the init
Jeremy Bicha jbi...@ubuntu.com writes:
On 11 September 2012 21:32, Chris Knadle chris.kna...@coredump.us wrote:
- My experience has been that NM conflicts with wicd when NM is running.
You have two network managers running on your computer and you expect
networking to not have problems?
The
On Tuesday, September 11, 2012 21:59:49, Jeremy Bicha wrote:
On 11 September 2012 21:32, Chris Knadle chris.kna...@coredump.us wrote:
- There are other network managers than NM.
Of course, but only one is part of GNOME. Nothing else integrates into
GNOME Shell's top bar or System Settings
On Tuesday, September 11, 2012 22:04:08, Russ Allbery wrote:
Chris Knadle chris.kna...@coredump.us writes:
- Furthermore my experience has been that disabling NM via modifying the
init script (i.e. the exit 0 suggestion which came up on
[debian-devel], or making the init script
20 matches
Mail list logo
