Red Hat Bugzilla – Bug 691483
[RFE] rebase augeas in RHEL
Last modified: 2013-09-19 08:20:09 EDT
augeas is used by netcf, but the netcf versions in all Fedora releases and RHEL are identical, and the Fedoras are already using augeas-0.8.0, so there should be no problems with netcf.
Case 00446661 filed with the same request.
2. What is the nature and description of the request?
Customer would like a rebase of augeas package in RHEL6
3. Why does the customer need this? (List the business requirements here)
It is a matter of automation, there are a large number of lenses added in
later augeas releases that allow easier scale and automation for our
systems. The more we can automate the less it costs. Couple this with the
fact that debugging output is broken in this version of augeas and for all
intent and purposes there isn't a great deal of utility in this particular
version of augeas. It is unable to parse EFI based grub entries,
/letc/login.defs, or a fair number of other files thus restricting our
ability to automate.
4. How would the customer like to achieve this? (List the functional
Customer want to see Augeas 0.8.0 or higher available in rhel 6 channel
5. For each functional requirement listed in question 4, specify how Red
Hat and the customer can test to confirm the requirement is successfully
He should be able to install Augeas 0.8.0 or higher in rhel 6 machine.
6. Is there already an existing RFE upstream or in Red Hat bugzilla?
7. How quickly does this need resolved? (desired target release)
8. Does this request meet the RHEL Inclusion criteria (please review)
9. List the affected packages
10. Would the customer be able to assist in testing this functionality if implemented?
This has missed the RHEL 6.1 window for rebases. Moving to 6.2, but with plan to get it into 6.2 early.
*** Bug 696271 has been marked as a duplicate of this bug. ***
Built augeas-0.9.0-1.el6 in brew
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.