Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #209269 > unrolled thread

Re: lightweight wifi UI (Was: Insidious systemd)

Back to article view | Back to linux.debian.user

Contents

  Re: lightweight wifi UI (Was: Insidious systemd) bw <bwtnguy@yahoo.com> - 2019-05-28 03:20 +0200
    Re: lightweight wifi UI (Was: Insidious systemd) Patrick Bartek <nemommxiv@gmail.com> - 2019-05-28 16:30 +0200
      Re: lightweight wifi UI (Was: Insidious systemd) Reco <recoverym4n@enotuniq.net> - 2019-05-28 18:20 +0200
        Re: lightweight wifi UI (Was: Insidious systemd) Patrick Bartek <nemommxiv@gmail.com> - 2019-05-28 19:10 +0200
          Re: lightweight wifi UI (Was: Insidious systemd) Reco <recoverym4n@enotuniq.net> - 2019-05-28 20:00 +0200
            Re: lightweight wifi UI (Was: Insidious systemd) Patrick Bartek <nemommxiv@gmail.com> - 2019-05-28 20:40 +0200
              Re: lightweight wifi UI (Was: Insidious systemd) Vincent Lefevre <vincent@vinc17.net> - 2019-05-29 18:10 +0200
                Re: lightweight wifi UI (Was: Insidious systemd) Reco <recoverym4n@enotuniq.net> - 2019-05-29 20:10 +0200
                  Re: lightweight wifi UI (Was: Insidious systemd) Vincent Lefevre <vincent@vinc17.net> - 2019-06-01 15:00 +0200
                    Re: lightweight wifi UI (Was: Insidious systemd) Patrick Bartek <nemommxiv@gmail.com> - 2019-06-02 06:10 +0200

#209269 — Re: lightweight wifi UI (Was: Insidious systemd)

In-Reply-To: <20190527163821.6e4b5d95@debian9>

...
>Based on my past experiences and research with systemd, I now
>always have do simulated installs with everything just to be sure
>nothing untoward happens.  The Subject Title was appropriate.

Patrick, I've seen some baloney in my day, but that prose takes the cake.
I think you're full of crap, but you could prove me wrong sort of 
something like this:

$ apt -s install sysvinit-core wicd
NOTE: This is only a simulation!
      apt needs root privileges for real execution.
      Keep also in mind that locking is deactivated,
      so don't depend on the relevance to the real current situation!
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following additional packages will be installed:
  cgmanager initscripts insserv libcgmanager0 libglade2-0 libnih-dbus1 
libnih1 net-tools
  python-dbus python-gi python-glade2 python-gobject python-wicd startpar 
systemd-shim
  sysv-rc wicd-daemon wicd-gtk
Suggested packages:
  bootchart2 python-dbus-dbg python-dbus-doc python-gi-cairo 
python-gtk2-doc pm-utils bum
  bootlogd
Recommended packages:
  gksu python-notify
The following packages will be REMOVED:
  systemd-sysv
The following NEW packages will be installed:
  cgmanager initscripts insserv libcgmanager0 libglade2-0 libnih-dbus1 
libnih1 net-tools
  python-dbus python-gi python-glade2 python-gobject python-wicd startpar 
systemd-shim
  sysv-rc sysvinit-core wicd wicd-daemon wicd-gtk
0 upgraded, 20 newly installed, 1 to remove and 0 not upgraded.

$ apt policy
Package files:
 100 /var/lib/dpkg/status
     release a=now
 500 http://security.debian.org/debian-security stretch/updates/main amd64 
Packages
     release 
v=9,o=Debian,a=stable,n=stretch,l=Debian-Security,c=main,b=amd64
     origin security.debian.org
 500 http://http.us.debian.org/debian stretch-updates/main amd64 Packages
     release 
o=Debian,a=stable-updates,n=stretch-updates,l=Debian,c=main,b=amd64
     origin http.us.debian.org
 500 http://http.us.debian.org/debian stretch/main amd64 Packages
     release v=9.9,o=Debian,a=stable,n=stretch,l=Debian,c=main,b=amd64
     origin http.us.debian.org
