mirror of
https://github.com/xcat2/xcat-dep.git
synced 2026-10-12 08:12:34 +00:00
Daniel Hilst
f72d5335be
dnf install xCATsn on an EL service node does not resolve. Against the repositories a service node has -- BaseOS and AppStream from copycds, plus xcat-core and xcat-dep -- it reports "nothing provides" for perl-IO-Tty, perl(IO::Pty), perl-Crypt-CBC, perl-Crypt-Rijndael, perl(Expect) and perl(HTML::Form), and per release for perl-Crypt-SSLeay, perl-Net-Telnet and perl-Digest-SHA1. The service node then has no xcatd, and every hierarchical case fails. packages-manifest.conf assumed CRB and EPEL stand behind every EL target. That holds for a management node and not for a service node, so those packages were built only for rocky-10-riscv64-xcat, the one target with no EPEL. Each EL target section now lists the perl packages BaseOS and AppStream do not carry. mockbuild-perl-packages.pl had no table entry for perl-IO-Tty, so no target could build it. Its sources move to IO-Tty 1.20 with a spec. In 1.12 the Makefile.PL pty probe only takes the address of each candidate function, the current toolchain drops that reference, the build then defines HAVE__GETPTY on a glibc that has no _getpty, and IO/Tty/Tty.so fails to load. 1.20 calls the function in the probe. perl-Net-DNS stays out. An EL10 service node needs it, this tree holds 0.80, and 0.80 has no KEY resource record that xCAT's ddns.pm builds. Signed-off-by: Daniel Hilst <392820+dhilst@users.noreply.github.com>