perl-Config-Augeas-0.400-2.fc12.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 370928 [details] root.log root.log for i386
Created attachment 370929 [details] build.log build.log for i386
Created attachment 370930 [details] mock.log mock.log for i386
Created attachment 370931 [details] root.log root.log for x86_64
Created attachment 370932 [details] build.log build.log for x86_64
Created attachment 370933 [details] mock.log mock.log for x86_64
+ ./Build test /usr/share/augeas/lenses/dist/xinetd.aug:23.17-.33:invalid regexp /[^\001-\004\t\n +-=\\]+/: Invalid range end This is a manifestation of https://fedorahosted.org/augeas/ticket/35 Build test works with augeas from git, so this is blocking on either new augeas upstream release or patch in Fedora.
<lutter> apevec: you could work around it with 'export LANG=C' in %check This worked: http://koji.fedoraproject.org/koji/buildinfo?buildID=142858 I'll push this update to F-10/11/12 branches.
perl-Config-Augeas-0.501-1.fc10 has been submitted as an update for Fedora 10. http://admin.fedoraproject.org/updates/perl-Config-Augeas-0.501-1.fc10
perl-Config-Augeas-0.501-1.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/perl-Config-Augeas-0.501-1.fc11
perl-Config-Augeas-0.501-1.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/perl-Config-Augeas-0.501-1.fc12
perl-Config-Augeas-0.501-1.fc10 has been pushed to the Fedora 10 stable repository. If problems still persist, please make note of it in this bug report.
perl-Config-Augeas-0.501-1.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report.
perl-Config-Augeas-0.501-1.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.