Pinned packages:

[toc] | [next] | [standalone]

#209314

On Mon, 27 May 2019 21:00:36 -0400 (EDT)
bw <bwtnguy@yahoo.com> wrote:

> In-Reply-To: <20190527163821.6e4b5d95@debian9>
> 
> ...
> >Based on my past experiences and research with systemd, I now
> >always have do simulated installs with everything just to be sure
> >nothing untoward happens.  The Subject Title was appropriate.  
> 
> Patrick, I've seen some baloney in my day, but that prose takes the cake.
> I think you're full of crap, but you could prove me wrong sort of 
> something like this:
> 
> $ apt -s install sysvinit-core wicd
> [snip]

Unapplicable in my case: sysvinit conversion done a year ago.

For the Doubting Thomas that your are, the output of my simulated
install -- the salient portions I spoke of highlighted.

B

******************************

root@debian9:/home/patrick# apt -s install wicd
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following additional packages will be installed:
  dbus-user-session gconf2 gcr gksu gnome-keyring libgck-1-0
libgcr-3-common libgcr-base-3-1 libgcr-ui-3-1 libgksu2-0
libgnome-keyring-common libgnome-keyring0 libgtop-2.0-10
libgtop2-common libpam-gnome-keyring net-tools p11-kit p11-kit-modules
pinentry-gnome3 python-gobject python-notify python-wicd rfkill
systemd-sysv wicd-daemon wicd-gtk wireless-tools
 ^^^^^^^^^

Suggested packages:
  gconf-defaults-service pinentry-doc ethtool pm-utils

The following packages will be REMOVED:
  sysvinit-core
     ^^^^^^^^
The following NEW packages will be installed:
  dbus-user-session gconf2 gcr gksu gnome-keyring libgck-1-0
libgcr-3-common libgcr-base-3-1 libgcr-ui-3-1 libgksu2-0
libgnome-keyring-common libgnome-keyring0 libgtop-2.0-10
libgtop2-common libpam-gnome-keyring net-tools p11-kit p11-kit-modules
pinentry-gnome3 python-gobject python-notify python-wicd rfkill
systemd-sysv wicd wicd-daemon wicd-gtk wireless-tools
 ^^^^^^^^

0 upgraded, 28 newly installed, 1 to remove and 0 not upgraded.

Remv sysvinit-core [2.88dsf-59.9] [init:amd64 ]
        ^^^^^^^^

Inst systemd-sysv (232-25+deb9u11 Debian:9.9/stable,Debian-Security:9/stable [amd64])
      ^^^^^^^^^

