Fedora (.rpm package) does not force install specific dependencies

[pgi-jsanchez]

Greetings.

For certain reason, I couldn't connect to the VPN using Fedora 40 on my system, due to a research to find out what happened, for some reason, specific dependencies were not resolved when reinstalled forticlient with the latest version (7.4.0.1636) and testing on a VM, I found that some dependencies were not installed on my system and the rpm package didn't expected to resolve, so I took the list of dependencies using dnf repoquery that matches with forticlient, using dnf install $(cat <listDependencies.txt>), and got my issue solved.

If someone else is dealing with that, here's the list of dependencies that I installed:

Spoiler

alsa-lib-0:1.2.12-1.fc40.x86_64
at-spi2-atk-0:2.52.0-1.fc40.x86_64
at-spi2-core-0:2.52.0-1.fc40.x86_64
atk-0:2.52.0-1.fc40.x86_64
bash-0:5.2.26-3.fc40.x86_64
bzip2-libs-0:1.0.8-18.fc40.x86_64
cairo-0:1.18.0-3.fc40.x86_64
cups-libs-1:2.4.10-3.fc40.x86_64
dbus-libs-1:1.14.10-3.fc40.x86_64
dnf-utils-0:4.8.0-1.fc40.noarch
expat-0:2.6.2-1.fc40.x86_64
fontconfig-0:2.15.0-6.fc40.x86_64
freetype-0:2.13.2-5.fc40.x86_64
gdk-pixbuf2-0:2.42.10-8.fc40.x86_64
glib2-0:2.80.3-1.fc40.x86_64
glibc-0:2.39-22.fc40.i686
glibc-0:2.39-22.fc40.x86_64
gtk2-0:2.24.33-18.fc40.i686
gtk2-0:2.24.33-18.fc40.x86_64
gtk3-0:3.24.43-1.fc40.x86_64
keyutils-0:1.6.3-3.fc40.x86_64
libX11-0:1.8.10-1.fc40.x86_64
libX11-xcb-0:1.8.10-1.fc40.x86_64
libXScrnSaver-0:1.2.4-3.fc40.i686
libXScrnSaver-0:1.2.4-3.fc40.x86_64
libXcomposite-0:0.4.6-3.fc40.i686
libXcomposite-0:0.4.6-3.fc40.x86_64
libXcursor-0:1.2.1-7.fc40.i686
libXcursor-0:1.2.1-7.fc40.x86_64
libXdamage-0:1.1.6-3.fc40.i686
libXdamage-0:1.1.6-3.fc40.x86_64
libXext-0:1.3.6-1.fc40.i686
libXext-0:1.3.6-1.fc40.x86_64
libXfixes-0:6.0.1-3.fc40.i686
libXfixes-0:6.0.1-3.fc40.x86_64
libXi-0:1.8.1-5.fc40.x86_64
libXrandr-0:1.5.4-3.fc40.i686
libXrandr-0:1.5.4-3.fc40.x86_64
libXrender-0:0.9.11-6.fc40.i686
libXrender-0:0.9.11-6.fc40.x86_64
libXtst-0:1.2.5-1.fc40.i686
libXtst-0:1.2.5-1.fc40.x86_64
libdrm-0:2.4.122-1.fc40.x86_64
libgcc-0:14.2.1-1.fc40.x86_64
libnotify-0:0.8.3-3.fc40.x86_64
libsecret-0:0.21.4-2.fc40.i686
libsecret-0:0.21.4-2.fc40.x86_64
libuuid-0:2.40.1-1.fc40.x86_64
libxcb-0:1.17.0-1.fc40.i686
libxcb-0:1.17.0-1.fc40.x86_64
libxcrypt-compat-0:4.4.36-5.fc40.x86_64
libxkbcommon-0:1.6.0-2.fc40.x86_64
mesa-libgbm-0:24.1.5-2.fc40.x86_64
nspr-0:4.35.0-24.fc40.x86_64
nss-0:3.101.0-1.fc40.x86_64
nss-tools-0:3.101.0-1.fc40.x86_64
nss-util-0:3.101.0-1.fc40.x86_64
pango-0:1.54.0-1.fc40.x86_64
polkit-libs-0:124-2.fc40.x86_64
redhat-lsb-core-0:5.0-0.9.20231006git8d00acdc.fc40.i686
redhat-lsb-core-0:5.0-0.9.20231006git8d00acdc.fc40.x86_64
sqlite-libs-0:3.45.1-2.fc40.x86_64
systemd-libs-0:255.10-1.fc40.i686
systemd-libs-0:255.10-1.fc40.x86_64
zlib-ng-compat-0:2.1.7-1.fc40.x86_64

[dominikot]

It really depends on the software — some is well-behaved with missing optional dependencies, while other software just isn't, with weird errors or worse something just not working with no clue as to why.

Generally, if you want this to work, you should suggest that the package maintainer convert those dependencies to weak deps.

You can install the packages with RPM, but this will probably cause DNF to get confused later at some point. It's not worth it in most cases. Is there a particular problem you're trying to solve, or is this just for cleanliness https://mobdro.bio/ ?

[pgi-jsanchez]

The particular issue that i was trying to solve is that forticlient didn't installed propperly, did load but couldn't connect to the VPN, and the only solution was to find out which packages were missing, despite that maybe on the package might manage some of them as weak dependencies, there are some that must be defined as strong dependencies and install them when they are missing or are not updated. Maybe someone else might have a issue like this