slimrat: FTBFS: POD errors

Bug #1507077 reported by Logan Rosen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
slimrat (Debian)
Fix Released
Unknown
slimrat (Ubuntu)
Triaged
High
Unassigned

Bug Description

Imported from Debian bug http://bugs.debian.org/724173:

Source: slimrat
Version: 1.0-1
Severity: serious
Tags: jessie sid
User: <email address hidden>
Usertags: qa-ftbfs-20130922 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> make[1]: Entering directory `/«PKGBUILDDIR»'
> rm -f debian/manpages
> test -d debian/pod2man || mkdir debian/pod2man
> for i in slimrat slimrat-gui; do \
> pod2man --section=8 src/$i > debian/pod2man/$i.8; \
> done
> Wide character in printf at /usr/share/perl/5.18/Pod/Simple.pm line 539.
> src/slimrat around line 600: Non-ASCII character seen before =encoding in 'Přemek'. Assuming UTF-8
> POD document had syntax errors at /usr/bin/pod2man line 71.
> Wide character in printf at /usr/share/perl/5.18/Pod/Simple.pm line 539.
> src/slimrat-gui around line 683: Non-ASCII character seen before =encoding in 'Přemek'. Assuming UTF-8
> POD document had syntax errors at /usr/bin/pod2man line 71.
> make[1]: *** [override_dh_installman] Error 255

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2013/09/22/slimrat_1.0-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Tags: ftbfs
Logan Rosen (logan)
Changed in slimrat (Ubuntu):
status: New → Triaged
importance: Undecided → High
tags: added: ftbfs
description: updated
Changed in slimrat (Debian):
importance: Undecided → Unknown
Changed in slimrat (Debian):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.