Bug#688772: Current options for resolving 688772 [Re: Bug#688772: gnome Depends network-manager-gnome]
Don Armstrong <email@example.com> writes:
> This is the current text of the options for #688772. I'd like to vote on
> this before the 9th if at all possible. If anyone has any comments,
> changes, or would like to propose different options, please do so now.
After considering this and following the discussion, I'm not willing to
vote for either A or B, and would end up voting further discussion. I'd
like to add an option C, along the lines of:
4. After further discussion, we understand that reintroducing
network-manager on upgrade was part of the intent, due to both
substantial improvements in network-manager and tighter integration of
network-manager with the GNOME desktop in wheezy. Since the gnome
metapackage has historically been more aggressive at pulling in
additional packages, we believe the move of the dependency from
gnome-core to gnome is an acceptable compromise that was not raised
during the previous discussion. Users who want to remove
network-manager can still use the gnome-core metapackage to get the
basic GNOME desktop functionality.
We recommend that this upgrade behavior for users of the gnome
metapackage be documented in the release notes.
This is not to say that I'm opposed to fixing network-manager to deal with
some of the other upgrade problems. I'm all in favor! But I'm not
comfortable with making inclusion of the dependency conditional on solving
the broader problem in the way described there. If it happens in time for
the release, I'm all in favor, and it makes it an even better compromise,
but I think it would be acceptable to release without that fix and
document the issue in the release notes.
In other words, my *preferred* option is B with the fix to the
network-manager package, but B as phrased has consequences for not getting
that fix done in time that I'm not comfortable with.
Russ Allbery (firstname.lastname@example.org) <http://www.eyrie.org/~eagle/>