From Fedora Project Wiki
No edit summary |
No edit summary |
||
| Line 10: | Line 10: | ||
</pre> | </pre> | ||
Because FC3 is not supported for long time | Because FC3 is not supported for long time, I'm proposing to change it to: | ||
<pre> | <pre> | ||
This error occurs because of DOS line breaks in a file. Fix it with in | This error occurs because of DOS line breaks in a file. Fix it with in | ||
the %prep section with sed: <code>%{__sed} -i 's/\r//' src/somefile</code> | the %prep section with sed: <code>%{__sed} -i 's/\r//' src/somefile</code> | ||
or dos2unix. | or dos2unix. | ||
</pre> | |||
But the problem could still be in EPEL4, so a note should be added to guidelines specific to it: <br /> | |||
https://fedoraproject.org/wiki/EPEL/GuidelinesAndPolicies#EL4 | |||
<pre> | |||
* Don’t use dos2unix under EPEL4, as it could fail. | |||
</pre> | </pre> | ||
Revision as of 07:06, 5 June 2009
Proposal to explicitly allow dos2unix
In guidelines in common errors section https://fedoraproject.org/wiki/Packaging/Guidelines#Rpmlint_Errors there is the following phrase:
This error occurs because of DOS line breaks in a file. Fix it with sed
in the %prep section: %{__sed} -i 's/\r//' src/somefile -- DONT use
dos2unix, that can cause build fail on FC3.
Because FC3 is not supported for long time, I'm proposing to change it to:
This error occurs because of DOS line breaks in a file. Fix it with in
the %prep section with sed: <code>%{__sed} -i 's/\r//' src/somefile</code>
or dos2unix.
But the problem could still be in EPEL4, so a note should be added to guidelines specific to it:
https://fedoraproject.org/wiki/EPEL/GuidelinesAndPolicies#EL4
* Don’t use dos2unix under EPEL4, as it could fail.