Re: connman does not respect /etc/network/interfaces when upgrading from buster to bullseye and more general considerations
Hi Michael, On Sun, Sep 26, 2021 at 01:01:28AM +0200, Michael Biebl wrote: > Am 23.09.21 um 20:17 schrieb Holger Wansing: > > > I have just installed an LXDE system to test this, and now adding > > network-manager-gnome, installs 24 new packages, taking 39 MB of additional > > disk space, according to the apt-get output > I might consider splitting off network-manager's /usr/share/locale into an > (optional, Recommends/Suggests) network-manager-l10n package. The locales > take up about 8,5 MB of disk space. I agree that 8.5MB are not much these days but if it helps to accept network-manager as a unique default this would probably a sensible step. > While I don't necessarily think that 8,5 MB are actually that much of an > issue for desktop installations, trimming down the on disk footprint might > make network-manager more suitable for more constrained environments. > > There is also a (somewhat stale) MR [1] for network-manager asking for the > individual plugins to be split into separate packages to make it possible to > trim down the dependency chain. > > If there is real demand for it, we could revisit that. In the same way I wrote above: If increases the acceptance for NM - yes, this sounds good. Kind regards Andreas. -- http://fam-tille.de
Re: connman does not respect /etc/network/interfaces when upgrading from buster to bullseye and more general considerations
Am 23.09.21 um 20:17 schrieb Holger Wansing: I have just installed an LXDE system to test this, and now adding network-manager-gnome, installs 24 new packages, taking 39 MB of additional disk space, according to the apt-get output I might consider splitting off network-manager's /usr/share/locale into an (optional, Recommends/Suggests) network-manager-l10n package. The locales take up about 8,5 MB of disk space. While I don't necessarily think that 8,5 MB are actually that much of an issue for desktop installations, trimming down the on disk footprint might make network-manager more suitable for more constrained environments. There is also a (somewhat stale) MR [1] for network-manager asking for the individual plugins to be split into separate packages to make it possible to trim down the dependency chain. If there is real demand for it, we could revisit that. Michael [1] https://salsa.debian.org/utopia-team/network-manager/-/merge_requests/4 OpenPGP_signature Description: OpenPGP digital signature
Re: No network management in LXDE task
Quoting Holger Wansing (2021-09-25 22:30:20) > Hi, > > Michael Biebl wrote (Sat, 25 Sep 2021 22:17:48 +0200): > > Am 25.09.21 um 22:05 schrieb Holger Wansing: > > > A patch to address this issue for LXDE is attached. > > > > > > So now you have 3 network configuration systems involved: > > > > - ifupdown, which is still installed by default > > - connman, which is pulled in by the lxde package (via connman-gtk) > > - network-manager(-gnome), which is pulled in via task-lxde-desktop > > > > that doesn't sound like a good solution. > > Hmm, as there are no Conflicts dependencies set for those, I assumed this > is no problem... ? Not only conflicting packages can be non-sensible to pull in by a task. There are no conflicts declared across httpd daemons or dns servers - because in complex scenarios they can be listening on non-default ports. Similarly, network-manager can be custom-configured to only manage some devices and connman only some other devices. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Re: No network management in LXDE task
Hi, Michael Biebl wrote (Sat, 25 Sep 2021 22:17:48 +0200): > Am 25.09.21 um 22:05 schrieb Holger Wansing: > > A patch to address this issue for LXDE is attached. > > > So now you have 3 network configuration systems involved: > > - ifupdown, which is still installed by default > - connman, which is pulled in by the lxde package (via connman-gtk) > - network-manager(-gnome), which is pulled in via task-lxde-desktop > > that doesn't sound like a good solution. Hmm, as there are no Conflicts dependencies set for those, I assumed this is no problem... ? Holger -- Holger Wansing PGP-Fingerprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
Re: No network management in LXDE task
Control: retitle -1 LXDE: Please include a user-friendly network management tool
Control: tags -1 + patch
[ Returning back to #988696 as the correct bug for this issue; dropping 994875
from CC ]
Jaycee Santos wrote (Thu, 23 Sep 2021 20:42:05 +):
> On Thursday, September 23rd, 2021 at 1:05 PM, Michael Biebl
> wrote:
> > Am 23.09.21 um 21:35 schrieb Jaycee Santos:
> > > Is there a reason why to choose gnome-network-manager over something like
> > > nm-tray for LXDE?
> >
> > I think nm-tray (being based on Qt5) is a reasonable choice for LXQT (which
> > is also Qt5 based). LXDE on the other hand uses GTK, so I think
> > network-manager-gnome is a better fit there. (both disk footprint and
> > memory usage wise)
>
> Ah. My apologies. I thought nm-applet was provided by nm-tray. I was wrong.
> I did not know that nm-applet was part of network-manager-gnome!
>
> So I agree with network-manager-gnome being a better fit for LXDE.
Regarding LXQT: this DE already installs cmst by default (an Qt based
GUI for connman, which also has a system tray icon), and since there were
no complains so far from LXQT users related to the network management tool
used, I would not touch LXQT for this.
A patch to address this issue for LXDE is attached.
Holger
diff --git a/debian/changelog b/debian/changelog
index 148cd82d..f4fba03e 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,21 +1,22 @@
tasksel (3.69) UNRELEASED; urgency=medium
* Install CUPS for all *-desktop tasks, now that task-print-service is no
longer existing. Closes: #993668
+ * Install network-manager-gnome in LXDE environment. Closes: #988696
-- Holger Wansing Wed, 08 Sep 2021 22:20:05 +0200
tasksel (3.68) unstable; urgency=medium
diff --git a/debian/control b/debian/control
index 1f469e86..ec6ced7e 100644
--- a/debian/control
+++ b/debian/control
@@ -208,34 +208,36 @@ Package: task-lxde-desktop
Architecture: all
Description: LXDE
This task package is used to install the Debian desktop, featuring
the LXDE desktop environment, and with other packages that Debian users
expect to have available on the desktop.
Depends: ${misc:Depends},
task-desktop,
lightdm,
lxde,
Recommends:
lxtask,
lxlauncher,
xsane,
# libreoffice widgets using just gtk, and also accessibility needs the GTK
frontend
libreoffice-gtk3,
# Package management.
synaptic,
+# desktop network setup
+ network-manager-gnome,
# libreoffice is the best word processor / office suite at the moment
libreoffice-writer,
libreoffice-calc,
libreoffice-impress,
# make help menu work
libreoffice-help-en-us,
# make thesaurus work
mythes-en-us,
# make spellchecker work
hunspell-en-us,
# make hyphenation work
hyphen-en-us,
# gui for configuration of the print service
system-config-printer,
# orca works with lxde, adding accessibility
orca,
--
Holger Wansing
PGP-Fingerprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
Re: No network management in LXDE task
Am 25.09.21 um 22:05 schrieb Holger Wansing: Control: retitle -1 LXDE: Please include a user-friendly network management tool Control: tags -1 + patch [ Returning back to #988696 as the correct bug for this issue; dropping 994875 from CC ] Jaycee Santos wrote (Thu, 23 Sep 2021 20:42:05 +): On Thursday, September 23rd, 2021 at 1:05 PM, Michael Biebl wrote: Am 23.09.21 um 21:35 schrieb Jaycee Santos: Is there a reason why to choose gnome-network-manager over something like nm-tray for LXDE? I think nm-tray (being based on Qt5) is a reasonable choice for LXQT (which is also Qt5 based). LXDE on the other hand uses GTK, so I think network-manager-gnome is a better fit there. (both disk footprint and memory usage wise) Ah. My apologies. I thought nm-applet was provided by nm-tray. I was wrong. I did not know that nm-applet was part of network-manager-gnome! So I agree with network-manager-gnome being a better fit for LXDE. Regarding LXQT: this DE already installs cmst by default (an Qt based GUI for connman, which also has a system tray icon), and since there were no complains so far from LXQT users related to the network management tool used, I would not touch LXQT for this. A patch to address this issue for LXDE is attached. So now you have 3 network configuration systems involved: - ifupdown, which is still installed by default - connman, which is pulled in by the lxde package (via connman-gtk) - network-manager(-gnome), which is pulled in via task-lxde-desktop that doesn't sound like a good solution. OpenPGP_signature Description: OpenPGP digital signature