Inst python-gobject (3.22.0-2 Debian:9.9/stable [all])
Inst net-tools (1.60+git20161116.90da8a0-1 Debian:9.9/stable [amd64])
Inst python-wicd (1.7.4+tb2-5~deb9u1 Debian:9.9/stable [all])
Inst wireless-tools (30~pre9-12+b1 Debian:9.9/stable [amd64])
Inst wicd-daemon (1.7.4+tb2-5~deb9u1 Debian:9.9/stable [all])
Inst dbus-user-session (1.10.26-0+deb9u1 Debian:9.9/stable [all])
Inst gconf2 (3.2.6-4+b1 Debian:9.9/stable [amd64])
Inst libgck-1-0 (3.20.0-5.1 Debian:9.9/stable [amd64])
Inst libgcr-3-common (3.20.0-5.1 Debian:9.9/stable [all])
Inst libgcr-base-3-1 (3.20.0-5.1 Debian:9.9/stable [amd64])
Inst libgcr-ui-3-1 (3.20.0-5.1 Debian:9.9/stable [amd64])
Inst gcr (3.20.0-5.1 Debian:9.9/stable [amd64])
Inst libgnome-keyring-common (3.12.0-1 Debian:9.9/stable [all])
Inst libgnome-keyring0 (3.12.0-1+b2 Debian:9.9/stable [amd64])
Inst libgtop2-common (2.34.2-1 Debian:9.9/stable [all])
Inst libgtop-2.0-10 (2.34.2-1 Debian:9.9/stable [amd64])
Inst libgksu2-0 (2.0.13~pre1-9+b1 Debian:9.9/stable [amd64])
Inst gksu (2.0.2-9+b1 Debian:9.9/stable [amd64])
Inst p11-kit-modules (0.23.3-2 Debian:9.9/stable [amd64])
Inst p11-kit (0.23.3-2 Debian:9.9/stable [amd64])
Inst pinentry-gnome3 (1.0.0-2 Debian:9.9/stable [amd64])
Inst gnome-keyring (3.20.0-3 Debian:9.9/stable [amd64])
Inst libpam-gnome-keyring (3.20.0-3 Debian:9.9/stable [amd64])
Inst python-notify (0.1.1-4 Debian:9.9/stable [amd64])
Inst rfkill (0.5-1+b1 Debian:9.9/stable [amd64])
Inst wicd-gtk (1.7.4+tb2-5~deb9u1 Debian:9.9/stable [all])
Inst wicd (1.7.4+tb2-5~deb9u1 Debian:9.9/stable [all])
Conf systemd-sysv (232-25+deb9u11 Debian:9.9/stable,
Debian-Security:9/stable [amd64]) Conf python-gobject (3.22.0-2
Debian:9.9/stable [all]) Conf net-tools (1.60+git20161116.90da8a0-1
Debian:9.9/stable [amd64]) Conf python-wicd (1.7.4+tb2-5~deb9u1
Debian:9.9/stable [all]) Conf wireless-tools (30~pre9-12+b1
Debian:9.9/stable [amd64]) Conf wicd-daemon (1.7.4+tb2-5~deb9u1
Debian:9.9/stable [all]) Conf dbus-user-session (1.10.26-0+deb9u1
Debian:9.9/stable [all]) Conf gconf2 (3.2.6-4+b1 Debian:9.9/stable
[amd64]) Conf libgck-1-0 (3.20.0-5.1 Debian:9.9/stable [amd64])
Conf libgcr-3-common (3.20.0-5.1 Debian:9.9/stable [all])
Conf libgcr-base-3-1 (3.20.0-5.1 Debian:9.9/stable [amd64])
Conf libgcr-ui-3-1 (3.20.0-5.1 Debian:9.9/stable [amd64])
Conf gcr (3.20.0-5.1 Debian:9.9/stable [amd64])
Conf libgnome-keyring-common (3.12.0-1 Debian:9.9/stable [all])
Conf libgnome-keyring0 (3.12.0-1+b2 Debian:9.9/stable [amd64])
Conf libgtop2-common (2.34.2-1 Debian:9.9/stable [all])Conf
gnome-keyring (3.20.0-3 Debian:9.9/stable [amd64]) Conf
libpam-gnome-keyring (3.20.0-3 Debian:9.9/stable [amd64]) Conf
python-notify (0.1.1-4 Debian:9.9/stable [amd64]) Conf rfkill (0.5-1+b1
Debian:9.9/stable [amd64]) Conf wicd-gtk (1.7.4+tb2-5~deb9u1
Debian:9.9/stable [all]) Conf wicd (1.7.4+tb2-5~deb9u1
Debian:9.9/stable [all]) Conf libgtop-2.0-10 (2.34.2-1
Debian:9.9/stable [amd64]) Conf libgksu2-0 (2.0.13~pre1-9+b1
Debian:9.9/stable [amd64]) Conf gksu (2.0.2-9+b1 Debian:9.9/stable
[amd64]) Conf p11-kit-modules (0.23.3-2 Debian:9.9/stable [amd64])
Conf p11-kit (0.23.3-2 Debian:9.9/stable [amd64])
Conf pinentry-gnome3 (1.0.0-2 Debian:9.9/stable [amd64])

