Bug 991875 - hugin: FTBFS in rawhide
Summary: hugin: FTBFS in rawhide
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: hugin
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Bruno Postle
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F20FTBFS 998564 1000961 1001341 1001342
TreeView+ depends on / blocked
 
Reported: 2013-08-05 02:52 UTC by Dennis Gilmore
Modified: 2013-08-27 19:26 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-08-27 19:26:07 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Dennis Gilmore 2013-08-05 02:52:27 UTC 
Your package hugin failed to build from source in current rawhide.

http://koji.fedoraproject.org/koji/taskinfo?taskID=5663415

Build logs:
root.log: http://kojipkgs.fedoraproject.org/work/tasks/3415/5663415/root.log
build.log: http://kojipkgs.fedoraproject.org/work/tasks/3415/5663415/build.log
state.log: http://kojipkgs.fedoraproject.org/work/tasks/3415/5663415/state.log
NOTE: build logs are cleaned up after 1 week

For details on mass rebuild see https://fedoraproject.org/wiki/Fedora_20_Mass_Rebuild
Comment 1 Rex Dieter 2013-08-26 14:14:30 UTC 
Looks like a perl'ism:

Wide character in printf at /usr/share/perl5/vendor_perl/Pod/Simple.pm line 539.
/builddir/build/BUILD/hugin-2012.0.0/doc/deghosting_mask.pod around line 90: Non-ASCII character seen before =encoding in 'Lukáš'. Assuming UTF-8
POD document had syntax errors at /usr/bin/pod2man line 69.
make[2]: Leaving directory `/builddir/build/BUILD/hugin-2012.0.0'
make[2]: *** [doc/deghosting_mask.1.gz] Error 255
Comment 2 Rex Dieter 2013-08-26 14:27:58 UTC 
Hoping this upstream fix helps, 
http://sourceforge.net/p/hugin/hugin/ci/aae44c4b0570e2cfc609e84d6e74d38a31453b73/

Submitted patched build...
http://koji.fedoraproject.org/koji/taskinfo?taskID=5854853
Comment 3 Rex Dieter 2013-08-27 19:26:07 UTC 
the upstream fix worked, closing.
Note You need to log in before you can comment on or make changes to this bug.