On Fri, Jun 23, 2017 at 09:19:43PM +0100, Dominic Hargreaves wrote: > On Fri, Jun 23, 2017 at 07:43:52PM +0200, gregor herrmann wrote:
> > So it looks like we really need PERL_USE_UNSAFE_INC, and we might > > want to insert it unconditionally manually where we did prior to the > > accidental removal in the last upload. > It does rather look like a mistaken attempt to solve this problem, and > I agree that the logic is a bit odd, but this seems like the patch > likely to get accepted upstream; can you send this patch to the module > author? > > I feel like we should try and not diverge further from upstream; that > seems almost guaranteed to end up with similar issues later. FWIW, I've scheduled a test rebuild of all the 679 libmodule-build-perl reverse build dependencies on perl.debian.net to get a feeling of how widespread this issue actually is. If it's bad enough, we should probably patch around it temporarily in any case and drop it later in a more controlled fashion. I'll follow up with an update once we have results. -- Niko