********************************

[toc] | [prev] | [next] | [standalone]

#209323

	Hi.

On Tue, May 28, 2019 at 07:10:22AM -0700, Patrick Bartek wrote:
> On Mon, 27 May 2019 21:00:36 -0400 (EDT)
> bw <bwtnguy@yahoo.com> wrote:
> 
> > In-Reply-To: <20190527163821.6e4b5d95@debian9>
> > 
> > ...
> > >Based on my past experiences and research with systemd, I now
> > >always have do simulated installs with everything just to be sure
> > >nothing untoward happens.  The Subject Title was appropriate.  
> > 
> > Patrick, I've seen some baloney in my day, but that prose takes the cake.
> > I think you're full of crap, but you could prove me wrong sort of 
> > something like this:
> > 
> > $ apt -s install sysvinit-core wicd
> > [snip]
> 
> Unapplicable in my case: sysvinit conversion done a year ago.
> 
> For the Doubting Thomas that your are, the output of my simulated
> install -- the salient portions I spoke of highlighted.
> 
> B
> 
> root@debian9:/home/patrick# apt -s install wicd

Try this:

# apt install wicd -s -o APT::Install-Recommends="0"

wicd by itself does not require systemd, but it recommends gksu. gksu,
which is kinda-sorta part of GNOME, on the other hand - does.

Reco

[toc] | [prev] | [next] | [standalone]

#209329

On Tue, 28 May 2019 18:56:44 +0300
Reco <recoverym4n@enotuniq.net> wrote:

> 	Hi.
> 
> On Tue, May 28, 2019 at 07:10:22AM -0700, Patrick Bartek wrote:
> > On Mon, 27 May 2019 21:00:36 -0400 (EDT)
> > bw <bwtnguy@yahoo.com> wrote:
> >   
> > > In-Reply-To: <20190527163821.6e4b5d95@debian9>
> > > 
> > > ...  
> > > >Based on my past experiences and research with systemd, I now
> > > >always have do simulated installs with everything just to be sure
> > > >nothing untoward happens.  The Subject Title was appropriate.    
> > > 
> > > Patrick, I've seen some baloney in my day, but that prose takes the cake.
> > > I think you're full of crap, but you could prove me wrong sort of 
> > > something like this:
> > > 
> > > $ apt -s install sysvinit-core wicd
> > > [snip]  
> > 
> > Unapplicable in my case: sysvinit conversion done a year ago.
> > 
> > For the Doubting Thomas that your are, the output of my simulated
> > install -- the salient portions I spoke of highlighted.
> > 
> > B
> > 
> > root@debian9:/home/patrick# apt -s install wicd  
> 
> Try this:
> 
> # apt install wicd -s -o APT::Install-Recommends="0"

apt/apt-get already by default set NOT to install Recommends, only
dependencies.  And I check before installing anything just to be sure.

I've abandoned wicd and am considering other utilities, wifi-radar
being toward the top of the list.  I may just go commandline since I
only have to configure this home-based box once for wifi.

> wicd by itself does not require systemd, but it recommends gksu. gksu,
> which is kinda-sorta part of GNOME, on the other hand - does.

Due to GNOME's systemd dependency, I avoid with a passion any app,
utility, etc. that is even remotely related to GNOME.

Thanks for your advice.

B 

[toc] | [prev] | [next] | [standalone]

#209337

