Bug #5662
closed
Zypper Management Technique doesn't behave correctly, and should be splitted in two separated techniques
Added by Nicolas CHARLES about 10 years ago.
Updated about 10 years ago.
Description
Zypper Management Technique tries to do two things at once:
- configure global Zypper parameters
- configure the repos
The issue here is that you can have several instance of this Technique used, and one may end up defining conflicting global zypper parameters, without knowing it.
The goal here is two split this technique in two, one for managing Zypper, and one for the repos
Unfortunately, there is no real overlap between features of Yum/APT and Zypper repo, so it would not make much sense to have on technique to manage them all (only APT and Zypper can define "Install recommends", only APT and Yum can define proxy)
- Status changed from In progress to Pending technical review
- Assignee changed from Nicolas CHARLES to Jonathan CLARKE
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/542
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset policy-templates:commit:b00b7603bb102eb4b6300753ab46c769c7640dff.
Applied in changeset policy-templates:commit:989a35dc439251d7ad2004cc3c56b17a9d3728f2.
- Subject changed from Zypper Management Technique doesn't behave correctly, and should be split in two to Zypper Management Technique doesn't behave correctly, and should be splitted in two separated techniques
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.10.7 and 2.11.4, which were released today.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by