Skip Menu |

This queue is for tickets about the Geo-Coordinates-OSGB CPAN distribution.

Report information
The Basics
Id: 89214
Status: resolved
Worked: 30 min
Priority: 0/
Queue: Geo-Coordinates-OSGB

People
Owner: toby [...] cpan.org
Requestors: gregoa [...] debian.org
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: [PATCH] POD fix
Date: Wed, 2 Oct 2013 23:44:26 +0200
To: bug-geo-coordinates-osgb [...] rt.cpan.org
From: gregor herrmann <gregoa [...] debian.org>
In Debian we are currently applying the attached patch to Geo-Coordinates-OSGB. We thought you might be interested in it, too. Description: add =encoding to fix POD ERROR Origin: vendor Author: gregor herrmann <gregoa@debian.org> Last-Update: 2013-10-02 Thanks in advance, gregor herrmann, Debian Perl Group

Message body is not shown because sender requested not to inline it.

On Wed Oct 02 17:44:45 2013, gregoa@debian.org wrote: Show quoted text
> In Debian we are currently applying the attached patch to Geo- > Coordinates-OSGB. > We thought you might be interested in it, too. > > Description: add =encoding to fix POD ERROR > Origin: vendor > Author: gregor herrmann <gregoa@debian.org> > Last-Update: 2013-10-02 > > > Thanks in advance, > gregor herrmann, Debian Perl Group
I have investigated and fixed this bug. Adding the "=encoding" directive was a sensible suggestion but it is not supported on all current levels of Perl (eg my mac system still has 5.12 as the default). So I decided simply to remove the two offending UTF-8 characters from the POD, and I have added a step to my build checks to ensure that the POD only contains plain ASCII characters. The new version 2.06 is on it's way to CPAN.