On Tue, May 28, 2019 at 09:49:45AM -0700, Patrick Bartek wrote:
> On Tue, 28 May 2019 18:56:44 +0300
> Reco <recoverym4n@enotuniq.net> wrote:
> 
> > 	Hi.
> > 
> > On Tue, May 28, 2019 at 07:10:22AM -0700, Patrick Bartek wrote:
> > > On Mon, 27 May 2019 21:00:36 -0400 (EDT)
> > > bw <bwtnguy@yahoo.com> wrote:
> > >   
> > > > In-Reply-To: <20190527163821.6e4b5d95@debian9>
> > > > 
> > > > ...  
> > > > >Based on my past experiences and research with systemd, I now
> > > > >always have do simulated installs with everything just to be sure
> > > > >nothing untoward happens.  The Subject Title was appropriate.    
> > > > 
> > > > Patrick, I've seen some baloney in my day, but that prose takes the cake.
> > > > I think you're full of crap, but you could prove me wrong sort of 
> > > > something like this:
> > > > 
> > > > $ apt -s install sysvinit-core wicd
> > > > [snip]  
> > > 
> > > Unapplicable in my case: sysvinit conversion done a year ago.
> > > 
> > > For the Doubting Thomas that your are, the output of my simulated
> > > install -- the salient portions I spoke of highlighted.
> > > 
> > > B
> > > 
> > > root@debian9:/home/patrick# apt -s install wicd  
> > 
> > Try this:
> > 
> > # apt install wicd -s -o APT::Install-Recommends="0"
> 
> apt/apt-get already by default set NOT to install Recommends, only
> dependencies.  And I check before installing anything just to be sure.

Yet your apt tries to install gksu, and mine does not.


> I've abandoned wicd and am considering other utilities, wifi-radar
> being toward the top of the list.  I may just go commandline since I
> only have to configure this home-based box once for wifi.

wpa_cli and an appropriate wpa_supplicant.conf is more than enough for
my laptop needs. Personally I see any GUI to WiFi as redundant
(aircrack-ng/kismet being an exception), but I suggest you to try
dhcpcd-gtk (GTK2) or wpagui (QT).

Both Notwork Manager and wicd try to do too many things, WiFi being one
of them. Both try to hide the fact that all that you really need is
something for L2 (wpa-supplicant or iwd) and for L3 (any dhcp client).

Both dhcpcd-gtk and wpagui simply try to provide a frontend to
wpa_supplicant.conf without trying to replace your whole network
configuration.

Reco

[toc] | [prev] | [next] | [standalone]

#209342

On Tue, 28 May 2019 20:39:53 +0300
Reco <recoverym4n@enotuniq.net> wrote:

> On Tue, May 28, 2019 at 09:49:45AM -0700, Patrick Bartek wrote:
> > On Tue, 28 May 2019 18:56:44 +0300
> > Reco <recoverym4n@enotuniq.net> wrote:
> >   
> > > 	Hi.
> > > 
> > > On Tue, May 28, 2019 at 07:10:22AM -0700, Patrick Bartek wrote:  
> > > > On Mon, 27 May 2019 21:00:36 -0400 (EDT)
> > > > bw <bwtnguy@yahoo.com> wrote:
> > > >     
> > > > > In-Reply-To: <20190527163821.6e4b5d95@debian9>
> > > > > 
> > > > > ...    
> > > > > >Based on my past experiences and research with systemd, I now
> > > > > >always have do simulated installs with everything just to be sure
> > > > > >nothing untoward happens.  The Subject Title was appropriate.      
> > > > > 
> > > > > Patrick, I've seen some baloney in my day, but that prose takes the cake.
> > > > > I think you're full of crap, but you could prove me wrong sort of 
> > > > > something like this:
> > > > > 
> > > > > $ apt -s install sysvinit-core wicd
> > > > > [snip]    
> > > > 
> > > > Unapplicable in my case: sysvinit conversion done a year ago.
> > > > 
> > > > For the Doubting Thomas that your are, the output of my simulated
> > > > install -- the salient portions I spoke of highlighted.
> > > > 
> > > > B
> > > > 
> > > > root@debian9:/home/patrick# apt -s install wicd    
> > > 
> > > Try this:
> > > 
> > > # apt install wicd -s -o APT::Install-Recommends="0"  
> > 
> > apt/apt-get already by default set NOT to install Recommends, only
> > dependencies.  And I check before installing anything just to be sure.  
> 
> Yet your apt tries to install gksu, and mine does not.

I'll check.  It could be a dependency of a wicd dependency.  Although,
it's academic: I won't be using wicd.

