mirror of
https://github.com/xcat2/xcat-dep.git
synced 2026-09-25 09:14:06 +00:00
Daniel Hilst
18a2fccba1
The 2.19 release needs riscv64 debs, and sbuild-all.pl accepted only amd64 and ppc64el, so no target produced them. The supported architecture set moves into BuildUtils as one source of truth (supported_arches/is_supported_arch), which --arch, --target and --expect-arch now consult; the mirror rule becomes "anything but amd64 is on ubuntu-ports", which is what ppc64el already needed and riscv64 needs too; and the genesis control remap stops naming ppc64el. ipmitool-xcat also could not build there. Its debian/control names architectures explicitly and omitted riscv64, so debhelper reported "No packages to build. Possible architecture mismatch" and the build died at ./configure. conserver and goconserver say Architecture: any and needed nothing. debs-manifest.conf gains a [<codename>-riscv64] section for each codename. It lists neither the x86 boot loaders -- a riscv64 node netboots UEFI grub2 -- nor xcat-genesis-base, whose riscv64 flavour is the OpenEmbedded one in the shared pool. t/sbuild-all.t covers the control-file defect: it fails on ipmitool without this change. Signed-off-by: Daniel Hilst <392820+dhilst@users.noreply.github.com>
28 lines
1.2 KiB
Plaintext
28 lines
1.2 KiB
Plaintext
Source: ipmitool-xcat
|
|
Section: utils
|
|
Priority: optional
|
|
Maintainer: xCAT <xcat-user@lists.sourceforge.net>
|
|
Build-Depends: debhelper (>= 12), libreadline-dev, libssl-dev, quilt
|
|
Standards-Version: 3.6.2.1
|
|
|
|
Package: ipmitool-xcat
|
|
Architecture: i386 amd64 ia64 ppc64el riscv64
|
|
Depends: libc6 (>= 2.15), libssl3t64 | libssl3 | libssl1.1
|
|
Suggests: openipmi
|
|
Description: utility for IPMI control with kernel driver or LAN interface
|
|
A utility for managing and configuring devices that support the
|
|
Intelligent Platform Management Interface. IPMI is an open standard
|
|
for monitoring, logging, recovery, inventory, and control of hardware
|
|
that is implemented independent of the main CPU, BIOS, and OS. The
|
|
service processor (or Baseboard Management Controller, BMC) is the
|
|
brain behind platform management and its primary purpose is to handle
|
|
the autonomous sensor monitoring and event logging features.
|
|
.
|
|
The ipmitool program provides a simple command-line interface to this
|
|
BMC. It features the ability to read the sensor data repository
|
|
(SDR) and print sensor values, display the contents of the System
|
|
Event Log (SEL), print Field Replaceable Unit (FRU) inventory
|
|
information, read and set LAN configuration parameters, and perform
|
|
remote chassis power control.
|
|
|