Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Receiving error while building "redhat-logos-84.5-1.el8.src.rpm
=================================================================
The command "rpmbuild -ba redhat-logos.spec" returns with:
error: Failed build dependencies:
syslinux-perl is needed by redhat-logos-84.5-1.el8.x86_64
================================================================
I have checked with Backline(Steven Gardner-gsound) and he has mentioned the following.
~~~
I checked the spec file, and yes the spec file does claim that syslinux-perl is required to build the rpm. I also attempted to build myself and got the same error. But I'm not 100% sure if the spec file is actually correct, maybe the spec file is just wrong.
Regardless, if the spec file requires it to build then we need to offer the package in some repo somewhere.
~~~
Comment 3Marta Lewandowska
2023-03-10 09:53:03 UTC
I was able to build the rpm after taking out the dependency and didn't get any errors, but I can't judge if it's necessary or not.
syslinux-perl was built as part of syslinux: https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=2110121 but was not pushed to any repos from what we can tell.
changing component to redhat-logos.
Comment 4Ray Strode [halfline]
2023-03-10 15:10:14 UTC
syslinux-perl ships with a utility called ppmtolss16 which converts a boot splash graphic from one kind of bitmap to another kind of bitmap. It's needed for syslinux.
redhat-logos used to call ppmtolss16 during its build process, but these days we just ship the converted bitmap directly.
So we can drop the build dependency
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (redhat-logos bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2023:7108
Receiving error while building "redhat-logos-84.5-1.el8.src.rpm ================================================================= The command "rpmbuild -ba redhat-logos.spec" returns with: error: Failed build dependencies: syslinux-perl is needed by redhat-logos-84.5-1.el8.x86_64 ================================================================ I have checked with Backline(Steven Gardner-gsound) and he has mentioned the following. ~~~ I checked the spec file, and yes the spec file does claim that syslinux-perl is required to build the rpm. I also attempted to build myself and got the same error. But I'm not 100% sure if the spec file is actually correct, maybe the spec file is just wrong. Regardless, if the spec file requires it to build then we need to offer the package in some repo somewhere. ~~~