Bug #5609
closed
It's not possible to update package to latest version
Added by Nicolas CHARLES about 10 years ago.
Updated about 10 years ago.
Description
Due to issues in the underlying code, it is not possible to update a package to the latest avaiable version.
But we can update it to a specific version, thanks to #5587
Note that behaviour changed in 3.5 and 3.6, so there may be several different fixes for that
Related bug is https://dev.cfengine.com/issues/6625
Well sadly it works only with yum systems...
- Status changed from New to Pending technical review
- Assignee set to Jonathan CLARKE
- Target version changed from 2.10.7 to 2.6.19
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/530
I fixed this on 2.6
However, when merging to 2.10, it will be necessary to add result to #5595 to be realy useful
- Assignee changed from Jonathan CLARKE to Benoît PECCATTE
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset policy-templates:commit:78d847af4d92a5476cf2d88034fdb7645c9e05c6.
- Category changed from 14 to Techniques
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.6.19, 2.10.7 and 2.11.4, which were these days.
- Related to Bug #4335: Impossible to upgrade rpm packages via RPM Technique added
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by