Your package rsnapshot failed to build from source in current rawhide. http://koji.fedoraproject.org/koji/taskinfo?taskID=4979366 Build logs: root.log: http://kojipkgs.fedoraproject.org/work/tasks/9366/4979366/root.log build.log: http://kojipkgs.fedoraproject.org/work/tasks/9366/4979366/build.log state.log: http://kojipkgs.fedoraproject.org/work/tasks/9366/4979366/state.log NOTE: build logs are cleaned up after 1 week For details on mass rebuild see https://fedoraproject.org/wiki/Fedora_19_Mass_Rebuild
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
yup, looks like the newer pod2man (well technically Pod::Man under the hood) now errors when =over and =back's don't match up. I've contacted upstream and working on getting the upstream source fixed and then I'll do a release with a patch in the interim until the new upstream release comes out.
rsnapshot-1.3.1-10.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/rsnapshot-1.3.1-10.fc19
Package rsnapshot-1.3.1-10.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing rsnapshot-1.3.1-10.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-12671/rsnapshot-1.3.1-10.fc19 then log in and leave karma (feedback).
rsnapshot-1.3.1-10.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.