On Fri, Oct 20, 2023 at 3:46 PM Fabian Vogt <fvogt@suse.de> wrote:
Hi,
Am Freitag, 20. Oktober 2023, 14:35:40 CEST schrieb Andrei Borzenkov:
On Fri, Oct 20, 2023 at 3:26 PM Thorsten Kukuk <kukuk@suse.de> wrote:
I guess you are implying that containers have no core utilities. That is something I didn't know, and assumed otherwise.
There are base containers, which include coreutils and util-linux, and there is our busybox base container, which only includes busybox and the symlinks for the tools. So both exists, depending on your needs.
Which reminds me. There were multiple reports on forums about zypper selecting busybox as a dependency for some binary (/usr/bin/xxx). My best guess is that zypper simply takes the first package in alphabetical order when several choices exist.
Correct.
Is there any way to mark some packages as preferred *at runtime*? OBS solves it in project config, but it does not help in this case.
Yes, by having some other package that is part of the transaction suggest the non-busybox option. This is already done by patterns-base-base, but this is not always installed and probably also incomplete...
You probably misunderstood the problem. andrei@tumbleweed:~> zypper se --requires /usr/bin/patch Loading repository data... Reading installed packages... S | Name | Summary | Type --+-----------------+------------------------------------+-------- | flatpak-builder | Tool to build flatpaks from source | package | lsb | LSB Fake Package | package andrei@tumbleweed:~> zypper se --provides -x /usr/bin/patch Loading repository data... Reading installed packages... S | Name | Summary | Type --+---------------+---------------------------------+-------- | busybox-patch | Busybox applets replacing patch | package | patch | GNU patch | package andrei@tumbleweed:~> How are you going to ensure that installing flatpak-builder installs "patch" and not "busybox-patch"? By always pre-installing "patch" on every system?