-
Notifications
You must be signed in to change notification settings - Fork 200
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
util.aug empty comments with CRLF line endings #161
Comments
Unfortunately, this leads to a typecheck error (run 'augparse lenses/util.aug over the changed file) Could you give an example of what causes CRLF errors for you ? |
I've caught a similar issue but could fix that in lens (nor did the above patch work for me): When a properties file have CRLF-style endings then empty lines (i.e. the lines which have no characters except CRLF in them) are not treated like those by Augeas but are transformed into paths like |
The problem happens probably only with empty comments. With LF line ending there is no issue, whether the comment is empty with space afterwards or without. timurb's issue is happening for me too, there are inaccessible nodes Example file is here: http://home.zcu.cz/~majlen/aaa.properties |
I got same problem now with CentOS-7-4 and its cloud-init update. Cloud-init adds now in /etc/resolv.conf
This secund line is a problem for puppet/augeas. |
Can you post the full resolv.conf that augeas barfs on ? That would help troubleshooting this a lot. |
Hi lutter, yep, thank you !
RPM versions / CentOS Linux release 7.4.1708 (Core)
When I play with augeas , it failes
When my puppet agent try to apply DNS config :
If I just remove line 2 which contain only the fire ; , provided by this cloud-init version, augeas do not fail. |
I have ran into this issue with Java .properties file with CRLF line endings.
Originally I used new properties.aug lens in augeas 0.10.0 and I had no issues. In augeas 1.2.0 I ran into issue in util.aug, which can be fixed with the included diff.
I do not see any issues with this change (it should be even correct, since for CRLF it is needed to select more (2) characters.
The text was updated successfully, but these errors were encountered: