Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Created attachment 849542 [details]
mock config for replication

Description of problem: Attempting to rebuild xvattr-1.3-24.el7 fails due to error in pod2man --center='User Commands' xvattr.pod >xvattr.1


Version-Release number of selected component (if applicable):xvattr-1.3-24.el7


How reproducible: 100%


Steps to Reproduce:
1. install minimal build environment with listed BuildRequires:
2. rpmbuild --rebuild xvattr-1.3-24.el7.src.rpm
3.

Actual results:
<snip>
pod2man --center='User Commands' xvattr.pod >xvattr.1
xvattr.pod around line 106: Non-ASCII character seen before =encoding in 'Bj�rn'. Assuming ISO8859-1
POD document had syntax errors at /usr/bin/pod2man line 69.
make: *** [xvattr.1] Error 255
make: *** Waiting for unfinished jobs....
error: Bad exit status from /var/tmp/rpm-tmp.FNREgJ (%build)
</snip>


Expected results:
can rebuild

Additional info:

%prep converts xvattr1 to utf8, but xvattr.pod has no =encoding and pod2man assumes iso8859-1.

This works, but I cannot remember having written something so ugly in a very long time:

# Convert man page to UTF-8
iconv -f iso8859-1 -t utf-8 -o tmp xvattr.pod
%{__mv} -f tmp xvattr.pod
iconv -f iso8859-1 -t utf-8 -o tmp xvattr.pod.in
%{__mv} -f tmp xvattr.pod.in
%{__perl} -lne 'print $_; print "\n\n=encoding utf8\n" if(/=pod/);' xvattr.pod.in >tmp
%{__mv} -f tmp xvattr.pod.in
%{__perl} -e 'use Pod::Man;' -e 'my $parser = Pod::Man->new(utf8);' -e '$parser->parse_from_file ("xvattr.pod", "xvattr.1");'
sed -i 's|pod2man|pod2man -u|' Makefile.am
sed -i 's|pod2man|pod2man -u|' Makefile.in

Fixed by importing F20's fix, see bug #993161 for details.