Re: Who installed package "foo"?

David Wright wrote: > On Mon 02 Nov 2020 at 09:52:53 (+0700), Victor Sudakov wrote: > > Dan Ritter wrote: > > > > > > > > When I want to figure out what package has installed package "foo" as a > > > > dependency, is there a less barbaric method than > > > > > > > > apt-get -s remove foo > > >

Re: Who installed package "foo"?

On Mon 02 Nov 2020 at 09:52:53 (+0700), Victor Sudakov wrote: > Dan Ritter wrote: > > > > > > When I want to figure out what package has installed package "foo" as a > > > dependency, is there a less barbaric method than > > > > > > apt-get -s remove foo > > > > In addition to the other answer

Re: Who installed package "foo"?

Dan Ritter wrote: > > > > When I want to figure out what package has installed package "foo" as a > > dependency, is there a less barbaric method than > > > > apt-get -s remove foo > > In addition to the other answers I see, you probably have a > record of when it happened in /var/log/history.

Re: Who installed package "foo"?

Jean-Philippe MENGUAL wrote: > > > > > > When I want to figure out what package has installed package "foo" as a > > > dependency, is there a less barbaric method than > > > > > > apt-get -s remove foo > > > > > > ? > > or apt-cache rdepends foo I got the impression that it shows all possible

Re: Who installed package "foo"?

Andreas Ronnquist wrote: > >Dear Colleagues, > > > >When I want to figure out what package has installed package "foo" as a > >dependency, is there a less barbaric method than > > > >apt-get -s remove foo > > > >? > > > > There's > > aptitude why [package] > > which should do what you ask. I

Re: why buster doesn't enter sleep mode

On Sun 01 Nov 2020 at 20:49:48 (+), Long Wind wrote: > On Sunday, November 1, 2020, 2:46:28 PM EST, Long Wind > wrote: > > > > tty2 doesn't enter sleep mode after long period of keyboard inactivityby > > sleep mode i mean monitor isn't turned offi believe that sound playing on > > tty3 p

Re: package of cfdisk

On 11/1/20 5:53 PM, gregoire roumache wrote: Hello, I've found multiple bugs while using the command : cfdisk. I've written a report to sub...@bugs.debian.org , however it was rejected because I didn't specify a package (line at the very first line of the mail b

Re: package of cfdisk

On Sun, Nov 01, 2020 at 11:53:18PM +0100, gregoire roumache wrote: > Hello, > > I've found multiple bugs while using the command : cfdisk. I've written a > report to sub...@bugs.debian.org, however it was rejected because I didn't > specify a package (line at the very first line of the mail body).

Re: package of cfdisk

On Sun, Nov 01 2020 at 11:53:18 PM, gregoire roumache wrote: > Hello, > > I've found multiple bugs while using the command : cfdisk. I've written a > report to sub...@bugs.debian.org, however it was rejected because I didn't > specify a package (line at the very first line of the mail body). > Un

package of cfdisk

Hello, I've found multiple bugs while using the command : cfdisk. I've written a report to sub...@bugs.debian.org, however it was rejected because I didn't specify a package (line at the very first line of the mail body). Unfortunately, I couldn't determine what package cfdisk was part of. If you

Re: The .xsession-errors problem

On Sun, Nov 1, 2020, 11:48 AM Teemu Likonen wrote: > * 2020-11-01 11:09:50+01, Anders Andersson wrote: > > > On Mon, Oct 26, 2020 at 5:43 PM Teemu Likonen wrote: > >> From my backups I found an ~/.xsession-errors file of size 111 > >> megabytes. Probably I deleted the file at that point and it s

Re: The .xsession-errors problem

* 2020-11-01 11:09:50+01, Anders Andersson wrote: > On Mon, Oct 26, 2020 at 5:43 PM Teemu Likonen wrote: >> From my backups I found an ~/.xsession-errors file of size 111 >> megabytes. Probably I deleted the file at that point and it started >> grow again. > > Amateur. I found a 24 GB .xsession-e

unable to login

I was getting along quite well with my Debian 10.6 installation when I encountered a strange problem. I have Kde with Plazma installed in Debian and the machine is a dual installation with Windows 10. When starting I selected Debian from Grub, that was normal and went through the startup routine a

Re: Who installed package "foo"?

Victor Sudakov wrote: > Dear Colleagues, > > When I want to figure out what package has installed package "foo" as a > dependency, is there a less barbaric method than > > apt-get -s remove foo In addition to the other answers I see, you probably have a record of when it happened in /var/log/

Re: Who installed package "foo"?

Le 01/11/2020 à 13:35, Andreas Ronnquist a écrit : On Sun, 1 Nov 2020 18:59:16 +0700, Victor Sudakov wrote: Dear Colleagues, When I want to figure out what package has installed package "foo" as a dependency, is there a less barbaric method than apt-get -s remove foo ? There's aptitude w

Re: Who installed package "foo"?

On Sun, 1 Nov 2020 18:59:16 +0700, Victor Sudakov wrote: >Dear Colleagues, > >When I want to figure out what package has installed package "foo" as a >dependency, is there a less barbaric method than > >apt-get -s remove foo > >? > There's aptitude why [package] which should do what you ask.

Who installed package "foo"?

Dear Colleagues, When I want to figure out what package has installed package "foo" as a dependency, is there a less barbaric method than apt-get -s remove foo ? -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN 2:5005/49@fidonet http://vas.tomsk.ru/ signature.asc Description: PGP signature

Re: Mounting a USB device

Many thanks for your email, David. Apologies for any contradictory messages i have posted. My understanding of the automatic mount of USB devices has been rapidly evolving. I have now seen that people have had various problems with usbmount over the years, so I can quite understand why it might n

Re: The .xsession-errors problem

On Mon, Oct 26, 2020 at 5:43 PM Teemu Likonen wrote: > > It seems that ~/.xsession-errors file can still grow to infinity in > size. Sometimes it grows really fast. This is nothing new: we have all > seen it and talked about it. What do you do to maintain this file? > > - Do you just delete it w