> 
> > I've abandoned wicd and am considering other utilities, wifi-radar
> > being toward the top of the list.  I may just go commandline since I
> > only have to configure this home-based box once for wifi.  
> 
> wpa_cli and an appropriate wpa_supplicant.conf is more than enough for
> my laptop needs. Personally I see any GUI to WiFi as redundant
> (aircrack-ng/kismet being an exception), but I suggest you to try
> dhcpcd-gtk (GTK2) or wpagui (QT).

Thanks. I'm getting a new laptop this year which I haven't needed in a
long time.  And I'll install a customized window manager only system on
it like I have on the desk box. So, I haven't kept up with all the wifi
utilities available.

> Both Notwork Manager and wicd try to do too many things, WiFi being one
> of them. Both try to hide the fact that all that you really need is
> something for L2 (wpa-supplicant or iwd) and for L3 (any dhcp client).

Good to know.

> Both dhcpcd-gtk and wpagui simply try to provide a frontend to
> wpa_supplicant.conf without trying to replace your whole network
> configuration.
>

Thanks.  I check it out.

B 

[toc] | [prev] | [next] | [standalone]

#209380

On 2019-05-28 11:18:39 -0700, Patrick Bartek wrote:
> On Tue, 28 May 2019 20:39:53 +0300
> Reco <recoverym4n@enotuniq.net> wrote:
> 
> > On Tue, May 28, 2019 at 09:49:45AM -0700, Patrick Bartek wrote:
> > > On Tue, 28 May 2019 18:56:44 +0300
> > > Reco <recoverym4n@enotuniq.net> wrote:
> > > apt/apt-get already by default set NOT to install Recommends, only
> > > dependencies.  And I check before installing anything just to be sure.  
> > 
> > Yet your apt tries to install gksu, and mine does not.
> 
> I'll check.  It could be a dependency of a wicd dependency.

No, there isn't any dependency, even recursively:

ypig:~> apt install -s wicd
[...]
The following additional packages will be installed:
  python-glade2 python-notify python-wicd rfkill wicd-daemon wicd-gtk
  wireless-tools
[...]

and I don't have gksu already installed:

ypig:~> dpkg -s gksu
dpkg-query: package 'gksu' is not installed and no information is available
Use dpkg --info (= dpkg-deb --info) to examine archive files.

-- 
Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

[toc] | [prev] | [next] | [standalone]

#209384

	Hi.

On Wed, May 29, 2019 at 05:39:05PM +0200, Vincent Lefevre wrote:
> On 2019-05-28 11:18:39 -0700, Patrick Bartek wrote:
> > On Tue, 28 May 2019 20:39:53 +0300
> > Reco <recoverym4n@enotuniq.net> wrote:
> > 
> > > On Tue, May 28, 2019 at 09:49:45AM -0700, Patrick Bartek wrote:
> > > > On Tue, 28 May 2019 18:56:44 +0300
> > > > Reco <recoverym4n@enotuniq.net> wrote:
> > > > apt/apt-get already by default set NOT to install Recommends, only
> > > > dependencies.  And I check before installing anything just to be sure.  
> > > 
> > > Yet your apt tries to install gksu, and mine does not.
> > 
> > I'll check.  It could be a dependency of a wicd dependency.
> 
> No, there isn't any dependency, even recursively:
> 
> ypig:~> apt install -s wicd
> [...]
> The following additional packages will be installed:
>   python-glade2 python-notify python-wicd rfkill wicd-daemon wicd-gtk
>   wireless-tools
> [...]

$ apt-cache show wicd-gtk | grep Recommends
Recommends: gksu, python-notify

Things might be different in buster or sid, of course. This is stretch.

Reco

[toc] | [prev] | [next] | [standalone]

#209493

