Bug 525152 – app-misc/muttprint - src_compile(): pod2man: muttprint around line 1: Invalid =encoding syntax: ALREADYDONE =head1 NAME

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Bernd Raschke 2014-10-12 14:17:53 UTC]

Created attachment 386520 [details]
emerge --info

An update of muttprint to muttprint-0.73-r2 failed today, due to a suspected formatting error in the generated pod file:

pod2man --center="Muttprint Kurzanleitung" muttprint muttprint.1
muttprint around line 1: Invalid =encoding syntax: ALREADYDONE =head1 NAME
POD document had syntax errors at /usr/bin/pod2man line 71.

The suspected cause:
# head -2 /var/tmp/portage/app-misc/muttprint-0.73-r2/work/muttprint-0.73/doc/manpages/de/muttprint
=encoding latin1
=head1 NAME

From perlpod manual:
       "=encoding" affects the whole document, and must occur only once.

       And don't forget, when using any other command, that the command lasts
       up until the end of its paragraph, not its line.  So in the examples
       below, you can see that every command needs the blank line after it, to
       end its paragraph.

And indeed, adding a newline after the encoding directive enables me to build muttprint.

This affects all four language files in the manpages directory:
# head -2 ??/muttprint.pod
==> de/muttprint.pod <==
=encoding latin1
=head1 NAME

==> en/muttprint.pod <==
=encoding latin1
=head1 NAME

==> es/muttprint.pod <==
=encoding latin1
=head1 NOMBRE

==> it/muttprint.pod <==
=encoding latin1
=head1 NOME

[Comment 1 Bernd Raschke 2014-10-12 14:18:23 UTC]

Created attachment 386522 [details]
emerge -pqv

[Comment 2 Bernd Raschke 2014-10-12 14:20:36 UTC]

Created attachment 386524 [details]
build log

[Comment 3 Chema Alonso Josa (RETIRED) 2014-11-02 10:47:55 UTC]

Can't reproduce this here. I'm using =dev-lang/perl-5.18.2-r2.

Could you test it?. Thanks.

[Comment 4 Bernd Raschke 2014-11-04 22:08:51 UTC]

Created attachment 388556 [details]
tail of emerge with error

Still the same error.

[Comment 5 Bernd Raschke 2014-11-04 22:12:05 UTC]

Created attachment 388558 [details]
offensive file "muttprint"

generated by:
sed -e 's,##DOCDIR##,/usr/share/doc/muttprint,g' -e 's,##SHAREDIR##,/usr/share,g' -e 's,##BINDIR##,/usr/bin,g' -e 's,##SYSCONFDIR##,/etc,g' -e 's,##TEMPDIR##,/tmp,g' -e 's,##LIBDIR##,/usr/lib64,g' ./muttprint.pod > muttprint

error message:
# pod2man --center="Muttprint Kurzanleitung" muttprint muttprint.1
muttprint around line 1: Invalid =encoding syntax: ALREADYDONE =head1 NAME
POD document had syntax errors at /usr/bin/pod2man line 71.

[Comment 6 Chema Alonso Josa (RETIRED) 2014-12-19 22:23:50 UTC]

Sorry for the long delay.

I haven't managed to reproduce this at my side. Anyway I've bumped muttprint-0.73 to -r3 and added a newline after the =encoding line as stated in the perlpod manual.

Please, resync and confirm everything is okay. Thanks for the report

+*muttprint-0.73-r3 (19 Dec 2014)
+
+  19 Dec 2014; Chema Alonso <[e-mail]> +muttprint-0.73-r3.ebuild,
+  +files/muttprint-0.73-r3-pod-encoding.patch:
+  Fix bug 525152. Thanks to Bernd Raschke
+

[Comment 7 Bernd Raschke 2014-12-21 19:08:42 UTC]

Can confirm that app-misc/muttprint-0.73-r3 compiled on my system without error.

Thanks!

[Comment 8 Chema Alonso Josa (RETIRED) 2014-12-27 18:11:01 UTC]

Closing.