Details
-
Improvement
-
Resolution: Won't Fix
-
Minor
-
None
-
Lustre 2.3.0
-
None
-
CentOS 6.3 - kernel-2.6.32-279.el6.x86_64
-
8487
Description
Building the binary RPM from the source produced the incorrect RPM names.
http://downloads.whamcloud.com/public/lustre/lustre-2.3.0/el6/client/RPMS/x86_64/
lustre-client-2.3.0-2.6.32_279.5.1.el6.x86_64.x86_64.rpm
lustre-client-debuginfo-2.3.0-2.6.32_279.5.1.el6.x86_64.x86_64.rpm
lustre-client-modules-2.3.0-2.6.32_279.5.1.el6.x86_64.x86_64.rpm
lustre-client-source-2.3.0-2.6.32_279.5.1.el6.x86_64.x86_64.rpm
lustre-client-tests-2.3.0-2.6.32_279.5.1.el6.x86_64.x86_64.rpm
With centOS 6.3, kernel-2.6.32-279.el6.x86_64, my build ended up with the same RPMs names (i.e. x86_64.x86_64).
There is nothing wrong with the macros or the SPEC file. The fact that the kernel release already has "x86_64" in it (2.6.32-279.el6.x86_64) resulted in RPMs name with duplicated string "x86_64".
Could you update the upstream file, lustre.spec.in, to correct the naming to prevent the confusion now and in the future in case the future kernel release might carry "x86_64"?
Suggest to replace the line:
Release: %
with
Release: %(bash -c "echo %{fullrelease}
| sed -e 's/\.x86_64$//' -e 's/\.i[3456]86$//' -e 's/-smp$//' -e 's/-bigsmp$//' -e 's/-ppc64$//' -e 's/-default$//'")