Actions
Bug #5174
closed
Use of a wrong conditional to detect if we are building on sles in several package specfile
Status:
Released
Priority:
1 (highest)
Assignee:
Jonathan CLARKE
Category:
Packaging
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
This conditionnal is wrong:
%if 0%{?sles}
it should be replaced with:
%if 0%{?sles_version}
This problem impacts the dependencies of the new webapp rudder handling, and ncf-api-virtualenv
Updated by Matthieu CERDA over 10 years ago
- Project changed from Rudder to 34
- Status changed from In progress to Pending technical review
- Assignee changed from Matthieu CERDA to Jonathan CLARKE
- % Done changed from 0 to 100
- Pull Request set to https://github.com/Normation/rudder-packages/pull/421
PR is ready !
Updated by Vincent MEMBRÉ over 10 years ago
- Status changed from Pending technical review to Pending release
This was fixed on Friday 27/06 by commit:bbf8a68113e9b46dd8e4b68e0bb9eab35b13d349
Updated by Vincent MEMBRÉ over 10 years ago
- Subject changed from 2.11 SLES RPMs sometimes use a wrong conditionnal to detect if we are building on sles to Use of a wrong conditionnal to detect if we are building on sles in several package specfile
Updated by Vincent MEMBRÉ over 10 years ago
- Subject changed from Use of a wrong conditionnal to detect if we are building on sles in several package specfile to Use of a wrong conditional to detect if we are building on sles in several package specfile
Updated by Vincent MEMBRÉ over 10 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.11.0~beta2 (announcement , changelog), which were released today.
- Download information: https://www.rudder-project.org/site/get-rudder/downloads/
Updated by Benoît PECCATTE almost 10 years ago
- Project changed from 34 to Rudder
- Category set to Packaging
Actions