New answers tagged

2

Unless the package depends another library update or something that was introduced in a point release, a single build for all of CentOS 7 will suffice. You can see examples of this in the updates repositories. Many packages will use a %dist tag that is el7, but you can also see some that are tagged el7_4. See: http://vault.centos.org/7.4.1708/updates/...


4

From a package developer's perspective CentOS == Red Hat Enterprise Linux (without licensed / copyrighted Red Hat content & logo's and without the enterprise support tiers) So you can use the extensive Red Hat documentation (a nice overview here) Compatibility Within A Major Release One of the core goals of the Red Hat Enterprise Linux family of ...


0

All Centos 7.x are juste minor upgrades, so I don't think you need to make the difference in your rpms. All centos packages are suffixed with el7, not with el7.6 or similar so I think you can do that safely (we are doing it for at least two years already).


0

You can utilize dnf info. Here is an example Bash script to get values and to set as a variable: function dnfinfo() { dnf info "$(echo "${1}" | sed 's/\.rpm$//g')" } function splitname() { eval $( dnfinfo "${1}" | \ grep "^Arch\|^Name\|^Release\|^Version" | \ sort | \ awk -F": " {'print "\""$2"\""'} | \ tr "\n" " " | \ ...


1

Check the proxy settings for subscription-manager in this below file: /etc/rhsm/rhsm.conf Set the correct value for proxy_hostname and proxy_port. If needed fill out the proxy_user and proxy_password lines as well.


0

try this: - name: Installed the rpm files shell: yum localinstall *.rpm -y args: chdir: /tmp/rpm_dir ignore the waring.


Top 50 recent answers are included