On Thu, Jun 29, 2017 at 12:06:21PM +0100, Dominic Hargreaves wrote: > On Tue, Jun 27, 2017 at 08:55:00AM +0000, Niels Thykier wrote: > > On Sat, 3 Dec 2016 14:12:53 +0000 Dominic Hargreaves <d...@earth.li> wrote: > > > [...] > > > > > > Hi Niels, > > > > > > (and sorry about the silence). > > > > > > No, not yet. That will need a full rebuild with the debhelper change > > > reverted, and I'm unlikely to have time to do that until the new year. > > > > > > Cheers, > > > Dominic. > > > > > > > > > > Ping. :) > > > > I was reminded of this due to a related chat on #d-perl today. :) > > Hi Niels, > > Sorry about this. At this stage I think it might be better to wait > until perl 5.26 has transitioned, so we can reassess all the various > breakages without the local modifications that we introduced for 5.24. > > I think a transition bug will be opened soon, so this shouldn't delay > by more than another couple of months, which should be acceptable for > the buster release?
(For the bug record). Niels removed this from debhelper compat 11: https://anonscm.debian.org/git/debhelper/debhelper.git/tree/debhelper.pod#n683 but I don't this changes my plan above to push on this after the perl 5.26 transition is underway. It means that module maintainers can move to debhelper 11 as a way to verify whether their packages need properly fixing. Thanks Niels! Dominic.