Bug #4128
closed
Technique "RUG / YaST package manager configuration (ZMD)": 'security-level' option is misnamed 'package source policy'
Description
Actually, this is not possible to add a repository into SLES10 if the option 'security-level' is set to 'signature'.
It would be great if it was possible to be able to configure rug options, at least 'security-level'.
Updated by Nicolas PERRON about 11 years ago
- Target version changed from 2.4.12 to 2.4.13
Updated by Nicolas PERRON about 11 years ago
In fact, this is possible to set it but the option to set it is not clear: "package source policy" when "security-level" is used by Rug.
I suppose we can reject this bug.... or maybe rename the option.
Updated by François ARMAND almost 11 years ago
- Subject changed from Technique "RUG / YaST package manager configuration (ZMD)": Permit to configure options like 'security-level' of rug to Technique "RUG / YaST package manager configuration (ZMD)": 'security-level' option is misnamed 'package source policy'
- Assignee set to Jonathan CLARKE
Jon, seems like a bug, no ?
Updated by Jonathan CLARKE almost 11 years ago
- Status changed from New to Discussion
- Assignee changed from Jonathan CLARKE to Nicolas PERRON
I'm sorry, but I don't understand the problem. Nicolas, could you clarify please? What are these options for, and why do they matter? Thanks.
Updated by Nicolas PERRON almost 11 years ago
- Assignee changed from Nicolas PERRON to Jonathan CLARKE
The problem is that "Package source policy" is not clear: the option into Rug is named "security-level" (it permit to configure if we need to check GPG keys or not).
Updated by Jonathan CLARKE almost 11 years ago
Nicolas PERRON wrote:
The problem is that "Package source policy" is not clear: the option into Rug is named "security-level" (it permit to configure if we need to check GPG keys or not).
OK. So could this just be changed with a 1 line patch to rename the option? If so, could you just open the PR please? It will be a lot quicker than me trying to understand and doing it, etc... :)
Updated by Jonathan CLARKE almost 11 years ago
- Assignee changed from Jonathan CLARKE to Nicolas PERRON
Updated by Vincent MEMBRÉ almost 11 years ago
- Target version changed from 2.4.13 to 2.6.11
Since version 2.4 is not maintained anymore, retargeting to branch 2.6
Updated by Nicolas PERRON almost 11 years ago
- Tracker changed from User story to Bug
- Status changed from Discussion to In progress
Updated by Nicolas PERRON almost 11 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Nicolas PERRON to Jonathan CLARKE
- % Done changed from 0 to 100
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/294
Pull Request URL added: https://github.com/Normation/rudder-techniques/pull/294
Jon, could you review it please ?
Updated by Nicolas PERRON almost 11 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset commit:5f970406591c243fcefd19c3db893cd31119e1a7.
Updated by Jonathan CLARKE almost 11 years ago
Applied in changeset commit:27c6657ca4c5acdb155962677761680510c32855.
Updated by Vincent MEMBRÉ almost 11 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.6.11, which was released today.
Check out:
- The release announcement: http://www.rudder-project.org/pipermail/rudder-announce/2014-March/000077.html
- The full ChangeLog: http://www.rudder-project.org/foswiki/bin/view/System/Documentation:ChangeLog26
- Download information: https://www.rudder-project.org/site/get-rudder/downloads/
Updated by Benoît PECCATTE almost 10 years ago
- Project changed from 24 to Rudder
- Category set to Techniques