perl-SVN-Mirror-0.75-2.fc11.src.rpm Failed To Build From Source against the rawhide tree. See http://fedoraproject.org/wiki/FTBFS for more information.
Setting to ASSIGNED per Fedora Bug Triage workflow. https://fedoraproject.org/wiki/BugZappers/BugStatusWorkFlow
Created attachment 353620 [details] root.log root.log for i386
Created attachment 353621 [details] build.log build.log for i386
Created attachment 353622 [details] mock.log mock.log for i386
Created attachment 353623 [details] root.log root.log for x86_64
Created attachment 353624 [details] build.log build.log for x86_64
Created attachment 353625 [details] mock.log mock.log for x86_64
http://koji.fedoraproject.org/koji/buildinfo?buildID=121496 failed in koji
This package failed to build in Koji for Fedora 12, and at this point in the release cycle (Beta is out), we'll have to live with the F11 build of the package unless there is another bug in your package which would prevent the release of Fedora 12. If your package is now obsolete and should be removed from Fedora 12 and future, please follow the End of Life instructions here: https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life If your package is not obsolete, and you wish it to remain in the distribution for Fedora 13, please update your package's devel branch in CVS so that it builds, build it in koji, and close this bug as "CLOSED RAWHIDE", including the link to the koji build that succeeded. You can do this now, while final touches are being placed on Fedora 12 without affecting F12. Shortly after F12 is out, but before the F13 Alpha release, all F12FTBFS-blocking bugs will be re-evaluated. At that time, if progress has not been made to fix the package, it will be removed from the distribution for F13.
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle. Changing version to '12'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
The problem seems to be an incompatibility between SVN::Mirror and subversion 1.6. It seems to be the same bug as http://rt.cpan.org/Public/Bug/Display.html?id=51088 and http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=543099.
There hasn't been any response by the SVN::Mirror author and the module hasn't been updated since 2008. The package was removed from Debian and may have to be removed from Fedora.
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.