[cmake-developers] [CMake 0013248]: CPackRPM bug - empty per-component REQUIRES
Mantis Bug Tracker
mantis at public.kitware.com
Fri May 25 06:57:57 EDT 2012
The following issue has been SUBMITTED.
======================================================================
http://public.kitware.com/Bug/view.php?id=13248
======================================================================
Reported By: Sergei Golubchik
Assigned To:
======================================================================
Project: CMake
Issue ID: 13248
Category: CPack
Reproducibility: always
Severity: major
Priority: normal
Status: new
======================================================================
Date Submitted: 2012-05-25 12:57 CEST
Last Modified: 2012-05-25 12:57 CEST
======================================================================
Summary: CPackRPM bug - empty per-component REQUIRES
Description:
If building per-component RPMs and some rpms have OBSOLETES (or REQUIRES,
whatever) and other don't - in this case all rpm's that don't provide OBSOLETES
will inherit the OBSOLETES header of the previous (in the alphabetical order)
component. It happens because CPackRPM does not unset the corresponding header
variable, when a per-component variable is not set. This patch fixes it:
--- CPackRPM.cmake 2012-05-25 12:50:53.000000000 +0200
+++ CPackRPM.cmake 2012-05-25 12:50:45.000000000 +0200
@@ -488,6 +488,8 @@
MESSAGE("CPackRPM:Debug: User defined ${_PACKAGE_HEADER_NAME}:\n
${CPACK_RPM_PACKAGE_${_RPM_SPEC_HEADER}_TMP}")
ENDIF(CPACK_RPM_PACKAGE_DEBUG)
SET(TMP_RPM_${_RPM_SPEC_HEADER} "${_PACKAGE_HEADER_NAME}:
${CPACK_RPM_PACKAGE_${_RPM_SPEC_HEADER}_TMP}")
+ELSE(CPACK_RPM_PACKAGE_${_RPM_SPEC_HEADER}_TMP)
+ UNSET(TMP_RPM_${_RPM_SPEC_HEADER})
ENDIF(CPACK_RPM_PACKAGE_${_RPM_SPEC_HEADER}_TMP)
ENDFOREACH(_RPM_SPEC_HEADER)
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
2012-05-25 12:57 Sergei GolubchikNew Issue
======================================================================
More information about the cmake-developers
mailing list