Bug 1709416

Summary: [RFE] rebase augeas in RHEL 8.1
Product: Red Hat Enterprise Linux 8 Reporter: Pino Toscano <ptoscano>
Component: augeasAssignee: Pino Toscano <ptoscano>
Status: CLOSED ERRATA QA Contact: YongkuiGuo <yoguo>
Severity: medium Docs Contact:
Priority: medium    
Version: 8.1CC: mtessun, ptoscano, rjones, yoguo
Target Milestone: betaKeywords: Rebase
Target Release: 8.1Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: augeas-1.12.0-1.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-11-05 22:18:06 UTC Type: Enhancement
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1671950    

Description Pino Toscano 2019-05-13 14:43:32 UTC 
Description of problem:
The version of augeas shipped in RHEL 8.0 is 1.10.1, released at the end of January 2018.
In the meanwhile, two new upstream versions were released (1.11.0, 1.12.0), providing new lenses for handling (new) configuration files, fixes to existing lens (e.g. new configuration keys), and also memory improvements (e.g. issue 569).

augeas maintains a strong binary compatibility, so applications linked to it will continue to work as expected.
The shipped lenses generally maintain compatibility with the tree of the parsed options; rarely there may happen commits that change the parsed tree, however it is not the case between the versions in our case (i.e. 1.10.1 -> 1.12.0).

[1] https://github.com/hercules-team/augeas/issues/569

Version-Release number of selected component (if applicable):
1.12.0 is the current target.
Comment 2 YongkuiGuo 2019-07-31 09:19:42 UTC 
Verified with the package:
augeas-1.12.0-2.el8.x86_64

Gating test result:
https://dashboard.osci.redhat.com/#/artifact/brew-build/aid/21958563

Result: PASSED
Comment 4 errata-xmlrpc 2019-11-05 22:18:06 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2019:3576