Please do not reply directly to this email. All additional comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=573151
--- Comment #15 from Steve Traylen steve.traylen@cern.ch 2010-03-17 16:16:41 EDT --- Created an attachment (id=400877) --> (https://bugzilla.redhat.com/attachment.cgi?id=400877) Clean rpmlint on .spec file.
This is cosmetic but cleans up:
python26.spec:342: W: unversioned-explicit-obsoletes Distutils python26.spec:343: W: unversioned-explicit-provides Distutils python26.spec:344: W: unversioned-explicit-obsoletes python2 python26.spec:415: W: unversioned-explicit-obsoletes python2-devel python26.spec:436: W: unversioned-explicit-obsoletes python2-tools python26.spec:451: W: unversioned-explicit-obsoletes tkinter2 python26.spec:730: E: hardcoded-library-path in %{buildroot}/usr/lib/python%{pybasever}/site-packages python26.spec:789: E: hardcoded-library-path in %{_prefix}/lib/debug/%{_libdir} python26.spec:956: E: hardcoded-library-path in %{_prefix}/lib/python%{pybasever} python26.spec:957: E: hardcoded-library-path in %{_prefix}/lib/python%{pybasever}/site-packages python26.spec: W: mixed-use-of-spaces-and-tabs (spaces: line 27, tab: line 159) python26.spec: W: %ifarch-applied-patch Patch101: python-2.3.4-lib64-regex.patch
to
python26.spec:728: E: hardcoded-library-path in %{buildroot}/usr/lib/python%{pybasever}/site-packages python26.spec:787: E: hardcoded-library-path in %{_prefix}/lib/debug/%{_libdir} python26.spec:954: E: hardcoded-library-path in %{_prefix}/lib/python%{pybasever} python26.spec:955: E: hardcoded-library-path in %{_prefix}/lib/python%{pybasever}/site-packages python26.spec: W: %ifarch-applied-patch Patch101: python-2.3.4-lib64-regex.patch
The hardcoded-lib-paths are easily justified. I leave to someone else to decide if that last patch is safe on other archs.