From: Ian Jackson Date: Fri, 24 Aug 2012 18:07:31 +0000 (+0100) Subject: 681834 rra-draft-ijackson substantive changes X-Git-Url: https://git.donarmstrong.com/?a=commitdiff_plain;h=709dbac0c30fbd520be80e3cfe403e79bee684e4;p=debian-ctte.git 681834 rra-draft-ijackson substantive changes --- diff --git a/681834_gnome_recommends_networkmanager/rra-draft-ijackson b/681834_gnome_recommends_networkmanager/rra-draft-ijackson index 3aa53eb..b284c8c 100644 --- a/681834_gnome_recommends_networkmanager/rra-draft-ijackson +++ b/681834_gnome_recommends_networkmanager/rra-draft-ijackson @@ -1,3 +1,5 @@ + Whereas: + 1. The gnome-core metapackage is intended to reflect the core of the GNOME desktop environment: the basic tools and subsystems that together constitute GNOME. The gnome metapackage is intended to @@ -13,11 +15,10 @@ but not Depends. In wheezy, currently, network-manager has moved from gnome to gnome-core, and from Recommends to Depends. This represents a substantially increased insistance that users of the GNOME - metapackages have network-manager installed. This change is, so far - as the Technical Committee understands, driven primarily by user - confusion and bug reports, but does not reflect a deeper or tighter - integration of network-manager into GNOME than was the case in - squeeze. + metapackages have network-manager installed. This change does + not reflect, so far as the Technical Committee understands, a + deeper or tighter integration of network-manager into GNOME than + was the case in squeeze. 4. If matters are left as they currently stand, users who have the gnome metapackages installed but do not have network-manager installed will, @@ -44,9 +45,7 @@ importance) will make it more difficult than necessary for GNOME users to swap network management components, something for which there appears to be noticable demand. We therefore believe that - network-manager should be either moved to Recommends in gnome-core, or - moved from the gnome-core metapackage to the gnome metapackage (which - is defined as including additional, optional components). + network-manager should be moved to Recommends in gnome-core. 7. Please note that this is not a general statement about GNOME components. It is very specific to network-manager because all of the @@ -66,3 +65,13 @@ 8. If any of these points did not apply, the situation would be significantly different. + + Therefore: + + 9. The Technical Committee overrules the decision of the gnome-core + metapackage maintainers. The dependency from gnome-core to + network-manager-gnome should be downgraded to Recommends. + + 10. The Technical Committee requests that the Release Managers + unblock the update to implement this decision, so that this + change may be released in wheezy.