Bug 2193023

Summary: find_package draco, imported target "draco::draco_static" references the file "/usr/lib64/libdraco.a" does not exist.
Product: [Fedora] Fedora Reporter: Felix Wang <topazus>
Component: dracoAssignee: Luya Tshimbalanga <luya_tfz>
Status: CLOSED ERRATA QA Contact:
Severity: medium Docs Contact:
Priority: unspecified    
Version: rawhideCC: luya_tfz
Target Milestone: ---Keywords: Bugfix
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: draco-1.5.6-3.fc39 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-05-04 17:16:25 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Felix Wang 2023-05-04 03:03:19 UTC 
After installing draco-devel package and use find_package(draco REQUIRED) in cmake file, the following errors appeared, due to the missing draco static lib that removed from the spec file:
CMake Error at /usr/share/cmake/draco/draco-targets.cmake:83 (message):
  The imported target "draco::draco_static" references the file

     "/usr/lib64/libdraco.a"

  but this file does not exist.  Possible reasons include:

  * The file was deleted, renamed, or moved to another location.

  * An install or uninstall procedure did not complete successfully.

  * The installation package was faulty and contained

     "/usr/share/cmake/draco/draco-targets.cmake"

  but not all the files it references.

Call Stack (most recent call first):
  /usr/share/cmake/draco/draco-config.cmake:27 (include)
  CMakeLists.txt:17 (find_package)

Reproducible: Always
Comment 1 Fedora Update System 2023-05-04 17:15:07 UTC 
FEDORA-2023-61bc45563c has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-61bc45563c
Comment 2 Fedora Update System 2023-05-04 17:16:25 UTC 
FEDORA-2023-61bc45563c has been pushed to the Fedora 39 stable repository.
If problem still persists, please make note of it in this bug report.