While build requirements are indeed not stored in the final RPM (as jsbillings pointed out) dnf was improved over the last years so you can actually query build requirements now.
dnf repoquery --disablerepo=* --enablerepo=*-source --arch=src --whatrequires <provide>
Source: Examples in the DNF Command Reference (at the very end of that section)
The GitLab Runner images are based on either Ubuntu or Alpine Linux. This is stated in the docs:
The following Docker images are available:
gitlab/gitlab-runner:latest based on Ubuntu.
gitlab/gitlab-runner:alpine based on Alpine with much a smaller
footprint (~160/350 MB Ubuntu vs ~45/130 MB Alpine
Both Ubuntu ...
Probably your package Database-devel provides Database-devel. You can check this like this:
rpm -q Database-devel --provides
it should say something like this:
Database-devel = 2.0.0-0
if it says also:
without version number, then this means for rpm and thus for yum that it provides all versions of Database-devel, including version 1.0.0....
The Yum configuration file /etc/yum.conf of the CentOS Docker image contains tsflags=nodocs which stops the documentation from installing.
The Zabbix create.sql.gz file is installed as part of the documentation and this is the reason why it's missing.
To install the create.sql.gz file either comment out the tsflags line in the /etc/yum.conf file or amend ...
You can use yum whatprovides nslookup to see which package delivers it:
~$ yum whatprovides nslookup
Loaded plugins: fastestmirror
Determining fastest mirrors
32:bind-utils-9.11.4-9.P2.el7.x86_64 : Utilities for querying DNS name servers
Repo : base
Filename : /usr/bin/nslookup
32:bind-utils-9.9.4-74.el7_6.2.x86_64 : Utilities ...
In Fedora 31 Server I tried KDE, I tried cinnamon, all in su - user mode. Then I searched and found this post: groupinstall in su - user mode
yum groupinstall "Fedora Workstation" --skip-broken
Used startx an old command I read of. And the Fedora Server is now GUI. Thanks a bunch.
Given the lack of mutual dependencies, which is guaranteed, the following algorithm will yield the minimal set:
for each package in the list, list all of its requirements (rpm -qR foo)
for each package in the requirements, remove it from the list if it’s present
Listing foo’s requirements yields baz (presumably among others), and listing baz’s requirements ...
Removed the three salt-stack repo's which as mentioned caused the issue. Install ran fine after that.
in the folder /etc/yum.repos.d/
Removed the three salt repos
Installed a single repo relating to salt.
ran the install script again and it no longer errors on the packages.
It is working for me at ansible 2.9. The only difference from your playbook is that I have quotes around kernel*:
- name: upgrade all packages, excluding kernel