On 2019-05-29 20:47:06 +0300, Reco wrote:
> 	Hi.
> 
> On Wed, May 29, 2019 at 05:39:05PM +0200, Vincent Lefevre wrote:
> > On 2019-05-28 11:18:39 -0700, Patrick Bartek wrote:
> > > On Tue, 28 May 2019 20:39:53 +0300
> > > Reco <recoverym4n@enotuniq.net> wrote:
> > > 
> > > > On Tue, May 28, 2019 at 09:49:45AM -0700, Patrick Bartek wrote:
> > > > > On Tue, 28 May 2019 18:56:44 +0300
> > > > > Reco <recoverym4n@enotuniq.net> wrote:
> > > > > apt/apt-get already by default set NOT to install Recommends, only
> > > > > dependencies.  And I check before installing anything just to be sure.  
> > > > 
> > > > Yet your apt tries to install gksu, and mine does not.
> > > 
> > > I'll check.  It could be a dependency of a wicd dependency.
> > 
> > No, there isn't any dependency, even recursively:
> > 
> > ypig:~> apt install -s wicd
> > [...]
> > The following additional packages will be installed:
> >   python-glade2 python-notify python-wicd rfkill wicd-daemon wicd-gtk
> >   wireless-tools
> > [...]
> 
> $ apt-cache show wicd-gtk | grep Recommends
> Recommends: gksu, python-notify
> 
> Things might be different in buster or sid, of course. This is stretch.

Yes, this has changed:

ypig:~> apt-cache show wicd-gtk | grep Recommends
Recommends: policykit-1 | menu | kde-runtime, python-notify
Recommends: gksu, python-notify

But anyway, this was just a Recommends, and the OP had apt configured
not to install Recommends by default.

-- 
Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

[toc] | [prev] | [next] | [standalone]

#209516

On Sat, 1 Jun 2019 14:30:38 +0200
Vincent Lefevre <vincent@vinc17.net> wrote:

> On 2019-05-29 20:47:06 +0300, Reco wrote:
> > 	Hi.
> > 
> > On Wed, May 29, 2019 at 05:39:05PM +0200, Vincent Lefevre wrote:  
> > > On 2019-05-28 11:18:39 -0700, Patrick Bartek wrote:  
> > > > On Tue, 28 May 2019 20:39:53 +0300
> > > > Reco <recoverym4n@enotuniq.net> wrote:
> > > >   
> > > > > On Tue, May 28, 2019 at 09:49:45AM -0700, Patrick Bartek wrote:  
> > > > > > On Tue, 28 May 2019 18:56:44 +0300
> > > > > > Reco <recoverym4n@enotuniq.net> wrote:
> > > > > > apt/apt-get already by default set NOT to install Recommends, only
> > > > > > dependencies.  And I check before installing anything just to be sure.    
> > > > > 
> > > > > Yet your apt tries to install gksu, and mine does not.  
> > > > 
> > > > I'll check.  It could be a dependency of a wicd dependency.  
> > > 
> > > No, there isn't any dependency, even recursively:
> > >   
> > > ypig:~> apt install -s wicd  
> > > [...]
> > > The following additional packages will be installed:
> > >   python-glade2 python-notify python-wicd rfkill wicd-daemon wicd-gtk
> > >   wireless-tools
> > > [...]  
> > 
> > $ apt-cache show wicd-gtk | grep Recommends
> > Recommends: gksu, python-notify
> > 
> > Things might be different in buster or sid, of course. This is stretch.  
> 
> Yes, this has changed:
> 
> ypig:~> apt-cache show wicd-gtk | grep Recommends  
> Recommends: policykit-1 | menu | kde-runtime, python-notify
> Recommends: gksu, python-notify
> 
> But anyway, this was just a Recommends, and the OP had apt configured
> not to install Recommends by default.

I checked that and some time ago had set Recommends back to install by
default, but had forgotten.  When I initially installed Stretch last
year I had set Recommends not to install as a precaution against
systemd reinstalling itself which it tried to a lot.  That changed
after about a month or so.  After a while since I was having to install
some Recommends by hand anyway as apps were complaining, I set it back.

I apologize for my forgetfulness.

B

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web