Missing ChangeLog when compiling with bundled spec file

[Google Code Exporter]

When recompiling pdsh from the tarball with
   rpmbuild -ta  --with genders --with nodeattr pdsh-2.27.tar.bz2
the packaging dies while processing files with the following error:

+ cp -pr COPYING README ChangeLog NEWS DISCLAIMER 
/var/tmp/pdsh-2.27-1-root-root/usr/share/doc/pdsh-2.27
cp: cannot stat `ChangeLog': No such file or directory
error: Bad exit status from /var/tmp/rpm-tmp.87249 (%doc)

A quick check in the spec file show around line 363
%files
%defattr(-,root,root)
%doc COPYING README ChangeLog NEWS DISCLAIMER 
%doc README.KRB4 README.modules README.QsNet
%{_bindir}/pdsh

But the ChangeLog file is missing. There are 2 solution: 1) bundle the 
ChangeLog file in the tarball or 2) remove the ChangeLog file from the %doc 
entry.

Unluck redhat doesn't ship a precompiled rpm for this great program so it is 
better if the spec file is in order i think :)

Thank you very much

Original issue reported on code.google.com by [e-mail] on 6 Feb 2012 at 2:15

[Google Code Exporter]

Sorry I didn't respond to this issue sooner.

The fix is already in pdsh-2.28, which I realize I haven't uploaded to
the Downloads section yet. I'll get to that immediately.

Thanks

Original comment by [e-mail] on 11 Feb 2012 at 2:47

• Changed state: Accepted

[Google Code Exporter]

Ok, pdsh-2.28 is up in the Downloads section. Can you try that and let me know
if you still see a problem?

Thanks!

Original comment by [e-mail] on 11 Feb 2012 at 3:23

[Google Code Exporter]

Thank you very much for the upload. I will try pdsh-2.28 at work on monday (we 
use it on our Scientific HPC). It's a pain for me to connect to it from my home 
due to my very fragile and slow internet connection.

See you on Monday!
Best regards

Original comment by [e-mail] on 11 Feb 2012 at 3:59

[Google Code Exporter]

Sorry for the late, i got the usual bunch of Monday-problems (HD failure on a 
server raid controller). pdsh-2.28 builds (and works) like a charm without the 
need of a workaround.

You can close the issue (the interface doesn't seems to let me close it)

Thank you very much

Original comment by [e-mail] on 13 Feb 2012 at 10:56

[Google Code Exporter]

Original comment by [e-mail] on 15 Feb 2012 at 5:06

• Changed state: Done