Attempts to use `dodoc' on files of 0 bytes will cause it to fail. Example Case: Package contains a NEWS file, however, there is no news to report, thus the file has nothing in it. Ii may contain data in the future, so in the interests of this possibility, the NEWS file is run through dodoc anyways, even though it'll produce a 0 byte output file to get merged into the system. Two solutions are illustrated here: 1) Make dodoc use the `-e ' instead of `-s' to check only if the file exists. 2) Make the error message more clear that dodoc does not operate on 0 byte files. The first option is if it's decided to make dodoc handle 0-byte files. The second option is if the decision is made to leave it as-is (thus necessitating the change in the error message to be more clear why the operation failed). Patches attached for both options.
Created attachment 58318 [details, diff] Change `-s' to `-e'
Created attachment 58319 [details, diff] Make error message more clear
i already fixed cvs with -e/-s
This doesn't appear to be InCVS at all... Personally, I'm for the better error message.
sure it is http://www.gentoo.org/cgi-bin/viewcvs.cgi/portage/bin/dodoc?root=gentoo-src&r1=1.6&r2=1.7
if [ -s "${x}" ] ; then ... else echo "dodoc: ${x} does not exist" 1>&2 fi ^^^ This is the same in both versions but this is what the bug is about if I'm not mistaken.
Fixed on or before 2.0.51.22-r1
Looking through the batch of bugs, I'm not sure that some of these are actually fixed in stable. Others, the requirements have possibly changed after the initial fix was committed. If you think this bug has been closed incorrectly, please reopen or ask that it be reopened.
