On Sat, Oct 19, 2019 at 06:46:34PM +0200, Linux-Fan wrote: > tomas@tuxteam.de writes: > > >On Sat, Oct 19, 2019 at 02:46:38PM +0200, Étienne Mollier wrote: [...] > >> # apt install sysvinit-core firefox-esr [...] > > > [... it works!] > Hello tomás, > > if I understand the difference between the commands correctly, the > specification of an already-installed package in an install command causes > the packaging system to consider only such operations that leave the listed > packages in place. Yes, that's what (I think) I'm seeing. > I believe the phenomenon you are experiencing might be due to some > `Recommends`-type dependencies (somewhere on the way from `firefox-esr`) > which eventally recommend the installation of systemd. Perhaps. I never went that deep into apt's innards. But, FWIW, I have APT::Install-Recommends no; in /etc/apt/apt.conf.d/95no-recommends -- and apt (apt-get, too) do heed that advice. Whether they still consider Recommends: while reckoning dependency resolution I don't know. But yes, it's a possibility. > If you want to explore the situation interactively, I would suggest > trying the `install firefox-esr` command with `aptitude` instead of > `apt` [...] Well, it's already installed -- and at the end it went well. The most important lesson for me is that I was barking up the wrong tree: that was not a real (indirect) dependency, but just a (for me) non-intuitive decision taken by the dependency resolver. I guess I've to tell the resolver that I do care about sysvinit-core. Cheers -- t
Attachment:
signature.asc
Description: Digital signature