Discussion:
Processed (with 1 error): Re: gnome-core should recommend network-manager instead of network-manager-gnome
Add Reply
Debian Bug Tracking System
2024-08-31 19:40:02 UTC
Reply
Permalink
reopen -1
Bug #1071383 {Done: Jeremy Bícha <***@ubuntu.com>} [gnome-core] gnome-core should recommend network-manager instead of network-manager-gnome
Bug #1077739 {Done: Jeremy Bícha <***@ubuntu.com>} [gnome-core] Remove network-manager-gnome from the recommended list
Bug #1077740 {Done: Jeremy Bícha <***@ubuntu.com>} [gnome-core] Remove network-manager-gnome from the list of dependencies
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions meta-gnome3/1:47~beta+1.
No longer marked as fixed in versions meta-gnome3/1:47~beta+1.
No longer marked as fixed in versions meta-gnome3/1:47~beta+1.
reassign -1 task-gnome-desktop
Bug #1071383 [gnome-core] gnome-core should recommend network-manager instead of network-manager-gnome
Bug #1077739 [gnome-core] Remove network-manager-gnome from the recommended list
Bug #1077740 [gnome-core] Remove network-manager-gnome from the list of dependencies
Bug reassigned from package 'gnome-core' to 'task-gnome-desktop'.
Bug reassigned from package 'gnome-core' to 'task-gnome-desktop'.
Bug reassigned from package 'gnome-core' to 'task-gnome-desktop'.
No longer marked as found in versions meta-gnome3/1:43+1.
No longer marked as found in versions meta-gnome3/1:43+1.
No longer marked as found in versions meta-gnome3/1:43+1.
Ignoring request to alter fixed versions of bug #1071383 to the same values previously set
Ignoring request to alter fixed versions of bug #1077739 to the same values previously set
Ignoring request to alter fixed versions of bug #1077740 to the same values previously set
fixed gnome-core/1:47~beta+1
Unknown command or malformed arguments to command.
forwarded -1 https://salsa.debian.org/installer-team/tasksel/-/merge_requests/31
Bug #1071383 [task-gnome-desktop] gnome-core should recommend network-manager instead of network-manager-gnome
Bug #1077739 [task-gnome-desktop] Remove network-manager-gnome from the recommended list
Bug #1077740 [task-gnome-desktop] Remove network-manager-gnome from the list of dependencies
Set Bug forwarded-to-address to 'https://salsa.debian.org/installer-team/tasksel/-/merge_requests/31'.
Set Bug forwarded-to-address to 'https://salsa.debian.org/installer-team/tasksel/-/merge_requests/31'.
Set Bug forwarded-to-address to 'https://salsa.debian.org/installer-team/tasksel/-/merge_requests/31'.
--
1071383: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071383
1077739: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077739
1077740: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077740
Debian Bug Tracking System
Contact ***@bugs.debian.org with problems
Debian Bug Tracking System
2024-09-15 08:30:01 UTC
Reply
Permalink
tag -1 pending
Bug #1071383 [task-gnome-desktop] gnome-core should recommend network-manager instead of network-manager-gnome
Bug #1077739 [task-gnome-desktop] Remove network-manager-gnome from the recommended list
Bug #1077740 [task-gnome-desktop] Remove network-manager-gnome from the list of dependencies
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
--
1071383: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071383
1077739: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077739
1077740: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077740
Debian Bug Tracking System
Contact ***@bugs.debian.org with problems
Debian Bug Tracking System
2024-10-03 18:10:01 UTC
Reply
Permalink
Your message dated Thu, 03 Oct 2024 18:06:50 +0000
with message-id <E1swQDy-00CGNA-***@fasolo.debian.org>
and subject line Bug#1071383: fixed in tasksel 3.76
has caused the Debian Bug report #1071383,
regarding gnome-core should recommend network-manager instead of network-manager-gnome
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ***@bugs.debian.org
immediately.)
--
1071383: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071383
Debian Bug Tracking System
Contact ***@bugs.debian.org with problems
Simon McVittie
2024-10-14 15:20:01 UTC
Reply
Permalink
The name of the network-manager-gnome package is indeed a bit misleading
nowadays.
Thus for some time I contemplated splitting up the package (similar to how
Fedora has done) into network-manager-applet and nm-connection-editor. The
former would contain the nm-applet binary, the latter nm-connection-editor.
network-manager-gnome would become a transitional metapackage depending on
both.
Desktop environments which already provide an applet/tray could then skip
installing network-manager-applet and opt into installing
nm-connection-editor only (for its advanced functionality).
In trixie's metapackages, we now have:

