Bug 2381330 - os-autoinst: FTBFS with change proposal CMake drop non-standard variables
Summary: os-autoinst: FTBFS with change proposal CMake drop non-standard variables
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: os-autoinst
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Adam Williamson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 2376113
TreeView+ depends on / blocked
 
Reported: 2025-07-16 16:51 UTC by Cristian Le
Modified: 2025-09-17 20:21 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-09-17 20:21:12 UTC
Type: ---
Embargoed:
fedora-admin-xmlrpc: mirror+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker FC-2294 0 None None None 2025-09-17 20:01:33 UTC

Description Cristian Le 2025-07-16 16:51:21 UTC
Dear package maintainer,

This is an automated bug created due to a FTBFS when rebuilding this package for the change proposal CMake drop non-standard variables.

The rebuild is being tracked in https://copr.fedorainfracloud.org/coprs/lecris/cmake-drop_vars/package/os-autoinst.

See https://fedoraproject.org/wiki/Changes/CMake_drop_install_vars for more information on how to make the package compatible.

Most likely the build failure is due to the project assuming the presence of `LIB_SUFFIX` as an input. You can provide
this variable as shown in the change proposal. If possible, please open an issue in upstream and ask them to use
`GNUInstallDirs` instead.

You can check the build locally following the instructions in the change proposal, or submit your build to the tracking
copr project.

Let me know if you encounter any issues, or need any other help.

Comment 1 Adam Williamson 2025-09-17 20:01:11 UTC
Builds are too old to see now.

Comment 2 Cristian Le 2025-09-17 20:21:12 UTC
It failed on ppc instead of x86_64, for this change proposal, I suspect only x86_64 to be affected or all of them, so probably a false-positive


Note You need to log in before you can comment on or make changes to this bug.