Skip Menu |

This queue is for tickets about the LaTeX-Encode CPAN distribution.

Report information
The Basics
Id: 88094
Status: resolved
Priority: 0/
Queue: LaTeX-Encode

People
Owner: chris.travers [...] gmail.com
Requestors: carnil [...] debian.org
Cc:
AdminCc:

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



Subject: [PATCH] Fix build failure with perl 5.18 in POD conversion due to stricter parser
Date: Sun, 25 Aug 2013 07:58:18 +0200
To: bug-latex-encode [...] rt.cpan.org
From: Salvatore Bonaccorso <carnil [...] debian.org>
Hi In Debian we are currently applying the attached patch to LaTeX-Encode. We thought you might be interested in it, too. Description: Add explicit encoding to POD Fix "FTBFS with perl 5.18: POD failure" as the new POD parser is more strict with perl 5.18. Bug-Debian: http://bugs.debian.org/720740 Author: Salvatore Bonaccorso <carnil@debian.org> Last-Update: 2013-08-25 --- Thanks in advance, Salvatore Bonaccorso, Debian Perl Group

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

Any news? Did you get a chance to look at the patch? intrigeri, Debian Perl Group
On Fri Jan 24 14:25:23 2014, intrigeri@boum.org wrote: Show quoted text
> Any news? Did you get a chance to look at the patch? > > intrigeri, Debian Perl Group > >
Sorry about the delay. I am taking ownership of this ticket. This year, the previous maintainer, Andrew Ford, passed away and I have taken over this project. I expect to get this patch reviewed and possibly applied today or tomorrow.
I have committed this to the repo and it will be in the next version.
On 2014-09-10 17:49:31, EINHVERFR wrote: Show quoted text
> I have committed this to the repo and it will be in the next version.
Please release this patch to the cpan -- the shipped version still shows this issue. (It is helpful to leave tickets open until they have actually been released, so as to avoid people opening a new ticket and forking the github repository to send a patch only to discover that it's already been fixed in git.)
On Fri Mar 13 18:20:53 2015, ETHER wrote: Show quoted text
> On 2014-09-10 17:49:31, EINHVERFR wrote: > (It is helpful to leave tickets open until they have actually been > released, so as to avoid people opening a new ticket and forking the > github repository to send a patch only to discover that it's already > been fixed in git.)
There's even a ticket status 'patched' meant for exactly this case.