Package: gnome-core # a smallish GNOME system
Recommends: network-manager [linux-any]

Package: gnome # a fully-featured GNOME system
Depends: network-manager [linux-any]
Suggests: network-manager-gnome [linux-any]

and I think all of that is reasonable.

If you split network-manager-gnome as discussed, then we would certainly
replace network-manager-gnome with nm-connection-editor. We could also
consider promoting nm-connection-editor from Suggests back to Recommends
in the "big" gnome metapackage, although I'm unsure whether we should
or not (my personal inclination would be not).

At the moment, network-manager-gnome is also a Recommends for
gnome-control-center, but perhaps that's a bug? Or perhaps g-c-c uses some
part of n-m-g internally?

task-gnome-flashback-desktop does pull in network-manager-gnome as a
Depends, but that seems right for GNOME Flashback, which is a continuation
of GNOME 2 and doesn't use GNOME Shell (that's the point).

Various non-GNOME desktops do pull in network-manager-gnome, and I'm not
sure which half of it they want: Budgie, Cinnamon, LXDE, LXQt and MATE
pull it in as a Recommends or Depends in their metapackages, XFCE pulls it
in via task-xfce-desktop, and the design-desktop and parl-desktop
metapackages (both of which are XFCE variants) have it as Depends. Those
desktops' maintainers might have an opinion on whether this split would
be helpful.

smcv
Yves-Alexis Perez
2024-10-17 16:20:01 UTC
Reply
Permalink
Post by Simon McVittie
Various non-GNOME desktops do pull in network-manager-gnome, and I'm not
sure which half of it they want: Budgie, Cinnamon, LXDE, LXQt and MATE
pull it in as a Recommends or Depends in their metapackages, XFCE pulls it
in via task-xfce-desktop, and the design-desktop and parl-desktop
metapackages (both of which are XFCE variants) have it as Depends. Those
desktops' maintainers might have an opinion on whether this split would
be helpful.
Good idea. Looping them in here for their feedback.
(Sorry for the massive cross-post and "misusing" this bug report).
Hey, thanks for bringing us (Xfce) in the loop. For Xfce desktop, there is no
(at the moment) equivalent of either nm-applet or nm-connection-editor, so we
use both features (although I guess nm-applet is the most used).

I'm not sure if there are graphical frontend for systemd-networkd but that
could be an alternative as well (never played with it though).

