This repository has been archived by the owner on Dec 13, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 102
/etc/rpc-release should have a linefeed at the end of the file #938
Milestone
Comments
Says who? |
says me |
No other distro release files do... hence why it does not. |
/etc/redhat-release doesn't? |
/etc/lsb-release /etc/os-release do not. |
@claco ummm - it does too. |
sure does not on my 12.04 install. |
|
opened in stock vi. No line feed. |
vi /etc/rpc-release
|
here is some more information
|
breu
changed the title
/etc/rpc-release should have a newline at the end of the line
/etc/rpc-release should have a newline at the end of the file
Apr 21, 2014
Then it's a problem with https://github.com/rcbops-cookbooks/osops-utils/blob/master/recipes/version.rb#L22
We most certainly don't want a newline. |
0x0a is your linefeed. That is present in the files you references, but not /etc/rpc-release |
breu
changed the title
/etc/rpc-release should have a newline at the end of the file
/etc/rpc-release should have a linefeed at the end of the file
Apr 21, 2014
edited title so it reflects a linefeed instead of a newline |
here is a proposed solution: https://github.com/rackerjoe/rcbops-osops-utils/commit/5e844726286648ba26ce4cd002f45c31be6a0e8d |
claco
added a commit
to claco/osops-utils
that referenced
this issue
May 23, 2014
Unlike other release files in /etc, the rpc-release did not have a proper line-feed at the end of the file. - Change version recipe to add LF to /etc/rpc-release Issue rcbops/chef-cookbooks#938
claco
added a commit
to claco/osops-utils
that referenced
this issue
May 27, 2014
Unlike other release files in /etc, the rpc-release did not have a proper line-feed at the end of the file. - Change version recipe to add LF to /etc/rpc-release Issue rcbops/chef-cookbooks#938 (cherry picked from commit af1beef)
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
No description provided.
The text was updated successfully, but these errors were encountered: