On Tue, 2013-04-30 at 20:59 +0000, Bohne, Andrew wrote: > In my %install section I have the following lines consecutively: > > > > %{__cp} -a bin/%{name} ${RPM_BUILD_ROOT}%{_bindir}/%{name} > > %{__cp} -a bin/%{name} ${RPM_BUILD_ROOT}%{_bindir}/%{name}-2 > > > > And in the %files section I have > > > > %attr(0755,root,root) %{_bindir}/* > > > > The files are both added to the rpm in the correct spot, but > %{_bindir}/%{name} is added as a 0 byte file, while > %{_bindir}/%{name}-2 is added as the correct size. The source file is > a shell script if that has any bearing on the matter. That is odd. Have you tried doing a rpmbuild -bi and inspecting the files in the buildroot? Also, minor nitpick, when two files are identical I usually prefer to make one a symlink to the other. Maybe there's a valid reason why you are not but that seems to be the norm. e.g. cp -a bin/%{name} %{buildroot}%{_bindir}/%{name} ln -sf %{name} %{buildroot}%{_bindir}/%{name}-2 Minor nitpick 2 - I prefer not to use %{name} in a filelist because if you change the name of the package, it breaks the filelist. e.g. you come out with foo v3 but you want foo v2 to be installable as well side by side, so you change the name of foo v2 package from foo to foo2 and rebuild. _______________________________________________ Rpm-list mailing list Rpm-list@xxxxxxxxxxxxx http://lists.rpm.org/mailman/listinfo/rpm-list