Regards,
- --
Yves-Alexis
Mike Gabriel
2024-11-05 12:10:01 UTC
Reply
Permalink
Hi all,
Hi Simon,
thanks for your reply
Post by Simon McVittie
The name of the network-manager-gnome package is indeed a bit misleading
nowadays.
Thus for some time I contemplated splitting up the package (similar to how
Fedora has done) into network-manager-applet and nm-connection-editor. The
former would contain the nm-applet binary, the latter nm-connection-editor.
network-manager-gnome would become a transitional metapackage depending on
both.
Desktop environments which already provide an applet/tray could then skip
installing network-manager-applet and opt into installing
nm-connection-editor only (for its advanced functionality).
Package: gnome-core # a smallish GNOME system
Recommends: network-manager [linux-any]
Package: gnome # a fully-featured GNOME system
Depends: network-manager [linux-any]
Suggests: network-manager-gnome [linux-any]
and I think all of that is reasonable.
If you split network-manager-gnome as discussed, then we would certainly
replace network-manager-gnome with nm-connection-editor. We could also
consider promoting nm-connection-editor from Suggests back to Recommends
in the "big" gnome metapackage, although I'm unsure whether we should
or not (my personal inclination would be not).
At the moment, network-manager-gnome is also a Recommends for
gnome-control-center, but perhaps that's a bug? Or perhaps g-c-c uses some
part of n-m-g internally?
task-gnome-flashback-desktop does pull in network-manager-gnome as a
Depends, but that seems right for GNOME Flashback, which is a continuation
of GNOME 2 and doesn't use GNOME Shell (that's the point).
Various non-GNOME desktops do pull in network-manager-gnome, and I'm not
sure which half of it they want: Budgie, Cinnamon, LXDE, LXQt and MATE
pull it in as a Recommends or Depends in their metapackages, XFCE pulls it
in via task-xfce-desktop, and the design-desktop and parl-desktop
metapackages (both of which are XFCE variants) have it as Depends. Those
desktops' maintainers might have an opinion on whether this split would
be helpful.
Good idea. Looping them in here for their feedback.
In MATE Desktop we actively want / use / rely-on
network-manager-gnome. When touching the whole thing, may I suggest
renaming the bin:pkg "network-manager-gnome" to another name? Such es
network-manager-applet?

Mike
--
DAS-NETZWERKTEAM
c\o Technik- und Ökologiezentrum Eckernförde
Mike Gabriel, Marienthaler Str. 17, 24340 Eckernförde
mobile: +49 (1520) 1976 148
landline: +49 (4351) 850 8940

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31
mail: ***@das-netzwerkteam.de, http://das-netzwerkteam.de
Simon McVittie
2024-11-06 10:40:02 UTC
Reply
Permalink
The name of the network-manager-gnome package is indeed a bit misleading
nowadays.
Thus for some time I contemplated splitting up the package (similar to how
Fedora has done) into network-manager-applet and nm-connection-editor. The
former would contain the nm-applet binary, the latter nm-connection-editor.
network-manager-gnome would become a transitional metapackage depending on
both.
This split is now present in unstable.
In MATE Desktop we actively want / use / rely-on network-manager-gnome. When
touching the whole thing, may I suggest renaming the bin:pkg
"network-manager-gnome" to another name? Such es network-manager-applet?
Please see the quoted text above, and please change MATE's dependency to
either nm-applet (if you want the icon in the notification area/"tray")
or nm-connection-editor (if you want the configuration editor) or both
(if you want all of the previous functionality of n-m-gnome).

The network-manager-gnome transitional package cannot usefully be renamed:
the whole point of transitional packages is that they keep the old name,
and depend on the new name(s). But desktop environments can stop depending
on it.

smcv
Mike Gabriel
2024-11-06 16:10:01 UTC
Reply
Permalink
Post by Simon McVittie
The name of the network-manager-gnome package is indeed a bit
misleading
nowadays.
Thus for some time I contemplated splitting up the package
(similar to how
Fedora has done) into network-manager-applet and
nm-connection-editor. The
former would contain the nm-applet binary, the latter
nm-connection-editor.
network-manager-gnome would become a transitional metapackage
depending on
both.
This split is now present in unstable.
In MATE Desktop we actively want / use / rely-on network-manager-gnome. When
touching the whole thing, may I suggest renaming the bin:pkg
"network-manager-gnome" to another name? Such es network-manager-applet?
Please see the quoted text above, and please change MATE's dependency to
either nm-applet (if you want the icon in the notification area/"tray")
or nm-connection-editor (if you want the configuration editor) or both
(if you want all of the previous functionality of n-m-gnome).
Urgh... will network-manager-applet work / behave well if
nm-connection-editor is not installed? IMHO, nm-applet is quite
useless with nm-connection-editor. Wouldn't it be could to let
network-manager-applet depend on nm-connection-editor?

