Bug#688772: gnome Depends network-manager-gnome

[Don Armstrong]

On Tue, 25 Sep 2012, Ian Jackson wrote:
> This bug is to track this issue. Please send all discussion on this
> topic only to this bug report. I will make sure that the gnome
> maintainers are pointed to this bug report.

Discussion seems to have stopped on this bug; I have drafted an
additional set of options for discussion, both of which borrow
liberally from ian's draft, and are presented below.

I'd like to either reconcile these options in the next few days so we
can vote on this issue and resolve it before it impacts the release
schedule. [I don't anticipate calling for votes before our meeting on
Thursday, but we should at least try to get any preliminaries out of
the way first if possible.]


Don Armstrong

-- 
When I was a kid I used to pray every night for a new bicycle. Then I 
realized that the Lord doesn't work that way so I stole one and asked
Him to forgive me.
 -- Emo Philips.

http://www.donarmstrong.com              http://rzlab.ucr.edu
-------------- next part --------------
1. The TC notes the decision of the meta-gnome maintainers to
   implement the TC decision in #681834 by:
    (a) softening the dependency in the gnome-core metapackage
        from Depends to Recommends, as required
    (b) adding a new dependency in the gnome metapackage,
        as a Depends.  (In squeeze, this is where the dependency
        was, but it was a Recommends.)

2. Our intent, as stated in the rationale section of our previous
   decision (#681834, paras 3 and 5), is that squeeze users who have
   gnome installed but not network-manager do not find that
   network-manager becomes installed when they upgrade to wheezy.

3. A Recommends from gnome to network-manager-gnome would serve no
   purpose in wheezy as gnome Depends on gnome-core which already
   Recommends network-manager-gnome.

Therefore

A 4. We overrule the decision of the meta-gnome maintainers to add a
A    dependency from gnome to network-manager-gnome; this dependency
A    should be removed for the release of wheezy.
A 
A 5. We request that the Release Team unblock update(s) to meta-gnome so
A    that our decisions may be implemented in wheezy.

B 4. We overrule the decision of the meta-gnome maintainers to add a
B    dependency from gnome to network-manager-gnome; this dependency
B    should be replaced with a dependecy on network-manager-gnome (>=
B    0.9.4) | wicd.
B
B 5. Bugs in network-manager-gnome which break the functionality of
B    existing /etc/network/interfaces rules are to be considered RC.
B
B 6. We request that the Release Team unblock update(s) to meta-gnome so
B    that our decisions may be implemented in wheezy.
-------------- next part --------------
Whereas

1. The TC notes the decision of the meta-gnome maintainers to
   implement our decision in #681834 by:
    (a) softening the dependency in the gnome-core metapackage
        from Depends to Recommends, as required
    (b) adding a new dependency in the gnome metapackage,
        as a Depends.  (In squeeze, this is where the dependency
        was, but it was a Recommends.)

2. Our intent, as stated in the rationale section of our previous
   decision (#681834, paras 3 and 5), is that squeeze users who have
   gnome installed but not network-manager do not find that
   network-manager becomes installed when they upgrade to wheezy.

3. The actions of the meta-gnome maintainers do not achieve this
   objective.

4. Insofar as any reasons have been advanced for the meta-gnome
   maintainer's decision, we do not find them convincing.

5. A Recommends from gnome to network-manager-gnome would serve no
   purpose in wheezy as gnome Depends on gnome-core which already
   Recommends network-manager-gnome.

Therefore

6. We overrule the decision of the meta-gnome maintainers to add a
   dependency from gnome to network-manager-gnome.  This dependency
   should be removed.

7. We request that the Release Team unblock update(s) to meta-gnome so
   that our decisions may be implemented in wheezy.

8. We specifically forbid anyone from introducing in wheezy, or
   in sid until wheezy is released:
    a. Any new or enhanced dependencies, or any other mechanisms,
       which increase the likelihood of network-manager being
       installed;
    b. Any new or enhanced user-facing warnings, imprecations, or
       other kinds of message regarding the alleged desirability or
       requirement to install network-manager;
    c. Any change which in any way impairs (or further impairs) the
       functioning of systems with GNOME components installed but
       without network-manager;
    d. Any change which is contrary to the spirit or intent of either
       our previous resolution in #681834 or this resolution.
   without first obtaining the permission of at least one member of
   the Technical Committee.

Furthermore

9. It is disappointing that this proposed solution to the problem was
   not mentioned during the TC discussion.  If it had been, it could
   have been accepted or rejected by the TC at the time.

10. We remind everyone that the Constitution requires members of the
   project not to work against decisions properly made according to
   the project's governance processes.  On this occasion we do not
   feel it necessary to refer anyone to the Debian Account Managers
   asking for a review of their status.