info
Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Bug#994875: connman does not respect /etc/network/interfaces when upgrading from buster to bullseye
3 views
Skip to first unread message
Andreas Tille
Sep 22, 2021, 7:20:03 AM9/22/21
to
Package: connman
Version: 1.36-2.2
Severity: important
X-Debbugs-Cc: debian...@lists.debian.org
Hi,
recently I was upgrading a workstation running buster to bullseye from
remote. This box had a fixed IP set in /etc/network/interfaces. After
a rebooting I've "lost" the machine and I had to check the machine
physicaly. It was asking for a totally different IP address via DHCP.
I found out that connman was installed on this machine due to lxde
metapackage Recommends. After simply purging connman which is not used
anyway all went fine on this machine.
I would have loved to track this down in more detail but this
workstation is mission critical and there is no option to bother users
with fiddling around on the system that is now running as expected
again. I'm fine with digging in the logs if you tell me what kind of
information is needed.
Kind regards
Andreas.
-- System Information:
Debian Release: 11.0
APT prefers testing
APT policy: (501, 'testing'), (50, 'buildd-unstable'), (50, 'unstable'), (5, 'experimental'), (1, 'buildd-experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-8-amd64 (SMP w/4 CPU threads)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE:de
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages connman depends on:
ii dbus 1.12.20-2
ii init-system-helpers 1.60
ii iptables 1.8.7-1
ii libc6 2.31-13
ii libdbus-1-3 1.12.20-2
ii libglib2.0-0 2.68.4-1
ii libgnutls30 3.7.1-5
ii libreadline8 8.1-1
ii libxtables12 1.8.7-1
ii lsb-base 11.1.0
Versions of packages connman recommends:
pn bluez <none>
pn ofono <none>
ii wpasupplicant 2:2.9.0-21
Versions of packages connman suggests:
pn connman-vpn <none>
Version: 1.36-2.2
Severity: important
X-Debbugs-Cc: debian...@lists.debian.org
Hi,
recently I was upgrading a workstation running buster to bullseye from
remote. This box had a fixed IP set in /etc/network/interfaces. After
a rebooting I've "lost" the machine and I had to check the machine
physicaly. It was asking for a totally different IP address via DHCP.
I found out that connman was installed on this machine due to lxde
metapackage Recommends. After simply purging connman which is not used
anyway all went fine on this machine.
I would have loved to track this down in more detail but this
workstation is mission critical and there is no option to bother users
with fiddling around on the system that is now running as expected
again. I'm fine with digging in the logs if you tell me what kind of
information is needed.
Kind regards
Andreas.
-- System Information:
Debian Release: 11.0
APT prefers testing
APT policy: (501, 'testing'), (50, 'buildd-unstable'), (50, 'unstable'), (5, 'experimental'), (1, 'buildd-experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-8-amd64 (SMP w/4 CPU threads)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE:de
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages connman depends on:
ii dbus 1.12.20-2
ii init-system-helpers 1.60
ii iptables 1.8.7-1
ii libc6 2.31-13
ii libdbus-1-3 1.12.20-2
ii libglib2.0-0 2.68.4-1
ii libgnutls30 3.7.1-5
ii libreadline8 8.1-1
ii libxtables12 1.8.7-1
ii lsb-base 11.1.0
Versions of packages connman recommends:
pn bluez <none>
pn ofono <none>
ii wpasupplicant 2:2.9.0-21
Versions of packages connman suggests:
pn connman-vpn <none>
Andreas Tille
Sep 22, 2021, 8:40:03 AM9/22/21
to
Hi,
I'd like to draw the attention of debian-devel to the problem below
(reported ad bug #994875) which breaks certain systems on upgrades.
As I described in bug #988696 which boils down to my last message to
this bug report where I wrote "No idea how to configure network easily
after fresh lxde install." This means: Even an experienced user like
me does not obviously find easy access to a very important feature of a
fresh installation to login to a network.
My reason to bring this up on debian devel is that I have the feeling
that while we provide lots of different desktops in dedicated images the
general QA how useful these might be is left to the maintainers of this
desktop who probably have a focussed view and do not realise what
hurdles newcomers might need to take.
My other point is that we here have another case where the freedom of
choice of tools to use leads to non-default behaviour. I simply assumed
that network-manager would be some kind of default and if it would be
used in lxde task those two problems would not have happened. So my
suggestion is to propose some set of default tools for every desktop
environment we are providing and network configuration should be part of
it. (I admit I also had trouble with wicd which until some point of
time was installed as default with xfce4 installer media - no idea
whether this is the case any more - my arguing would be the same here.)
Kind regards
Andreas.
PS: I also CCed debian-desktop list. If you feel the discussion
should happen there please CC me since I'm not subscribed to
that list.
On Wed, Sep 22, 2021 at 01:09:17PM +0200, Andreas Tille wrote:
> Package: connman
> Version: 1.36-2.2
> Severity: important
>
--
http://fam-tille.de
I'd like to draw the attention of debian-devel to the problem below
(reported ad bug #994875) which breaks certain systems on upgrades.
As I described in bug #988696 which boils down to my last message to
this bug report where I wrote "No idea how to configure network easily
after fresh lxde install." This means: Even an experienced user like
me does not obviously find easy access to a very important feature of a
fresh installation to login to a network.
My reason to bring this up on debian devel is that I have the feeling
that while we provide lots of different desktops in dedicated images the
general QA how useful these might be is left to the maintainers of this
desktop who probably have a focussed view and do not realise what
hurdles newcomers might need to take.
My other point is that we here have another case where the freedom of
choice of tools to use leads to non-default behaviour. I simply assumed
that network-manager would be some kind of default and if it would be
used in lxde task those two problems would not have happened. So my
suggestion is to propose some set of default tools for every desktop
environment we are providing and network configuration should be part of
it. (I admit I also had trouble with wicd which until some point of
time was installed as default with xfce4 installer media - no idea
whether this is the case any more - my arguing would be the same here.)
Kind regards
Andreas.
PS: I also CCed debian-desktop list. If you feel the discussion
should happen there please CC me since I'm not subscribed to
that list.
On Wed, Sep 22, 2021 at 01:09:17PM +0200, Andreas Tille wrote:
> Package: connman
> Version: 1.36-2.2
> Severity: important
>
http://fam-tille.de
Andreas Tille
Sep 23, 2021, 1:40:02 AM9/23/21
to
On Wed, Sep 22, 2021 at 10:21:10PM +0200, Ervin Dine wrote:
> I have not had any problems with conman in my LXDE Debian 11 install
> but if I may give my suggestion, gnome-network-manager works fine with
> LXDE and it has more features. Why not bundle that instead of conman?
> Conman does not even have an icon in the status bar where you can
> toggle wifi on and off or choose another connection.
The missing icon in the status bar triggered bug #988696. I personally
consider this very unfriendly to new users.
Kind regards
Andreas.
--
http://fam-tille.de
> I have not had any problems with conman in my LXDE Debian 11 install
> but if I may give my suggestion, gnome-network-manager works fine with
> LXDE and it has more features. Why not bundle that instead of conman?
> Conman does not even have an icon in the status bar where you can
> toggle wifi on and off or choose another connection.
The missing icon in the status bar triggered bug #988696. I personally
consider this very unfriendly to new users.
Kind regards
Andreas.
--
http://fam-tille.de
Holger Wansing
Sep 23, 2021, 2:20:02 PM9/23/21
to
Hi,
Andreas Tille <and...@fam-tille.de> wrote (Thu, 23 Sep 2021 07:20:57 +0200):
> On Wed, Sep 22, 2021 at 10:21:10PM +0200, Ervin Dine wrote:
> > I have not had any problems with conman in my LXDE Debian 11 install
> > but if I may give my suggestion, gnome-network-manager works fine with
> > LXDE and it has more features. Why not bundle that instead of conman?
> > Conman does not even have an icon in the status bar where you can
> > toggle wifi on and off or choose another connection.
LXDE is one of the light-weighted desktops, and LXDE is not Gnome.
So, if you add gnome-network-manager to the LXDE task, how much of Gnome will
be pulled in via dependencies?
This might be an argument pro connman.
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 (the whole LXDE system having
3,4 GB of disk space used).
I guess this would be worth it.
What do others think? LXDE people?
>
> The missing icon in the status bar triggered bug #988696. I personally
> consider this very unfriendly to new users.
Holger
--
Holger Wansing <hwan...@mailbox.org>
PGP-Fingerprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
Andreas Tille <and...@fam-tille.de> wrote (Thu, 23 Sep 2021 07:20:57 +0200):
> On Wed, Sep 22, 2021 at 10:21:10PM +0200, Ervin Dine wrote:
> > I have not had any problems with conman in my LXDE Debian 11 install
> > but if I may give my suggestion, gnome-network-manager works fine with
> > LXDE and it has more features. Why not bundle that instead of conman?
> > Conman does not even have an icon in the status bar where you can
> > toggle wifi on and off or choose another connection.
So, if you add gnome-network-manager to the LXDE task, how much of Gnome will
be pulled in via dependencies?
This might be an argument pro connman.
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 (the whole LXDE system having
3,4 GB of disk space used).
I guess this would be worth it.
What do others think? LXDE people?
>
> The missing icon in the status bar triggered bug #988696. I personally
> consider this very unfriendly to new users.
--
Holger Wansing <hwan...@mailbox.org>
PGP-Fingerprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
Andreas Tille
Sep 23, 2021, 3:30:03 PM9/23/21
to
Hi,
On Thu, Sep 23, 2021 at 08:17:37PM +0200, Holger Wansing wrote:
>
> LXDE is one of the light-weighted desktops, and LXDE is not Gnome.
Sure. That was the reason why I had choosen this as desktop for quite some
old hardware.
> So, if you add gnome-network-manager to the LXDE task, how much of Gnome will
> be pulled in via dependencies?
> This might be an argument pro connman.
>From my point of view it is bearable.
> 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 (the whole LXDE system having
> 3,4 GB of disk space used).
I'm more about memory usage than disk space usage. IMHO 39MB for something
that works in contrast to saving space that is hard to use or even might
break a system under some circumstances is a sensible tradeof.
> I guess this would be worth it.
I agree here (may be removing connman saves some extra space again (probably
not much).
> What do others think? LXDE people?
On Thu, Sep 23, 2021 at 08:17:37PM +0200, Holger Wansing wrote:
>
> LXDE is one of the light-weighted desktops, and LXDE is not Gnome.
old hardware.
> So, if you add gnome-network-manager to the LXDE task, how much of Gnome will
> be pulled in via dependencies?
> This might be an argument pro connman.
> 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 (the whole LXDE system having
> 3,4 GB of disk space used).
that works in contrast to saving space that is hard to use or even might
break a system under some circumstances is a sensible tradeof.
> I guess this would be worth it.
not much).
> What do others think? LXDE people?
Jaycee Santos
Sep 23, 2021, 4:00:02 PM9/23/21
to
On Wed, Sep 22, 2021 at 10:21:10PM +0200, Ervin Dine wrote:
> I have not had any problems with conman in my LXDE Debian 11 install
> but if I may give my suggestion, gnome-network-manager works fine with
> LXDE and it has more features. Why not bundle that instead of conman?
> Conman does not even have an icon in the status bar where you can
> toggle wifi on and off or choose another connection.
Is there a reason why to choose gnome-network-manager over something like
> I have not had any problems with conman in my LXDE Debian 11 install
> but if I may give my suggestion, gnome-network-manager works fine with
> LXDE and it has more features. Why not bundle that instead of conman?
> Conman does not even have an icon in the status bar where you can
> toggle wifi on and off or choose another connection.
nm-tray for LXDE?
Jaycee
Michael Biebl
Sep 23, 2021, 4:10:02 PM9/23/21
to
Am 23.09.21 um 21:35 schrieb Jaycee Santos:
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)
(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)
Jaycee Santos
Sep 23, 2021, 5:10:04 PM9/23/21
to
On Thursday, September 23rd, 2021 at 1:05 PM, Michael Biebl <bi...@debian.org> wrote:
> Am 23.09.21 um 21:35 schrieb Jaycee Santos:
> 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.
> > 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)
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.
Apparently, I was already using it.
Jaycee
Holger Wansing
Sep 25, 2021, 4:10:03 PM9/25/21
to
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 ]
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 <hwan...@mailbox.org> 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,
Control: tags -1 + patch
[ Returning back to #988696 as the correct bug for this issue; dropping 994875 from CC ]
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 <hwan...@mailbox.org> 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,
Michael Biebl
Sep 25, 2021, 4:20:03 PM9/25/21
to
Am 25.09.21 um 22:05 schrieb Holger Wansing:
- 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.
> 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 <jlsa...@protonmail.com> wrote (Thu, 23 Sep 2021 20:42:05 +0000):
>> On Thursday, September 23rd, 2021 at 1:05 PM, Michael Biebl <bi...@debian.org> 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:
> Control: tags -1 + patch
>
>
> [ Returning back to #988696 as the correct bug for this issue; dropping 994875 from CC ]
>
> Jaycee Santos <jlsa...@protonmail.com> wrote (Thu, 23 Sep 2021 20:42:05 +0000):
>> On Thursday, September 23rd, 2021 at 1:05 PM, Michael Biebl <bi...@debian.org> 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.
- 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.
Holger Wansing
Sep 25, 2021, 4:40:02 PM9/25/21
to
Hi,
Michael Biebl <bi...@debian.org> wrote (Sat, 25 Sep 2021 22:17:48 +0200):
> Am 25.09.21 um 22:05 schrieb Holger Wansing:
is no problem... ?
Holger
Michael Biebl <bi...@debian.org> 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
>
>
> 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.
is no problem... ?
Holger
Jonas Smedegaard
Sep 25, 2021, 5:40:02 PM9/25/21
to
Quoting Holger Wansing (2021-09-25 22:30:20)
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
> Hi,
>
> Michael Biebl <bi...@debian.org> 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.
>
> Michael Biebl <bi...@debian.org> 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... ?
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
Michael Biebl
Sep 25, 2021, 7:10:03 PM9/25/21
to
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
> 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
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
Andreas Tille
Sep 26, 2021, 2:20:02 AM9/26/21
to
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.
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.
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.
this sounds good.
0 new messages