Mike
--
DAS-NETZWERKTEAM
c\o Technik- und Ökologiezentrum Eckernförde
Mike Gabriel, Marienthaler Str. 17, 24340 Eckernförde
mobile: +49 (1520) 1976 148
landline: +49 (4351) 850 8940

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31
mail: ***@das-netzwerkteam.de, http://das-netzwerkteam.de
Simon McVittie
2024-11-06 13:10:01 UTC
Reply
Permalink
Post by Simon McVittie
The name of the network-manager-gnome package is indeed a bit misleading
nowadays.
Thus for some time I contemplated splitting up the package (similar to how
Fedora has done) into network-manager-applet and nm-connection-editor. The
former would contain the nm-applet binary, the latter nm-connection-editor.
network-manager-gnome would become a transitional metapackage depending on
both.
This split now exists in unstable.
Post by Simon McVittie
Various non-GNOME desktops do pull in network-manager-gnome, and I'm not
sure which half of it they want: Budgie, Cinnamon, LXDE, LXQt and MATE
pull it in as a Recommends or Depends in their metapackages, XFCE pulls it
in via task-xfce-desktop, and the design-desktop and parl-desktop
metapackages (both of which are XFCE variants) have it as Depends. Those
desktops' maintainers might have an opinion on whether this split would
be helpful.
Good idea. Looping them in here for their feedback.
I've opened bugs for the non-GNOME packages that Depend/Recommend/Suggest
the transitional network-manager-gnome, asking for them to
move to Depends/Recommends/Suggests on network-manager-applet,
nm-connection-editor and/or network-manager.

(I didn't bother to open bugs for GNOME team packages, I just fixed them
instead :-)

smcv
David Mohammed
2024-11-04 20:10:01 UTC
Reply
Permalink
Post by Simon McVittie
The name of the network-manager-gnome package is indeed a bit misleading
nowadays.
Thus for some time I contemplated splitting up the package (similar to how
Fedora has done) into network-manager-applet and nm-connection-editor. The
former would contain the nm-applet binary, the latter nm-connection-editor.
network-manager-gnome would become a transitional metapackage depending on
both.
Desktop environments which already provide an applet/tray could then skip
installing network-manager-applet and opt into installing
nm-connection-editor only (for its advanced functionality).
Package: gnome-core # a smallish GNOME system
Recommends: network-manager [linux-any]
Package: gnome # a fully-featured GNOME system
Depends: network-manager [linux-any]
Suggests: network-manager-gnome [linux-any]
and I think all of that is reasonable.
If you split network-manager-gnome as discussed, then we would certainly
replace network-manager-gnome with nm-connection-editor. We could also
consider promoting nm-connection-editor from Suggests back to Recommends
in the "big" gnome metapackage, although I'm unsure whether we should
or not (my personal inclination would be not).
At the moment, network-manager-gnome is also a Recommends for
gnome-control-center, but perhaps that's a bug? Or perhaps g-c-c uses some
part of n-m-g internally?
task-gnome-flashback-desktop does pull in network-manager-gnome as a
Depends, but that seems right for GNOME Flashback, which is a continuation
of GNOME 2 and doesn't use GNOME Shell (that's the point).
Various non-GNOME desktops do pull in network-manager-gnome, and I'm not
sure which half of it they want: Budgie, Cinnamon, LXDE, LXQt and MATE
pull it in as a Recommends or Depends in their metapackages, XFCE pulls it
in via task-xfce-desktop, and the design-desktop and parl-desktop
metapackages (both of which are XFCE variants) have it as Depends. Those
desktops' maintainers might have an opinion on whether this split would
be helpful.
smcv
From a budgie perspective, network management is handled by
budgie-control-center which is similar to gnome-control-center.

Budgie also utilises nm-applet for its panel. Budgie has no need for
nm-connection-editor nor does it need gnome-core.
Loading...