Skip Menu |

This queue is for tickets about the JSON-Any CPAN distribution.

Report information
The Basics
Id: 90130
Status: resolved
Priority: 0/
Queue: JSON-Any
People
Owner: ether [...] cpan.org
Requestors: dmn [...] debian.org
Cc:
AdminCc:
Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: 1.33

History Show all quoted text
  Thu Nov 07 15:21:44 2013 dmn [...] debian.org - Ticket created
Subject: [PATCH] missing =encoding in JSON::Any POD
Date: Thu, 7 Nov 2013 21:36:12 +0200
To: bug-json-any [...] rt.cpan.org
From: Damyan Ivanov <dmn [...] debian.org>
Hi, While updating the Debian package of JSON-Any to version 1.32, I noticed that the generated manual page contains the following section: POD ERRORS Hey! The above document had some coding errors, which are explained below: Around line 701: Non-ASCII character seen before =encoding in 'Mannsaaker'. Assuming ISO8859-1 adding '=encoding ISO8859-1' fixes this. Trivial patch attached. Thanks for considering, dam, Debian Perl Group

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

  Wed Apr 16 20:34:24 2014 ether [...] cpan.org - Taken
  Wed Apr 16 22:04:56 2014 ether [...] cpan.org - Correspondence added
This should be fixed in 1.33.
  Wed Apr 16 22:04:57 2014 The RT System itself - Status changed from 'new' to 'open'
  Wed Apr 16 22:04:57 2014 ether [...] cpan.org - Status changed from 'open' to 'resolved'
  Thu Oct 23 18:16:53 2014 ether [...] cpan.org - Fixed in 1.33 added