Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: This is not necessarily a bug in rpm, although I would appreciate some help figuring out the cause. The new pre-push hook in Fedora git repos did not permit a push to the fontawesome-fonts repo. See this bug report: https://pagure.io/fedpkg/issue/517. As noted there, rpm seems to fail to expand %{fontpkgname1} and %{fontpkgname2}. $ python3 Python 3.11.2 (main, Feb 8 2023, 00:00:00) [GCC 12.2.1 20221121 (Red Hat 12.2.1-4)] on linux Type "help", "copyright", "credits" or "license" for more information. >>> import rpm >>> spec=rpm.spec('fontawesome-fonts.spec') >>> spec.sources [('fontawesome-fonts-opentype-css.patch', 0, 2), ('60-%{fontpkgname2}.conf', 4, 1), ('60-%{fontpkgname1}.conf', 3, 1), ('README-Trademarks.txt', 2, 1), ('trademarks.py', 1, 1), ('https://github.com/FortAwesome/Font-Awesome/archive/6.4.0/Font-Awesome-6.4.0.tar.gz', 0, 1)] Since the package builds successfully in both mock and koji, those macros are expanded successfully at RPM build time. Version-Release number of selected component (if applicable): rpm-4.18.0-1.fc37.x86_64 python3-rpm-4.18.0-1.fc37.x86_64 How reproducible: Always Steps to Reproduce: 1. sudo dnf install rpmdevtools 2. fedpkg clone fontawesome-fonts 3. cd fontawesome-fonts 4. spectool fontawesome-fonts.spec (or use rpm's python interface directly as shown above) Actual results: Source0: https://github.com/FortAwesome/Font-Awesome/archive/6.4.0/Font-Awesome-6.4.0.tar.gz Source1: trademarks.py Source2: README-Trademarks.txt Source3: 60-%{fontpkgname1}.conf Source4: 60-%{fontpkgname2}.conf Patch0: fontawesome-fonts-opentype-css.patch Expected results: Source0: https://github.com/FortAwesome/Font-Awesome/archive/6.4.0/Font-Awesome-6.4.0.tar.gz Source1: trademarks.py Source2: README-Trademarks.txt Source3: 60-fontawesome-6-free-fonts.conf Source4: 60-fontawesome-6-brands-fonts.conf Patch0: fontawesome-fonts-opentype-css.patch Additional info:
The problem is that those sources refer to macros that are not yet defined at that point, because "%fontpkg -a" only gets called much later. This happens to "work" during an actual build due to side-effects from the way rpm parses specs with BuildArchitecture:, but relying on that is walking on very very thin ice.
This message is a reminder that Fedora Linux 37 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 37 on 2023-12-05. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '37'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 37 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
This bug appears to have been reported against 'rawhide' during the Fedora Linux 40 development cycle. Changing version to 40.
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.
This is a duplicate, and the main bug has been fixed. Closing this one. Many thanks to the rpm team for the fix.