Since this is not mandated by guidelines and it is just recommended practice, the "MUST exclude cached Gem" should be relaxed to SHOULD IMO.
True, I will fix this for the next version. Thank you for the report.
I have fixed this upstream, see [1]. The fix will be part of the next release. I will close this bug once the next release gets into Fedora. [1] https://fedorahosted.org/FedoraReview/changeset?reponame=&new=cce02c2d056e21ed6c2bc6e87c8f2c450c5768e6%40src&old=bd82abb2e3fb4ab64bd6354d118b8acb73cfdfec%40src
fedora-review-0.3.0-1.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/fedora-review-0.3.0-1.fc16
fedora-review-0.3.0-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/fedora-review-0.3.0-1.fc17
fedora-review-0.3.0-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/fedora-review-0.3.0-1.fc18
Package fedora-review-0.3.0-1.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing fedora-review-0.3.0-1.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-14663/fedora-review-0.3.0-1.fc18 then log in and leave karma (feedback).
Since the new version, that includes the fix, is stable now, I'm closing this bug.