Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-81048

Installation of packages with /bin/ln requirements fails

Linking RHIVOS CVEs to...Migration: Automation ...Sync from "Extern...XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not a Bug
    • Icon: Normal Normal
    • None
    • CentOS Stream 10
    • coreutils
    • None
    • None
    • Assignee, Qa Contact, Doc Contact, AssignedTeam, Watchers, Developer
    • None
    • rhel-base-utils-core
    • ssg_core_services
    • None
    • None
    • None
    • None
    • None
    • x86_64
    • None

      What were you trying to do that didn't work?

      We are trying to install an rpm (IBM TSM / Storage Protect backup client) with a required for /bin/ln via dnf.

      dnf refuses to install the package as nothing provides /bin/ln. rpm install the packages without any issues.

      Source of the package:
      https://public.dhe.ibm.com/storage/tivoli-storage-management/maintenance/client/v8r1/Linux/LinuxX86/BA/v8125/8.1.25.0-TIV-TSMBAC-LinuxX86.tar

      What is the impact of this issue to you?

      We cannot use our automation to install the backup client and must build workarounds with rpm -Uvh instead of using dnf/repos.

      Please provide the package NVR for which the bug is seen:

      Compose CentOS-Stream-10-20250226.0

      dnf-4.20.0-11.el10.noarch
      libdnf-0.73.1-7.el10.x86_64

      How reproducible is this bug?:

      bash-5.2$ sudo dnf install --nogpgcheck ./gskssl64-8.0.55.31.linux.x86_64.rpm ./gskcrypt64-8.0.55.31.linux.x86_64.rpm
      Last metadata expiration check: 1:26:50 ago on Thu 27 Feb 2025 06:59:52 AM CET.
      Error:
       Problem 1: conflicting requests
        - nothing provides /bin/ln needed by gskssl64-8.0-55.31.x86_64 from @commandline
       Problem 2: conflicting requests
        - nothing provides /bin/ln needed by gskcrypt64-8.0-55.31.x86_64 from @commandline
      (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages or '--setopt=optional_metadata_types=filelists' to load additional filelists metadata)
      
      bash-5.2$ rpm -qp gskssl64-8.0.55.31.linux.x86_64.rpm --requires | grep /bin/ln
      warning: gskssl64-8.0.55.31.linux.x86_64.rpm: Header V4 RSA/SHA256 Signature, key ID 96e7c766: NOKEY
      /bin/ln
      
      bash-5.2$ rpm -q --whatprovides /bin/ln
      coreutils-9.5-6.el10.x86_64
      
      bash-5.2$ sudo rpm -Uvh gskssl64-8.0.55.31.linux.x86_64.rpm gskcrypt64-8.0.55.31.linux.x86_64.rpm
      warning: gskssl64-8.0.55.31.linux.x86_64.rpm: Header V4 RSA/SHA256 Signature, key ID 96e7c766: NOKEY
      Verifying...                          ################################# [100%]
      Preparing...                          ################################# [100%]
      Updating / installing...
         1:gskcrypt64-8.0-55.31             ################################# [ 50%]
         2:gskssl64-8.0-55.31               ################################# [100%]
      
      
      

      Steps to reproduce

      1. Download the software from IBM, extract the gsk* rpm for the tarball
      2. try to install the gskssl64-8.0.55.31.linux.x86_64.rpm and gskcrypt64-8.0.55.31.linux.x86_64.rpm via dnf

      Expected results

      rpm gets installed without issues

      Actual results

      rpm gets refused with dependency issues

              rh-ee-lzaoral Lukáš Zaoral
              larshendrik.bussmann@bertelsmann.de Lars Bussmann
              Lukáš Zaoral Lukáš Zaoral
              Radka Brychtova Radka Brychtova
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: